1. The European Organisation for the Safety of Air Navigation Focus Area: Meteorology “What Scott promised” The CRs from MET AIRM Review Forum – 12-Sept-2011 Dennis HART, DSR/CMN/IM

2. The CRs discussed in the MET domain AIRM Rulebook adherence ICAO Annex 3 adherence Volcanic Ash Representation OGC TestBed observations Namespaces ISO/OGC Observation & Measurement model v2 adherence Extension points

3. The CRs that survived (partly) AIRM Rulebook adherence ICAO Annex 3 adherence Volcanic Ash Representation OGC TestBed observations Namespaces ISO/OGC Observation & Measurement model v2 adherence Extension points

4. The European Organisation for the Safety of Air Navigation Focus Area: Meteorology “Lean and Mean” WXXM from AIRM AIRM Review Forum – 12-Sept-2011 Dennis HART & Hubert LEPORI, DSR/CMN/IM

5. Global Interoperability Global consensus: User requirements for MET could differ around the globe MET provision capability could differ around the globe MET Information exchange needs to be standardised

6. Global Interoperability SESAR AIRM version 1.1.1 --- MET IM, LDM, XML schema v1.1 MET contribution to SESAR ATM Information Exchange ‘AIRM’ centric WXCM/WXXM/WXXS version 1.1.3 Global draft specification for MET information exchange Baseline for ICAO & WMO adoption Data domain centric Notion of ATM Information Exchange/Management under development FAA  NextGen moving fast ICAO – WMO  Will probably take slightly longer

7. Facing reality in MET World Meteorological Organization ICAO

8. ‘lean and mean’ WXXM from AIRM Developing the AIRM whilst assuring global interoperability for the coming years AIRM  WXXM Pragmatic Automated (preferably) SESAR centric Designated task in P08.01.06 Question raised: Can we have a WXXM derived from the AIRM CLDM v.v.?

9. This image can only be used for AIS AGORA Promotion. The reproduction of the individual logos and their use requires the permission of the respective owner

10. Solution Sets, the options

11. “lean and mean” WXXM from AIRM 11 Option 1: WXXM = MET part of AIRM WXCM WXXM WXXS AIRM IM (MET) AIRM CLDM (MET) WXXS traces Replaced by AIRM – managed by AIRM CCB

12. “lean and mean” WXXM from AIRM 12 Option 1: WXXM – AIRM: gap analysis WXXM = “implementation independent, capable of supporting multiple physical implementations” WXXM follows the GML object-property model, which requires the properties of objects to be encapsulated by a simple type The WXXS is entirely machine-generated from the UML model. […] The toolset used to work with the UML model and generate the schema includes […] FullMoon. FullMoon official Web site & CSIRO Web siteFullMoon official Web siteWeb site FullMoon supports the processing of a UML «Application Schema», exported as an XMI document. FullMoon is able to process only an application schema which follows the ISO 19101 & ISO 19109 general feature model. WXXM

13. “lean and mean” WXXM from AIRM 13 Option 1: WXXM – AIRM: gap analysis ISO 19109 Rules For Application Schema: application schema conceptual schema for data required by one or more applications application manipulation and processing of data in support of user requirements 6.1 Purpose of an application schema An application schema is a conceptual schema for data required by one or more applications. An application schema defines - content and structure of data; and - specifications of operations for manipulating and processing data by an application. The purpose of an application schema is twofold: - to provide a computer-readable data description defining the data structure, which makes it possible to apply automated mechanisms for data management; and - to achieve a common and correct understanding of the data, by documenting the data content of the particular application field, thereby making it possible to unambiguously retrieve information from the data. WXXM is a UML Application Schema in the ISO 19109 sense WXXM

14. “lean and mean” WXXM from AIRM 14 Option 1: WXXM – AIRM: gap analysis WXXM includes XML or GML-related properties for UML classes and UML attributes, as required by FullMoon WXXM WXXM is NOT technology independent. It is an ISO 19109 Application Schema, extended with some XML/GML elements required to enable the generation of WXXS.

15. “lean and mean” WXXM from AIRM 15 Option 1: WXXM – AIRM: gap analysis Principle 3 The AIRM Consolidated Logical Data Model contains definitions of entities that are part of an ATM operational language, satisfying operational requirements and concerns. The entities are defined without the consideration of solution, system and implementation aspects. Rule 2 The AIRM models shall not contain model constructs with a purpose to support a specific implementation, algorithm, technology or solution. Note: Adding such constructs to a model in general imposes constraints that may make a model unnecessarily dependent on implementation decisions. The AIRM models should be focused on describing information needs independent of implementation and technological decisions. According to these rules, the AIRM shall only define a common semantic. In particular, the AIRM CLDM shall not contain “specifications of operations for manipulating and processing data by an application.” AIRM The AIRM does not qualify as an ISO 19109 Application schema The AIRM is technology independent.

16. “lean and mean” WXXM from AIRM 16 Option 1: WXXM – AIRM: gap analysis With the current AIRM and WXXM principles, Option 1 is NOT feasible. AIRMWXXM Option 1 AIRMWXXM Technology independent ? YESNO ISO 19109 UML Application schema ? NOYES

17. “lean and mean” WXXM from AIRM 17 Option 2: derive WXXM from AIRM AIRM IM WXXS AIRM CLDM traces AIRM – managed by AIRM CCB WXCM WXXM traces Derive WXCM WXXM WXXS traces

18. “lean and mean” WXXM from AIRM 18 Option 2: derive WXXM from AIRM Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model

19. “lean and mean” WXXM from AIRM 19 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model  Remove WXXM-specific Tagged Values  Remove stereotypes

20. “lean and mean” WXXM from AIRM 20 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model  Update the multiplicity of attributes In WXXM, the multiplicity [0..1] is displayed In AIRM, [0..1] is the default multiplicity (Rule 22). Rule 22 Attributes shall, by default, be represented with multiplicity of [0..1] (zero to one). If an operational constraint has been identified then multiplicities should be chosen to reflect such constraints.

21. “lean and mean” WXXM from AIRM 21 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Apply the AIRM Rulebook to the AIRM v1.1.1 MET package  The AIRM separates the Datatypes from the Subject fields  The properties typed with a Datatype (enumeration…) are modelled using UML attributes, and not of UML roles  Reversely, properties typed with Subject Fields are modelled using UML roles instead of UML attributes

22. “lean and mean” WXXM from AIRM 22 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Apply the AIRM Rulebook to the AIRM v1.1.1 MET package  Results: Updated package “Meteorology” in the CLDM: Contains the WXXM 1.1.3 concepts, Complies with the AIRM Foundation Rulebook Contains also new MET elements originating from other Domain Projects (AirportMeteorology)  All the concepts defined in this package are modelled consistently, according to the AIRM rules.

23. “lean and mean” WXXM from AIRM 23 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Define AIRM=>WXXM mapping rules AIRM CLDM WXXM Derive  Restore technology-specific information (stereotypes, tagged values…)  Replace associations by attributes  Replace attributes by associations  Update attributes/associations cardinalities ([0..1] for attributes)  Model clean-up: keep only The complete Meteorology package The classes from the other SubjectField packages which are connected at least to one MET element The classes from the Datatypes package which are used to type a MET property

24. “lean and mean” WXXM from AIRM 24 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM

25. “lean and mean” WXXM from AIRM 25 Apply the AIRM Rulebook to the AIRM v1.1.1 MET package Define AIRM=>WXXM mapping rules Implement mapping rules: programmatically recreate a “WXXM-like” model from the AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model Option 2: derive WXXM from AIRM Gap analysis: WXXM 1.1.3 vs “WXXM-like” model  No exact match Missing concepts / associations WXXM design rules may not be always consistent …  However, the solution should work fine with a more elaborated AIRM content and clearer AIRM=>WXXM rules

26. “lean and mean” WXXM from AIRM 26 Option 2: derive WXXM from AIRM Option 2 is feasible, provided the right mapping rules are specified Option 2 does not question the AIRM foundation rules nor the key WXXM principles The mapping can be (partially) automated WXXM can become an “AIRM-compliant” ISO 19109 Application Schema for Aviation Meteorology

27. “lean and mean” WXXM from AIRM 27 Looking now at the bigger picture… Let’s take a step back and look at the subject from a broader perspective ! We are trying to map a subset of AIRM concepts into an ISO 19109 Application Schema and subsequent physical model This is NOT specific to the MET Domain !

28. “lean and mean” WXXM from AIRM 28 “AIRM => ISO 19109 Application Schema” Mapping Rules “AIRM => AIXM” Mapping rules “AIRM => TICM” Mapping rules … METAerodrome Airspace Env Terrain … AIRM CLDM Subject Fields AIS Domain AIXM 5.1 WXXM Terrain information 8.1.4 Domain Model for Terrain

29. “lean and mean” WXXM from AIRM 29 Which “AIRM-compliant” physical models for SWIM services ? Type of Business Service * Strategic phase Pre-tactical phase (D-1) Tactical phase … MET Aerodrome Airspace … Utility Service Trajectory management Flight Operation … SWIM Service Taxonomy ** Service Life Cycle * From B4.3-D11 Service Scope & Approach Technological binding TBD Example: WFS 2.0 Pub/Sub … Utility Service providing MET data for the Pre-tactical and tactical phases Technological binding: ► WFS 2.0 ► An AIRM-compliant ISO 19109 Application Schema would satisfy my requirements ► Apply the mapping rules AIRM=>ISO Application schema to the AIRM MET subject field ► WXXM / WXXS is suitable ! EXAMPLE ** SWIM service taxonomy NOT formally defined in Sept 2011 ATM Domain

30. “lean and mean” WXXM from AIRM 30 Conclusion The AIRM defines the shared ATM concepts & the AIRM governance is now up and running WP B is moving forward with regards to the definition of the SWIM Service taxonomy Some 8.1.x projects have started to map subsets of the AIRM CLDM into other models that enable the generation of ad-hoc physical models Time to close the loop and prototype the services !

31. “lean and mean” WXXM from AIRM 31