Nirnaya-Sārathi
Operational intelligence for railway controllers
A single command surface for divisional railway operations — bringing live operations, safety, crew and fleet together in one view, so the right call is made before the train moves.
Divisional control runs on fragmented channels
Controllers coordinate across phone, radio, paper and chat — making hundreds of safety-critical calls a day, with the full picture only reconciled after the fact. Nirnaya-Sārathi brings it onto one live surface, while there's still time to act.
One clear picture, one confident decision
See the whole division at once
Live operations, safety, crew and fleet in a single view — so controllers manage from the real picture instead of piecing it together from scattered sources.
Act before, not after
Safety and operating issues surface in time to do something about them — not in a review long after the moment to act has passed.
Decide with confidence
The information behind each call is reconciled in one place, so decisions rest on the full operating picture rather than instinct and memory.
From reactive coordination to a proactive operating picture
Ready to bring Nirnaya-Sārathi to your division?
We work with divisional offices, zonal HQs and Railway Board programmes. Book a discovery call to walk through the platform and scope a deployment.
Common questions
- Does Nirnaya-Sārathi replace the Control Office Application?
- No. It reads from the COA rather than replacing it, auto-ingesting on a three-minute cycle and combining that feed with crew, safety and fleet information the controller would otherwise have to gather from separate places. The existing systems of record stay where they are.
- Does it need internet connectivity?
- No. It runs entirely on the railway intranet. This is a deployment requirement rather than a preference — divisional control rooms are not internet-connected environments, and a system that assumes otherwise cannot be installed in one.
- What does the crew Sign-On / Sign-Off lifecycle cover?
- It tracks crew from booking through sign-on, trip and sign-off as a single continuous record, so a controller can see current crew availability and hours rather than reconstructing them from lobby registers after the fact.
- What is banking locomotive prediction for?
- On graded sections, banking locomotives have to be positioned before a train needs them. The system predicts requirement ahead of time from the live movement picture, so the decision is made with notice instead of reactively.
- How long does a divisional deployment take?
- Typically 6 to 8 weeks to a live pilot, because the product is configured to the division rather than built for it. Data access approvals and intranet connectivity are usually the critical path, not the software.
- Is it customised for each division?
- It is configured, not custom-built. Sections, crew rules and thresholds differ by division and are set up per deployment, but the product itself is the same one that improves with every division it runs in.