Network planning, technology strategy and finance teams

Rank the next sites by the customers and revenue behind each gap

A capital round has fewer sites in it than the network needs. The candidates are ranked by technical severity, and nobody can say afterwards what the money did.

Request a working session The product that runs it: Network Investment & Intelligence

No demonstration is configured for this journey yet.

Seen by the customer · Planning workbench, English

From the record, not a run: what would reach them, on Planning workbench, in English.

The case

Annotated from the record

What happened

A capital round has fewer sites in it than the network needs, and the candidates are ranked by technical severity alone.

A capital round has fewer sites in it than the network needs. The candidates are ranked by technical severity, and nobody can say afterwards what the money did.

What it reads

Telemetry and topology for each candidate
The demand forecast and cell-level revenue attribution
Cost per site and finance's approval position
Maintenance freezes and change policy

Checks before anything is sent

Telemetry quality, topology match, finance approval, maintenance freeze and change policy checks pass.

Every option considered, including doing nothing

The sites ranked by customers, revenue and cost togetherConsidered
A capacity change on an existing site instead of a new oneConsidered
Rehoming traffic while the site waitsConsidered
No investment, where the forecast does not justify itConsidered

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.

Evidence record

Preview

Reference: Issued when a run is saved. An evaluation that was never saved has none.
Decision: One of the options, including no action, with the reason.
Checks: Telemetry quality, topology match, finance approval, maintenance freeze and change policy checks pass.
Evidence kept: Telemetry snapshot
topology version
demand forecast
cell-level revenue attribution
recommendation
approval
change ticket
before/after KPIs
The measures: Traffic, revenue and experience at the built sites against the forecast that justified them.
Connection: Stated on every record. In the demonstration no operator system is connected, and each record carries that state.

The shape of the record, with no values. A reference appears only after a run is saved.

The improvement, and how it is measured

Hypothesis

A site chosen by the customers behind it can be shown to have paid; a site chosen by the loudest alarm cannot.

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

Assumptions, costs and the record’s five answers

01
Desired result
The result wanted.
Improved service and reliability; lower cost/energy; better CAPEX prioritisation; reduced MTTR
02
Mechanism
The mechanism that could produce it.
Collect → validate topology → detect/forecast → quantify impact → recommend → human/controller approve → execute → verify service/economic result → learn
03
Evidence required
The records kept to show it.
Telemetry snapshot; topology/version; recommendation; approval/change ticket; controller response; before/after KPI; finance validation
04
Costs and risks
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
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: Traffic, revenue and experience at the built sites against the forecast that justified them.
Running cost: Implementation + annual licence by network scale/use case; optional managed analytics; verified savings only with agreed finance baseline
What evidence supports it: Telemetry snapshot, topology version, demand forecast, cell-level revenue attribution, recommendation, approval, change ticket and before/after KPIs.

The journey in detail

Step by step, from both sides

Step	What the customer experiences	What the operator does
The momentThe moment that started it.	A capital round has fewer sites in it than the network needs, and the candidates are ranked by technical severity alone.	Reads telemetry and topology for each candidate, the demand forecast and cell-level revenue attribution, cost per site and finance's approval position, maintenance freezes and change policy.
The decisionThe decision to be made.	Nothing reaches the customer yet.	Ranks candidate sites by the customers, revenue and cost behind each gap, with the demand forecast, and recommends the order.
The safeguardsThe conditions that stop it.	Still nothing. No action is sent until every check has passed.	Telemetry quality, topology match, finance approval, maintenance freeze and change policy checks pass.
The actionThe action that reaches the customer.	Hand the ranked recommendation to the change authority with its evidence; build only what the authority approves. Reaches them on Planning workbench, in English.	Recommends. The system that holds the right confirms, charges or provisions.
When it goes wrongRefusal, failure and recovery.	The demand forecast is built on a quarter with a festival in it, and the top-ranked site is empty by the time it is built.	The before-and-after KPI shows the miss, the forecast's window is corrected with the evidence, and the finance validation records the site's actual benefit rather than the forecast's.
The resultThe change it made.	What changed for them is what is counted; nothing else is claimed.	Traffic, revenue and experience at the built sites against the forecast that justified them.
The proofThe proof anyone can check.	Can be answered for, later, from the record.	Telemetry snapshot, topology version, demand forecast, cell-level revenue attribution, recommendation, approval, change ticket and before/after KPIs.

Operator systems remain authoritative. HeuriTel reads these to propose an action; it does not decide on their behalf.

Refusal, failure and recovery

What goes wrong

The demand forecast is built on a quarter with a festival in it, and the top-ranked site is empty by the time it is built.

What happens then

The before-and-after KPI shows the miss, the forecast's window is corrected with the evidence, and the finance validation records the site's actual benefit rather than the forecast's.

The products in this journey

Runs the decision
Network Investment & Intelligence
Network, customer and economic data rank sites, capacity and coverage gaps together, the operator's change authority approves the investment, and the result is verified against the forecast.
Contributes
Network Operations & Autonomous Networks
the same telemetry, read for faults rather than for capital
Contributes
Field & Workforce Operations
who goes to the site the plan chose
The definition it demonstratesHeuriTel Site Prioritisation
Results it movesTurn network capabilities into enterprise services · Reduce avoidable service cost

Available to see today

No demonstration is configured for this journey yet.

Request a working session Request a working session