TfGM SNV Single Network View — home

Single Network View · Day-1 capability

One operational picture for the whole network.

Bus, tram, rail, highways and active travel harmonised into one governed model — with detection, incident workflow, recovery and management information in a single console.

  • 5 modes
  • 8 live feeds
  • Auditable by design
transport modes
5
transport modes
feeds harmonised
8
feeds harmonised
median acknowledge
<2m
median acknowledge
Open the live console See the architecture

Live network

The network, right now

The same snapshot the OCC sees: mode health, open incidents and published public alerts.

0 of 0 feeds live Updated 01:16 · Europe/London

Open incidents

0

0 critical or major

Median acknowledge

—

operator response

Network performance

100%

observed vs baseline

Passengers affected

0

estimated journey impact

  • Bus

    100%

    0 open incidents

  • Tram

    100%

    0 open incidents

  • Rail

    100%

    0 open incidents

  • Highway

    100%

    0 open incidents

  • Active

    100%

    0 open incidents

Full network status

How it works

Four layers, deliberately separated.

Data is harmonised once. Orchestration is configuration, not bespoke code. The experience layer never talks to a provider payload.

  1. GTFS-R
  2. SIRI
  3. DATEX II
  4. UTC
  5. Weather
  6. Crowd
  1. Layer 1

    Ingestion

    Connectors and normalisers validate, de-duplicate and quality-score every source before it reaches the model.

  2. Layer 2

    Canonical data model

    Locations, corridors, services, assets, conditions and events in one versioned, portable schema.

  3. Layer 3

    Operational orchestration

    Detection rules, impact analysis, playbooks, escalation and alert publishing — all runtime configuration.

  4. Layer 4

    Experience

    The OCC console, the public status page and the management-information workspace share one truth.

Capability, labelled honestly

Available today. Configured for you. Roadmap where it belongs.

Evaluators can compare like with like: every claim on this site carries the same four-state label used in the demonstration.

  • DEMO-1 Available today

    Single Network View

    Fused multimodal map, KPI strip, live feed, mode and source health.

    Limitation: Demonstration transport is simulated; operational geometry and logic are real.

    /ops
  • DEMO-2 Available today

    Detection and impact assessment

    Configurable rules, confidence scoring, explainable signals, impact calculation and optional AI explanation.

    Limitation: Estimates use observed speed versus baseline until APC/ticket data is connected.

    /ops/detection
  • DEMO-3 Available today

    Incident management

    Lifecycle, playbook tasks, allocation, timeline, escalation, audit and AI-assisted alert drafts with human approval.

    Limitation: Social/VMS/partner delivery adapters are configuration; web publishing is live.

    /ops/incidents
  • DEMO-4 Available today

    Recovery and operational monitoring

    Restoration against baseline, closure gate, post-incident review.

    Limitation: Closure checklist is configurable per playbook.

    /ops/recovery
  • DEMO-5 Available today

    Historical analysis and operational learning

    Volumes, response times, impact minutes, corridor hotspots, CSV export.

    Limitation: Scheduled report delivery and economic-impact analysis are roadmap.

    /ops/analytics
  • A1-A4 Available today

    Multi-source detection, classification and explainability

    Eight tuneable rules, confidence, signal/threshold evidence, affected services and a “why this fired” panel.

    Limitation: Assets and permits are not yet resolved into impact; estimates use speed vs baseline.

    /ops/detection
  • A6-A7 Available today

    Explainable prioritisation and decision audit

    Severity × impact priority with a visible explanation; append-only audit of decisions, overrides and AI suggestions.

    Limitation: Queue order is severity-first; comparative ranking rationale is per incident.

    /ops/incidents
  • A9 Available today

    Basic mitigation guidance and playbooks

    PB-ROAD, PB-TRANSIT and PB-INFRA steps create routed tasks; AI suggestions are advisory and require operator acceptance.

    Limitation: Advanced optimisation and automatic mitigation remain later-phase.

    /ops/config/playbooks
  • U1-U6,U9 Available today

    Single view, lifecycle and automatic timestamps

    Role-based view, transition-guarded lifecycle, acknowledge/resolve/close timestamps.

    Limitation: Lifecycle states are fixed; U16 configurability is not yet exposed.

    /ops/incidents
  • U17-U18 Available today

    Impacted operators, partners and dynamic impact

    Affected services/locations, operator metadata, impact recalculation.

    Limitation: Partner contact lists are configuration; no automatic impact refresh.

    /ops/incidents
  • R1-R6,R13 Available today

    Operational reporting, outcomes and disrupted journeys

    Incident export, response metrics, audit, multimodal delay aggregation, disrupted-journey estimate.

    Limitation: R3/R4 data-quality warnings and a governed KPI catalogue are partial.

    /ops/analytics
  • R14,R19 Available today

    Shift-period and live/historic dashboard analytics

    7/30/90-day volume, mode, category, severity, response-time and impact views.

    Limitation: Shift boundaries are not modelled; analytics are period-based.

    /ops/analytics
  • DP1-DP6 Available today

    Modular delivery and product principles

    Separate data, orchestration and experience layers; configuration-driven rules and playbooks.

    Limitation: Roadmap modules are separable but not all are implemented.

    /platform/architecture

Next step

Bring one operational picture into your control room.

We will walk your OCC, highways and UTC teams through the same incident, end to end, in one session.

Request a demonstration Read the capability matrix