George BALDEHRO/AIM

AIXM –Purpose, Scope, implementation and

future evolution(Dakar, Senegal, 3-5 October 2016)

Agenda Items 6b

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.

AIXM Scope

Air Transportation Information

MET

Ground Infrastructure Rules and procedures

Airspace structures and routes

Flight

Passenger

Surveillance

Terrain and obstacles

Sources

AIP

Sep 2005

AIXM 4.5

AIXM Development

<AIXM-Snapshot>

<Vor>

<VorUid>

<codeID>AML</codeID>

<geoLat>34.3928N</geoLat>

<geoLon>123.4333W</geoLon>

</VorUid>

…

</AIXM-Snapshot>

AIXM 4.5: two main components

AIXM – Logical Information Model

<AIXM-Update> <AIXM-Update>

<AIXM-Snapshot> <AIXM-Snapshot> <AIXM-Snapshot>

AIXM – Data Exchange Format

AICM 4.5 Web Based Training

AIXM in EAD (today)

Static dataUpdate

(e)AIP Production

Chart Production

Support NOTAM productionDigital Data Input(AIXM 4.5 XML)

AIXM 4.5 / 5.1 XML output

Provided by industry. Similar implementation in local AIS systems

(SDO) Based on AIXM 4.5

AIXM version 5

Ae

ron

au

tica

l

Info

rma

tio

n

Dynamic /

delta

(NOTAM)

Static /

baseline /

AIRAC

(AIP, charts,

etc.)

Dig

ita

l

2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015

EAD

operational

AIXM 3.3

AIXM 4.5

EAD

Release 4

AIXM 5.0 AIXM 5.1

Joint development EUROCONTROL – FAA(with the support of the international AIS community)

AIXM 5 Design Objectives

New capabilities

Extensibility

FlexibleExchange

FlexibleMessages

Static and Dynamic

Expand/Refresh Domain Model

Terminal

Procedures

Obstacles

Aerodrome

Mapping

Metadata Integrity

External Constraints

UML

ISO19100series

GML 3.2

Technical Design DecisionsModularity

AIXM version 5.1

UML

XSD

Temporality Concept

www.aixm.aero

www.aixm.aero

www.aixm.aero/wiki

AIXM Wiki

AIXM Forum

<OK for computers>

<not OK for computers>

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

• 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>

AIXM 5.1 – Digital NOTAM capability

AIXM Temporality document

Implementation Guidance

• GML Guidelines for aviation data

– Encoding rules / conventions

– Profile

• OGC Aviation Domain WG

– See OGC Portal

Implementation Guidance

Use of xlink:href and UUID

1 Scope..........................................................................................4

1.1 Introduction ....................................................................................................................4

1.2 References ......................................................................................................................4

1.3 Assumptions and Dependencies .....................................................................................4

2 Feature identification (UUID).....................................................5

2.1 The gml:identifier property.............................................................................................5

2.2 Use of UUID...................................................................................................................5

2.3 UUID version and codeSpace.........................................................................................6

2.4 The gml:id property ........................................................................................................6

3 Feature Reference (xlink:href) ..................................................8

3.1 Introduction ....................................................................................................................8

3.2 Concrete local references within a message ...................................................................8

3.3 Concrete external references...........................................................................................9

3.4 Abstract references .........................................................................................................9

3.5 Use of xlink:title ...........................................................................................................11

A.1. UUID algorithms .....................................................................13

<aixm:clientAirspace xlink:href="urn:uuid:a82b3fc9-4aa4-4e67-8def-

aaea1ac595j"/>

Implementation Guidance

• Metadata Profile– Requirements for

Aviation Metadata

– Guidance on the Aviation Metadata Profile

• Business Rules

• CRC

• Etc.

Requirement/Source Annex

15

ADQ INSPIRE

IR

OWS-6

5.1.1 Resource Title

5.1.2 Resource Abstract

5.1.3 Resource Language

5.2.1 Topic Category

5.3.1 Geographic Bounding Box

5.3.2 Spatial Reference System

5.4.1 Temporal Extent

5.4.2 Date of Publication

5.4.3 Date of Last Revision

5.4.4 Date of Creation

5.4.5 Temporal Reference System

5.5.1 Lineage

5.5.2 Accuracy of Numerical Data

5.6.1 Conditions Applying to Access

and Use

5.6.2 Limitations on Public Access

5.7.1 Responsible Party

5.7.2 Responsible Party Role

5.8.1 Metadata Point of Contact

5.8.2 Metadata Date

5.8.3 Metadata Language

Global AIM Congress of 2006

• Recommendation 1 – “ICAO adopt the AICM/AIXM as the

standard aeronautical information conceptual model and the standard aeronautical information exchange model, and

• develop appropriate means of compliance, and

• global mechanisms to manage and develop the AICM/AIXM”

ICAO SARPS

AMDT 37 expected to make this a mandatory requirement and provide more details

Draft AMDT 37 to Annex 15

See: http://www2.icao.int/en/ais-aimsg/AISAIM%20Meeting%20MetaData/SN%202%20complete.pdf

Draft AMDT 37 to Annex 15

ICAO SARPS

AMDT 37 expected to make this a mandatory requirement and provide more details

Validation of AIXM 5.1

Syntactic check

- Does the data make sense?- Is it compliant with international standards ?- Do I respect recommended practices?- …

Semantic check

Rules

=

- Check the compliance of an XML dataset with the XSD grammar- Performed by standard XML parsers (e.g. xerxes, MSXML, XMLSpy, etc.)

AIXM 5.1UML

AIXM 5.1XML

Airportfeatures

AIXM 5.1XSD

SBVR specification

• SBVR = (OMG) Semantics of Business Vocabulary and Business Rules

– defines the vocabulary and rules for documenting the semantics of business vocabularies, business facts, and business rules.

• It identifies two types of business rules

– Structural rules

– Operative rules

• AIXM 5 has adopted this terminology and identifies the following business rules:

– AIXM Structural rules: the enumerations of values (datatypes)

– AIXM Operative rules: rules extracted from official documents (ICAO Annexes), minimum data rules, consistency rules, recommended practices, coding rules…

1st AIXM 5.1 Business Rules Report

• Currently, an Excel report– Containing textual rules classified by type etc…

– Providing Schematron code

– Working Draft status

• AIXM Users are able to pick-up the rules they need for their systems

ARC Tool

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

ICAO AIS to AIM Roadmap

3 phases

21 inter-

related stepsTim

e

AIXM 5.1 proposed to ICAO

Pre-AIXM 5

2006 2007 2008 2009 2010 2011 2012

AIXM 5.0

AIXM 5.1 and further UpdatesAIS-AIM SG

International AIXM Change Control Board

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!

Roles

• CCB Member– Any AIXM stakeholder (organisation)

• Raise/comment issues• Develop/review change proposals

• CCB Secretariat - Eurocontrol and FAA– JIRA maintenance– Drives the change proposal process

• but does not take decisions in isolation!– Implements the model changes– Maintains www.aixm.aero and related Web sites

• CCB Advisory Board – Maximum 20 members - Representatives of stakeholder groups– Maintain the “AIXM CCB Charter”– Witness the correctness of the CCB process– Receive regular reports from Secretariat– Not requested to approve individual changes!

Future versions policy• Major Version (v.5, v.6, etc.)

– None foreseen for the moment

• Intermediate Version (v.5.x, v.6.x, etc.)– Every 3-4 years– Include bi-directional mapping rules– AIXM 5.2 not earlier than end 2013

• CCB process to start in Q2 2012

• Minor Version (v.5.1.x, v.5.2.x, etc.) – Probably AIXM 5.1.1 in 2012

• Editorial bugs – corrections• Enable gml:identifier for “objects”