The European Organisation for the Safety of Air Navigation AIXM Support for Digital NOTAM AIXM XML...

The European Organisation for the Safety of Air Navigation

AIXM Support for Digital NOTAMAIXM XML Developers’ Seminar #523 March 2010

AIXM Support for Digital NOTAM 2

Contents

• Event Message Type

• Temporality• The Temporality Model• Applying the Temporality Model• Usage Examples

• Properties with Schedule• eASM examples


Event Message Type - UMLDraft used in xNOTAM Trial

CodeEventType

TEMPORARY : stringTRANSIENT : stringPERMANENT : stringOTHER : string

(from Digital NOTAM Data Types)

<<enumeration>>

AIXMFeature

identifier : CodeUUIDType

(from AIXM Abstract Feature)

<<feature>>

EventMember<<collectionMemberChoice>>

11

refersTo

NOTAM

series : AlphanumericTypenumber : AlphanumericTypeissued : DateMonthDayTypecancelled : DateMonthDayTypetranslationICAO : AlphanumericTypetranslationPlainLanguage : AlphanumericTypetranslationTraditional : AlphanumericTypelocation : AlphanumericType

<<object>>

Event

name : TextNameTypedescription : TextInstructionTypetype : CodeEventType

<<message>>

1..*1..*

hasMember

0..10..1

isDecodedAs

0..10..1isUpdateFor


Event Message Type – XMLDraft used in xNOTAM Trial


Event Message Type

• Upgraded to AIXM 5.1 extension • Tested in OGC OWS-7 testbed

NOTAM

series : AlphanumericTypenumber : AlphanumericTypeissued : DateMonthDayTypecancelled : DateMonthDayTypetranslationICAO : Character2TypetranslationPlainLanguage : Character3TypetranslationTraditional : Character3Typelocation : AlphanumericType

<<object>>

EventProperties

name : TextNameTypedescription : TextInstructionTypetype : CodeEventBaseType

<<object>>

Event<<message>>

0..1

+textNOTAM

0..1

isDecodedAs

0..1+previousEvent

0..1isUpdateFor

0..1

+properties

0..1

isDefinedAs

EventMember<<collectionMemberChoice>>

1..*1..*

hasMember

AIXMFeature


(from AIXM Abstract Feature)

11

refersTo

CodeEventBaseType

TEMPORARY : stringTRANSIENT : stringPERMANENT : stringOTHER : string

<<codelist>>

CodeEventType

nilReason : NilReasonEnumeration

<<datatype>>

string

<<XSDfacet>> whiteSpace : null = preserve

(from XMLSchemaDatatypes)

<<XSDsimpleType>>


Contents





Temporality Summary - Time Slice types

• BASELINE = A kind of Time Slice that describes the feature state (the set of all feature’s properties) as result of a permanent change;

• PERMDELTA = A kind of Time Slice that describes the difference in a feature state as result of a permanent change;

• TEMPDELTA = A kind of Time Slice that describes the transitory changes of a feature state during a temporary event;

• SNAPSHOT = A kind of Time Slice that describes the state of a feature at a time instant, as result of combining the actual BASELINE Time Slice valid at that time instant with all TEMPDELTA Time Slices applicable at that time instant.


Feature has time varying properties

Time

P1

FeatureProperties

value 1 value 2 value 3 value 4

P2 value a value b

P3 value x

P4 value z

P5 value $ value #


The basic Time Slice model

Time

P1

FeatureProperties

value 1 value 2 value 3 value 4

P2 value a value b

P3 value x

P4 value z

P5 value $ value #


The basic Time Slice model

P1

FeatureProperties

P2

P3

P4

P5

TimeSlices: TS 1 TS 2 TS 3 TS 4 TS 5 TS 6 TS 7 TS 8

states


P1

FeatureProperties

P2

P3

P4

P5


temporaryvalue w

TS "temp”

event

Temporary events – digital NOTAM


P1

FeatureProperties

P2

P3

P4

P5


temporaryvalue w

SNAPSHOT

SNAPSHOT = describes the state of a feature at a time instant, as result of combining the actual BASELINE Time Slice valid at that time instant with all TEMPDELTA Time Slices applicable at that time instant.

Current State


P1

FeatureProperties

P2

P3

P4

P5


temporaryvalue w

TS "temp”

event

PERMDELTA = A kind of Time Slice that describes the difference in a feature state as result of a permanent change.

Permanent changes


P1

FeatureProperties

P2

P3

P4

P5

Time

Time Slice Types

PERMDELTA 1(start of life)

PERMDELTA 2 PERMDELTA 3PERMDELTA 4

PERMDELTA 5 PERMDELTA 6PERMDELTA 7

PERMDELTA 8PERMDELTA 9

(end of life)

TEMPDELTA

temporaryvalue w

SNAPSHOT


Corrections

• Information about events that are planned to take place in future

• update the already communicated information

• may affect “event” Time Slices - of type PERMDELTA and TEMPDELTA.

• Solution

• Identify Time Slice concerned by a “sequence number”

• Also needed: “correctionNumber”


Final UML representation

AIXMFeature


<<feature>>

AIXMFeatureTimeSlice

validTimeinterpretationsequenceNumbercorrectionNumberfeatureLifetimeproperty1property2property3...

1..* +time varying properties1..*

AIXMFeaturePropertyGroup<<object>>

1 +propertyGroup1


AIXM UML – including temporality


Summary - Time Slice types

• BASELINE = A kind of Time Slice that describes the feature state (the set of all feature’s properties) as result of a permanent change;

• PERMDELTA = A kind of Time Slice that describes the difference in a feature state as result of a permanent change;

• TEMPDELTA = A kind of Time Slice that describes the transitory changes of a feature state during a temporary event;

• SNAPSHOT = A kind of Time Slice that describes the state of a feature at a time instant, as result of combining the actual BASELINE Time Slice valid at that time instant with all TEMPDELTA Time Slices applicable at that time instant.


An Example: Navaid frequency change

Imagine that AML Navaid undergoes an upgrade that changes its frequency from 112.0 MHz to 113.2 MHz…


Applying the model for Digital NOTAM

• TEMPDELTA

• For temporary situations

• PERMDELTA

• For permanent changes

• BASELINEs

• For so called “transient” features


TEMPDELTA

• Changes of a limited duration• Considered to be overlaid on the permanent state of the feature• When the temporary change ends, the temporary changes no

longer apply and we revert back to the permanent feature state.


Feature - gml:identifier

Optional: include the BASELINE/SNAPSHOT in the message

TEMPDELTA


Identifying the feature affected by “delta”

<Feature> <gml:identifier>35149fb2-971f-492c-94c2-5671d4580587</gml:identifier> <timeSlice> <validTime>….</validTime> <interpretation>BASELINE</interpretation> <sequenceNumber>23</sequenceNumber> <property1>….</property1> <property2>….</property2> …. </timeSlice> <timeSlice> <validTime>….</validTime> <interpretation>TEMPDELTA</interpretation> <sequenceNumber>23</sequenceNumber> <property4>….</property4> </timeSlice></Feature>

AIXMFeature


<<feature>>





1 +propertyGroup1


Identifying the feature affected by “delta”

<Feature> <gml:identifier>35149fb2-971f-492c-94c2-5671d4580587</gml:identifier> <timeSlice> <validTime>….</validTime> <interpretation>SNAPSHOT</interpretation> <property1>….</property1>  <property2>….</property2> </timeSlice> <timeSlice> <validTime>….</validTime> <interpretation>TEMPDELTA</interpretation> <sequenceNumber>23</sequenceNumber> <property4>….</property4> </timeSlice></Feature>

AIXMFeature


<<feature>>





1 +propertyGroup1


PERMDELTA

• Considered irreversible at the time when it is being made

• For Permanent Events, two Timeslices are created: • the first one is of type PERMDELTA and contains just the

values of the modified properties; • the second one is of type BASELINE and contains the result of

merging the changes (as they appear in the above PERMDELTA) with the existing BASELINE form the database. The result is this new BASELINE. It is a recomendation of the Temporality model to include in the AIXM 5 message both the PERMDELTA and the BASELINE


PERMDELTA



BASELINE with End-of-life

• A temporary obstacle that did not exist before and does not have a baseline (static data) can also be created as a Temporary Event.

• This creates a BASELINE which has an end-of-life


• Feature creation (commissioning)• Feature withdrawal (de-commissioning)


BASELINE with End-of-life


Cancelling a Time Slice

• Indicate a cancellation:• validTime is empty• Use same sequence number• Use a higher correction number

<Feature> <gml:identifier>35149fb2-971f-492c-94c2-5671d4580587</gml:identifier> <timeSlice> <gml:validTime nilReason=“inapplicable” /> <interpretation>PERMDELTA</interpretation> <sequenceNumber>23</sequenceNumber> <correctionNumber>1</correctionNumber> …. </timeSlice></Feature>


Contents





Properties With Schedule (1)

SpecialDate

type : CodeSpecialDateTypedateDay : DateMonthDayTypedateYear : DateYearTypename : TextNameType

<<feature>>

Timesheet

timeReference : CodeTimeReferenceTypestartDate : DateMonthDayTypeendDate : DateMonthDayTypeday : CodeDayTypedayTil : CodeDayTypestartTime : TimeTypestartEvent : CodeTimeEventTypestartTimeRelativeEvent : ValDurationTypestartEventInterpretation : CodeTimeEventCombinationTypeendTime : TimeTypeendEvent : CodeTimeEventTypeendTimeRelativeEvent : ValDurationTypeendEventInterpretation : CodeTimeEventCombinationTypedaylightSavingAdjust : CodeYesNoTypeexcluded : CodeYesNoType

<<object>>

OrganisationAuthority

name : TextNameTypedesignator : CodeOrganisationDesignatorTypetype : CodeOrganisationTypemilitary : CodeMilitaryOperationsType

(from Organisation)

<<feature>>

0..1

0..*

+authority 0..1

0..*

isAssociatedWith

PropertiesWithSchedule<<object>>

0..*+timeInterval 0..*

isComposedOf

0..*

0..*

+specialDateAuthority

0..*

0..*appliesSpecialDatesOf


Properties With Schedule (2)

PropertiesWithSchedule(from Schedules)

<<object>>

NavaidOperationalStatus

operationalStatus : CodeStatusNavaidTypesignalType : CodeRadioSignalType

<<object>>

0..*0..*

+availability

worksBy

Navaid

type : CodeNavaidServiceTypedesignator : CodeNavaidDesignatorTypename : TextNameTypeflightChecked : CodeYesNoTypepurpose : CodeNavaidPurposeTypesignalPerformance : CodeSignalPerformanceILSTypecourseQuality : CodeCourseQualityILSTypeintegrityLevel : CodeIntegrityLevelILSType

<<feature>>


Temporality Documentation


eASM extension

Unit

airspaceManagementCell : CodeYesNoType

<<extension>>

Classes and associations in blue color are extensions specific to the eASM package. The rest are part of AIXM Core.

Airspace

flexibleUse : CodeYesNoTypelevel1 : CodeYesNoTypelevel2 : CodeYesNoTypelevel3 : CodeYesNoType

<<extension>>

AirspaceActivation

activity : CodeAirspaceActivityTypestatus : CodeStatusAirspaceType

(from Airspace)

<<object>>

Unit(from Organisation)...)

<<feature>>

0..*

0..1

0..*

+responsibleAMC 0..1

isUnderResponsib ilityOf

MilitaryActivity

militaryActivity : CodeMilitaryActivityType

<<object>>

Airspace(from Airspace)

<<feature>>

0..*

+activation

0..*

isActive

AirspaceActivation

reservationPhase : CodeAirspaceReservationPhaseType

<<extension>>

0..*

0..1

0..*

+requestor

0..1

isRequestedBy

0..*+militaryUse 0..*

isUsedFor

0..*

0..*

+hostAirspace0..*

0..*

isLocatedIn

PropertiesWithSchedule(from Schedules)

<<object>>

Classes and associations in blue color are extensions specific to the eASM package. The rest are part of AIXM Core.

ConstrainingAirspaceActivity

effect : CodeAirspaceReservationImpactType

<<object>>

RouteSegment(from En-route)

<<feature>>RouteAvailability

direction : CodeDirectionTypecardinalDirection : CodeCardinalDirectionTypestatus : CodeRouteAvailabilityType

(from En-route)

<<object>>

0..*

+availability

0..*isActiveBy

Airspace(from Airspace)

<<feature>>

RouteAvailability

conditionalRouteType : CodeConditionalRouteType

<<extension>>

0..*

0..*

0..*

+hostAirspace0..*

isLocatedIn

0..*

0..*

+causeOfLimitation0..*

0..*

hasOperationalDependencies


eASM examples – TSA airspace

• AIXM 5.1 data set containing “baseline” information about a TSA airspace. TSA baseline

• It includes

• the airspace geometry definition

• the declaration of the default state “available for activation”. This means that the airspace is normally inactive and information about its activation will be promulgated as a “delta” Timeslice.

• Information about the activation of the airspace is provided in an “eAMI” message, that includes a TempDelta TimeSlice for the TSA airspace

eAMI message – Airspace Activation


Appendix

• Some tricky examples


“Delta” for multiple occurring properties

<AirportHeliportTimeSlice> …. <serves> <City>

<name>…</name> </City> </serves> <serves> <City>

<name>…</name> </City> </serves>…

AirportHeliport

designator : CodeAirportHeliportDesignatorTypename : TextNameTypelocationIndicatorICAO : CodeICAOTypedesignatorIATA : CodeIATATypetype : CodeAirportHeliportTypeprivate : CodeYesNoTypecontrolType : CodeMilitaryOperationsTypereferencePointDescription : TextDescriptionTypefieldElevation : ValDistanceVerticalTypefieldElevationAccuracy : ValDistanceVerticalTypeverticalDatum : CodeVerticalDatumTypelocationDescription : TextDescriptionTypemagneticVariation : ValMagneticVariationTypedateMagneticVariation : DateYearTypemagneticVariationChange : ValMagneticVariationChangeTypereferenceTemperature : ValTemperatureTypealtimeterCheckLocation : TextDescriptionTypesecondaryPowerSupply : TextDescriptionTypewindDirectionIndicator : TextDescriptionTypelandingDirectionIndicator : TextDescriptionTypetransitionAltitude : ValDistanceVerticalTypetransitionLevel : ValFLTypelowestTemperature : ValTemperatureTypeabandoned : CodeYesNoType

<<feature>>

City

name : TextNameType

<<object>>

0..*0..* serves

Rule: Include all occurrences of the <serves> property in a TEMPDELTA or a PERMDELTA!


“Delta” for complex properties

<AirportHeliportLimitation> …. <hasApplicableTimes> <Timetable> <workingHours>…</workingHours> <isComposedOf>

<Timesheet>…</Timesheet> </isComposedOf> <isComposedOf>

<Timesheet>…</Timesheet> </isComposedOf> …. </hasApplicableTimes>…Rule: Include the whole complex property!

(“delta” applies strictly to the 1st level of properties!)

AirportHeliportUsageLimitation

codeUsageLimitation : CodeUsageLimitationType

<<object>>

Timesheet

timeReference : CodeTimeReferenceTypestartDate : DateMonthDayTypeendDate : DateMonthDayTypeday : CodeDayTypedayTil : CodeDayTypestartTime : TimeTypestartEvent : CodeTimeEventTypestartTimeRelativeEvent : ValDurationTypestartEventInterpretation : CodeTimeEventCombinationTypeendTime : TimeTypeendEvent : CodeTimeEventTypeendTimeRelativeEvent : ValDurationTypeendEventInterpretation : CodeTimeEventCombinationType

(f rom Time Management)

<<object>>

Timetable(f rom Time Management)

<<object>>0..10..1

hasAppl icableTimes

1

0..*

1

0..*isComposedOf

Date post:	20-Jan-2016
Category:	Documents
Upload:	noreen-may
View:	224 times
Download:	0 times

The European Organisation for the Safety of Air Navigation AIXM Support for Digital NOTAM AIXM XML...

Documents