[2.0] [STAND.LIM] Aircraft stand - usage limitation change

Definition

The temporary usage limitation of aircraft stand(s).

Notes:

this scenario includes the usage limitation of one or more aircraft stands (could be all aircraft stands at the airport);
more than one aircraft stand can be included only if the limitations conditions apply equally to all. Otherwise, separate message (NOTAM) shall be issued;

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event. Note that the flight and/or aircraft categories branch is optional, but can be more than once.

EBNF Code

input = "airport designator" ["airport name"] "aircraft stand designator" {"aircraft stand designator"} \n
("conditional for" | "closed, except for" |  "prohibited for" | "allowed for")
(["aircraft"] ["flight"]) {["aircraft"] ["flight"]} ["PPR time" ["PPR details"]] \n
["reason"] "start time" "end time" [schedule] \n
[note].

The table below provides more details about each information item contained in the diagram. It also provides the mapping of each information item within the AIXM 5.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).

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
conditional for	The description of one or more operations, which is permitted under special conditions, usually a prior permission requirement	AircraftStand.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and AircraftStand/..Availability/..Usage.type with value 'CONDITIONAL'
closed, except for	Aircraft stand is closed, except for operations explicitly identified in the input data.	AircraftStand.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and AircraftStand/..Availability/..Usage.type with value 'RESERV'
prohibited for	The description of one or more operations that are prohibited for during the event duration.	AircraftStand.availability.ApronAreaAvailability.operationalStatus with value 'LIMITED' and AircraftStand/..Availability/..Usage.type with value 'FORBID'
additionally allowed for	The description of one or more additional operations that are available for a specific purpose during the event duration.	AircraftStand.availability.ApronAreaAvailability.operationalStatus with value 'OTHER:EXTENDED' and AircraftStand/..Availability/..Usage.type with value 'PERMIT'
aircraft	The description of one or more aircraft (such as "helicopter") types are permitted or prohibited (depending on the limitation type) during the event duration.	AirportHeliport/..Availability/..Usage/..selection/..AircraftCharacteristics Only the following AircraftCharacteristics properties are allowed to be used in this scenario: type, engine, wingSpan, wingSpanInterpretation, weight, weightInterpretation.
flight	The description of one or more type of flight categories (such as "emergency") that are permitted or prohibited (depending on the limitation type) during the event duration.	AirportHeliport/..Availability/..Usage/..selection/..FlightCharacteristics. Only the following FlightCharacteristics properties are allowed to be used in this scenario: type, rule, status, military, origin, purpose.
PPR time	The value (minutes, hours, days) of the prior permission request associated with a 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'
reason	The reason for the aircraft stand usage limitation.	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 on the apron, not a reason for a limitation.
start time	The effective date & time when the aircraft stand limitation starts. This might be further detailed in a "schedule".	AircraftStand/ApronTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition
end time	The end date & time when the aircraft stand limitation ends.	AircraftStand/ApronTimeSlice/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's usage is effectively limited according to a regular timetable, within the overall limitation period.	AircraftStand/ApronAreaAvailability/Timesheet/...according to the rules for Schedules
note	A free text note that provides further details concerning the aircraft stand limitation.	AircraftStand/ApronAreaAvailability.annotation with purpose='REMARK'

Assumptions for baseline data

It is assumed that the related ApronElement, Apron and AirportHeliport BASELINE Timeslice covering the entire duration of the event exist. In addition the information about the aircraft stand(s) concerned by the event already exist in the form of a AircraftStand BASELINE TimeSlice, which contains as a minimum:

designator, and
an association with the ApronElement, which is associated with an Apron, which is associated with an AirportHeliport;

It is also assumed that the following principle have been followed for the encoding of BASELINE AircraftStand.availability data (if available in the BASELINE data):

- the operationalStatus has the value 'NORMAL' (meaning that the facility operates with nominal parameters) for all AircraftStand.ApronAreaAvailability that are part of the BASELINE data;

Data encoding rules

The data encoding rules provided in this section shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. The compliance with some of these encoding rules can be checked with automatic data validation rules. When this is the case, the number of the encoding rule is mentioned in the data validation rule.

Identifier	Data encoding rule
ER-01	The temporary closure of an aircraft stand shall be encoded as: a new Event with a 'BASELINE' TimeSlice (scenario='STAND.LIM', version='2.0'), for which a PERMDELTA TimeSlice may also be provided; and a TimeSlice of type TEMPDELTA for each affected AircraftStand feature, for which the "event:theEvent" property points to the Event instance created above;
ER-02	First, all the BASELINE availability.ApronAreaAvailability (with operationalStatus='NORMAL'), if present, shall be copied in the TEMPDELTA (see Usage limitation and closure scenarios). Then, an additional availability.ApronAreaAvailability element shall be included in each Apron TEMPDELTA having: operationalStatus='LIMITED' if the apron usage is "conditional for", "closed, except for", "prohibited for"; operationalStatus='OTHER:EXTENDED' if the apron usage is "allowed for". Note: there is no mistyping - ApronAreaAvailability is the actual name of the object containing information about the operational status of an AircraftStand.
ER-03	If the aircraft stand usage is "conditional for" specified operations, flight and/or aircraft categories, then all specified limitations shall be encoded as ApronAreaUsage child elements with type='CONDITIONAL'.
ER-04	If the aircraft stand is "closed, except for" specified operations, flight and/or aircraft categories, then all specified limitations shall be encoded as ApronAreaUsage child elements with type='RESERV'.
ER-05	If the aircraft stand usage is "prohibited for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as ApronAreaUsage child elements with type='FORBID'.
ER-06	If the aircraft stand usage is "allowed for" specified operations, flight and/or aircraft categories, all specified limitations shall be encoded as ApronAreaUsage child elements with type='PERMIT'.
ER-07	The "aircraft-flight-PPR" branch can be used more than once. If this the case, then a parent ConditionCombination with logicalOperator='OR' shall be coded first. Otherwise, this parent element is not necessary. Then, each flight and/or aircraft combination shall be coded as a child ConditionCombination with logicalOperator equal to: 'NONE' - if either a flight condition or aircraft condition is specified (but not both); 'AND' - if both a flight condition and aircraft condition are specified.
ER-08	If PPR time is specified, the uom attribute shall also be specified.
ER-09	If the limitation concerns only 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 (with operationalStatus='LIMITED' or 'OTHER:EXTENDED') of all affected AircraftStand TEMPDELTA Timeslice(s). See the rules for Event Schedules.
ER-10	The system shall automatically identify the FIR where the AirportHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event
ER-11	The AirportHeliport concerned by the closure shall also be coded as concernedAirportHeliport property in the Event.

Examples

Following coding examples can be found on GitHub (links attached):

to be developed