NTF review and its impact on the management of fleet performance

Report
Fleet Challenge
Christian Roth
Fleet Challenge Chairman
Contents
•
•
•
•
•
What is Fleet Challenge
What are we doing
What has been achieved
Why we have changed performance measures
What are TOC’s doing
Fleet Challenge
• NTF requested the Fleet Engineering Community to improve
PPM by 1 additional point during CP4 by reducing fleet delays
• NFRIP split into two components for delivery;
– ReFocus (tactical improvements) and
– Fleet Challenge (strategic improvements)
• Fleet Challenge membership consists of senior engineering
managers from:
–
–
–
–
TOCs
OEMs
RoSCos
DfT
• Programme of work was jointly agreed
Progress to date with Fleet Challenge
Workstream
Outcome
Depot enhancement
Survey of depots contributed to Depot RUS
Performance Fund
submissions
Portfolio of differentiated TOC fleet
schemes for investment.
• Circa £15m schemes authorised to date
• Further £15m planned for funding
• Livetrain to complex and risky as national
programme
Managing delays from
technical incidents
Survey contributing to Joint Ops/Fleet
workstream under development
Refocus
Developing content of good practice guide
(20pp) via voluntary workshops
Review point
• Fleet Challenge target re-assessed as 0.5ppm
based on value for money
• Review identified Fleet Reliability has
improved continually.
– law of diminishing returns is making incremental
improvement harder.
– However delay minutes have increased
New Fleet Performance Measures
• Move from Unit Miles per Technical Casualty
• Measure Unit Miles per Technical Incident
(MTIN) and Delay per Technical Incident (DPI)
from April 2011
– Better correlation with PPM
– Larger data set from 5 mins to 3 mins
– Moving towards a right time railway
– Possible to build a JPIP target from MTIN and DPI
targets
Period MAA of MTIN and DPI
(Technical Incidents only)
34.0
9000
7000
28.0
6000
MTIN (Unit Miles per Incident)
26.0
DPI (TOC-Self Mins per Incident)
5000
Linear (MTIN (Unit Miles per Incident))
24.0
Linear (DPI (TOC-Self Mins per Incident))
4000
Incidents and Delay Minutes Ssurced from Network Rail data.
TOC-on-Self Fleet Technical (701D )incidents.
DPI based on combined primary and reactioanry delay minutes.
Unit Mileage in MTIN sourced from TOC fleet data.
3000
P13
07/08 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
08/09 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
09/10 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
10/11 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
11/12 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
12/13 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
13/14 P1
P2
P3
P4
P5
P6
P7
P8
P9
P10
P11
P12
P13
Miles per Technical Incident (MTIn)
30.0
22.0
20.0
Average Delay Per Incident (DPI)
32.0
8000
Current MTIN & DPI MAA performance
P7 2011/2012
Unit Miles per TIN MAA P7 2011/12
c2c
SWT
CrossCountry
FCC
Southern
Southeastern
LondonMidland
VirginTrains
TOC
TPE
EastMidlandsTrains
EastCoast
NXEA
Merseyrail
LondonOverground
Chiltern
FGW
Northern
Scotrail
ATW
TOC on Self : Delay per Technical Incident MAA P7
2011/2012
Southern
NXEA
Southeastern
SWT
FCC
FGW
c2c
East Coast
London…
ATW
TOC
Northern
Scotrail
London Midland
Virgin Trains
Cross Country
East Midlands…
Chiltern
TPE
Merseyrail
0
5000 10000 15000 20000 25000 30000
Unit Miles per TIN MAA
0.0
20.0
40.0
60.0
Delay Minutes per Technical Incident MAA
National average fleet reliability is 9259 Unit Miles per technical
TRUST incident (MTIN)
Way forward - TOC actions
• Individual Fleet schemes planned to improve DPI
and MTIN (circa £24m investment in the
approved and in the authorisation process)
• New collaborative effort on minimising delays
from technical incidents based on good practice
–
–
–
–
Operation Blitz - SWT
Interactive Virtual Train – FGW, EMT
Web based decision support tool in control (Southern)
Development of good practice in minimising delays
from technical incidents – ReFocus
– Benchmarking RCM systems
Summary
• Fleet Reliability has improved circa 55% since
2004/5
• Fleet Challenge current programme of work is
estimated to deliver an additional 0.5ppm
• Little focus on minimising delay from technical
incidents
• Going forward this must be equally important

similar documents