NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.2 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:

the abbreviation SSE.BL. indicates that the corresponding data item must be taken from the SatelliteService BASELINE, which is valid at the start time of the Event;
the abbreviation SSM.BL. indicates that the corresponding data item must be taken from the SatelliteSystem BASELINE, which is valid at the start time of the Event;
the abbreviation GSS.BL. indicates that the corresponding data item must be taken from the GBASService BASELINE, which is valid at the start time of the Event;

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). See Several NOTAM possible for additional guidance.

Event.concernedAirspace	Event.concernedAirportHeliport	NOTAM to be generated
assigned value(s)	assigned value(s)	Produce a "first" NOTAM (scope AE) for all FIR (using template_area_outage) and one of the aerodromes (using template_aerodrome) associated with the Event and additional (scope A) NOTAM for each additional airport (using template_aerodrome)
assigned value(s)	NIL	produce a single NOTAM for all the FIR(s) identified (using template_area_outage)

Item A

The item A shall be generated according to the general production rules for item A using:

if present, the AirportHeliport associated with the SSE.BL.satelliteService.approachLocation or GSS.BL.servedApproach/RunwayDirection property;
otherwise, if the SSE.BL.SatelliteServiceArea.area is provided, the Airspace(s) of type 'FIR' that overlap with the affected area.

Item Q

Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:

Q Code

If item A is an aerodrome then QGAAU shall be used, if item A is FIR use QGWAU instead.

Scope

Follow Several NOTAM possible cases.

Items B, C and D

Items B and C shall be decoded from the values of SSE.BL.validTime or GSS.BL.validTime following the common production rules.

If at least one SSE.BL.SatelliteServiceArea.operationalStatus.timeInterval, SSE.BL.SatelliteApproachOperation.operationalStatus.timeInterval, or GBASService.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}}.

Item E

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

EBNF Code

EBNF

template_area_outage = "SSM.BL.designator (1)" "SSE.BL.Area.operationalStatus (3)" \n 
["(6)" "in an area defined as" "SSE.BL.Area.area"] "for" [ "(7)"  "SSE.BL.serviceType" ] \n 
["due to"] ["SSE.BL.annotation (10)"] "." \n
{"SSE.BL.annotation (10)" "."}.

EBNF

template_aerodrome = ("SSM.BL.designator (1)" | "GSS.BL.name (2)") ["SSE.BL.SatelliteApproachOperation.operationalStatus (4)"] ["GSS.BL.NavaidOperationalStatus (5)"] \n 
"for" ["SSE.BL.SatelliteApproachOperation.satelliteApproachType (8)"] ["GSS.BL.servedApproach (9)"] \n 
["due to"] ["SSE.BL.annotation (10)" | "GSS.BL.annotation (10)"] "." \n
{("SSE.BL.annotation (10)" | "GSS.BL.annotation (10)") "."}.

*Reference*	Data item (from coding scenario)	*Rule*
(1)	satellite system	The name of satellite system for which service may be impacted shall be included, if present in SSM.BL.designator.
(2)	GBAS service	If GSS.BL.name is provided, this shall be translated in "GBAS"
(3)	operational status	When SSM.BL.designator is provided, then operational status as provided in SSE.BL.SatelliteServiceArea.operationalStatus shall be used. When operationalStatus= 'RAIM_NOT_AVBL' - this shall be translated into 'RAIM not available'; 'UNSERVICEABLE' - this shall be translated into 'unserviceable' or 'U/S'; 'UNRELIABLE' - this shall be translated into 'may be unreliable'.
(4)	operational status	If there is an approachLocation associated with a coded SatelliteService BASELINE and SSM.BL.designator is provided, then SSE.BL.SatelliteApproachOperation.operationalStatus shall be provided. When operationalStatus= 'RAIM_NOT_AVBL' - this shall be translated into 'RAIM not available'; 'UNSERVICEABLE' - this shall be translated into 'unserviceable' or 'U/S'; 'UNRELIABLE' - this shall be translated into 'may be unreliable'. If no SSE.BL.SatelliteApproachOperation.operationalStatus, then leave blank.
(5)	operational status	If there there is a servedApproach associated with a coded GBASService BASELINE then GSS.BL.NavaidOperationalStatus shall be inserted. When NavaidoperationalStatus= 'UNSERVICEABLE' - this shall be translated into 'unserviceable' or 'U/S'; 'FALSE_INDICATION' - this shall be translated into 'do not use, false indication possible' 'FALSE_POSSIBLE' - this shall be translated into 'use with caution, false indication possible' If no GSS.BL.NavaidOperationalStatus is provided, then leave blank. Note: the composition of the message in terms of operational status may need to be adapted to meet the local regulations.
(6)	service outage area	If specified for the SatelliteServiceArea.area, the GML encoding of the area (gml:Surface) shall be translated into human readable text, following the rules for encoding and decoding GML geometries.
(7)	satellite navigation service	If provided, insert here the SSE.BL.serviceType indicating affected operations in the specified area. Otherwise, leave blank.
(8)	approach type	Insert here the satellite approach type from SSE.BL.SatelliteApproachOperation.satelliteApproachType. Leave blank if not provided.
(9)	runway direction designator	Insert here RunwayDirection.BL.designator associated with GSS.BL.servedApproach, if available.
(8)	note	Annotations 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 E /wiki/spaces/CGWIP/pages/309363178, 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 = ("SSM.BL.designator (1)" | "GSS.BL.name (2)") ((["SSE.BL.Area.operationalStatus (3)"] ["SSE.BL.SatelliteApproachOperation.operationalStatus (4)"] ["GSS.BL.NavaidOperationalStatus (5)"]) | " : New NOTAM to follow (11)").

Reference

Rule

(11)

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”.

Browser not supported