Rail, on one record.
OpenRail is the rail platform on Mission Systems. Crews, rolling stock and timetables as rail-specific modules, on the same operational model as everything else the operator runs.
What a rail operation runs on, modelled properly.
The same shape as OpenAir for aviation: the sector’s own records and constraints, added to the model the rest of the platform already shares.
Crew diagrams and rosters
Drivers and on-board crew planned against hours, rest and the route and traction knowledge each person holds, with a breach an infeasible answer rather than a warning.
Rolling stock with its maintenance
Units planned together with their exam and maintenance windows, so a unit that is due stops being diagrammed before it becomes a failure in service.
Timetable and disruption
A late unit or a missing driver re-enters the solve while the day is running. The plan re-solves around it and holds every rule it held before.
What it writes to the model, and what Launchpad does with it.
A driver is one record whether the diagram, the competence register or payroll is looking at it. A unit is one record from the maintenance window to the timetable it runs.
- Reads & writes
- crews, rolling stock, diagrams, timetables, depots, maintenance windows
- Launchpad
- Diagrams crew inside hours and knowledge rules. Keeps a unit due for maintenance out of the plan. Re-solves the day around a late unit or a missing driver.
- Autonomy
- Set per capability, from off to unattended, and movable back
- Works with
- Workforce, Operations, Analytics