Track Inspection Compliance demo
For track owners: every inspection, rail test, slow order and gap pinned by milepost, and the file read first as an FRA inspector would. 1:26
What the demo shows
A track inspection compliance system: inspections, rail tests and slow orders read by milepost
Agents read the subdivision’s inspection records, rail tests, track bulletins and work orders together, check every inspection interval in calendar days, and trace each defect to its slow order and repair record. A challenger reads the file as an FRA track inspector would and finds what the records hide, such as a slow order lifted on a work order never started, or a make-up inspection that broke the required interval. Agents never set or lift a slow order: the roadmaster does, on the dispatcher’s bulletin, with a what-if on the repair options, and the rail-testing contractor answers in fixed fields. The chief engineer opens the repair record and co-signs each closure, and railroad counsel decides any statement to FRA.
Transcript
- Track Inspection Compliance checks a roadmaster's track records against federal rules.
- Seven agents read nineteen records; mid-run, Dale adds a weather inspection.
- A challenger reads it all as FRA would: a slow order lifted with no repair.
- It shades miles fifty to sixty-one point eight: one day between inspections; the rule needs three.
- Agents never set slow orders; Dale restores ten miles an hour at seven twelve.
- A what-if prices tonight's rail swap against joint bars Thursday; Dale picks tonight.
- The contractor answers in fixed fields: a retest booked for the thirteenth.
- Next morning the gang's repair record arrives; Dale opens it and signs the closure.
- The chief engineer opens the chart and record, then co-signs; no defect closes on one name.
- Seven points in one morning, and the defect closed by the next morning.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.