[2.0] [STAND.CLS] Aircraft stand - closure (NOTAM)

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 AST.BL indicates that the corresponding data item must be taken from the AircraftStand BASELINE;
the abbreviation AHP.BL indicates that the corresponding data item must be taken from the AirportHeliport BASELINE associated with the Apron that is associated with the ApronElement that is associated with the AircraftStand(s) concerned;
the abbreviation AST.TD indicates that the corresponding data item must be taken from one of the AircraftStand TEMPDELTA that were created for the Event.
- Note: According to encoding rule APN.CLS.02, several AircraftStand features, as affected by the closure, will have a TEMPDELTA encoded. However, the closure information will be identical for all these AircraftStand(s). Therefore, the STD.TD referred in the NOTAM production rules below can be any of these.

In general, the ICAO DOC 8126 and the OPADD rules shall be followed. These have not been copied in this document in order to avoid duplication with those documents. Only instructions that are specific to the AIXM encoding of this event are stated here.

- 1.1 Item Q
  - 1.1.1 Q code
  - 1.1.2 Scope
  - 1.1.3 Lower limit / Upper limit
  - 1.1.4 Geographical reference
- 1.2 Items B, C and D
- 1.3 Item E
- 1.4 Items F & G
2 Event Update

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

Insert: QMPLC

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 following the common production rules.

If at least one AST.TD.availability.ApronAreaAvailability.timeInterval exists (i.e. the Event has an associated schedule), then all such Timesheet(s) shall be represented 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:

EBNF Code

template = ["(1)" "AHP.BL.type (2)" ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] \n "Acft stand" "AST.BL.designator" ["(4)" ("and"|",")]{"AST.BL.designator" ["(4)" ("and"|",")]} "closed" [ "due to" "AST.TD.availability.annotation (5)"] \n \n
{"\n" "AST.TD.availability.annotation(6)" "."} ["."].

Reference	Data item (from encoding scenario)	Rule

Reference

Data item (from encoding scenario)

Rule

(1)

If AHP.BL.locationIndicatorICAO is not null, then ignore this branch.

(2)

Insert here the type of the airport decoded as follows

AHP.BL.type	Text to be inserted in Item E
AD or AH	"AD"
HP	"Heliport"
LS or OTHER	"Landing site"

(3)

(a) If AHP.BL.name is not NIL, then insert it here. (b) Otherwise insert here the text "located at" followed by the AHP.BL.ARP.ElevatedPoint decoded according to the text NOTAM production rules for aixm:Point.

(4)

aircraft stand designator

If more than one AircraftStand has a TEMPDELTA associated with the Event, then insert the designator of each additional AircraftStand preceded by ",". The word "Acft stand" need not be repeated. Insert "and" before the last entry.

(5)

closure reason

If there exists a AST.TD.availability.ApronAreaAvailability.annotation having propertyName='operationalStatus' and purpose='REMARK', then translate it into free text according to the decoding rules for annotations.

(6)

note

Annotations of AST.TD.ApronAreaAvailability shall be translated into free text according to the decoding rules for annotations.

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 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 NOTAMC

If a NOTAMC 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 Code

template_cancel = "AHP.BLtype (1)" ["(2)"  ("AHP.BL.name (3a)" | "AHP.BL.ARP (3b)")] "Acft stand" "AST.BL.name" ["(4)" ("and"|",")]{"AST.BL.name" ["(4)" ("and"|",")]} ("resumed normal operations." | " : New NOTAM to follow.(7)").

Reference

Rule

(7)

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