Seems fine so far.What's the situation this morning? I have to travel from Portsmouth back to London
Seems fine so far.What's the situation this morning? I have to travel from Portsmouth back to London
Hope so, thanksSeems fine so far.
Where's "Earlesfield"...?T3 Possession unsurprisingly has been setup to get to the root of this issue. Hopefully the night team solve it. Best of luck to them.View attachment 184600
Haha must be a typo on siggyWhere's "Earlesfield"...?
Yup - paper-perfect-plans! Although I'd rather be in control for the SWML than Scotland, at least the SW division was a pretty simple layout to play with!Also an ex-Controller, although never for a railway as busy as Waterloo (Scotland in my case, with different challenges).Contingency Plans are workable when the disruption occurs just after the service has shut down for the night, giving Control time to arrange and disseminate the amended train plan. If it happens once the service has started things are not so simple, and losing half the platforms at a station as busy as Waterloo must be close to unmanageable. The number of trains and Traincrew displaced as already mentioned will be immense.
Which is not to make excuses for the railway, signalling failures such as this should simply not happen - And especially should not happen twice. The design and reliability of the system needs forensic examination.
You're absolutely right - the plans themselves are generally sensible in principle, but rely on crew and stock all being in the new right place at a new right time - which is...challenging, to say the least.There is likely an immediate contingency plan for partial or complete losses of platforms at Waterloo. And the service pattern would indeed have to be thinned, and the plan would probably tell you what service groups and what is cancelled / terminated short etc.
However, this is very different - as you know - to having an off-the-shelf train service plan for the various stock if it terminates at Clapham Junction / Wimbledon / Surbiton etc. Trains step up, don't form their booked workings, shunt, crew are displaced etc.
What the industry does need to be better on is not the actual contingency plans themselves - which prescribe the number of tph and the service patterns - but the practicalities of doing so with the stock and crew constraints. These need to be developed somewhat in advance and flexibility of crew arrangements required to pull them off diagrams sooner so long as they don't trip over the usual issues (late PNBs / finish at wrong destination).
Workload is of course another issue, but having the fundamental, 'off-the-shelf' "train service plan for the SX contingency plan 24A" already available to utilise and share, can surely help massively. But it can't be done on the fly with the train service controllers who are already firefighting the issue - it's another issue entirely to essentially make VSTPs for the rest of the day.
A plan isn't worth the paper it's on if it's not implementable in practice.You're absolutely right - the plans themselves are generally sensible in principle, but rely on crew and stock all being in the new right place at a new right time - which is...challenging, to say the least.
A plan isn't worth the paper it's on if it's not implementable in practice.
I guess I'd made a grave error assuming that the people who drafted a contingency plan would have drafted something that could also be implemented.
What kind of signalling issue prevents a train from running in passenger service but allows it to run as empty stock?Seems to have been a residual problem on the Shepperton branch this morning. 2H05 (0640 Kingston to Shepperton, unit 701044) was terminated at Hampton Wick, ran ECS to Shepperton and back to Fulwell, then took up its diagram again at Fulwell as 2H14 at 0723 (should have been the 0711 ex-Shepperton). Signalling issues were cited as the cause. Not sure what the issue was, as this was not the first train of the day down the branch.
Guard caught up in the chaos the previous night needing their 12hrs rest?What kind of signalling issue prevents a train from running in passenger service but allows it to run as empty stock?
Trouble is, when do you plan for that plan to apply? To make a plan that's easily implemented in the current environment, you're talking a train-by-train, and even crew-by-crew plan, that has to account for the time of day as well, as you're operating these days with minimal full-crew/stock working and minimal spare crew coverage, and rationalised (read: reduced) route knowledge. With that in mind, 0900's contingency plan actions at 1000 (ie an hour into disruption) is likely to be completely different to 1000's contingency plan for an incident that started at 1000 (if that makes sense).A plan isn't worth the paper it's on if it's not implementable in practice.
I guess I'd made a grave error assuming that the people who drafted a contingency plan would have drafted something that could also be implemented.
Who knows? Butn it's odd it was only taken out of passenger service after it had got to Hampton Wick.Guard caught up in the chaos the previous night needing their 12hrs rest?
several thousand people at Woking who've gone there because shuttle trains managed to get them that far and optimism said there might be a train to Waterloo afterward when the reality is there wasn't isn't much fun for them or the staff.
This does seem to work on the assumption that Waterloo is the only destination people want to get to when in reality there are huge flows elsewhere on the network. It's poor when a signal failure in London often means no service for hours on end as far away as Portsmouth, Exeter or Weymouth and that local passengers are effectively abandoned.
It certainly contrasts poorly with London Underground who will run shuttles either side of any infrastructure failure.
Graham Eccles when recently interviewed on the Green Signals Podcast did consider that they are overly complex and need to be simplified if swifter recovery from disruption is ever going to be achieved.The SWR network is rather different from the Underground however - Weymouth is rather further from Waterloo that Epping is from West Ruislip, for example, making amending Traincrew workings very much simpler! However it does seem poor when multiple cancellations occur so far from the point of disruption, are SWR's crew diagrams so complex that arranging shuttles is impossible, or at least very difficult?
Unfortunately, yes. Simplest diagrams when I was crew were often Farnham-Waterloo-Basingstoke with driver and unit, then Basingstoke-Waterloo-Alton-Farnham with driver and a new unit. The worst would have been Farnham-Waterloo with driver and unit, Waterloo-Staines via Hounslow (new unit), Staines-Waterloo via Hounslow (new unit), Waterloo-Reading (new driver and unit), Reading-Farnham empty (or by taxi if you outstabled).The SWR network is rather different from the Underground however - Weymouth is rather further from Waterloo that Epping is from West Ruislip, for example, making amending Traincrew workings very much simpler! However it does seem poor when multiple cancellations occur so far from the point of disruption, are SWR's crew diagrams so complex that arranging shuttles is impossible, or at least very difficult?
It's not just the SWR network. A large part of the railway has tied itself up in knots making everything overly complex in the name of flexibility, under the illusion that this is a good idea, because it apparently saves money.The SWR network is rather different from the Underground however - Weymouth is rather further from Waterloo that Epping is from West Ruislip, for example, making amending Traincrew workings very much simpler! However it does seem poor when multiple cancellations occur so far from the point of disruption, are SWR's crew diagrams so complex that arranging shuttles is impossible, or at least very difficult?
I echo this... it would be more resilient (IMHO) to have:I have long been of the opinion that the SWR network would be significantly more resilient, if as many stretches of line as possible had local shuttle services as part of the regular timetable, such as the Bournemouth to Winchester train.
I echo this... it would be more resilient (IMHO) to have:
This sort of thing works well in Switzerland...
- Shuttles running all stations between Waterloo/Woking, Woking/Basingstoke, Basingstoke/Southampton, Southampton/Bournemouth, Bournemouth/Weymouth
- A semi-fast service only stopping at Woking, Farnborough
, Basingstoke, Southampton, Bournemouth and Weymouth - plus maybe Eastleigh and Poole
Switzerland tends to have invested in generously resourced infrastructure, fleet and manpower.I echo this... it would be more resilient (IMHO) to have:
This sort of thing works well in Switzerland...
- Shuttles running all stations between Waterloo/Woking, Woking/Basingstoke, Basingstoke/Southampton, Southampton/Bournemouth, Bournemouth/Weymouth
- A semi-fast service only stopping at Woking, Farnborough
, Basingstoke, Southampton, Bournemouth and Weymouth - plus maybe Eastleigh and Poole
Not really. The infrastructure is built based on the desired timetable and does not support much more than that. Everything is highly automated and controlled from a few signaling centers. There is not a lot of manpower available, but a lot of flexibility (drivers sign quite a lot of routes and traction) and less fragmentation. Only very few restrictions regarding vehicles and routes, almost everything can go everywhere.Switzerland tends to have invested in generously resourced infrastructure, fleet and manpower.
True... but that's mostly a symptom of our typical 1 or 2tph service patterns where, if a connection is poorly scheduled or missed, you have a 30 minute wait.trouble is that "Station x loses direct service to London" is a guaranteed headline generator that any politically savvy manager will shy away from.
I do think a lot of station pairs outside London are actually quite poorly served with the current timetable on the SWML due to services skip stopping on different patterns. It's certainly interesting to contemplate where a radically different approach would lead, and if it could also be more robust in disruption. Probably one for a new thread!True... but that's mostly a symptom of our typical 1 or 2tph service patterns where, if a connection is poorly scheduled or missed, you have a 30 minute wait.
With 4tph, it's always less than a 15 minute connection - which isn't that long, and you will probably make up on the fast section of a journey.