|
Post by scheduler on Jun 28, 2021 0:38:38 GMT
How about because the platform indicators at Richmond cannot display a destination of Edgware Road.
|
|
|
Post by AndrewPSSP on Jun 28, 2021 6:44:08 GMT
Why won't they be able to? I thought it was all digital displays at Richmond
|
|
|
Post by upminster on Jun 28, 2021 10:45:27 GMT
Upminster and Barking drivers do not go beyond HSK. This goes back to C stock days.
|
|
|
Post by spsmiler on Jun 28, 2021 22:06:31 GMT
Upminster and Barking drivers do not go beyond HSK. This goes back to C stock days. yes but why would they? ... as history states that this is Metropolitan territory! I suppose that this also means that in the days when the District operated some of the Circle line trains (on Sundays) these were not crewed by Upminster or Barking staff.
|
|
|
Post by scheduler on Jul 1, 2021 22:54:25 GMT
London Underground timetables and operations have spent many years proving that simple repetitive routings make line control in times of disruption simpler, and ease recovery after disruption. Having multiple interlocking routes is a recipe for disaster, and would put reliability and recoverability of service in doubt. So have the passengers do a cross platform change, not the trains works out better. There is no spare platform capacity at Edgware Road to reverse another or higher level of service, remember 1 bay platform reverses the Circle Line, the other bay platform reverses the District, with each on a 10 minute service pattern, and needing at least 5 minutes (preferably more) to reverse the train, there's no room for anything else. On the odd occasion at the service start-up (and on frequency changes during the day) there might be an odd train from Ealing run to Edgware Road, but there's a total block on anything to/from Richmond running to Edgware Road.
|
|
|
Post by scheduler on Jul 1, 2021 22:57:16 GMT
Why won't they be able to? I thought it was all digital displays at Richmond Not in Network Rail's computer system.
|
|
|
Post by Dstock7080 on Jul 2, 2021 8:01:28 GMT
There is no spare platform capacity at Edgware Road to reverse another or higher level of service, remember 1 bay platform reverses the Circle Line, the other bay platform reverses the District, with each on a 10 minute service pattern, and needing at least 5 minutes (preferably more) to reverse the train, there's no room for anything else. Stepping-back of District trains at Edgware Road is on the cards, possibly not for WTT152 in September but soon after, to provide a 7½min frequency or lower.
|
|
DWS
every second count's
Posts: 2,487
|
Post by DWS on Jul 2, 2021 10:05:16 GMT
There is no spare platform capacity at Edgware Road to reverse another or higher level of service, remember 1 bay platform reverses the Circle Line, the other bay platform reverses the District, with each on a 10 minute service pattern, and needing at least 5 minutes (preferably more) to reverse the train, there's no room for anything else. Stepping-back of District trains at Edgware Road is on the cards, possibly not for WTT152 in September but soon after, to provide a 7½min frequency or lower. What changes are happening with WTT152 in September 2021 ?
|
|
|
Post by Dstock7080 on Jul 2, 2021 12:43:56 GMT
Stepping-back of District trains at Edgware Road is on the cards, possibly not for WTT152 in September but soon after, to provide a 7½min frequency or lower. What changes are happening with WTT152 in September 2021 ? Nothing too much for the District, mostly to accommodate the changes to the faster running time of Circle H&C trains Hammersmith-Whitechapel/Tower Hill and the retiming and service changes across the Piccadilly Line. Metropolitan will also have additional City trains in the peak as well as faster running from Finchley Road-Aldgate
|
|
rincew1nd
Administrator
Junior Under-wizzard of quiz
Posts: 10,286
|
Post by rincew1nd on Jul 3, 2021 7:34:29 GMT
There is no spare platform capacity at Edgware Road to reverse another or higher level of service, remember 1 bay platform reverses the Circle Line, the other bay platform reverses the District, with each on a 10 minute service pattern, and needing at least 5 minutes (preferably more) to reverse the train, there's no room for anything else. I wasn't aware of any bay platforms at Edgware Road.
|
|
|
Post by 35b on Jul 3, 2021 7:41:08 GMT
There is no spare platform capacity at Edgware Road to reverse another or higher level of service, remember 1 bay platform reverses the Circle Line, the other bay platform reverses the District, with each on a 10 minute service pattern, and needing at least 5 minutes (preferably more) to reverse the train, there's no room for anything else. I wasn't aware of any bay platforms at Edgware Road. I’m trying to remember the last time I was aware of a train using p2 or p3 from the east!
|
|
DWS
every second count's
Posts: 2,487
|
Post by DWS on Jul 3, 2021 8:03:16 GMT
There is no spare platform capacity at Edgware Road to reverse another or higher level of service, remember 1 bay platform reverses the Circle Line, the other bay platform reverses the District, with each on a 10 minute service pattern, and needing at least 5 minutes (preferably more) to reverse the train, there's no room for anything else. I wasn't aware of any bay platforms at Edgware Road. I think the author of this post means platforms 2 &3 at Edgware Road.
|
|
|
Post by Dstock7080 on Jul 3, 2021 9:33:09 GMT
I’m trying to remember the last time I was aware of a train using p2 or p3 from the east! Can only go into pfm.2 from east after using shunt-ahead from pfm.1. No direct access into pfm.2 from east
|
|
|
Post by d7666 on Jul 3, 2021 12:06:46 GMT
London Underground timetables and operations have spent many years proving that simple repetitive routings make line control in times of disruption simpler, and ease recovery after disruption. Having multiple interlocking routes is a recipe for disaster, and would put reliability and recoverability of service in doubt. So have the passengers do a cross platform change, not the trains works out better. Ease of recovery for control perhaps, but not necessarily for passengers; if you plan A to B via X and seperately C to D also via X, then if a problem occurs say between A and X then B loses out too - passengers many have majorly disrupted or even no service anywhere from A to B; if normal is A to B or D alternating with C to B or D then that leaves at least some service to B. If you use the argument of turning back short to serve B, well that fits both scenarios (B and D) so cancels out. Don't think another or higher level of service was suggested by the OP, merely different origin points. Also, elsewhere in the thread people seem to be using the argument that some depots don't know all the roads. That is not a blocking point to planned timetabling - if the service were so planned differently into timetables, then they would know the roads, they'd have to, route training would be part of the business plan to introduce it.
|
|
castlebar
Planners use hindsight, not foresight
Posts: 1,316
|
Post by castlebar on Jul 3, 2021 12:57:55 GMT
I think this thread proves that optimists and innovators will always try and find the reason "why" to do something and see how it works
Whereas there are others who will deliberately go and look for a "reason why not" to do something.
Thank goodness we do still have some innovators in this country.
"Different" and "innovative" don't necessarily mean "complex"
|
|
|
Post by 35b on Jul 3, 2021 13:00:29 GMT
London Underground timetables and operations have spent many years proving that simple repetitive routings make line control in times of disruption simpler, and ease recovery after disruption. Having multiple interlocking routes is a recipe for disaster, and would put reliability and recoverability of service in doubt. So have the passengers do a cross platform change, not the trains works out better. Ease of recovery for control perhaps, but not necessarily for passengers; if you plan A to B via X and seperately C to D also via X, then if a problem occurs say between A and X then B loses out too - passengers many have majorly disrupted or even no service anywhere from A to B; if normal is A to B or D alternating with C to B or D then that leaves at least some service to B. If you use the argument of turning back short to serve B, well that fits both scenarios (B and D) so cancels out. Don't think another or higher level of service was suggested by the OP, merely different origin points. Also, elsewhere in the thread people seem to be using the argument that some depots don't know all the roads. That is not a blocking point to planned timetabling - if the service were so planned differently into timetables, then they would know the roads, they'd have to, route training would be part of the business plan to introduce it. My own experience as a passenger is that simple service patterns lend themselves to service recovery better than complex ones. While shared track means you can’t completely isolate disruption, relying on complex diagrams for trains and/or crew creates ripple effects that make recovery harder by introducing both interdependencies and complexity.
|
|
|
Post by d7666 on Jul 3, 2021 13:43:17 GMT
I think this thread proves that optimists and innovators will always try and find the reason "why" to do something and see how it works Whereas there are others who will deliberately go and look for a "reason why not" to do something. Thank goodness we do still have some innovators in this country. "Different" and "innovative" don't necessarily mean "complex" Indeed. Look back at the weeping and wailing and gnashing of teeth when breaking the Circle and forming the 'teacup' came up. Impossible. Impractical. They all said. One argument for not doing something is complex train crew and who know what, and I don't dis-agree, but innovation in this example of origin points to Edgware Road does imply all crews would have to know all routes - and that does not complexicate things when it comes to recovery, it SIMPLYFIES them. ! But ... "we've always done it this way" ........
|
|
|
Post by MoreToJack on Jul 3, 2021 13:58:53 GMT
I wasn't aware of any bay platforms at Edgware Road. I’m trying to remember the last time I was aware of a train using p2 or p3 from the east! Two booked into platform 3 from Baker Street (one empty), also commonly used to put IR Circles in the correct platform if they've started back at Moorgate. Two are also booked into platform 2 ex Paddington and on to Baker Street in service. Nothing booked platform 3 west to east reversal (or, indeed, straight east ex Paddington). Edit: And it turns out there’s several short tripping to Edgware Road and then reversing west to east in 3 today!
|
|
|
Post by spsmiler on Jul 3, 2021 17:26:54 GMT
Trains from the Bayswater direction sometimes queue to enter Edgware Road, when this happens it would seem better if there was the option to reverse at the station before - Paddington - which for many passengers IS their destination. It would also reduce overcrowding caused by waiting passengers.
|
|
Tom
Administrator
Signalfel?
Posts: 4,196
|
Post by Tom on Jul 3, 2021 17:44:54 GMT
Trains from the Bayswater direction sometimes queue to enter Edgware Road, when this happens it would seem better if there was the option to reverse at the station before - Paddington - which for many passengers IS their destination. Yes, but it doesn't help the bigger picture for a number of reasons: (1) The passengers wishing to alight will have to fight those wishing to board to travel towards High Street Kensington - depending on which platform is used this would also result in the inner rail passengers having to cross over to the Outer Rail platform though some quite narrow corridors. If the suggested crossover brings the arriving train into the Inner Rail platform this means that you're now having to hold up the previously unaffected inner rail service for it. (2) The train could only reverse at Paddington if it doesn't have a crew relief at Edgware Road (i.e. it can only be a District train or a Circle which doesn't have a crew relief). (3) It would then go back out of turn which affects junction working and subsequent crew reliefs - potentially it could get to somewhere like Earl's Court and there would be no relieving Train Operator as they're stuck behind it. (Yes I know it can be reformed but that's why it's sometimes better to have everything 20 late rather than one on time and the others all late). There are, as you can see, good reasons why we don't do this sort of thing.
|
|
Chris M
Global Moderator
Forum Quizmaster
Always happy to receive quiz ideas and pictures by email or PM
Posts: 19,762
|
Post by Chris M on Jul 4, 2021 0:36:51 GMT
Trains from the Bayswater direction sometimes queue to enter Edgware Road, when this happens it would seem better if there was the option to reverse at the station before - Paddington - which for many passengers IS their destination. Yes, but it doesn't help the bigger picture for a number of reasons: (1) The passengers wishing to alight will have to fight those wishing to board to travel towards High Street Kensington - depending on which platform is used this would also result in the inner rail passengers having to cross over to the Outer Rail platform though some quite narrow corridors. If the suggested crossover brings the arriving train into the Inner Rail platform this means that you're now having to hold up the previously unaffected inner rail service for it. (2) The train could only reverse at Paddington if it doesn't have a crew relief at Edgware Road (i.e. it can only be a District train or a Circle which doesn't have a crew relief). (3) It would then go back out of turn which affects junction working and subsequent crew reliefs - potentially it could get to somewhere like Earl's Court and there would be no relieving Train Operator as they're stuck behind it. (Yes I know it can be reformed but that's why it's sometimes better to have everything 20 late rather than one on time and the others all late). There are, as you can see, good reasons why we don't do this sort of thing. A crossover between Paddington and Praed Street junction with passengers tipped out onto the platform would mean (1) was not an issue, but would not solve (2) or (3). A reversing siding between the tracks where it could wait out the way of other trains until it's turn would resolve (3) but (a) there isn't space, (b) even if there was it would be very expensive to build, (c) it would not solve the crew relief at Edgware Road issue and (d) I'm not sure how much of the original problem it would solve. Even with just (b) and (d) that would be a non-starter in practical terms. Rebuilding High Street Kensington so platform 3 was the normal northbound through platform and platform 2 was a bi-directional through platform where trains could wait their turn would (in combination with a reversing siding between Paddington and Praed Street junction) solve (1) and (3) and possibly slightly mitigate the delay issues (by having timetables that took advantage of the flexibility at HSK to allow for recovery time there). I don't know whether this would be possible (a quick look at various online resources combined with my own memories of HSK suggests that it isn't obviously either possible or impossible, although the platform would need to move south) but even if it is then it would be very expensive, wouldn't solve issue (2) and so be very unlikely to be good value for money.
|
|
Tom
Administrator
Signalfel?
Posts: 4,196
|
Post by Tom on Jul 4, 2021 9:08:34 GMT
You have of course assumed Chris that the train can get out of Paddington platform and at least move up so as to be clear of a potential crossover, which would put the front of the train past where the old Praed Street Junction home signal was. Given that the issue is about queuing into Edgware Road this is unlikely to be of great benefit.
In any case the discussion is starting to drift into RIPAS territory now...
|
|
roythebus
Pleased to say the restoration of BEA coach MLL738 is as complete as it can be, now restoring MLL721
Posts: 1,275
|
Post by roythebus on Jul 5, 2021 8:34:57 GMT
Upminster and Barking drivers do not go beyond HSK. This goes back to C stock days. yes but why would they? ... as history states that this is Metropolitan territory! I suppose that this also means that in the days when the District operated some of the Circle line trains (on Sundays) these were not crewed by Upminster or Barking staff. The only District crews to do the Circle were from Parsons Green. Acton Town crews signed to Edgware Road. Upminster and Barking (District) crews didn't go beyond High Street until fairly modern times. I don't think that was until well after the 1970s. I don't recall east end staff doing Edgware Road services in the early 1970s when I was on the District, but I may be wrong.
|
|
|
Post by greatkingrat on Jul 5, 2021 18:08:49 GMT
I think this thread proves that optimists and innovators will always try and find the reason "why" to do something and see how it works Whereas there are others who will deliberately go and look for a "reason why not" to do something. Thank goodness we do still have some innovators in this country. "Different" and "innovative" don't necessarily mean "complex" Anyone can come up with dozens of possible "innovations" to service patterns in a few minutes. Just because you can pick two stations that do not currently have direct services between them doesn't automatically mean that introducing such a service is always better than the status quo.
|
|
|
Post by quex on Jul 5, 2021 18:56:04 GMT
Why won't they be able to? I thought it was all digital displays at Richmond Not in Network Rail's computer system. I was passing through Richmond one weekend when there were South Kensington turnbacks. The DMIs could only display "SKENSIN Via: Earls Court" for every train.
My guess - based on NR practise - is the DMIs have some sort of overlay that translates the raw code (like SKENSIN) into a human-readable plain name. The translation is then presumably only available for a select few codes corresponding to "important"/common locations (Upminster etc). I guess you could get it to display Edgware Road by giving it the correct translation.
|
|
|
Post by Chris L on Jul 5, 2021 21:38:11 GMT
The original idea for splitting the Circle line was for trains to run from Hammersmith and loop the Circle line and then head for Barking.
Trains from Barking would do the opposite.
It would have given drivers more time in the open but it would have been difficult to communicate to passengers. The current service pattern was thought to be simpler.
|
|
|
Post by johnlinford on Jul 5, 2021 21:41:01 GMT
Presumably that would have effectively abolished the Hammersmith and City line?
|
|
Tom
Administrator
Signalfel?
Posts: 4,196
|
Post by Tom on Jul 5, 2021 22:26:07 GMT
A similar concept was tried for the Covered Way 58 renewal works in June (July?) 1999. The plan was Circle line trains would run Olympia - Earl's Court - Aldgate - Edgware Road - Earl's Court - Wimbledon (it may have been Olympia to Edgware Road and thence round the circle to Wimbledon now I come to think of it, it was 22 years ago after all). In the end it was just too complicated to operate and was abandoned after a week, with the Circles cancelled, the District back to their 'ordinary' working timetable, and a few C Stock Extras operating Mansion House to Putney Bridge in the peaks.
When I sat on the Tower Hill desk in Earl's Court Control Room, whilst on Work Experience, the first thing I learnt to do on the desk was cancel circles and I spent the whole day doing it.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 6, 2021 0:38:03 GMT
I remember changing the TD signs at Cannon St and Tower Hill for new glass that showed Olympia’s
|
|
|
Post by jimbo on Jul 6, 2021 4:15:06 GMT
When the current service was first proposed, it was claimed that there would be no cost for change to maps and signage! Only need for High Street side and north side to have signs saying change at Edgware Road for Circle line when no through train shown! That would have allowed easy reversion if it didn't work well, as in 1999 trial.
|
|