Home |
Search |
Today's Posts |
![]() |
|
London Transport (uk.transport.london) Discussion of all forms of transport in London. |
|
LinkBack | Thread Tools | Display Modes |
#11
![]() |
|||
|
|||
![]()
In message of Sat, 21 Feb
2009 13:32:07 in uk.transport.london, Paul Corfield writes On Sat, 21 Feb 2009 05:10:24 -0800 (PST), wrote: On Feb 21, 12:53*pm, Paul Corfield wrote: On Fri, 20 Feb 2009 01:26:43 -0800 (PST), wrote: Seems that theres been a failure this morning between T123 and T5 according to the traffic news. Can't even virtually brand new signals work without failing on this system? Whats the reason, cheap components, poor maintenance, bad design? What's interesting is that I checked our internal real time service information page when I saw your post. *I then went to the "history" page for the Picc line that would list every single disruption affecting the service on Friday. *There was no failure since start of traffic at the locations you cite or indeed anywhere on the Picc Line. *Perhaps the travel news got it wrong or was it Heathrow Express that went wrong? That morning, I had a text from TfL about a points failure meaning no service to T5 and minor delays to the rest of the line. The disruption was also on the TfL live travel new page. Odd - oh well, cue Boltar making some remark about LUL not knowing what it's doing if it can't update its internal system. He might be right. As is my usual practice, I checked the service status on http://www.tfl.gov.uk/ on Friday morning and saw the report Boltar referenced. There was no mention of access to HEX or Heathrow Connect. Tfl's information is not as accurate as I would like. On Thursday about 16.30, I reported the following to Chemisa, the duty LU Customer Services Supervisor. It has still not been fixed. http://www.tfl.gov.uk/tfl/livetravel...aspx?offset=we ekend and reality today show no Metropolitan service between Aldgate and Moorgate. There is a link entitled "Track Closures" from there to http://www.tfl.gov.uk/assets/livetravelnews/realtime/tube/track-closures.pdf where that closure is not mentioned. I find Lu's inability to accurately report service withdrawal - particularly when planned - is a farce. They don't seem to recognise that changing information to reflect reality is necessary. e.g. look at the link between Monument and Bank on the Tube Map; listen on a train at Monument to the interchange information advising interchange to Central, Northern and Waterloo & City lines. Pretty well everywhere on a Saturday after 08.00 on a manuscript Service Update whiteboard, you will see the Waterloo & City status as "Planned Closure". Unusually, it is true this weekend. It took me a good 5 minutes at Holloway Road to persuade the gateline CSA to correct this error a couple of weeks ago. Today, no gateline CSA was to be seen. I HATE operational gates without staff in sight. It scorns customers. -- Walter Briscoe |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Northern line failure | London Transport | |||
Signal Failure | London Transport | |||
Signal failure on the central line? | London Transport | |||
How can you have a signal failure on an ATO system? | London Transport | |||
Why can't LU cope with a signal failure? | London Transport |