1 / 31

AIXM – why necessary

AIXM – why necessary. EAD Feasibility Study (by “CAPdebis”) - 1993

abel-casey
Download Presentation

AIXM – why necessary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. AIXM – why necessary • EAD Feasibility Study (by “CAPdebis”) - 1993 • “The exchange of static data in an electronic format is rare for ground based systems. Other than ARINC 424 format, which was developed according to the demands of FMS, a state of the art, commonly used standard format for the exchange of static data information […] is not available.” • Need for aeronautical information logical model + data exchange format • For the implementation of the European AIS Database (EAD) • Basis for eAIP • Contribution to ICAO (AIS/MAP Divisional Meeting of 1998) • For industry implementations • etc.

  2. AIXM Scope Air Transportation Information Airspace structures and routes Ground Infrastructure Rules and procedures Terrain and obstacles Passenger MET Surveillance Flight

  3. AIP AIXM Development Sources

  4. <AIXM-Snapshot> <AIXM-Snapshot> <AIXM-Snapshot> <AIXM-Update> <AIXM-Update> AIXM 4.5: two main components AIXM – Logical Information Model <AIXM-Snapshot> <Vor> <VorUid> <codeID>AML</codeID> <geoLat>34.3928N</geoLat> <geoLon>123.4333W</geoLon> </VorUid> … </AIXM-Snapshot> AIXM – Data Exchange Format

  5. AICM 4.5 Web Based Training

  6. AIXM in EAD (today) Chart Production Static data Update (e)AIP Production (SDO) Based on AIXM 4.5 Digital Data Input (AIXM 4.5 XML) Support NOTAM production Provided by industry. Similar implementation in local AIS systems AIXM 4.5 / 5.1 XML output

  7. AIXM version 5 Joint development EUROCONTROL – FAA (with the support of the international AIS community)

  8. AIXM 5 Design Objectives New capabilities Expand/Refresh Domain Model Modularity Technical Design Decisions Extensibility Aerodrome Mapping ISO19100series FlexibleExchange Terminal Procedures UML FlexibleMessages Obstacles GML 3.2 Static and Dynamic Metadata Integrity External Constraints

  9. XSD Temporality Concept AIXM version 5.1 UML www.aixm.aero

  10. AIXM 5.1 – Digital NOTAM capability TWY closure • Currently, published as NOTAM A0874/03 NOTAMN Q) EBBU/QMXLC/IV/M/A/000/999/5054N00429E005 A) EBBR B) 0308250500 C) 0310271600 E) TAXIWAYS OUTER 7 AND E6 CLSD <OK for computers> <not OK for computers> • With Digital NOTAM - AIXM 5.1 encoded message • Something like this … <taxiway> <name>OUTER 7</name> <status>CLOSED</status> </taxiway> <taxiway> <name>E6</name> <status>CLOSED</status> </taxiway>

  11. AIXM Temporality document

  12. www.aixm.aero

  13. www.aixm.aero/wiki AIXM Wiki

  14. AIXM Forum

  15. Implementation Guidance • GML Guidelines for aviation data • Encoding rules / conventions • Profile • OGC Aviation Domain WG • See OGC Portal

  16. Implementation Guidance • Use of xlink:href and UUID

  17. Implementation Guidance • Metadata Profile • Requirements for Aviation Metadata • Guidance on the Aviation Metadata Profile

  18. - Does the data make sense? - Is it compliant with international standards ? - Do I respect recommended practices? - … AIXM 5.1UML AIXM 5.1XML AIXM 5.1XSD Airportfeatures Business Rules Validation of AIXM 5.1 = Syntactic check Semantic check - Check the compliance of an XML dataset with the XSD grammar - Performed by standard XML parsers (e.g. xerxes, MSXML, XMLSpy, etc.)

  19. Aeronautical Data Quality (ADQ) • ADQ 1 • COMMISSION REGULATION (EU) No 73/2010 • “laying down requirements on the quality of aeronautical data and aeronautical information for the single European sky” • Basically; Turning Annex 15 into European Law • Compliance dates: 2013-2017 • Means of Compliance • Electronic AIP (eAIP) Published • Aeronautical Information Exchange (AIX) Final Draft • AIXM 5.1 is proposed as compliant model • Data Quality Requirements (DQR) Under development • Data Assurance Levels (DAL) Under development • Data Origination (DO) Under development

  20. AIXM 5.1 Mappings • Aeronautical Information Publication (AIP) into AIXM 5.1 • See www.aixm.aero/wiki -> Mappings • Status: review in progress

  21. AIXM 5.1 Mappings • Airport Mapping Requirements • See www.aixm.aero/wiki -> Mappings • ED 99/DO 272 (A/B/C) into AIXM 5.1 • Status: review in progress • Includes an AIXM 5.1-AMDB extension

  22. AIXM 5.1 Mappings • AIXM 4.5 Conversion Guidelines • See www.aixm.aero/wiki -> Mappings • Status: proposed release • More detailed mapping developed by EAD • Based on actual EAD data

  23. ICAO AIS to AIM Roadmap 3 phases 21 inter-related steps Time

  24. AIXM 5.1 proposed to ICAO mandate International AIXM Change Control Board AIS-AIM SG AIXM 5.1 and further Updates AIXM 5.0 Pre-AIXM 5 2011 2012 2010 2009 2008 2007 2006

  25. AIXM Change Control Board - mandate • Transparency • Stakeholder representation • States, Military • ANSP, Service Providers • Airlines, Airports • Manufacturing industry • Decisions by consensus! • Change proposals developed collectively • If no serious disagreement with a change proposal is notified (silent process) -> adopted • A widely acceptable solution needs to be found for any issue!

  26. Registration process • CCB • See link on http://www.aixm.aero • One representative per organisation/company (or Department for very large organisations • No deadline, you are welcome at any time! • CCAB • Eurocontrol and FAA will contact organisations/groups as indicated in the Charter to seek participation in the CCAB

  27. Future versions • Proposed • Minor Release AIXM 5.1.1 in 2013 (April-May) • XML Schema improvements/corrections, such as: • gml:identifier for <<object>> • allow empty AIXM_BasicMessage • bug corrections (spelling errors) • UML model • No changes to classes, attributes, associations • Possibly, improvements of definitions • Migration from RationalRose (IBM) to EA (Sparx)

  28. Future versions • Proposed • Regular update AIXM 5.2 by mid 2014 • backwards compatible with AIXM 5.1 • deprecation instead of simple removal • allow new classes, properties, associations where operationally required • Including mapping rules to AIXM 5.1 • eventually mapping code (XSLT) provided as part of the release

  29. Questions?

More Related