During 2 lengthy chats respectively with a driver during a lengthy delay and with a customer services staff member after the same, they both expressed frustration that one of the main issue was being unable to get information from control...because control were too busy addressing the issue.
Both also expressed the possibly contentious viewpoint that Control staff (at FCC and GTR) were rarely ex-drivers, but usually people who had come up the signalling staff side and hence, perhaps, "did not fully appreciate the passenger perspective".
I recall that fateful evening a year or two back where, due to a software glitch, a huge number of trains were stranded on the ECML, because the TSGN trains wouldn't restart after a break in power, and required the in person attendance at numerous locations for technicians to do so. At least an hour was wasted, as I recall, because management couldn't decide what the best option was.
That is always a problem - information should flow through various "hubs" ideally, but people cut out the middle man go direct to the source that already has 10 phone calls queued whilst already contacting the necessary individuals to get the show moving again. It's not ideal for say staff at Lewisham to hear it 3rd hand, but the key parties are the driver, MOM, signaller and possibly controller. But station hubs are quite useful
Do any posters on here actually work in a railway control room? I get the impression this is turning into a bit of an echo chamber and it’s a tad unfair that control staff are unable or willing to defend themselves. I’m sure they’re well aware improvements can and need to be made, but having shadowed on a day where the brown stuff properly hit the fan they certainly try
Yep.
There is a practical problem as I listed above. Firstly that when you really get into a scenario like Lewisham your workload doesn't say double from normal, it goes up 10x. Everyone wants information at the same time. And unless you have a bank of competent qualified people ready to step in to help manage the situation available spare 24/7, there will be communication bottlenecks. Nothing will be able to change that unfortunately. However, some controllers are not proactive to the point at which its gone from "oh this isn't great" to "a critical decision needs to be made". If you do read the full report you'll see it took over 40 minutes before the Incident Controller and the responsible controller was even aware there was a problem. Some of this goes down to a lack of proactiveness but I was working this day in the region and everything was going wrong everywhere. I can understand not picking it up straight away. What would have helped is the following:
1) The signaller not to presume everything was running normally and to push every train right up to the closing signal which blocked the entire Lewisham area.
2) The SSM to have been forthright in his call about the stranded train (departing Lewisham 2M48) when speaking to control rather than "issues".
3) Control to have acted soon and following their own guidleines about stranded trains (stuck 2M50) on a 376 which is known not to have toilets.
4) The command structure to have worked appropriately.
5) Southeastern's passenger information wasn't consistent and angered people (being called "tresspassers")
Many of the above have been learnt and new policies implemented. It was unfortunate every train was just slightly too long to overlap signals.
Don't get me wrong I think there are several individuals who - despite being in a position which is often advertised as requiring calmness under pressure - are not up to it when it gets really bad and get focused in one very specific detail and try to fix that. It was noted that the SE/NR team didn't hold any timeouts to assess the situation and look at the wider picture. They were firefighting the whole time and hence they were lurching from issue to issue with no holistic plan.
If controllers do not have stock experience and no trackside experience then they are being asked to deal with things which they do not have the knowledge to sort.
Where they generally shine is it getting the service back when the issue has been fixed, not in sorting the initial issue if that involves equipment failure.
You need some stock experience, but tell me why exacting trackside experience is necessary? Controllers will be aware of limitations on the infrastructure, areas of concern on the network, core stock details. They are not stock technicians/engineers/fitters and there are plenty of people either within a control room or a depot who are a call away for a driver. I know many controllers who regularly go out to visit their network and speak to local hubs (although not happening recently of course).
Edits: mainly due to my spelling and grammar.