Versions Compared

Old Version 8

changes.mady.by.user POROSNICU Eduard

Saved on

compared with

New Version 9

changes.mady.by.user POROSNICU Eduard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Definition

...

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:

  1. designator, and

  2. 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):

...

10

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-06If 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-11The 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):

...