PHILIPE
Veteran Member
I've noticed on ATW Twitter that when answering a query, people are referred to links, Journey Check etc. when the answer can be a straightforward "Yes" or "No"
As someone that does both for my employer, there's a big difference in putting together a 2000-character line problem message in Tyrell for guards and customers and my colleague behind me putting together a 140-character message for twitter - one takes a lot longer and requires a lot more thought! Aim is for initial line problem message to be issued within 10 minutes, and twitter takes a fraction of that time.
Worth remembering that everything twitter does is quotable and everyone expects a compromise on quality because :twitter: but a line problem needs to be written like a press release - you can and do get quoted in full by local press, and the line problem go out to traffic agencies so they need to be understandable by laymen.
Last thing intended is to keep crews out of the loop, and I take pride in making sure that crews on my TOC are kept regularly informed during disruption - y'all'd still be on pagers if not 2B46 LT SOU WT CRW EXP 20M.
But all the Guard/ Driver might need is " Broken down train ahead"
2B46 at a stand Clapham Junction plat 7 with door fault. Driver is PAF. UMFL blocked. 1A48, 2L48, 1P46 first affected and trapped behind. Services may be switched to UMSL at Wimbledon. Further information to follow.
Unfortunately they were withdrawn in favour of an automated system that couldn't anticipate platform alterations and CIS Control looking after over 5 large stations and lots of small ones. It felt like hurting into a rush hour crash barrier - you knew the platform alteration was coming but had no time to get back to it and no explanation.
How wonderful centralised CIS and subsequently Darwin is, not.
The message is sent to all guards due to the size of the company and limitations of the system used - I endeavour to send an internal message first with a brief description, but even that needs to be a lot more specific than "broken train ahead" - it needs headcode, location, line blocked, expected impact, and ideally next few services affected. As an example:
2B46 at a stand Clapham Junction plat 7 with door fault. Driver is PAF. UMFL blocked. 1A48, 2L48, 1P46 first affected and trapped behind. Services may be switched to UMSL at Wimbledon. Further information to follow.
Whilst that doesn't take that long to run out (maybe a minute), your average information controller has a heck of a lot to do additionally to that, with service alterations, listening out to the status from fleet, ensuring that their team managing CIS and announcements are all informed as well - it's an additional task there may not be time for, and you could as well be better off just getting the public one together.
What does PAF mean?
We used to love having a station announcer who could react to such messages locally, amend platforms and provide info to both passengers and staff locally, alongside useful jobs like phone through and coordinate passenger assistance.
Unfortunately they were withdrawn in favour of an automated system that couldn't anticipate platform alterations and CIS Control looking after over 5 large stations and lots of small ones. It felt like hurting into a rush hour crash barrier - you knew the platform alteration was coming but had no time to get back to it and no explanation.
How wonderful centralised CIS and subsequently Darwin is, not.
What does PAF mean?
But all the Guard/ Driver might need is " Broken down train ahead"