Corridor
Data notice

TMS, SMMS, TDMS, COA and BDMS are internal Indian Railways systems with no external access. The maintenance backlog shown here is generated, not observed. Corridor geometry and protected paths are measured from published data; the daily shape of detention cost is assumed.

seed 7 · priced by duration, hazard, detentionfull limitations →

17 zones · 68 divisions · 425 posts

Sign in

Accounts here are posts, not people: five to a division — Sr.DEN, Sr.DSTE, Sr.DEE, Sr.DOM and the DRM — and five to a zone. Choose a zone and a division to see the posts that hold an account, then sign in as one.

A demonstration directory, not RailNet. The 17 zones and 68 divisions are the Ministry’s published list; the posts on them are generated, and their passwords are printed on this page. A real deployment would carry no user table at all — every officer already has an HRMS employee ID, and a block plan is an auditable document, so “approved by Sr.DEN” has to resolve to an establishment record rather than a row in our database.

SrDEN/ECoR/WATblock@2026plan solved

Permanent way. Owns the track defect register (TMS).

What your post can see

The credential is checked in the database, and so is everything you read after it. A divisional post sees its own division’s plan; a zonal post sees the plans of its own zone; an officer of any other zone gets nothing at all — not a copy of someone else’s plan relabelled with their division.

That scope is applied inside the query rather than in the browser, so it is not something this page can be edited to opt out of. It is also why most posts here show an empty planner: only one division has been solved, and saying so is the point.