It’s a universal system that pretty much every TOC uses because of how it feeds JourneyCheck and the CIS through Darwin. It isn’t perfect, however I find it quick and easy to use even though it doesn’t read back so well at times. But they are the tools that we are all given. I’ve worked with it for almost 10 years and the interface and what you can do has never really changed that much.
I'm not blaming those who input the data, and it's great that it's easy to use for those entering the information.
But, from my point of view as someone
using the information, it just doesn't work.
It's not a question of not reading back well. At least in the case of TfW, the information is often incomplete, misleading and just downright nonsense.
As an example, if a line is blocked then there aren't going to be trains until it opens, so don't tell me there
may be cancellations or delays.
Unfortunately, again because of the algorithm, one or two cancellations will show “good service” if you think about it one or two cancellations on a line that has a very frequent service is “good” where as if it was an hourly or two hourly that threshold is different. Once CSL2 is activated all lines should show “Red” and “Major Disruption”
Believe me, it will show "good service" when there is far more than the odd train cancelled. Services through Queen Street can have fallen apart completely yet the screen is still happily showing "Good service" on all routes.
Although in any case I would assume "Good service" meant the full timetable running with minor delays at most.
As I said above it's easy to just sit on the sidelines carping. But over and over and over again TfW fail to give accurate and useful information when there's disruption and I do find it hard to believe that they couldn't do better.
On another note, Journeycheck seems to be suggesting a half hourly service tomorrow from Queen Street to Coryton but not Caerphilly. But nothing going the other way!
