Digital AIM Training - AIXM

Name: Digital AIM Training - AIXM
Uploaded: 2017-08-24T10:43:38+00:00
Duration: PTM31S15
Channel: Iris Titterington
Description: Digital AIM Training - AIXM

Digital AIM Training - AIXM
Notes: EUROCONTROL Copyright 2011

AIXM Logical Model - UML
Digital AIM Training - AIXM AIXM Logical Model - UML UML Class Diagrams Classes (simple inheritance only) Attributes, data types, lists of values Associations Until 5.1 – IBM Rational Rose Data Modeller In progress - migration to Sparx EA (8.1) Important note: UML model is ‘static’ (Temporality Concept applied directly in the XML Schema generation process) In order to keep the diagrams relatively de-cluttered EUROCONTROL Copyright 2011

Stereotypes: feature vs. object
Digital AIM Training - AIXM Stereotypes: feature vs. object <<feature>> <<object>> <<object>> another <<feature>> EUROCONTROL Copyright 2011

AICM 5.1 - Packages AICM 5.1 - Packages 245 classes
around attributes + associations

AirportHeliport feature
Digital AIM Training - AIXM AirportHeliport feature This diagrams shows the main properties of the AerodromeHeliport feature. Notes: OPERATE EUROCONTROL Copyright 2011

Fully collocated with EBBR
Airport collocation Fully collocated with EBBR EBMB EBBR

Runway 02/20 02 20 This diagram shows how runways and their properties are modelled, both for airplanes and helicopters. Runways are mandatory associated with an AerodromeHeliport and have a property that allows distinguishing between normal runways, used by airplanes and "runway like" surfaces used by helicopters for final approach and take-off (FATO). The properties of a runway include surface characteristics, marking, lenght, width, etc. It is also possible to describe runway elements and the painted centreline, as required by the AMDB concept. Notes: THR EUROCONTROL Copyright 2011

Airport mapping data Construction Area Stand Guidance Line Note also that the AIXM model also covers the requirements for encoding airport mapping data. This is an industry standard which provides requirements for data used to create and display an airport map on an Electronic Flight Bag device (EFB). On this diagram, you can see an extract from the AMDB standard, which highlights the most important elements of an AMDB data set: Runway geometries Taxiway geometries Apron geometries De-icing areas Etc. The standard was developed by EUROCAE WG44 / RTCA SC217 and it is named « User requirements for aerodrome mapping information (ED99A/DO272A) » The data actually upload in compliant EFB devices is encoded in the ARINC Embedded Aerodrome Database format specified by the ARINC 816 standard. Although the production of an AMDB is not (yet) required by ICAO, the airport maps included in AIP actually contain 70%-80% of the AMDB data. AMDB are nice to have for Digital NOTAM applications, as they support graphical visualisation and graphical data input of Digital NOTAM, such as closed portion of a taxiway. Notes: EUROCONTROL Copyright 2011

Airport usage restrictions
Digital AIM Training - AIXM Airport usage restrictions NORMAL, LIMITED, CLOSED … PERMIT, FORBID, COND… This diagram shows how airport/heliport availability information is modelled, as a complex property of the feature. The availability includes an operational status attribute and associated usage restrictions. The AirportHeliportUsage class is derived from the generic UsageCondition class, which models permissions/restrictions based on type of flight, type of aircraft and/or MET conditions. Notes: LANDING, TAKEOFF, ALTN_LANDING… EUROCONTROL Copyright 2011

Airport Usage Restrictions
AND, OR… engine type, wing span, etc. IFR/VFR, status, scheduled, etc.

Airport services This diagram shows the model for services that provide maintenance of the airport infrastructure and direct support to aircraft on the ground. The model allows several services of the same type to be described. However, business rules might further restrict that: - usually, there should be just one airport clearance service; - several fire fighting services should exist only if they have non-overlapping Timetables; - aircraft and passenger services should be grouped by service provider (the associated Unit). Notes: EUROCONTROL Copyright 2011

“Shared” packages

Geometries

Notes AirportHeliport, etc. Point, Address, etc. cityServed
DESCRIPTION language …

Shared packages

Address, phone, link…

Schedules UTC, UTC+1 … 01/04… 30/09… FRI HOL … MON 17:00 SR, SS SR+30…
06:00 NO Yes…

<<object>>
Airspace layers <<object>> AIP Text "...Limit" Value "...LimitReference" "SFC" GND "UNL" UNL "XXXX FT AGL" XXXXX FT SFC "XXXX FT AMSL" MSL "XXXX M AGL" M "XXXX M AMSL" "FL XXX" XXX FL STD "SM XXX" SM "ITS LOWER LIMIT" FLOOR OTHER - empty - "ITS UPPER LIMIT" CEILING

Standard Levels IFR, IFR-RVSM, VFR … ODD, EVEN … FL, SM …
RVSM, NON-RVSM …

Airspace

Airspace P EBP01 BRUSSELS CITY Use of GML for aviation data

Airspace defined by aggregation
BRUSSELS TMA BASE UNION 1 2

Airspace aggregation By reference - between synchronized databases For example, let's consider a TMA defined as a circle from which the airspace occupied by an neighbouring FIR is subtracted. To model this, two AirspaceVolumes are necessary: - one AirspaceVolume having as horizontalProjection a Surface of type "full circle" and specified vertical limits; - a second AirspaceVolume, which has as contributorAirspace the related FIR. For this second AirspaceVolume, two possibilities exist. The first one is presented on this diagram. The first method is limited to referring to another airspace, but without effectively copying the geometry of that Airspace as own AirspaceVolume(s). This method might be appropriate for data provision between synchronized databases, such as between a local and a regional database and it is equivalent to the approach of the previous AIXM 4.5 version (which is not based on GML). The disadvantage of this method is that the client needs to eventually retrieve the geometry of the referenced Airspace and do the geospatial calculations that are necessary in order to effectively get the actual geometry of the current Airspace in a GML usable form. The advantage is that it preserves a true association with the composing Airspace. Notes: EUROCONTROL Copyright 2011

Airspace aggregation By copying the geometry - geometrical data for direct consumption Combined – also possible The second method consists in effectively copying the geometry of the referenced Airspace as local AirspaceVolume. Note that this might be a recursive operation, as the referenced Airspace might have more than one AirspaceVolume and some or even all these could also depend on the geometry of other Airspace. This method might be appropriate for applications that need to provide fully digested geometrical data for direct consumption (e.g. graphical visualization, spatial calculations). The disadvantage of this method is that the referenced geometry might also change in time. This is not a problem when the aggregation is used for the provision of SNAPSHOT data (valid at a time instant) but it might become problematic when providing Baseline data (which is valid for a period of time). Future changes of the geometry of referenced airspace needs to be propagated to the AirspaceVolume of the aggregated airspace. The advantage is that this method provides complete geometrical data for the aggregated Airspace and does not require further calculations by the client system. The two methods can also be combined. Notes: EUROCONTROL Copyright 2011

Geoborder and significant point references
Digital AIM Training - AIXM Geoborder and significant point references Use of GML for aviation data Airspace boundaries may be based on national borders or on other geographical features, such as shorelines, rivers, etc. A particularity of this situation is that official definitions of the airspace, as provided in the Aeronautical Information Publication (AIP) or in NOTAM messages, do not include the actual geometry of the referenced geographical border. It is left for the end users to derive the actual geometry of the airspace by using a source of geographical border data. The UML model of AIXM shows a “dependency” association between Surface and GeoBorder in order to cater for such situations. The encoding is possible in two ways: either with a simple annotation (and copy of all necessary points) or by reference. See the AIXM GML Guidelines for details. Notes: EUROCONTROL Copyright 2011

Airspace activation <<object>> This diagram shows how the airspace activation status is modelled as a complex property of the Airspace feature. It includes properties that model the type of activity and associations with vertical layers, etc. The AirspaceActivation is declared as a derivation of PropertiesWithSchedule, which enables modelling airspace activations that occur according to a repetitive schedule. Notes: AVLB_FOR_ACTIVATION, ACTIVE, … CEILING, 1000 FT, … FLOOR, 300 FT, … EUROCONTROL Copyright 2011

Airspace classification
Digital AIM Training - AIXM Airspace classification C D This diagram shows how multiple airspace class layers are modelled for an airspace. It uses the general "LevelAndTimeBlock" class, which associates the levels concerned with an eventual timetable. Note that it is no longer necessary to create CLASS airspace for each layer that has a different classification. Notes: EUROCONTROL Copyright 2011

Other Airspace aspects
ENTRY, EXIT, ENTRY_EXIT OWN, DLGT, …

ATC and other Services Modified (as compared with AIXM 4.5): Service specialisation (Airport ground services, Etc.) New: Service availability This diagram shows the main elements of the Service model. The abstract Service class describes elements that are common to the various service types. This class is then specialised into specific service catagories, such as information provision, search and rescue, ATC, etc. A service is provided by a Unit of an OrganisationAuthority. Notes: EUROCONTROL Copyright 2011

Point and Navaid Package
Digital AIM Training - AIXM Point and Navaid Package EUROCONTROL Copyright 2011

Navaids VOR/DME FLO FLORA 00:00-24:00 Changes as compared with version 4.5: New: Navaid service and operational status Modified: Navaid equipment This diagram shows the separation between navaid equipment (the physical antenna) and the navaid service. For example, a VOR/DME is a navaid service, using two physical equipments. NavaidComponent is used to describe the relationship of each equipment to the navaid service; equipment located together (collocatedGroup), etc. Notes: VOR (DVOR) DME OPERATIONAL EUROCONTROL Copyright 2011

Routes U M 170 ATS IFR INT 1 2 3 Modified (as compared with AIXM 4.5): Route designator decomposition Segment Points Point references This diagram shows the most important components of the Route concept: - the route header, modelled by the EnRouteRoute feature - the route segments that are part of each route - route portions that are used for specifying flight restrictions. Notes: 4 EUROCONTROL Copyright 2011

Route Segment 660 (FL) STD 195 (FL) STD 247 067 8.1 (NM) 5 COMPULSORY This diagram shows how route segments are modelled. The role of the Segment model group is to group together those properties that are derived from the positions of the start and end point, such as lenght, width, tracks. The SegmentPoint enables associating one or more PointLocations (angle and distances from various navaids) with the SignificantPoints that are used as star/end of the route segment. The EnRouteSegmentPoint class is a specialisation of the SegmentPoint, which has attributes that are specific for the en-route environment. Notes: YES <<choice>> DINKI LNO EUROCONTROL Copyright 2011

Route availability What about CDR routes? <<object>> FORWARD OPEN This diagram shows the main elements that may be used to specify the usage related to a route portion: - the direction of interest is specified using either the direction or the compassDirection attributes of the RoutePortionUsage feature - the usage type is specified by the routeAvailability object, which may also include levels and schedules. RouteAvailability models restrictions that are from point to point and which depend on time and eventually aircraft characteristics (such as navaid equipment, propulsion type, etc. Flight Restrictions (also named "traffic flow restrictions") should be used for those restrictions that depend on flight origin/destination and eventually on type (civil, military, scheduled, etc.). Concerning the CDR status of a route, this is supported through the “COND” value of the status attribute. The exact CDR level is modelled through an extension to the core AIXM model. Notes: 660 (FL) STD 195 (FL) STD EUROCONTROL Copyright 2011

AIXM 5.1 and extensions Additional information exchanged between selected partners Core AIXM Aeronautical information that is relevant for the whole ATM community (AIP, NOTAM, CRAM, etc.) extension Extensions enable the provision of data that is of local/regional interest or specific to a particular user community. This is also used in order to prevent introducing into the core model concepts (such as FUA/CDR) that are specific to Europe only. Remember that the objective for AIXM 5.1 is to have it adopted by ICAO. Notes: EUROCONTROL Copyright 2011

eASM extension of AIXM 5.1 The eASM extension adds the CDR 1/2/3 type of a route, which otherwise is just “conditional” in the core model. A similar extension approach adds to Airspace the AMC Manageable status, which is also part of the FUA Concept. The R-AMC and D-AMC airspace types do no longer exist in AIXM 5.1. For the proper encoding of the European route and airspace data, a system such as the EAD will have to also implement the relevant part of the eASM extension. Notes: CDR1, CDR2, … EUROCONTROL Copyright 2011

Flight Restrictions Package (eRAD)
Digital AIM Training - AIXM Flight Restrictions Package (eRAD) EUROCONTROL Copyright 2011

Flight (routing) restrictions

Overview

Conditions

Routings

Procedures (SID/STAR/IAP)
Digital AIM Training - AIXM Procedures (SID/STAR/IAP) EUROCONTROL Copyright 2011

Procedure = SID, STAR or Approach

AIXM 5.1 Procedure Model - Overview
The terminal area procedures and related concepts (MSA, TAA...) Navaids Points Guidance Service, Point Reference, and Segment Points Holding Holding Patterns Service For Information services (ATIS) and ATC services Shared.Surface Assesment

AIXM 5.1 Procedure Model - Overview
Designator SID & STAR: designator (+ name?) Approach: name + 6 first attributes of class InstrumentApproachProcedure approachPrefix = Blank approachType = VOR multipleIdentification = X copterTrack = Blank circlingIdentification = Blank courseReversalInstruction = Blank

Procedure design vs Procedure encoding
The AIXM model defines the class SegmentLeg which represents an elementary portion of a Procedure A SegmentLeg is associated to a Procedure. A procedure is designed by attaching several SegmentLeg to the procedure A Procedure can be divided into a series of Procedure Transitions More optimised for Procedure Encoding Procedure Design Procedure Encoding

Procedure Transition & SegmentLeg
Approach Transition GEBTI Approach Transition VFA Final Approach Missed Approach SegmentLeg HoldingPattern

SegmentLeg SegmentLeg contains a set of attributes inspired from the Arinc424 specification Note: It is not mandatory to use Arinc424 concepts => legPath SegmentLeg is an abstract class which is specialised: - 1st specialisation per type of procedure - 2nd specialisation per type of transition for approach procedures For a SID For a STAR For an Approach For a missed approach For an approach transition For a final approach

Path Terminators 14 RNAV Types
Digital AIM Training - AIXM Path Terminators 14 RNAV Types Course to an Altitude - CA Course to a Fix CF Direct to a Fix DF Fix to an Altitude FA Fix to a Manual Termination - FM Racetrack Course Reversal (Alt Term) - HA Racetrack (Single Circuit - Fix Term) - HF Racetrack (Manual Termination) - HM Initial Fix IF Track to a Fix TF Constant Radius Arc RF Heading to an Altitude - VA Heading to an Intercept - VI Heading to a Manual Termination - VM EUROCONTROL Copyright 2011

AircraftCharacteristics
Approach Conditions finalApproachPath = STRAIGHT_IN ApproachCondition aircraftLandingCategory = C AircraftCharacteristics altitude = 218 ft altitudeCode = OCA altitudeReference = MSL height = 200 ft heightCode = OCH heightReference = HAT Minima

Organisation Authority / Unit / Service
Digital AIM Training - AIXM Organisation Authority / Unit / Service EUROCONTROL Copyright 2011

Organisation/Authority
States ANSP Civil Aviation Authority Ministry of Transportation Airport Authority Military Authority Airline Eurocontrol Etc. OWNED_BY, MEMBER, …

Unit ATC Centre TWR NOTAM Office Etc.

Service

AIXM list of features and properties
Digital AIM Training - AIXM AIXM list of features and properties For those who are interested, the complete list of all AIXM features and properties is provided in the form of an Excel file. This may be used, for example, in the planning phase in order to decide which parts of the AIXM model are necessary for a particular application. It is unlikely to find an application that really requires to implement the full AIXM. For example, an AIS office will probably not need the AIXM part that deals with aerial refuelling procedures, which is more of interest for military aeronautical information databases. Notes: EUROCONTROL Copyright 2011

Digital AIM Training - AIXM

Similar presentations

Presentation on theme: "Digital AIM Training - AIXM"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Digital AIM Training - AIXM

Similar presentations

Presentation on theme: "Digital AIM Training - AIXM"— Presentation transcript:

Similar presentations

About project

Feedback