Page Comparison

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 APL.BL. indicates that the corresponding data item must be taken from the ApproachLightingSystem BASELINE, which is valid at the start time of the Event;
• the abbreviation RLS.BL. indicates that the corresponding data item must be taken from the RunwayDirectionLightSystem BASELINE, which is valid at the start time of the Event;
• the abbreviation TWL.BL. indicates that the corresponding data item must be taken from the TaxiwayLightSystem BASELINE, which is valid at the start time of the Event;
• the abbreviation VGI.BL. indicates that the corresponding data item must be taken from the VisualGlideSlopeIndicator BASELINE, which is valid at the start time of the Event;
• the abbreviation RDN.BL. indicates that the corresponding data item must be taken from the RunwayDirection BASELINE, which is valid at the start time of the Event;
• the abbreviation AHP.BL. indicates that the corresponding data item must be taken from the AirportHeliport BASELINE, which is valid at the start time of the Event;
• the abbreviation TWY.BL. indicates that the corresponding data item must be taken from the Taxiway BASELINE, which is valid at the start time of the Event;
• the abbreviation APL.BLTD. indicates that the corresponding data item must be taken from the ApproachLightingSystem TEMPDELTA, which is valid at the start time of the Event;
• the abbreviation RLS.BLTD. indicates that the corresponding data item must be taken from the RunwayDirectionLightSystem TEMPDELTA, which is valid at the start time of the Event;
• the abbreviation TWL.BLTD. indicates that the corresponding data item must be taken from the TaxiwayLightSystem TEMPDELTA, which is valid at the start time of the Event
• the abbreviation VGI.BLTD. indicates that the corresponding data item must be taken from the VisualGlideSlopeIndicator 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 associated AirportHeliport where one of the services is provided 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.

and

and

Scope

...

Scope

Insert the value ‘A’.

Lower limit / Upper limit

Use “000/999”

Geographical reference

Insert the coordinate of the ARP (AHP.BL.ARP.ElevatedPoint) of the airport, formatted as follows:

• the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters;
• the radius value is “005”.

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 

Image RemovedImage Added

template = ["(1)"ACG "AHP.BL.type (12)" | ("ASVAHP.BL.type or categoryname (23a)" | "PSVAHP.BL.typeARP (33b)")  ] "\n" \n
( "(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") "."}."ALS RWY" "RDN.BL.designator" {"/" "RDN.BL.designator"} | "(5)" "RWY" "RLS.TD.position" {"AND" "RLS.TD.position"} "LIGHTS" "RDN.BL.designator" {"/" "RDN.BL.designator"} | "(6)" "TWY" "TWL.TD.position" {"AND" "TWL.TD.position"} "LIGHTS" "TWY.BL.designator" {"," "TWY.BL.designator"} | "(7)" "VGI.TD.type" "RDN.BL.designator" {"/" "RDN.BL.designator"}) \n
"TD.operationalStatus (8)" ["(9)" "EXCEPT" "APL.TD.lightIntensity"] "TD.annotation (10)"

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

...

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

EBNF Code Image Added

Image Removed

template_cancel = ["(1)" "ACGAHP.BL.type (12)" | ("ASVAHP.BL.typename or category (23a)" | "PSVAHP.BL.typeARP (33b)")] ( ["(4)" ("ACG"ALS RWY" "RDN.BL.ServiceOperationalStatusdesignator" |{"/" "ASVRDN.BL.ServiceOperationalStatusdesignator"} | "PSV "(5)" "RWY" "RLS.TD.position" {"AND" "RLS.TD.position"} "LIGHTS" "RDN.BL.ServiceOperationalStatusdesignator")] [{"/"New NOTAM to follow  "RDN.BL.designator"} | "(6)"] "." \n  

...

 "TWY" "TWL.TD.position" {"AND" "TWL.TD.position"} "TWY.BL.designator" {"," "TWY.BL.designator"} | "(7)" "VGI.TD.type" "RDN.BL.designator" {"/" "RDN.BL.designator"}) ("resumed normal operations." | " : New NOTAM to follow. (10)").