Find the fault before the customer does, and fix it through the change process the network already trusts.
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.
For Network operations and assurance teams responsible for incidents, changes and the experience customers get.
Forty alarms fire in ten minutes across three regions and the queue is ordered by the time each arrived.
The incident worked first, the remedy recommended, and the person who approves it.
The incident with the most customers and revenue behind it, firstConsidered
A tune or a traffic rehome the controller can apply on approvalConsidered
A dispatch, where the fault needs a visitConsidered
No action, where the alarm is a known conditionConsidered
Before anything reaches the customer: Telemetry quality, topology match, maintenance freeze, safety policy and vendor controller checks pass.
What would reach them: Dispatch, tune or rehome through the controller on approval, and tell the affected customers what is being done. On Operations console, SMS.
The incident worked first, the remedy recommended, and the person who approves it.
Forty alarms fire in ten minutes across three regions. The queue is ordered by arrival time, and the cell serving a hospital is fourth.
The incident with the most customers and revenue behind it, first
A tune or a traffic rehome the controller can apply on approval
A dispatch, where the fault needs a visit
No action, where the alarm is a known condition
What it does
Three things it helps you decide or do.
Correlate alarms and predict faults with the customer impact attached
Anomaly detection, alarm correlation, fault prediction and root-cause analysis read telemetry with topology and the customer experience behind each cell, so an incident is prioritised by whom it affects.
site_or_cell_id
timestamp
traffic
throughput
latency
loss
utilisation
alarms
coverage
affected_customers
revenue_aggregate
capex_or_opex
action_outcome
Recommend the remedy the change policy allows
Tune, rehome traffic, dispatch, schedule a change or escalate; low telemetry quality, a maintenance freeze or a rejection by the vendor controller holds the recommendation.
Observe
tune
dispatch
add capacity
rehome traffic
schedule change
communicate
reject investment
escalate
Keep the before-and-after evidence for every change
The telemetry snapshot, the approval or change ticket, the controller's response and the KPI before and after are kept together, so a self-healing recommendation earns its closed loop on record.
Telemetry snapshot
topology/version
recommendation
approval/change ticket
controller response
before/after KPI
finance validation
The journey
Fix the incident that hurts the most customers, through the change process
No demonstration is configured for this product yet.
Network operations and assurance teams
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.
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.
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
05
Measurement approach
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
The change
Time to restore for the incidents that touched the most customers, and repeat incidents on the same cells.
Running cost
Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline
What evidence supports it
Alarm set, correlation, customer impact, recommendation, approval or change ticket, controller response and before/after KPIs.
Technical detail
Inputs, decision logic, systems touched, records kept.
Four questions an evaluation asks in a different order every time. Every field is the workbook’s own, unedited.
What would we need from your systems, and how much history?
Attributes required
site_or_cell_id
timestamp
traffic
throughput
latency
loss
utilisation
alarms
coverage
affected_customers
revenue_aggregate
capex_or_opex
action_outcome
Also useful, not required
Competitor/drive-test data
weather
events
crowds
complaints
device mix
spectrum
energy
partner demand
8-12 weeks telemetry and topology; stable site/cell mapping; incident/action history; cost/action catalogue; aggregated customer value where used
How is the action chosen, and what stops it?
Actions it may choose between
Observe
tune
dispatch
add capacity
rehome traffic
schedule change
communicate
reject investment
escalate
Conditions that stop execution
Low telemetry quality
topology mismatch
maintenance freeze
safety/change policy
capacity unavailable
finance approval
vendor controller rejects action
Default to observe/recommend; never make unapproved network change; open incident; preserve last-known-good config and audit trail
What does it connect to, and what stays authoritative?
Use network, customer and economic data to support network anomaly detection, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network alarm correlation, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network fault prediction, with operator-approved actions, change controls and post-action verification.
/d/HT-0366
HeuriTel Network Root Cause AnalysisDecision definitionHT-0367
Use network, customer and economic data to support network root cause analysis, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network incident prioritisation, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network self-healing recommendation, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network configuration audit, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network performance prediction, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network experience prediction, with operator-approved actions, change controls and post-action verification.
/d/HT-0373
HeuriTel Network Service AssuranceDecision definitionHT-0374
Use network, customer and economic data to support network service assurance, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support network slice assurance, with operator-approved actions, change controls and post-action verification.
Identify eligible records for load balancing recommendation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0378
HeuriTel Energy OptimisationDecision definitionHT-0379
Use network, customer and economic data to support energy optimisation, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support cell outage detection, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support fibre fault prediction, with operator-approved actions, change controls and post-action verification.
/d/HT-0381
HeuriTel Field Dispatch RecommendationDecision definitionHT-0382
Identify eligible records for field dispatch recommendation, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
/d/HT-0382
HeuriTel Mean Time to Repair ReductionDecision definitionHT-0383
Identify eligible records for mean time to repair reduction, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Use network, customer and economic data to support nwdaf analytics enablement, with operator-approved actions, change controls and post-action verification.
Use network, customer and economic data to support autonomous network level assessment, with operator-approved actions, change controls and post-action verification.
Identify eligible records for closed-loop automation guardrails, choose from approved actions including no action, execute through the system of record, and measure the agreed business outcome.
Use network, customer and economic data to support network operations copilot, with operator-approved actions, change controls and post-action verification.
Four stages, and what has to be true before the next one starts.
12-16 weeks for decision support; closed-loop automation requires additional change, safety and vendor certification. A team of 8 roles, named in the record rather than promised.
01
Scope
One use case, one value unit and a denominator finance has agreed to. Without these there is nothing a later result can be compared against.
Select scenario
define action authority
baseline
02
Connect
The attributes mapped from your systems, and the decision and outcome interfaces working in both directions.
map topology/telemetry
integrate tickets
03
Validate
Eligibility agreed, a dry run with nothing sent, then a controlled pilot with a holdout that is actually respected.
build detection/ranking
shadow
operator-approved pilot
04
Operate
The live loop: decide, check, execute through your systems, capture what came back, and measure against the control.
Collect
validate topology
detect/forecast
quantify impact
recommend
human/controller approve
execute
verify service/economic result
learn
Who does it. 1 network solution lead · 1 network SME · 1 data engineer · 1 ML engineer · 1 OSS integration developer · 0.5 QA · 0.5 DevSecOps · 1 coordinator
Four states are tracked, and each is assessed against your systems.
Readiness is assessed per client: nothing is offered as pilot-ready until your data, your integration and your authority have been checked.
Readiness
Needs client data and integration review
The client’s data and integration position.Runtime / build state
Target product definition
What exists as running software.Surface state
Not audited
Whether this product shows the entry anywhere.Client status
Not assessed
Where a named client has reached.
Next steps from here.
24 definitions sit under Network Operations & Autonomous Networks. The two links that matter first are the journey this page describes, and the rest of the family it belongs to.
What can the network itself do for a bank, an agency or a planner?
CAMARA & GSMA Open Gateway APIsLet a bank or an app verify a number, a SIM change or a location from the network itself, with the customer's consent recorded.
Network Investment & IntelligencePut the next site, upgrade or fibre route where the customers and the revenue are, and show afterwards what the money did.
Government & Public SectorGive a public service the aggregate picture and the citizen contact it needs, without exposing a single subscriber's data.
Jobs & Social ImpactRun a jobs programme that can say who it reached, who was placed and who stayed employed.
Fraud, Identity & Customer ProtectionStop the SIM swap, the takeover and the subscription fraud before the money moves, and let the fraud system make the call.
