AIXM 5 Concepts

AIXM 5 ConceptsAIXM 5 Concepts

MissionMission

• Based on global aeronautical data requirements– ICAO standards and practices– Industry requirements

• Modular and extensible• Support current and future AIM information

system requirements– Digital AIPs– Automated charting and publications– Integrated digital NOTAMs– Aerodrome Mapping Databases and applications– Situational displays

• Based on global aeronautical data requirements– ICAO standards and practices– Industry requirements

• Modular and extensible• Support current and future AIM information

system requirements– Digital AIPs– Automated charting and publications– Integrated digital NOTAMs– Aerodrome Mapping Databases and applications– Situational displays

Presentation TopicsPresentation Topics

• AIXM Design Principles

• Design Concepts– ISO 19100 standards– Geography Markup Language (GML)– Temporality

• Conceptual Areas











AIXM Design ObjectivesAIXM Design Objectives

Metadata Integrity

Data Quality Mandates

Technical Design Decisions

UML

ISO19100series

GML 3.2


New Data Requirements

TerminalProcedures

Obstacles

Aerodrome Mapping

Metadata Integrity


UML

ISO19100series

GML 3.2

Technical Design Decisions


Future Capabilities

Extensibility

FlexibleExchange

FlexibleMessages

Permanent & Temporary


TerminalProcedures

Obstacles

Aerodrome Mapping

Metadata Integrity


UML

ISO19100series

GML 3.2

Technical Design DecisionsModularity


Future Capabilities

Extensibility

FlexibleExchange

FlexibleMessages

Permanent & Temporary


TerminalProcedures

Obstacles

Aerodrome Mapping

Metadata Integrity


UML

ISO19100series

GML 3.2

Technical Design DecisionsModularity








Technical Design DecisionsIn the ISO19100 series framework

Technical Design DecisionsIn the ISO19100 series framework

• Internationally developed standard for expressing geographical data– Features - Airports, Runways, Airspace– Metadata - Data originator, Status, Published Date– Temporality - Start and end dates– Geometry - Point, Line, Polygon

• Helps us organize information for the aeronautical domain

• Well-established– Geography Markup Language (GML)– Widely adopted and implemented by vendors and governments

• Standards reduce barriers to adoption by vendors and governments

• Internationally developed standard for expressing geographical data– Features - Airports, Runways, Airspace– Metadata - Data originator, Status, Published Date– Temporality - Start and end dates– Geometry - Point, Line, Polygon

• Helps us organize information for the aeronautical domain

• Well-established– Geography Markup Language (GML)– Widely adopted and implemented by vendors and governments

• Standards reduce barriers to adoption by vendors and governments

Aeronautical Features

AIXM Structure and ApplicationBased on ISO 19100


AIXM Conceptual Model (UML)

Geometry

Temporality Metadata

Ext

en

sib

ilityProperties

Data Types

Ap

plic

atio

n

Mo

de

ls

ISO 19126 Feature CatalogISO 19109 Application SchemaISO 19107 SpatialISO 19108 TemporalISO 19115 Metadata

Conceptual ModelFeature Catalog

Feature Data Dictionary

Application Schema



AIXM XML Schema (XML)

GML 3.1 Profile

Features

Ap

plic

atio

n S

che

ma

s

Data Types

ISO 19136 GMLXML Schema

Data encoding layer

Aeronautical Features

AIXM Conceptual Model (UML)

Geometry

Temporality Metadata

Ext

en

sib

ilityProperties

Data Types

Ap

plic

atio

n

Mo

de

ls

AIXM Structure and ApplicationAIXM Structure and Application

• AIXM provides the standard foundation for describing aeronautical information– Features: Runway, En route Route, Airspace– Properties: Valid time, Location– Data Types: code list of airspace types– Metadata: Data originator

• AIXM can be used to build compliant application schemas– Enable real-world implementation– Digital NOTAMs– Procedure Design– Automated Charting

• Enables maximum flexibility while remaining ISO compliant– Examples this afternoon and tomorrow

• AIXM provides the standard foundation for describing aeronautical information– Features: Runway, En route Route, Airspace– Properties: Valid time, Location– Data Types: code list of airspace types– Metadata: Data originator

• AIXM can be used to build compliant application schemas– Enable real-world implementation– Digital NOTAMs– Procedure Design– Automated Charting

• Enables maximum flexibility while remaining ISO compliant– Examples this afternoon and tomorrow

What is GML?What is GML?

• ISO exchange format for geographical features encoding– Based on XML Schema– Open GIS Consortium

• Good industry adoption by Geographic InformationSystem (GIS) vendors– Commercial Off the Shelf Software

• ISO exchange format for geographical features encoding– Based on XML Schema– Open GIS Consortium

• Good industry adoption by Geographic InformationSystem (GIS) vendors– Commercial Off the Shelf Software

<gml:Point> <gml:pos>46.90278 0.08111</gml:pos></gml:Point>

Temporality ModelTemporality Model

• Definition– A model that incorporates the concept of time

• Key assertions– All features are temporal with start of life and end of

life• Example, A new air traffic control sector

– All features change over time• Example, A VOR is out of service for a day

• AIXM Temporality Model – Relates features to the time extent in which they are

valid– Provides various means to describe the time extent

• Definition– A model that incorporates the concept of time

• Key assertions– All features are temporal with start of life and end of

life• Example, A new air traffic control sector

– All features change over time• Example, A VOR is out of service for a day

• AIXM Temporality Model – Relates features to the time extent in which they are

valid– Provides various means to describe the time extent

Versions and DeltaVersions and Delta

• Version – The state of a feature and value of its properties over a time period between two changes.

• Delta – Difference between two consecutive versions.

• Version – The state of a feature and value of its properties over a time period between two changes.

• Delta – Difference between two consecutive versions.

Temporality Model (continued) Temporality Model (continued)

• Operational changes are modeled as deltas

• Deltas can be permanent or temporary:– Permanent delta: A set of properties that have changed or will change

permanently. The permanent delta will result in a new baseline.

– Baseline: The state of a feature and all of the feature properties as a result of a permanent delta. The Baseline state of a feature also exists when the feature is initially created. The Baseline state lasts until the next permanent delta.

– Temporary delta: A set of values for one or more feature properties that are effective for a limited time. The result is a temporary change to an underlying feature version.

– Version: The state of a feature and all the feature properties during the time period between two changes.

• Operational changes are modeled as deltas

• Deltas can be permanent or temporary:– Permanent delta: A set of properties that have changed or will change

permanently. The permanent delta will result in a new baseline.

– Baseline: The state of a feature and all of the feature properties as a result of a permanent delta. The Baseline state of a feature also exists when the feature is initially created. The Baseline state lasts until the next permanent delta.

– Temporary delta: A set of values for one or more feature properties that are effective for a limited time. The result is a temporary change to an underlying feature version.

– Version: The state of a feature and all the feature properties during the time period between two changes.

This is a conceptual temporal model that can be implemented in many ways

TemporalityConceptual Model


Imagine that AML Navaid undergoes an upgrade that changes its frequency from 125 MHz to 132.5 MHz…

1. Schedule permanent change to coincide with update cycle

2. Shutdown AML before the upgrade3. Perform the upgrade4. Start AML in test mode to evaluate

change

AIP: NAVAID = AMLStatus = Operational, Freq = 126.00MHz


Status = Offline for upgrades

Status = OnTestfor upgrades

Version 1 Version 2 Version 3 Version 4

Frequency upgrade

coordinated to be

effective next cycle

Baseline 1 Baseline 2

TemporaryDelta 1

TemporaryDelta 2

Permanent Delta 1



Status = Offline for upgrades

Status = OnTestfor upgrades

Version 1 Version 2 Version 3 Version 4

Frequency upgrade

coordinated to be

effective next cycle

Baseline 1 Baseline 2

TemporaryDelta 1

TemporaryDelta 2

Permanent Delta 1



Imagine that AML Navaid undergoes an upgrade that changes its frequency from 125 MHz to 132.5 MHz…








AIXM CoverageAIXM Coverage

• Aerodrome/Heliport• Aerodrome/Heliport Facilities• Airspace• Holding• Navaids and Points• Obstacles• Organizations• Procedures• Routes• Services

• Aerodrome/Heliport• Aerodrome/Heliport Facilities• Airspace• Holding• Navaids and Points• Obstacles• Organizations• Procedures• Routes• Services

Shared Components• Geometry• Notes• Time Management• Aircraft

Shared Components• Geometry• Notes• Time Management• Aircraft

Aerodrome and HeliportsAerodrome and Heliports

• Aerodromes• Heliports• Movement Areas• Distances, Services, Lights

• Aerodromes• Heliports• Movement Areas• Distances, Services, Lights


• Data necessary to support aerodrome mapping applications (RTCA DO-272A, EUROCAE ED-99A)

• Data necessary to support aerodrome mapping applications (RTCA DO-272A, EUROCAE ED-99A)

• Movement area geometries

• Intersections• Markings


• Usage and Restrictions– Who can use

the aerodrome– When they can

use it

• Usage and Restrictions– Who can use

the aerodrome– When they can

use it

AerodromeOperation<<object>>AircraftCharacteristics

(from Shared)

<<object>>

FlightCharacteristics(from Shared)

<<object>>

AerodromeHeliportUsageCondition<<object>>

0..1

0..*

0..1

0..*

basedOnAircraft

0..1

0..*

0..1

0..*

basedOnFlight0..10..1

basedOnOperation

Timetable(from Time Managem...

<<object>>

AerodromeHeliportUsageLimitation<<object>>

0..*0..*madeOf

0..10..1

hasApplicableTimes

AerodromeHeliportUsage<<feature>>

1..*1..* madeOf

MovementAreaElements<<object>>

11affects

Aerodrome and Heliport FacilitiesAerodrome and Heliport Facilities

• Fuel• Oil• Oxygen• Passenger Facility

• Fuel• Oil• Oxygen• Passenger Facility

• Ground Services– Repair– Fire fighting– Other…

• Ground Services– Repair– Fire fighting– Other…

AirspaceAirspace

• Represents – ICAO Regions– Areas– Zones– Sectors

• Airspaces used in/by– Air traffic services– Special regulated airspace– Client defined airspace– Various ‘limited’ airspace

• Represents – ICAO Regions– Areas– Zones– Sectors

• Airspaces used in/by– Air traffic services– Special regulated airspace– Client defined airspace– Various ‘limited’ airspace

Airspace AltitudesAirspace Altitudes

Derived AirspaceDerived Airspace

Airspaces with same horizontal border

Airspace derived fromaggregation of parts

HoldingHolding

• En route and terminal holding• Planned and Unplanned• Segments by length or time• Integrated with procedure conceptual area

• En route and terminal holding• Planned and Unplanned• Segments by length or time• Integrated with procedure conceptual area

HoldingPatternDistance

+ length : valDist

<<object>>

HoldingPatternLength<<choice>>

11

hasLengthDuration

11

hasLengthDistance

HoldingPattern

+ type : codeTypeHoldProc+ outboundCourse : valAngleBrg+ outboundCourseType : codeTypeCourse+ inboundCourse : valAngleBrg+ turnDirection : codeDirTurn+ upperLimit : valDistVer+ upperLimitReference : codeDistVer+ lowerLimit : valDistVer+ lowerLimitReference : codeDistVer+ speedLimit : valSpeed+ description : txtDescr+ nonStandardHoldingReason : txtDescr

<<feature>>

11

hasSpan

SegmentPoint

+ reportingATC : codeRepAtc+ flyBy : codeYesNo+ waypoint : codeYesNo+ radarGuidance : codeYesNo

(from Navaids Points)

<<object>>

11

hasEndPoint

0..10..1

basedOn

Navaids and PointsNavaids and Points

Significant Points Used for Navigation

Navaids Navigation Service based on Equipment

Designated Points Points not associated with equipment

DME, VOR, TACAN, Azimuth, and so on

Fixes and waypoints

ObstaclesObstacles

• ICAO Annex 4, 14,15 & DOC 8126

• RTCA /EUROCAE DO-276A/ED-98A

• IATA

• ICAO Annex 4, 14,15 & DOC 8126

• RTCA /EUROCAE DO-276A/ED-98A

• IATA

• Lighting• Schedule• Area 1, 2, 3• Point, Line, Polygon

Organizations and UnitsOrganizations and Units

• Organization Authority– “Model organizations and authorities”– ATS organizations (IATA), Aircraft Operators

(United), States (Argentina), Groups of States (NATO Members)

• Unit– “’Unit’ that provides services”– Approach Control, Military, Tower, ARTCC

• Organization Authority– “Model organizations and authorities”– ATS organizations (IATA), Aircraft Operators

(United), States (Argentina), Groups of States (NATO Members)

• Unit– “’Unit’ that provides services”– Approach Control, Military, Tower, ARTCC

Terminal ProceduresTerminal Procedures

• Coverage– PANS-OPS, TERPS– Arinc 424– Conventional and GPS

• Describes– Procedures– Segment Legs– Minima– Circling– Protection Areas– Design Surfaces

• Coverage– PANS-OPS, TERPS– Arinc 424– Conventional and GPS

• Describes– Procedures– Segment Legs– Minima– Circling– Protection Areas– Design Surfaces

RoutesRoutes

• Describe En route structure• Conventional and GPS• Minimum clearance altitudes• Usage restrictions

• Describe En route structure• Conventional and GPS• Minimum clearance altitudes• Usage restrictions

EnRouteRouteRouteSegment

Flight LevelsTrack LengthTrack WidthTrack DirectionFlight Rules and Use

RoutePortion

Standard flight levelsMinimum AltitudesChange over pointsDME usage (RNAV)

ServicesServices

• Airspace• Route• Aerodrome/Heliport• Route• Holding• Procedure• …

• Airspace• Route• Aerodrome/Heliport• Route• Holding• Procedure• …

ServiceUnit

Unit provides service

• Communication• Flight Information• Air Traffic Control• Meteorological• Radar• …

Provided On

Service is

Status and ScheduleWith FAA implementation plans

Status and ScheduleWith FAA implementation plans

2005 2010

2006 2007 2008 2009

Dec 06AIXM 5 RC 1

Jun 07AIXM 5 RC 2

Dec 07AIXM 5

Jun 06AIM Global Congress

Dec 09Possible AIXM 5.x

2007AIXM User Conference

2006AIXM Design Review



Sep 06 - Dec 07Digital NOTAM trials

2008 - 2010AIXM Implementations

Documents

AIXM 5 Concepts