Skip to content
MLNetworks

MLNetworks for Mobile Network Operators

Keep sites in service. Plan the upgrade.

Site incidents, power, field work and upgrade planning on one platform, so an outage has a cause and the next capex round has its data.

A city skyline with a cell tower rising above the rooftops

Thousands of sites.One incident list.

From alarm to restored service

One incident, from alarm to closure.

From the first alarm at a site to the proof of visit, on one record.

  1. 01

    Related alarms become one incident

    Alarms from the same event at a site are grouped. Repeats are counted, not queued again.

    • Mains failureAC gridRaised 7 times02:14
    • Generator failed to startGenerator02:15
    • Low battery voltageBattery03:02

    INC-2041

    Site power issue

    Ridgeview RDG-0417

    HighInvestigating

    Correlated alarms

    3 related alarms, grouped into one incident

  2. 02

    The work is assigned and scheduled

    The work order carries the incident and the site data, so the field engineer does not start from a blank ticket.

    All Work Orders

    Search by ID, title, site
    IDTitleStatus
    WO-7718Inspect generator start circuitAssigned
    WO-7719Check battery terminalsAccepted
    WO-7720Walk the tower baseCreated

    Showing 3 work orders at Ridgeview RDG-0417

    Next steps

    AcceptedReassign
  3. 03

    Closed on proof of visit

    The job form and photos are reviewed before the ticket is closed.

    Work & EvidenceWO-7718

    WO-7718

    Inspect generator start circuit

    Ridgeview RDG-0417

    HighSubmitted

    Submitted form

    5 of 5 required
    • Start circuit inspected

      Yes

      Approved
    • Fault found

      Start relay contact worn

      Approved
    • Action taken

      Relay replaced

      Approved
    • Start test result

      Started on first attempt

      Awaiting review

    Attachments (4)

    • Start-relay-before.jpg
    • Start-relay-after.jpg
    • Generator-running.jpg
    • Start-test.pdf

    Review actions

    Pending review - level 1

    Review comments (required)

    Relay replaced and start test recorded on site. Photographs match the checklist.

    RejectApprove

Feed repeat faults into the capex plan

Repeat incidents, asset condition and site constraints sit beside each option, and the approved decision keeps that data through delivery.

Investment Planning

Carried into delivery

Replace aging equipment

Ridgeview RDG-0417

Approved
  • Decision

    Power resilience

  • Reason

    Service at risk from repeated grid loss

  • Assumptions

    3 listed with the plan

  • Asset record

    Linked to the equipment concerned

Accounting stays with your ERP.

Customer story

A mobile network operator in New Zealand

How a mobile operator put its 5G investment where customers feel it

A mobile operator combined customer data with network data to rank 1,200 sites for new builds and 5G. The AI model behind the ranking is 90% accurate, and the plan takes 60% less time to produce.

Read the story
90%
Accuracy of the AI model behind the investment ranking
1,200
Sites ranked for deployment
60%
Less time to produce the plan

Works from the systems your network already runs on

Integration scope is defined for each deployment, and each source is validated with your team before it is named as supported.

  • Alarm and fault systems
  • Site controllers and telemetry
  • Site and asset records
  • Work orders and tickets

FAQ

Questions we get asked

Does MLNetworks replace our OSS or ticketing systems?

No. It reads from the systems you already run and shows their alarms, site records and work orders on one record.

Does it cover radio and traffic performance?

The views shown on this site cover site incidents, energy, assets, field work and site capacity. Radio and traffic performance data depends on what is connected in your deployment, so we scope it with you.

Does the platform act on the network by itself?

No. It prepares the finding and proposes the action. A person approves or rejects it, and the reason is recorded.

Where do we start?

Most deployments start with one workflow, such as site power incidents, and widen from there. Scope and timing are agreed for each deployment.

Mobile Network Operators

Which incident or upgrade do you want to look at first?

Bring a real case. An MLNetworks expert will walk through it with you.

Talk to an Expert