Integrating information towards Digital ATM

Information Structures

- AIXM -

Presented By: Eduard Porosnicu, Eurocontrol

Date: August 27, 2013

AIXM 1.1 (April 1998)

After a number of discussions and consultations, it was decided to formally describe the AIXM by using “syntax and semantics” based on the DML (Data Manipulation Language) part of the internationally standardized Database Language SQL. An important additional reason to base the AIXM on SQL is:

SQL (the most commonly used database language) was standardized in 1986 by both the American National Standards Institute (ANSI) and International Standards Organization (ISO) standard bodies.

It should, however, be stressed that the use of SQL syntax and particularly (imperative) keywords such as INSERT, DELETE, UPDATE, COMMIT, etc. do not imply that AIXM engages in direct database access and (related) transaction management. The meaning of such keywords in the context of the AIXM will be explained in section 6 “AIXM SYNTAX AND SEMANTICS”.

After a number of discussions and consultations, it was decided to formally describe the AIXM by using “syntax and semantics” based on the DML (Data Manipulation Language) part of the internationally standardized Database Language SQL. An important additional reason to base the AIXM on SQL is:

SQL (the most commonly used database language) was standardized in 1986 by both the American National Standards Institute (ANSI) and International Standards Organization (ISO) standard bodies.

It should, however, be stressed that the use of SQL syntax and particularly (imperative) keywords such as INSERT, DELETE, UPDATE, COMMIT, etc. do not imply that AIXM engages in direct database access and (related) transaction management. The meaning of such keywords in the context of the AIXM will be explained in section 6 “AIXM SYNTAX AND SEMANTICS”.

AIXM 1.1 (April 1998)

INSERT INTO HEADER (source, serial_number, date_time) VALUES

( ‘BELGIUM AIS’, ‘AMDT-56’, ‘1998-01-03 10:00’); COMMIT;

INSERT INTO aerodrome/heliport (adhp_m_code_icao, dt_wef, dt_til, txt_name, code_iata, ...) VALUES (‘EBBR’, ‘1998-01-26 00:00’, NIL, ‘Brussels National’, ‘BRU’, ...);

COMMIT;

INSERT INTO aerodrome/heliport (adhp_m_code_icao, dt_wef, dt_til, txt_name, code_iata, ...) VALUES (‘EBBR’, ‘1998-09-28 00:00’, NIL, ‘Brussels National’, ‘BXL’, ...);

UPDATE aerodrome/heliport SET dt_til = ‘1998-09-27 23:59’ WHERE adhp_m_code_icao = ‘EBBR’ AND dt_wef = ‘1998-01-26 00:00’;

COMMIT;

DELETE fuel WHERE adhp_m_code_icao = ‘EBBR’ AND dt_wef = ‘1998-01-26 00:00’

AND code_cat = ‘WRONG GAS’; COMMIT;

INSERT INTO END_SESSION (source, serial_number, date_time) VALUES

( ‘BELGIUM AIS’, ‘AMDT-56’, ‘1998-01-03 10:15’);

COMMIT;

Figure 6.1 Session Example

INSERT INTO HEADER (source, serial_number, date_time) VALUES

( ‘BELGIUM AIS’, ‘AMDT-56’, ‘1998-01-03 10:00’); COMMIT;

INSERT INTO aerodrome/heliport (adhp_m_code_icao, dt_wef, dt_til, txt_name, code_iata, ...) VALUES (‘EBBR’, ‘1998-01-26 00:00’, NIL, ‘Brussels National’, ‘BRU’, ...);

COMMIT;

INSERT INTO aerodrome/heliport (adhp_m_code_icao, dt_wef, dt_til, txt_name, code_iata, ...) VALUES (‘EBBR’, ‘1998-09-28 00:00’, NIL, ‘Brussels National’, ‘BXL’, ...);

UPDATE aerodrome/heliport SET dt_til = ‘1998-09-27 23:59’ WHERE adhp_m_code_icao = ‘EBBR’ AND dt_wef = ‘1998-01-26 00:00’;

COMMIT;

DELETE fuel WHERE adhp_m_code_icao = ‘EBBR’ AND dt_wef = ‘1998-01-26 00:00’

AND code_cat = ‘WRONG GAS’; COMMIT;

INSERT INTO END_SESSION (source, serial_number, date_time) VALUES

( ‘BELGIUM AIS’, ‘AMDT-56’, ‘1998-01-03 10:15’);

COMMIT;

Figure 6.1 Session Example

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><txtName chg="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>

<?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><txtName chg="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>

Content

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

<AIXM-Snapshot><Vor>

<VorUid><codeID>AML</codeID><geoLat>34.3928N</geoLat><geoLon>123.4333W</geoLon>

</VorUid>…

</AIXM-Snapshot>

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

Versions in use - AIXM 4.5

• Published: MAR 2008• UML Model• GML Schema• Full AIP/NOTAM data

– Including obstacle, airport mapping, etc.

• Metadata• Extensibility• Use:

– Partially, by FAA and NGA

Airspace<<feature>>

OrganisationAuthority(f rom Organisation)

<<feature>>

AircraftCharacteristic

type : CodeAircraftTypeengine : CodeAircraftEngineTypenumberEngine : CodeAircraftEngineNumberTypetypeAircraftICAO : CodeAircraftICAOTypeaircraftLandingCategory : CodeAircraftCategoryTypewingSpan : ValDistanceTypewingSpanInterpretation : CodeValueInterpretationTypeclassWingSpan : CodeAircraftWingspanClassTypeweight : ValWeightTypeweightInterpretation : CodeValueInterpretationTypepassengers : NoNumberTypepassengersInterpretation : CodeValueInterpretationTypespeed : ValWeightTypespeedInterpretation : CodeValueInterpretationTypewakeTurbulence : CodeWakeTurbulenceType

(f rom Aircraf t and Flight)

<<object>>

AirspaceUsage<<feature>>

1

0..*

+restrictedAirspace

1

0..*isSpecifiedFor

AirspaceLayerUsage

activity : CodeAirspaceActivityTypestatusActivation : CodeAirspaceActivationTypetrafficAllowed : CodeMilitaryStatusType

<<object>>

0..*

0..*

0..*

+user 0..*

hasUser

0..*

+aircraft

0..*

involvesAircraft

1..*+usage 1..*

isComposedOf

Timetable

workingHours : CodeTimetableType

(f rom Time Management)

<<object>>

LayerAndTime

upperLimit : ValDistanceVerticalTypeupperLimitReference : CodeVerticalReferenceTypelowerLimit : ValDistanceVerticalTypelowerLimitReference : CodeVerticalReferenceTypealtitudeInterpretation : CodeAltitudeUseType

(f rom Lev el and Time Block)

<<object>>

0..* +levels0..*

concerns

0..1 +schedule0..1

isActiveBy

StandardLevelColumn

series : CodeLevelSeriesTypeunitOfMeasurement : UomDistanceVerticalTypeseparation : CodeRVSMType

(f rom Standard Lev els)

<<feature>>

0..*

0..1

0..*

+discreteLevelSeries 0..1

isRestrictedTo

Versions in use - AIXM 5.0

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

Current version – AIXM 5.1

Current version – AIXM 5.1

Tools for AIXM 5.1 data visualisation

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

• AIXM 4.5 Conversion Guidelines– See www.aixm.aero/wiki -> Mappings,

version 1.1– Status: Released– Including feedback from EAD mapping

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

1.1 AM_RUNWAYELEMENT ED-99A Definition: Part of a runway.

AIXM 5.1 Definition: Runway element may consist of one ore more polygons not defined as other portions of the runway class.

ED-99A AIXM 5.1

AM_RunwayElement RunwayElement[type=‘NORMAL’]

idarpt associatedRunway.Runway.associatedAirportHeliport.AirportHeliport.locatio

nIndicatorICAO

idrwy associatedRunway.Runway.designator

pcn surfaceProperties.SurfaceCharacteristics.classPCN

width width

Note: there is also nominalWidth on Runway

length length

Note: there is also nominalLength on Runway

surftype surfaceProperties.SurfaceCharacteristics.composition

AND

surfaceProperties.SurfaceCharacteristics.preparation

geopoly extent.ElevatedSurface

feattype Note: Can be implied

vacc extent.ElevatedSurface.verticalAccuracy

vres extent.ElevatedSurface.verticalResolution

hacc extent.ElevatedSurface.horizontalAccuracy

hres extent.ElevatedSurface.horizontalResolution

integr integrity

source source

OR

gmd:MD_Metadata.gmd:dataQualityInfo.gmd:lineage.gmd:LI_Lineage.gmd:

processStep.gmd:LI_ProcessStep

Note: Needs processor with a role set to “originator”.

revdate revisionDate

AIXM 5.1 Mappings - updates

Coding/usage guidelines

• XHTML profile/guidelines for AIXM ?

Digital NOTAM

• Event Specification – version 2.0 in preparation

•Other Event (any other situation that does not have a dedicated scenario)

•Taxiway lights unserviceable•Surface contamination (SNOWTAM)

•Visual Approach slope indicator unserviceable•Taxiway closure

•Obstacle lights unserviceable•New obstacle

•Runway lights unserviceable•Navaid unserviceable

•Approach lights downgraded•Runway closure

•Approach lights unserviceable•Aerodrome closure

•Taxiway usage limitation•Route portion opening

•Runway usage limitation•Route portion closure

•Airport Usage limitation•Ad-hoc ATS airspace – creation

•Runway portion closure•Ad-hoc special activity area – creation

•Declared distances changes•Published ATS airspace - activation or deactivation

•Displaced threshold•Published special activity area – activation

•Increment 2 scenarios•Increment 1 scenarios

FAA Digital NOTAM Beta Testing

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

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

Industry developments

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

Future versions

Future versions

• ATIEC 2012Future versions

• Proposed– Minor Release AIXM 5.1.1 by end 2012

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

Future versions

• Proposed– Regular update AIXM 5.2 by end 2013

• 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

Too early….

Now planned : Q1 2014 Intended : 2015

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

WXXM Coordination

• AvXML 1.0 RC-2– Simple Aeronautical

Feature (SAF) model

class Context Diagram: Aerodrome

«FeatureType»Aerodrome

{root,leaf}

+ designator :CodeAirportHeliportDesignatorType [0..1]+ name :TextNameType [0..1]+ locationIndicatorICAO :CodeICAOType [0..1]+ designatorIATA :CodeIATAType [0..1]+ fieldElevation :Distance [0..1]

GM_Primitive

«type»Geometric primitiv e::

GM_Point

«FeatureType»Runway

{root,leaf}

+ designator :TextDesignatorType [0..1]

«FeatureType»RunwayDirection

{root,leaf}

+ designator :TextDesignatorType [0..1]+ trueBearing :Angle [0..1]+ elevationTDZ :Distance [0..1]

0..*

isSituatedAt

+associatedAirportHeliport 0..10..*

hasReferencePoint

+ARP 0..1

0..*

uses

+usedRunway 0..1

FIXM coordination• AIXM provides the

“infrastructure” part

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

Questions

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