In development
Rail performance insight
SectionIQ
See the section. Understand the performance.
SectionIQ is being designed to turn an ordinary operational journey into useful performance data without
demanding constant interaction from the person carrying the device.
An authorised tester or operational user starts a recording session, puts the phone away and carries on
with the job. SectionIQ can then map the journey and derive station dwell, sectional running time, average
speed and other timing information for later review.
Simple capture
Start once. Let it run.
Recording is deliberately user-controlled. Start the session before the journey, allow SectionIQ to work
in the background, then stop it when the run is complete. The aim is useful data without creating another
operational distraction.
What it can measure
Journey data that actually means something.
The planned analysis includes station arrival and departure timing, dwell time, sectional journey time,
average speed, route mapping and comparison of observed running against published timetable information.
Bigger picture
Spot patterns across multiple runs.
SectionIQ is intended to support a central review view where authorised teams can combine journey data,
identify recurring delay points and distinguish isolated events from repeat operational patterns.
Built for context
Performance data, not a blame button.
Railway performance is affected by infrastructure, signalling, passenger demand, regulation, rolling stock,
weather and many other factors. SectionIQ is designed to add evidence and context to operational analysis —
not to make automated employment decisions about individual people.
Location and privacy
Tracking should be obvious and controlled.
SectionIQ is intended to collect location data only during an active recording session. It is not designed
for continuous off-duty location monitoring. Details of the intended data handling are set out in the
SectionIQ Privacy Policy.
Current release status
Prototype and development stage.
SectionIQ is currently being developed and tested. Features, data fields and deployment arrangements may
change before any production release, and the privacy documentation will be updated to match the final build.