230 likes | 438 Views
CNS/ATM Steering Group Single European Sky Regulation Overview and Progress EASA, Köln – 20. June 2007 Sven Halle EC DG TREN F2. Background. 20 April 2004: Entry into force of 4 Regulations of the European Parliament and the Council: No 549/2004: Framework
E N D
CNS/ATM Steering Group Single European Sky Regulation Overview and Progress EASA, Köln – 20. June 2007 Sven Halle EC DG TREN F2
Background 20 April 2004: Entry into forceof 4 Regulations of the European Parliament and the Council: • No 549/2004:Framework • No 550/2004:Service Provision • No 551/2004:Airspace • No 552/2004:Interoperability Publication in the Official Journal of the European Union in edition L 96 of 31 March 2004, http://europa.eu.int/eur-lex/en/archive/2004/l_09620040331en.html
Interoperability • Objective and scope • Interoperability means a set of functional, technical an operational properties required of the ATM systems in order to enable its safe, seamless and efficient operation • Interoperability between the different systems, their constituents and associated procedures of the European ATM network • Coordinated introduction of new agreed and validated concepts of operations or technology
Interoperability • Different tools • Essential Requirements (ER) • Implementing Rules (IR) • Community Specifications (CS) • Conformity Assessment
Interoperability • Essential requirements: • Seamless operation, • Safety, • Civil-military coordination, • Support of new concepts of operation, • Environmental constraints, • Principles governing the logical architecture, • Principles governing the construction of systems. Essential requirements are compulsory, reference Annex 2 of the interoperability regulation
Interoperability • Implementing rules: • Can be developed by Eurocontrol in conformity with the mandate issued by the EC • Shall determine any specific requirement that complements or refine the Essential Requirements, • Shall also describe the coordinated introduction of new, agreed and validated concepts of operation or technology, • Shall specify the conditions of implementation (including dates), • Shall be adopted by the Single Sky Committee (SSC), published in the Official Journal and are for interoperability also compulsory.
Interoperability • Community Specifications: • Are possible means of compliance and will be mandated by the EC being either • European standards (drawn up by European Standardisation Organisations CEN/CENELEC/ETSI in cooperation with EUROCAE) • Eurocontrol specifications (for operational coordination purposes) • Systems, procedures and constituents which meet Community Specifications are presumed to be compliant with mandatory rules
Content of Community Specifications • Depending on the CS development mandate, Community Specifications can contain the following elements: • Technical part • Operational part • Procedural part • Certification and/or Institutional part • Maintenance and Operation part • Implementation guidance material • Compliance matrix (Annex SA) referring to the applicable requirements in terms of (Essential Requirements and/or Implementing Rules)
Community Specification Development Process Industry Consultation Body ICB ATMSCG Air Traffic Management Standards Coordination Group CEN - CENELEC - ETSI - EUROCAE - EUROCONTROL - EASA - EC/EFTA ICB Interoperability Sub Group Interoperability Regulation 552/04 Article 4.1.a …European standards for systems or constituents, together with the relevant provisions, drawn up by European Standardisation bodies in cooperation with EUROCAE Interoperability Regulation 552/04 Article 4.1.b …Specifications drawn up by Eurocontrol on matters of operational coordination between Air Navigation Service Providers Presentation toCOMMITTEE ON « STANDARDS AND TECHNICAL REGULATIONS » (98/34 COMMITTEE) and mandate in accordance with Standardisation Directive 98/34 European Commission requests Eurocontrol to draw up specifications following the Single Sky Committee (SSC) advisory procedure in accordance with Framework Regulation 549/04 European Standardisation Organisation development (drafting and consultation) of European standards (Community Specification) and European Standardisation Organisation EN approval process (including publication) Development of Community Specifications within the Eurocontrol regulatory framework After the SSC advisory procedure, European Commission publishes references to Eurocontrol specifications in the Official Journal of the European Union European Commission publishes references to European Standards in the Official Journal of the European Union
TCAM Committee NSA Certification GND EASA Certification AIR CS Community Specification Process Overview SESAR - MASTERPLAN ICB Interoperability SG European Commission ICAO Global ATM Concept Industry Roadmap ICB RTCA & (EASTCAE) ARINC (AEEC) Global Interoprability NATO STANAG Civil Military Interoperability 98/34 Committee Single Sky Committee DG ENTR DG TREN ATMSCG Standardisation Mandate Specification Request EUROCONTROL CEN CENELEC ETSI Air Traffic Management TF191 Air Traffic Management TG25 Aeronautics Mandate Group Programme As a means of compliance with SES regulation (ERs and IRs) Task Forces Task Forces Task Forces EUROCAE WG x1 WG x2 Industry ATM ANSPs Industy Avionics Eurocontrol Airspace Users WG x3 WG x4 WG xn
CS work programme Prio 1 • ICB Interoperability Sub Group in proposed CS prioritisation and ICB/10 (Feb.06) in coordination with ATMSCG agreed that work should start on the Prio1 CSs • Single Sky Committee (Jun.06) requested Eurocontrol to develop the first set of CS (Initial Flight Plan, OLDI, ADEX-P), Eurocontrol accepted the mandate and initial plans have been returned to EC in Nov.06 • 98/34 Committee (Jul.06) agreed upon and send out mandate M/390 (SWAL, A-CDM, A-SMGCS, FDP Interoperability ATC) to ESOs, which CEN + ETSI accepted • Single Sky Committee (Sep.06) requested Eurocontrol to develop CS on Flexible Use of Airspace, Eurocontrol accepted the mandate, work started early 2007
CS work programme Prio 1 • Initial ATM mandate M/354 has been withdrawn by DG ENTR (following written consulation of 98/34 Committee in Nov.06) aligning now the new DG TREN standardisation development process • SSC (Dec.06) adopted IR on Flight Message Transfer Protocol (FMTP) with a new approach to have now a CS covering the core technical part, Eurocontrol has started to transform the FMTP CS part
CS work programme Prio 2 • Discussions (ICB Interoperability Sub Group + ATMSCG) on the Priority 2 Community Specifications started in Sep. 2006 • Clarification activities have been initiated on 4 CSs (AMAN/DMAN, Airport + ATS use of MET Data, MET Information Exchange) in Dec.06, Study results End 2007 • 98/34 Committee (Mar.07) agreed upon and send out mandate M/408 (GBAS Cat 1, APV) to ESOs in Apr.07 • 98/34 Committee agreed in written consultation process to send out mandate M/405 (Ground ATM equipment under the scope of R&TTE Directive1999/5/EC) to ESOs in Apr.07 • Single Sky Committee (Apr.07) requested Eurocontrol to develop CS on AMHS (ATS Message Handling System)
CS work programme • At least 14 CSs (Data Link, Surveillance, Aeronautical Informantion) are directly linked to the development of Implementing Rules. Considerable mandate package will be issued after IR adoption (from autumn 07 onwards) • Coordination with the SESAR Masterplan (work package T2.6.2 for D3 Standardisation) started in Mar.07 and will be continued via the JU SESAR for the development phase
Main aims/issues of SES Implementation are • Reduction of Fragmentation within EATMN • Establishment of a seamless environment • Implementation of new technologies STANDARDISATION • Is a key component in SES Interoperability • Must be an industry driven process • Needs to be done in a global scale • Will be linked to the SESAR Masterplan
In case of any questions… Sven Halle European Commission DG TREN/F/2 Single European Sky & Modernisation of ATC Mail address: DM24 05/69, B-1049 Bruxelles Phone: (+).32.2.298.00.70 Fax: (+).32.2.296.83.53 e-mail: sven.halle@ec.europa.eu
STANDARDISATION WORK PROGRAMME - Backup -
CS future work programme (as of Oct.06) • General • CS on Software Assurance Levels (SWAL) P1 • CS on Airport Collaborative Decision Making (A-CDM) P1 • CS on Cross Domain Information Sharing P3 • CS on Reference Concept of Operation (including long term) deleted • CS on UAV Systems Operation P3 • CS on En-route and Airspace CDM P3 • Airspace Management • CSs on Flexible use of Airspace P1* • CSs on Airspace Design P1 pending • Air Trafffic Flow Management (ATFM) • CS on European Air Traffic Flow Management (CFMU/IFPS (TACT and CADF, ETFMS)) P3 (IR) • CS on updated IFPS Users manual P1 • CS on Data Exchange Formats P1 • CS on Advanced Data Exchange Formats P3
CS future work programme • Air Traffic Service (ATS) • CS on On-Line Data Interchange (OLDI) P1 • CSs on Interoperability of Flight Data Processing (ATC-ATC) P1 • CS on A-SMGCS (Level 1 & 2) P1 • CS on Link Baseline 1 DL Services over ATN/VDLM2 in Continental Airspace P2* • CS on DL Services over FANS-1/A in ATN Continental Airspace P2* • CS on DL Services over ACARS in continental airspace P2* • CSs on Open ATC system architecture model P3 • CS on A-SMGCS (Levels 3 and higher) P3 • CS on arrival management P2 pending • CS on departure management P2 pending • CS on Surveillance Performance P2* • CSs on Interfaces between Controller Working Positions and Data Processing (flight and Surveillance Data) P3 • CSs on Interface with Flight Data Operator Positions P3
CS future work programme • Air Traffic Service (ATS) • CSs on Interfaces with Local centre sub-systems (Surveillance, Supervision, Recording and Data Analysis Systems; Adaptation Database) P3 • CSs on Flight Plan Information Subscriber systems (for e.g. Airline Operators and Airports) P3 • CS on Interoperability of Flight Data Processing (Middleware ATM-ATM) P3 • CS on Surveillance Data Processing P4 • Communication • CS on ATS Message Handling System (AMHS) P2 • CS on VoIP (ground-ground) for use in EATMN P3 • CS on telephone used for ATC purposes in the EATMN P2 R • CS on Directory Service in support of AMHS P3 • CS on VoIP (including air-ground VoIP/Ethernet) for use in EATMN P3 • CSs on ground and mobile stations in the aeronautical mobile service (AM radio telephone installations) operating in range 117.975 – 137 MHz P4 R • CS on HF radio equipment P4 • CS on UHF for use by civil ATC P4 R
CS future work programme • Navigation • CS on Space Based Augmentation Systems P4 • CS on Galileo, GNSS P3 • CS on distance measuring ground equipment (DME) P3 R • CS on ILS ground equipment P3 R • CS on MLS P3 R • CS on Ground Based Augmentation Systems (CAT II/III) P3 • CS on non-directional beacon (NDB) ground equipment P4 R • CS on omni-directional radio range ground equipment (VOR, D-VOR) P4 R • CS on VHF Marker Beacon ground equipment P4 R • CS on Ground-Based Augmentation Systems (CAT I only) P4 R • Surveillance • CS on ground-based primary radar equipment for use in the EATMN P2* • CS on Multilateration Equipment for use in the EATMN P2* • CS on Surveillance Data Exchange P2*
CS future work programme • Surveillance • CS on surveillance services using ADS-B P2* • CS on ADS-B equipment P2* • CS on ground-based secondary radar systems for use in the EATMN P2* • Aeronautical Information Service AIS • CS on AIS - Generic data process & Principles (incl. Data & Quality Management) P2* • CS on Integrity of Aeronautical Information - Data Origination P2* • CS on Integrity of Aeronautical Information - Data Publication P2* • CS on Aeronautical Information Exchange (AIXM) P3 • Meteorological Informations • CS on Systems and Procedures for the Use of Meteorological Information P2 pending • CS on Meteorological Information Exchange (eg XML) P2 pending • additional required / necessary CSs……… (*) means that the CS development is dependent on parallel development of a related IR ( R ) means that the CS development might be dependent on activities related to the R&TTE directive