Network operations and assurance teams
Forty alarms fire in ten minutes across three regions. The queue is ordered by arrival time, and the cell serving a hospital is fourth.
No demonstration is configured for this journey yet.
Seen by the customer · Operations console, English
From the record, not a run: what would reach them, on Operations console, SMS, in English, Kiswahili.
What happened
Forty alarms fire in ten minutes across three regions and the queue is ordered by the time each arrived.
Forty alarms fire in ten minutes across three regions. The queue is ordered by arrival time, and the cell serving a hospital is fourth.
What it reads
Checks before anything is sent
Telemetry quality, topology match, maintenance freeze, safety policy and vendor controller checks pass.
Every option considered, including doing nothing
No action is a valid outcome, and it is recorded with its reason. Nothing is computed on this page: the options are the record's own, and no run has decided anything.
The shape of the record, with no values. A reference appears only after a run is saved.
Hypothesis
An incident worked in order of the customers it hurts restores the most service per hour; one worked in order of arrival restores the oldest alarm.
Desired result: Improved service and reliability; lower cost/energy; better CAPEX prioritisation; reduced MTTR
Modelled not observed
No figure is modelled for this journey. The mechanism that could produce the result is stated instead.
Collect → validate topology → detect/forecast → quantify impact → recommend → human/controller approve → execute → verify service/economic result → learn
Observed
Nothing yet. Measurement begins in a pilot’s validate stage, on your systems, against a comparison agreed first.
Matched site/cell comparison, stepped-wedge rollout or before/after with seasonality controls; technical and economic acceptance criteria
Measured on: Service experience; utilisation; incidents; MTTR; repeat fault; avoided congestion; cost; energy; affected customers; incremental/retained value
The result wanted.
Improved service and reliability; lower cost/energy; better CAPEX prioritisation; reduced MTTR
The mechanism that could produce it.
Collect → validate topology → detect/forecast → quantify impact → recommend → human/controller approve → execute → verify service/economic result → learn
The records kept to show it.
Telemetry snapshot; topology/version; recommendation; approval/change ticket; controller response; before/after KPI; finance validation
The cost, and the ways it can go wrong.
Costs: Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline
If it fails: Default to observe/recommend; never make unapproved network change; open incident; preserve last-known-good config and audit trail
The measure that shows it helped.
Matched site/cell comparison, stepped-wedge rollout or before/after with seasonality controls; technical and economic acceptance criteria
Measured on: Service experience; utilisation; incidents; MTTR; repeat fault; avoided congestion; cost; energy; affected customers; incremental/retained value
Nothing has been observed for this product. Every line above is the record's own design intent; measurement begins in a pilot's validate stage, on your systems, with the comparison agreed first.
The business side
| Step | What the customer experiences | What the operator does |
|---|---|---|
| The momentThe moment that started it. | Forty alarms fire in ten minutes across three regions and the queue is ordered by the time each arrived. | Reads the alarm set and its correlation, topology and the customers behind each cell, maintenance freezes and the safety policy, the vendor controller's response. |
| The decisionThe decision to be made. | Nothing reaches the customer yet. | Correlates the alarms into incidents, ranks them by the customers and revenue behind each, and recommends the remedy the change policy allows. |
| The safeguardsThe conditions that stop it. | Still nothing. No action is sent until every check has passed. | Telemetry quality, topology match, maintenance freeze, safety policy and vendor controller checks pass. |
| The actionThe action that reaches the customer. | Dispatch, tune or rehome through the controller on approval, and tell the affected customers what is being done. Reaches them on Operations console, SMS, in English, Kiswahili. | Recommends. The system that holds the right confirms, charges or provisions. |
| When it goes wrongRefusal, failure and recovery. | The recommended rehome moves traffic onto a cell already at capacity, and the remedy causes a second incident. | The capacity check refuses the rehome, the recommendation falls back to a dispatch, and the before-and-after KPI for the first remedy is kept so the rule is corrected. |
| The resultThe change it made. | What changed for them is what is counted; nothing else is claimed. | Time to restore for the incidents that touched the most customers, and repeat incidents on the same cells. |
| The proofThe proof anyone can check. | Can be answered for, later, from the record. | Alarm set, correlation, customer impact, recommendation, approval or change ticket, controller response and before/after KPIs. |
Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.
What goes wrong
The recommended rehome moves traffic onto a cell already at capacity, and the remedy causes a second incident.
What happens then
The capacity check refuses the rehome, the recommendation falls back to a dispatch, and the before-and-after KPI for the first remedy is kept so the rule is corrected.
Anomalies, correlated alarms and predicted faults are ranked by the customers and revenue behind them, and each remedy goes to the controller as a recommendation with its evidence.
the same telemetry, read for capital rather than for faults
where a customer affected by a fault is told what is being done
No demonstration is configured for this journey yet.