Definition
...
Data item | Description | AIXM mapping |
---|---|---|
airport designator | The published designator of the airport where the aircraft stand is located, used in combination with other elements in order to identify the aircraft stand concerned. | AirportHeliport.designator |
airport name | The published name of the airport where the aircraft stand is located, used in order to identify the aircraft stand concerned. | AirportHeliport.name |
aircraft stand designator | The designator of the aircraft stand to be closed. | AircraftStand.designator |
closure reason | The reason for the aircraft stand closure. | AircraftStand/ApronAreaAvailability.annotation with propertyName="operationalStatus" and purpose="REMARK". Note that the property "warning" of the ApronAreaAvailability class is not used here because it represents a reason for caution when allowed to operate at the aircraft stand, not a reason for a closure. |
PPR time | The value (minutes, hours, days) of the advanced permission request associated with the permitted operation. | AircraftStand/ApronAreaAvailability/..Usage.priorPermission with uom attribute |
PPR details | Additional information concerning the prior permission requirement. | AircraftStand/ApronAreaAvailability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK" |
aircraft | The description of one or more aircraft (such as "acft with wingspan less than") types that are exceptionally permitted at the aircraft stand during its closure. | AircraftStand/ApronAreaAvailability/..Usage/../AircraftCharacteristicsNote that only certain properties can be used in this scenario. See data validation rules for details. |
flight | The description of one or more type of flight categories (such as "emergency") that are exceptionally permitted at the aircraft stand during its closure. | AircraftStand/ApronAreaAvailability/..Usage/../FlightCharacteristics |
other combination | Another combination of aircraft/flight characteristics that are excepted from the closure. | AircraftStand/ApronAreaAvailability/..Usage/ConditionCombination.logicalOperatorwith its value set to "OR". |
start time | The effective date & time when the aircraft stand closure starts. This might be further detailed in a "schedule". | AircraftStand/AircraftStandTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition |
end time | The end date & time when the aircraft stand closure ends. | AircraftStand/AircraftStandTimeSlice/TimePeriod.endPosition, Event/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also applying the rules for{{Events with estimated end time}} |
schedule | A schedule might be provided, in case the aircraft stand is effectively closed according to a regular timetable, within the overall closure period. | AircraftStand/ApronAreaAvailability/Timesheet/...according to the rules for {{Schedules}} |
note | A free text note that provides further details concerning the aircraft stand closure. | AircraftStand/ApronAreaAvailability.annotation according to the rules for encoding annotations |
...
Identifier | Data encoding rule |
---|---|
ER-01 | The temporary closure of an aircraft stand shall be encoded as:
|
ER-02 | One ApronAreaAvailability element having operationalStatus=CLOSED shall be included in each Apron TEMPDELTA. If the aircraft stand is "closed except for" flight and/or aircraft categories, all specified excepted operations shall be encoded as ApronAreaUsage child elements with:
Note: No mistyping - ApronAreaAvailability is the actual name of the object containing information about the operational status of an AircraftStand. |
ER-03 | If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE". |
ER-04 | Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND". |
ER-05 | If the "other combination" branch is used, then a root ConditionCombinations element shall be encoded having logicalOperator="OR" and each pair of flight/aircraft included as a sub-condition (with logicalOperator="AND", see ER-04). |
ER-06 | If the aircraft stand closure is limited to a discrete schedule within the overall time period between the "start time" and the "end time", then this shall be encoded using as many as necessary timeInterval/Timesheet properties for the ApronAreaAvailability of the Air TEMPDELTA Timeslice. See the rules for Event Schedules. |
ER-07 | In accordance with the AIXM Temporality Concept, the ApronAreaAvailability elements included in the TEMPDELTA completely replace all the BASELINE ApronAreaAvailability information, during the TEMPDELTA time of applicability. Therefore, if the closure only concerns certain times, then the other times, when the aircraft stand eventually remains subject to the availability conditions of the Baseline data, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional ApronAreaAvailability elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification. All ApronAreaAvailability elements that are copied from the BASELINE data for completeness sake shall get an associated Note with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation". This is based on the current NOTAM practice which consists of including in the NOTAM only the changed information and not explicitly including the static data that remains valid during the NOTAM applicability. It is recommended that the input interface provides a "calendar" view of each taxiway element closure, enabling the operator to graphically check the availability at different times, such as in the example below: In the calendar view, the Baseline information that remains valid during the Event validity time shall be visibly identified from the information that is specific to the Event, for example by using a different colour fill pattern. |
...