AIXM 5 Conceptsaixm.aero/sites/aixm.aero/files/imce/library/2007... · ISO 19100 standards used in...
Transcript of AIXM 5 Conceptsaixm.aero/sites/aixm.aero/files/imce/library/2007... · ISO 19100 standards used in...
AIXM 5 ConceptsAIXM 5 Concepts
Presentation TopicsPresentation Topics
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
Presentation TopicsPresentation Topics
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
RequirementsRequirements
• Based on global aeronautical data requirements– ICAO standards and practices– RTCA/EUROCAE Airport Mapping Databases– PANS-Ops and TERPS Terminal Procedures– Airport Layout Plans (AirMAT)– NATO and Military requirements
• Support for current and future AIM Information System Requirements– Aeronautical Information Publication (AIP)– Integrated Digital NOTAMs– Aerodrome Mapping Databases and Applications– Charts– Procedure Design– Situational displays– Industry requirements
• Based on global aeronautical data requirements– ICAO standards and practices– RTCA/EUROCAE Airport Mapping Databases– PANS-Ops and TERPS Terminal Procedures– Airport Layout Plans (AirMAT)– NATO and Military requirements
• Support for current and future AIM Information System Requirements– Aeronautical Information Publication (AIP)– Integrated Digital NOTAMs– Aerodrome Mapping Databases and Applications– Charts– Procedure Design– Situational displays– Industry requirements
Presentation TopicsPresentation Topics
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
AIXM Design ObjectivesAIXM Design Objectives
Metadata Integrity
Data Quality Mandates
Technical Design Decisions
UML
ISO19100series
GML 3.2
AIXM Design ObjectivesAIXM Design Objectives
New Data Requirements
TerminalProcedures
Obstacles
Aerodrome Mapping
Metadata Integrity
Data Quality Mandates
UML
ISO19100series
GML 3.2
Technical Design Decisions
Information in NOTAM
Military
AIXM Design ObjectivesAIXM Design Objectives
Future Capabilities
Extensibility
FlexibleExchange
FlexibleMessages
Permanent & Temporary
New Data Requirements
TerminalProcedures
Obstacles
Aerodrome Mapping
Metadata Integrity
Data Quality Mandates
UML
ISO19100series
GML 3.2
Technical Design DecisionsModularity
Information in NOTAM
Military
AIXM Design ObjectivesAIXM Design Objectives
Future Capabilities
Extensibility
FlexibleExchange
FlexibleMessages
Permanent & Temporary
New Data Requirements
TerminalProcedures
Obstacles
Aerodrome Mapping
Metadata Integrity
Data Quality Mandates
UML
ISO19100series
GML 3.2
Technical Design DecisionsModularity
Information in NOTAM
Military
Presentation TopicsPresentation Topics
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
Unified Modeling Language (UML)Unified Modeling Language (UML)
VOR- frequency
DME- channel
+colocated
+colocated
En Route Route
Route Segment+defines
+hasNavigation Aid
- codeID- location- elevation- name
+startingAt
+endingAt
• Visual language for capturing relationships, behavior and high-level ideas
• Originally intended for Software Engineering• Today also used for
– Business process modeling– Data modeling– Requirements modeling– Others…
NavaidComponent+ collocationGroup : NoSequenceType+ markerPos ition : CodePos itionInILSType+ providesNavigableLocation : CodeYesNoType
<<object>>
0..*
0..*
NavaidEquipment+ des ignator : CodeNavaidDesignatorType+ nam e : TextNameType+ emissionClas s : CodeRadioEmissionType+ mobile : CodeYesNoType+ magneticVariation : Va lMagneticVariationType+ dateMagneticVaria tion : DateYearType+ operationalSta tus : CodeStatusNavaidType+ fligh tChecked : CodeYes NoType
<<feature>>
isComposedOf0..10..1
ElevatedPoint(f rom Geom etry )
<<object>>
hasNavigab leLocation
Navaid+ type : CodeNavaidServiceType+ designator : CodeNavaidDesignatorType+ landingCategory : CodeLandingAidCategoryType+ operationalStatus : CodeStatusNavaidType+ flightChecked : CodeYesNoType
<<feature>>
0..*
0..*
Association Class(Object containing properties of the relationship)
Unified Modeling Language (UML)Unified Modeling Language (UML)StereotypeFeature class
(Abstraction of real world phenomenon that can exist on its own)
Relationship(NavaidhasNavigableLocation0 or 1 ElevatedPoint)
Object class (Does not exist on its own)
Unified Modeling Language (UML)Unified Modeling Language (UML)
Choice class(Indicates exclusivity property can be one of many values)(Navaid isInstalledAt either RunwayDirection or TouchDownLiftOff)
Navaid+ type : CodeNavaidServiceType+ designator : CodeNavaidDesignatorType+ landingCategory : CodeLandingAidCategoryType+ operationalStatus : CodeStatusNavaidType+ flightChecked : CodeYesNoType
<<feature>>
0..10..*0..*
isInstalledAt
0..1LandingAreaChoice
<<choice>>
0..10..1
RunwayDirection(f rom R unway )
<<feature>>TouchDownLiftOff
(f rom Helicopter Surf ac...)
<<feature>>
0..10..1
Unified Modeling Language (UML)Unified Modeling Language (UML)
Elevation+ a ng le Nom in al : ValAng leType+ a ng le Minimum : ValAngle Type+ a ng le Spa n : ValAn gl eT yp e
<<feature>>Gli de path
+ frequency : ValFrequencyType+ slope : ValAngleType+ rdh : ValDistanceVerticalType
<<feature>>
Localizer+ frequency : ValFrequencyType+ magneticBearing : ValBearingType+ trueBearing : ValBearingType+ widthCourse : ValAngleType+ backCourseUsable : CodeILSBackCourseType
<<fea tu re >>
NavaidEquipment+ designator : CodeNavaidDesignatorType+ name : TextNameType+ emissionClass : CodeRadioEmissionType+ mobile : CodeYesNoType+ magneticVariation : ValMagneticVariationType+ dateMagneticVariation : DateYearType+ operationalStatus : CodeStatusNavaidType+ fl ightChecked : CodeYesNoType
<<feature>>
Inheritance(Localizer inherits properties of the NavaidEquipment)
Abstract class (Cannot be instantiated in an instance document)
ISO19100 series frameworkISO19100 series framework
• Internationally developed standards 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– Feature data dictionaries, feature catalogs, registries and
application schemas• Well-established
– Geography Markup Language (GML)– Widely adopted and implemented by vendors and governments
• Internationally developed standards 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– Feature data dictionaries, feature catalogs, registries and
application schemas• Well-established
– Geography Markup Language (GML)– Widely adopted and implemented by vendors and governments
ISO 19100 standards used in AIXMISO 19100 standards used in AIXM
AIXM Conceptual Model (UML)
Geometry ISO 19107
Temporality ISO 19108
Metadata ISO 19115
Documentation
Feature Catalog ISO 19126
AIXM Exchange Model (XML)
GML ISO 19136
Metadata ISO 19139
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>
GML structures the AIXM Exchange Model GML structures the AIXM Exchange Model
• Object-Property Model– Objects have properties– Properties are simple values or other objects
• Geometry– Points, Lines, Polygons
• Temporality– Timeslices describing feature state over a time period
• Metadata– Based on ISO 19139
• Object-Property Model– Objects have properties– Properties are simple values or other objects
• Geometry– Points, Lines, Polygons
• Temporality– Timeslices describing feature state over a time period
• Metadata– Based on ISO 19139
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
AIXM TimeSlice ModelAIXM TimeSlice Model
TimeSlice created every time one or more feature properties change
TimeSlice – Version and DeltaTimeSlice – Version 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.
An Example: Navaid frequency changeAn Example: Navaid frequency change
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
An Example: Navaid frequency changeAn Example: Navaid frequency change
Imagine that AML Navaid undergoes an upgrade that changes its frequency from 125 MHz to 132.5 MHz…
Status = Operational, Freq = 112.0 MHz Status = Operational, Freq = 113.2 MHz
NOTAMStatus = Offline
for upgradesNOTAM
Status = on test,do not use
Snapshot 1
Frequency upgrade coordinated to be effective next cycle
TempDelta 1TempDelta 2
Permanent Delta 2
Freq = 113.2 MHz
Baseline 1Baseline 2
Permanent Delta 1
Snapshot 2 Snapshot 3 Snapshot 4
Basic Structure of AIXMBasic Structure of AIXM
Extension<<object>>
MessageMetadata(from AIXMMessageMetadata)
<<object>>
AIXMMessage+ sequenceNumber : NoSequenceType
<<object>>
0..1 +messageMetadata0..1Feature Properties
Attributes and associations are specifically modelled for each AIXM feature and are encoded as part of the Feature Time Slice.
FeatureMetadata(from FeatureMetadata)
<<object>>
FeatureTimeSliceMetadata(from Fea tureTimeslice Me ta data)
<<object>>
AIXMFeature+ identifier : CodeUUIDType
<<feature>>
0..1
+featureMetaData
0..1
AIXMTimeSlice+ validTime : TimePrimitive+ interpretation : TimeSliceInterpretationType+ sequenceNumber : NoNumberType+ correctionNumber : NoNumberType
<<object>>
0..1 +timeSliceMetadata0..1
1..*+timeSlice
1..*
AIXMFeaturePropertyGroup<<object>>
1
+propertyGroup
1
0..* +extension0..*
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
Presentation TopicsPresentation Topics
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
• Requirements• AIXM Design Components• Design Concepts
– UML– ISO 19100 standards– Geography Markup Language (GML)– Temporality
• Conceptual Model Packages
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
Aerodrome and HeliportsAerodrome and Heliports
• 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
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 : code TypeHoldProc+ outbo undCourse : valAngleBrg+ outbo undCourseType : cod eTypeCourse+ inbou ndCourse : valAngleBrg+ turnDirection : codeDirTurn+ upperLimit : val DistVer+ upperLimitReference : codeDistVer+ lowerLimit : valDistVe r+ lowerLimitReference : codeDistVer+ speedLimit : valSpeed+ descri ption : txtDescr+ nonS tanda rdHo ldingReaso n : 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
NavaidsNavigation 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
EnRouteRouteRouteSegmentFlight LevelsTrack LengthTrack WidthTrack DirectionFlight Rules and Use
RoutePortionStandard 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• …Service is
Provided On