Obviously I’m not aware of all nuances, nor do I want to be (that’s for the legal and compliance experts). As a control manager and controller, my job is to run a train service and a service for the public, not run a contract, but you have to see it from both sides unfortunately.
Interesting.
So I am guessing Hitachi at Etches Park will be contracted to provide X 810s a day, presumably with concessions to the operator for defects going into service. This might not appear to be different to the Agility contracts for the 800s which guaranteed the number of trains in service !!
Probably not at the start but eventually Hitachi / EMR will have an agreed availability figure for the 810’s (and 222’s) since this thread is specifically about the 222’s. There will be planned stopped units (exam, planned maintenance) which fall outside of any penalty, but any further units stopped incur a penalty.
As I said, EMR don’t want cancellations and Hitachi don’t want over and above stopped units that incur a penalty, so that’s the stalemate at times. But sometimes, it will be the case EMR will have to say this unit has ran around with 2 engines out for example for over a week, we’re no longer accepting this unit for service until it’s stopped and a full repair carried out which forces the hand of Hitachi.
There are other scenarios and this happens with TOC’s when the maintenance is in house too but
service disruption is important to mention which is out of control of the maintainer and TOC.
For example, let’s say 222021 was due for exam and engine repairs at Etches Park, however there’s major disruption end of service and the unit ends at Cricklewood instead, the unit hasn’t got enough mileage to complete the diagram the next day and there are cancellations. Hitachi argue that if the unit had been presented to them on time, they’d have completed the engine repairs and exam, the blame lies with EMR as to why the unit is unavailable. Obviously, this is an extreme example and there are of course allowances for such occasions. But it would be unfair of me to say, the blame always lies squarely with the maintainer.
But, such things have to be considered, as a controller, you’re just looking to get the service put back together as quickly as possible, but you always have to have an eye on the maintenance too and that might mean an extra one or two full cancellations, to get the unit on its correct diagram again so it ends at the depot for exam / maintenance. It’s poor service recovery to have an incident that ended on day 1 roll into day 2, these things do happen, I’ve seen it first hand.