Skip to content
MLNetworks
Talk to an Expert

Network Monitoring & Incident Response

Seven alarms. One incident.

Network Monitoring & Incident Response is the part of MLNetworks that groups related alarms from your sites into one incident, with the site and power data beside them, so the NOC can see the probable cause and decide what to send first.

MLNetworks groups the alarms from one event into a single incident, states the probable cause and what supports it, and prepares the repair for a person to approve.

Talk to an Expert
Incident QueueINC-2041

INC-2041

Site power issue

Ridgeview RDG-0417

HighInvestigating
Started
02:14
Work family
Generator
Site match
Matched - can dispatch
Work order
None yet

Probable cause

Confidence: Medium

Generator did not start during a grid outage

Correlated alarms

  • Mains failurePrimary02:14
  • Generator failed to startInferred02:15
  • Low battery voltageInferred03:02

From first alarm to dispatch

  1. 01

    Related alarms become one incident

    Alarms from the same event at a site are correlated into one incident. A flapping alarm is counted once and does not queue 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 probable root cause

    Each incident gives a probable cause, the chain of faults behind it and a confidence level. Measured readings and inferred ones are marked separately.

    Incident QueueINC-2041

    Probable cause

    Confidence: Medium

    Generator did not start during a grid outage

    Causal chain

    1. 1Grid supply lost
    2. 2Generator did not start
    3. 3Battery carried the load until low voltage

    Evidence

    • Grid lost 7 times in 24 hoursmeasured
    • No generator run recorded on the fifth outagemeasured
    • Battery discharge follows each outageinferred

    What is unproven

    Why the generator did not start. To be checked on site.

  3. 03

    A repair, ready to approve

    The record proposes a repair action. A person approves or rejects it and gives a reason. The decision stays on the incident.

    Incident QueueINC-2041

    INC-2041

    Site power issue

    Ridgeview RDG-0417

    HighInvestigating

    Proposed repair actions

    Inspect generator start circuit

    Work order type: Generator

    Held for a person to dispatch

    Reason *

    No start on the fifth outage. Send the field team with the evidence attached.

    RejectApprove

The systems that raise your alarms

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

Fewer tickets, more on each one

  • Mains failure

    Last 24 hours

    00:0006:0012:0018:0024:00
    7 alarm events1 line on the incident

    Duplicates, flapping and alarm floods

    An alarm that raises and clears seven times is one line on the incident, with its count. The queue lists incidents, not every alarm.

  • Ridgeview RDG-0417

    Tower site, 36 m

    INC-2041
    Power sources
    Grid, generator, battery
    Battery state of charge
    41%
    Generator
    No run in 24 hours
    Open work orders
    None

    Site status beside the alarm

    Power sources, battery SoC and open work orders sit next to the incident. The first questions the NOC asks are already answered.

From incident to site visit

An approved action becomes a work order with the finding attached. The incident stays open against the work until the site is checked again.

Workforce & Scheduling

Work order progress

Inspect generator start circuit

WO-7718 · Ridgeview RDG-0417

Completion evidence

  1. Prepared

    Finding and evidence attached

  2. Dispatched

    Field team assigned

  3. On site

    Start circuit inspected and repaired

  4. Completion evidence

    3 photographs, start test recorded

Mark restored

Built so the NOC can check the call

  • Readings behind every cause

    Each cause lists the readings that support it, and marks which are measured and which are inferred.

  • Says what is not proven

    When the data is thin the record says so and names what to check on site.

  • People keep the decision

    Proposed actions wait for approval. Every approval or rejection has a reason.

FAQ

Questions from operations teams

How are alarms grouped into an incident?

Alarms from the same event at a site are correlated into one incident. The primary alarm is marked and the related ones are listed under it, with repeats counted.

Does the platform act on its own?

It prepares the finding and proposes a repair. A person approves or rejects it, and the reason is recorded on the incident.

What happens when the evidence is thin?

The record says so. The probable cause carries a confidence level, a note of what is unproven and what to check next.

Which alarm sources can it connect to?

That is defined for each deployment. We validate each source with your team before we name it as supported.

Does it replace our monitoring or ticketing systems?

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

Network Monitoring & Incident Response

Which incident would you like walked through?

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

Talk to an Expert

More of the platform

Every part uses the same sites and assets. Start where the need is greatest and add the next when you are ready.