...
...
...
...
...
...
Text NOTAM production rules
This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:
- the abbreviation NAV.BL. indicates that the corresponding data item must be taken from the Navaid BASELINE, which is valid at the start time of the Event;
- the abbreviation NAV.TD. indicates that the corresponding data item must be taken from the Navaid TEMPDELTA;
- the abbreviation NEQ.BL. indicates that the corresponding data item must be taken from the NavaidEquipment BASELINE, which is valid at the start time of the Event;
- the abbreviation NEQ.TD. indicates that the corresponding data item must be taken from the NavaidEquipment TEMPDELTA;
- Important note: According to encoding rule ER-11, the TEMPDELTA might also include NavaidOperationalStatus elements that have been copied from the BASELINE data for compliance with the AIXM Temporality rules. The current practice is to not include such static information in the NOTAM text. Therefore, all NavaidOperationalStatus that have an associated annotation with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall be excepted from the text NOTAM generation algorithm!
Several NOTAMs possible
There are several situations that can trigger the need to issue several NOTAM to ensure that the information appears in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). The Event can have an explicit associationEvent to AirportHeliport as defined in ER-12. If the Event has an associationEvent to an AirportHeliport, a "navaid unserviceable" NOTAM with scope AE and subsequent NOTAMs for each airport that is affected needs to be published, with the corresponding airport designator in item A.
...
Note: A better solution would be that such navaid outages are translated into one NOTAM with the FIR in item A. Then, separate Events and separate NOTAM should be published for the affected Procedures, having the airport identifier in item A. This approach will be considered for the further development of this Specification, when the scenario for Procedures unavailability will be included.
Item A
The item A shall be generated according to the geographical location of the Airspace and shall contain the Airspace.designator of the predefined FIR(s) for which a NOTAM has to be issued, except if there is an association Event to an AirportHeliport case in the AirportHeliport.designator shall be used.
Item Q
Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:
Q code
The mapping provided in the tables below shall be used.
...
NAV.TD.operationalStatus | Corresponding Q codes (4th and 5th letters) |
|---|---|
UNSERVICEABLE | AS |
ONTEST | CT |
INTERRUPT | LS |
PARTIAL | AS |
FALSE_INDICATION | XX |
DISPLACED | CM |
IN_CONSTRUCTION | XX |
OTHER | XX |
Scope
Insert here AE.
Items B, C and D
Items B and C shall be decoded from the values of NAV.TD.validTime following the common production rules.
If at least one NAV.TD.NavaidOperationalStatus.timeInterval exists (the Event has an associated schedule), then the associated Timesheets(s) shall be decoded in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.
Item E
The following pattern should be used for automatically generating the E field text from the AIXM data:
...
Reference | Rule | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | The name of the Navaid shall be included if present in the NAV.BL data | ||||||||||||||||||||||||||||||||||||||||
(2) | Insert the type from the Navaid baseline, according to the following decoding rule:
| ||||||||||||||||||||||||||||||||||||||||
(3) | If the Navaid Baseline has several Navaid components and only one of its primary component NavaidEquipment has a NEQ.TD associated with the Event, then insert the type of that equipment, according to the following decoding rule:
| ||||||||||||||||||||||||||||||||||||||||
(4) | If NAV.BL is TACAN or VORTAC and its (TACAN)TD.availability.signalType is specified, then insert its value here. | ||||||||||||||||||||||||||||||||||||||||
(5) | The following rules apply:
| ||||||||||||||||||||||||||||||||||||||||
(6) | Apply the following rules:
| ||||||||||||||||||||||||||||||||||||||||
(7) | Apply the following rules:
| ||||||||||||||||||||||||||||||||||||||||
(8) | Insert the NEQ.TD.operationalStatus decoded as follows:
| ||||||||||||||||||||||||||||||||||||||||
(9) | If specified, insert here only the NEQ.TD.NavaidOperationalStatus.annotation that has propertyName="operationalStatus" and purpose="REMARK", translated into free text according to the following encoding rules. | ||||||||||||||||||||||||||||||||||||||||
(10) | Annotations shall be translated into free text according to the rules for annotations decoding. |
Note: The objective is to full automatic generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error, when re-typing is allowed).
Items F & G
Leave empty.
Event Update
The eventual update of this type of event shall be encoded following the general rules for {{Event updates or cancellation}}, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAM C
...