/
[AIXM-532] Direct associations between certain services and RouteSegment

[AIXM-532] Direct associations between certain services and RouteSegment

Owned by georgiana.andrei04
Last updated: 2024 Aug 20 by ADAM STYLES

ID:

AIXM-531

target version:

AIXM 5.2

version:

1.0

last updated:

08 AUG 2022

status:

APPROVED


Description

Direct associations are added from InformationService, AirTrafficControlService, AirTrafficManagementService, and SearchAndRescueService towards RouteSegment.

Rationale for change

See https://aixmccb.atlassian.net/browse/AIXM-378

In the AIXM 5.1, the relation between a Route and its Controlling Unit is quite complex, regarding the effective operational need for the AIP dataset in ENR 3.X: "Remarks, including an indication of the controlling unit and its operating frequency." (ENR 3.X, "Remarks'' column). Moreover, there is no direct relation between a RouteSegment and its Controlling Unit, knowing that all the RouteSegments of a Route won't always have the same Controlling Unit.

A processing must be done to relate a RoutePortion object (associated to a Route) with a RouteSegment, in order to provide the AIP information.

In order to simplify this situation, it is proposed to add a direct n..1 relation from a subset of concrete Service types to one or more RouteSegment.

Impact assessment

[FWD_1:1] No data mapping is necessary 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.

Change Proposal details

In the UML model, add a new association as follows:

  • InformationService ‘isLocatedAt’ RouteSegment
    • .* on the InformationService side,
    • .* on the RouteSegment side, “clientRouteSegment” role name, definition = “The route segment for which the information is provided.”
  • AirTrafficManagementService ‘manages’ RouteSegment
    • .* on the AirTrafficManagementService side,
    • .* on the RouteSegment side, “clientRouteSegment” role name, definition = “The route segment for which the flight planning and air traffic flow management services is provided.”
  • AirTrafficControlService ‘controls’ RouteSegment
    • .* on the AirTrafficControlService side,
    • .* on the RouteSegment side, “clientRouteSegment” role name, definition = “The route segment for which the air traffic control is provided.”
  • SearchRescueService ‘services’ RouteSegment
    • .* on the SearchRescueService side,
    • .* on the RouteSegment side, “clientRouteSegment” role name, definition = “The route segment where the search and rescue service is provided.”

The following UML class diagram indicates the new associations:


Mapping AIXM 5.1.1 to AIXM 5.2 (forward)

Not applicable

Mapping AIXM 5.2 to AIXM 5.1.1 (backward)

The following algorithm shall be applied:

  • [MAPC-00] For each clientSegment child element of a InformationService, AirTrafficManagementService, AirTrafficControlService or SearchRescueService element:
    • retrieve the RouteSegment referenced through the xlink:href value of the clientSegment and then add a clientRoute child element with
      • xlink:href value equal to the RouteSegment.routeFormed.xlink:href value
      • EnRouteSegmentPoint.pointChoice_….xlink:href value value equal to the RouteSegment.start.EnRouteSegmentPoint.pointChoice_….xlink:href value
      • EnRouteSegmentPoint.pointChoice_….xlink:href value value equal to the RouteSegment.end.EnRouteSegmentPoint.pointChoice_….xlink:href value
    • remove the clientSegment element.

Mapping example

(Note: for mapping test data see: https://github.com/aixm/mapping_52_511/tree/master/AIXM-xxx) 

AIXM InputAIXM Output