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 FFS.TD. indicates that the corresponding data item must be taken from the FireFightingService TEMPDELTA, 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
FFS.TD.ServiceOperationalStatusQCode
'UNSERVICEABLE'QFFAS
'LIMITED' Note: downgradedQFFCG
'OTHER:EXTENDED'QFFCH
Scope

Insert the value 'A'

Items B, C and D

Items B and C shall be decoded from the values of FFS.TD.validTime following the common production rules.

If at least one FFS.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 

EBNF 
template = ("Rescue and fire fighting services (1)")  "FFS.TD.ServiceOperationalStatus (2)" "FFS.TD.category (3)" "." \n
["\n" "due to" "4" ("FFS.TD.annotation") "."] \n
{"\n" "4" ("FFS.TD.annotation") "."}.

Reference

Data item (from coding scenario)

Rule

(1)
The name of the service shall be spelled out as "Rescue and fire fighting service"
(2)operational status

FFS.TD.ServiceOperationalStatus shall be inserted:

  • 'OTHER:EXTENDED' - this shall be translated into 'upgraded';
  • 'UNSERVICEABLE' - this shall be translated into 'unserviceable' or 'U/S';
  • 'LIMITED' - this shall be translated into 'downgraded'.
(3)service categoryFFS.TD.category numerical ('1' to '10') value shall be inserted, omitting the letter denominator "A" (aircraft) or "H" (helicopter).
(4)noteAnnotations shall be translated into free text according to the decoding rules for Notes

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 [archived] Event update 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:

EBNF 
template_cancel = ("Rescue and fire fighting services (1)") ("resumed normal operations" ["FFS.BL.category (3)"] | " : New NOTAM to follow (5)").
ReferenceRule
(5)

If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to choose the "New NOTAM to follow" branch.  This branch cannot be selected automatically because this information is only known by the operator.

Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”. 



  • No labels