90 likes | 230 Views
NM USER FORUM 2014. N etwork Performance: addressing more challenging targets. Brian Flynn Head Performance, Forecasts and Relations 30/01/2014. Single Sky Performance Pillar. SES I: Performance-based regulatory framework, SES II: Performance Scheme RP1 2012-2014
E N D
NM USER FORUM 2014 Network Performance: addressing more challenging targets Brian Flynn Head Performance, Forecasts and Relations 30/01/2014
Single Sky Performance Pillar • SES I: Performance-based regulatory framework, • SES II: Performance Scheme RP1 2012-2014 • Performance scheme RP2 2015-2019 • SES II +:
Traffic trend ER DLA trend APT DLA trend Long term Delay and Traffic Evolution Clear evidence that the ATFM enroute delay situation has seen a sustained improvement
Environment Flight Efficiency progress has also been good. However additional progress to be achieved. Addressed in this User Forum
The Performance Puzzle Cost Competing or complementary targets? Safety Capacity Environment
RP2 2015 to 2019 • Performance targets being finalised • Environment KPIs • Continue improvement of FPL to reach 4.1% in 2019 • Actual Trajectory to reach 2.6% in 2019 • Enroute Delay KPIs • Maintain at 0.5 minutes/flight • Safety KPIs • Level D maturity for Safety policy, risk management, assurance, promotion and level C for safety culture • Risk Analysis tool applied to applicable safety occurrences • Cost KPIs • Further reduction in determined unit costs
RP2 2015 to 2019 – Performance Indicators • No targets • Environment • FUA bookings and Use • Use of CDRs (planning and actual use) • Taxi out time • Additional time in terminal airspace • Enroute Delay • Arrival ATFM delays • Adherence to ATFM slots • Departure ATFM delays • Safety • Monitoring of separation infringements and runway incursions • Cost • EUROCONTROL costs
RP2 – Performance Targets - Discussion RP2 Performance targets: explanations NM Performance Reporting: Does it meet your needs Airspace User ATM Performance plans? NM Performance Plan: Suggestions
A Performance Partnership? • Some ideas • Avoiding traffic bunching • Optimising RRP • Slot swapping and reactionary delays • Slot extensions and associated delay assignment