[AIXM-531] Add possibility to indicate ‘EXTENDED’/’UPGRADED’ in operationalStatus

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

[FWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (A) that uses AIXM 5.1.1 for output towards a system (B) that uses AIXM 5.2 for input.

[BWD_MAP_1:1] Data mapping is possible and no data loss occurs when data is exchanged from a system (B) that uses AIXM 5.2 for output towards a system (A) that uses AIXM 5.1.1 for input.

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)