...
- It is assumed that information about the Navaid and NavaidEquipment specialisations concerned covering the complete period of validity of the event exists and it was coded as specified in the Coding Guidelines for the (ICAO) AIP Data Set - Navaid [NAV].
In addition, it is assumed that:
- all primary components (NavaidEquipment specialisations) exist and are associated with the Navaid;
no NavaidEquipment specialisation exists without being used as component for at least one Navaid;
all Navaid of type 'ILS' or 'MLS' are associated with at least one runway direction.
...
Identifier | Data encoding rule | |||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ER-01 | First, create a new Event with a BASELINE TimeSlice (scenario='NAV.UNS', version='2.0') for which a PERMDELTA TimeSlice may also be provided | |||||||||||||||||||||||||||||||||
ER-02 | Second, identify the NavaidEquipment specialisations that are affected, as follows:
For each of the NavaidEquipment specialisations identified as explained above:
| |||||||||||||||||||||||||||||||||
ER-03 | Third, identify the Navaid affected by considering all Navaid which use one or more of the NavaidEquipment identified applying ER-02 as primary component. Important Note: if more than one Navaid is concerned, this scenario shall be applied for each such Navaid separately. In that very particular case, the NavaidEquipment TEMPDELTA will be associated with only one of the Events, because it cannot be associated in the same time with two (or more) distinct Events. The additional Event can be a " consequence" of the first Event. For the corresponding Navaid:
| |||||||||||||||||||||||||||||||||
ER-04 | The value 'PARTIAL' can only be used only for the operationalStatus of a TACAN, and for the associated Navaid with type=('TACAN' or 'VORTAC') if just one of its signalType ('AZIMUTH' or 'DISTANCE') is affected. | |||||||||||||||||||||||||||||||||
ER-05 | The values 'FALSE_POSSIBLE', 'CONDITIONAL' and 'DISPLACED' cannot be used in this scenario. | |||||||||||||||||||||||||||||||||
ER-06 | The value 'UNSERVICEABLE' shall be used only if the navaid does not emit any signal. Otherwise, the value 'ON_TEST' shall be used (which will be decoded as "On test, do not use. False indication possible"). | |||||||||||||||||||||||||||||||||
ER-07 | If no component was specified in the input data for a Navaid that has more than one component, then its NavaidOperationalStatus.operationalStatus shall get the value specified by the "operational status" input parameter. | |||||||||||||||||||||||||||||||||
ER-08 | In the case of a Navaid for which only one of its components (primary or not primary) NavaidEquipment specialisations is affected (has a temporarily changed operational status) but not all, then the TEMPDELTA TimeSlice of the Navaid shall have the value indicated in the following table (priority from top to bottom):
For example, if a VOR (equipment) component of a VOR/DME Navaid (service) is unserviceable, then the Navaid (of type VOR/DME) shall have a TEMPDELTA TimeSlice with operationalStatus='PARTIAL'. In the same time, the VOR (NavaidEquipment) will have a TEMPDELTA TimeSlice with operationalStatus='UNSERVICEABLE'. Note: This scenario is limited to one Navaid and either one or all its primary components. Thus, the first column in the table above applies to that single primary component being affected by the temporary situation. | |||||||||||||||||||||||||||||||||
ER-09 | In the case of a Navaid that has more than one a NavaidEquipment specialisation component with a changed operationalStatus equal to 'UNSERVICEABLE', 'ON_TEST', 'FALSE_INDICATION' or 'IN_CONSTRUCTION', then the unavailability of that component may change while the other primary component(s) exist and have an unmodified operationalStatus, then the nature of the navaid service may change. If this is the case, then the TEMPDELTA TimeSlice encoded for the Navaid shall also temporarily change the type of the Navaid. For example, if the DME component of a VOR/DME navaid is unserviceable, then the Navaid TEMPDELTA TimeSlice shall also indicate that type="VOR" only and the operationalStatus shall be "PARTIAL". The table below provides more detailed rulesthe specific cases where this rule applies:
| |||||||||||||||||||||||||||||||||
ER-10 | If the Navaid or NavaidEquipment status change 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 NavaidOperationalStatus of their TEMPDELTA Timeslice. See also the rules for Event Schedules. It is recommended that the HMI of a data provider application allows to provide a schedule only in relation with active times, because only these will be translated into NOTAM text. | |||||||||||||||||||||||||||||||||
ER-11 | In accordance with the AIXM Temporality Concept (see sections 3.4 and 3.5 in version 1.0), the NavaidOperationalStatus associated with the TEMPDELTA replaces all the BASELINE NavaidOperationalStatus information, during the TEMPDELTA time of applicability. Therefore, if the modified operational status only concerns certain times, the other times when the navaid or equipment eventually remains with the same status as in the Baseline data, shall be explicitly included in the TEMPDELTA. The calculation of the necessary additional NavaidOperationalStatus elements to be included in the TEMPDELTA shall be automatically done by the applications implementing this specification. All NavaidOperationalStatus 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/level" view of the navaid/equipment unserviceability, enabling the operator to graphically check the navaid/equipment operational status at different times, such as in the example below:
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. | |||||||||||||||||||||||||||||||||
| ER-12 | The system shall automatically identify the FIR where the Navaid is located. This shall be coded as corresponding concernedAirspace property in the Event If any different "affected FIR" from the one determined above is provided by the data originator, then corresponding concernedAirspace property(ies) shall be coded in the Event. | |||||||||||||||||||||||||||||||||
| ER-13 | If an "affected aerodrome" is provided by the data originator, then a corresponding concernedAirportHeliport property shall be coded in the Event. |
...