The Planner
Veteran Member
- Joined
- 15 Apr 2008
- Messages
- 19,676
I expect it was hoped for, but the clock would have run out.Was there ever an intention to do anything in May 25 anyhow?
I expect it was hoped for, but the clock would have run out.Was there ever an intention to do anything in May 25 anyhow?
But then why is it deferred until Dec 2025?. It shouldn't take the industry another 15 months to tweak a timetable they have been working on for 5+ years.And that is what is happening.
Agree the timetable has to work but why would the govt want spend billions again on any rail infrastructure enhancement if it doesn't deliver the outcome promised. The industry has a poor track record of late compared to BR who wired, resignalled and procured brand new trains for ECML and delivered the enhanced timetable when they said they would and within budget.
This is for the industry to collectively resolve and demonstrate to govt it can deliver.
You need to understand the process. Any May or December timetable change clock, when it comes to the lines on the graph, starts 40 weeks out, with the offer back to operators at 26 weeks out. The May 25 timetable starts on the 18th May. The D40 date was 8th August, with the D26 offer on the 15th November. It clearly wasn't considered possible, as @Clarence Yard has posted above, to meet that deadline in just under the 13 weeks we have left.But then why is it deferred until Dec 2025?. It shouldn't take the industry another 15 months to tweak a timetable they have been working on for 5+ years.
Quite simply, the Government didn’t spend the billions to deliver the outcome promised. They cut the infrastructure improvements needed to deliver the promised outcome. So there were potentially too many trains for the infrastructure supplied.
Since then NR has struggled with the problem. The region has spent ages getting virtually nowhere and created an unworkable timetable which was then handed over to MK earlier this year.
To be fair to NR, MK has spent a lot of time straightening it all out since then but they are not quite there yet.
Looks like there may hopefully be a workable new ECML timetable delivered for December 2025. However I assume there will have to be a timetable in May 2025 that enables Cambridge South Station to open.You need to understand the process. Any May or December timetable change clock, when it comes to the lines on the graph, starts 40 weeks out, with the offer back to operators at 26 weeks out. The May 25 timetable starts on the 18th May. The D40 date was 8th August, with the D26 offer on the 15th November. It clearly wasn't considered possible, as @Clarence Yard has posted above, to meet that deadline in just under the 13 weeks we have left.
The dates are all in the public domain here.
Is that really going to be possible without a rewrite? the 9Sxx would have no margin for any perturbation the 2Hxx would have a few more mins to play with the 2Cxx have time at Cambridge but Southbound departure too close to 9Sxx to allow an earlier departure to accommodate Cambridge Sth stn call. the 1Txx have 5m at Cambridge but don't they change crews here? Of course the planners will now where time might be stuffed in the schedules for pathing/engineering allowance that could help.Looks like there may hopefully be a workable new ECML timetable delivered for December 2025. However I assume there will have to be a timetable in May 2025 that enables Cambridge South Station to open.
Ok, but we knew about these timetable issues what, 12 months ago? What have the team been doing in that time?You need to understand the process. Any May or December timetable change clock, when it comes to the lines on the graph, starts 40 weeks out, with the offer back to operators at 26 weeks out. The May 25 timetable starts on the 18th May. The D40 date was 8th August, with the D26 offer on the 15th November. It clearly wasn't considered possible, as @Clarence Yard has posted above, to meet that deadline in just under the 13 weeks we have left.
The dates are all in the public domain here.
My thoughts too, for what it's worth. It will be frustrating for all involved, but it does give 'the new regime' an opportunity to assess opportunities and priorities. My own hope is for a reduction in the narrow TOC-focused approach and better integration overall under GBR.
At the end of the day freight is subsidised as much as passenger operators in covering the costs of running the network so the govt needs to make a clear policy decision over what its priorities are so the industry can implement them.As the stumbling blocks to this timetable are between nationalised LNER and private freight operators vying for competing access to the network I’m not sure GBR is likely to make any difference.
The stumbling block is not between LNER and the freight companies, the stumbling block is between Network Rail and the operators!As the stumbling blocks to this timetable are between nationalised LNER and private freight operators vying for competing access to the network I’m not sure GBR is likely to make any difference.
The stumbling block is not between LNER and the freight companies, the stumbling block is between Network Rail and the operators!
So if GBR had existed the problem would be internal and have to be resolvedThe stumbling block is not between LNER and the freight companies, the stumbling block is between Network Rail and the operators!
ExactlySo if GBR had existed the problem would be internal and have to be resolved
Then who ever authorised LNER additional services should not of done so untilYes it’s between the operators and NR (and in part because the additional infrastructure has not been built), but the fact remains that it’s the additional LNER paths alongside against existing freight paths that’s not currently able to be accommodated.
Exactly
== Doublepost prevention - post automatically merged: ==
Then who ever authorised LNER additional services should not of done so until
It was certain the paths were available.
As I say. It isn’t LNER causing the issue. It’s NWR unable to path all services which want to run.
So if GBR had existed the problem would be internal and have to be resolved
Trying to remove the clashes! You cannot just move freight and flex other paths in minutes. It can be literally a case of putting a minute in one schedule affects 20-30 others consequentially. All those need to be checked, flexed and agreed with operators. You could break a platform end margin at Kings Cross, break a terminal time for a freight service somewhere etc etc.. To say there needs to be a "can do" attitude is insulting.Ok, but we knew about these timetable issues what, 12 months ago? What have the team been doing in that time?
A lot of the rail industries problems are rightly blamed on government etc but IMO there does need to be more of a "can do" attitude from inside the industry. I appreciate that is easy for me to say from the outside but ultimately the railways rely on public support. Delays like this do nothing to help win hearts and minds.
I wasn't intending to insult individuals - apologies if that was the case. I stand by criticism of the system and processes though. If it takes 2+ years to develop a timetable then something is badly wrong. Appreciate it's complex but it should be possible to do things faster than that. If it's not, then the processes have to change. Maybe a more agile system, where a "near ready" version of the timetable is maintained and edited in short sprints?Trying to remove the clashes! You cannot just move freight and flex other paths in minutes. It can be literally a case of putting a minute in one schedule affects 20-30 others consequentially. All those need to be checked, flexed and agreed with operators. You could break a platform end margin at Kings Cross, break a terminal time for a freight service somewhere etc etc.. To say there needs to be a "can do" attitude is insulting.
How long should it take? the December 2008 VHF timetable and Dec 22 rewrite of the WCML all took as long as that, as do most other re-writes. What processes need to change? You still have to build a compliant timetable from scratch taking into account multiple stakeholder requirements, and no one has come up with an automated way of doing it yet anywhere.I wasn't intending to insult individuals - apologies if that was the case. I stand by criticism of the system and processes though. If it takes 2+ years to develop a timetable then something is badly wrong. Appreciate it's complex but it should be possible to do things faster than that. If it's not, then the processes have to change. Maybe a more agile system, where a "near ready" version of the timetable is maintained and edited in short sprints?
If I recall correctly, there were other projects mooted that never happened, e.g. extending the up slow north of Huntingdon.Agree the timetable has to work but why would the govt want spend billions again on any rail infrastructure enhancement if it doesn't deliver the outcome promised. The industry has a poor track record of late compared to BR who wired, resignalled and procured brand new trains for ECML and delivered the enhanced timetable when they said they would and within budget.
This is for the industry to collectively resolve and demonstrate to govt it can deliver.
I attempted to list them a few months back in post #119, I copied the list from the 2016 TAA:If I recall correctly, there were other projects mooted that never happened, e.g. extending the up slow north of Huntingdon.
Quite simply, the Government didn’t spend the billions to deliver the outcome promised. They cut the infrastructure improvements needed to deliver the promised outcome. So there were potentially too many trains for the infrastructure supplied.
Since then NR has struggled with the problem. The region has spent ages getting virtually nowhere and created an unworkable timetable which was then handed over to MK earlier this year.
To be fair to NR, MK has spent a lot of time straightening it all out since then but they are not quite there yet.
… and I bet if they did it would be a disaster. It would probably look fine to the computer programme, with the maximum number of wishes fulfilled, but the computer programmes have no experience of travelling 400 miles with a child and elderly mother, or needing to stop occasionally for a PNB etcand no one has come up with an automated way of doing it yet anywhere.
In around 1992, when I had a flat on Ermine St, EMUs reversed on the down fast right outside my window.Prior to electrification the 2 car DMUs reversed on the down fast then again on the up slow to get from the down side to the up bay. With a 2 car DMU the driver didn't take long to get from one end of the train to the other.
But I can't recall that being done after electrification. For a long time the 1622 from Kings Cross terminated at Huntingdon, but it went to Conington to reverse on the down slow.
Various timetables had morning starters from Huntingdon that used the up bay, but coming empty from Nene sidings.
Not yet, but its time will come.no one has come up with an automated way of doing it yet anywhere.
Actually a machine would do that far better than a human. A big data model would include sensitivity analysis, for example on station dwell overtime, and its impacts further down the line, in a way that a human system never could.It would probably look fine to the computer programme, with the maximum number of wishes fulfilled, but the computer programmes have no experience of travelling 400 miles with a child and elderly mother, or needing to stop occasionally for a PNB etc
I expect it will, but not in the short term. Every new train planning system promises the world, with TPS being the last one in 2010, it never seems to pan out that way though.Not yet, but its time will come.
Recent advances in big data and machine learning probably mean that it is already feasible, the difficulty is the cost of development, which can't be shared amongst lots of customers.
Actually a machine would do that far better than a human. A big data model would include sensitivity analysis, for example on station dwell overtime, and its impacts further down the line, in a way that a human system never could.
The big data and machine learning capabilities available now didn't exist in 2010.I expect it will, but not in the short term. Every new train planning system promises the world, with TPS being the last one in 2010, it never seems to pan out that way though.
Maybe not, but nothing is going to change in the next 10-15 years on this front. If anything, more people will get taken on.The big data and machine learning capabilities available now didn't exist in 2010.
Nothing? No drones, no driverless vehicles, no EVs, no WFH, no AI, no need to travel, no trains, no jobs for timetable planners ...?Maybe not, but nothing is going to change in the next 10-15 years on this front. If anything, more people will get taken on.
You have lost me there, clearly you knew I was talking about changes in the way timetables are built.Nothing? No drones, no driverless vehicles, no EVs, no WFH, no AI, no need to travel, no trains, no jobs for timetable planners ...?
Add in the complications of the web of TOC contracts, FOC contracts, access rights, Network Code; the views of important stakeholders along the route; stock and crew resources; the different timescales all of the previous work to. Plus many other factors that need to be considered.… and I bet if they did it would be a disaster. It would probably look fine to the computer programme, with the maximum number of wishes fulfilled, but the computer programmes have no experience of travelling 400 miles with a child and elderly mother, or needing to stop occasionally for a PNB etc