TfGM SNV Single Network View — home

Technical overview

The architecture behind the single view.

Ingestion, canonical model, orchestration and experience. The separation is structural; it is what allows new feeds and workflows without redesign.

  • UK South
  • Queue-based ingest
  • Versioned contracts
Read the capability matrix

Layers

Four layers, one direction of dependency.

The experience layer never reads a provider payload; the orchestrator never knows a source protocol.

  1. Sources
  2. Validate
  3. Normalise
  4. Canonical event
  5. Orchestrate
  6. Experience
  1. Layer 1

    Ingestion

    Pull and push connectors with idempotency (source + source event id), dead-letter handling and quality scoring.

  2. Layer 2

    Canonical data model

    Location, corridor, service, journey, asset, vehicle, condition, event — versioned in ops_schema_versions.

  3. Layer 3

    Operational orchestration

    Detection rules, impact analysis, state machine, playbooks, escalation, alert publishing, metrics.

  4. Layer 4

    Experience

    Operator console, public status page, management information — all reading one cached snapshot.

Hosting and assurance

Designed for a UK public authority.

Residency, resilience and support are part of the design, not an afterthought.

  • UK South

    Data residency

    Production data and backups remain in the UK. Sub-processors are documented and governed under Article 28 terms.

  • CE / CE+

    Certification

    Cyber Essentials today; Cyber Essentials Plus committed before contract commencement.

  • 99.9%

    Availability

    Zone-resilient Azure services, monitored health checks, backup restore tests and SLA reporting.