[2.0] [STAND.CLS] Aircraft stand - closure

Owned by Andreea Perca (Deactivated)
Last updated: 2024 Mar 13 by POROSNICU Eduard

Definition

The temporary "complete" closure of aircraft stand(s). 

Notes:

  • this scenario includes the closure 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 closure conditions (closure exceptions) applies equally to all. Otherwise, separate NOTAM shall be issued;
  • this scenario includes only a "complete" closure of an aircraft stand, a "partial" closure except for flight and/or aircraft categories or temporary addition of a supplementary restriction to the aircraft stand availability, such as "closed for aircraft heavier than..." is included in STAND.LIM scenario. 
  • this scenario does not cover the temporary change of the operational hours of an aircraft stand;
  • this scenario does not cover the situation when the aircraft stand is operating normally, but subject to a reason for caution. 

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event.

EBNF Code 
input = "airport designator" ["airport name"] "aircraft stand designator" {"aircraft stand designator"} \n
"status=CLOSED" ["closure reason"] \n
"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

status=CLOSEDThe operational status of the aircraft stand. In this scenario, it is only possible to indicate a complete closure.AircraftStand/ApronAreaAvailability.operationalStatus

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.

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/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 Event 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 with purpose='REMARK'

Assumptions for baseline data

It is assumed that the related ApronElement, Apron and AirportHeliport and 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:

  1. designator, and

  2. an association with the ApronElement, which is associated with an Apron, which is associated with an AirportHeliport;

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.CLS', 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 having operationalStatus='CLOSED' shall be coded in the AircraftStand TEMPDELTA.

Editorial 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 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 (with operationalStatus='CLOSED') of the TEMPDELTA Timeslice. See the rules for Event Schedules.

ER-04

The system shall automatically identify the 'FIR' where the AirportHeliport is located. This shall be coded as corresponding concernedAirspace property in the Event

ER-05The 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 provided