1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationDD CEN/TS 16071:2010Interoperability of FlightData Processing (Air TrafficControl Air Traffic Control)for application under theSingle European Sky Interoperability Regulation EC5
2、52/2004DD CEN/TS 16071:2010 DRAFT FOR DEVELOPMENTNational forewordThis Draft for Development is the UK implementation of CEN/TS16071:2010.This publication is not to be regarded as a British Standard.It is being issued in the Draft for Development series of publicationsand is of a provisional nature.
3、 It should be applied on thisprovisional basis, so that information and experience of its practicalapplication can be obtained.Comments arising from the use of this Draft for Developmentare requested so that UK experience can be reported to theinternational organization responsible for its conversio
4、n toan international standard. A review of this publication willbe initiated not later than 3 years after its publication by theinternational organization so that a decision can be taken on itsstatus. Notification of the start of the review period will be made inan announcement in the appropriate is
5、sue of Update Standards.According to the replies received by the end of the review period,the responsible BSI Committee will decide whether to support theconversion into an international Standard, to extend the life of theTechnical Specification or to withdraw it. Comments should be sentto the Secre
6、tary of the responsible BSI Technical Committee at BritishStandards House, 389 Chiswick High Road, London W4 4AL.The UK participation in its preparation was entrusted to TechnicalCommittee ACE/58/-/5, Panel for European Air Traffic ManagementStandardization.A list of organizations represented on thi
7、s committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. BSI 2010ISBN 978 0 580 70124 5ICS 35.240.60; 49.020Compliance with a British Standard cannot confer immunit
8、y fromlegal obligations.This Draft for Development was published under the authority ofthe Standards Policy and Strategy Committee on 31 October 2010.Amendments issued since publicationDate Text affectedDD CEN/TS 16071:2010TECHNICAL SPECIFICATION SPCIFICATION TECHNIQUE TECHNISCHE SPEZIFIKATION CEN/T
9、S 16071 September 2010 ICS 35.240.60; 49.020 English Version Interoperability of Flight Data Processing (Air Traffic Control - Air Traffic Control) for application under the Single European Sky - Interoperability Regulation EC 552/2004 Interoprabilit des systmes de traitement des donnes de vol (cont
10、rle de la circulation arienne) pour mise en oeuvre dans le cadre du rglement Ciel unique europen - Interoprabilit EC 552 2004 Interoperabilitt der Flugdatenverarbeitung (Flugverkehrskontrolle - Flugverkehrskontrolle) zur Anwendung gem der Interoperabilittsverordnung EG 552/2004 im Rahmen des Einheit
11、lichen Europischen Luftraums (SES) This Technical Specification (CEN/TS) was approved by CEN on 26 June 2010 for provisional application. The period of validity of this CEN/TS is limited initially to three years. After two years the members of CEN will be requested to submit their comments, particul
12、arly on the question whether the CEN/TS can be converted into a European Standard. CEN members are required to announce the existence of this CEN/TS in the same way as for an EN and to make the CEN/TS available promptly at national level in an appropriate form. It is permissible to keep conflicting
13、national standards in force (in parallel to the CEN/TS) until the final decision about the possible conversion of the CEN/TS into an EN is reached. CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany
14、, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and United Kingdom. EUROPEAN COMMITTEE FOR STANDARDIZATION COMIT EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG Ma
15、nagement Centre: Avenue Marnix 17, B-1000 Brussels 2010 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. CEN/TS 16071:2010: EDD CEN/TS 16071:2010CEN/TS 16071:2010 (E) 2 Contents Page Foreword 3Introduction .41 Scope 52 Normative refere
16、nces 53 Terms, definitions and abbreviations 54 FDP IOP Implementation Framework 74.1 General 74.2 Operational Framework and Behaviour 74.2.1 General 74.2.2 ICAO Operational Concept .74.2.3 SESAR Concept of Operations (CONOPS) .94.2.4 Eurocontrol Interoperability Requirements Documents. 104.3 Common
17、 environment requirements 114.4 Architectural Framework . 114.5 AIM Data Model and Services 114.6 Flight Data Model and Services . 114.7 Safety . 114.8 Middleware Services 124.9 Test and Maintenance 125 Perspectives for further development of this specification . 12Bibliography . 13DD CEN/TS 16071:2
18、010CEN/TS 16071:2010 (E) 3 Foreword This document (CEN/TS 16071:2010) has been prepared by Technical Committee CEN/TC 377 “Air Traffic Management”, the secretariat of which is held by DIN. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent r
19、ights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent rights. This Technical Specification has been prepared under a mandate given to the CEN/CENELEC/ETSI by the European Commission and developed in cooperation with EUROCAE to support Essential Requirements o
20、f the Single European Sky Interoperability Regulation 2. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to announce this Technical Specification: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estoni
21、a, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. DD CEN/TS 16071:2010CEN/TS 16071:2010 (E) 4 Introduction The European Un
22、ion launched the Legislation “Single European Sky“ (SES) in 2002 which was adopted in 2004 and largely amended in 2009. The SES legislation is based on a framework of four regulations, which include the Interoperability Regulation (EC 552/2004 as amended). The objective of the Interoperability Regul
23、ation is to ensure interoperability of the European Air Traffic Management Network (EATMN) consistent with air navigation services. The technical detail for the provision of Flight Data Processing (ATC-ATC) Interoperability is not included in the body of this document. DD CEN/TS 16071:2010CEN/TS 160
24、71:2010 (E) 5 1 Scope This Technical Specification is for the production of conformity evidence for FDP-FDP ground-based system interoperability which has to be declared by the Air Navigation Service Provider (ANSP) before putting FDP-systems into service. This Technical Specification defines the Te
25、chnical, Operational and Maintenance requirements for Flight Data Processing (ATC-ATC) system interoperability. Flight Data Processing (FDP) interoperability between ATC units is a key element to facilitate and harmonise Flight Data systems data exchanges and critical to the functioning of a harmoni
26、sed European Air Traffic Management system. FDP Interoperability can be achieved by the use of different techniques appropriate to the operational need, e.g. message exchange, replication mechanisms and data sharing. The architectural framework in which the different actors have to inter-operate is
27、of major importance to define the context in which the European Standards have to be developed. For a systematic solution to certain flight data inconsistency problems currently existing in Europe, the definition of a Flight Object (FO) is required to become a conceptual single point of reference fo
28、r flight data to be used by stakeholder systems. Interoperability of FDP (ATC-ATC) includes coordination and transfer; correlation and surveillance, facilitation of optimum routes; MTCD and resolutions; recovery support; ground-ground situation awareness and traffic management. Any software elements
29、 related to the software assurance level of a FDP System are outside of the scope of the present document. Although a consensus can be reached on the present state of the art in FDP interoperability, this state of the art is not mature enough to be put into a European Standard (EN). The European Com
30、mittee for Standardisation thus resolved to record the obtained technical consensus as the present Technical Specification, with informative status. The present document thus does not give legal presumption of conformity to any piece of European legislation. 2 Normative references The following refe
31、renced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EUROCAE ED-133, Flight Object Interoperability Specification 3 Term
32、s, definitions and abbreviations ACC Area Control Centre AIM Aeronautical Information Management ANS Air Navigation Service ANSP Air Navigation Service Provider DD CEN/TS 16071:2010CEN/TS 16071:2010 (E) 6 AOI Area of Interest AOR Area of Responsibility APP Approach ATC Air Traffic Control ATM Air Tr
33、affic Management ATSU Air Traffic Service Unit CDM Collaborative Decision Making CEN Comit Europen de Normalisation / European Committee for Standardization CS Community Specification EATMN European Air Traffic Management Network EC European Commission ESARR EUROCONTROL Safety Regulatory Requirement
34、 ESO European Standards Organisation EUROCAE European Organisation for Civil Aviation Equipment FDP Flight Data Processing FDPS Flight Data Processing System FO Flight Object FOIPS Flight Object Interoperability Proposed Standard FOS Flight Object Server ICAO International Civil Aviation Organisatio
35、n ICOG Interoperability Consultancy Group IOP Interoperability IRD Interoperability Requirements Document MTCD Common environment requirements; Architectural Framework; AIM Data Model and Services; Flight Data Model and Services; Middleware Services; Safety; Test and Maintenance. ED-133 in its entir
36、ety is relevant and shall be complied with. It contains interface definitions and sets of associated requirements (e.g. IOP-FOM-010). 4.2 Operational Framework and Behaviour 4.2.1 General Whereas the operational framework presented here is indicative of the wider ATM context, only the ATC-ATC aspect
37、s should be considered within the scope of this document. The high level operational framework for the FDP interoperability specification is provided by 14 the ICAO Global Air Traffic Management Operational Concept. It is further refined by 5 the SESAR Concept of Operations and 7 to 13 the applicabl
38、e Eurocontrol Interoperability Requirements Documents. 4.2.2 ICAO Operational Concept 4.2.2.1 General The high level operational framework for the FDP interoperability specification is provided by the 14 ICAO Global Air Traffic Management Operational Concept which describes the general principles fo
39、r Air Traffic Management together with related ATM Service Delivery Management and Information Management which drive the need for FDP Interoperability. The relevant Guiding Principles and Information Services applicable to the field of FDP Interoperability are outlined below (by 14 section referenc
40、e). 4.2.2.2 Guiding Principles (14 1.5) a) “Information. The ATM community will depend extensively on the provision of timely, relevant, accurate, accredited and quality-assured information to collaborate and make informed decisions. Sharing information on a system-wide basis will allow the ATM comm
41、unity to conduct its business and operations in a safe and efficient manner.“ b) “Collaboration. The ATM system is characterized by strategic and tactical collaboration in which the appropriate members of the ATM community participate in the definition of the types and levels of service. DD CEN/TS 1
42、6071:2010CEN/TS 16071:2010 (E) 8 Equally important, the ATM community collaborates to maximize system efficiency by sharing information, leading to dynamic and flexible decision making.“ The future ATM system will be based on the provision of integrated operational services. These services are enabl
43、ed by additional information services which describe the exchange and management of information used by the different processes and services. For FDP Interoperability the ATM Service Delivery Management and the Information Services are the main services to be considered: 1) (14 2.1.9) ATM service de
44、livery management will operate seamlessly from gate to gate for all phases of flight and across all service providers. The ATM service delivery management component will address the balance and consolidation of the decisions of the various other processes/services, as well as the time horizon at whi
45、ch, and the conditions under which, these decisions are made. Flight trajectories, intent and agreements will be important components to delivering a balance of decisions. Key conceptual changes include: i) services to be delivered by the ATM service delivery management component will be established
46、 on an as-required basis subject to ATM system design. Once established, they will be provided on an on-request basis; ii) ATM system design will be determined by collaborative decision making and system-wide safety and business cases. 2) (14 2.8.1) The ATM service delivery management function will
47、manage the balance and consolidation of the decisions of the various other processes/services, as well as the time horizon at which, and the conditions under which, these decisions are made. Services to be delivered by the ATM service delivery system will be established on an on-request basis subjec
48、t to ATM system design. ATM system design will be determined by collaborative decision making and system-wide safety and business cases. 3) (14 2.8.2) When there is a request for ATM services, the process will consist of building an agreement on the flight trajectory based on user wishes and prefere
49、nces, the constraints and opportunities related to the other services, and the information available on the operational situation. The agreement will then be the subject of monitoring. A significant deviation from the agreement, as observed or inferred from information available, will trigger a revision to the agreement or a warning to draw attention to the need to revert to the agreement. 4) (14 2.8.3) ATM service delivery management will manage the distribution of the responsibiliti
