ETSI EN 303 212 V1.1.1 (2010-06)

Final draft ETSI EN 303 212 V1.1.1 (2010-03)
European Standard (Telecommunications series)

Airport Collaborative Decision Making (A-CDM);
Community Specification for application under the
Single European Sky Interoperability Regulation EC 552/2004

2 Final draft ETSI EN 303 212 V1.1.1 (2010-03)

Reference
DEN/AERO-00002
Keywords
air traffic management, aeronautical, interoperability
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In
case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for
the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 6
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 10
4 Role, Responsibility and Interrelation requirements . 11
5 Functional, Technical, Interface and Validation Requirements . 12
5.1 Introduction . 12
5.1.1 Test and validation methods . 12
5.2 Airport CDM Elements . 12
5.3 Airport CDM Information Sharing - ACIS . 12
5.3.1 Background . 12
5.3.2 ACIS Functional Requirements . 13
5.3.2.1 ACIS Display of identical information . 13
5.3.2.2 ACIS User access . 13
5.3.2.3 Alert messaging and handling . 13
5.3.2.4 ACIS Manual data entry . 13
5.3.2.5 ACIS Flight information sharing . 13
5.3.2.6 ACIS Aeronautical and meteorological information sharing . 13
5.3.2.7 ACIS Archiving . 13
5.3.2.8 ACIS Filtering of information . 14
5.3.3 ACIS Technical Requirements . 14
5.3.3.1 ACIS Data validation . 14
5.3.3.2 ACIS Data protection . 14
5.3.3.3 ACIS Parameter and performance supervision . 14
5.3.3.4 ACIS Input data prioritization . 14
5.3.3.5 ACIS System time . 14
5.3.3.6 ACIS Data timeliness . 14
5.3.3.7 ACIS System availability . 15
5.3.3.8 ACIS System capacity. 15
5.3.4 ACIS Interface Requirements . 15
5.3.4.1 ACIS Flight identification . 15
5.3.4.2 ACIS Message formatting . 15
5.3.4.3 ACIS Data source identification . 15
5.3.4.4 ACIS Information exchange. 15
5.3.4.5 ACIS Event identification . 15
5.3.4.6 ACIS Duration parameters . 16
5.3.4.7 ACIS Airport resources identification . 16
5.3.4.8 ACIS Alert identification . 16
5.3.4.9 ACIS Key flight information. 16
5.4 Airport CDM Collaborative Turn-Round Process - CTRP . 16
5.4.1 Background . 16
5.4.2 CTRP Functional Requirements . 17
5.4.2.1 A-CDM CTRP Milestone approach . 17
5.4.2.2 A-CDM CTRP Milestone processing. 17
5.4.2.3 A-CDM CTRP Milestone updating . 17
5.4.2.4 A-CDM CTRP Operational alerting. 17
ETSI
4 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
5.4.3 CTRP Technical Requirements . 18
5.4.3.1 Void. 18
5.4.4 CTRP Interface Requirements . 18
5.4.4.1 Void. 18
5.5 Airport CDM Variable Taxi Time Calculation - VTTC . 18
5.5.1 Background . 18
5.5.2 VTTC Functional Requirements . 18
5.5.2.1 A-CDM VTTC Variable taxi time calculation implementation . 18
5.5.2.2 A-CDM VTTC Automatic taxi time calculation and Update . 18
5.5.2.3 A-CDM VTTC Data timeliness . 18
5.5.2.4 A-CDM VTTC Input data . 18
5.5.2.5 A-CDM VTTC Methods . 19
5.5.3 VTTC Technical Requirements . 19
5.5.3.1 Void. 19
5.5.4 VTTC Interface Requirements . 19
5.5.4.1 Void. 19
5.6 Airport CDM Collaborative Management of Flight Updates - COFU . 19
5.6.1 Background . 19
5.6.2 COFU Functional Requirements . 19
5.6.2.1 A-CDM COFU Collaborative Management of Flight Updates Implementation . 19
5.6.2.2 A-CDM COFU Data timeliness . 19
5.6.2.3 A-CDM COFU Data Operations . 19
5.6.2.4 A-CDM COFU Message processing . 20
5.6.2.4.1 A-CDM COFU Message processing - Generic DPI process . 20
5.6.2.4.2 A-CDM COFU Message processing - Early DPI process . 20
5.6.2.4.3 A-CDM COFU Message processing - Target DPI process . 20
5.6.2.4.4 A-CDM COFU Message processing - ATC DPI process . 20
5.6.2.4.5 A-CDM COFU Message processing - Cancel DPI process . 20
5.6.2.4.6 A-CDM COFU Message processing - Sequence of DPI messages . 21
5.6.2.5 A-CDM COFU Message Content . 21
5.6.3 COFU Technical Requirements . 21
5.6.3.1 Void. 21
5.6.4 COFU Interface Requirements . 21
5.6.4.1 A-CDM COFU Collaborative Management of Flight Updates Implementation . 21
5.6.4.2 A-CDM COFU Data item identifier . 21
5.6.4.3 A-CDM COFU Data format . 21
5.6.4.4 A-CDM COFU Quality . 22
5.7 Airport CDM Collaborative Pre-Departure Sequence - CPDS. 22
5.7.1 Background . 22
5.7.2 CPDS Functional Requirements . 22
5.7.2.1 A-CDM CPDS Collaborative Pre-Departure Sequence Implementation . 22
5.7.2.2 A-CDM CPDS Distribution and Display . 22
5.7.2.3 A-CDM CPDS TSAT calculation . 22
5.7.3 CPDS Technical Requirements . 23
5.7.3.1 Void. 23
5.7.4 CPDS Interface Requirements . 23
5.7.4.1 Void. 23
5.8 Airport CDM in Adverse Conditions - CDAC . 23
5.8.1 Background . 23
5.8.2 CDM CDAC Functional Requirements . 23
5.8.2.1 A-CDM CDAC A-CDM in adverse conditions implementation . 23
5.8.2.2 A-CDM CDAC Flight cancellations and delay . 23
5.8.2.3 A-CDM CDAC Resource availability . 23
5.8.3 CDAC Technical Requirements . 23
5.8.3.1 Void. 23
5.8.4 CDAC Interface Requirements . 23
5.8.4.1 Void. 23
Annex SA (normative): Standards Annex . 24
SA.1 Correspondence between this European Standard and the Single European Sky Interoperability
Regulation (as amended) for A-CDM . 24
ETSI
5 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
Annex A (normative): Checklist . 35
A.1 Interoperability Regulation Annex II Essential Requirements; Part A: General requirements . 36
A.2 Interoperability Regulation Annex II Essential Requirements Part B: Specific requirements . 43
A.2.1 Systems and procedures for airspace management. 43
A.2.2 Systems and procedures for air traffic flow management . 43
A.2.3 Systems and procedures for air traffic services . 44
A.2.3.1 Flight data processing systems. 44
A.2.3.2 Surveillance data processing systems . 50
A.2.3.3 Human-machine interface systems . 51
A.2.4 Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air
communications . 52
A.2.5 Navigation systems and procedures . 53
A.2.6 Surveillance systems and procedures . 53
A.2.7 Systems and procedures for aeronautical information services . 53
A.2.8 Systems and procedures for the use of meteorological information . 54
Annex B (informative): The EN title in the official languages . 55
Annex C (informative): Bibliography . 56
History . 57

ETSI
6 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining
to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in
ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server
(http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can
be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Aeronautics
(AERO), and is now submitted for the Vote phase of the ETSI standards Two-step Approval Procedure.
The present document has been produced by ETSI in response to European Commission mandate M/390 for the
Interoperability of the European Air Traffic Management Network.
The present document has been developed in cooperation with Eurocae for compliance with the Essential Requirements of
the Single European Sky Interoperability Regulation [i.1] and/or requirements given in implementing rules for the Single
European Sky Interoperability Regulation.
The presumption of conformity which is linked to the full application of the present document can only be claimed after the
present document has been listed in the Official Journal of the European Union as Community Specification.
General and specific requirements for presumption of conformity to SES Interoperability Regulation 552/2004 as
amended by Regulation 1070/2009 are given in the normative annexes of the present document.
NOTE: Other requirements and other EU Regulations and/or Directives may be applicable to the product(s) falling
within the scope of the present document.

Proposed national transposition dates
Date of latest announcement of this EN (doa): 3 months after ETSI publication
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 6 months after doa
Date of withdrawal of any conflicting National Standard (dow): 18 months after doa

Introduction
The European Union launched the Legislation "Single European Sky" (SES) in 2002 which was adopted in 2004 and
amended by Regulation (EC) No 1070/2009 [i.1].
The SES legislation is based on a framework of 4 regulations, which includes the Interoperability Regulation [i.1]. The
objective of the Interoperability Regulation is to ensure interoperability of the European Air Traffic Management Network
(EATMN) consistent with air navigation services. Under this regulation, the use of a European Standard referenced in the
Official Journal of the European Union as Community Specification (CS) is a means of compliance to the essential
requirements of the Regulation and/or the relevant implementing rules for interoperability.
The present document takes into account the Council Decision 2009/320/EC [i.4] endorsing the European Air Traffic
Management Master Plan of the Single European Sky ATM Research (SESAR) project [i.4].
ETSI
7 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
Figure 1 shows the high level relationship between the Eurocontrol and Eurocae which were developed in parallel.
EUROCONTROL EUROCAE
Documents Documents
System Requirements
Concept of Operations
Document (ED-141)
Functional
Interface Definition
Requirements
Document (ED-145)
Document
Implementation Test and Validation
Manual Document (ED-146)
Figure 1: Eurocontrol and Eurocae Document Relationship
ETSI
8 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
1 Scope
The present document is applicable to Air Traffic Management Airport Collaborative Decision Making (A-CDM).
The present document addresses the specific roles, responsibilities, procedures, systems and interfaces needed to fulfil the
Airport CDM (A-CDM) Operating Concept as requested by Mandate M/390 of the European Commission. It references
existing documentation where necessary to clarify the more detailed aspects of a procedure or system implementation
requirement to avoid unnecessary repetition.
Airport Collaborative Decision making (A-CDM) is about improving the way operational partners at airports and European
ATFCM (Air Traffic Flow and Capacity Management, Air Traffic Control, Airlines, Ground Handling Agents/Units and
Airports) work together at an operational level.
A-CDM allows an Airport CDM partner to make the right decisions for a flight during the whole Airport CDM process in
collaboration with other Airport CDM partners, knowing their preferences and constraints and the actual and predicted
situation. The decision making by the Airport CDM partners is dependent upon the sharing of accurate and timely
information and upon adapted Airport CDM procedures, mechanisms and tools.
Any software elements related to the software assurance level of an A-CDM System are outside of the scope of the present
document. As such the essential requirements of the Interoperability Regulation are not considered for software elements
within the present document.
The present document does not give a presumption of conformity related to maintenance requirements, safety, civil/military
coordination or environmental constraints.
NOTE: For these ERs, please refer to the Air Navigation Service Provider procedures.
Requirements in the present document which refer to "should" statements or recommendations in the normatively
referenced material (clause 2.1) are to be interpreted as fully normative ("shall") for the purpose of compliance with the
present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the purposes
of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated references,
only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any
amendments) applies.
[1] Eurocontrol: "Airport CDM Operational Concept Document" (Version 3.0, Sept 2006).
NOTE: See figure 1.
ETSI
9 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
[2] Eurocontrol: "Airport CDM Functional Requirements Document" (Version 4.0 May 2009).
NOTE: See figure 1.
[3] Eurocontrol: "CFMU DPI Implementation Guide" (Version 1.3).
NOTE: See figure 1.
[4] Eurocontrol: "CFMU Flight Progress Messages" (Version 1.6).
NOTE: See figure 1.
[5] Eurocae: "Minimum Technical Specification for the Airport Collaborative Decision Making (Airport-
CDM)" - ED141 - (Version 1, October 2008).
NOTE: See figure 1.
[6] Eurocae: "Airport-CDM Interface Specification" - ED145 - (Version 1, October 2008).
NOTE: See figure 1.
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with regard
to a particular subject area. For non-specific references, the latest version of the referenced document (including any
amendments) applies.
[i.1] Regulation (EC) No 552/2004 of the European Parliament and of the Council of 10 March 2004 on
the interoperability of the European Air Traffic Management network (the Interoperability
Regulation), OJ L 96, 31.03.2004 p.26 as amended by Regulation (EC) No 1070/2009, OJ L 300,
14.11.2009 p.34.
[i.2] Eurocontrol: "Airport CDM Implementation Manual" (Version 3).
NOTE: See figure 1.
[i.3] Regulation (EC) No 549/2004 of the European Parliament and of the Council of 10 March 2004
laying down the framework for the creation of the single European sky (the Framework Regulation),
OJ L 96, 31.03.2004 p.1 as amended by Regulation (EC) No 1070/2009, OJ L 300, 14.11.2009 p.34.
[i.4] Council Decision 2009/320/EC endorsing the European Air Traffic Management Master Plan of the
Single European Sky ATM Research (SESAR) project, 30.03.2009 published in OJ L95, p.41,
9.4.2009.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in the Framework Regulation [i.3],
Interoperability Regulation [i.1], in the Functional Requirements Document [2] and the following apply:
ground handling: covers a complex series of processes that are required to separate an aircraft from its load (passengers,
baggage, cargo and mail) on arrival and combine it with its load prior to departure
NOTE: Source: www.iata.org.
ETSI
10 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in Functional Requirements Document [2] and the
following apply:
A-CDM Airport CDM
ACIS Airport CDM Information Sharing
ACISP Airport CDM Information Sharing Platform
ATC Air Traffic Control
ATFCM Air Traffic Flow and Capacity Management
ATFM Air Traffic Flow Management
ATM Air Traffic Management
CDAC CDM in Adverse Conditions
CDM Collaborative Decision Making
CEN Comité Européen de Normalization
CFMU Central Flow Management Unit
COFU COllaborative management of Flight Updates
CPDS Collaborative Pre-Departure Sequence
CS Community Specifications
CTOT Calculated Take Off Time (CFMU)
CTRP CDM Turn-Round Process
DPI Departure Planning Information message
EATMN European Air Traffic Management Network
EC European Community
EDDM Munich International Airport
EEC EUROCONTROL Experimental Centre
EEZT Estimated End of De-icing Time
ER Essential Requirement
ERZT Estimated Ready for De-icing Time
ETSI European Telecommunications Standards Institute
EU European Union
EUROCAE EURopean Organization for Civil Aviation Equipment
EUROCONTROL European Organization for the Safety of Air Navigation
FUM Flight Update Message
HMI Human-Machine Interface
IATA International Air Transport Association
ICAO International Civil Aviation Organization
IPR Intellectual Property Rights
MST Milestone
SES Single European Sky
TMA Terminal Manoeuvring Area
TOBT Target Off-Block Time
TSAT Target Start-Up Approval Time
TTOT Target Take Off Time
VTTC Variable Taxi Time Calculation
ETSI
11 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
4 Role, Responsibility and Interrelation requirements
All parties listed in the following table shall comply with the requirements of the present document related to their specific
role within the Airport CDM process. Collectively, the parties below are referred to within the present document as the
Airport CDM Partners. The column "interrelation with respect to the present document" of the following table has to be
considered as the minimum requirements. Further relations may differ and depend on local Airport CDM Partners
responsibilities.
Ref Role Responsibility Interrelation with respect to the
present document
4.1 Air Traffic Control (ATC) A civil or military unit responsible for ATC needs:
providing Air Traffic Control services. In 1. Updated CDM situational
case of Airport CDM it is mainly the Air information such as planned,
Traffic Control Tower at the CDM Airport. TOBT, Gate/stand number.
ATC provides:
2. Updated planned, estimated
and actual landing, in-blocks,
TSAT and TTOT.
4.2 Airport Operations Airport Operations is an organization Airport Operations needs:
providing Airport Management, Airport
3. Updated CDM situational
Traffic Operations Centre, and Stand & information such as planned,
Gate Management. estimated and actual landing,
in-blocks, TOBT, TSAT and
TTOT.
Airport Operations provide:
4. Airport Schedule information,
Airport resources allocation.
4.3 Ground handling agents Ground Handling can provide a subset of Ground Handling needs:
the data normally delivered by the 5. Updated CDM situational
Aircraft Operator, depending on the information such as planned,
agreement between the particular Aircraft estimated and actual landing,
Operator and Ground Handling Agents in-blocks, TSAT and TTOT.
as mentioned above. Ground Handling can provide:
6. Flight Plan and other data
related to the flight, planned,
estimated and actual times
related to progress of
turn-around such as TOBT.
4.4 Aircraft Operator A person, organization or enterprise Aircraft Operations need:
engaged in, or offering to engage in, an 7. Updated CDM situational
aircraft operation. This includes the flight information such as planned,
operator or a nominated representative. estimated and actual landing,
in-blocks, TSAT and TTOT.
Aircraft Operations provide:
8. Flight Plan and other data
related to the flight, planned,
estimated and actual times
related to progress of
turn-around such as TOBT.
4.5 Eurocontrol Central Flow CFMU provides flight plan data and
ATFCM needs:
Management Unit (CFMU) ATFCM data. Depending on 9. Departure Planning
local/national implementation, Information (DPIs).
information to and from the CFMU may ATFCM provides:
pass through the ATC system. 10. Flight Plan Data, Calculated
Take-off Times (Departure
slots), Flight Update
Messages (FUM).
4.6 De Icing Operations A person or organization which provides De-icing Operations needs:
all services related to the de icing of an 11. Updated information about
aircraft. aircraft requesting de-icing and
the ERZT and TSAT.
De-icing Operations can provide:
12. Status of De-icing for the
particular aircraft.
13. Prediction of EEZT (Estimated
End of De-icing Time).
ETSI
12 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
5 Functional, Technical, Interface and Validation
Requirements
5.1 Introduction
This clause describes the essential functional, technical and interface requirements associated with implementing an
A-CDM. Each A-CDM concept element is formed of at least one functional requirement. All requirements have an
associated test and validation requirement which describes the method of demonstrating compliance to the present
document.
5.1.1 Test and validation methods
The methods of Inspection, Demonstration and Analysis are chosen as suitable for showing compliance to each specific
functional, technical and interface requirement. The following table provides guidance for each method:
• Inspection:
- Does the system under test embody the expected characteristics as described within the requirement?
• Demonstration:
- Does the system under test produce the output required?
• Analysis:
- Does the system under test provide calculated results or operate in accordance to performance values as
required?
5.2 Airport CDM Elements
The required Airport CDM capabilities have been grouped into key elements and shall be met as defined in Airport CDM
Operational Concept Document [1], and Functional Requirements Document [2], with regard to:
• Airport CDM - Information Sharing - ACIS.
• Airport CDM - Collaborative Turn-Round Process - CTRP.
• Airport CDM - Variable Taxi Time Calculation - VTTC.
• Airport CDM - Collaborative Management of Flight Updates - COFU.
• Airport CDM - Collaborative Pre-Departure Sequence - CPDS.
• Airport CDM - CDM in Adverse Conditions - CDAC.
5.3 Airport CDM Information Sharing - ACIS
5.3.1 Background
The Airport CDM Information Sharing (ACIS) provides the overall environment through which Airport CDM Partners can
interact with shared information securely, with the assurance that data is accurate, relevant, timely and authoritative. The
ACIS is the foundation for implementing all remaining A-CDM Elements. There are two purposes of the ACIS; firstly it
provides a consistent display and security approach for all of the A-CDM Elements, and secondly it creates the
environment for the sharing of all relevant events. This clause details the functional, technical, interface and validation
requirements associated with the ACIS Element.
ETSI
13 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
5.3.2 ACIS Functional Requirements
5.3.2.1 ACIS Display of identical information
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Display of identical information at all working positions in accordance with Requirements 20 and 230 within the
Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.2 ACIS User access
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Positive identification, validation and authorization of users with regard to data entry and modification in
accordance with Requirements 30, 40, 50 and 60 within the Functional Requirements Document [2], and shall be
tested and validated by demonstration.
5.3.2.3 Alert messaging and handling
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Provision and handling of alert messages in accordance with Requirements 90, 100, 800, 810 and 820 within the
Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.4 ACIS Manual data entry
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Manual data entry and modification of system parameters in accordance with Requirements 110 and 120 within
the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.5 ACIS Flight information sharing
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Collection, collation, correlation and distribution of relevant arriving and departing flight information to and from
all A-CDM Partners in accordance with Requirements 210, 220, 230, 240, 250, 530, 540, 550, 570 and 780 within
the Functional Requirements Document [2], and shall be tested and validated by demonstration and analysis.
5.3.2.6 ACIS Aeronautical and meteorological information sharing
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Access to aeronautical and meteorological information relevant to A-CDM Partners in accordance with
Requirement 270 within the Functional Requirements Document [2], and shall be tested and validated by
demonstration.
5.3.2.7 ACIS Archiving
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Archiving capability in accordance with Requirements 280, 290 and 310 within the Functional Requirements
Document [2], and shall be tested and validated by demonstration.
ETSI
14 Final draft ETSI EN 303 212 V1.1.1 (2010-03)
5.3.2.8 ACIS Filtering of information
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Filtering of information for onward processing by originator and timeliness in accordance with Requirements 320,
330, 380, 390 and 730 within the Functional Requirements Document [2], and shall be tested and validated by
demonstration and analysis.
5.3.3 ACIS Technical Requirements
5.3.3.1 ACIS Data validation
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Validation of data appropriate to the known phase of flight in accordance with Requirement ED141-0120 within
the Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and validated by
demonstration.
5.3.3.2 ACIS Data protection
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Ensuring that commercially sensitive information remains confidential and that information presented to users is
relevant in accordance with Requirement ED141-0790 within the Minimum Technical Specification for the
Airport CDM Systems [5], and shall be tested and validated by demonstration.
5.3.3.3 ACIS Parameter and performance supervision
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Capability for operational and technical supervisors to add, modify and monitor platform parameters and
performance in accordance with Requirements ED141-0010, ED141-0020, ED141-0060, ED141-0061, ED141-
0064, ED141-0065, ED141-0066 and ED141-0068 within the Minimum Technical Specification for the Airport
CDM Systems [5], and shall be tested and validated by demonstration.
5.3.3.4 ACIS Input data prioritization
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Prioritization of data sources in accordance with Requirement 730 within the Functional Requirements Document
[2] and ED141-0063 within the Minimum Technical Specification for the Airport CDM Systems [5], and shall be
tested and validated by demonstration.
5.3.3.5 ACIS System time
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• System time reference and accuracy in accordance with Requirements ED141-0870 and ED141-0895 within the
Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and validated by
demonstration and analysis.
5.3.3.6 ACIS Data timeliness
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Timeliness of information flows between Partners in accordance with Requirement ED1
...

European Standard (Telecommunications series)

Airport Collaborative Decision Making (A-CDM);
Community Specification for application under the
Single European Sky Interoperability Regulation EC 552/2004

2 ETSI EN 303 212 V1.1.1 (2010-06)

Reference
DEN/AERO-00002
Keywords
air traffic management, aeronautical,
interoperability
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI EN 303 212 V1.1.1 (2010-06)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 6
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Role, Responsibility and Interrelation requirements . 11
5 Functional, Technical, Interface and Validation Requirements . 12
5.1 Introduction . 12
5.1.1 Test and validation methods . 12
5.2 Airport CDM Elements . 12
5.3 Airport CDM Information Sharing - ACIS . 12
5.3.1 Background . 12
5.3.2 ACIS Functional Requirements . 13
5.3.2.1 ACIS Display of identical information . 13
5.3.2.2 ACIS User access . 13
5.3.2.3 Alert messaging and handling . 13
5.3.2.4 ACIS Manual data entry . 13
5.3.2.5 ACIS Flight information sharing . 13
5.3.2.6 ACIS Aeronautical and meteorological information sharing . 13
5.3.2.7 ACIS Archiving . 13
5.3.2.8 ACIS Filtering of information . 14
5.3.3 ACIS Technical Requirements . 14
5.3.3.1 ACIS Data validation . 14
5.3.3.2 ACIS Data protection . 14
5.3.3.3 ACIS Parameter and performance supervision . 14
5.3.3.4 ACIS Input data prioritization . 14
5.3.3.5 ACIS System time . 14
5.3.3.6 ACIS Data timeliness . 14
5.3.3.7 ACIS System availability . 15
5.3.3.8 ACIS System capacity. 15
5.3.4 ACIS Interface Requirements . 15
5.3.4.1 ACIS Flight identification . 15
5.3.4.2 ACIS Message formatting . 15
5.3.4.3 ACIS Data source identification . 15
5.3.4.4 ACIS Information exchange. 15
5.3.4.5 ACIS Event identification . 15
5.3.4.6 ACIS Duration parameters . 16
5.3.4.7 ACIS Airport resources identification . 16
5.3.4.8 ACIS Alert identification . 16
5.3.4.9 ACIS Key flight information. 16
5.4 Airport CDM Collaborative Turn-Round Process - CTRP . 16
5.4.1 Background . 16
5.4.2 CTRP Functional Requirements . 17
5.4.2.1 A-CDM CTRP Milestone approach . 17
5.4.2.2 A-CDM CTRP Milestone processing. 17
5.4.2.3 A-CDM CTRP Milestone updating . 17
5.4.2.4 A-CDM CTRP Operational alerting. 17
5.4.3 CTRP Technical Requirements . 18
ETSI
4 ETSI EN 303 212 V1.1.1 (2010-06)
5.4.3.1 Void. 18
5.4.4 CTRP Interface Requirements . 18
5.4.4.1 Void. 18
5.5 Airport CDM Variable Taxi Time Calculation - VTTC . 18
5.5.1 Background . 18
5.5.2 VTTC Functional Requirements . 18
5.5.2.1 A-CDM VTTC Variable taxi time calculation implementation . 18
5.5.2.2 A-CDM VTTC Automatic taxi time calculation and Update . 18
5.5.2.3 A-CDM VTTC Data timeliness . 18
5.5.2.4 A-CDM VTTC Input data . 18
5.5.2.5 A-CDM VTTC Methods . 19
5.5.3 VTTC Technical Requirements . 19
5.5.3.1 Void. 19
5.5.4 VTTC Interface Requirements . 19
5.5.4.1 Void. 19
5.6 Airport CDM Collaborative Management of Flight Updates - COFU . 19
5.6.1 Background . 19
5.6.2 COFU Functional Requirements . 19
5.6.2.1 A-CDM COFU Collaborative Management of Flight Updates Implementation . 19
5.6.2.2 A-CDM COFU Data timeliness . 19
5.6.2.3 A-CDM COFU Data Operations . 19
5.6.2.4 A-CDM COFU Message processing . 20
5.6.2.4.1 A-CDM COFU Message processing - Generic DPI process . 20
5.6.2.4.2 A-CDM COFU Message processing - Early DPI process . 20
5.6.2.4.3 A-CDM COFU Message processing - Target DPI process . 20
5.6.2.4.4 A-CDM COFU Message processing - ATC DPI process . 20
5.6.2.4.5 A-CDM COFU Message processing - Cancel DPI process . 20
5.6.2.4.6 A-CDM COFU Message processing - Sequence of DPI messages . 21
5.6.2.5 A-CDM COFU Message Content . 21
5.6.3 COFU Technical Requirements . 21
5.6.3.1 Void. 21
5.6.4 COFU Interface Requirements . 21
5.6.4.1 A-CDM COFU Collaborative Management of Flight Updates Implementation . 21
5.6.4.2 A-CDM COFU Data item identifier . 21
5.6.4.3 A-CDM COFU Data format . 21
5.6.4.4 A-CDM COFU Quality . 22
5.7 Airport CDM Collaborative Pre-Departure Sequence - CPDS. 22
5.7.1 Background . 22
5.7.2 CPDS Functional Requirements . 22
5.7.2.1 A-CDM CPDS Collaborative Pre-Departure Sequence Implementation . 22
5.7.2.2 A-CDM CPDS Distribution and Display . 22
5.7.2.3 A-CDM CPDS TSAT calculation . 22
5.7.3 CPDS Technical Requirements . 23
5.7.3.1 Void. 23
5.7.4 CPDS Interface Requirements . 23
5.7.4.1 Void. 23
5.8 Airport CDM in Adverse Conditions - CDAC . 23
5.8.1 Background . 23
5.8.2 CDM CDAC Functional Requirements . 23
5.8.2.1 A-CDM CDAC A-CDM in adverse conditions implementation . 23
5.8.2.2 A-CDM CDAC Flight cancellations and delay . 23
5.8.2.3 A-CDM CDAC Resource availability . 23
5.8.3 CDAC Technical Requirements . 23
5.8.3.1 Void. 23
5.8.4 CDAC Interface Requirements . 23
5.8.4.1 Void. 23
Annex SA (normative): Standards Annex . 24
SA.1 Correspondence between this European Standard and the Single European Sky Interoperability
Regulation (as amended) for A-CDM . 24
ETSI
5 ETSI EN 303 212 V1.1.1 (2010-06)
Annex A (normative): Checklist . 35
A.1 Interoperability Regulation Annex II Essential Requirements; Part A: General requirements . 36
A.2 Interoperability Regulation Annex II Essential Requirements Part B: Specific requirements . 43
A.2.1 Systems and procedures for airspace management. 43
A.2.2 Systems and procedures for air traffic flow management . 43
A.2.3 Systems and procedures for air traffic services . 44
A.2.3.1 Flight data processing systems. 44
A.2.3.2 Surveillance data processing systems . 50
A.2.3.3 Human-machine interface systems . 51
A.2.4 Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air
communications . 52
A.2.5 Navigation systems and procedures . 53
A.2.6 Surveillance systems and procedures . 53
A.2.7 Systems and procedures for aeronautical information services . 53
A.2.8 Systems and procedures for the use of meteorological information . 54
Annex B (informative): The EN title in the official languages . 55
Annex C (informative): Bibliography . 56
History . 57

ETSI
6 ETSI EN 303 212 V1.1.1 (2010-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Aeronautics
(AERO).
The present document has been produced by ETSI in response to European Commission mandate M/390 for the
Interoperability of the European Air Traffic Management Network.
The present document has been developed in cooperation with Eurocae for compliance with the Essential Requirements
of the Single European Sky Interoperability Regulation [i.1] and/or requirements given in implementing rules for the
Single European Sky Interoperability Regulation.
The presumption of conformity which is linked to the full application of the present document can only be claimed after
the present document has been listed in the Official Journal of the European Union as Community Specification.
General and specific requirements for presumption of conformity to SES Interoperability Regulation 552/2004 as
amended by Regulation 1070/2009 are given in the normative annexes of the present document.
NOTE: Other requirements and other EU Regulations and/or Directives may be applicable to the product(s)
falling within the scope of the present document.

National transposition dates
Date of adoption of this EN: 17 May 2010
Date of latest announcement of this EN (doa): 31 August 2010
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2011
Date of withdrawal of any conflicting National Standard (dow): 29 February 2012

Introduction
The European Union launched the Legislation "Single European Sky" (SES) in 2002 which was adopted in 2004 and
amended by Regulation (EC) No 1070/2009 [i.1].
The SES legislation is based on a framework of 4 regulations, which includes the Interoperability Regulation [i.1]. The
objective of the Interoperability Regulation is to ensure interoperability of the European Air Traffic Management
Network (EATMN) consistent with air navigation services. Under this regulation, the use of a European Standard
referenced in the Official Journal of the European Union as Community Specification (CS) is a means of compliance to
the essential requirements of the Regulation and/or the relevant implementing rules for interoperability.
ETSI
7 ETSI EN 303 212 V1.1.1 (2010-06)
The present document takes into account the Council Decision 2009/320/EC [i.4] endorsing the European Air Traffic
Management Master Plan of the Single European Sky ATM Research (SESAR) project [i.4].
Figure 1 shows the high level relationship between the Eurocontrol and Eurocae which were developed in parallel.
EUROCONTROL EUROCAE
Documents Documents
System Requirements
Concept of Operations
Document (ED-141)
Functional
Interface Definition
Requirements
Document (ED-145)
Document
Implementation
Test and Validation
Manual
Document (ED-146)
Figure 1: Eurocontrol and Eurocae Document Relationship
ETSI
8 ETSI EN 303 212 V1.1.1 (2010-06)
1 Scope
The present document is applicable to Air Traffic Management Airport Collaborative Decision Making (A-CDM).
The present document addresses the specific roles, responsibilities, procedures, systems and interfaces needed to fulfil
the Airport CDM (A-CDM) Operating Concept as requested by Mandate M/390 of the European Commission. It
references existing documentation where necessary to clarify the more detailed aspects of a procedure or system
implementation requirement to avoid unnecessary repetition.
Airport Collaborative Decision making (A-CDM) is about improving the way operational partners at airports and
European ATFCM (Air Traffic Flow and Capacity Management, Air Traffic Control, Airlines, Ground Handling
Agents/Units and Airports) work together at an operational level.
A-CDM allows an Airport CDM partner to make the right decisions for a flight during the whole Airport CDM process
in collaboration with other Airport CDM partners, knowing their preferences and constraints and the actual and
predicted situation. The decision making by the Airport CDM partners is dependent upon the sharing of accurate and
timely information and upon adapted Airport CDM procedures, mechanisms and tools.
Any software elements related to the software assurance level of an A-CDM System are outside of the scope of the
present document. As such the essential requirements of the Interoperability Regulation are not considered for software
elements within the present document.
The present document does not give a presumption of conformity related to maintenance requirements, safety,
civil/military coordination or environmental constraints.
NOTE: For these ERs, please refer to the Air Navigation Service Provider procedures.
Requirements in the present document which refer to "should" statements or recommendations in the normatively
referenced material (clause 2.1) are to be interpreted as fully normative ("shall") for the purpose of compliance with the
present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] Eurocontrol: "Airport CDM Operational Concept Document" (Version 3.0, Sept 2006).
NOTE: See figure 1.
[2] Eurocontrol: "Airport CDM Functional Requirements Document" (Version 4.0 May 2009).
NOTE: See figure 1.
[3] Eurocontrol: "CFMU DPI Implementation Guide" (Version 1.3).
NOTE: See figure 1.
ETSI
9 ETSI EN 303 212 V1.1.1 (2010-06)
[4] Eurocontrol: "CFMU Flight Progress Messages" (Version 1.6).
NOTE: See figure 1.
[5] Eurocae: "Minimum Technical Specification for the Airport Collaborative Decision Making
(Airport-CDM)" - ED141 - (Version 1, October 2008).
NOTE: See figure 1.
[6] Eurocae: "Airport-CDM Interface Specification" - ED145 - (Version 1, October 2008).
NOTE: See figure 1.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] Regulation (EC) No 552/2004 of the European Parliament and of the Council of 10 March 2004 on
the interoperability of the European Air Traffic Management network (the Interoperability
Regulation), OJ L 96, 31.03.2004 p.26 as amended by Regulation (EC) No 1070/2009, OJ L 300,
14.11.2009 p.34.
[i.2] Eurocontrol: "Airport CDM Implementation Manual" (Version 3).
NOTE: See figure 1.
[i.3] Regulation (EC) No 549/2004 of the European Parliament and of the Council of 10 March 2004
laying down the framework for the creation of the single European sky (the Framework
Regulation), OJ L 96, 31.03.2004 p.1 as amended by Regulation (EC) No 1070/2009, OJ L 300,
14.11.2009 p.34.
[i.4] Council Decision 2009/320/EC endorsing the European Air Traffic Management Master Plan of
the Single European Sky ATM Research (SESAR) project, 30.03.2009 published in OJ L95, p.41,
9.4.2009.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in the Framework Regulation [i.3],
Interoperability Regulation [i.1], in the Functional Requirements Document [2] and the following apply:
ground handling: covers a complex series of processes that are required to separate an aircraft from its load
(passengers, baggage, cargo and mail) on arrival and combine it with its load prior to departure
NOTE: Source: www.iata.org.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in Functional Requirements Document [2] and the
following apply:
A-CDM Airport CDM
ACIS Airport CDM Information Sharing
ACISP Airport CDM Information Sharing Platform
ATC Air Traffic Control
ATFCM Air Traffic Flow and Capacity Management
ATFM Air Traffic Flow Management
ATM Air Traffic Management
ETSI
10 ETSI EN 303 212 V1.1.1 (2010-06)
CDAC CDM in Adverse Conditions
CDM Collaborative Decision Making
CEN Comité Européen de Normalization
CFMU Central Flow Management Unit
COFU COllaborative management of Flight Updates
CPDS Collaborative Pre-Departure Sequence
CS Community Specifications
CTOT Calculated Take Off Time (CFMU)
CTRP CDM Turn-Round Process
DPI Departure Planning Information message
EATMN European Air Traffic Management Network
EC European Community
EDDM Munich International Airport
EEC EUROCONTROL Experimental Centre
EEZT Estimated End of De-icing Time
ER Essential Requirement
ERZT Estimated Ready for De-icing Time
ETSI European Telecommunications Standards Institute
EU European Union
EUROCAE EURopean Organization for Civil Aviation Equipment
EUROCONTROL European Organization for the Safety of Air Navigation
FUM Flight Update Message
HMI Human-Machine Interface
IATA International Air Transport Association
ICAO International Civil Aviation Organization
IPR Intellectual Property Rights
MST Milestone
SES Single European Sky
TMA Terminal Manoeuvring Area
TOBT Target Off-Block Time
TSAT Target Start-Up Approval Time
TTOT Target Take Off Time
VTTC Variable Taxi Time Calculation
ETSI
11 ETSI EN 303 212 V1.1.1 (2010-06)
4 Role, Responsibility and Interrelation requirements
All parties listed in the following table shall comply with the requirements of the present document related to their
specific role within the Airport CDM process. Collectively, the parties below are referred to within the present
document as the Airport CDM Partners. The column "interrelation with respect to the present document" of the
following table has to be considered as the minimum requirements. Further relations may differ and depend on local
Airport CDM Partners responsibilities.
Ref Role Responsibility Interrelation with respect to the
present document
4.1 Air Traffic Control (ATC) A civil or military unit responsible for ATC needs:
providing Air Traffic Control services. In 1. Updated CDM situational
case of Airport CDM it is mainly the Air information such as planned,
Traffic Control Tower at the CDM Airport. TOBT, Gate/stand number.
ATC provides:
2. Updated planned, estimated
and actual landing, in-blocks,
TSAT and TTOT.
4.2 Airport Operations Airport Operations is an organization Airport Operations needs:
providing Airport Management, Airport 3. Updated CDM situational
Traffic Operations Centre, and Stand & information such as planned,
Gate Management.
estimated and actual landing,
in-blocks, TOBT, TSAT and
TTOT.
Airport Operations provide:
4. Airport Schedule information,
Airport resources allocation.
4.3 Ground handling agents Ground Handling can provide a subset of Ground Handling needs:
the data normally delivered by the 5. Updated CDM situational
Aircraft Operator, depending on the information such as planned,
agreement between the particular Aircraft estimated and actual landing,
Operator and Ground Handling Agents in-blocks, TSAT and TTOT.
as mentioned above. Ground Handling can provide:
6. Flight Plan and other data
related to the flight, planned,
estimated and actual times
related to progress of
turn-around such as TOBT.
4.4 Aircraft Operator A person, organization or enterprise
Aircraft Operations need:
engaged in, or offering to engage in, an 7. Updated CDM situational
aircraft operation. This includes the flight information such as planned,
operator or a nominated representative. estimated and actual landing,
in-blocks, TSAT and TTOT.
Aircraft Operations provide:
8. Flight Plan and other data
related to the flight, planned,
estimated and actual times
related to progress of
turn-around such as TOBT.
4.5 Eurocontrol Central Flow CFMU provides flight plan data and ATFCM needs:
Management Unit (CFMU) ATFCM data. Depending on 9. Departure Planning
local/national implementation,
Information (DPIs).
information to and from the CFMU may ATFCM provides:
pass through the ATC system. 10. Flight Plan Data, Calculated
Take-off Times (Departure
slots), Flight Update
Messages (FUM).
4.6 De Icing Operations A person or organization which provides De-icing Operations needs:
all services related to the de icing of an 11. Updated information about
aircraft. aircraft requesting de-icing and
the ERZT and TSAT.
De-icing Operations can provide:
12. Status of De-icing for the
particular aircraft.
13. Prediction of EEZT (Estimated
End of De-icing Time).
ETSI
12 ETSI EN 303 212 V1.1.1 (2010-06)
5 Functional, Technical, Interface and Validation
Requirements
5.1 Introduction
This clause describes the essential functional, technical and interface requirements associated with implementing an
A-CDM. Each A-CDM concept element is formed of at least one functional requirement. All requirements have an
associated test and validation requirement which describes the method of demonstrating compliance to the present
document.
5.1.1 Test and validation methods
The methods of Inspection, Demonstration and Analysis are chosen as suitable for showing compliance to each specific
functional, technical and interface requirement. The following table provides guidance for each method:
• Inspection:
- Does the system under test embody the expected characteristics as described within the requirement?
• Demonstration:
- Does the system under test produce the output required?
• Analysis:
- Does the system under test provide calculated results or operate in accordance to performance values as
required?
5.2 Airport CDM Elements
The required Airport CDM capabilities have been grouped into key elements and shall be met as defined in Airport
CDM Operational Concept Document [1], and Functional Requirements Document [2], with regard to:
• Airport CDM - Information Sharing - ACIS.
• Airport CDM - Collaborative Turn-Round Process - CTRP.
• Airport CDM - Variable Taxi Time Calculation - VTTC.
• Airport CDM - Collaborative Management of Flight Updates - COFU.
• Airport CDM - Collaborative Pre-Departure Sequence - CPDS.
• Airport CDM - CDM in Adverse Conditions - CDAC.
5.3 Airport CDM Information Sharing - ACIS
5.3.1 Background
The Airport CDM Information Sharing (ACIS) provides the overall environment through which Airport CDM Partners
can interact with shared information securely, with the assurance that data is accurate, relevant, timely and authoritative.
The ACIS is the foundation for implementing all remaining A-CDM Elements. There are two purposes of the ACIS;
firstly it provides a consistent display and security approach for all of the A-CDM Elements, and secondly it creates the
environment for the sharing of all relevant events. This clause details the functional, technical, interface and validation
requirements associated with the ACIS Element.
ETSI
13 ETSI EN 303 212 V1.1.1 (2010-06)
5.3.2 ACIS Functional Requirements
5.3.2.1 ACIS Display of identical information
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Display of identical information at all working positions in accordance with Requirements 20 and 230 within
the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.2 ACIS User access
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Positive identification, validation and authorization of users with regard to data entry and modification in
accordance with Requirements 30, 40, 50 and 60 within the Functional Requirements Document [2], and shall
be tested and validated by demonstration.
5.3.2.3 Alert messaging and handling
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Provision and handling of alert messages in accordance with Requirements 90, 100, 800, 810 and 820 within
the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.4 ACIS Manual data entry
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Manual data entry and modification of system parameters in accordance with Requirements 110 and 120
within the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.5 ACIS Flight information sharing
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Collection, collation, correlation and distribution of relevant arriving and departing flight information to and
from all A-CDM Partners in accordance with Requirements 210, 220, 230, 240, 250, 530, 540, 550, 570 and
780 within the Functional Requirements Document [2], and shall be tested and validated by demonstration and
analysis.
5.3.2.6 ACIS Aeronautical and meteorological information sharing
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Access to aeronautical and meteorological information relevant to A-CDM Partners in accordance with
Requirement 270 within the Functional Requirements Document [2], and shall be tested and validated by
demonstration.
5.3.2.7 ACIS Archiving
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Archiving capability in accordance with Requirements 280, 290 and 310 within the Functional Requirements
Document [2], and shall be tested and validated by demonstration.
ETSI
14 ETSI EN 303 212 V1.1.1 (2010-06)
5.3.2.8 ACIS Filtering of information
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Filtering of information for onward processing by originator and timeliness in accordance with Requirements
320, 330, 380, 390 and 730 within the Functional Requirements Document [2], and shall be tested and
validated by demonstration and analysis.
5.3.3 ACIS Technical Requirements
5.3.3.1 ACIS Data validation
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Validation of data appropriate to the known phase of flight in accordance with Requirement ED141-0120
within the Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and
validated by demonstration.
5.3.3.2 ACIS Data protection
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Ensuring that commercially sensitive information remains confidential and that information presented to users
is relevant in accordance with Requirement ED141-0790 within the Minimum Technical Specification for the
Airport CDM Systems [5], and shall be tested and validated by demonstration.
5.3.3.3 ACIS Parameter and performance supervision
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Capability for operational and technical supervisors to add, modify and monitor platform parameters and
performance in accordance with Requirements ED141-0010, ED141-0020, ED141-0060, ED141-0061,
ED141-0064, ED141-0065, ED141-0066 and ED141-0068 within the Minimum Technical Specification for
the Airport CDM Systems [5], and shall be tested and validated by demonstration.
5.3.3.4 ACIS Input data prioritization
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Prioritization of data sources in accordance with Requirement 730 within the Functional Requirements
Document [2] and ED141-0063 within the Minimum Technical Specification for the Airport CDM
Systems [5], and shall be tested and validated by demonstration.
5.3.3.5 ACIS System time
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• System time reference and accuracy in accordance with Requirements ED141-0870 and ED141-0895 within
the Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and validated by
demonstration and analysis.
5.3.3.6 ACIS Data timeliness
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Timeliness of information flows between Partners in accordance with Requirement ED141-0900 within the
Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and validated by
demonstration and analysis.
ETSI
15 ETSI EN 303 212 V1.1.1 (2010-06)
5.3.3.7 ACIS System availability
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Local agreement of system availability targets with Partners in accordance with Requirement ED141-0930
within the Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and
validated by demonstration.
5.3.3.8 ACIS System capacity
Where Airport CDM is implemente
...

SLOVENSKI STANDARD
01-julij-2010
6RGHORYDOQRRGORþDQMHQDOHWDOLãþLK$&'06SHFLILNDFLMD6NXSQRVWLY8UHGEL(&
RPHGREUDWRYDOQRVWLQDHQRWQHPHYURSVNHPQHEX
Airport Collaborative Decision Making (A-CDM) - Community Specification for application
under the Single European Sky Interoperability Regulation EC 552/2004
Ta slovenski standard je istoveten z: EN 303 212 Version 1.1.1
ICS:
03.220.50 =UDþQLWUDQVSRUW Air transport
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Airport Collaborative Decision Making (A-CDM);
Community Specification for application under the
Single European Sky Interoperability Regulation EC 552/2004

2 ETSI EN 303 212 V1.1.1 (2010-06)

Reference
DEN/AERO-00002
Keywords
air traffic management, aeronautical,
interoperability
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2010.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
LTE™ is a Trade Mark of ETSI currently being registered
for the benefit of its Members and of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI EN 303 212 V1.1.1 (2010-06)
Contents
Intellectual Property Rights . 6
Foreword . 6
Introduction . 6
1 Scope . 8
2 References . 8
2.1 Normative references . 8
2.2 Informative references . 9
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 Role, Responsibility and Interrelation requirements . 11
5 Functional, Technical, Interface and Validation Requirements . 12
5.1 Introduction . 12
5.1.1 Test and validation methods . 12
5.2 Airport CDM Elements . 12
5.3 Airport CDM Information Sharing - ACIS . 12
5.3.1 Background . 12
5.3.2 ACIS Functional Requirements . 13
5.3.2.1 ACIS Display of identical information . 13
5.3.2.2 ACIS User access . 13
5.3.2.3 Alert messaging and handling . 13
5.3.2.4 ACIS Manual data entry . 13
5.3.2.5 ACIS Flight information sharing . 13
5.3.2.6 ACIS Aeronautical and meteorological information sharing . 13
5.3.2.7 ACIS Archiving . 13
5.3.2.8 ACIS Filtering of information . 14
5.3.3 ACIS Technical Requirements . 14
5.3.3.1 ACIS Data validation . 14
5.3.3.2 ACIS Data protection . 14
5.3.3.3 ACIS Parameter and performance supervision . 14
5.3.3.4 ACIS Input data prioritization . 14
5.3.3.5 ACIS System time . 14
5.3.3.6 ACIS Data timeliness . 14
5.3.3.7 ACIS System availability . 15
5.3.3.8 ACIS System capacity. 15
5.3.4 ACIS Interface Requirements . 15
5.3.4.1 ACIS Flight identification . 15
5.3.4.2 ACIS Message formatting . 15
5.3.4.3 ACIS Data source identification . 15
5.3.4.4 ACIS Information exchange. 15
5.3.4.5 ACIS Event identification . 15
5.3.4.6 ACIS Duration parameters . 16
5.3.4.7 ACIS Airport resources identification . 16
5.3.4.8 ACIS Alert identification . 16
5.3.4.9 ACIS Key flight information. 16
5.4 Airport CDM Collaborative Turn-Round Process - CTRP . 16
5.4.1 Background . 16
5.4.2 CTRP Functional Requirements . 17
5.4.2.1 A-CDM CTRP Milestone approach . 17
5.4.2.2 A-CDM CTRP Milestone processing. 17
5.4.2.3 A-CDM CTRP Milestone updating . 17
5.4.2.4 A-CDM CTRP Operational alerting. 17
5.4.3 CTRP Technical Requirements . 18
ETSI
4 ETSI EN 303 212 V1.1.1 (2010-06)
5.4.3.1 Void. 18
5.4.4 CTRP Interface Requirements . 18
5.4.4.1 Void. 18
5.5 Airport CDM Variable Taxi Time Calculation - VTTC . 18
5.5.1 Background . 18
5.5.2 VTTC Functional Requirements . 18
5.5.2.1 A-CDM VTTC Variable taxi time calculation implementation . 18
5.5.2.2 A-CDM VTTC Automatic taxi time calculation and Update . 18
5.5.2.3 A-CDM VTTC Data timeliness . 18
5.5.2.4 A-CDM VTTC Input data . 18
5.5.2.5 A-CDM VTTC Methods . 19
5.5.3 VTTC Technical Requirements . 19
5.5.3.1 Void. 19
5.5.4 VTTC Interface Requirements . 19
5.5.4.1 Void. 19
5.6 Airport CDM Collaborative Management of Flight Updates - COFU . 19
5.6.1 Background . 19
5.6.2 COFU Functional Requirements . 19
5.6.2.1 A-CDM COFU Collaborative Management of Flight Updates Implementation . 19
5.6.2.2 A-CDM COFU Data timeliness . 19
5.6.2.3 A-CDM COFU Data Operations . 19
5.6.2.4 A-CDM COFU Message processing . 20
5.6.2.4.1 A-CDM COFU Message processing - Generic DPI process . 20
5.6.2.4.2 A-CDM COFU Message processing - Early DPI process . 20
5.6.2.4.3 A-CDM COFU Message processing - Target DPI process . 20
5.6.2.4.4 A-CDM COFU Message processing - ATC DPI process . 20
5.6.2.4.5 A-CDM COFU Message processing - Cancel DPI process . 20
5.6.2.4.6 A-CDM COFU Message processing - Sequence of DPI messages . 21
5.6.2.5 A-CDM COFU Message Content . 21
5.6.3 COFU Technical Requirements . 21
5.6.3.1 Void. 21
5.6.4 COFU Interface Requirements . 21
5.6.4.1 A-CDM COFU Collaborative Management of Flight Updates Implementation . 21
5.6.4.2 A-CDM COFU Data item identifier . 21
5.6.4.3 A-CDM COFU Data format . 21
5.6.4.4 A-CDM COFU Quality . 22
5.7 Airport CDM Collaborative Pre-Departure Sequence - CPDS. 22
5.7.1 Background . 22
5.7.2 CPDS Functional Requirements . 22
5.7.2.1 A-CDM CPDS Collaborative Pre-Departure Sequence Implementation . 22
5.7.2.2 A-CDM CPDS Distribution and Display . 22
5.7.2.3 A-CDM CPDS TSAT calculation . 22
5.7.3 CPDS Technical Requirements . 23
5.7.3.1 Void. 23
5.7.4 CPDS Interface Requirements . 23
5.7.4.1 Void. 23
5.8 Airport CDM in Adverse Conditions - CDAC . 23
5.8.1 Background . 23
5.8.2 CDM CDAC Functional Requirements . 23
5.8.2.1 A-CDM CDAC A-CDM in adverse conditions implementation . 23
5.8.2.2 A-CDM CDAC Flight cancellations and delay . 23
5.8.2.3 A-CDM CDAC Resource availability . 23
5.8.3 CDAC Technical Requirements . 23
5.8.3.1 Void. 23
5.8.4 CDAC Interface Requirements . 23
5.8.4.1 Void. 23
Annex SA (normative): Standards Annex . 24
SA.1 Correspondence between this European Standard and the Single European Sky Interoperability
Regulation (as amended) for A-CDM . 24
ETSI
5 ETSI EN 303 212 V1.1.1 (2010-06)
Annex A (normative): Checklist . 35
A.1 Interoperability Regulation Annex II Essential Requirements; Part A: General requirements . 36
A.2 Interoperability Regulation Annex II Essential Requirements Part B: Specific requirements . 43
A.2.1 Systems and procedures for airspace management. 43
A.2.2 Systems and procedures for air traffic flow management . 43
A.2.3 Systems and procedures for air traffic services . 44
A.2.3.1 Flight data processing systems. 44
A.2.3.2 Surveillance data processing systems . 50
A.2.3.3 Human-machine interface systems . 51
A.2.4 Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air
communications . 52
A.2.5 Navigation systems and procedures . 53
A.2.6 Surveillance systems and procedures . 53
A.2.7 Systems and procedures for aeronautical information services . 53
A.2.8 Systems and procedures for the use of meteorological information . 54
Annex B (informative): The EN title in the official languages . 55
Annex C (informative): Bibliography . 56
History . 57

ETSI
6 ETSI EN 303 212 V1.1.1 (2010-06)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Technical Committee Aeronautics
(AERO).
The present document has been produced by ETSI in response to European Commission mandate M/390 for the
Interoperability of the European Air Traffic Management Network.
The present document has been developed in cooperation with Eurocae for compliance with the Essential Requirements
of the Single European Sky Interoperability Regulation [i.1] and/or requirements given in implementing rules for the
Single European Sky Interoperability Regulation.
The presumption of conformity which is linked to the full application of the present document can only be claimed after
the present document has been listed in the Official Journal of the European Union as Community Specification.
General and specific requirements for presumption of conformity to SES Interoperability Regulation 552/2004 as
amended by Regulation 1070/2009 are given in the normative annexes of the present document.
NOTE: Other requirements and other EU Regulations and/or Directives may be applicable to the product(s)
falling within the scope of the present document.

National transposition dates
Date of adoption of this EN: 17 May 2010
Date of latest announcement of this EN (doa): 31 August 2010
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 28 February 2011
Date of withdrawal of any conflicting National Standard (dow): 29 February 2012

Introduction
The European Union launched the Legislation "Single European Sky" (SES) in 2002 which was adopted in 2004 and
amended by Regulation (EC) No 1070/2009 [i.1].
The SES legislation is based on a framework of 4 regulations, which includes the Interoperability Regulation [i.1]. The
objective of the Interoperability Regulation is to ensure interoperability of the European Air Traffic Management
Network (EATMN) consistent with air navigation services. Under this regulation, the use of a European Standard
referenced in the Official Journal of the European Union as Community Specification (CS) is a means of compliance to
the essential requirements of the Regulation and/or the relevant implementing rules for interoperability.
ETSI
7 ETSI EN 303 212 V1.1.1 (2010-06)
The present document takes into account the Council Decision 2009/320/EC [i.4] endorsing the European Air Traffic
Management Master Plan of the Single European Sky ATM Research (SESAR) project [i.4].
Figure 1 shows the high level relationship between the Eurocontrol and Eurocae which were developed in parallel.
EUROCONTROL EUROCAE
Documents Documents
System Requirements
Concept of Operations
Document (ED-141)
Functional
Interface Definition
Requirements
Document (ED-145)
Document
Implementation
Test and Validation
Manual
Document (ED-146)
Figure 1: Eurocontrol and Eurocae Document Relationship
ETSI
8 ETSI EN 303 212 V1.1.1 (2010-06)
1 Scope
The present document is applicable to Air Traffic Management Airport Collaborative Decision Making (A-CDM).
The present document addresses the specific roles, responsibilities, procedures, systems and interfaces needed to fulfil
the Airport CDM (A-CDM) Operating Concept as requested by Mandate M/390 of the European Commission. It
references existing documentation where necessary to clarify the more detailed aspects of a procedure or system
implementation requirement to avoid unnecessary repetition.
Airport Collaborative Decision making (A-CDM) is about improving the way operational partners at airports and
European ATFCM (Air Traffic Flow and Capacity Management, Air Traffic Control, Airlines, Ground Handling
Agents/Units and Airports) work together at an operational level.
A-CDM allows an Airport CDM partner to make the right decisions for a flight during the whole Airport CDM process
in collaboration with other Airport CDM partners, knowing their preferences and constraints and the actual and
predicted situation. The decision making by the Airport CDM partners is dependent upon the sharing of accurate and
timely information and upon adapted Airport CDM procedures, mechanisms and tools.
Any software elements related to the software assurance level of an A-CDM System are outside of the scope of the
present document. As such the essential requirements of the Interoperability Regulation are not considered for software
elements within the present document.
The present document does not give a presumption of conformity related to maintenance requirements, safety,
civil/military coordination or environmental constraints.
NOTE: For these ERs, please refer to the Air Navigation Service Provider procedures.
Requirements in the present document which refer to "should" statements or recommendations in the normatively
referenced material (clause 2.1) are to be interpreted as fully normative ("shall") for the purpose of compliance with the
present document.
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are necessary for the application of the present document.
[1] Eurocontrol: "Airport CDM Operational Concept Document" (Version 3.0, Sept 2006).
NOTE: See figure 1.
[2] Eurocontrol: "Airport CDM Functional Requirements Document" (Version 4.0 May 2009).
NOTE: See figure 1.
[3] Eurocontrol: "CFMU DPI Implementation Guide" (Version 1.3).
NOTE: See figure 1.
ETSI
9 ETSI EN 303 212 V1.1.1 (2010-06)
[4] Eurocontrol: "CFMU Flight Progress Messages" (Version 1.6).
NOTE: See figure 1.
[5] Eurocae: "Minimum Technical Specification for the Airport Collaborative Decision Making
(Airport-CDM)" - ED141 - (Version 1, October 2008).
NOTE: See figure 1.
[6] Eurocae: "Airport-CDM Interface Specification" - ED145 - (Version 1, October 2008).
NOTE: See figure 1.
2.2 Informative references
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] Regulation (EC) No 552/2004 of the European Parliament and of the Council of 10 March 2004 on
the interoperability of the European Air Traffic Management network (the Interoperability
Regulation), OJ L 96, 31.03.2004 p.26 as amended by Regulation (EC) No 1070/2009, OJ L 300,
14.11.2009 p.34.
[i.2] Eurocontrol: "Airport CDM Implementation Manual" (Version 3).
NOTE: See figure 1.
[i.3] Regulation (EC) No 549/2004 of the European Parliament and of the Council of 10 March 2004
laying down the framework for the creation of the single European sky (the Framework
Regulation), OJ L 96, 31.03.2004 p.1 as amended by Regulation (EC) No 1070/2009, OJ L 300,
14.11.2009 p.34.
[i.4] Council Decision 2009/320/EC endorsing the European Air Traffic Management Master Plan of
the Single European Sky ATM Research (SESAR) project, 30.03.2009 published in OJ L95, p.41,
9.4.2009.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in the Framework Regulation [i.3],
Interoperability Regulation [i.1], in the Functional Requirements Document [2] and the following apply:
ground handling: covers a complex series of processes that are required to separate an aircraft from its load
(passengers, baggage, cargo and mail) on arrival and combine it with its load prior to departure
NOTE: Source: www.iata.org.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in Functional Requirements Document [2] and the
following apply:
A-CDM Airport CDM
ACIS Airport CDM Information Sharing
ACISP Airport CDM Information Sharing Platform
ATC Air Traffic Control
ATFCM Air Traffic Flow and Capacity Management
ATFM Air Traffic Flow Management
ATM Air Traffic Management
ETSI
10 ETSI EN 303 212 V1.1.1 (2010-06)
CDAC CDM in Adverse Conditions
CDM Collaborative Decision Making
CEN Comité Européen de Normalization
CFMU Central Flow Management Unit
COFU COllaborative management of Flight Updates
CPDS Collaborative Pre-Departure Sequence
CS Community Specifications
CTOT Calculated Take Off Time (CFMU)
CTRP CDM Turn-Round Process
DPI Departure Planning Information message
EATMN European Air Traffic Management Network
EC European Community
EDDM Munich International Airport
EEC EUROCONTROL Experimental Centre
EEZT Estimated End of De-icing Time
ER Essential Requirement
ERZT Estimated Ready for De-icing Time
ETSI European Telecommunications Standards Institute
EU European Union
EUROCAE EURopean Organization for Civil Aviation Equipment
EUROCONTROL European Organization for the Safety of Air Navigation
FUM Flight Update Message
HMI Human-Machine Interface
IATA International Air Transport Association
ICAO International Civil Aviation Organization
IPR Intellectual Property Rights
MST Milestone
SES Single European Sky
TMA Terminal Manoeuvring Area
TOBT Target Off-Block Time
TSAT Target Start-Up Approval Time
TTOT Target Take Off Time
VTTC Variable Taxi Time Calculation
ETSI
11 ETSI EN 303 212 V1.1.1 (2010-06)
4 Role, Responsibility and Interrelation requirements
All parties listed in the following table shall comply with the requirements of the present document related to their
specific role within the Airport CDM process. Collectively, the parties below are referred to within the present
document as the Airport CDM Partners. The column "interrelation with respect to the present document" of the
following table has to be considered as the minimum requirements. Further relations may differ and depend on local
Airport CDM Partners responsibilities.
Ref Role Responsibility Interrelation with respect to the
present document
4.1 Air Traffic Control (ATC) A civil or military unit responsible for ATC needs:
providing Air Traffic Control services. In 1. Updated CDM situational
case of Airport CDM it is mainly the Air information such as planned,
Traffic Control Tower at the CDM Airport. TOBT, Gate/stand number.
ATC provides:
2. Updated planned, estimated
and actual landing, in-blocks,
TSAT and TTOT.
4.2 Airport Operations Airport Operations is an organization Airport Operations needs:
providing Airport Management, Airport 3. Updated CDM situational
Traffic Operations Centre, and Stand & information such as planned,
Gate Management.
estimated and actual landing,
in-blocks, TOBT, TSAT and
TTOT.
Airport Operations provide:
4. Airport Schedule information,
Airport resources allocation.
4.3 Ground handling agents Ground Handling can provide a subset of Ground Handling needs:
the data normally delivered by the 5. Updated CDM situational
Aircraft Operator, depending on the information such as planned,
agreement between the particular Aircraft estimated and actual landing,
Operator and Ground Handling Agents in-blocks, TSAT and TTOT.
as mentioned above. Ground Handling can provide:
6. Flight Plan and other data
related to the flight, planned,
estimated and actual times
related to progress of
turn-around such as TOBT.
4.4 Aircraft Operator A person, organization or enterprise
Aircraft Operations need:
engaged in, or offering to engage in, an 7. Updated CDM situational
aircraft operation. This includes the flight information such as planned,
operator or a nominated representative. estimated and actual landing,
in-blocks, TSAT and TTOT.
Aircraft Operations provide:
8. Flight Plan and other data
related to the flight, planned,
estimated and actual times
related to progress of
turn-around such as TOBT.
4.5 Eurocontrol Central Flow CFMU provides flight plan data and ATFCM needs:
Management Unit (CFMU) ATFCM data. Depending on 9. Departure Planning
local/national implementation,
Information (DPIs).
information to and from the CFMU may ATFCM provides:
pass through the ATC system. 10. Flight Plan Data, Calculated
Take-off Times (Departure
slots), Flight Update
Messages (FUM).
4.6 De Icing Operations A person or organization which provides De-icing Operations needs:
all services related to the de icing of an 11. Updated information about
aircraft. aircraft requesting de-icing and
the ERZT and TSAT.
De-icing Operations can provide:
12. Status of De-icing for the
particular aircraft.
13. Prediction of EEZT (Estimated
End of De-icing Time).
ETSI
12 ETSI EN 303 212 V1.1.1 (2010-06)
5 Functional, Technical, Interface and Validation
Requirements
5.1 Introduction
This clause describes the essential functional, technical and interface requirements associated with implementing an
A-CDM. Each A-CDM concept element is formed of at least one functional requirement. All requirements have an
associated test and validation requirement which describes the method of demonstrating compliance to the present
document.
5.1.1 Test and validation methods
The methods of Inspection, Demonstration and Analysis are chosen as suitable for showing compliance to each specific
functional, technical and interface requirement. The following table provides guidance for each method:
• Inspection:
- Does the system under test embody the expected characteristics as described within the requirement?
• Demonstration:
- Does the system under test produce the output required?
• Analysis:
- Does the system under test provide calculated results or operate in accordance to performance values as
required?
5.2 Airport CDM Elements
The required Airport CDM capabilities have been grouped into key elements and shall be met as defined in Airport
CDM Operational Concept Document [1], and Functional Requirements Document [2], with regard to:
• Airport CDM - Information Sharing - ACIS.
• Airport CDM - Collaborative Turn-Round Process - CTRP.
• Airport CDM - Variable Taxi Time Calculation - VTTC.
• Airport CDM - Collaborative Management of Flight Updates - COFU.
• Airport CDM - Collaborative Pre-Departure Sequence - CPDS.
• Airport CDM - CDM in Adverse Conditions - CDAC.
5.3 Airport CDM Information Sharing - ACIS
5.3.1 Background
The Airport CDM Information Sharing (ACIS) provides the overall environment through which Airport CDM Partners
can interact with shared information securely, with the assurance that data is accurate, relevant, timely and authoritative.
The ACIS is the foundation for implementing all remaining A-CDM Elements. There are two purposes of the ACIS;
firstly it provides a consistent display and security approach for all of the A-CDM Elements, and secondly it creates the
environment for the sharing of all relevant events. This clause details the functional, technical, interface and validation
requirements associated with the ACIS Element.
ETSI
13 ETSI EN 303 212 V1.1.1 (2010-06)
5.3.2 ACIS Functional Requirements
5.3.2.1 ACIS Display of identical information
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Display of identical information at all working positions in accordance with Requirements 20 and 230 within
the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.2 ACIS User access
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Positive identification, validation and authorization of users with regard to data entry and modification in
accordance with Requirements 30, 40, 50 and 60 within the Functional Requirements Document [2], and shall
be tested and validated by demonstration.
5.3.2.3 Alert messaging and handling
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Provision and handling of alert messages in accordance with Requirements 90, 100, 800, 810 and 820 within
the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.4 ACIS Manual data entry
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Manual data entry and modification of system parameters in accordance with Requirements 110 and 120
within the Functional Requirements Document [2], and shall be tested and validated by demonstration.
5.3.2.5 ACIS Flight information sharing
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Collection, collation, correlation and distribution of relevant arriving and departing flight information to and
from all A-CDM Partners in accordance with Requirements 210, 220, 230, 240, 250, 530, 540, 550, 570 and
780 within the Functional Requirements Document [2], and shall be tested and validated by demonstration and
analysis.
5.3.2.6 ACIS Aeronautical and meteorological information sharing
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Access to aeronautical and meteorological information relevant to A-CDM Partners in accordance with
Requirement 270 within the Functional Requirements Document [2], and shall be tested and validated by
demonstration.
5.3.2.7 ACIS Archiving
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Archiving capability in accordance with Requirements 280, 290 and 310 within the Functional Requirements
Document [2], and shall be tested and validated by demonstration.
ETSI
14 ETSI EN 303 212 V1.1.1 (2010-06)
5.3.2.8 ACIS Filtering of information
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Filtering of information for onward processing by originator and timeliness in accordance with Requirements
320, 330, 380, 390 and 730 within the Functional Requirements Document [2], and shall be tested and
validated by demonstration and analysis.
5.3.3 ACIS Technical Requirements
5.3.3.1 ACIS Data validation
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Validation of data appropriate to the known phase of flight in accordance with Requirement ED141-0120
within the Minimum Technical Specification for the Airport CDM Systems [5], and shall be tested and
validated by demonstration.
5.3.3.2 ACIS Data protection
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Ensuring that commercially sensitive information remains confidential and that information presented to users
is relevant in accordance with Requirement ED141-0790 within the Minimum Technical Specification for the
Airport CDM Systems [5], and shall be tested and validated by demonstration.
5.3.3.3 ACIS Parameter and performance supervision
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Capability for operational and technical supervisors to add, modify and monitor platform parameters and
performance in accordance with Requirements ED141-0010, ED141-0020, ED141-0060, ED141-0061,
ED141-0064, ED141-0065, ED141-0066 and ED141-0068 within the Minimum Technical Specification for
the Airport CDM Systems [5], and shall be tested and validated by demonstration.
5.3.3.4 ACIS Input data prioritization
Where Airport CDM is implemented, the Airport CDM Information Sharing shall be implemented with regard to:
• Prioritization of data sources in accordance with Requirement 730 within the Functional Requirements
Document [2] and ED141-0063 within the Minimum Technical Specification for the Airport CDM
Systems [5], and shall be tested and validated by demonstration.
5.3.3.5 ACIS System time
Where Airport CDM is implemented, the Airport CDM Information
...