The ATS unit providng providing service for an airspace is not part of the minimum AIP data set but required in ENR 2.1 ENR 2.1 FIR, UIR, TMA AND CTA:
...
Thus, it is considered conditional data.
In AIXM 5 does not provide a direct relationship between the Airspace and Unit feature. A Service is provided by a Unit. The Service of a certain type can then be related to an Airspace.
Service is an abstract feature which is specialised into the following classes:
- AirTrafficManagementService
A kind of service that provides flight planning and flow management operations. - SearchRescueService
The performance of distress monitoring, communication, coordination and search and rescue functions, initial medical assistance or medical evacuation, through the use of public and private resources, including cooperating aircraft, vessels and other craft and installations. - InformationService
A kind of service that consists in the provision of aeronautical, meteorological, traffic and related information to aircraft crew and other actors involved in flight operations, in flight or on the ground. - AirTrafficControlService
A kind of service that provides control and separation services to aircraft in the air.
Altough Although the AIXM model allows it, AirTrafficManagementService shall not be used as ATS Unit provding providing service for airspace, as it is not a an ATS unit.
The Unit providing the Service carries a name attribute that shall be used for the identification.
For certain specialisations of services, a relationship to the concerned AirportHeliport can be defined. This is applicable for AD 2.17 Air traffic services airspaces.
The CallSignDetail class is used to provide information about the operational identifier, by which the provider of the service is called, i.e. the callSign and the language used.
For the language, the ISO 639
shall be used. Note that in AIXM the language code is restricted to lower case and 3 characters.
...
Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | |||||
---|---|---|---|---|---|---|---|---|---|
SER-701 | If a Service has a clientAirspace that is an ATS airspace or an a special activity airspace the Unit.name of the related to the Service shall be provided. | PANS AIM | TBD |
| |||||
SER-702 | If a Service has a clientAirspace that is an ATS airspace or an special activity airspace the Service.type shall be provided. | Data consistency | TBD | ||||||
SER-703 | If a Service has a clientAirspace that is an ATS airspace or an special activity airspace the Service.callsign shall be provided. | Data consistency | TBD | ||||||
SER-704 | If a Service has a clientAirspace that is an AD 2.17/AD 3.17 airspace the Unit.airportLocation of the unit providing the service should be provided. | Data consistency | TBD | ||||||
SER-705 | If a CallSignDetail.callSign is provided, also a CallSignDetail.language shall be provided. | Data consistency | TBD | ||||||
SER-706 | For the provison provision of the CallSignDetail.language Language codes - ISO 639 shall be used. | Data harmonisation | TBD |
| |||||
SER-707 | AirTrafficManagementService shall not be used as Service in case the clientAirspace is an ATS airspace or an a special activity airspace. | Data harmonisation | TBD | ||||||
RCC-101 | RadioCommunicationChannel.frequencyTransmission and RadioCommunicationChannel.frequencyReception shall be encoded in case of two-way radio communication is provided. | Data harmonisation | TBD |
...