Concept Design
Turning a wholesale outage notice into accurate retail updates
A wholesaler reports affected network infrastructure; the retailer contacts customers by service and address. The footprint changes as repairs progress. Mapping the incident to a postcode can notify unaffected customers and miss others on the same infrastructure.
System landscape
Source evidence comes from network incident and service inventory. The proposed workflow sends the decision to incident controller.
Proposed architecture
Connect wholesale incident identifiers, retail service inventory, access-service relationships and approved message versions. Recompute the affected population when scope changes and distinguish service restoration from closure of the wholesale ticket.
- Source recordsNetwork incident and service inventory
- ProcessingResolve affected retail services
- Decision ownerIncident controller
- Operational outputVersioned customer update
Reliability and operating controls
The incident controller approves customer statements and channel choice. Track delivery failures, customers without a usable primary channel and services still failing after upstream restoration.
Illustrative operating scenario
A supplier narrows an outage to one access node. The retail dashboard shows which services should receive a revised update and which still need an individual fault investigation.
Delivery boundaries
The provider and wholesale partner own network actions, communications and regulated customer decisions. The integration tracks what was accepted and carried out.
Expected business impact
Reduce missed notifications and inaccurate status for affected retail services.
Acceptance test and handover
Simulate an expanding outage, partial restoration and a failed SMS channel. Verify how quickly the team identifies affected services and whether updates match the evidence available at issue time.
Industry evidence
ACMA describes communication obligations for significant and major outages. ACMA outage communication rules