scope:

PURPOSE, SCOPE, APPLICABILITY

This document sets minimum requirements on the data exchanged betwee CDM system, which is regarded hereon as a single system, and the logical elements that provide information to the system.

The intended audience includes developers of generic Airport-CDM system and developers of specific implementations for Airport-CDM systems (industry) and developers of specific implements for Airport-CDM at airports: desingners, installers, manufacturers, service providers, and users.  This document  assumes knowledge of Airport CDM.

This document descrbes the minimum requirments on the exchanged data to provide the basis for intetoperability and compatibility between different implementations of Airport CDM systems.

wherever possible this document supports freedom of design and therfore only sets requirements where considered necessary for reasons of interoperability.  For example interfaces between elements within the Airport-CDM system itself and who has the responsibility for sending the data are considered beyond the scope of this document as  they may differ from one implementation to another whilst stil  enabling the overarching requirement that logical elements be able to connect to the Airport-CDM system in a consistent manner.

It is expected that this document will be used as a basis for developing a more detailed interface design specification (such as an interface control document) that can be applied at a local level for a spefic implementation.

Chapter 1, this chapter, presents an overview of Airport CDM, the document set relating to the subject and the purpose and scope of this document.  The remainer of this chapter is chapter is dedicated to the terminology, terms, conventions, and references used.

Chapter 2, data exchange with logical elements, introduces the logical elements to the Airport-CDM system and introduces the milestones approach. The chapter concludes with the identification of interfaces per partner and milestone.

Chapter 3, data model, describes the interfaces by name and their form generic description method is used, that is compliant w at. For this, a ith the existing data exchange presentation ADEXP [6] but can also easily be transformed to XML.

Annex A contains a matrix with all Airport-CDM Data Items referenced to its type, the recommended sender, and the CDM milestone where the data item coud occur.

Requirements in this document are denoted by a unique number and pred]ceded by "IR." to represent the fact that they are Interface Requirements. The following section denotes the strength of each requirement used.