Puzzled by the rationale behind the change from Miles per Technical Incident Number (MTIN) to Miles per 701D code (Mp701D) for recording fleet reliability, I asked the Rail Delivery Group, which is responsible for Fleet Challenge, for some background.Mark Molyneux, RDG’s National Fleet Performance Manager, duly obliged with an interview.
We have all become used to MTIN, which supplanted Miles per fiveminute delay (MP5MD) a decade ago. This change represented a tightening up of the measure, since a TIN is registered on TRUST when a failure causes a delay of three minutes.
Most fleets saw their reliability statistics fall back as a result (Table 1). As Table 2 shows, the latest change has had a broadly similar effect.
According to Mr Molyneux, there were a number of reasons behind the latest change. First, the new yardstick is seen as an ‘independent’ number. RDG downloads from TRUST the incidents attributed to Fleet (701D) for each Class. Depots now supply just the mileage for each class in the latest four-week reporting period. RDG then divides mileages by incidents to get Mp701D.
Previously, under MTIN, depots were responsible for supplying RDG with the number of TINs attributed to each of their fleet…
