TfGM SNV Single Network View — home

Incident management

Investigate, allocate, record, escalate, close.

Every action is attributed, timestamped and auditable. Playbooks create the tasks; operators make the decisions.

  • Lifecycle
  • Task routing
  • Escalation
  • Audit
lifecycle states
7
lifecycle states
escalation levels
3
escalation levels
actions audited
100%
actions audited

One incident, end to end

What the console records.

A collision on the Mancunian Way, from the first signal to the review.

  1. 14:28

    Detection fires

    Rule CV-04 sees average speed fall to 9.3 kph. Confidence 87%. Four signals are recorded with the detection.

  2. 14:29

    Operator verifies

    The incident moves to triage. Impact is calculated across two bus routes and the East Didsbury tram line.

  3. 14:31

    Playbook instantiates tasks

    On-road response, signal timing review, public alert and recovery check are created and allocated.

  4. 14:34

    Escalation and comms

    Supervisor escalates to level 2, approves the public alert and notifies the partner agency.

  5. 15:05

    Recovery confirmed

    Speeds return within 10% of baseline. Queue clears. The incident moves to monitoring.

  6. 15:12

    Closed with review

    Closure records the outcome, two lessons and three actions with owners.

Controls

Built for an operational audit.

  • Append-only timeline

    Corrections are new entries, not edits. The record survives a shift handover and a procurement audit.

  • Task routing by role

    Playbook steps carry a role and a due time. Reassigning an incident reassigns the open work.

  • Escalation with evidence

    Level 2 and 3 escalation records who was notified, when, and on which channel.

Next step

Bring a real incident to the demonstration.

We will run it through the same lifecycle and show you the audit trail afterwards.