airport-cdm-manual-2017 (1)

With this list of criteria, the six Concept Elements
are developed and defined in this document. These
Concept Elements are dependent on each other, and
hence require a recommended order of implementation.
However, local considerations, such as size and
complexity of the airport, may require simultaneous
implementation of all elements or influence the type of
element implementation e.g. sequencing on a small
airport can be done manually rather the automatically,
if this enables the airport to meet the information accuracy
requirements set in the next chapters.
Below, the list of Concept Elements is presented:
n
n
n
n
n
n
Information Sharing
Milestone Approach
Variable Taxi Time
Pre-departure Sequencing
Adverse Conditions
Collaborating Management of Flight Updates
Of the available Airport CDM Concept Elements, Information
Sharing is essential in as much as it creates
the foundation by enabling the sharing of information
and creating a common situational awareness. In addition,
it potentially brings predictability and resource
efficiency benefits. After the creation of this information
platform (see also chapter 3.2), the main priority is implementation
of the Target Off-Block Time (TOBT) by
using the Milestone Approach to improve predictability
during the turn-round process of aircraft. Together,
Information Sharing and the Milestone Approach are
the essential requirements for implementation of the
remaining Concept Elements.
2.7 Inventory for Implementation
An obvious method of minimising costs is to utilise
existing resources to the maximum extent possible,
including networks, computers, displays, etc.
è
Airport CDM elements implemented as software
applications are neither computation
intensive nor mission critical in the sense
that an ATC system is.
Existing networks and other hardware can usually be
used, minimising the need for buying new equipment.
Adding the Airport CDM elements to existing systems
can be cost effective, however it should be borne in
mind that modifying host systems may be more expensive
than building appropriate interfaces into the
software application itself.
è
n An inventory of partners’ existing systems
is required (see to Attachment 3.2)
n Appropriate resources may already be
available
2.8 Gap Analysis and Completeness
Assessment
Before commencing an implementation project, it is
recommended that each airport has a Gap Analysis
performed by EUROCONTROL or an independent
consultancy company. This analysis has the purpose
to achieve a clear vision of what is available
and what is missing within the airport partners’ technical
infrastructure (see Attachment 3.2).
è
All Airport CDM projects must commence
with the implementation of Airport CDM Information
Sharing. Other elements can be
selected and implemented either simultaneously
as one process or in the recommended
order to enable the successive elements to be
most beneficial at the location in question.
At the end of the implementation project an external
Completeness Assessment will be performed by
either EUROCONTROL or a consultancy company,
in order to recommend to Network Operations on
the exchange of DPI messages to feed the network
with airport Target Take Off Time (TTOT) predictions.
This Completeness Assessment will be conducted
2-10