ID: | AIXM-531 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 08 AUG 2022 |
status: | APPROVED |
Description
Additional status value is added to CodeStatusServiceBaseType and CodeStatusAirportBaseType
Rationale for change
See https://aixmccb.atlassian.net/browse/AIXM-527
It was identified that there exist situations when an operationalStatus of e.g. service or availability may be 'upgraded' or 'extended' based on the dynamically changing situation (RFFS category upgraded to allow for larger aircrafts' operations, extended HO of AirportHeliport on top of the normal HO etc. announced by NOTAM)
Current list of values used in data types CodeStatusServiceType and CodeStatusAirportType only allow to indicate NORMAL, LIMITED or CLOSED/UNSERVICEABLE status. To allow for addressing the upgraded status value 'UPGRADED' is added to CodeStatusServiceBaseType and 'EXTENDED' to CodeStatusAirportBaseType.
Impact assessment
There is no impact on existing implementations as the current AIXM 5.1.(.1) data remains fully valid against AIXM 5.2. No values are removed from this list.
When receiving data from AIXM 5.2 implementations, current AIXM 5.1(.1) systems will be able to map back the new values into OTHER:... values, as described in the mapping rules further in this document.
Change Proposal details
In the UML model:
- In the data type CodeStatusServiceBaseType add following value:
- UPGRADED, type = string, definition = “Extended/upgraded operations.”
- In the data type CodeStatusAirportBaseType add following value:
- EXTENDED, type = string, definition = “The facility operates with extended parameters.”
The following UML class diagram shows the properties that use the modified lists of values
Mapping AIXM 5.1.1 to AIXM 5.2 (forward)
[MAPC-01] The following data conversion algorithm is proposed:
- For each FireFightingService/ServiceOperationalStatus.operationalStatus that has values of ”OTHER:UPGRADED”
- Replace the value with “UPGRADED”
- For each PassengerService/ServiceOperationalStatus.operationalStatus that has values of ”OTHER:UPGRADED”
- Replace the value with “UPGRADED”
- For each AirportSuppliesService/ServiceOperationalStatus.operationalStatus that has values of ”OTHER:UPGRADED”
- Replace the value with “UPGRADED”
- For each AircraftGroundService/ServiceOperationalStatus.operationalStatus that has values of ”OTHER:UPGRADED”
- Replace the value with “UPGRADED”
- For each AirportHeliportAvailability.operationalStatus that has values of ”OTHER:EXTENDED”
- Replace the value with “EXTENDED”
- For each ApronAreaAvailability.operationalStatus that has values of ”OTHER:EXTENDED”
- Replace the value with “EXTENDED”
- For each ManoeuvringAreaAvailability.operationalStatus that has values of ”OTHER:EXTENDED”
- Replace the value with “EXTENDED”
Mapping AIXM 5.2 to AIXM 5.1.1 (backward)
[MAPC-01] The following data conversion algorithm is proposed:
- For each FireFightingService/ServiceOperationalStatus.operationalStatus that has values of “UPGRADED”
- Replace the value with ”OTHER:UPGRADED”
- For each PassengerService/ServiceOperationalStatus.operationalStatus that has values of “UPGRADED”
- Replace the value with ”OTHER:UPGRADED”
- For each AirportSuppliesService/ServiceOperationalStatus.operationalStatus that has values of “UPGRADED”
- Replace the value with ”OTHER:UPGRADED”
- For each AircraftGroundService/ServiceOperationalStatus.operationalStatus that has values of “UPGRADED”
- Replace the value with ”OTHER:UPGRADED”
- For each AirportHeliportAvailability.operationalStatus that has values of ”EXTENDED”
- Replace the value with “OTHER:EXTENDED”
- For each ApronAreaAvailability.operationalStatus that has values of ”EXTENDED”
- Replace the value with “OTHER:EXTENDED”
- For each ManoeuvringAreaAvailability.operationalStatus that has values of ”EXTENDED”
- Replace the value with “OTHER:EXTENDED”
Mapping example
(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx)
| AIXM 5.2 | AIXM 5.1(.1) |
|---|---|