Railways & Metro

Every train, track section and failure connected, so trains run on time.

Rolling stock, track, signalling and passenger data are run by separate departments on legacy systems.

The question it answers

“Which assets fail repeatedly and cause delays on this route?”

What changes: Higher punctuality, fewer in-service failures.

All seven layers

How ForgeOrbis works for railways and metro.

  1. 01

    Connect

    Ingest

    Data sources

    • Maintenance systems
    • Train operations
    • Signalling logs (read-only)
    • Ticketing
    • Asset inventory
    • Inspection apps
  2. 02

    Understand

    Extract

    Facts from unstructured data

    • Inspection reports
    • Failure reports
    • Passenger complaints
  3. 03

    Unify

    Resolve

    What must be matched

    • Coaches/locomotives across depots
    • Track sections
    • Vendors
  4. 04

    Relate

    Model

    Objects and links (the ontology)

    • Train
    • Coach
    • Locomotive
    • Track Section
    • Station
    • Signal
    • Failure
    • Work Order
  5. 05

    Decide

    Ask

    Example question

    “Which assets fail repeatedly and cause delays on this route?”

  6. 06

    Execute

    Act

    Approved actions

    • Schedule maintenance
    • Re-plan rakes
    • Alert control room
    With approval; never writes to signalling
  7. 07

    Trust

    Govern

    Trust and compliance

    • Safety-critical boundary
    • Government data rules
    • Audit

What a pilot measures

Each pilot measures 2 to 3 KPIs you already track, before and after. We publish no benefit numbers until a customer has measured them.

  • Punctuality %
  • Failures per million km
  • Maintenance backlog
  • Asset availability

Who it is for

  • Zonal/divisional operations head
  • Metro COO

Where it stands today

What runs today, and what we are still building.

We would rather tell you up front than discover it in week three. A pilot starts with what runs today.

The platform

  • 01ConnectIngestPartly live
  • 02UnderstandExtractPartly live
  • 03UnifyResolveRoadmap
  • 04RelateModelPartly live
  • 05DecideAskLive
  • 06ExecuteActLive
  • 07TrustGovernPartly live

Still to build for railways and metro

  • Enterprise connectorsLayer 1ERP, databases, ticketing, CRM, TMS/WMS, PLM connectors
  • OT/SCADA connectorsLayer 1Read-only connectors to SCADA, DCS historians, PLCs (OPC-UA, Modbus)
  • Time-series/telemetryLayer 1High-volume sensor and machine data, windowing, anomaly baselines
  • Geospatial/mapLayer 4Map-native objects, routes, areas, proximity questions

Live means shipping in the product today. Partly live means part of the layer ships today and the rest is being built. Roadmap means being built and not available yet. We never show it as available.

Book a pilot

One site, one problem, measured in weeks.

Each pilot measures 2 to 3 KPIs you already track, before and after. We publish no benefit numbers until a customer has measured them.