AENA, DFS, DSNA, ENAV, EUROCONTROL, FREQUENTIS, INDRA, NATMIG, NORACON, SELEX, THALES

Transcription

1 Document information Project Title Project Number Project Manager Deliverable Name Deliverable ID AIRM Deliverable EUROCONTROL n/a Edition Template Version Task contributors AENA, DFS, DSNA, ENAV, EUROCONTROL, FREQUENTIS, INDRA, NATMIG, NORACON, SELEX, THALES Abstract Within the European SESAR programme, an ATM Information Reference Model (AIRM) was developed with the aim to ensure semantic interoperability within the European ATM Network. The SESAR AIRM constitutes a significant input to Global and European ATM information and services interoperability developments. Indeed, the development of an ICAO AIRM is identified by the ICAO Global Air Navigation Plan (GANP), and the SES Deployment Programme identifies the SESAR AIRM as an input to standardisation in the context of initial SWIM. This document details the strategic objectives for the SESAR AIRM in order to guide its future development and maintenance.

2 Authoring & Approval Prepared By - Authors of the document. Name & Company Position & Title Date Scott Wilson / EUROCONTROL P Project Manager 05/02/2014 Dr Stefan Keller / DFS Project Member 04/03/2014 Reviewed By - Reviewers internal to the project. Name & Company Position & Title Date Gérard Terrien / EUROCONTROL Project Member 04/03/2014 Sam Van der Stricht / EUROCONTROL WP8.1 Deputy Leader 12/02/2015 Dr Robert Suzic / EUROCONTROL Project Member 12/02/2015 Svein Johnsen / NATMIG Project Member 28/04/2015 Joe Gorman / NATMIG Project Member 28/04/2015 Gianluca Marrazzo / SELEX Project Member 28/04/2015 Alberto Anguita Jiménez / INDRA Project Member 28/04/2015 Reviewed By - Other SESAR projects, Airspace Users, staff association, military, Industrial Support, other organisations. Name & Company Position & Title Date Jean-Michel Galais / EUROCONTROL C.03 Project Member 09/02/2015 Juliette Engel / EUROCONTROL B4.3 Project Member 28/04/2015 Klaus-Peter Sternemann / AOPA Airspace User 28/04/2015 Approved for submission to the SJU By - Representatives of the company involved in the project. Name & Company Position & Title Date <Name / Company> <Position / Title> <DD/MM/YYYY> Rejected By - Representatives of the company involved in the project. Name & Company Position & Title Date <Name / Company> <Position / Title> <DD/MM/YYYY> Rational for rejection None. Document History Edition Date Status Author Justification /02/2014 Draft Scott Wilson New Document /03/2014 Revised Draft Scott Wilson Updated after reviews /04/2014 Revised Draft Scott Wilson Updated after reviews /11/2014 Revised Draft Scott Wilson Updated to reflect current situation and to split document into two /01/2015 Revised Draft Scott Wilson Updated with new content 2 of 24

3 /01/2015 Revised Draft Scott Wilson Updated after initial review /01/2015 Revised Draft Scott Wilson More comments processed /02/2015 Revised Draft Scott Wilson /03/2015 Revised Draft Scott Wilson After review by C.03 and WP8 Management After review by AIRM maintenance team /04/2015 Revised Draft Scott Wilson After review by Stefan /05/2016 Final Scott Wilson Reviewed and accepted by AIRM CCB. Intellectual Property Rights (foreground) This deliverable consists of SJU foreground. 3 of 24

4 Table of Contents EXECUTIVE SUMMARY INTRODUCTION PURPOSE OF THE DOCUMENT INTENDED READERSHIP INPUTS FROM OTHER PROJECTS ACRONYMS TERMINOLOGY STRATEGIC DIRECTIONS VALUE PROPOSITION AND STAKEHOLDERS STRATEGIC OBJECTIVES AND GUIDING PRINCIPLES Strategic Objective 1: Ensure the transition from SESAR to post-sesar Strategic Objective 2: Establish the AIRM as a value-adding interoperability provision GUIDING PRINCIPLES Guiding Principle 1: Ensure Widespread Adoption Guiding Principle 2: Ensure Cost-Effectiveness for Stakeholders Guiding Principle 3: Ensure Model Correctness and Cross-Domain Validity GENERAL OVERVIEW OF THE AIRM AIRM PURPOSE AIRM STRUCTURE AND SCOPE The ICAO AIRM The SESAR AIRM and SES AIRM Future Work Opportunities AIRM PROCESSES AIRM MANAGEMENT AND GOVERNANCE During SESAR After SESAR AIRM QUALITY ASSURANCE AIRM STRATEGIC INITIATIVES WITH REGARDS TO OTHER ACTIVITIES Development Phase Drivers Implementations and AIRM Compliance Framework Community of Interest Standards ICAO AIRM International Coordination AIRM DEPLOYMENT AND STANDARDISATION AIRM SUPPORT SESAR SCHEDULE : Finish Research : Establish Maintenance Post-2016: Deployment and Standardisation REFERENCES APPENDIX A LICENCE of 24

5 List of tables Table 1: AIRM 2015 Schedule Table 2: AIRM 2016 Schedule Table 3: AIRM Post-2016 Schedule List of figures Figure 1: AIRM Roadmap Figure 2: AIRM Product Structure Figure 3: SESAR AIRM Landscape Figure 4: ICAO Global Interoperability Framework Figure 5: SES AIRM and ICAO AIRM of 24

6 Executive summary Within the European SESAR programme, an ATM Information Reference Model (AIRM) was developed with the aim to ensure semantic interoperability within the European ATM Network. The SESAR AIRM constitutes a significant input to Global and European ATM information and services interoperability developments. Indeed, the development of an ICAO AIRM is identified by the ICAO Global Air Navigation Plan (GANP), and the SES Deployment Programme identifies the SESAR AIRM as an input to standardisation in the context of initial SWIM. This document details the strategic objectives for the SESAR AIRM in order to guide its future development and maintenance. 6 of 24

7 1 Introduction 1.1 Purpose of the document Within the European SESAR programme, an ATM Information Reference Model (AIRM) was developed with the aim to ensure semantic interoperability within the European ATM Network. This document details the strategic objectives for the SESAR AIRM in order to guide its development. It does this by considering: The purpose and scope of the SESAR AIRM The key relationship between the AIRM and other artefacts and stakeholders The key aims to be met for a high-quality SESAR AIRM The roadmap for standardising and deploying the SESAR AIRM This version of covers the transition from the initial development work within SESAR to a post-sesar steady state situation in which the AIRM is driven primarily by the evolution of the ATM business processes and the resulting system evolution needs. This means that the main focus is on the period of mid-2015 until the end of It is not the purpose of this document to detail the day-to-day work on the SESAR AIRM. This level of detail is handled by a dedicated AIRM Management and Release Plan [4]. The SESAR is approved and published by the AIRM Change Control Board (AIRM CCB). Future evolutions of the strategy are managed through the AIRM governance process [6]. 1.2 Intended readership Members of Members of the AIRM CCB SESAR WP8 Management The SESAR Joint Undertaking 1.3 Inputs from other projects The strategy is in line with: The SESAR Release 4 strategy [1]; The SESAR Architecture and Technical System Strategy [2]; Standardisation Roadmap [3]. 1.4 Acronyms Acronym Definition AIM AIRM AIS AIXM ATM CCB CLDM Aeronautical Information Management ATM Information Reference Model Aeronautical Information Service Aeronautical Information Exchange Model Air Traffic Management Change Control Board Consolidated Logical Data Model 7 of 24

8 Acronym Definition CONOPS EATMA EIF FF-ICE FIXM GANP GIF GML ICAO IM ISO ISRM IWXXM MET NSDMCG OFA OGC PCP SCG SES SESAR SJU SWIM UML WXXM Concept of Operations European ATM Architecture European Interoperability Framework Flight and Flow Information for a Collaborative Environment Flight Information Exchange Model Global Air Navigation Plan Global Interoperability Framework Geography Markup Language International Civil Aviation Organisation Information Model International Organisation for Standardisation Information Service Reference Model ICAO Weather Information Exchange Model Meteorology NextGen-SESAR Data Model Coordination Group Operational Focus Area Open Geospatial Consortium Pilot Common Project Service Coordination Group Single European Sky Single European Sky ATM Research Programme SESAR Joint Undertaking (Agency of the European Commission) System Wide Information Management Unified Modeling Language Weather Information Exchange Model 1.5 Terminology This document uses some prefixes in order to disambiguate all of the AIRM threads : SESAR AIRM. This refers to the AIRM that is developed by SESAR. 8 of 24

9 SES AIRM. This refers to the SESAR AIRM once it is handed over to the deployment body. ICAO AIRM. This refers to the AIRM identified by the ICAO GANP. It is important to note that the prefixes have been added only to disambiguate the multiple AIRM threads. It is not proposed to have multiple, competing AIRMs, but a series of extensions controlled by the Global Interoperability Framework (IGIF) (as explained in section 2.4.4). 9 of 24

10 2 Strategic Directions 2.1 Value Proposition and Stakeholders The AIRM s value proposition is to ensure that information can be shared across domains without introducing ambiguity, in order to mitigate the associated cost efficiency and potential safety risks. Therefore, in order to make the AIRM effective, the addresses the concerns of the following stakeholders: Analysts and architects of ATM business processes who seek to improve the coherency of the ATM system by implementing the concept of Information Services as described in the Global ATM concept (ICAO Doc 9845) [9]. This stakeholder group will benefit: o If the AIRM provides a portfolio of definitions of Information in Flow items that have been pre-agreed across domains. Developers and governance bodies of ATM domain information exchange standards who seek to coordinate with efforts in neighbouring ATM domains. This stakeholder group will benefit in two ways: o o Through saving development effort in their work be reusing pre agreed data structure Through minimizing their coordination effort by not having to coordinate with neighbouring domains individually. Developers and operators of shared ATM information services who seek to ensure that their service can be orchestrated with services developed in other ATM domains, or develop value added application by orchestration. This stakeholder group will benefit in two ways: o The ability to document the data offered by ta service in terms of a cross-domain reference will allow potential customers to cost-efficiently establish the usability of the service for their intended business purposes up front, thus promoting service re-use. o The ability to reliably establish upfront (i.e. at system design time) whether data items received from different sources are semantically equivalent or not will reduce the effort required for system integration and testing. Developers and operators of ATM systems and system components, who seek to ensure that the system logic is based on a consistent semantic interpretation of the incoming and outgoing data flows. In addition, the concerns of regulating bodies who may consider the AIRM as a potential metric of interoperability (in the spirit of EU regulation EC 552/2004) could play a role in shaping the AIRM strategy. 2.2 Strategic Objectives and Guiding Principles Given the time period covered by this version of the strategy, the strategic objectives are: Ensure the transition from SESAR to post-sesar Establish the AIRM as a value-adding interoperability provision Strategic Objective 1: Ensure the transition from SESAR to post-sesar The benefits of the AIRM will only materialize if it is used throughout the lifecycle of operational systems from deployment to replacement. Therefore it is essential that the AIRM is put into operational use in time to have an effect on the initial deployment of the solutions developed in SESAR. 10 of 24

11 Figure 1 illustrates the key relationship between the multiple threads of AIRM development. It shows: As the SESAR AIRM is finalised, mature concepts which have global applicability are fed into the candidate ICAO AIRM. This includes, e.g., the ICAO vocabulary modelled as part of the AIRM Foundation and a set of units of measurement used in ATM. As the SESAR AIRM is finalised, a number of further research topics are identified and added to the SESAR 2020 descriptions of work. As the research mature, the work can be proposed for inclusion in the SES AIRM. Requirements are passed from the ICAO level towards deployment. Therefore the SES AIRM can be seen as a regional extension to the ICAO AIRM. This relationship is further illustrated in Figure 4 which concerns the ICAO Global Interoperability Framework. SESAR ICAO Candidate AIRM 2018 AIRM Global Concepts Requirements Global Concepts Research Deployment SESAR AIRM 2016 SES AIRM Research Topics Research Topics Mature Concepts SESAR 2020 SES AIRM Research Figure 1: AIRM Roadmap Strategic Objective 2: Establish the AIRM as a value-adding interoperability provision Section 2.1 shows that the benefits of the AIRM from an individual stakeholder perspective are quite limited. While it may be convenient to use an existing body of material, if an ATM domain or IT system is considered in isolation it will always be easier and more cost-effective to use the terminology already established in the ATM domain. The benefits of interoperability using the AIRM only materialise if multiple domains actually buy in to using the AIRM for the benefit of the overall system. It is therefore critical to the success of the AIRM effort that this widespread buy in of stakeholders actually happens. That is, a critical mass of actual AIRM uses is required before the AIRM can demonstrate real-world benefit. 2.3 Guiding Principles To achieve the strategic objectives, the development steps taken in the scope of this strategy need to be harmonized by application of the following guiding principles. Actions in conflict with any of these principles should be avoided where possible Guiding Principle 1: Ensure Widespread Adoption Semantic Interoperability is primarily an issue between different and traditionally separated communities of interest. Therefore, it is important that the AIRM concepts are rolled out to the entire 11 of 24

12 ATM community. While there might be issues of different maturity, focussing on the easy, mature domains (e.g. those with established reference models) will limit the positive effects of the AIRM. Consequently, high priority must be given to eliminating barriers to adoption of the AIRM. This may affect not only communication with stakeholders, but also implies (for example) that great care needs to be taken when extrapolating from early adopters to other, less mature communities of interest Guiding Principle 2: Ensure Cost-Effectiveness for Stakeholders The value proposition of the AIRM is ultimately one of cost effectiveness. This must be realised for all stakeholder groups to ensure widespread adoption (objective 2). In must be recognised that using the AIRM may actually induce extra cost for an individual stakeholder. It is therefore imperative that the AIRM products and governance are as user friendly and cost effective as possible Guiding Principle 3: Ensure Model Correctness and Cross- Domain Validity The long-term success of the AIRM approach, as well as its initial adaptation, obviously depends on establishing and supervising the product quality. The key contents are the definitions and logical structures made available. For these, the most important quality criteria are Correctness. Cross-domain acceptance. This obviously requires establishing good working relations with the stakeholder community at large (and in particular with trusted domain experts), but also rigorous and transparent application of procedural and quality management guidelines during the ongoing evolution of the AIRM. 12 of 24

13 3 General Overview of the AIRM 3.1 AIRM Purpose On a strategic level the SESAR AIRM intends to ensure semantic interoperability between systems and services within the European ATM Network. The European Interoperability Framework (EIF), which supports seamless cross-border public services, defines semantic interoperability as concerning the Precise meaning of exchanged information which is preserved and understood by all parties [4]. This goal can be further refined by the statements coming from the ICAO Information Management Panel (IMP) [8]. In early 2015 it met to discuss the creation of the ICAO AIRM identified by the ICAO Global Air Navigation Plan (GANP) [10]. Although the following extract details the ICAO AIRM, the statements are equally applicable to the SES AIRM [8]. The reference model will enable system architects and developers to build system solutions in a more cost-effective fashion. The reference model will be used to align ATM data communities and their associated Configuration Control Boards. [The reference model will facilitate] Seamless information interoperability, quality and reliability between the ATM stakeholders. [The reference model will] Further evolve the exchange models in a more consistent and nonambiguous way. Within SESAR, the AIRM Primer [7] sets out the uses and structure of the SESAR AIRM. It states: The ATM Information Reference Model (AIRM) is used as a common reference for the different information and logical data models that will be developed as part of SESAR. The AIRM represent civil, military and civil-military information constructs relevant to ATM. This means that information constructs from the AIRM can be used, for example: As the standardised and reusable information elements for the description of the information exchanges between information providers and consumers in process models; In a domain model 1 ; As a (semantic) reference for linking models from different domains; As the reference for the definition of the payload (information content) of a shared ATM service; As the reference for the definition of the payload (information content) of a standardised interface between functional blocks of an ATM system. The SES AIRM is expected to be used in all the capacities mentioned. 3.2 AIRM Structure and Scope The ICAO AIRM The ICAO Information Management Panel [8] envisages the development of an AIRM that: Will provide a structured, traceable, unified, harmonised, common, digital reference representation based on standard modelling notation. 1 A domain is a universe of discourse created by a set of strongly coherent and loosely coupled ATM business processes. Examples of domains are Aeronautical Information Management, Airspace Management, etc.. 13 of 24

14 The AIRM scope will, as a minimum, contain the ATM data elements which require information interoperability. This statement is equally applicable to the SESAR and SES AIRM The SESAR AIRM and SES AIRM The SESAR AIRM product structure is given in Figure 2. Figure 2: AIRM Product Structure The components are detailed in the AIRM Primer [7] but a summary is included below: AIRM Primer. The AIRM primer is the entry point into the ATM Information Reference Model (AIRM). It provides an introduction to the AIRM and sets it and each of its components into context. It also outlines those documents that support the usage of the AIRM. AIRM Glossary. This AIRM Glossary provides a simple dictionary of general terms and definitions that may be used to provide consistency across points-of-view and increase semantic interoperability. The glossary consists of a large subset of the terms and definitions from AIRM models. AIRM Foundation. The AIRM Foundation contains the definition of the rules to be applied in modelling the AIRM. In addition, it imports a series of standards in support of the rules. These imported standards provide a set of reusable building blocks such as primitive (e.g. numeric types) and other data types (e.g. geometries) for use in the AIRM. AIRM Information Model. The AIRM Information Model provides a reference model for the SESAR information concepts for operational experts. It contains entities and relationships relevant to the ATM operational discourse and concerns. As such, its scope is ATM-wide. However, in order to support ATM, it also includes entities which are closely related to ATM. AIRM Consolidated Logical Data Model. The AIRM Consolidated Logical Data Model provides a reference model of the SESAR data concepts for service architects and system implementers. It contains the data entities necessary to model the shared information of ATM. It can be used in order to construct derived logical data models and, indeed, information exchange models. As such, it can be used to create a model that can be used to build services and operations. AIRM Constraints Model. The AIRM Constraints Model provides the ATM operational and structural constraints which have an impact on the content of the AIRM Information Model 14 of 24

15 and/or the AIRM Consolidated Logical Data Model and which cannot be easily expressed in a diagrammatic notation. These can be used to restrict the information exchange models. As shown in figure 1, the intention is to use SESAR AIRM as baseline for the SES AIRM, hence the initial product structure of the SES AIRM is expected to be essentially the same Future Work Semantic of Metadata In addition to the ICAO AIRM itself, the ICAO Information Management Panel [8] envisages the development of: Common information management provisions addressing inter alia descriptive (meta) data, model extensibility and technical conventions. These aspects are not fully explored by the SESAR AIRM. However, several other work-streams inside the SESAR organisation and in standardization bodies outside SESAR have dealt with aspects of this topic. Generally, in a very early stage of establishing interoperability a capability is required to find information and determine whether the information itself and its delivery mechanisms are fit-forpurpose. All this information is metadata of the actual information exchange. As a prerequisite to this, there is a need to agree the meaning of each of the metadata fields whether they describe information discovery ( registry ), information delivery ( service ) or the information itself ( dataset ). While the registry and service concepts themselves are obviously not components of semantic interoperability, defining the semantics of the metadata is generally considered a part of the semantic interoperability framework. In other words, information discovery and information delivery metadata are additional in-scope domains. This view is, for instance, supported by the European Interoperability Framework which firmly places all types of metadata within the sphere of semantic interoperability. Consequently, replicating the approach taken in developing the AIRM subject fields, the SESAR AIRM community should collaborate with the stakeholders of the information discovery ( registry ) and information delivery ( services ) domains to elaborate the relevant metadata definitions. For this activity, it would bring to the table: The experience gathered with dataset metadata for geospatial information (ISO 19115) that is already part of the AIRM foundation and is referenced by the AIRM model components, and The AIRM foundation itself as a proven framework for creating semantic reference material. This activity is clearly in line with Guiding Principle 1 Ensure Adoption. It could ultimately lead to an integrated metadata profile for ATM at large, with potential domain specific extensions. In this way, the AIRM could generate added-value by transversely supporting other components of the global interoperability framework, in line with strategic objective Opportunities Opportunities to further strengthen semantic interoperability should be acted on as they are identified. 15 of 24

16 4 AIRM Processes 4.1 AIRM Management and Governance During SESAR Until the end of Q1/ 2016, the SESAR AIRM will be developed under the SESAR 1 Programme. Decisions on changes to the SESAR AIRM, including changes to the, are made by the AIRM Change Control Board (see [6]). This mechanism ensures that the SESAR AIRM stakeholders have a say in the development of the SESAR AIRM After SESAR The SESAR Programme is scheduled to close by the end of It is intended that the SESAR AIRM will be handed-over to a different body for deployment, standardisation, maintenance and further development at the end of 2016 (see also Figure 1). At the time of writing this version of the strategy, the identity of the recipient body is unknown. However, given that the current AIRM CCB is seen as fit-for-purpose it is proposed to continue this body as a SES AIRM CCB with the addition of some new stakeholders. Given that the AIM/SWIM Team today provides a working forum to strike high-level agreements on information exchange related matters on a pan-european scale, it would appear to be a natural candidate for providing the organisational and decision making context under which the technical support and facilitation for the SES AIRM and the SES AIRM CCB could be provided. 4.2 AIRM Quality Assurance In theory, it is possible to say that no model is ever correct. This relates to the nature of abstraction itself. But models are very powerful collaboration means when related to clear objectives and built with usability in mind, thus achieving the quality needed and bringing the expected added-value. Consequently, the intention is to build high quality SESAR AIRM UML models. Therefore, an AIRM Quality Assurance Handbook has been created to outline what high quality means in connection with the SESAR AIRM. The following is an extract of the AIRM Quality Assurance Handbook [5]. 1. The AIRM UML models apply the AIRM Rulebook (Verification) 2. The AIRM UML models shall be consistent (Consistency) 3. The AIRM UML models shall be understandable (Understandable) 4. The AIRM UML models shall be usable as a semantic reference (Usability) 5. The AIRM UML models shall be comprehensive (Comprehensive) 6. The AIRM UML models shall be useable in different contexts (Flexibility) 7. The AIRM UML models shall be managed. (Stability) 16 of 24

17 5 AIRM Strategic Initiatives with Regards to Other Activities Figure 3 illustrates the key activities and how they relate to the SESAR AIRM. These relationships help to define the priorities and content of the SESAR AIRM. The sub-sections detail each of these relationships. AIRM Management AIRM Governance Drivers ICAO, CONOPS, OFA, EATMA, V&V EXE, SWIM AIRM Quality Assurance AIRM ICAO AIRM AIRM Compliance Framework Implementations Service, Systems Community of Interest Standards AIXM, WXXM, FIXM... Figure 3: SESAR AIRM Landscape Development Phase Drivers During the current Research and Development phase, the main drivers for the content of the SESAR AIRM come from ICAO, the SESAR CONOPS, SESAR Operational Focus Area (OFA) activity, the European ATM Architecture (EATMA), and the various validation and verification exercises running within SESAR. Furthermore, a SWIM Foundation is being developed in support of Initial SWIM (iswim) deployment as identified by the draft deployment programme under the umbrella of the Deployment Alliance. At this stage it is only possible to state that a number of performance-based essential requirements on information are foreseen as part of the SWIM Foundation. The goal is to ensure that the SESAR AIRM will act as a standard means of compliance to some of the requirements Implementations and AIRM Compliance Framework Service implementations and systems also act as a driver to the SESAR AIRM. These rely on information exchange models/physical models. 17 of 24

18 In order to deliver the benefits of semantic interoperability using the AIRM, it is important that a critical mass of these models / specifications of data representations can be shown to be compliant to the semantics of the SESAR AIRM. Therefore work is undertaken to ensure that implementations can demonstrate their compliance with the SESAR AIRM, and to actively support them in adapting this approach. The AIRM Compliance Framework has been created to define the processes whereby implementations can demonstrate compliance with the semantics of the AIRM. This framework will be handed over to the AIRM CCB for maintenance Community of Interest Standards Community of interest standards include standardised information exchange models such as AIXM, WXXM and FIXM. Many more models could be listed such as the IATA s Aviation Information Data Exchange (AIDX) model and the EUROCAE/RTCA Aerodrome Mapping standard ED99/ED119. Ultimately, the community of interest standards shall be compliant with the semantics of the ICAO AIRM. During the SESAR Programme, the AIRM Compliance Framework is applied in order to ensure the standards are compliant with the semantics of the SESAR AIRM. It should be noted that the standards should rely on the same technical foundations in order to allow greater interoperability between different ATM data domains. These common foundations may include: Standards from the ISO series, such as GML; OGC standards and best practices. However, this technical foundation is outside the scope of the AIRM. In the scope of this strategy, work will continue to ensure that a critical mass of standardised community of interest models (most notably the three core models mentioned above) are compliant with the SESAR AIRM ICAO AIRM The requirement for an ATM Information Reference Model (AIRM) was identified in the ICAO Global Air Navigation Plan (GANP) [10]. The 12th Air Navigation Conference endorsed the creation of an ATM Information Reference Model (AIRM) and an ATM Information Services Reference Model (ISRM), acting as an overarching reference for the ATM domains: Flight, AIM, MET, Surveillance etc. Work was undertaken in the context of the SESAR AIRM to explore the ICAO AIRM concept. The current intention is to create a candidate ICAO AIRM which builds upon the outcome of SESAR. It is acknowledged that not all parts of the SESAR AIRM need to be promoted to the ICAO level. With this in mind, an ICAO Global Interoperability Framework (IGIF) is proposed which includes several frameworks including the Semantic Interoperability Framework. 18 of 24

19 Figure 4: ICAO Global Interoperability Framework The IGIF proposes a pyramid structure with ICAO at the top and regional/local frameworks which specialise ICAO. This allows an ICAO AIRM and a SES AIRM to complement each other as seen in Figure 5. Figure 5: SES AIRM and ICAO AIRM International Coordination Work on defining the candidate ICAO AIRM and IGIF is undertaken by the NextGen-SESAR Data Model Coordination Group (NSDMCG) under Coordination Plan 2.1. It is expected that the NSDMCG will be enlarged with other representations leading to the proposition of a concrete ICAO AIRM during subsequent ICAO IM Panel meetings. 19 of 24

20 5.2 AIRM Deployment and Standardisation Due to the central role of the AIRM in an overall compliance framework, it is expected and actually desirable to apply some sort of formal standardisation, as is indeed foreseen in the SESAR standardisation roadmap. However the standardisation approach is as yet unknown. At this point, it can only be reported that the SESAR standardisation roadmap (in view of the needs of the ICAO GANP and the European Commission s Pilot Common Project) sets 2017 as the required timeframe for availability of the standard, which is well within the scope of this strategy. It must be concluded that while this seems possible from a content point of view, it may be necessary to revise the present strategy once the standardisation approach is defined. Regardless of the formal standardisation framework, the SES AIRM should be an open standard published under a BSD licence such as found in Appendix A. This is an important factor in minimizing the risk that legal constraints will jeopardize adaption of the AIRM. The intent of a BSD licence is to protect the SES AIRM as an open standard from claims of ownership by third parties. With the same rationale, the SES AIRM will be made available free for charge to the public. 5.3 AIRM Support The AIRM Primer [7] details the supporting wiki that is evolving over time. It is used to share guidance material and best practices in order to support the use of the SESAR AIRM. The support material should be expanded as the SESAR AIRM is finalised. The support material should include tools to support the usage of the SESAR AIRM and a dedicated website. 5.4 SESAR 2020 The final details on SESAR 2020 are not known at the time of writing this version of the AIRM Strategy. However, it is expected that the SESAR AIRM will be handed over to a deployment body. That body can use SESAR 2020 to perform further research on a number of topics. Once the concepts have been matured they can be fed into the SES AIRM using the AIRM governance mechanisms (e.g. the AIRM CCB). This further means that the AIRM as a SESAR1 deliverable is qualified as mature for deployment. Hence it is expected that the further work on AIRM will spread over activities that are part of the support to standardisation in the context of SESAR deployment and further research as part of SESAR of 24

21 6 Schedule The schedule for developing the AIRM can be divided into a number of phases: Post : Finish Research Schedule SESAR AIRM v3.3.0 March SESAR AIRM v3.3.1 May SESAR AIRM v4.0.0 September SESAR AIRM v4.0.1 (optional) November 2015 Table 1: AIRM 2015 Schedule : Establish Maintenance Schedule SESAR AIRM v4.1.0 (optional) March SESAR AIRM v4.2.1 (optional) July Candidate ICAO AIRM Work will be ongoing Table 2: AIRM 2016 Schedule Post-2016: Deployment and Standardisation Schedule Post SES AIRM Start Research Topics ICAO AIRM IOC 2018 Table 3: AIRM Post-2016 Schedule 21 of 24

22 7 References [1] SJU, Release Strategy 2014 [2] SJU, Architecture and Technical System Strategy [3] Standardisation Roadmap [4] AIRM Management and Release Plan [5] AIRM Quality Assurance Handbook [6] AIRM Governance Handbook [7] AIRM Primer [8] ICAO Information Management Panel (IM Panel), job-card on Information Architecture & Management [9] ICAO Doc Global ATM concept [10] ICAO Global Air Navigation Plan (GANP) 22 of 24

23 Appendix A Licence Copyright (c) 2016, SESAR Joint Undertaking =========================================== All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the disclaimer in the documentation and/or other materials provided with the distribution. * Neither the names of the SESAR Joint Undertaking nor the names of its contributors may be used to endorse or promote products derived from this specification without specific prior written permission. DISCLAIMER THIS SPECIFICATION IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ========================================== Editorial note: this license is an instance of the BSD license template as provided by the Open Source Initiative: Details on the SJU and its members: 23 of 24

24 -END OF DOCUMENT- 24 of 24