ESSIP Plan Edition 2012
Commitment decision body: Provisional Council (PC)
Objective approved/endorsed in: 07/2000
Latest change to objective approved/endorsed in: 07/2008
Expected performance benefits
Safety : Reduced unexpected overload situations.
Capacity : Reduced wasted capacity; reduced delays.
Cost-effectiveness : Reduction of costs induced by delays.
Environment : N/A.
Security : N/A
Detailed SloA descriptions
FCM01-ASP01 Supply ETFMS with basic correlated position data Start:08/2001 Finish:12/2004
Action by : ANS Providers
Description & purpose : Provide ETFMS with correlated Position Data for all airborne flights inside its Flight Data Processing Area. For the initial implementation of ETFMS, the CFMU accepts a limited number of existing message formats.
Notes : The implementation of this SLoA is no longer needed as soon as FCM01-ASP02 has been completed in a given State or
ACC.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of CPRs by CFMU has been ensured.
FCM01-ASP02 Supply ETFMS with Standard Correlated Position Data Start:08/2001 Finish:12/2006
Action by : ANS Providers
Description & purpose : Provide ETFMS with Correlated Position Data for all airborne flights inside its Flight Data Processing Area in ASTERIX Category 062 format.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of CPRs in ASTERIX Category 062 format by CFMU has been ensured.
FCM01-ASP03 Receive and process ATFM data from the CFMU Start:03/1995 Finish:12/2001
Action by : ANS Providers
Description & purpose : Ensure that all ATFM messages received from the CFMU are automatically correlated to the ATC Flight Plan data. The ATFM data is automatically presented to the Air Traffic Controllers (as a minimum to the TWR Controllers) on strips or on electronic displays.
Notes : The SloA can be considered as not applicable if the amount of IFR/GAT traffic does not justify automation.
Finalisation criteria : Automatic presentation of the ATFM data correlated to flight data to at least TWR controllers has been ensured.
FCM01-ASP04 Inform CFMU of flight activations and estimates for ATFM purposes Start:03/1995 Finish:12/1999
Action by : ANS Providers
Description & purpose : Send to CFMU a First System Activation (FSA) message as evidence of flight activations in the local ATC system. The FSA informs the CFMU of the actual position of the aircraft (i.e: the actual time of departure or the time and flight level at the FDPA entry co-ordination point).
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of FSA messages by CFMU has been ensured.
FCM01-ASP06 Inform CFMU of re-routings inside FDPA for ATFM purposes Start:03/2001 Finish:12/2006
Action by : ANS Providers
Description & purpose : Send an FSA message for flights for a route change which does not affect the exit point and when this information has not already been sent by an AFP message.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of FSA messages by the CFMU for route changes has been ensured.
FCM01
Implement enhanced tactical flow management services
ESSIP Plan Edition 2012
FCM01-ASP07 Inform CFMU of aircraft holding for ATFM purposes Start:03/2003 Finish:12/2006
Action by : ANS Providers
Description & purpose : Send an FSA to inform the CFMU that the flight is holding.
Specific applicability : ECAC States, IFR/GAT only.
Finalisation criteria : Reception of FSA messages by the CFMU for holding of flights has been ensured.
FCM01-ASP08 Supply CFMU with Departure Planning Information (DPI) Start:03/2005 Finish:-
Action by : ANS Providers
Description & purpose : Supply the CFMU/ETFMS with flight data related updates that are only available shortly before departure. The DPI is used to supply the CFMU with the taxi-time and SID per flight and with the Take-Off Time based upon the departure sequence.
Notes : This SLoA is linked to AOP05-APO05 "Define and implement the exchange of messages, Flight Update Message (FUM)
and Departure Planning Information (DPIs) between CFMU and the airport in accordance with Airport CDM manual guidelines (enhanced CDM)".
No "By-date" is specified because implementation is linked to the implementation of departure management related procedures and tools which are currently being specified
Specific applicability : Airports that can provide DPI data with the required accuracy, IFR/GAT only. Finalisation criteria : Reception of the DPI messages by CFMU has been ensured.
PAGE LEFT INTENTIONALLY BLANK
ECIP Active PE
FCM03
Implement collaborative flight planningREG ASP MIL APO USE INT IND
ESSIP Plan Edition 2012
Description & purpose
Improve the collaboration between the CFMU, ANS providers, airports and airspace users in flight plan filing, in particular to assist airspace users in filing their flight plans and in re-routings according to the airspace availability and ATFM situation. Improve flight plan distribution to increase consistency of flight plan data amongst all parties involved (CFMU IFPS/ETFMS, ANS Providers, etc). Note:out of all SLoAs that are allocated to ANSPs, the most beneficial ones at European level are those dealing with Processing of APL and ACH messages (FCM03-ASP04), missing flight plans (FCM03-ASP05), change of route (FCM03-ASP06), diversion (FCM03-ASP07) and change of requested cruising level (FCM03-ASP09). Therefore States are invited to complete them as a priority.
Applicable area(s) Operational capability dates FOR THIS OBJECTIVE
Initial operational capability: 01/2000 All ECAC States
Full operational capability: 12/2012
References
European ATM Master Plan relationship
OI step - [DCB-0302]-Collaborative Management of Flight Updates
OI step - [IS-0101]-Improved Flight Plan Consistency Pre-Departure
OI step - [IS-0102]-Improved Management of Flight Plan After Departure
Applicable legislation
- Commission Regulation (EC) No 1033/2006 of 4 July 2006 laying down the requirements on procedures for flight plans in the pre-flight phase for the Single European Sky, as amended by Regulation (EC) 929/2010
Applicable ICAO Annexes and other references
DMEAN project 'Improve Management of Flight Plan after Departure'.
Stakeholder Lines of Action (SloA )
SloA ref. Title Start Finish
FCM03-ASP01 Provide flight plan message processing in ICAO format 03/1995 12/1995
FCM03-ASP02 Automatically process FPLs derived from RPLs 03/1995 12/1995
FCM03-ASP03 Provide flight plan message processing in ADEXP format 12/1997 12/2012
FCM03-ASP04 Processing of APL and ACH messages 12/1997 12/1999
FCM03-ASP05 Provide AFP for missing flight plans 03/1998 12/2012
FCM03-ASP06 Provide AFP message for change of route 03/2003 12/2012
FCM03-ASP07 Provide AFP message for a diversion 03/2008 12/2012
FCM03-ASP08 Provide AFP message for a change of flight rules or flight type 03/2003 12/2012
FCM03-ASP09 Provide AFP message for a change of requested cruising level 03/2003 12/2012
FCM03-ASP10 Provide AFP messages in ADEXP format 03/1998 12/2012
FCM03-ASP11 Use IFPLID in all messages to ETFMS 03/2005 12/2006 ▲
FCM03-ASP12 Use IFPLID in exchange of route-charge data DELETED ▲
FCM03-ASP13 Provide AFP message for change of aircraft type 03/2003 12/2012
FCM03-ASP14 Provide AFP message for change of aircraft equipment 03/2008 12/2012
▲ Applicable to the military.
Description of finalised SLoAs is available on the EIPR website at http://www.eurocontrol.int/articles/essip-plan/