Previously, we covered trains and tracks, the two major reasons for the problems, not just in the Thames Valley region, but across the whole FGW network. Now we move to some of the other problems that impact your commuting lives.
I'm going to start with an issue that is wholly within FGW's control and for which there is no excuse. Strangely, the more bad press that FGW received, the more this issue seems to become aparent. The issue is, of course, staff shortages.
There are may delays that are caused by staff sickness, by them not turning up for work or by them being diaplaced because of earlier disruption. These delays are one of the biggest pains of all because they are largely avoidable. Unfortunately, FGW is not top of most people's list as a company to work for these days because you know that you're going to have a bad day. This ceates a lot of the problems. A lot of staff sickness is, I'm fairly sure, the result of people who realy don't want to get up, rolling over and thinking 'sod it' because they cant be bothered to deal with the grief. I have days like that and I'm not on the front line dealing with people every minute that I'm at work.
Owing to the fact that FGW is not a popular company to work for, they are having trouble with both staff recruitment and staff retention. Even the most saintly of people gets tired of having people yell at them all day sooner or later and they move on to a more fulfilling career. This problem on the part of FGW is not one that should be passed to the customer, but sadly it largely is. If there is sickness and there are crew in the facility, they can take the train onwards, provided they are not on a mandated rest break. Often, however, there are no crew who could be got to the station in time to make the train worth running and so it is cancelled.
FGW is currently understaffed. In fact I believe that I am correct in stating that there is a nationwide shortage of rail staff. FGW offers good renumeration to its staff by and large. A fully qualified train driver (the bigest shortage) can earn £40,000. A trainee driver can walk off the street on £20,000. The problem is that most people are looking for a certain level of job satisfaction and they don't tend to get it in the current environment of FGW. Morale is low, but I think you guys alreay guessed that.
FGW obviously has ownership of this and it's my opinion that this problem is a symptom of other problems and, were things to get better on the railway, the staf would come back and there would be less of these types of problems. I know that FGW is currenbtly undergoing a recruitment drive to get people to come and work for them and you can't really ask them to do more in terms of providing numbers. However, I do thk that they could put more thought into the deployment of standby crew, based on trends of where the majority of delays of this type come in, (which, incidentally, seem to be the ex-Wessex line from Cardiff to Portsmouth). That also provides a neat segue into my next point, fuzzy thinking.
FGW has some very bright people working for it. It'sjust a shame that most of those poeple are not in positions of power. In my previos post on the nonsense surrounding claims ofr the disruption caused by the July floods, I went into some detail about the fuzy thinking mployed by FGW at times, but it is not just limited to customer service. Some of the decisions that have been made in the past, particularly regarding the management of disruption have been ludicrous. Some delays are unavoidable, this is true, but if there was a consistent, clear plan in place for the basic management of disruption, then delays would decrease. It seem sometimes as though FGW forget everyhing they learned the last time there as a big problem and just start fom scratch as to the best way to get out of whatever mess they are in. I'm sure you can all think of plenty of examples of this yourselves.
To be fair this is not all FGW's issue. We come back to our old friends NR for part of this. When there is a problem such as aisgnal failure and trains cannot get thourhg the blacked area, there is congestion and queues. When (if) the problem is repaired, it is not FGW that gets the final say on which train move first. We have an input certainly, but NR, as the owner of the track and controller of the signals, decides on movement priorities and which trains go first. I think FGW should take more of a stand on what they want to se move, but semtimes I do not feel that that would do much good, as neither organisation seems to be able to think clearly about what would be the best way to get the trains moving again and they seem to change their minds form train to train about what to do.
To give credit where it is due, I have at times, been so impressed with FGW's response to problems. I would cite Ufton Nervet as an example. The last major train crash a couple of years ago. I'm sure some of you remember it. I was in the office until mdnight on the day that happened and the following day from 7am to 8pm. I saw the whole handlingof the incident unfold and I spoke to many of the families of peope who had been on that train. Then I went and got very drunk, but it staggers me that if FGW can do it right then, why do they have such a problem doing it right at other times?
I'm afraid that I can't answer that, nor can I really provide any real insight on what it would take to fix this nagging difficulty. The idea that most immediately springs to mind is get rid of NR and give the train companies back their infrastructure. Then put some semblance of operational control back with the staff in the scene. Let the drivers clip points in the case of failures rather than have to call out an NR manager from God-knows-where. Let FGW decide on their own train priorities after disruption. That would make things better. Of course, it would also help if their were people in direct, operational control who learned from past insnaces, knew the pitfals of doing certain thigs and were able to get things running smothly, quickly. That, however, may be wishful thinking.
The final category of problem realy, are miscellaneous delays. Those are delays that are largely unavoidable, within no-one's control and the only thing that can really be done about them is to try and mitigate the effects (see above).
These are things like bad weather, fallen trees and other blockages, vehicles striking rail bridges, leaves on the line, lineside fires, vandalism, earthslips and, of course, fatalities. Before I get to these, I'm taking the opportunit to rant for a bit about two of the biggest railway jokes in existance, leaves on the line and the wrong type of snow. Everybody has a good chortle at these, but they are actually genuine problems.
Snow first. Whoever came out with that wrong snow line needs to be shot. I bet he feels bad now. However, I will now explain this and it may help fo those of you who haven't heard it before. There are, in fact, many types of snow. The one that causes the problem for the railways is the snow that is formed of large ice crystals. When this type of snow hits the rails, instead of just melting like snow formed of smaller crystals, it tends to form a layer of frost on the rails which makes them slippery and causes delays because all trains have to proceed under EROS (Emergency Restriction of Speed). So, although it was worded very badly, there is actually a wrong type of snow, so maybe we can all get over the joke now.
Leaves are another one that everybody likes to scoff at. Well, allow me to retort. When leaves land on the line, and this usually happens in wet weather, they tend to stick. When many tons of train goes over the leaves, it crushes them and the break down and forma slippery, resin-like coating on the rails. It's been described, more or less accurately, as the rail equivalent of black ice. Again, this means speed restricions. So, we can put that joke to bed now as well. Rant over.
Fatalities are the main problem as far as external delays go. Not so much because of their number, although it is depessingly high, but because of the amount of disruption they cause when they do happen. The police have to come to the scene and it has to be investigated to make sure that it was a suicide and then the coroner has to be called for the body. As unsavouray as it siunds, in mnay cses they have to make sure they have all the pieces. Then NR have to come out and inspect the track and make sure there is no structural damage. Then they have to clean the track. More often than not, we have to get a replacement driver to take the train onwards, as the old driver, understandably, usually does not feel up to it. This can take many, many hours, depending on how far everybody has to come.
Bridge strikes are another common one. They can take many hours to resolve, as wherever a road vehicle hits a rail bridge, the full bridge inspection team have to come out and go over every inch of the bridge to make sure that is is still structurally sound before they let the trains move again.
When there are lineside fires, depending on where the fire is, there may be an exclusion zone surrounding the track that trains cannot go through, earthslips and line obstructions have to be cleared.
These are all delays that no-one can really take ownership of as there are no real preventative measures than can be taken to stop them ocurring. However, what we can do, is make the impact of these delays less hard felt and that does require getting the house in order.
It's a depressing picture I know and I hope that I have been able to give some idea of the sher scale of the task that faces, not just FGW, but the UK rail network as a whole. I'm gonna leave this a couple of days to give people a chance to add their thoughts and then we'll have a big follow up and address the issues that arise out of this. Also, pardon my spelling in this post, I know it's crap.
See y'all soon.
Peace
Monday, 3 September 2007
Saturday, 1 September 2007
Reader Mail IV (The Crux of the Matter)
I was looking for something to post on but I couldn't decide on a subject. So I was, in the interest of balancing things, going to post part 2 of my criticisms of FGW. However, upon checking the comments to my last post, which I hope you all enjoyed, I came across a lengthy comment from Brian. He posed the question:
'So Insider what are the root causes of the poor peak hours service between Slough-Paddington and back, and who owns the actions to sort them?'
Bloody good question that, isn't it? Handily, it also solves my dilemma on what to post about.
So here we go. This is likely to be a long one and it may be in several parts. It may also cover ground I've already posted about, but never mind. It may also come across as bitter in places and it's quite likely that many of you with disagree with at least some parts of what I have to say. Although the focus of Brian's question is on Slough-Paddington, a lot of what I'm going to write can be juxtaposed to the rest of the network. also, any rail jargon will be explained. So, lengthy preamble over, let's get to the good bit.
A lot of people have said that a railway is an unsuitable thing for a private company to run, owing to the tendency to put profit before service. To a certain extent, this is true. However, British Rail, in the 'goold old days' of nationalisation was not in it simply to get you guys from A to B. They were in it to make money. Only they were making it for the government, rather than shareholders. Governments like money, they have so many things they can waste it on.
British Rail did not have hugely expensive fares, a major critisism of FGW. Granted, they did not have to pay the Government £1.2bn for the priviledge of a crappy service specification, but that's by the by. British Rail fares were controlled by the Government, so in order to be profitable, and to have some cash for investment, they had to find ways of reducing costs. Luckily, there was a very handy way to do this. British Rail was responsible for its own track, there was no Network Rail. So British Rail decided that one handy way to save money was not to bother with any of this silly track maintenance rubbish and to only fix things when they broke. Granted, when things did break, they were a lot more efficient at fixing them than Network Rail, but there was very little routine upgrading.
When privitisation came along, the track was old. Old and clapped out. Ever wonder why there is so much engineering work-related disruption. It's because now, it has to be done. We have reached a critical point. The track is too old and too fragile to sustain the number of trains that pass over it. There is too much ground to cover for proper maintenance. By the time one thing has been fixed, something else has gone wrong. The only way to bring everything up to code would be to shut down the railway and replace the track. Trust me on this. There is no 'yeah, but we could do this....', it's fact.
Another fact is that, were the track up to scratch, the number and length of delays that you suffer would half on average. In the Thames Valley, your delays would on average, be reduced by 66%.
Journey times have lengthened over th period of privatisation. Want to know why? Mostly, it's because you can now make very few journeys throughout the FGW region without at least part of that journey being covered by a 50mph speed restriction. This is because..... wait for it... oh yes, the track is too knackered to be able to stand trains traveling over it at a higher speed, and NR is too overworked to have got round to sorting that particular bit yet.
Don't get me wrong here, I don't blame NR for this. I blame British Rail and the governmental overseers who let them get away with it and demanded a profit without any allowance for improvements or any cash investment of their own. This is why it irks me so much when people say how great things were under British Rail. May be so, but the company you are heaping praise on is a large reason why things suck now.
To relate this specifically to Slough, I've drawn you a piccy. Well, that's not true, I just borrowed it from my files. Here it is:

It's not very clear and I apologise. You may need to save to your computer and enlarge it to see it properly. Don't worry, it's ok to do this. What the picture shows is the main approach into Paddington. In the red circle is a set of points, known as Airport Junction. They are moved 8 times every hour and are the longest points, certainly in the country, possibly the world, but don't quote me on that.
Last year, they failed a total of 46 times or, to put it another way, once every 8 days. Pretty crappy right? Also causes a great deal of problems and it a major contributor to the delays suffered by commuters and everyone else as well. It's the biggest problem area in the Thames Valley, but it's not the only one.
As to who takes ownership of this. Well that would be Network Rail, but they really are fighting a losing battle and this is a very tricky problem to fix totally. There is a plan in place to totally renew the Airport Junction points in the near future, which should help with major delays, but there will always be the niggling delays. Minor signal problems, track circuit failures, speed restrictions and other stuff like that will continue to be a problem for many years to come, especially as NR hasd a whole country to worry about.
Of course, this is not just an excercise in bashing NR. If 50% of the delays come from NR, then 50% of the delays must come from somewhere else. That would be where FGW comes in. The main contributor to FGW's side of this sorry story would be the trains. I was on the 'More Train Less Strain' site the other day. Aside from the fact that I consider their ethos to be totally counterproductive and that they do not help the situation at all, (We got everyone to go on a fares strike. Whoop-de-doo, aren't we big and clever.) there are some glaring errors in their site. There mission statement for example. They state that 'FGW has no trains less than 20 years old and some close to 30.' Thats a very strong statement and would lend credence to their argument, if we ignore that inconvenient fact about the Adelantes that entered service in 2004 making them... let's see... yep, 3 years old. (Please forgive my sarcasm. Although I am, by nature, incredibly sarcastic, I try to keep it out of this blog). I'm not counting the Desiros that run the Heathrow Connect service.
The point that they are trying to make, I think, is that FGW trains are old. A fair point. They are. This does lead them to be more prone to mechanical failure. Mechanical failure is a big cause of delays. Not just what we think of as failure i.e. the train breaking down. Trains are actually ridiculously safe and there is a whole list of things that can lead to a train being declared as a failure. For example, a non-functioning windscreen wiper. Get one of them and the train in unsafe to run, rain or not. That means that the train doesn't run and you're all left on the platform. To a cterina extent, it makes me understand why information is withheld. If an announcement came out at Reading that a train wasn't running because one of its windscreen wipers wasn't working, to quote somebody, I predict a riot.
The fact is that the trains do suffer mechanical failures fairly often. These do not always requre the train to be cancelled. Sometimes they just cause delays. If there is a fitter nearby who can fix the problem quickly, the train can go about its business. A problem such as loss of power in the engine will not require a cancellation, but will slow the train down, giving the infamous crawling journey.
Obviously, FGW has to take ownership of this. The recent refit of the HSTs has helped a lot. Whatever people think of the paint job, the new seats or anything else, what the trains did get was a new engine and a complete refurbishment of the mechanical and electrical components on the trains. They are, now that the kinks have been ironed out, much more reliable than the trains that have not had this treatment. Having said that, the HST, despite its age, still remains one of the most reliable trains in the UK and boasts a better record that Virgin's famed Pendelinos. This is why Arriva trains were trying to source some in the event that Virgin refuse to lease them thier existing stock for the new Cross Country franchise.
However, it is not just HSTs that run on the Thames Valley line, or across the network as a whole. FGW also has many of the smaller trains, the 158s, 165s and 166s and also the 150s and 143s that cover the ex-Wessex lines.
These trains are smaller, not necessarily older, but certainly less well made, and are more prone to all types of problems. They need a refit at the very least and replacement at the very best. There is a refurbishment plan in place for the turbo trains once the HST refit is done and this will take place next year. They will be overhauled and given new engines, which should take care of a lot of these problems but they will still be old.
As mentioned, the ideal solution would replacement of FGW's entire fleet and bringing in new trains. This is easier said than done. A quick scan of the rolling stoc of most companies relveals that there is not that much new stock kicking around. If a train company wants new trains, they pretty much have to comission them and have them built new a la Virgin. FGW have been working on a new train called the HS2 with Siemens but it is still on the drawing board and has ben for about 4 years. Bringing in new trains is a long terms solution and it costs a lot of money (although less in the long run than constant maintenance on the existing fleet). I mentioned in a previous post about the short length of franchises being counterproductive to long term thinking
and that is certainly a consideration here. FGW have no wish to spend many years and a lot of money bringing in a whole new set of trains that they will never get to use because they lose the franchise. However, this is not really a choice any more and it has to be done. I think that £1.2 bn that we're paying the DfT would be well spent in this regard and some real progress could be made, but funds are not exactly in abundance at present, whatever you may think of FGW's fare structure.
OK, part 1 done. We've covered tracks and trains, the biggies. Next, we'll look at staffing problems, fuzzy thinking and miscellaneous delays. Then, to avoid me getting sidetracked, I'll do a follow up and answer the inevitable questions. Right now, my head is too messed up to think properly. I'm still recovering from Friday night.
Till the next time.
'So Insider what are the root causes of the poor peak hours service between Slough-Paddington and back, and who owns the actions to sort them?'
Bloody good question that, isn't it? Handily, it also solves my dilemma on what to post about.
So here we go. This is likely to be a long one and it may be in several parts. It may also cover ground I've already posted about, but never mind. It may also come across as bitter in places and it's quite likely that many of you with disagree with at least some parts of what I have to say. Although the focus of Brian's question is on Slough-Paddington, a lot of what I'm going to write can be juxtaposed to the rest of the network. also, any rail jargon will be explained. So, lengthy preamble over, let's get to the good bit.
A lot of people have said that a railway is an unsuitable thing for a private company to run, owing to the tendency to put profit before service. To a certain extent, this is true. However, British Rail, in the 'goold old days' of nationalisation was not in it simply to get you guys from A to B. They were in it to make money. Only they were making it for the government, rather than shareholders. Governments like money, they have so many things they can waste it on.
British Rail did not have hugely expensive fares, a major critisism of FGW. Granted, they did not have to pay the Government £1.2bn for the priviledge of a crappy service specification, but that's by the by. British Rail fares were controlled by the Government, so in order to be profitable, and to have some cash for investment, they had to find ways of reducing costs. Luckily, there was a very handy way to do this. British Rail was responsible for its own track, there was no Network Rail. So British Rail decided that one handy way to save money was not to bother with any of this silly track maintenance rubbish and to only fix things when they broke. Granted, when things did break, they were a lot more efficient at fixing them than Network Rail, but there was very little routine upgrading.
When privitisation came along, the track was old. Old and clapped out. Ever wonder why there is so much engineering work-related disruption. It's because now, it has to be done. We have reached a critical point. The track is too old and too fragile to sustain the number of trains that pass over it. There is too much ground to cover for proper maintenance. By the time one thing has been fixed, something else has gone wrong. The only way to bring everything up to code would be to shut down the railway and replace the track. Trust me on this. There is no 'yeah, but we could do this....', it's fact.
Another fact is that, were the track up to scratch, the number and length of delays that you suffer would half on average. In the Thames Valley, your delays would on average, be reduced by 66%.
Journey times have lengthened over th period of privatisation. Want to know why? Mostly, it's because you can now make very few journeys throughout the FGW region without at least part of that journey being covered by a 50mph speed restriction. This is because..... wait for it... oh yes, the track is too knackered to be able to stand trains traveling over it at a higher speed, and NR is too overworked to have got round to sorting that particular bit yet.
Don't get me wrong here, I don't blame NR for this. I blame British Rail and the governmental overseers who let them get away with it and demanded a profit without any allowance for improvements or any cash investment of their own. This is why it irks me so much when people say how great things were under British Rail. May be so, but the company you are heaping praise on is a large reason why things suck now.
To relate this specifically to Slough, I've drawn you a piccy. Well, that's not true, I just borrowed it from my files. Here it is:
It's not very clear and I apologise. You may need to save to your computer and enlarge it to see it properly. Don't worry, it's ok to do this. What the picture shows is the main approach into Paddington. In the red circle is a set of points, known as Airport Junction. They are moved 8 times every hour and are the longest points, certainly in the country, possibly the world, but don't quote me on that.
Last year, they failed a total of 46 times or, to put it another way, once every 8 days. Pretty crappy right? Also causes a great deal of problems and it a major contributor to the delays suffered by commuters and everyone else as well. It's the biggest problem area in the Thames Valley, but it's not the only one.
As to who takes ownership of this. Well that would be Network Rail, but they really are fighting a losing battle and this is a very tricky problem to fix totally. There is a plan in place to totally renew the Airport Junction points in the near future, which should help with major delays, but there will always be the niggling delays. Minor signal problems, track circuit failures, speed restrictions and other stuff like that will continue to be a problem for many years to come, especially as NR hasd a whole country to worry about.
Of course, this is not just an excercise in bashing NR. If 50% of the delays come from NR, then 50% of the delays must come from somewhere else. That would be where FGW comes in. The main contributor to FGW's side of this sorry story would be the trains. I was on the 'More Train Less Strain' site the other day. Aside from the fact that I consider their ethos to be totally counterproductive and that they do not help the situation at all, (We got everyone to go on a fares strike. Whoop-de-doo, aren't we big and clever.) there are some glaring errors in their site. There mission statement for example. They state that 'FGW has no trains less than 20 years old and some close to 30.' Thats a very strong statement and would lend credence to their argument, if we ignore that inconvenient fact about the Adelantes that entered service in 2004 making them... let's see... yep, 3 years old. (Please forgive my sarcasm. Although I am, by nature, incredibly sarcastic, I try to keep it out of this blog). I'm not counting the Desiros that run the Heathrow Connect service.
The point that they are trying to make, I think, is that FGW trains are old. A fair point. They are. This does lead them to be more prone to mechanical failure. Mechanical failure is a big cause of delays. Not just what we think of as failure i.e. the train breaking down. Trains are actually ridiculously safe and there is a whole list of things that can lead to a train being declared as a failure. For example, a non-functioning windscreen wiper. Get one of them and the train in unsafe to run, rain or not. That means that the train doesn't run and you're all left on the platform. To a cterina extent, it makes me understand why information is withheld. If an announcement came out at Reading that a train wasn't running because one of its windscreen wipers wasn't working, to quote somebody, I predict a riot.
The fact is that the trains do suffer mechanical failures fairly often. These do not always requre the train to be cancelled. Sometimes they just cause delays. If there is a fitter nearby who can fix the problem quickly, the train can go about its business. A problem such as loss of power in the engine will not require a cancellation, but will slow the train down, giving the infamous crawling journey.
Obviously, FGW has to take ownership of this. The recent refit of the HSTs has helped a lot. Whatever people think of the paint job, the new seats or anything else, what the trains did get was a new engine and a complete refurbishment of the mechanical and electrical components on the trains. They are, now that the kinks have been ironed out, much more reliable than the trains that have not had this treatment. Having said that, the HST, despite its age, still remains one of the most reliable trains in the UK and boasts a better record that Virgin's famed Pendelinos. This is why Arriva trains were trying to source some in the event that Virgin refuse to lease them thier existing stock for the new Cross Country franchise.
However, it is not just HSTs that run on the Thames Valley line, or across the network as a whole. FGW also has many of the smaller trains, the 158s, 165s and 166s and also the 150s and 143s that cover the ex-Wessex lines.
These trains are smaller, not necessarily older, but certainly less well made, and are more prone to all types of problems. They need a refit at the very least and replacement at the very best. There is a refurbishment plan in place for the turbo trains once the HST refit is done and this will take place next year. They will be overhauled and given new engines, which should take care of a lot of these problems but they will still be old.
As mentioned, the ideal solution would replacement of FGW's entire fleet and bringing in new trains. This is easier said than done. A quick scan of the rolling stoc of most companies relveals that there is not that much new stock kicking around. If a train company wants new trains, they pretty much have to comission them and have them built new a la Virgin. FGW have been working on a new train called the HS2 with Siemens but it is still on the drawing board and has ben for about 4 years. Bringing in new trains is a long terms solution and it costs a lot of money (although less in the long run than constant maintenance on the existing fleet). I mentioned in a previous post about the short length of franchises being counterproductive to long term thinking
and that is certainly a consideration here. FGW have no wish to spend many years and a lot of money bringing in a whole new set of trains that they will never get to use because they lose the franchise. However, this is not really a choice any more and it has to be done. I think that £1.2 bn that we're paying the DfT would be well spent in this regard and some real progress could be made, but funds are not exactly in abundance at present, whatever you may think of FGW's fare structure.
OK, part 1 done. We've covered tracks and trains, the biggies. Next, we'll look at staffing problems, fuzzy thinking and miscellaneous delays. Then, to avoid me getting sidetracked, I'll do a follow up and answer the inevitable questions. Right now, my head is too messed up to think properly. I'm still recovering from Friday night.
Till the next time.
Thursday, 23 August 2007
Reader Mail Vol III (The Wide World of Tickets)
Firstly, I would like to welcome the newest member of staff at In defence of First Great Western. My flatmate, who has now been press-ganged into bringing me toasted sandwiches while I write these. Let's have 0.5 secs silent contemplation of the hard work that he does.
This edition of reader mail is devoted to Tim and his comments on tickets in response to my last post. They can be found here. (Scroll way down). Lets go to the questions.
1. Off peak season tickets. Interesting question. It is true that regular season tickets are relatively cheap and a lot better option if you travel regularly. The fact that they are valid at any time also sweetens the deal (if you fancy travelling the route to work on yourday off) and that is one reason why they are not offered. The other reason is that there is little demand for them. There are not many customers who ravel regularly enough to make a season ticket worthwhile but make all their journeys off-peak. Season tickets are aimed at the commuter market and there aren't that many with a nice enough work schedule that they can avoid rush hour entirely.
2. Off peak returns. The official explanation for this ones that the return portion of the ticket s heavily discounted in order to encourage people to make both legs of their journey with us. Personally, I do not see the logic as the price difference is usually 10p and it costs more than that to take a passenger on a journey. I suppose it can help to develop loyalty and stop people straying to coaches but that only really works if the journey goes well. I think it is more likely that people would not be willing to pay twice the price of an off-peak single for a return ticket and reducing the single price so that a double price return would be reasonably priced is not cost effective.
3. Off-peak singles. That is a good point and was one of the thoughts behind making the new range of advcance pircahse fares single only. This allowed people to mix and match their tickets and also, if they could only get a coach on one leg, it discouraged them from getting the coach on both legs because all the single tickets were prohibatively priced.
There is a problem as you point out in that these advance purchase fares are not offered on all journeys and with the rail-link coach, only returns are offered (on the theory that if you go to an airport, sooner or later, you'll be coming back). I agree that there are a multitude of situations where an off peak single that was half the price of the return would be useful but again, it somes down to money.
With peak time returns, the single is, of course, half the price of the return, because the amount of money involved is larger. It would not make sense to have a standard open return 10p more than a single. Nor would people stand for having a single 10p less than the current return price. In addition to that, we like to encourage people out of the peak times, so making the single half the return encourages them to only go peak one way if that's all they need.
Good points there and I hope the answers helped. I will see if I can bring the points on off-peak singles to the attention of those who make such decisions and we may be able to get somehting done for the future.
This edition of reader mail is devoted to Tim and his comments on tickets in response to my last post. They can be found here. (Scroll way down). Lets go to the questions.
1. Off peak season tickets. Interesting question. It is true that regular season tickets are relatively cheap and a lot better option if you travel regularly. The fact that they are valid at any time also sweetens the deal (if you fancy travelling the route to work on yourday off) and that is one reason why they are not offered. The other reason is that there is little demand for them. There are not many customers who ravel regularly enough to make a season ticket worthwhile but make all their journeys off-peak. Season tickets are aimed at the commuter market and there aren't that many with a nice enough work schedule that they can avoid rush hour entirely.
2. Off peak returns. The official explanation for this ones that the return portion of the ticket s heavily discounted in order to encourage people to make both legs of their journey with us. Personally, I do not see the logic as the price difference is usually 10p and it costs more than that to take a passenger on a journey. I suppose it can help to develop loyalty and stop people straying to coaches but that only really works if the journey goes well. I think it is more likely that people would not be willing to pay twice the price of an off-peak single for a return ticket and reducing the single price so that a double price return would be reasonably priced is not cost effective.
3. Off-peak singles. That is a good point and was one of the thoughts behind making the new range of advcance pircahse fares single only. This allowed people to mix and match their tickets and also, if they could only get a coach on one leg, it discouraged them from getting the coach on both legs because all the single tickets were prohibatively priced.
There is a problem as you point out in that these advance purchase fares are not offered on all journeys and with the rail-link coach, only returns are offered (on the theory that if you go to an airport, sooner or later, you'll be coming back). I agree that there are a multitude of situations where an off peak single that was half the price of the return would be useful but again, it somes down to money.
With peak time returns, the single is, of course, half the price of the return, because the amount of money involved is larger. It would not make sense to have a standard open return 10p more than a single. Nor would people stand for having a single 10p less than the current return price. In addition to that, we like to encourage people out of the peak times, so making the single half the return encourages them to only go peak one way if that's all they need.
Good points there and I hope the answers helped. I will see if I can bring the points on off-peak singles to the attention of those who make such decisions and we may be able to get somehting done for the future.
Thursday, 16 August 2007
It's All Gone Quiet At The Front
Apologies for my absence blog fans. I regret that I have been out of the country (well, in Bristol, but that might as well be another planet to me) with little time to do anything other than explain exactly what libel means and chip in a bit with the promise of this post.
Since my last post, you've been letting me know about how horrible things were last Saturday night and I do sympathise. Ollie has helped me out in my absence with a bit of info and he is right again but the core of the problem seems to be lack of and incorrect info.
This is not a new story. In fact, I would go so far as to say that it is FGW's biggest failing among things that they have total control over. Well that's not really fair. They have total control over how they disseminate the information but not always total control over what information is available.
I'll give you an example of this. Remember back on 2 July when the lightnig hit the signals and everybody was stranded. There were a whole lot of complaints that customers were not being kept up to date and staff could not tell them what was best to do. Problem is, the staff weren't being kept up to date and they didn't know the best thing to do. As you all know, Network Rail fix the signals and they provide FGW with info on how it's going and timescales and all that jazz. Or, at least, they are supposed to. They very often don't.
Staff don't know what is happening. They can't tell customers when the problem is likely to be fixed. They don't want to tell customers to go to Waterloo and get a SW train to Reading if the problem is going to be fixed in 20 minutes so they say nothing for fear of saying the wrong thing and get labeled (unfairly I feel) as unhelpful and uncommunicative. Your experience Tim, is an example of when staff have guessed and been wrong and subsequently looked bad.
Yes FGW should and do push Network Rail for updates but if they won't tell, we can't make 'em. I think maybe we should consider station announcements to say 'Sorry you're delayed. We'd like to tell you what's going on but Network Rail won't tell us. Sorry.'
Some of the time, you can substitute Network Rail for another TOC or an external organisation, like the Coroner in the case of fatality or the Fire Department in the case of, well, a fire. So next time, you're stuck at a station and the train is delayed, and you don't know what's happening, think about why you might not know.
Of course, that is not to say that FGW is totally faultless. When customers are not even told what is wrong, that is inexcusable because that is easy to find out. Control know what has happened and one quick phone call from a station and Control will tell them, it comes up on the tracking system. Sometimes, staff do know what is happening and don't tell people.
Sometimes, this is laziness on the part of the staff. Sometimes, it is fear. I know that I would not really want to face the whole of Paddington station, full of commuters and have to tell them that they aren't going anywhere for 3 hours. It's easy to say to the staff that customers will be less angry knowing than not knowing but it seems like a different story when you're the poor sod who has to do the telling. (I've done both parts of it, so I can sympathise). Ditto for Train Managers.
Sometimes TMs will deliberately keep passengers in the dark or lie to them. Not very ethical, I know, but long experience has shown us that if a TM announces a fatality or a fire or something like that, it sprks panic in some and a morbid curiosity in others. Either way, not something you want to have to deal with.
This applies to 'on the spot' information, but, of course, there are many other types. Like advance information on cancellations and changes to the timetable, as Tim and jp mentioned. There is no excuse for not providing this information. It's available, all stations get it, hard copies and pager messages.
I personally think that it should all be displayed on large posters so that there is absolutely no doubt about what is going on. I also think that we should go back to the paper copies of amended timetables that were in the station info racks. They were great and very useful.
I appreciate the fact that knowing what is going on and an approximate timescale can mitigate the frustration of a delay just a little and I think that FGW staff do appreciate it too and they get just as frustrated when they don't know and can't help, not least because they have a station full of people yeling at them.
To answer Tim, the staff on the Customer Service booth are not usually a different grade than the staff under the departure boards unless someone is filling in, but the staff at the booth tend to get a more varied line of questioning and the departure board staff get a little jaded, I think, at being asked the same thing all day.
That's my take on information. There's more but most of it is tangents and a bit rambling. So, to keep a bit more focused, I'll open this up to questions from the floor.
Since my last post, you've been letting me know about how horrible things were last Saturday night and I do sympathise. Ollie has helped me out in my absence with a bit of info and he is right again but the core of the problem seems to be lack of and incorrect info.
This is not a new story. In fact, I would go so far as to say that it is FGW's biggest failing among things that they have total control over. Well that's not really fair. They have total control over how they disseminate the information but not always total control over what information is available.
I'll give you an example of this. Remember back on 2 July when the lightnig hit the signals and everybody was stranded. There were a whole lot of complaints that customers were not being kept up to date and staff could not tell them what was best to do. Problem is, the staff weren't being kept up to date and they didn't know the best thing to do. As you all know, Network Rail fix the signals and they provide FGW with info on how it's going and timescales and all that jazz. Or, at least, they are supposed to. They very often don't.
Staff don't know what is happening. They can't tell customers when the problem is likely to be fixed. They don't want to tell customers to go to Waterloo and get a SW train to Reading if the problem is going to be fixed in 20 minutes so they say nothing for fear of saying the wrong thing and get labeled (unfairly I feel) as unhelpful and uncommunicative. Your experience Tim, is an example of when staff have guessed and been wrong and subsequently looked bad.
Yes FGW should and do push Network Rail for updates but if they won't tell, we can't make 'em. I think maybe we should consider station announcements to say 'Sorry you're delayed. We'd like to tell you what's going on but Network Rail won't tell us. Sorry.'
Some of the time, you can substitute Network Rail for another TOC or an external organisation, like the Coroner in the case of fatality or the Fire Department in the case of, well, a fire. So next time, you're stuck at a station and the train is delayed, and you don't know what's happening, think about why you might not know.
Of course, that is not to say that FGW is totally faultless. When customers are not even told what is wrong, that is inexcusable because that is easy to find out. Control know what has happened and one quick phone call from a station and Control will tell them, it comes up on the tracking system. Sometimes, staff do know what is happening and don't tell people.
Sometimes, this is laziness on the part of the staff. Sometimes, it is fear. I know that I would not really want to face the whole of Paddington station, full of commuters and have to tell them that they aren't going anywhere for 3 hours. It's easy to say to the staff that customers will be less angry knowing than not knowing but it seems like a different story when you're the poor sod who has to do the telling. (I've done both parts of it, so I can sympathise). Ditto for Train Managers.
Sometimes TMs will deliberately keep passengers in the dark or lie to them. Not very ethical, I know, but long experience has shown us that if a TM announces a fatality or a fire or something like that, it sprks panic in some and a morbid curiosity in others. Either way, not something you want to have to deal with.
This applies to 'on the spot' information, but, of course, there are many other types. Like advance information on cancellations and changes to the timetable, as Tim and jp mentioned. There is no excuse for not providing this information. It's available, all stations get it, hard copies and pager messages.
I personally think that it should all be displayed on large posters so that there is absolutely no doubt about what is going on. I also think that we should go back to the paper copies of amended timetables that were in the station info racks. They were great and very useful.
I appreciate the fact that knowing what is going on and an approximate timescale can mitigate the frustration of a delay just a little and I think that FGW staff do appreciate it too and they get just as frustrated when they don't know and can't help, not least because they have a station full of people yeling at them.
To answer Tim, the staff on the Customer Service booth are not usually a different grade than the staff under the departure boards unless someone is filling in, but the staff at the booth tend to get a more varied line of questioning and the departure board staff get a little jaded, I think, at being asked the same thing all day.
That's my take on information. There's more but most of it is tangents and a bit rambling. So, to keep a bit more focused, I'll open this up to questions from the floor.
Friday, 10 August 2007
TFI Friday
So tired. Horrible day today. Normally I do like to go through all the new comments and answer them but right now I'm just not in the mood.
As I'm sure many of you know, there was a signal failure at West Drayton today. Not a particularly interesting one again. Of more interest was the signal problem in South Wales around Bridgend. It didn't interest me at first, but on a whim I decided to go into the TRUST system and have a squint at some of the trains that were being delayed as the length of the delays to trains coming out of Wales was becoming a concern.
My interest was peaked when I saw the following: XR CABLE CUT next to the delays. XR is a delay attribution code and stands for 'External Reason'. Oh yes, it was vandalism. Someone had taken the time and trouble to come and fuck up the signals (pardon the venacular) for jollies.
That so rags me off. Can't people find anything better to do???
I will take this time to answer Lee regarding turbos. There may be some pacers heading our way but nothing is confirmed as of yet. With regards to the turbos, we get to keep all the 165s and 166s from the Reading fleet but we are losing approximately 9 complete 158 sets from the ex-Wessex fleet. Supposedly, we will be getting somehting to replace them (maybe from those 1300 carriages the DfT has ordered) but again, nothing is confirmed. Not much help I know but it's all abit up in the air at the moment.
That's all for now. Back soon.
As I'm sure many of you know, there was a signal failure at West Drayton today. Not a particularly interesting one again. Of more interest was the signal problem in South Wales around Bridgend. It didn't interest me at first, but on a whim I decided to go into the TRUST system and have a squint at some of the trains that were being delayed as the length of the delays to trains coming out of Wales was becoming a concern.
My interest was peaked when I saw the following: XR CABLE CUT next to the delays. XR is a delay attribution code and stands for 'External Reason'. Oh yes, it was vandalism. Someone had taken the time and trouble to come and fuck up the signals (pardon the venacular) for jollies.
That so rags me off. Can't people find anything better to do???
I will take this time to answer Lee regarding turbos. There may be some pacers heading our way but nothing is confirmed as of yet. With regards to the turbos, we get to keep all the 165s and 166s from the Reading fleet but we are losing approximately 9 complete 158 sets from the ex-Wessex fleet. Supposedly, we will be getting somehting to replace them (maybe from those 1300 carriages the DfT has ordered) but again, nothing is confirmed. Not much help I know but it's all abit up in the air at the moment.
That's all for now. Back soon.
Thursday, 9 August 2007
Tickets and Fares
My last post on fares got quite a buzz going and JP asked the question about why combination tickets can often be cheaper than a straight-through fare and why staff do not make this known to customers. So I will try and answer these questions here today.
Firstly, we need to set a background. The UK rail network fare structure, at its core, is infinitely complex. It's even more complex than the issue of actually running the trains. I got my start in the railway industry working for a certain organisation now residing somewhere in Bangalore. As we dealt with the entire country rather than just FGW, I got to know a lot about the UK fares structure. At one point during my tenure, it was estimated that, when you took into account AP fares, promotional tickets and each TOCs particular quirks, there were somewhere in the region of 10,000 distinct ticket types. I don't know how true this is and I'm not sure I want to, but it gives you an idea of how a big a scale we're dealing with. The idea is to not pass on too much of this complexity to the customer, but behind the scenes, it's a different story.
What we also have to take into account is that rail fares are not just priced on distance. If they were, things would be much easier. Routes are also priced on usage. A ticket from point A to Paddington will cost you more than a ticket from point A to point B in the opposite direction, even though you are travelling the same distance. This is especially true of peak fares.
(Partly, this is due to the function of fares as a capacity control. You offer cheap tickets off-peak to encourage those who can travel off-peak to do so. But as an extra guarentee, on routes where you have a lot of commuters and really need the peak time space, you make peak time fares such that it really is worth travelling off-peak if you can possibly help it.)
Anyway, it is this usage pricing which creates the fares anomolies. To use JP's example: Bath to Paddington is a well travelled route, hence fares are expensive. Bath to Didcot is a less well travelled route. Even though the train ultimately may end up in Paddington, those of you travelling to Didcot will be off the train before Reading. Didcot to London is a well travelled route also, but a ticket from Didcot to Paddington takes advantage of the distance factor. It's closer so it's cheaper. If you are willing to do the research, you can get good deals with combo tickets, finding the best mid point so that you can take advantage of usage and distance pricing.
Staff do not tell you about combo tickets partly because they don't have to. They have to sell you a ticket and if you ask for a ticket from Bath to Paddington, you'll get the straight-through fare. The other reason is that it takes time to work out these combo tickets. I have seen a staff member report someone standing at a booking office for 30 minutes asking another staff member for every possible combination of tickets so that he could pick the cheapest. An extreme situation no doubt but imagine if this was peak time and you were in the queue behind him. If you ask staff about combo tickets, they will help you but there is a time and a place.
The fares structure in terms of the number of tickets available to purchase can be confusing, espcially when you get to AP ticketing. Back in the good old days there were two main AP tickets, Apex and Super Advance. Individual TOCs had their own systems like Virgin's Value Advance range but FGW stuck to the big two.
Until recently.
Recently came the advent of the Leisure Advance and Business Advance tickets. These were intended to provide a ticketing style similar to airlines. Single journeys only, on a first-come-first-served basis. This was intended to reward customers for early booking (we like early booking, it helps us with usage figures) as well as allowing them to mix and match tickets for their specific journey (peak one way and off-peak the other rather than a peak return ticket even though only one leg was peak, first and standard etc).
Leisure Advance were the off-peak tickets and Business Advance were peak. Not many Business Advance tickets were offered on peak trains as we try and encourage off-peak travel where possible with AP tickets. Each had three bands, A, B and C. C is the cheapest, A the most expensive. As the fare became more expensive, more of them were offered. The impetus being, if you want a really cheap fare you better book damn early. Of course, if you did book damn early, you better not change your mind, because none of the Leisure Advance tickets are refundable (although Business Advance are, and contrary to what anyone may tell you, this is not against the Sale of Goods Act nor does it breach your statutory rights, or any other nonsense).
This was a good system really, and not that complicated once you read around it a bit. However, from May this year, things went a little crazy and each ticket type was increased to 5 bands. Now it's complicated. Unbelievably cheap if you get the bottom band ticket, but complicated.
Sometimes it just makes you want to give up and buy a Saver.
Of course, the restrictions are simple: they're valid on one train, don't miss it. Not so when it comes to walk on ticket restrictions as I believe JP mentioned. There is a lovely little book called the National Fares Manual or NFM. I don't know how many of you have seen this book, or know about it, but here is a picture of one with my hand for scale, taken at my old office at 2130 when I was working (very) late and bored.
This manual contains a list of every fare within the region as well as every restriction for every ticket. As you can see, this one just covers the West region. There are 7 of these to cover the country. It's produced by ATOC and approximately 1/3 of that book is restrictions that determine what ticket type you can by and when, for every journey across the FGW network. It's all available on computer now and it makes me sad in a way as so few people I see nowadays know how to use one properly.
Anyway, enough of nostalgia. As you can see, with this many restrictions, it's no wonder that customers find the fare system complicated and even the staff get confused. It really does take a long time to get to grips with. This is why, JP, you find that your fares vary so dramatically, there are an awful lot of different restrictions.
FGW are in fact, only partly to blame for this as it is ATOC who set the majority of the restrictions. They are independant of TOCS so can apparently be relied upon to be fair to everybody. It is, however, FGW who set the price for the diffent bands so you can still blame them for fares being too high. Since fares seem to be a hot topic at present, I will next present my piece on what goes into deciding your fare or, to put it another way, what exactly are you paying for.
Apologies that this was a bit long and rambling. I may not have been entirely clear in places. If anybody wants to know anything further, as always, I'm open to questions.
Peace
Firstly, we need to set a background. The UK rail network fare structure, at its core, is infinitely complex. It's even more complex than the issue of actually running the trains. I got my start in the railway industry working for a certain organisation now residing somewhere in Bangalore. As we dealt with the entire country rather than just FGW, I got to know a lot about the UK fares structure. At one point during my tenure, it was estimated that, when you took into account AP fares, promotional tickets and each TOCs particular quirks, there were somewhere in the region of 10,000 distinct ticket types. I don't know how true this is and I'm not sure I want to, but it gives you an idea of how a big a scale we're dealing with. The idea is to not pass on too much of this complexity to the customer, but behind the scenes, it's a different story.
What we also have to take into account is that rail fares are not just priced on distance. If they were, things would be much easier. Routes are also priced on usage. A ticket from point A to Paddington will cost you more than a ticket from point A to point B in the opposite direction, even though you are travelling the same distance. This is especially true of peak fares.
(Partly, this is due to the function of fares as a capacity control. You offer cheap tickets off-peak to encourage those who can travel off-peak to do so. But as an extra guarentee, on routes where you have a lot of commuters and really need the peak time space, you make peak time fares such that it really is worth travelling off-peak if you can possibly help it.)
Anyway, it is this usage pricing which creates the fares anomolies. To use JP's example: Bath to Paddington is a well travelled route, hence fares are expensive. Bath to Didcot is a less well travelled route. Even though the train ultimately may end up in Paddington, those of you travelling to Didcot will be off the train before Reading. Didcot to London is a well travelled route also, but a ticket from Didcot to Paddington takes advantage of the distance factor. It's closer so it's cheaper. If you are willing to do the research, you can get good deals with combo tickets, finding the best mid point so that you can take advantage of usage and distance pricing.
Staff do not tell you about combo tickets partly because they don't have to. They have to sell you a ticket and if you ask for a ticket from Bath to Paddington, you'll get the straight-through fare. The other reason is that it takes time to work out these combo tickets. I have seen a staff member report someone standing at a booking office for 30 minutes asking another staff member for every possible combination of tickets so that he could pick the cheapest. An extreme situation no doubt but imagine if this was peak time and you were in the queue behind him. If you ask staff about combo tickets, they will help you but there is a time and a place.
The fares structure in terms of the number of tickets available to purchase can be confusing, espcially when you get to AP ticketing. Back in the good old days there were two main AP tickets, Apex and Super Advance. Individual TOCs had their own systems like Virgin's Value Advance range but FGW stuck to the big two.
Until recently.
Recently came the advent of the Leisure Advance and Business Advance tickets. These were intended to provide a ticketing style similar to airlines. Single journeys only, on a first-come-first-served basis. This was intended to reward customers for early booking (we like early booking, it helps us with usage figures) as well as allowing them to mix and match tickets for their specific journey (peak one way and off-peak the other rather than a peak return ticket even though only one leg was peak, first and standard etc).
Leisure Advance were the off-peak tickets and Business Advance were peak. Not many Business Advance tickets were offered on peak trains as we try and encourage off-peak travel where possible with AP tickets. Each had three bands, A, B and C. C is the cheapest, A the most expensive. As the fare became more expensive, more of them were offered. The impetus being, if you want a really cheap fare you better book damn early. Of course, if you did book damn early, you better not change your mind, because none of the Leisure Advance tickets are refundable (although Business Advance are, and contrary to what anyone may tell you, this is not against the Sale of Goods Act nor does it breach your statutory rights, or any other nonsense).
This was a good system really, and not that complicated once you read around it a bit. However, from May this year, things went a little crazy and each ticket type was increased to 5 bands. Now it's complicated. Unbelievably cheap if you get the bottom band ticket, but complicated.
Sometimes it just makes you want to give up and buy a Saver.
Of course, the restrictions are simple: they're valid on one train, don't miss it. Not so when it comes to walk on ticket restrictions as I believe JP mentioned. There is a lovely little book called the National Fares Manual or NFM. I don't know how many of you have seen this book, or know about it, but here is a picture of one with my hand for scale, taken at my old office at 2130 when I was working (very) late and bored.
This manual contains a list of every fare within the region as well as every restriction for every ticket. As you can see, this one just covers the West region. There are 7 of these to cover the country. It's produced by ATOC and approximately 1/3 of that book is restrictions that determine what ticket type you can by and when, for every journey across the FGW network. It's all available on computer now and it makes me sad in a way as so few people I see nowadays know how to use one properly.Anyway, enough of nostalgia. As you can see, with this many restrictions, it's no wonder that customers find the fare system complicated and even the staff get confused. It really does take a long time to get to grips with. This is why, JP, you find that your fares vary so dramatically, there are an awful lot of different restrictions.
FGW are in fact, only partly to blame for this as it is ATOC who set the majority of the restrictions. They are independant of TOCS so can apparently be relied upon to be fair to everybody. It is, however, FGW who set the price for the diffent bands so you can still blame them for fares being too high. Since fares seem to be a hot topic at present, I will next present my piece on what goes into deciding your fare or, to put it another way, what exactly are you paying for.
Apologies that this was a bit long and rambling. I may not have been entirely clear in places. If anybody wants to know anything further, as always, I'm open to questions.
Peace
Tuesday, 7 August 2007
Track Problems
As I am sure many of you know, there was a massive signal failure near Didcot today. There was no interesting explanation for this one. Is it just me, or does it feel better somehow ehen the reason for a delay is interesting? Maybe I've just worked here for too long and I'm bored of mundane delays.
Anywho, this one was certainly mundane. Something just wore out. As with all signal faults, when somehting wasn;t right, the signla automatically defaulted to caution and everything was brought to a standstill.
To their credit, Network Rail go their Mobile Operations Manager and engineers on the scene fairly sharpish and they were able to fix the problem fairly quickly. Not before, however, we had 3 trains over 2 hours late and a load more over 60 minutes late through knock-on delays. As I looked at the TV above my desk, it was not pleasant to see that much red on a 42" screen.
I'm not sure how much infomation was provided on the scene. We were relying on Network Rail for updates and we certainly didn't get them where I was. My apologies for those of you who were not kept in the know but, if it's any consolation, neither were we. We only knew the status when we were told, (by one of our own staff who was at Didcot station no less) that the signal was green again. The lack of info is the factor that narks me off most, as it is something that we get the blame for when we are not in control of it. Rant on this coming soo, I feel.
I was hoping that the explanation for the signal failure would be a little more interesting but it comes down to the age of the infrastucture yet again, something that Network Rail needs to address urgently and something that the DfT plans to make you guys pay to address. As much as everybody remembers the 'good old days' under British Rail. They are largely to blame for the current state of the track as they never did any maintenance (part of the reason why fares were cheap). Railtrack only did 'cure' maintenance, fixing stuff when it broke and now, Network Rail are trying to do 'prevention' maintenance but because no-one before them did, they are stuck most of the time doing 'cure'. It's an uphill struggle to fix problems as they occur as well as renew track, especially down in this part of the country where we have some of the oldest and most fragile track. More on this problem later.
Sleep well folks. Tomorrow should be a better day.
Anywho, this one was certainly mundane. Something just wore out. As with all signal faults, when somehting wasn;t right, the signla automatically defaulted to caution and everything was brought to a standstill.
To their credit, Network Rail go their Mobile Operations Manager and engineers on the scene fairly sharpish and they were able to fix the problem fairly quickly. Not before, however, we had 3 trains over 2 hours late and a load more over 60 minutes late through knock-on delays. As I looked at the TV above my desk, it was not pleasant to see that much red on a 42" screen.
I'm not sure how much infomation was provided on the scene. We were relying on Network Rail for updates and we certainly didn't get them where I was. My apologies for those of you who were not kept in the know but, if it's any consolation, neither were we. We only knew the status when we were told, (by one of our own staff who was at Didcot station no less) that the signal was green again. The lack of info is the factor that narks me off most, as it is something that we get the blame for when we are not in control of it. Rant on this coming soo, I feel.
I was hoping that the explanation for the signal failure would be a little more interesting but it comes down to the age of the infrastucture yet again, something that Network Rail needs to address urgently and something that the DfT plans to make you guys pay to address. As much as everybody remembers the 'good old days' under British Rail. They are largely to blame for the current state of the track as they never did any maintenance (part of the reason why fares were cheap). Railtrack only did 'cure' maintenance, fixing stuff when it broke and now, Network Rail are trying to do 'prevention' maintenance but because no-one before them did, they are stuck most of the time doing 'cure'. It's an uphill struggle to fix problems as they occur as well as renew track, especially down in this part of the country where we have some of the oldest and most fragile track. More on this problem later.
Sleep well folks. Tomorrow should be a better day.
Subscribe to:
Posts (Atom)