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 ACG.BL. indicates that the corresponding data item must be taken from the AircraftGroundService BASELINE, which is valid at the start time of the Event;
• the abbreviation ASV.BL. indicates that the corresponding data item must be taken from the AirportSuppliesService BASELINE, which is valid at the start time of the Event;
• the abbreviation PSV.BL. indicates that the corresponding data item must be taken from the PassengerService BASELINE, which is valid at the start time of the Event;
• the abbreviation ACG.TD. indicates that the corresponding data item must be taken from the AircraftGroundService TEMPDELTA, which is valid at the start time of the Event;
• the abbreviation ASV.TD. indicates that the corresponding data item must be taken from the AirportSuppliesService TEMPDELTA, which is valid at the start time of the Event;
• the abbreviation PSV.TD. indicates that the corresponding data item must be taken from the PassengerService TEMDELTA, which is valid at the start time of the Event;

Item A

The item A shall be generated according to the general production rules for item A using the Event.concernedAirportHeliport.

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.

Scope

Insert the value 'A'

Items B, C and D

Items B and C shall be decoded from the values of ACG.TD.validTime, ASV.TD.validTime, PSV.TD.validTime following the common production rules.

If at least one ACG.TD.ServiceOperationalStatus.timeInterval, ASV.TD.ServiceOperationalStatus.timeInterval, or PSV.TD.ServiceOperationalStatus.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}}.

Item E

The following patterns should be used for automatically generating the E field text from the AIXM data: 

EBNF Code 

template = ("ACG.BL.type(1)" | "ASV.BL.type or category (2)" | "PSV.BL.type (3)")  ("4" ("ACG.TD.ServiceOperationalStatus" | "ASV.TD.ServiceOperationalStatus" | "PSV.TD.ServiceOperationalStatus")) "." \n
["\n" "due to" "5" ("ACG.TD.annotation" | "ASV.TD.annotation" | "PSV.TD.annotation") "."] \n
{"\n" "5" ("ACG.TD.annotation" | "ASV.TD.annotation" | "PSV.TD.annotation") "."}.

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

If a NOTAM C is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "AK", except for the situation of a “new NOTAM to follow, in which case “XX” shall be used.

The following pattern should be used for automatically generating the E field text from the AIXM data:

template_cancel = ("ACG.BL.type(1)" | "ASV.BL.type or category (2)" | "PSV.BL.type (3)")  ("resumed normal operations." | " : New NOTAM to follow.(6)").