ID: | AIXM-504 |
target version: | AIXM 5.2 |
version: | 1.0 |
last updated: | 05 AUG 2021 |
status: | PROPOSED |
An attribute to indicate if an instrument approach procedure is used for close simultaneous approaches on close parallel runways is added in the InstrumentApproachProcedure class. Additional coded values are added in the CodeServiceATCType, CodeAirspaceType and CodeRuleProceduteTitleType in order to support the coding of information related to simultaneous close parallel approaches and the runway monitoring service.
See https://aixmccb.atlassian.net/browse/AIXM-485
The current model is missing the possibility to indicate if an instrument approach procedure is used for simultaneous operations on parallel (near-parallel) runways. It is also not possible to code information about the monitoring of the protection areas associated with such procedures - the Normal operating zone (NOZ) and No transgression zone (NTZ).
This requires an additional property in the InstrumentApproachProcedure and additional coded values for the data types used to identify ATC service types and Airspace types. In addition, in order to allow identifying the textual information about close parallel approach procedures, the list of values of the RulesProcedures class needs to be complemented with specific values related to such operations.
[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_LOSS] Data mapping is possible, but some data would be lost (or converted into Notes) 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.
In the UML model:
The following UML class diagram shows the new properties and coded values:
The following algorithm is proposed for the respective Change Proposal details:
1. [MAPC-01] - For each AirTrafficControlService.type that has value of ”OTHER:PRM”
2. [MAPC-01] - For each RulesProcedures.category that has value of: ”OTHER:INDEPENDENT_PARALLEL_APPROACHES”,
For each RulesProcedures.category that has value of: ”OTHER:DEPENDENT_PARALLEL_APPROACHES”,
For each RulesProcedures.category that has value of: “OTHER:INDEPENDENT_PARALLEL_DEPARTURES”,
For each RulesProcedures.category that has value of: “OTHER:SEGREGATED_PARALLEL_OPERATIONS”
3. [MAPC-01] For each Airspace.type that has value of: “OTHER:NTZ”
For each Airspace.type that has value of: “OTHER:NOZ”
1. [MAPC-02] For each InstrumentApproachProcedure that has closeParallelApproach from the three backward mapping options applicable in this case, the first two (discard the value or use an extension) are straightforward and do not need any further details. The 3rd option (backward mapping into a Note) is detailed in order to provide a complete description of this case and its conversion option. The following mapping into Note algorithm is proposed:
2. [MAPC-01] - For each AirTrafficControlService.type that has value of ”PRM”
3. [MAPC-01] - For each RulesProcedures.category that has value of: ”INDEPENDENT_PARALLEL_APPROACHES”,
For each RulesProcedures.category that has value of: ”DEPENDENT_PARALLEL_APPROACHES”,
For each RulesProcedures.category that has value of: “INDEPENDENT_PARALLEL_DEPARTURES”,
For each RulesProcedures.category that has value of: “SEGREGATED_PARALLEL_OPERATIONS”
4. [MAPC-01] For each Airspace.type that has value of: “NTZ”
For each Airspace.type that has value of: “NOZ”
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) | ||
---|---|---|---|
|
|