Traveline monitors the timeliness of its data uploads and ways to improve the processing of timetable data.

1. Traveline data quality Simon Day Durham CC/ NETIS data management With thanks to Stuart Reynolds (SE) for data crunching

2. What gets measured? Completeness “ are all the services in the JP system?” - now effectively an obsolete issue Timeliness - 14 days prior to service change - by start of service change

3. What are the targets? Timeliness: By 14 days prior to start By start > 50 days notice 100% 100% 28 - 49 days notice 80% 100% All changes 60% 70%

4. What is the actual performance?(1)

5. What is the actual performance?(2)

6. How do we do even better? Why so many short notice changes? - almost all due to operators & local authorities! Focus on the right priorities? - not all changes are equally significant … Improve “weak link” partners? - problems tend to be from same sources! Faster release of data into live JP?

7. Traveline data quality Simon Day Durham CC/ NETIS data management With thanks to Stuart Reynolds (SE) for data crunching