The ATS unit providng service for an airspace is not part of the minimum AIP data set but required in ENR 3 of PANS-AIM:
an indication of the controlling unit, its operating channel and, if applicable, its logon address, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations.
Hence in the scope of this guidelines it is considered conditional data.
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information.
| Warning | ||
|---|---|---|
| ||
In AIXM 5.1.1, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations cannot be encoded, except by using a Note. |
Thus, it is considered conditional data.
AIXM does not provide a direct relationship between Unit and RouteSegment class.
...
The type of service provided may be defined by the attribute Service.type, or it may be included in the . In addition also a Service.name, or it may be included in the Unit.name.provided.
| Info | ||||
|---|---|---|---|---|
| Which of the 3 options shall be laid down as coding rule?
| |||
Should there be rule/pattern how the names shall be compsed? Example "Amswell ACC" the Unit.name = "Amswell" or "Amswell ACC"? the Service.name = " NIL" or Also "Amswell ACC"? The Service.type = "ACS" |
The operation channel is encoded using the RadioCommunicationChannel class. The attribute frequencyTransmission and if applicable frequencyReception will carry the corresponding value and uom (see also Radio Communication Channel).
...
The linkage and protocol attribute may then be used to define the details about the logon address.
The figure below shows how the information about the controlling unit is published in an AIP:
Coding Rules for Controlling Unit
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | ||
|---|---|---|---|---|---|---|
| RTE-401 | All RouteSegments of a Route should have a related a Service provided by a Unit with the name attribute encoded. | Conditional dataPANS-AIM ENR 3 | TBD | RoutePortions have to be defined that cover all RouteSegments of a Route | ||
| RTE-402 | All RouteSegments of a Route should have a related Service that uses a RadioCommunicationChannel with the frequencyTransmission and frequencyRecption attribute encoded. | Conditional dataPANS-AIM ENR 3 | TBD | |||
| All RouteSegments of a Route should have a related Service that uses a RadioCommunicationChannel with the frequencyRecption attribute encoded, in case of a bidirectional communication. | Data consistency | Conditional dataTBD | ||||
| RTE-404 | Data link logon address should be encoded if available. | Conditional dataPANS-AIM ENR 3 | TBD | |||
| RTE-405 | If any, SATVOICE number, and any navigation, RCP and RSP specification(s) limitations should be encoded using Note. | Conditional data | TBD | PANS-AIM ENR 3 | TBD |
Coding Examples
The figure below shows how the information about the controlling unit is published in an AIP:
More examples TBD in the scope of the AIXM DONLON AIP dat set.