Definition

The notification that a subsystem of Ground Light System at the aerodrome service is temporary unserviceable (or downgraded). 

Notes:

  • this scenario shall be used to notify that one of (aerodrome) ground light systems is temporary unserviceable (or downgraded). 

  • this scenario does not cover the situation when the ground light sub-system is operating normally, but subject to a reason for caution.
  • the systems covered by this scenario include: ApproachLightingSystem, RunwayDirectionLightSystem, TaxiwayLightSystem, VisualGlideSlopeIndicator.

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" [name] \n
( "light type=ApproachLightingSystem.type" "light location" {"light location"} ["light intensity"] "operational status" | "light type=RunwayDirectionLightSystem.position" {"light type=RunwayDirectionLightSystem.position"} "light location" {"light location"} "operational status" | "light type=TaxiwayLightSystem.position" {"light type=TaxiwayLightSystem.position"} "light location" {"light location"} "operational status" | "light type=VisualGlideSlopeIndicator.type" "light location" {"light location"} "operational status" ) \n
"start time" "end time" ["schedule"] \n
{note}.

The following table 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).

Data item

Description

AIXM mapping

designator

The published designator of the airport/heliport concerned. This information, in combination with eventually the name is used to identify the airport/heliport.

AirportHeliport.designator

name

The published name of the airport/heliport. This information, in combination with the designator is used to identify the airport/heliport.

AirportHeliport.name

light type

The type/position of ground light subsystem which is affected.

  1. ApproachLightingSystem.type with CodeApproachLightingType list of values;
  2. RunwayDirectionLightSystem.position with CodeRunwaySectionType list of values;
  3. TaxiwayLightSystem.position with CodeTaxiwaySectionType list of values;
  4. VisualGlideSlopeIndicator.type with CodeVASISType list of values
light locationThe surface for which the lighting system is provided for.

RunwayDirection.designator or Runway.designator, Taxiway.designator

light intensityThe indication of the relative intensity of the  lighting system.

ApproachLightingSystem.intensityLevel with CodeLightIntensityType list of values;

operational status

The indication of a ground light subsystem unserviceability/limitation.

.../GroundLightingAvailability.operationalStatus with value = 'UNSERVICEABLE' or 'DOWNGRADED'.


start time

The effective date & time when the unserviceability of one of the airport ground light subsystems starts.

.../TimePeriod.beginPosition, Event/EventTimeSlice.validTime/timePeriod.beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The effective date & time when the unserviceability of one of the airport ground light subsystems ends.

Note: the end time can also be estimated. 

.../TimePeriod.endPosition, Event/EventTimeSlice.validTime/timePeriod.endPosition and Event/EventTimeSlice.featureLifetime/endPosition

schedule

A schedule might be provided, in case the predicted interruption of one of the ground light subsystems is only active according to a timetable, within the period between the start of life and the end of life..../GroundLightingAvailability/Timesheet according to the rules for {{Schedules}}

note

A free text note that provides further details concerning the unserviceability of one of the ground light subsystems.

/annotation with purpose=WARNING. The annotation is for the attention of a human users on the client side, which justify the use of purpose=WARNING

Note: In AIXM 5.1.1 - coding guidelines for AIP data set - interoperability rules - WARNING is reserved for notifications for operator. 

Assumptions for baseline data

It is assumed that information about the aerodrome (referring to light location) already exists in the form of AirportHeliport BASELINE TimeSlice(s) covering the complete period of validity of the event, for which the baseline availability is coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set.

It is assumed that information about the GroundLightSystem at the aerodrome already exists in the form of subclasses of GroundLightSystem BASELINE(s) TimeSlice covering the complete period of validity of the event, which contain as a minimum:

  1. aixm:type (for ApproachLightingSystem, VisualGlideSlopeIndicator) or aixm:position (for RunwayDirectionLightSystem, TaxiwayLightSystem)
  2. aixm:intensityLevel 
  3. aixm:availability with GroundLightAvailability=NORMAL
  4. aixm:airportHeliport referencing the airport/heliport where the service is provided.

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. To the maximum possible extent, the compliance with these encoding rules shall be verified with automatic data validation rules.

Identifier

Data encoding rule

ER-01

The unserviceability of one of the airport ground services at an airport shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario=”GLS.UNS”, version=”2.0”), for which a PERMDELTA TimeSlice may also be provided; and

  • a TimeSlice of type TEMPDELTA for the affected for ApproachLightingSystem, RunwayDirectionLightSystem, TaxiwayLightSystem, VisualGlideSlopeIndicator feature(s), for which the "event:theEvent" property points to the Event instance created above.

ER-02

One GroundLightAvailability element having operationalStatus=UNSERVICEABLE or (=DOWNGRADED for ApproachLightingSystem) shall be included in the ApproachLightingSystem, ApronLightSystem, RunwayDirectionLightSystem, TaxiwayLightSystem, TouchDownLiftOffLightSystem, VisualGlideSlopeIndicator TEMPDELTA.

ER-03At least one type (for ApproachLightingSystem, VisualGlideSlopeIndicator) or position (for RunwayDirectionLightSystem TaxiwayLightSystem) element shall be included in a respective TEMPDELTA.

ER-04

One intensityLevel element may be included in each ApproachLightingSystem TEMPDELTA with the list of values CodeLightIntensityType.
ER-05If the end of the event is estimated, gml:endPosition shall have the attribute indeterminatePosition="unknown". 
ER-06

If one of the airport ground services 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 GroundLightAvailability of the ApproachLightingSystem, RunwayDirectionLightSystem, TaxiwayLightSystem, VisualGlideSlopeIndicator TEMPDELTA Timeslice. See the rules for Event Schedules.

ER-07The Event BASELINE shall have event:textNOTAM with attributes xsi:nil="true" and nilReason="inapplicable". 
ER-10

The system shall automatically identify the FIR where the AerodromeHeliport 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):

  • to be developed
  • No labels