Phil
In memoriam
RIP 23-Oct-2018
Posts: 9,473
|
Post by Phil on Jul 31, 2008 19:20:46 GMT
This is not a rant - - - honest!!!, but a question (or lots!)
I was caught up in yesterday's debacle out west. summary is, I arrived Paddington on time by FGW (yes, Andrew Haines has REALLY turned the company round!) at 1040 for an appointment at Hounslow Central at 1200. Guess what time I got there - I'll give some clues!
1. Wimbleware to ECT: fine. Intend to change to Picc at Hamm. so cross platforms to find another Wimbledon - then another - then another....so it's 2. down to the Picc which states the only problem is Ruislip to UXB. 3. Heathrow train waits 8 mins at ECT then crawls to Baron's and to Hamm. 4. Put on local lines towards ACT, stop at Turnham Green (announced) the stop halfway to chiswick Park. Crawl into station overtaking another Picc on the fast. He overtakes us (doors open) and we eventually crawl to 2nd signal before ACT platforms. 5. We now wait for 15 min whilst THREE more piccs on the fast are allowed into the (one remaining) platform in front of us. By this time there was distinct unease beginning to spread. 6. Get into (local) platform, wait 5 mins, then told that this train was running to Northfields only - which it did while we were still waiting in the train in the fast platform....... 7. More waiting while train is reformed, then finally (slowly) away.
Get to Hounslow at.....? Yup, 1240, 2 hours from Padd: I had now missed my 'slot' and had to wait another 30 mins! Since the appointment involved measuring my blood pressure you can imagine what the effect was........
So, to tfc and the rest: I know all about the 'minor delays' bit covering a whole line, not just one area (though judging from the overtaking trains and the time they were spending in the platforms that whole end must have been up the wall), but WHY KEEP TRYING TO CON THE PUNTERS? To be specific, if they had told the truth at Hammersmith (rather than pretending it was all OK really, nothing to worry about), I would have been off the train, onto a direct bus to Hounslow and in time for the appointment. I was seriously inconvenienced when if I had the true picture I could have made it just a minor glitch. If this is TfL policy "don't scare the customers especially the ones for Heathrow" then I worry about where this much-vaunted customer service aspect is going......
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 31, 2008 19:35:50 GMT
I'm amazed you found so many Wimbledon trains at Earl's Court- there never seems to be any when I need one!! ;D ;D
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jul 31, 2008 23:02:15 GMT
IIRC there was a signal failure at Acton Town during the late morning - I checked my bus/tube journey into work at about 10:30 and was told about the suspension, with good service on the rest of the line. When I checked again shortly before midday it reported the severe delays due to a signal failure at Acton Town. Looking at the timings you give it's *possible* you were caught up in it as the situation began, which means that either staff were not aware of the problem, or had not yet realised the extent of the problem. Without being there at the time and knowing the details of the situation (ie, the exact problem, how quickly the nature of the problem was determined and therefore what could be done to work around it) it's hard to answer the question any further.
|
|
Phil
In memoriam
RIP 23-Oct-2018
Posts: 9,473
|
Post by Phil on Aug 1, 2008 6:36:07 GMT
Without being there at the time and knowing the details of the situation (ie, the exact problem, how quickly the nature of the problem was determined and therefore what could be done to work around it) it's hard to answer the question any further. Ta - I got to ECT Picc w/b platform at 1123 (yes, I was watching the clock even then.......). But to take 15 mins to get to Hammersmith (trains stick to stick) would surely have alerted the staff that the service was no longer 'minor delays'. And as soon as we were sent down the local I KNEW summat was up!!
|
|
|
Post by thc on Aug 1, 2008 6:38:49 GMT
Claiming that lines currrently have a "good" service, when in fact they have a normal or scheduled service, really doesn't earn LU any brownie points with the passengers. In any case, surely it's for the recipient of a service, rather than its provider, to determine whether it is "good" or not.
Many's the time I've been stood on Shepherds Bush H&C platforms to be told over the long-line PA that the H&C has a "good" service, when clearly it's nothing of the sort. The groan from fellow platform-dwellers is audible each time.
THC
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 4, 2008 11:53:06 GMT
In any case, surely it's for the recipient of a service, rather than its provider, to determine whether it is "good" or not. 'Good' is not just a superlative but also means something which achieves what it aims to do. For example if someone in rugby kicks a goal it is 'good' if it passes between the posts irrespective of how unspectacular or relatively easy it was. In the case of the Underground, you may think a good service (one achieving the aims of the service level determined on a particular a line) is not good enough (that it is too infrequent to meet the aims of moving a large number of people efficiently), but neither use of 'good' is any more accurate than the other. It all comes down to context, but LU usage here is correct. Saying it is a 'normal service' says nothing about how it is running, just that they are not operating a special timetable. A normal service can be subject to delays and cancellations, a good service cannot.
|
|
Chris M
Global Moderator
Forum Quizmaster
Always happy to receive quiz ideas and pictures by email or PM
Posts: 19,775
|
Post by Chris M on Aug 4, 2008 17:44:26 GMT
However in the experience of many people here, a service that is suffering significant delays is still being described as "good".
|
|
|
Post by superteacher on Aug 8, 2008 10:55:10 GMT
In any case, surely it's for the recipient of a service, rather than its provider, to determine whether it is "good" or not. 'Good' is not just a superlative but also means something which achieves what it aims to do. For example if someone in rugby kicks a goal it is 'good' if it passes between the posts irrespective of how unspectacular or relatively easy it was. In the case of the Underground, you may think a good service (one achieving the aims of the service level determined on a particular a line) is not good enough (that it is too infrequent to meet the aims of moving a large number of people efficiently), but neither use of 'good' is any more accurate than the other. It all comes down to context, but LU usage here is correct. Saying it is a 'normal service' says nothing about how it is running, just that they are not operating a special timetable. A normal service can be subject to delays and cancellations, a good service cannot. It's up to the passengers to decice if a service is good, not LUL. What utter arroganca that LUL think they have the right to dictate when a service is good. If I told you that a film was "good", you may not agree with me - fair enough? The Central line hasn't operated a good service in the peaks for many months now due to cancellations resulting from stock non availability. Gaps of 3 - 5 minutes are not uncommon, which leads to crush loading on the eastbound from Bank - Stratford. And blaring out, yet again, is the "good" service announcement. Some people need to wake up.
|
|
|
Post by Tomcakes on Aug 8, 2008 19:22:23 GMT
But hey, the managers want their "customer service" points... if they actually cared about their passengers/customers/wage-payers, they would care less about ticking boxes and more about what people actually want.
|
|
|
Post by superteacher on Aug 12, 2008 19:27:40 GMT
Just to fan the flames on this one (and to show those who defend this system to the death how rubbish it is):
Central Line - eastbound at Bank 17:30. Train departed from platform. Next departures 3min, 9 min and 11 min. This is below the timetabled 2 min service (it has been every evening, since the 92 stock motor problems began), but worse was to come. The platform was busy anyway (it usually is!), but the train describer didn't change for about 3 min. To me (and others in the know), this means that the service had stopped for some reason. There was a member of staff on the platform, but he hadn't been told anything. The platform was by now heaving (almost dangerously overcrowded), and then yes, you've guessed it:
"Circle line has minor delays, all other lines are operating a GOOD service."
Ermmmmmmm, it doesn't look like it. It was mentioned at one point that the "Good Service" tag is an overall line synopsis. However, there was a problem on the busiest stretch of the line, so surely the service on that section should take precedence when deciding if the service was "good." Eventually, the staff member announced that the delay was due to a passenger alarm being activated on a train at Marble Arch (the train that was 9 mins away). No doubt the train that was 3 mins away was being held to even out the gap behind it. Needless to say, it was chaos at Bank for the next 15 mins, because once the trains were moving, it took that long to disperse the crowds from the platform.
And yes, the "Good Service" message continued to play its merry tune, intermingled with the cries of children who were being squashed onto the train.
Now, is anyone going to defend the "Good Service" message . . .
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 13, 2008 23:13:26 GMT
Now, is anyone going to defend the "Good Service" message . . . Certainly not me, who a couple of weeks ago on a Saturday evening round about 23.00 was trying to catch an EB Central line train at Holborn to find myself with a 14 minute wait - and the gap was clearly bigger than 14 mins as there were quite a few people on the platform when we got there. The published frequency at that time of night (travelling to Leyton so disregarding which branch the train eventually went to) is every 5 mins. The Central line was advertising a good service. Pity my companion for the evening, who was treated to an extended rant about headways and advertising a good service when it is not. The truly amazing thing is he actually wants to go out with me again ;D
|
|
|
Post by ducatisti on Aug 14, 2008 8:43:12 GMT
Who do we shout at for this sort of thing? It's all very well saying "managers want...", but unless they are truly servants of evil, presumably it's done becuae they think it's what is wanted...
But qv my mini-rant on the rant thread, when announcements are percieved as being incorrect, they get ignored, which means an important announcement will be ignored too. Ditto the "no interchange at Bank", most people I know respond "lieing ****ers, I changed there this morning", so if it was genuinely shut for some reason, you'll still have the majority of commuters rocking up there
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 14, 2008 16:09:27 GMT
The customers who answer surveys and say that information isn't good enough? Because the things like service updates every four minutes are brought in because customers say they want them. At that frequency there is not much time for service control to react to reclassify the service (especially when dealing with the incident at the same time!) and station staff to react to a change of status (bearing in mind that the supervisor may well not be sitting next to his computer, or even in the same room as it). Within the company, it's the usual answer: every station *ought* to have a poster with details of how to contact the customer services department, as well as London TravelWatch. If you can't find it at your local station, ask the station staff or look on the TfL website's contacts page. Likewise, don't forget positive reinforcement: if there's a station which *does* generally keep on top of service status, puts out clear and accurate information during disruption, etc, then think about saying thank you in some way - it could be something as simple as letting a CSA know you appreciate the help.
|
|
|
Post by ducatisti on Aug 14, 2008 16:57:36 GMT
yeah - you are probably right. Mond you, I think the "more information" thing is a statistical wossname. I remember when out for a blast on the bike once I was accosted by a pollster asking about public transport in the Bewdley area. For some reason I replied "more information", when I should have not answered. I think "more information" can mean "ummm, no idea but I want to appear constructive/helpful". Or it can mean "more information that my train is on time" (ie I want my train on time). I also doubt very much people ask for "repeated recorded announcements that grate down one's spine after a few minutes..."
I *always* say thankyou to my local station staff. This may go some way to explaining why we had no difficulty photographing the special at West Finchley.
I shall try to get my finger out and respond.
I suspect everybody is simply trying to do the best they can, but that there's a logical flaw somewhere that gives funny outcomes.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 14, 2008 20:59:12 GMT
I suspect everybody is simply trying to do the best they can, but that there's a logical flaw somewhere that gives funny outcomes. As with a lot of things, you're relying on individuals (a large number of individuals in LU's case) to all work as a cohesive unit. Sometimes it works. Sometimes it doesn't. Stuff doesn't always go to plan, either, meaning you can give information in good faith only to have something unforeseen crop up. You've got an awful lot of steps where it can fall down: the Line Controller (and possibly signallers) have to deal with the incident and try to work out what the problem is, how to solve it, and how long it'll take to resolve. Line Information Assistants have to try to get the information out. That information has to be cascaded down to station staff by supervisors or control room assistants. And the information can be constantly changing during this - situations do not stay static. LU could probably do better - just as most companies could doubtless stand to improve in at least one area - but until telepathic communication is brought it, completely accurate information is never going to be 100% attainable. Connect radio can help - *if* used correctly - because there is a facility for group broadcasts. The intranet can be useful *but* most stations don't have someone constantly monitoring it because there are other things to do. The recorded service message takes a while to update (and relies on staff to call it). Service status messages are broadcast to the control room over a loudspeaker, but it can occasionally be hard to make out the information - and again, there will not always be someone in the control room at smaller stations, because the supervisor will be out attending to station checks and other such tasks. I've rambled! Sorry!
|
|
|
Post by superteacher on Aug 14, 2008 23:09:37 GMT
I suspect everybody is simply trying to do the best they can, but that there's a logical flaw somewhere that gives funny outcomes. As with a lot of things, you're relying on individuals (a large number of individuals in LU's case) to all work as a cohesive unit. Sometimes it works. Sometimes it doesn't. Stuff doesn't always go to plan, either, meaning you can give information in good faith only to have something unforeseen crop up. You've got an awful lot of steps where it can fall down: the Line Controller (and possibly signallers) have to deal with the incident and try to work out what the problem is, how to solve it, and how long it'll take to resolve. Line Information Assistants have to try to get the information out. That information has to be cascaded down to station staff by supervisors or control room assistants. And the information can be constantly changing during this - situations do not stay static. LU could probably do better - just as most companies could doubtless stand to improve in at least one area - but until telepathic communication is brought it, completely accurate information is never going to be 100% attainable. Connect radio can help - *if* used correctly - because there is a facility for group broadcasts. The intranet can be useful *but* most stations don't have someone constantly monitoring it because there are other things to do. The recorded service message takes a while to update (and relies on staff to call it). Service status messages are broadcast to the control room over a loudspeaker, but it can occasionally be hard to make out the information - and again, there will not always be someone in the control room at smaller stations, because the supervisor will be out attending to station checks and other such tasks. I've rambled! Sorry! A good summary of how complex things are, and few of us would disagree. In any large organisation, there are issues with passing on and cascading information down. The main gripe is keeping these "good service" messages playing when there clearly isn't a good service. If there is a good service, then nothing needs to be said. One thing is true - there may be more information given to passengers today than, say, 10 years ago. But the quality is some cases is worse. I remember when the Central line had issues in the early to mid 90's (a long story!), the information given at Bank eastbound about the service was much better. Announcements were made from the control room, reasons given for delays and so on. The announcements made were relevant, because they were specific to that location. Station supervisors do have access to the "line" radio channel, I'm sure. So as soon as they here of something that could affect the service at their station, they should announce it. Forget all these silly recorded announcements - they are just damaging LU's image. Passengers may have said that they wanted more information, but it's quality they want, not quantity.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 15, 2008 6:41:29 GMT
With regards to the radio: yes and no, from what I've observed - bearing in mind this is one station group on one line. Firstly, if they have it tuned to Line, they aren't then tuned to their own station - kinda pointless. They can set it so that the service controller interrupts their radio, but this isn't always much use - sometimes it 'sticks' to the controller's channel and if they need to put out a station message during the broadcast, they have to wait for the L/C to shut up because the radio is temporarily on his channel - likewise, they don't receive messages from their own staff until he's done. They could have a second radio tuned to service control, which some do, but at some stations there may not be a spare radio - Arnos was always a bad example of this, with some CSA's doing spare duties occasionally having to *share* a radio. Some stations may have a computer in the control room that can be left tuned to service control, but again that does require someone to be sitting there to listen to it. Bear in mind that Connect is actually still a work in progress so not all features are ready, working correctly, or even fully understood by all members of staff.
This comes down to the supervisor - see all the above comments about individuals, which were partly an attempt to answer this. Some of them will turn it straight off. Some of them won't. Sometimes it may be laziness, some of it may be that they're busy and out of the office - I'm sure we've had this discussion before - and a great many SS offices are (or are supposed to be!) kept locked, and/or the computer will be password protected, so it's not as easy as saying "Someone else should turn it off!". I know at stations where the message has been left, I've had access to the office, and the computer's been logged on, I have gone in and turned it off... but then I'm not on the gateline for five minutes or so, leaving plenty of opportunities for someone to get stuck in a gate or what-have-you and scream about there being no-one to help.
The trouble with this debate, from my point of view, is that it echoes the Oyster-is-rubbish one. We remember the bad examples because they stick in our minds. Commuters don't remember the dozens of journeys where nothing disrupted them - they remember the handful where things went wrong. A CSA can look at Oyster tickets and whine that they spent all day dealing with broken or malfunctioning cards and forget that countless people tapped in and tapped out with no trouble.
I'm conscientious, listen for the service updates over the train radio and, if we're approaching an interchange to an affected line, I make an announcement. I have no way of knowing if that information's correct - for all I know it's cleared up in the last five minutes, or worsened, or the line controller was bored and making stuff up. I simply pass it on in good faith. The station staff may give you other information, also in good faith. I don't think anyone deliberately sets out to misinform because, quite frankly, it's bloody pointless and makes our own lives harder...!
|
|
Dmitri
Posts: 750
Member is Online
|
Post by Dmitri on Aug 15, 2008 7:26:34 GMT
Just a note about how it is done in Moscow: 1) no announcements at all - normal operation (most of the time); 2) 'there are delays'; 3) 'no service'. Works pretty well. The truly amazing thing is he actually wants to go out with me again ;D You must be a very nice person .
|
|
|
Post by superteacher on Aug 15, 2008 8:38:55 GMT
I admit that yes, there are lots of journeys where no problem arises. I am actually someone who has stuck up for LU staff when passengers shout at them, because I know it's rarely that person's fault as an individual. I don't want LU to get slated, I am a big fan of the underground, and it does surprisingly well most of the time.
But let's get real - you are never going to be able to educate passengers. It is human nature to remember the few bad examples. But this "Good Service" lark is causing more problems, and in my opinion creates hassle for the staff at the front line.
Dmitri, the system in Moscow sounds spot on.
|
|