Versions Compared

Version Old Version 1 New Version Current
Changes made by

Andreea Perca (Deactivated)

POROSNICU Eduard

Saved on

Key

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

Coding

Definition

The temporary closure of area(s) a portion of an area intended to accommodate aircraft for purposes of loading or unloading passengers, mail or cargo, fuelling, parking or maintenance. The closure can be total (any traffic is forbidden) or partial (with the exception of particular operations, flights or aircraft categories).

Notes:

  • this scenario includes the closure of one or more aprons (could be all the aprons at the airport);
  • this scenario includes closure of apron portions, defined by reference to intersection with other airport surfaces;
  • this scenario also includes closure of an apron except for flight and/or aircraft categories;
  • more than one apron and apron element can be included only if the closure conditions (closed, exceptions, parts) applies equally to all. Otherwise, separate NOTAM shall be issueda portion of an apron. It is assumed that the apron portion does not exist in the baseline data, and has to be created for the event;
  • this scenario does not cover the temporary addition of a supplementary restriction to the apron availability, such as "closed for aircraft heavier than...". This will be dealt with in a separate scenario;
  • this scenario does not cover the temporary change of the operational hours of an apron or apron element;
  • this scenario does not cover the situation when the apron and/or apron element is operating normally, but subject to a reason for caution (such as "grass cutting in progress", etc.). Such situations will be covered in a different scenario. 

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.

Image Removed

Image Removed 

Image Added

Code Block
titleEBNF Code
collapsetrue
input = "airport designator" ["airport name"] ("apron name" ["closed_apron_portion_input"]) {(\n
"apron name"portion ["closed_apron_portion_input"])}\n
["closure reason"] {"except" ["PPR time" ["PPR details"]] [["aircraft"] ["flight"] {"other combination" ["aircraft"] ["flight"]}]} \n geometry" "location and extent description"  \n
"status=CLOSED" ["closure reason"] "start time" "end time" ["schedule"] \n
{[note}.

closed_apron_portion_input = ("between" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") "and" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") | "relative position to" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator")) {"between" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") "and" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator") | "relative position to" ("taxiway designator" | "runway designator" | "apron designator" | "stand designator")}.].

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.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).

input of a published apron, specified using intersection elements between that apron and other taxiways, runways, aprons or stands.

See note on closed apron portion input below.

ApronElement(s) identified as explained in the Data Encoding Rule ER-01. Apron/ or {{}}

Data item

Description

AIXM mapping

airport designator

The published designator of the airport where the apron is located, used in combination with other elements in order to identify the apron (s) and/or apron portion (s) concerned.

AirportHeliport.designator

airport name

The published name of the airport where the apron is located, used in order to identify the apron(s) and/or apron portion(s) concerned.

AirportHeliport.name

apron name

The published name of the apron concerned. This information is used in combination with the airport designator/name in order to identify the affected  apron(s) and/or apron portion(s)

Apron.nameclosed

apron portion closed geometry

The coordinates defining the apron portion

to be closed.


ApronElement.extent/ElevatedSurface.posList

location and extent description

Textual description of the closed portion location and extent. 

ApronElement.annotation with propertyName='extent' and purpose='DESCRIPTION'
status=CLOSEDThe operational status of the apron element.ApronElement/ApronAreaAvailability.operationalStatus

closure reason

The reason for the apron (s) and/or apron portion (s) closure.

PPR details

Apron/ or ApronElement/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 closure.

flight

The description of one or more type of flight categories (such as "emergency") that are exceptionally permitted on the apron(s) and/or apron portion(s) during closure.

Apron or ApronElement/ApronAreaAvailability/..Usage/../FlightCharacteristics

aircraft

The description of one or more aircraft (such as "helicopter") types that are exceptionally permitted on the apron(s) and/or apron portion(s) during its closure.

Apron/ or ApronElement/ApronAreaAvailability/..Usage/../AircraftCharacteristicsNote that only certain properties can be used in this scenario. See data validation rules for details.

other combination

Another combination of aircraft/flight characteristics that are excepted from the closure.

Apron/ or ApronElement/ApronAreaAvailability/..Usage/ConditionCombination.logicalOperator with its value set to "OR".

PPR time

The value (minutes, hours, days) of the advanced permission request associated with the permitted operation.

Apron/ or ApronElement/ApronAreaAvailability/..Usage.priorPermission with uom attribute

Additional information concerning the prior permission requirement.

Apron/ or ApronElement/ApronAreaAvailability/..Usage.annotation with propertyName="priorPermission" and purpose="REMARK"

start time

The effective date & time when the apron closure starts. This might be further detailed in a "schedule".

Apron/ or ApronElement/ApronTimeSlice/TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePosition beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the apron closure ends.

Apron/ or ApronElement/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 apron portion is effectively closed according to a regular timetable, within the overall closure period.

ApronElement/ApronAreaAvailability/Timesheet/... according to the rules for

Schedules

note

A free text note that provides further details concerning the apron closure.

Apron/ or ApronElement/ManoeuvringAreaAvailability.annotation according to the rules for encoding annotations

Note on closed apron portion input:

  1. The application shall allow graphical display and selection of apron(s) and/or apron portion(s) to be closed;

  2. The HMI application should support the operator in identifying all relevant portions that are affected by the closure and have an impact on operations. Generally, the application shall support the operator in avoiding cul-de-sac/dead-end situations and warn on situations leading to nowhere. E.q. if a taxiway leads to a closed apron, the appropriate taxiway portion leading to the closed apron shall be closed as well. 

  3. If the operator selects a closure which extends over multiple ApronElements (e.g. t.b.a.), the application shall split the selection in individual TaxiwayElements and request operator confirmation for the selection. 

with purpose='REMARK'

Assumptions for baseline data

It is assumed that AirportHeliport BASELINE that AirportHeliport BASELINE Timeslice covering the entire duration of the event exist and have been coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set. In addition:addition the information about the Apron already exists in the form of a Apron BASELINE TimeSlice, which contains as a minimum:

  1. a name, and

  2. an association with the AirportHeliport

    ;If apron portions are concerned, it is assumed that they are encoded in BASELINE ApronElements as suggested in the following diagram:
    t.b.a. 
    Fig.1 - Encoding of ApronElements
    It is assumed that each Taxiway and TaxiwayElements BASELINE have an annotation with purpose=“DESCRIPTION” and note describing their location as depicted below:defined by reference to intersection with other airport surfaces:
         Image Removed
    Fig. 2 - Encoding of ApronElement description 
    E.g.  "between acft stand 1 and acft stand 5".
  3. defined by a relative position to other airport surfaces,  e.g. “north of TWY F”, or
  4. a combination between a and b above. 
    5. It is assumed that the following principles have been followed for the encoding of BASELINE Apron.availability and ApronElement.availability data (as available in the BASELINE data):the operationalStatus has the value "NORMAL" (meaning that the facility operates with nominal parameters) for all Apron.availability and/or ApronElement.availability that are part of the BASELINE data

    ;

  5. operations that are explicitly permitted have been encoded as availability.ApronAreaAvailability.usage.ApronAreaUsage with type=PERMIT or type=CONDITIONAL (in case a PPR is necessary);
  6. operations that are explicitly forbidden have been encoded as availability.ApronAreaAvailability.usage.ApronAreaUsage with type=FORBID;
  7. if the taxiway is exclusively reserved for certain operations, then the ApronAreaAvailability that describes this condition contains only ApronAreaUsage elements with type=RESERV;
  8. in case of conflicts:
    1. the usages of type FORBID take precedence over usages of type PERMIT or RESERVE;
    2. the usages of type PERMIT take precedence over the usages of type RESERVE;

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.

If the all affected Apron and/or ApronElement TEMPDELTA . (e.g. If a ApronElement is closed based on a schedule, its associatedApron TEMPDELTA shall have the same associated schedule (question))

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 Apron and/or ApronElement 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 apron element closure, enabling the operator to graphically check the availability at different times, such as in the example below:

Image Removed

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.

If Apron and/or (STAND.CLS under development)

Identifier

Data encoding rule

ER-01

The temporary closure of an apron or portion thereof shall be encoded as:

  • a new Event with a 'BASELINE' TimeSlice (encoding=DIGITAL, scenario=APN'APE.CLS', version='2.0'), for which a PERMDELTA TimeSlice may also be provided; and
  • in case of complete apron closure:
    • a TEMPDELTA TimeSlice for each affected Apron feature, for which the "event:theEvent" property points to the Event instance created above;
  • in case of partial apron closure:a TEMPDELTA TimeSlice for each affected

    a TimeSlice of type 'BASELINE' for the ad-hoc ApronElement feature, for which the

    "

    “event:theEvent

    " property points to the Event instance created above;a TEMPDELTA TimeSlice for each affected Apron feature for which the above ApronElement describesPartOf (associatedApron), for which the "event:theEvent"

    ” property points to the Event instance created above

    ;

Identification of the ApronElements to be closed shall be done as follows:

  • The application shall support the operator in order to automatically select the ApronElements that are concerned, as much as possible with a graphical view

    .

     When no graphical view is available, the application would need to analyze the closed apron portion input provided by the operator in comparison with the baseline data descriptions.

  • If the operator specifies that the portion concerned is spread across multiple ApronElements, then the application shall automatically select the portions highlighted. 
ER-02In case of complete apron closure, one ApronAreaAvailability element having operationalStatus=CLOSED shall be included in each Apron TEMPDELTA

ApronElement BASELINE TimeSlice shall have ApronAreaAvailability with operationalStatus='CLOSED'.

ER-03In case of apron portion closure, one ApronAreaAvailability element having operationalStatus=CLOSED shall be included in each ApronElement TEMPDELTA selected to be closed.
ER-04

In case of apron portion closure, a TEMPDELTA TimeSlice for the affected Apron feature for which the ApronElement describesPartOf (associatedApron) shall be created and shall have Apron.availability/ApronAreaAvailability.operationalStatus=LIMITED.

ER-05

If the closure is "except for" flight and/or aircraft categories, all specified exceptions shall be encoded as ApronAreaUsage child elements with:

  • either type=PERMIT, if there is no prior permission requirement;
  • or type=CONDITIONAL, if a prior permission requirement was specified. Note that this implies that a "closed" apron can still allow certain particular operations.

ER-06

If a unique flight or aircraft are specified as being excepted, they shall be encoded as one ConditionCombination with logicalOperator="NONE".

ER-07

Each pair of flight and aircraft conditions specified as being excepted shall be encoded as one ConditionCombination with logicalOperator="AND".

ER-08

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-07).

ER-09

ApronElement BASELINE TimeSlice shall have associatedApron@xlink:href the Apron on which is located (as selected by the operator)
ER-04The location and extent description shall be encoded in free text as an ApronElement.annotation with propertyName='extent' and purpose='DESCRIPTION'
ER-05If the apron portion 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 ApronElement 'BASELINE' Timeslice(s) created with the Event. See the rules for Event Schedules

ER-10

. 
ER-11ER-06If there exists aircraft stands on the closed ApronElement and if the apron portion closure makes the aircraft stand unavailable, then a consequence STAND.CLS scenario shall also be encoded for the relevant AircraftStand feature and shall include a reference to the current event with role 'causeEvent'.

Examples

...

ER-07

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

ER-08The 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 generated