Aeronautical Information Exchange Model (AIXM) Lessons learned

Transcription

1 Aeronautical Information Exchange Model (AIXM) Lessons learned railml.org conference, Paris Speaker: Eduard Porosnicu EUROCONTROL, Senior AIM Specialist 18 Sep 2013

2 Contents About Eurocontrol AIXM purpose and scope AIXM version 5 -key aspects UML model Temporality concept Use of GML/XML Schema Extensibility Status and condition of aeronautical features (digital NOTAM) Business Rules SESAR Project SWIM Master Class

3 About EUROCONTROL - European Organisation for the Safety of Air Navigation 3

4 Europe air traffic at a glance 450 Important Airports Aircraft Operators Peaks + 34,400 Flights a day + 10,000,000 Flights a year 4

5 EUROCONTROL European Organisation for the Safety of Air Navigation 1960 s 1980 s 1990 s s 40 member states & the European Community 5

6 Complementary Partners Political direction Community method Regulatory authority Finance Technical expertise Facilitation skills Civil-military Technical Agency of the Single European Sky 6

7 You typically hear about us hen things go wrong 7

8 8

9 About AIXM 9

10 AIXM why necessary European Aeronautical Information Services Database (EAD) Feasibility Study (by CAPdebis ) 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 electronic AIP Proposal for global standard (International Civil Aviation Organisation) For industry implementations etc.

11 AIXM Scope Ground Infrastructure Airspace structures and routes Rules and procedures Air Transportation Information Passenger MET Terrain and obstacles Flight Surveillance

12 AIXM 4.5: two main components AIXM Logical Information Model <AIXM-Snapshot> <Vor> <VorUid> <codeid>aml</codeid> <geolat> n</geolat> <geolon> w</geolon> </VorUid> </AIXM-Snapshot> AIXM Data Exchange Format <AIXM-Snapshot> <AIXM-Snapshot> <AIXM-Snapshot> <AIXM-Update> <AIXM-Update>

13 AIXM in EAD (today) Static data Update Chart Production (e)aip Production (SDO) Based on AIXM 4.5 Digital Data Input (AIXM 4.5 XML) Provided by industry. Similar implementation in local AIS systems Support NOTAM production AIXM 4.5 / 5.1 XML output

14 AIXM version 5 key aspects 14

15 AIXM version 5 Joint development EUROCONTROL FAA (with the support of the international AIS community) AIXM 5.0 AIXM 5.1 AIXM 4.5 Digital Aeronautical Information

16 AIXM 5 Design Objectives New capabilities Modularity Extensibility Flexible Exchange Flexible Messages Static and Dynamic Technical Design Decisions ISO19100 series UML GML 3.2 Expand/Refresh Domain Model Aerodrome Mapping Terminal Procedures Obstacles Metadata Integrity External Constraints

17 AIXM version 5.1 <<feature>> AirspaceUsage +restrictedairspace <<feature>> Airspace 1 +user 0..* <<feature>> OrganisationAuthority (from Organisation) isspecifiedfor hasuser <<feature>> StandardLevelColumn (from Standard Levels) 0..* isrestrictedto +discretelevelseries 0..1 series : CodeLevelSeriesType unitofmeasurement : UomDistanceVerticalType separation : CodeRVSMType 0..* +usage 1..* iscomposedof <<object>> AirspaceLayerUsage activity : CodeAirspaceActivityType statusactivation : CodeAirspaceActivationType trafficallowed : CodeMilitaryStatusType UML concerns 0..* +levels <<object>> LayerAndTime (from Level and Time Block) upperlimit : ValDistanceVerticalType upperlimitreference : CodeVerticalReferenceType lowerlimit : ValDistanceVerticalType lowerlimitreference : CodeVerticalReferenceType altitudeinterpretation : CodeAltitudeUseType 0..* isactiveby schedule <<object>> Timetable (from Time Management) workinghours : CodeTimetableType involvesaircraft +aircraft 0..* <<object>> AircraftCharacteristic (from Aircraft and Flight) type : CodeAircraftType engine : CodeAircraftEngineType numberengine : CodeAircraftEngineNumberType typeaircrafticao : CodeAircraftICAOType aircraftlandingcategory : CodeAircraftCategoryType wingspan : ValDistanceType wingspaninterpretation : CodeValueInterpretationType classwingspan : CodeAircraftWingspanClassType weight : ValWeightType weightinterpretation : CodeValueInterpretationType passengers : NoNumberType passengersinterpretation : CodeValueInterpretationType speed : ValWeightType speedinterpretation : CodeValueInterpretationType waketurbulence : CodeWakeTurbulenceType XSD Temporality Concept

18 Temporality Model Definition A model that incorporates the concept of time at feature level! Key assertions All features are temporal with start of life and end of life Example - a new air traffic control sector All features can change over time Example - a navigation aid changes frequency Additional issue feature properties can have different values according to a repetitive schedule AIXM Temporality Model Relates feature properties to the time extent in which they are valid Provides various means to describe the time extent

19 The basic Time Slice model

20 Temporary events (digital NOTAM) Feature Properties P1 P2 P3 P4 P5 TimeSlices: TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7 TS 8

21 Many years ago NOTAM = NOtice To AirMen When not more than NOTAM were on the list for one flight J With NOTAM in force world-wide at every moment L only digital data processing can help 21

22 Digital NOTAM = visual NOTAM 22

23 Enhanced Pre-flight Information Bulletin (mockup) 23

24 AIXM 5 - Use of Geography Markup Language (GML) <geolat> </geolat> <geolong> </geolong> <codedatum>wge</codedatum> AIXM 4.5 non GML <aixm:elevatedpoint srsname="urn:ogc:def:crs:epsg::4326" gml:id="id55"> <gml:pos> </gml:pos> </aixm:elevatedpoint> AIXM 5.1 GML

25 GML-based tools for AIXM data visualisation

26 Guidance and Profile of GML for use with Aviation Data Published: MAY 2012 by OGC (produced by the Aviation Domain WG) Status: OGC Discussion Paper ( 1 st part - Encoding guidelines for aviation specific data srsname (WGS 84 is imposed in aviation) Surface and lines - specials Parallels Arcs Embedded curves/points Geographical borders re-used in Surface definitions In relation with the use of AIXM for aeronautical data encoding 2 nd part - GML Profile

27 AIXM 5.1 extensions Additional information exchanged between selected partners extension Core AIXM Aeronautical information that is relevant for the whole ATM community world-wide, not regional specific (AIP, NOTAM, etc.)

28 Extensions UML model <<object>> PropertiesWithSchedule (from Schedules) <<feature>> Airspace (from Airspace) 0..* isactive +hostairspace +activation 0..* <<object>> AirspaceActivation (from Airspace) activity : CodeAirspaceActivityType status : CodeStatusAirspaceType islocatedin <<extension>> Airspace flexibleuse : CodeYesNoType level1 : CodeYesNoType level2 : CodeYesNoType level3 : CodeYesNoType 0..* 0..* <<extension>> AirspaceActivation reservationphase : CodeAirspaceReservationPhaseType 0..* isunderresponsibilityof isrequestedby isusedfor +responsibleamc 0..1 <<feature>> Unit (from Organisat...) requestor +militaryuse 0..* <<object>> MilitaryActivity militaryactivity : CodeMilitaryActivityType <<extension>> Unit airspacemanagementcell : CodeYesNoType

29 Extensions feature/object Purpose data of local interest forward compatibility

30 <<object>> PropertiesWithSchedule (from Schedules) +operationalcondition <<object>> FlightConditionCircumstance hascondition flight <<object>> FlightConditionCombination logicaloperator : CodeFlowConditionOperationType +element 0..* appliestoflight hasoperand <<object>> FlightConditionElement index : NoSequenceType is 1 1 +flightcondition <<choice>> FlightConditionElementChoice <<feature>> FlightRestriction designator : CodeFlightRestrictionDesignatorTy... type : CodeFlightRestrictionType instruction : TextInstructionType isapplicableat +flightlevel 0..* <<object>> FlightRestrictionLevel regulatesuseof +regulatedroute 0..* <<object>> FlightRestrictionRoute priorpermission : CodeYesNoType issequenceof +routeelement 1..* <<object>> FlightRoutingElement ordernumber : NoSequenceType speed : ValSpeedType speedreference : CodeSpeedReferenceType speedcriteria : CodeComparisonType isrestrictedto 0..* +flightlevel hascontactinstructions <<object>> ContactInformation +contact (from Address) name : TextNameType 0..* title : TextNameType Validation of AIXM data sets AIXM 5.1 UML AIXM 5.1 XSD -Does the data make sense? -Is it compliant with international standards? -Do I respect recommended practices? - Syntactic check -Check the compliance of an XML dataset with the XSD grammar -Performed by standard XML parsers (e.g. xerxes, MSXML, XMLSpy, etc.) AIXM 5.1 XML Airport features = Semantic check Business Rules

31 Use of SBVR 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) (Most) coded already in the AIXM schema AIXM Operative rules: rules extracted from official documents (ICAO Annexes), minimum data rules, consistency rules, recommended practices, coding rules

32 SBVR in AIXM - example ICAO Annex 11: If a control zone is located within the lateral limits of a control area, it shall extend upwards from the surface of the earth to at least the lower limit of the control area. SBVR equivalent:

33 Encoding Business Rules ISO Schematron Schematron ( is an open language for the validation of XML document whose specification is standardized (ISO/IEC 19757) There are 6 basic elements in ISO Schematron: assertion, rule, pattern, schema, namespace and phase. AIXM 5.1 Business rules 33

34 SESAR System Wide Information Management 34

35 SWIM context SWIM consists of standards, infrastructure and governance enabling the management of ATM information and its exchange between qualified parties via interoperable services. SWIM Governance Qualified parties Qualified parties ATM information Air/Ground Datalink Qualified party ATM information Standards Standards Service consumer(s) Service(s) Standards Air-Ground SWIM SWIM Infrastructure Standards Network infrastructure (Internet, PENS) 35

36

37 2013 Open competition Raise awareness on SWIM Increase buy-in Accelerate uptake 1 More data providers 2 Development of services 3 Development of SWIM enabled applications 4 Key role for Standard Organisations 37

38 Conclusions AIXM version 5 - key aspects UML model Temporality concept Use of GML/XML Schema Extensibility Status and condition of aeronautical features (digital NOTAM) Business Rules We are interested in further cooperation GML? SWIM Master Class?

39 Contact Information Eddy Porosnicu(EUROCONTROL) +32 (2) Diana Young (FAA) +1 (202)