Today's signal failure position
Window: 06:00 yesterday to 06:00 today (IST). Counts come from the division registers and SMMS; no names or personal details are shown here.
Test room view
Tap a failure: the rectification guide for that gear, the station's mini SIP and RCC and the gear manuals (on Railnet), and Ask SAMARTH with the failure already filled in.
Failure register
| Register id | Failure time | Division | Station | Gear / asset | Failure | Duration | Trains | Status | Entry quality | Comments & checks |
|---|
Failures in the window
SMMS import (any time)
Load SMMS exports at any time, saved with SMMS's own Export button (.xlsx or .csv, up to 20 MB each): F1 Failure List, Failure Register, AS1, AS3, AS5, M2, M3, M6, M8, F2, F15, F17. The type is read from the file's columns. Loading a file again updates only the SMMS facts; what divisions entered is never changed. An SMMS failure is matched by its Failure Entry No. first, then by asset and time; a register-only entry of the same station and gear within 30 minutes is linked to it (one record, the division's details kept). Personal columns (names, phone numbers, remarks) are not stored.
ICMS import (monthly)
Loaded for this month
History import (old registers)
Load the name-free history file (history_import.json.gz) made from the zone and division failure registers (MS Access, 2007 onwards). It is sent in parts; loading it again changes nothing that is unchanged. History rows are read only: only a register note can be added. Fields filled from the code, cause and station lists (not typed by staff) are marked "derived".
Missing data (gaps)
What still needs attention: SMMS failures with an ICMS id but no register details, register-only failures SMMS still does not have, SMMS failures with neither an ICMS id nor a register link, register id serials missing in a day, and likely duplicates (same station within 30 minutes).
Fill blanks from existing data
Goes through every register and SMMS failure and fills only blanks that the data already answers for certain: asset code, make, model, sub-gear, gear type and location from the station's asset register (the gear name matches one item), the section when the station is in one section only, and the component when the cause names exactly one. Never overwrites a value; every fill is a saved version with its reason. Entry quality and "still needed" are worked out again. Check first, then fill.
Audit
Feedback desk
Feedback and questions from staff on failures, the form and the Failure Assistance guide, for your desk (a division test room sees its division; HQ sees every division). Open one to answer it: the answer goes back to the person who sent it, kept with the failure. Set In progress, Answered or Closed. HQ can also apply a data fix (station, equipment, component, cause) into the pickers at once, or reject it with a note.
Comments
The failures of your jurisdiction that have comments, newest first. Tap one to read and answer.
Performance
Failures of your jurisdiction in the period, one level down at a time. Tap a row to go down to the stations and the failures. Figures belong to a section, a division or the zone, never to a person.
What each figure means
Ask the data
Ask in your own words, in English or Hindi. The answer is worked out from the failure records of your jurisdiction, with the figures, what they mean, and a PDF or Excel report.
To enter
What each section has not entered by 12:00 the day after the failure, by section. Tap a failure to open it, or enter it for the section.
Home
Site accounts (SAMARTH login)
Normal way: give access to the person's SAMARTH e-mail. They sign in with the blue Sign in button.
Give register access to a person's existing SAMARTH account (the e-mail they sign in with). They then sign in normally and open this page. Accounts marked "set in code" are changed only in the site's code.
Register user IDs (only when HQ has given one)
Create a user ID for a division or HQ. Its temporary password is shown once here: give it to the person; they must change it at the first sign-in.