1 / 28

Integrating information towards Digital ATM

Integrating information towards Digital ATM. Information Structures - AIXM -. Presented By: Eduard Porosnicu, Eurocontrol Date: August 27, 2013. AIXM 1.1 (April 1998). AIXM 1.1 (April 1998). AIXM 3.1 (Oct 2002). <?xml version="1.0" encoding="UTF-8"?>

alvaro
Download Presentation

Integrating information towards Digital ATM

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. Integrating information towards Digital ATM Information Structures - AIXM - Presented By: Eduard Porosnicu, Eurocontrol Date: August 27, 2013

  2. AIXM 1.1 (April 1998)

  3. AIXM 1.1 (April 1998)

  4. AIXM 3.1 (Oct 2002) <?xml version="1.0" encoding="UTF-8"?> <AIXM-update xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="AIXM-Update.xsd" version="0.9.1" effective="2001-10-23T00:00:00" origin="EAD" number="1" created="2001-06-01T15:25:34"> <Group Reason="Vor 'BXL' has been re-located and complemented with a Dme facility"> <Changed> <!-- The location of the Vor is changed, thus a change in the unique identifier Therefore the old unique identifier <VorUid> is mentioned first--> <VorUid> <codeId>BXL</codeId> <geoLat>514333.34N</geoLat> <geoLong>0032301.21E</geoLong> </VorUid> <Vor> <VorUid> <codeId>BXL</codeId> <geoLat>514326.67N</geoLat> <geoLong>0032345.37E</geoLong> </VorUid> <OrgUid> <txtName>BELGIUM</txtName> </OrgUid> <txtNamechg="1">BRUSSELS VOR</txtName> <codeType>DVOR</codeType> <valFreq>119.00</valFreq> <uomFreq>MHZ</uomFreq> <codeTypeNorth>MAG</codeTypeNorth> <codeDatum>WGE</codeDatum> <Vtt> <codeWorkHr>H24</codeWorkHr> </Vtt> </Vor> </Changed>

  5. Content • AIXM Versions in use • Progress areas since ATIEC 2012 • Future versions • Global coordination

  6. Versions in use - AIXM 4.5 • Published: 2005 • Entity/Relationship • Custom XML schema • Core AIP data • Use: • European AIS Database (EAD) and European national systems • Estimated 20+ national systems world-wide…

  7. Versions in use - AIXM 5.0 • Published: MAR 2008 • UML Model • GML Schema • Full AIP/NOTAM data • Including obstacle, airport mapping, etc. • Metadata • Extensibility • Use: • Partially, by FAA and NGA

  8. Current version – AIXM 5.1 • Published: FEB 2010 • Update of AIXM 5.0 • Usage/availability model • Notes vs. descriptions • Other adjustments to facilitate Digital NOTAM encoding • Use • good news, see next slide !

  9. Current version – AIXM 5.1

  10. Tools for AIXM 5.1 data visualisation

  11. Coding/usage guidelines • AIXM Temporality Concept (FEB 2010) • Feature Identification and Reference (APR 2011) • OGC Aviation Domain Working Group • Metadata Guidelines for Aviation Data (MAR 2011) • Use of GML for Aviation Data (MAY 2012) • OGC test beds • WFS/FES Temporality Extension (Engineering Report) • Digital NOTAM • version 1.0 - JUN 2011 • version 2.0 – in preparation for publication • Work in progress • Obstacle data • SID/STAR/Approach Procedures… • Business rules

  12. AIXM 5.1 Mappings - updates • AIXM 4.5 Conversion Guidelines • See www.aixm.aero/wiki -> Mappings, version 1.1 • Status: Released • Including feedback from EAD mapping

  13. AIXM 5.1 Mappings - updates • Airport Mapping Requirements • See www.aixm.aero/wiki -> Mappings • ED 99/DO 272 (A/B/C) into AIXM 5.1 • Version 0.7 based on feed-back from FAA and AeroNavData • Includes an AIXM 5.1-AMDB extension

  14. Coding/usage guidelines • XHTML profile/guidelines for AIXM ?

  15. Increment 1 scenarios • Increment 2 scenarios • Published special activity area – activation • Displaced threshold • Published ATS airspace - activation or deactivation • Declared distances changes • Ad-hoc special activity area – creation • Runway portion closure • Ad-hoc ATS airspace – creation • Airport Usage limitation • Route portion closure • Runway usage limitation • Route portion opening • Taxiway usage limitation • Aerodrome closure • Approach lights unserviceable • Runway closure • Approach lights downgraded • Navaid unserviceable • Runway lights unserviceable • New obstacle • Obstacle lights unserviceable • Taxiway closure • Visual Approach slope indicator unserviceable • Surface contamination (SNOWTAM) • Taxiway lights unserviceable • Other Event (any other situation that does not have a dedicated scenario) Digital NOTAM • Event Specification – version 2.0 in preparation

  16. FAA Digital NOTAM Beta Testing

  17. Business Rules • Prevent • doubtful data (from a business point of view) • syntactical flaws, such as Baseline with TimeInstant, missing srsName, etc. • In general, give confidence to the recipient that the data is fit for purpose! • Critical for Digital NOTAM applications! • Work in progress • Focus on Airspace • Use of SBVR Standard • Small focus group, will become public by end September

  18. Industry developments OGC test beds (OWS-9) Links page on www.aixm.aero

  19. ICAO Adoption • Annex 15 AMDT 37 • AIXM as means of compliance • More details in AIS Manual (DOC 8126) and later possibly in a PANS-AIM

  20. Future versions

  21. Future versions • ATIEC 2012 Too early…. Now planned : Q1 2014 Intended : 2015

  22. AIXM CCB • Currently 30 issues recorded • 14 Bugs • 14 Possible enhancements • 2 possible new features • Ad-hoc face-to-face meeting on Monday, 26 August • AIXM 5.1.1 • Migration to EA (Sparx) • Minor corrections only: spelling errors, schema bugs, UML/XML discrepancies, lists of values • Definitions improvements

  23. WXXM Coordination • AvXML 1.0 RC-2 • Simple Aeronautical Feature (SAF) model

  24. FIXM coordination • AIXM provides the “infrastructure” part

  25. Conclusions • Conceptual/logical model level • Coherence AIXM/FIXM is a key issue (through a global AIRM) • SID/STAR/IAP (including procedure design) model, free flight airspace, flight restrictions are model areas expected to require some refreshment in AIXM 5.2 • Work in progress (high priority topics) for 2013-2014 • business rules • digital NOTAM encoding (increment 2) • procedures encoding • AIXM 5.1.1 – minor correction

  26. Questions

  27. Contact Information • www.aixm.aero • www.aixm.aero/wiki • Eddy Porosnicu (EUROCONTROL) • eduard.porosnicu@eurocontrol.int • +32 (2) 729-3326 • Diana Young (FAA) • diana.young@faa.gov • +1 (202) 385-7445

More Related