RailOps Ouroboros
Operations platform for international and domestic rail. Traction calculations, document generation, project management.
Overview
Ouroboros is the operational nervous system for RailOps — the tool dispatchers, route engineers and document specialists actually live in. It plans trains, calculates traction, generates regulatory paperwork, and ties projects to schedules across multiple national networks.
The brief
International rail is a thicket of incompatible standards: signalling, traction power, paperwork, languages, time zones. Operators stitch this together with tribal knowledge and a Frankenstack of vendor tools. The brief: replace it.
Approach
A modular NestJS backend with domain services for traction physics, route planning, and document generation. A NextJS operations console that gives dispatchers a single pane for projects, runs and paperwork. Carefully scoped permissions because actions in this system have real-world consequences.
What it does
- Traction physics engine for energy and time calculations
- Multi-jurisdiction document generation
- Project & milestone tracking tied to operational runs
- Audit-grade change history on every operational entity
- Role-based access for dispatchers, planners and auditors
Notes
This page is a living writeup. As the project evolves I'll fill in the screenshots and a more detailed account of the trade-offs that shaped it. Reach out if you want a deeper walkthrough of any particular system.