Organisations
Outage command platform for an operating company
One picture of the night for control, field, and communications
Situation
When the network or the service degrades after dark, operations, field crews, and communications each hold a different truth. Restoration is slower than the physics require because the picture is late and disputed.
Approach
How we would run it.
01
A command object model: incident, asset, crew, customer impact — agreed before interface design.
02
Boundaries respected. The platform consumes signals; it does not become a back door into control systems.
03
Workflow for dispatch, restoration, and after-action, with a trail leadership can inspect.
04
A communications view that is a projection of the same object, not a separate spreadsheet.
Target outcomes
Targets for a programme of this class — not claimed results from a named client.
- 1
- Shared incident object across functions
- Faster
- Time-to-picture after a night event
- Clean
- Inventoried access at every boundary
Practices involved
More programmes
Next step
Bring us the hard programme.
If the work needs architecture, security, and a team that will still be there at go-live, we should talk. Discovery conversations are with a senior architect — not a queue.