Daniel Tall, Head of Network Rail / Southeastern Joint Performance Team, presented on our performance improvement work at our most recent Tracsis DayOne user event. If you couldn’t make it, here’s an overview of their challenges, objectives and improvements:
Early Stages 2015-17
Southeastern had specific challenges during the Thameslink rebuild:
- Our unsupported Driver App had broken
- Our Unsupported Station reporting App was failing
- Small Delays were rising
- Performance to the passenger was poor and using TRUST data only gave us detail up to a minute
- We were interested in to the second data so that we could address issues to the second
- We were failing to hit Franchise targets and were being suitably penalised by the DfT
Southeastern first introduced the DayOne Hub into Station teams in 2016/7. As a result:
- Allowed removal of the old App
- Stations given accurate information about train operations
- Allowed more accurate tracking of where trains were losing time – especially in the 0-8m
- Gave Performance Analysts opportunity to study issues with far more granularity of information
- We could monitor the reliability and effectiveness of the timetable
How do we use DayOne?
In January 2018 we discovered, to our horror, that TLP signalling system changes were finalised late and the timetable was therefore out of sync. Passengers experienced an entire evening of red signal creep as new method of operation came into being. The 0-8m is our most critical area of operation – delays multiply quickly and passenger feedback is understandably negative.
DayOne section analysis
TRUST could not give us the detailed information that we needed but DayOne could and stations were accurately reporting why trains were delayed, fed straight into bugle to improve attribution accuracy. We were able to establish, using DayOne what was happening where and take appropriate steps to fix quickly.
DayOne timetable analysis
DayOne – Driving Timetable Change
Driver Reporting App
Key issues in how we were approaching driver reporting delays:
- Old App had failed
- Picking up delays for no cause rose to all time highs
- Paper reporting mechanism unsuitable for future
We had worked with Tracsis over many years, used a number of their products and believed they would be best option to develop.
The Development Team were great – they came, listened to what we were after and challenged our thinking about how the App would work. Worked closely with us to ensure we were happy with each part of the build.
Some of the things we came up against…
- Driver Team were consulted, there was some nervousness about time to use the App and driver take up.
- There were issues about easy identification of drivers to the correct trains.
- There was concern that drivers could be asked to fill in delay reports for both very large delays (already linked into incident where cause would be known) or very small knock on delays outside drivers control (e.g. reactionary delay to a non primary incident).
- Linkage into other systems so that we weren’t chasing drivers twice for the same delay.
- Would drivers use it and would it have the desired effect?
Visits were made to the Driver Managers around the company, providing a 30-minute demonstration with a Q&A which was sufficient to reassure them that the new app was easy to use and wouldn’t prove too time consuming.
- Tracsis developed a way to link the app to Driver diagrams so that they only needed to input their diagram number in order to receive their RFIs for the day.
- A further development gave the app the ability to record time loss between TRUST points.
- Further flexibility was introduced to allow adjustment on the amount of delay that generated an RFI.
Following the six week trial the app went live and we have now reached the point where we have had 90% total usage although depot specifics vary. Whilst we have had some reach 100% usage, there are still a few depots that require further work to improve the number of users at those locations.
Use of the DayOne app has supported the continued reduction of TO coded incidents and minutes.
The continued reduction of TO coded incidents and minutes supported by the reports received through DayOne has helped to drive down the number of incidents and minutes where there has been no Drivers’ report received.
Has it had the desired effect?
At the end of over a year’s work between our two organisations:
- We have reduced Driver No report delay attribution to Southeastern.
- We have a better understanding of the causes of delays from the driver perspective driving other workstreams.
- We have gotten 90% of our drivers to log into the App and to continue to use it.
- We have a reliable tool linked into our systems that reduces duplication and streamlines our processes.
If you’d like to find out more about how DayOne could improve your performance, get it touch today… email@example.com