EUROCONTROL AMHS Specification Workshop

Transcription

1 EUROCONTROL AMHS Specification Workshop Speaker Organisation Date and venue Jacky POUZET EUROCONTROL 23 rd June 2009, Brussels European Organisation for the Safety of Air Navigation

2 EUROCONTROL AMHS Specification Introduction Today s objectives Agenda Next Steps 2

3 EUROCONTROL AMHS Specification Why we are here To present the results of the Formal Consultation 3

4 EUROCONTROL AMHS Specification Agenda Welcome Update on Communication strategy Nikos Fistas ATM Standardisation in the SES context EU perspective Sven Halle EUROCONTROL perspective Eivan Cerasi 4 Overview of the Specification Richard Papior Results of the Consultation Overall results Bolek Gasztych Summary of Responses Tony Kerr Questions & Answers Conclusion and next steps

5 EUROCONTROL AMHS Specification End European Organisation for the Safety of Air Navigation

6 EUROCONTROL AMHS Specification Workshop Speaker Organisation Date and venue Nikos Fistas EUROCONTROL 23 rd June 2009, Brussels European Organisation for the Safety of Air Navigation

7 The big picture SES SESAR ATM Master Plan COM - Infrastructure Strategy 2

8 High-Level European ATM System 2020 architecture 3

9 Future Aeronautical Communications Satellite Communications ATC, AOC, (APC) Data link: CPDLC, FIS (ATN, ACARS) VHF voice 25 & 8,33 khz ATSU ATC, APC, AOC 4D (COCR ) New datalinks New mobile network CFMU MIL Airports IP network (PENS SWIM backbone) Applications: AMHS, OLDI/FMTP, Surveillance, AIM, Voice, ATSU Surveillance AIM Airline Ops 4

10 SESAR Service Levels - Communications Time (Calendar Years) Implementation R&D Available for operations Full A/G 4D trajectory digital voice, management A/A 4 Implementation R&D Available for operations Extending operations with advanced New data-links (L Band, satcom) separation modes ATM Service Levels Implementation R&D Available for operations Implementation R&D Available for operations Implementation R&D Available for operations Achieving Air/ground advanced transport automation layer, New in a Airport shared trajectory data-link environment (802.16) G/G IP network, VoIP (radio), Implementing Link16, net-centric 8.33kHz trajectory below FL195 management European Preparing IP Trajectory backbone, based VoIP operations (telephony) 0 Available for operations Implementation AMHS, Rolling VDL2/ATN, out Current 8.33 Best khz Practices above FL195 5

11 SJU WBS SJU SJU A/1 - WP Management B - Target concept & Architecture D - ATM Network R&D Programme C - Master Plan Maintenance E - LT & Innovative Research Industrial Support 16 - Transversal Areas 3 - Validation Infrastructure 7 - Network Operations 5 - TMA Operations 8 - Information Management 10 - ATC 12 - Airport 14 - SWIM 4 - En Route Operations 6 - Airport Operations 9 - Aircraft 11 - AOC 13 - NIMS 15- Ground CNS 6

12 SESAR WP15 WP15 Ground CNS Spectrum 15.1 COM 15.2 NAV15.3 SUR 15.4 FCI L band FCI - satellite FCI Airport surface Civil Military interoperability Terrestrial COM Infrastructure - SWIM 7

13 WP : Terrestrial Com Infrastructure - SWIM Task 1 : PENS service (adaptation when needed), SWIM requirements. Task 2 : Security policy (incl. SWIM requirements) Task 3 : Follow technical validation (performances, multicast, VoIP, SWIM) Civil/Military coordination International coordination (via existing steering groups incl. civil/mil) Architecture (outputs) (SESAR WP8-14) WP AMHS/SWIM AFTN/CIDIN AMHS PENS SWIM backbone 8

14 EUROCONTROL AMHS Specification The End European Organisation for the Safety of Air Navigation

15 Single European Sky Regulations EUROPEAN COMMISSION Eurocontrol AMHS Stakeholder Consultation Workshop,

16 Single European Sky Where did we start I SES started in 2004 with its 4 Regulations by laying down the foundations for.legal and institutional framework» Single Sky Committee assists the Commission in adopting the enabling legislation through comitology with civ/military participation, EASA, ICAO and 3rd countries» Industry Consultation Body enables all industry stakeholders and social partners to contribute to legislation» Technical support from Eurocontrol in the rulemaking process through mandates Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

17 Single European Sky Where did we start II.Separation of service provision from regulation» Each Member State has established a National Supervisory Authority (NSA) to ensure effective regulation and for avoiding conflict of interests. NSAs are also exercising a safety oversight function» Since 20 June 2007, air navigation service providers have become subject to certification by the NSAs (Regulation 2096/2005).Transparency of charges» Regulation 1794/2006 on a common charging scheme ensures full transparency in the establishement of air navigation service charges Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

18 Single European Sky Where did we start III.Harmonisation in licensing of controllers» Adoption of Directive 2006/23/CE that will achieve a harmonised level of competence and an improved mobility of workers (Important social dimension as there are i.e ATM controllers within the EU).Advances in the efficient use of airspace» Common provisions for the flexible use (civil and military) of airspace in accordance with Regulation 2150/2005» Harmonisation of airspace classification in the upper airspace in accordance with Regulation 730/2006 Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

19 Single European Sky Where did we start IV.Towards interoperable equipment» An effective interoperability mechanism has been established to adopt implementing rules (Regulations) and to develop Community specifications (Standards)» So far 6 implementing rules & 4 Community specifications have been adopted» Indispensable framework for the efficient implementation of SESAR (Single European Sky ATM Research) and incorporated in the European ATM Masterplan Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

20 Single European Sky 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 (SESAR) Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

21 Single European Sky Interoperability.Legislative Tools Binding Essential Requirements Implementing Rules Community Specifications SES Interoperability Regulation (552/2004) Mandatory Layer to implement the ERs. Developed under Commission Mandates European standards for systems, or constituents, together with the relevant provisions, drawn up by European Standardisation bodies in cooperation with EUROCAE Specifications drawn up by Eurocontrol on matters of operational coordination between Air NavigationService Providers Recognized as Means of Compliance with the ER / IR.Conformity Assessment Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

22 Single European Sky and what are challenges in the future:.environment» Aviation s share of EU greenhouse gas emissions (currently 3%) is predicted to increase.» Network improvements could save up to 4.8 mio tons of CO² per year.fragmentation» Significant additional costs for airspace users ( 2 bn per year could be saved by reducing fragmentation).economics» Cost efficiency efforts are not sufficient» Liberalization of aviation market vs. Harmonization of ATM» Current European route network is an amalgamation of national routes that makes intra-european flights 15% less efficient than domestic flights, resulting in additional costs of 1.4 bn per year.safety» Cannot be compromised and must be enhanced with increased traffic levels.capacity» Delay still accumulate to 1.3 bn per year and further increase of traffic (250% increase within the next 20 years, growth rate of new EU States exceeds 10%) with enlargement and Open Skies Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

23 Single European Sky 2nd package What are our goals put the emphasis on the right governance using the Community method as driving force of aviation regulation ensure the highest safety standards by implementing a comprehensive Total System Approach focus on a more efficient and performing but also still human centered air transport network including the pan- European perspective establish a sustainable European air transport system reducing the effects of aviation on the climate change Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

24 Single European Sky Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

25 Single European Sky 2nd package is based on 4 pillars PERFORMANCE SAFETY CAPACITY TECHNOLOGY Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

26 PERFORMANCE» Introduction of a performance-driven approach and framework (including independent performance review) on safety, environment, capacity and cost-efficiency, with the appropriate elements (incentives) to drive the change process» Economic and performance regulation with specific targets at Community level: Performance Target Setting for the Network Translate EU targets into national/local targets Adopt local targets and ensure coherence between local/eu targets» Involvement of all stakeholders, more effective civil/military cooperation and social dialogue, support to the Eurocontrol reform Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

27 PERFORMANCE» Acceleration of the creation and integration of Air Navigation Services in Functional Blocks of Airspace (FABs) towards dates politically committed by States (2012 implementation) and elimination of national obstacles» Enable Air Navigation Service Providers to perform their services in a more business-oriented and transparent manner» Network Management Function, improving management/ coordination of network functions and optimising the use of the network (including airport and en-route slot coordination)» Better flight-efficiency to be achieved through improvement of the network performance and more efficient use of resources Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

28 SAFETY» Effective use of the Community approach» Extension of EASA competence to airports, air navigation services and air traffic management» Implementation of the Total (gate-to-gate) System Approach» Strengthen the oversight of National Supervisory Authorities Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

29 CAPACITY» Action Plan for airport capacity, efficiency and safety in Europe» Establishment of an Observatory (Nov 2008) to exchange and monitor data/information on capacity (capacity assessment, capacity planning, co-modality, inter-modality)» Implementation of an integrated Capacity Management with an increased predictability (airport capacity management determines ATM capacity) and evolution to time based operation» Airports must be seen as an integral part of the ATM network Entry and Exit points of the network Effective use of capacity depends on all elements of transport chain Green operations require real-time flow of information (e.g. SWIM) between all stakeholders Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

30 TECHNOLOGY» SESAR Joint Undertaking (JU) established in 2007 based on EU Treaty Article 171 with Council Regulation (EC) No 219/2007» SESAR JU will drive technological improvements (converge fragmented R&D efforts) in line with the ATM-Masterplan» JU membership negotiations with industry and stakeholders» Completion of Definition phase and endorsement of the ATM- Masterplan by the Transport Council in 2008» Close cooperation between SESAR and CLEAN SKY» Global interoperability (SESAR / NextGen) Adoption of implementation elements through SES legal framework after validation of improvements/performance targets within the frame of the ATM Masterplan Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

31 TECHNOLOGY SESAR concept» Key to the SESAR concept is the business trajectory principle in which the users of the airspace and controllers define together, through a collaborative process, the optimal flight path. Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

32 TECHNOLOGY SESAR concept» Taking full advantage of existing and newly developed technologies (such as in GALILEO) SESAR s target concept relies on a number of new key features: - the Network Operation Plan, a dynamic rolling plan for continuous operations that ensures a common view of the network situation. - Full Integration of Airport operations as part of ATM and the planning process. - Trajectory management, reducing the constraints of airspace organisation to a minimum. - New aircraft separation modes allowing increased safety, capacity and efficiency. - System wide information management (SWIM) securely connecting all the ATM stakeholders which will share the same data. - Humans as the central decision makers: controllers and pilots will be assisted by new automated functions to ease their workload and enable complex decision making processes. Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

33 TECHNOLOGY SESAR Future ATM Concept The driver: Performance Based Approach ATM intranet Collaborative Decision Making Airports as Integrated Partners Network Management The foundation: Trajectory Based Operations Source: SESAR JU Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

34 TECHNOLOGY 5 4 R&D R&D Implementation Implementation Available for Operations Available for Operations Accommodating full 4D trajectory management based on user preferred trajectories Dynamic Sector shapes ASEP WV spacing, ASAS Self separation 4D-PTC Extending operations with advanced separation modes Dynamic Mobile Area, 3D-PTC User preferred trajectories ASEP C&P, SVS in low visibility conditions Compatibility between Airborne and Ground Safety nets ATM Service Level 3 2 IP1 1 R&D R&D R&D Implementation Implementation Available for Operations Implementation Available for Operations Available for Operations Preparing Trajectory based operations Interactive rolling NOP, Manual UDPP AMAN/DMAN integration ATSAW in flight and on surface, ATSA-ITP Improved Low Visibility Procedures Achieving advanced automation in a shared trajectory environment Dynamic TMAs and Flexible Military structures Dynamic ATFM using RBT Management Revision of RBT using Datalink Full set of Advanced Controller tools using RBT/SBT ASEP-ITP 2D-PTC on User Preferred Trajectories 3D-PTC on Predefined Routes Implementing net-centric trajectory management SWIM enabled NOP using RBT/SBT Full set of Complexity Management Tools ASPA S&M 2D-PTC on Predefined Routes Automated Surface Movement Planning and Routing Adjustment of Separation Based on Ground Wake Vortex detection 0 Implementation Available for Operations 2009 Rolling out current Best Practices (CDA, Flexible sectorisation, Continuous Climb Departure, Initial Data link, Automatic Flight Conformance Monitoring, Basic Departure Management (DMAN), Ground Based Safety Nets, Use of Runway Occupancy Time (ROT) Reduction Techniques) Date of Initial Operating Capability Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

35 Implementation Package 1 IP1 main characteristics Essential as the baseline for SESAR deployment It must be all about improving the current system making it coherent through implementation of best practices, better coordination and the preparation for trajectory / time based operations Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

36 Process of IP1 refinement EC, SESAR JU, Eurocontrol started as JWG the refinement process IP 3-2 Developments shifting Filtering of OIs from D5 = Existing IR, or linked to SES (IR & CS) regulation Or Mature/complete or confidence in initial deployment within the timeframe Justifiable with clear criteria (i.e. endorsed business case, anticipated network benefits) No critical R&D needed (~end of V3, EOCVM) mapping IP 1 Deployment Improve the current system Prepare for trajectory /time based operations defining Eurocontrol work programme, existing developments, R&D results Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

37 Additional IP1 refinement IP 1 Deployment Improve the current system Prepare for trajectory /time based operations Time classification Geographical classification Stakeholder/Airspace User segmentation further parameters Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

38 SESAR WP links Information Management Network Management Trajectory Management, Separation, Automation Airports Airports & Aerodrome ATC Aircraft Systems Aircraft Operations FOC TMA/En-Route Operations SWIM CNS Systems & Infrastructure Airspace and Network Management Aeronautical Information Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

39 IP1 CNS Systems & Infrastructure The IP1 baseline builds on existing/mature elements and consists of the following items: 1. Deployment of AMHS for ground-ground data communications 2. Deployment of VHF (8.33kHz) above FL195 for voice communication and VDL2/ATN for initial data link 3. Implement MLAT systems and deploy ADS-B ground stations to support surveillance applications 4. Implementation of GNSS applications (APV/LPV) 5. Creation of a European IP backbone network and start implementation of VoIP (Voice over IP) for ground-ground voice communication Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

40 IP1 AMHS CS. Single Sky Committee (Apr.07) requested Eurocontrol to develop a CS on AMHS (ATS Message Handling System) to ensure. interoperability and seamless operations of AMHS in EATMN The CS will augment existing standards and will include:» The Basic ATS Message Handling Service, with its functional components;» The Extended ATS Message Handling Service, including Safety and Security standards, and Directory services;» The interoperability aspects of communication gateways within the transition phase» The tests and verifications of compliance with the AMHS requirements.. Eurocontrol is expected to deliver the CS for SSC advisory procedure in 2009 as en element of Implementation Package 1 Sven Halle Eurocontrol AMHS Stakeholder Consultation Workshop,

41 THANK YOU! EUROPEAN COMMISSION

42 EUROCONTROL AMHS Specification Workshop Speaker Organisation Date and venue Eivan CERASI EUROCONTROL 23 rd June 2009, Brussels European Organisation for the Safety of Air Navigation

43 Interoperability Regulation EC Regulation 552/2004 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 Implementing Rules Community Specifications (Voluntary Standards) 2

44 Interoperability Regulation SES interoperability Regulation (552/2004) Essential Requirements (ERs) Implementing Rules (IRs) Community Specifications (CSs) Voluntary Standards Drafts developed by EUROCONTROL as EC Regulations Such specifications may be: ENs drawn up by ESOs (CEN/CENELEC/ETSI) in cooperation with Eurocae on technical issues, or Specifications drawn up by EUROCONTROL on matters of operational coordination Compliance with the ER and/or IR is presumed when meeting the CS 3

45 Interoperability Regulation EUROCONTROL Examples and AMHS Essential Requirements Essential Requirements COTR IR DLS IR VCS IR FMTP IR ADEXP CS OLDI CS FMTP CS EUROCONTROL Specification on AMHS to be recognised as EC Community Specifications - Voluntary - 4 EUROCONTROL Specifications (some are not Community Specifications) AMHS

46 Community Specifications Material of a voluntary nature, non binding Detailed technical/operational specifications Used as means of compliance with Essential Requirements and Implementing Rules Can include references to ICAO SARPs, Technical Manuals, EUROCAE docs Include traceability to regulatory requirements, in the case of the AMHS Community Specification it will be limited to the Essential Requirements 5

47 Specificity of AMHS No Implementing Rule on AMHS Therefore implementation of AMHS is not imposed by EC Regulation AMHS is part of SESAR and ESSIP SESAR enabler CTE-C10 to be available for operations by 2011 ESSIP Objective COM-05 (under revision) Value of EUROCONTROL Specifications State-of-Art AMHS specifications supported by a majority of stakeholders after formal consultation procedure 6 Value of the EUROCONTROL AMHS Specifications recognized as CS When used (as a whole) it provides a presumption of conformity with Essential Requirements of the SES interoperability regulation

48 EUROCONTROL Notice of Proposed Rule-Making (ENPRM) Mechanisms used for SES regulatory mandates Mandate ENPRM Mechanisms Consultation Stakeholders Workshop Initiation Phase Drafting Phase Initial impact assessment Regulatory Approach Full impact assessment Formal Consultation Review of Comments SSC Opinion Stakeholders Workshop Amendment of Draft Rule 7 EC Approval/Publication

49 Lessons Learned EUROCONTROL AMHS Specifications have been difficult to prepare in the absence of an Implementing Rule Further clarity should be given by the Commission on the way a Community Specification should be applied in this context (e.g. partial or full application of the provisions) 8

50 EUROCONTROL AMHS Specification End European Organisation for the Safety of Air Navigation

51 EUROCONTROL AMHS Specification Speaker Organisation Date and venue Richard PAPIOR EUROCONTROL 23 rd June 2009, Brussels European Organisation for the Safety of Air Navigation

52 EUROCONTROL AMHS Specification Introduction What is the specification based on? How the document developed The final structure What is the specification for? 2

53 EUROCONTROL AMHS Specification What is it based on? European Organisation for the Safety of Air Navigation

54 EUROCONTROL AMHS Specification What is it based on? SES Regulations EUROCONTROL AMHS Specification SES Environment EUR Doc 020 EUR AMHS Manual (Future EUR Documentation) EUR Doc 021 ATS Messaging Management Manual ICAO EUR Region Annex 10 SARPs Doc 9705 Sub-Volume III Doc 9880 Part IIB ATSMHS Doc 9705 Sub-Volume VII (DIR) Doc 9705 Sub-Volume VIII (SEC) ICAO Global ISO/IEC & ITU-T MHS Standards ISO/IEC ISPs International Standards 4

55 EUROCONTROL AMHS Specification Major Technical Inputs (1) ICAO SARPs: Annex 10 Volume II Annex 10 Volume III Part 1 Detailed technical provisions: Doc 9705 Third Edition (2002) Sub-Volume III / Doc 9880 Part IIB (AMHS) Doc 9705 Third Edition (2002) Sub-Volume VII / Doc 9880 Part IVA (Directory) Doc 9705 Third Edition (2002) Sub-Volume VIII (Security) Guidance material: Doc 9739 Draft Second Edition 5

56 EUROCONTROL AMHS Specification Major Technical Inputs (2) Regional manuals: ICAO EUR Doc 020 EUR AMHS Manual ICAO EUR Doc 021 ATS Messaging Management Manual ICAO EUR AFS Security Guidelines Others: ECG User Requirements Document SPACE project final report Studies on Directory and Security deployment architecture Supplier s Technical Documents 6

57 EUROCONTROL AMHS Specification How was it developed? European Organisation for the Safety of Air Navigation

58 EUROCONTROL AMHS Specification Development timeline 1. Enhanced Basic AMHS (e.g. TCP/IP) 2. Extended AMHS, Directory & Security (3 annexes) 3. Extended AMHS plus interconnection between AMHS and internet messaging networks (e.g. SMTP) Scoping Workshop 12/12/07 Scope Questionnaire EC mandate May 2007 Initial Plan Specification Approach Document 73% prefer Alternative 2 Draft Planning Specification N D J F M A M J J A S O N D J F M A

59 EUROCONTROL AMHS Specification Development timeline ICAO AMHS Workshop, Paris 5-6/06/08 COMT-42 Brussels 11-12/06/08 COMT-43 Brussels 8-9/10/08 Drafting Group 29/2/08 Drafting Group 02/04/08 Review Group 09/09/08 Review Group 6&7/11/08 ENPRM Workshop 23/06/09 Review Version Revised Structure Drafts Draft 0.3 Draft 0.4 Draft 0.5 Draft 0.6 Draft 1.0 SOR Final Report Drafting stage Informal consultation ENPRM consultation N D J F M A M J J A S O N D J F M A M J J A S

60 EUROCONTROL AMHS Specification What is in it? European Organisation for the Safety of Air Navigation

61 EUROCONTROL AMHS Specification Document Structure Specification is organised as a Main Body and Annexes. Chapters in Main Body provide contextual guidance and point to the self-contained Annexes Chapter 1 - introductory material describing the purpose and scope of the Specification Chapter 2 - describes the Basic level of interoperability for AMHS Chapter 3 - describes the Extended ATSMHS Chapter 4 - describes the use of Directory systems and procedures Chapter 5 - outlines possible future Security mechanisms based on ICAO provisions 11

62 EUROCONTROL AMHS Specification Document Structure Chapter 6 - additional requirements relating to implementation options, testing, and validation Chapter 7 - some of the transition and coexistence issues Chapter 8 - traceability between the means of compliance in the AMHS CS and Single European Sky essential requirements Chapter 9 - procedures for maintaining and updating the Specification Chapter 10 - Reference documents 12

63 EUROCONTROL AMHS Specification Document Structure Annex A (normative) - detailed requirements for the Air Traffic Services (ATS) Message Handling functionality at the level of the Basic ATSMHS. Annex B (normative) - detailed requirements for the ATS Message Handling functionality at the Extended ATSMHS level of service, requiring support of Functional Groups (FG) for: the Basic ATSMHS (Basic FG), use of file transfer body parts for binary data exchange (FTBP FG), use of interpersonal messaging heading extensions (IHE FG) use of Directory (DIR FG) Support of AMHS Security (SEC FG) is foreseen in the future Annex C (normative) - detailed requirements for Directory systems to support the DIR FG Annex D (informative) - indicative security provisions to support the SEC FG 13

64 EUROCONTROL AMHS Specification What is it for? European Organisation for the Safety of Air Navigation

65 EUROCONTROL AMHS Specification Transition to SESAR New concepts of operation SESAR / SWIM enablers Today s infrastructure Evolution SESAR / CNS infrastructure AMHS CS SES Regulations Presumption of compliance Communication systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to achieve the required performances... for a specific application, in particular in terms of communication processing time, integrity, availability and continuity of function 15

66 EUROCONTROL AMHS Specification The End European Organisation for the Safety of Air Navigation

67 EUROCONTROL AMHS Specification Workshop Speaker Organisation Date and venue Bolek GASZTYCH EUROCONTROL 23 rd June 2009, Brussels European Organisation for the Safety of Air Navigation

68 EUROCONTROL AMHS Specification Formal Consultation The draft EUROCONTROL AMHS Specification has been subject to a Formal Consultation period of 3 months (22nd January to 22nd April) Consulted Organisations National Civil and Military Authorities Air Navigation Service Providers International Organisations Airspace Users Organisations Military Airspace Users Industrial and Social Representatives EUROCONTROL Bodies 2

69 EUROCONTROL AMHS Specification Formal Consultation Outcome 35 Responses received from: National Civil and Military Authorities Air Navigation Service Providers International Organisations Military Airspace Users Industrial and Social Representatives EUROCONTROL Bodies The majority of responses were in support of the draft specification document 3

70 EUROCONTROL AMHS Specification Who responded? ENPRM-09/001 Draft EUROCONTROL Specification on AMHS Responses received per Stakeholder Category Military 8.6% Industry 8.6% Professional organisation 2.8% ANSP 48.6% Civil Authority 31.4% 4

71 EUROCONTROL AMHS Specification The responses were ENPRM-09/001 Draft EUROCONTROL Specification on AMHS Responses received per Response Category Acceptable without amendment 54.3% Not acceptable under any circumstances 11.4% 68.6% Acceptable Acceptable but would be improved with amendments 14.3% Not acceptable but would be acceptable with amendments 20.0% 5

72 EUROCONTROL AMHS Specification General Responses Overview Acceptable without amendment Acceptable but would be improved with amendments Not acceptable but would be acceptable with amendments Not acceptable under any circumstances Total by Stakeholder category % Service Providers (ANSPs) % CAA % Military % Industry % Other (professional organisation) % Total responses received by category % Percentage (%) 54.3% 14.3% 20.0% 11.4% 100.0% 6

73 EUROCONTROL AMHS Specification Total number of comments In total, 98 comment sheets received Some with significant overlap Many comments are requests for clarification 7

74 EUROCONTROL AMHS Specification General Responses by Category (1) 4 Responses with Not acceptable under any circumstances with 41 comment sheets All from the same Member State (ANSP, NSA, Military, Industry). Main objection relates to inclusion of Extended ATSMHS on the grounds of operational maturity, test specifications, ability to replace National specifications, lack of Concept of Operations, definition of Constituents, details of mapping to Essential Requirements. Comment sheet requests removal Annexes B, C and D. Not Agreed. Majority of responses in favour of adding value to Basic ATSMHS. The draft Specification is a candidate for adoption as a CS this is a voluntary means of compliance, not an IR. 8

75 EUROCONTROL AMHS Specification General Responses by Category (2) 7 Responses with Not acceptable, but would be acceptable with Amendments with 36 comment sheets Main amendment requests relate to removal of duplicated material, clarification of differences with ICAO documents, removal of advisory and background material, removal of informative security Annex. Mostly Agreed but informative security Annex should remain, with clarified status, for alignment with ICAO technical manual. Some concern over support for existing and planned deployments Will be clarified that there is no impact on existing deployments. Annex A could be used, together with additional materials, to justify EC Declaration. 9

76 EUROCONTROL AMHS Specification Proposed Specification Updates Search and remove material duplicated in other standards Replace AFTN/AMHS Gateway PRL Tables with cross-references to Doc 9880 Part IIB (reduction of ~30 pages) Update document references ICAO EUR Doc 020 now refers to Doc 9880 instead of Doc 9705 Remove reference to Extended ATSMHS test cases Additional text on: Use (or not) of Directory to determine recipient capabilities Support for Directory Names in O/R addresses 10

77 EUROCONTROL AMHS Specification End European Organisation for the Safety of Air Navigation

78 AMHS EUROCONTROL Specification Results of ENPRM Consultation - Consolidated Comments Speaker Organisation Date and venue Tony Kerr EUROCONTROL 23 June 2009, Brussels European Organisation for the Safety of Air Navigation

79 Summary of Responses Objective: To present consolidation of major themes occurring in ENPRM 09/001 responses Major Issues (Non-technical) Regulatory (SES) Technical Issues Other Issues All received comments, and more detail on proposed responses, are listed in SOR document Consolidated comment topics are given in Black headings EUROCONTROL Response and proposed Actions appear in Brown text 2

80 Summary of Responses Major Issues (Non-technical) Maturity of ATSMHS Extended Service Size of Specification vs. Value Added Definition of transitional steps Inclusion of AMHS Security requirements 3

81 Maturity of ATSMHS Extended Service The scope covers elements of the ATSMHS Extended Service that have not been fully defined and are not mature. Inclusion of the ATSMHS Extended Service at this moment is not feasible and should be removed from the EUROCONTROL Specification. 4 No change proposed. Security is already advisory only. Standards for the Extended ATSMHS are technically mature and validated, published by ICAO in 2002, based on long-established standards extensively validated in other domains. AMHS is part of SESAR Implementation Package 1 (IP1). It must support new concepts of operation and is part of the transition to SWIM. The Basic level of service adds little if any value to the existing AFTN and does not readily support new concepts of operation (e.g. binary content). The draft EUROCONTROL Specification: Offers a voluntary means of compliance with SES Regulations, Provides a means to kick-start the migration effort from the Basic to the Extended level of service by defining some initial requirements that can be built upon using the results of ongoing implementation projects. Document maintenance procedures ensure that less mature elements can be further elaborated as experience is gained and application performance requirements become clearer.

82 SESAR System Enabler (extract from e-atm Master Plan) Migration to AMHS (ATS Message Handling System) from AFTN is carried out to improve regional, global and civil/military global interoperability. The ATS Message Handling System (AMHS) is a proven messaging application based on the X.400 worldwide standards for messaging and on the Internet Protocol (IP) for transmission and routing. In the EUR ICAO Region it was decided to implement the AMHS on top of a TCP/IP network infrastructure. The deployment of AMHS is an ongoing work, which was started with the implementation of the "Basic Service" since An important development will be the introduction of the "Extended Service" which is described in the ICAO documentation. The realisation needs technical and theoretical support especially regarding operational procedures and resulting adaptations of the AMHS COTS software. Industrialisation Deployment Related Operational Improvement Steps 5

83 Size of Specification vs. Value Added 6 What benefit does the Specification add over the existing documentation to a EUR State implementing an AMHS system? It increases the overheads of maintaining the documentation. Advisory and background material should be removed, since this is a specification, not a guidance or training document. The draft EUROCONTROL Specification adds value in a number of areas: Basic ATSMHS - requirements are specified for safety and performance, management and conformity assessment for the various elements of the AMHS. Extended ATSMHS - additional requirements are specified for the detailed profile, directory architecture and functionality and conformity assessment, as well as guidance on deployment scenarios, etc. It clearly distinguishes requirements, recommendations and explanatory material. Just including a list of cross-references would make the document unreadable. Some of the conformity assessment material can be replaced with crossreferences, significantly reducing the size of Annexes A and B. Any unnecessary duplication of requirements will be removed.

84 Size of Specification vs. Value Added Can reduce by ~30 pages by replacing GWY PICS with x-ref 146 pages plus Appendices Total 226 pages, 176 plus Appendices Conformity assessment 39% Document control 14% Number of pages pages requirements / notes Conformity assessment Requirements & Notes Explanatory Document control Main Body analysis Requirements & Notes 13% Introduction Explanatory 34% 10 Basic AMHS Extended AMHS 0 Main body Annex A Annex B Annex C Annex D Appendix 1 Appendix 2 Use of Directory AMHS Security Requirements Additional AMHS Requirements Transition / Coexistence issues Traceability to Regulatory Provisions Document updatre procedures 7 List of references Document control

85 Definition of transitional steps Step-wise approach to compliance should be defined. Ensure that Annexes can be incrementally put into operation. ICAO manual allows indefinite support of Basic service as long as required. Initial AMHS interoperability target should include only Basic service, possibly with DIR, definitely excluding SEC. A series of interim targets should be defined, providing a more stepwise transition and a more stable, less ambitious target. One response - AMHS Basic service level implemented only as an interim solution on the transition path to SESAR information management (SWIM) services. 8 ICAO Doc 9880: It is intended that eventually the Extended level of service will be supported by all ATSMHS users, so that the Basic ATSMHS will not be required anymore. In the context of SESAR the value of the Basic level of service may be questioned, especially the lack of support for binary data transfer. When recognised as a CS, the specification will be a voluntary means of compliance to the SES essential requirements. It is a tool to aid conformity assessment. Detailed planning of transition steps is out of scope.

86 Inclusion of AMHS Security provisions (1/5) Security requirements are not yet mature, or are only mentioned in draft ICAO documents and should not be included in the CS. Regulation (EC) No 2096/2005 (Common Requirements): An ANSP must "ensure the security of operational data it receives or produces or otherwise employs A system-wide approach to information security must be taken, depending upon the results of an end-to-end threat analysis. Security must obviously be a consideration for the AFS, including for AMHS measures could be taken at application level and/or messaging level and/or network level. Secure messaging is one possible element of an overall information security policy, and is a key element of the Extended ATSMHS in ICAO Doc 9880 Part IIB. Technically validated security mechanisms for the ATN, including the recommended cryptographic algorithms, PKI and digital signature scheme, are defined in ICAO Doc 9705 Sub-Volume VIII (2002). No application threat analysis so far justifies use of AMHS security mechanisms. Clarification: Distinguish between (a) messaging protocols that can carry security elements and (b) security mechanisms. 9

87 What is meant by Security Support? SEC SEC functional group in the referenced MHS standardised profiles Transparent relay of securityrelated elements of service for forward compatibility System Enabler for secure messaging in the future SEC functional group of the Extended ATSMHS ICAO Doc 9880 Pt IIB Secure messaging using the message token ICAO Doc 9705 SV8 cryptographic algorithms, PKI 10 Recommended in Annex B for MTA, UA and MS components implementing the Extended ATSMHS Informative in Annex D

88 Inclusion of AMHS Security provisions (2/5) Impact assessment The justification and impact of AMHS security requirements must be assessed before any inclusion in the CS. AMHS Security requirements must remain Optional and not Recommended as currently worded, until there is a European agreement to implement AMHS Security, based on an appropriate impact study and cost analysis. Security performance requirements are an integral part of the SESAR Validation & Engineering Process. Cost-benefit analysis would be considered as part of the impact analysis of an implementing rule, and/or as part of an ANSP s system procurement. The CS will not mandate usage of security mechanisms. It is generally much more difficult to bolt on security at a later stage than to integrate it into the system design. Recommendations are not requirements; i.e. they are already Optional. 11

89 Inclusion of AMHS Security provisions (3/5) Product support The proposed AMHS security requirements are not currently supported by AMHS systems deployed or being implemented. For the Basic level of service, there are only basic security requirements for access control (Annex A, A ). For the Extended level of service, security-related provisions in Annex B (transparent relay) are not required for implementation, but are recommended for forward compatibility. There are no requirements for the security mechanism; cryptographic Security functionality is restricted to an informative annex Digital signing of message content is commonplace in some other domains, and does not represent a great technological leap forward. PKI products and services are widely available. 12

90 Inclusion of AMHS Security provisions (4/5) Uniform implementation Are ANSPs who implemented AMHS systems before the release of the CS required to implement the SEC function? If they do not, then how they can be interconnected with those who have implemented? If done by bilateral agreements, the non-sec capable AMHS systems could be vulnerable points of the AMHS community. There are no requirements to implement the SEC functional group of AMHS. Conformance to the Extended level of service can be achieved without the SEC functional group of the Extended ATSMHS ( 3.3.6). There should be no problem interconnecting a SEC and a non-sec system: If a SEC system sends a secure message to a non-sec system, it is processed like a regular non-sec message the ( non-critical ) message token is ignored. Confirmation could be requested at application level. SEC systems are required to be able to accept unsigned messages (without a message token) from non-sec systems. The security status would be flagged to the user and treated at application level. 13

91 Inclusion of AMHS Security provisions (5/5) Status of advisory material The sections on security are not as advanced as other elements of the Extended ATSMHS and should be removed, perhaps to another document, to separate specifications from advisory material pertaining to immature requirements. Use of "shall" in Annex D could mislead, as not in line with conventions ( 1.7.3). In response to previous consultation, AMHS security features (message origin authentication, content integrity assurance and supporting mechanisms) are included with informative status only, as a guideline for future deployments. Conclusion on AMHS Security Provisions: No change to the current scope is proposed. To be clarified that shall statements in Annex D only apply to systems claiming SEC conformance. If not, the whole Annex D is not applicable to the system. Threat analysis should be conducted per user application but out of scope of AMHS specification. 14

92 Summary of Responses Regulatory (SES) Status of the Specification vs. System Specification AMHS Constituents Testing and Conformity Assessment Timescales not Defined Granularity of SES traceability 15

93 Status of the Specification 16 Is the CS usable as a System Specification? Can it replace a National Specification? Is it sufficient for obtaining EC Declaration of Conformity or Suitability for Use (of Constituents)? A CS specifies a means of compliance to SES essential requirements and/or implementing rules for interoperability (Article 4 of Regulation 552/2004). Systems / procedures or constituents that meet the relevant CS requirements have presumption of compliance with the essential requirements and/or the implementing rules for interoperability. There is no interoperability implementing rule to refine the essential requirements in the area of ground-ground message handling systems. There is no requirement in the SES Regulations that a CS should be able to replace a national specification. CS compliance can be a key requirement in a system procurement, but is generally not sufficient to specify the functionality not related to interoperability. The EC Declaration of Conformity will refer to Community Specification(s) followed. (ANSPs may identify Constituents as part of an ATM System). Paragraph ( not intended to be a complete system specification sufficient for procurement purposes ) will be clarified.

94 AMHS Constituents AMHS belongs to communications systems and procedures for ground-to-ground [ ] communications (EATMN Systems in Reg (EC) No 552/2004 Annex I) CS should give ANSPs and manufacturers detailed requirements to design, build, maintain and operate the systems and their constituents for implementing Basic ATSMHS or Extended ATSMHS. Constituents should be specified e.g. ATS Message Server, User Agent, AFTN/AMHS Gateway, Access Unit, and if necessary sub-constituents, which are absolutely needed for Basic ATSMHS, or to provide additionally the Extended ATSMHS. It is a function of an IR to determine the constituents (Reg 552/2004 Article 3(3)(c)). ANSPs can also request an EC Declaration of conformity or suitability for use for IOP constituents not covered by IR/CS. The Technical File accompanying the EC Declaration of verification will contain the list of constituents. The draft EUROCONTROL Specification does distinguish between the main candidate constituents of the AMHS; e.g: 17 ATS Message Server A.2.2 (Basic) B.2.2 (Extended) ATS Message User Agent B.2.3 (Extended) A.2.3 (Basic)

95 Testing and Conformity Assessment 18 No test specification is currently available to ensure the correct implementation of the Extended ATSMHS SES implementing rules describe specific conformity assessment procedures. A CS, as a voluntary standard, cannot prescribe the execution of specific tests or the use of a specific test tool. The specific test cases for the Basic ATSMHS in ICAO EUR Doc 020 are not prescribed for SES compliance. They offer a means of assessing the conformity to the Basic level of service, but other tests are possible. It is feasible to define test cases for the Extended ATSMHS. EC Declaration of conformity or suitability for use will describe procedures followed. Records of tests and examinations performed constitute part of the Technical File accompanying the ANSP s EC declaration of verification. The Specification requires ( A.3.2) that tests shall be conducted within a common framework consistent with the procedures in the ICAO EUR AMHS Manual. Reference to Extended ATSMHS Conformance Tests doc will be removed.

96 Timescales not Defined Dates are not specified for compliance with the EUROCONTROL Specification and possible transition measures. Reasonable schedule required for applicability dates for step-wise compliance, taking into account areas where further enabling work is required. Implementation timescales are outside the scope of a EUROCONTROL Specification, which is limited to technical interoperability measures, and is a voluntary means of compliance. Regulation (EC) No 552/2004, Article 3 (3e): Implementing rules for interoperability shall in particular: (e) specify the conditions of implementation including, where appropriate, the date by which all relevant stakeholders are required to comply with them. 19

97 Granularity of SES Traceability Appendix 1 of the draft Specification does not give adequate traceability to the essential requirements (ERs) of Reg 552/2004. Separate matrices for Basic ATSMHS and Extended ATSMHS could be created, such that ER keywords extracted - e.g. from ER 1 (seamless operation) keywords are: designed, built, maintained, operated, information sharing); Evidence provided to every ER and extracted keywords at the constituent level and system level, and if necessary, procedure level; referenced documents contain chapter and paragraph details. No change proposed. The ERs in Regulation 552/2004 are extremely generic and high level - it is difficult to trace meaningfully at a greater level of granularity. Normally, a CS would trace requirements to an associated IR. There are no known precedents for splitting ERs based on keywords as suggested. E.g. ER4.1: Communication systems shall be designed built, maintained and operated using the appropriate and validated procedures, in such as way as to achieve the required performance for a specific application, in particular in terms of communication processing time, integrity, availability and continuity of function. => risk of combinatorial explosion! AMHS is an infrastructure component - required performance for a specific application can only be evaluated in the context of that application. 20

98 Granularity of conformity requirements (continued) Differentiation between Basic ATSMHS and the Extended ATSMHS is possible due to the format of the requirement tags. Example requirement tag: [AMHS-AMU-Axx] Component level: AMU = ATS Message User Agent Basic vs. Extended: A = Annex A (Basic service) B = Annex B (Extended service) Then Appendix 1 allows association with each ER at the Service and Component levels. 21

99 Summary of Responses Technical Issues Support for ATSMHS subsets AMHS user architecture Network protocols Interface Requirements 22

100 Support for ATSMHS subsets It is nowhere specified how the Directory can be used to determine the ATSMHS functional subsets which may be implemented by different systems. It should be clarified at what stage of implementation an ANSP can claim Extended AMHS capability, i.e. which of the listed Extended features and functions are needed. Various approaches are possible, e.g: a) Recipient capabilities known in advance by bilateral agreement. Direct host (application) AMHS users would send only to agreed pre-configured addresses, with compatible capability level. b) The existing ICAO Directory schema can be used to determine user capabilities : IHE supported if the atn-ipm-heading-extensions attribute is TRUE FTBP supported if the exclusively-acceptable-eits attribute includes the file transfer value {joint-iso-itu-t(2) mhs(6) ipms(1) eit(12) file-transfer(0)} SEC supported technically, a sending UA does not need to know this; a non-sec recipient ignores the message security features (they are marked non-critical ). Operationally, this could be achieved at application level, requiring a signed reply in response to a signed message. The draft Specification simplifies the subsetting problem by reducing the options to Configuration IX - {Basic + IHE + DIR + FTBP}. Therefore, any conformant system recipient with atn-ipm-heading-extensions set to TRUE will support IHE and FTBP. 23