List of Example Constituents and Standards for the CNS domain

The single European sky (SES) framework Regulation (EC Regulation No 549/2004 as amended by EC Regulation 1070/2009) defines the European Air Traffic Management network (EATMN) as a collection of eight systems enabling air navigation services.

Systems are defined as being an aggregate of airborne and ground-based constituents as well as space-based equipment.
At present, a very limited number of EATMN constituents are defined in SES implementing rules and/or Community specifications. Two are identified in implementing rules:

Other constituents are defined in the A-SMGCS Level 1 Community specification (EN 303 213-1) and the Data Link Services (DLS) System Community specification (EN 303 214).

Objective of the list

Constituents are defined as “tangible objects such as hardware and intangible objects such as software upon which the interoperability of the EATMN depends”. The objective of this material is to provide an list of typical communication, navigation and surveillance (CNS) objects that can be considered as ‘EATMN constituent’ by manufacturers (when considered within their ATM environment) or by air navigation service providers (as part of their ATM system), if they are concerned by certain requirements of the interoperability Regulation. The list provides examples and should not be considered as a complete nor exclusive. Over time, some of the listed examples may become formal constituents of future implementing rules or Community specifications.

The list was created following a top-down analysis of the standards and guidelines applicable to the CNS domain, an examination of the CNS facilities in use by two ANSPs, and a comparison of the findings. As a result, its focus is on the ground CNS domains.

This list is referred to by Section 3, Annex C and Annex D of the EUROCONTROL Guidelines on conformity assessment for the SES interoperability Regulation (EC Regulation No 552/2004 as amended by EC Regulation 1070/2009). As described in Section 3, air navigation service providers (ANSPs) will need to represent their real-world systems in terms of EATMN ‘systems’ and ‘constituents’ to which they will apply conformity assessment and it is expected that this list will facilitate that task.

Each example constituent is associated with the relevant CNS standard(s), the latter being part of the means of compliance (MoC) baseline described in Section 4.3 of the EUROCONTROL Guidelines on conformity assessment.

List Structure

Following the top-down analysis, each CNS domain is split into functional areas. For each functional area, a standards map identifies the standards applicable to the technology supporting these functional areas. As standards evolve, this map will need to be updated.

For each functional area, a table lists example constituents with a brief description, followed by a list of the relevant standards and guidelines. The indication of a relevant document does not imply that all of the requirements in the document are applicable and typically, high-level standards are shown first.

Industry standards such as the suite of internet RFCs or underlying ITU-T recommendations are mostly not shown, as they are not specific to air navigation.

In their description, some examples are marked as 'shared'. This indicates a specific area of functionality which is easily traceable to a functional area and to specific standards and requirements. However, in reality the functionality may be undertaken by a system which also performs other functions; therefore the shared example may not be a distinct constituent in its own right. For instance in the case of data recording, whilst it is necessary to record data link exchanges, voice conversations and surveillance information, this may be carried out by one shared central recording facility which encompasses all of the recording activities for several functional areas or domains.

Communication domain

List of example constituents and standards for the communications domain

For communications, only typical systems which are currently used in Europe were considered, as identified by the SESAR Definition Phase (WP2.5). Oceanic, unusual and future systems were not analysed – these criteria were used to exclude ADS-C, HFDL, VDL3, VDL4, AMS(R)S, and ACARS over HF or satellite.

Since the implementation of AIDC in Europe has not followed the ICAO ATN/OSI manual, only specifications appropriate to the European systems which are now referenced in the ICAO ATN/IPS manual are considered e.g. COTR (EC regulation 1032/2006) and FMTP (EC Regulation 633/2006).

Functional areas of the communications domain

Functional areas of the communications domain - full list (pdf)

Navigation domain

List of example constituents and standards for the navigation domain

The scope for the navigation domain was taken from the interoperability Regulation, which specifies that navigation systems shall be designed, built, maintained and operated using appropriate and validated procedures in such a way as to achieve the required horizontal and vertical navigation performance, in particular, in terms of accuracy and functional capability, for a given environment (surface, TMA, en-route), with known traffic characteristics and exploited under an agreed and validated operational concept.

The identified example constituents do not include airborne or space-based equipment; therefore GPS, Galileo and GLONASS were excluded as they have no ATM ground components. SBAS is not considered to be in scope because, although it does have ground infrastructure, this is not owned by the ANSP.

Only typical ground-based systems used in Europe were considered. This criterion was used to exclude unusual systems such as MLS. Although the interoperability Regulation covers all navigation applications and navaids, visual aids were not considered to be within scope.

Functional areas of the navigation domain

Functional areas of the navigation domain - full list (pdf)

 

Surveillance domain

List of example constituents and standards for the surveillance domain

The definition of surveillance taken from the interoperability Regulation covers ground surveillance and air-ground surveillance, but does not include air-air surveillance such as ACAS or ASAS. VDL4 and UAT were excluded as they are not widely implemented in Europe.

In addition, meteorological (MET) surveillance and AIS were not in scope.

Functional areas of the surveillance domain

Functional areas of the surveillance domain - full list (pdf)