GWR Performance Figures

[whole diary]

[TaplowGreen]

Once a revised timetable announced, delays are marked against that, rather than the original timetable. So the Cardiff cancellations would be excluded, once GWR^▸ (Great Western Railway) had announced they would only run once an hour, for example

Seriously???

You really couldn't make it up could you? So were there any void days as a result?

[NickB]

Maybe I'll raise this at the next Meet The Manager session.
Oh no, I can't, because they cancelled all means of face to face contact.

[ChrisB]

Yes, I thought that was the case.  How long does it take for those exclusion rules to apply though? 

Overnight. Published the evening before for the following day is good enough.

Also, bear in mind that the public PPM^‡(resolve) charter figures are *peak* trains only, so nothing after 1900 affects the stats. There is an all-day measure, but that is not the charter discount PPM.

[IndustryInsider]

Also, bear in mind that the public PPM^‡(resolve) charter figures are *peak* trains only, so nothing after 1900 affects the stats. There is an all-day measure, but that is not the charter discount PPM.

Yes, I was forgetting that.  Given the incident happened mid way through the peak, that would probably explain why the figures held up so well.  Bring on 'Delay Repay' I say, as there's no way such a large, disruptive incident should have such a small effect on the figures used to determine renewal discounts for season tickets.  And I agree that a void day should have been declared, as per the definition GWR^▸ (Great Western Railway) themselves provide - is it too late for that to happen?

[ChrisB]

Yes - as the day's figures would then be excluded from the Charter PPM^‡(resolve) stats.

[ChrisB]

Careful what you wish for - While Delay/Repay would get seasons compensation for this sort of an event, regular poor performance of over 10mins but less than 30mins affects the charter PPM^‡(resolve), but would render zilch on Delay/Repay.....so under this scheme seasons might get 5% renewal discount, under delay/repay, there would be nowt.

It works both ways unfortunately.

[IndustryInsider]

Careful what you wish for

I wish for a fairer system for passengers - one that reflects delays which they experience.  Apart from the 5% LTV^▸ (London [and] Thames Valley) discount, no other GWR^▸ (Great Western Railway) season is discounting (or even close to hitting the discount trigger), so whilst there may be the odd loser (a Slough to Windsor commuter for example), it's a far fairer system for the majority.

[ChrisB]

*IF* they suffer the odd long delay, yes.

But regular poor timekeeping (of the type LTV^▸ (London [and] Thames Valley) are suffering, hence the 5% discount) of less than 30mins will mean that they can lose out quite easily

[TaplowGreen]

So really then these performance figures don't reflect the chaotic reality which the derailment caused, they reflect the rest of the month along with a few days of performance against an "amended timetable"?

It'd be interesting to see the true picture, incorporating all the cancellations and delays which the incident caused.

This seems to be a very handy "Get out of jail free" card for GWR^▸ (Great Western Railway) - if there's serious disruption which will knacker your stats, simply declare an "amended timetable" and be measured against that rather than what actually happened?

[NickB]

Sounds like it is more efficient for GWR^▸ (Great Western Railway) to have an elite team of timetable writers and a good relationship with the print room than to try and run a train service to schedule. 😉

[ChrisB]

This seems to be a very handy "Get out of jail free" card for GWR^▸ (Great Western Railway) - if there's serious disruption which will knacker your stats, simply declare an "amended timetable" and be measured against that rather than what actually happened?

Not just GWR - them's the rules written into each franchise. Gets the taxpayer more money from the franchise process, doncha know.

[IndustryInsider]

It'd be interesting to see the true picture, incorporating all the cancellations and delays which the incident caused.

You can get much more information on the all day PPM^‡(resolve) scores here, see the 'Daily' and 'Recent Performance' tabs, but I'm pretty sure it was around 3000 delay minutes and 200 cancellations for the first day of the disuption.

https://www.firstgroup.com/uktrain/kpi/gw/

[IndustryInsider]

Latest graph attached.  Not an especially impressive month of stats, especially for HSS^▸ (High Speed Services) at only 86.8%, but the LTV^▸ (London [and] Thames Valley) MAA^▸ (Moving Annual Average) has risen by 0.4% so it must've been a lot better than this time last year.

[IndustryInsider]

Latest graph attached.  A pretty good month of figures given the widespread service alterations as a result of the engineering blockade at Hinksey.  The LTV^▸ (London [and] Thames Valley) figure exceeded the charter discount trigger for only the second time this year.

[IndustryInsider]

Latest graph attached and it was a pretty awful period, with LTV^▸ (London [and] Thames Valley) services barely recording 80% and HSS^▸ (High Speed Services) only a couple of percentage points better.  The Moving Annual Average also took quite a hit as a result.