FlightPlanDataManagement

The Flight Plan Data Management service supports any connecting CWP client to send certain inputs in order to trigger the correct & latest up-to-date controller information, more specifically: • Create ASPL or SFPL, • Modify an ASPL/SFPL or upgrade an SFPL, • Downgrade an SFPL into an ASPL, • Delete an existing ASPL/SFPL, • Submit requests about instructions/clearances given to the flight crew (e.g. DCT, CFL, NFL, speed, heading, …) • Change status information regarding the flight’s airframe (e.g. no FSSA, RVSM status, …) • Etc. When an input is made and successfully processed the response to the request is delivered in two parts: • Each input is first replied with the AcknowledgementMessage to indicate the acceptance or rejection of the request. The client is expected to start an internal timer in order to capture those cases where there would be no reply. In case of the latter, the client is expected to trigger a new input. • Secondly, provided the input was accepted, the updated information (as delivered by the Flight Plan Distribution service) on the flight is sent. As such, subscription to the Flight Plan Distribution service is mandatory prior the user requesting flight data modifications.

Operations

The operation allows to:
• Create ASPL or SFPL,
• Modify an ASPL/SFPL,
• Upgrade an ASPL into SFPL,
• Downgrade an SFPL into an ASPL.

The operation allows modifying:
• number of aircraft related to a flight plan
• aircraft type
• flight’s wake-turbulence category
• flight’s deviation status
• RVSM capability
• 8.33 kHz capability
• UHF equipment
• BRNAV/PRNAV equipment
• ModeS capability
• Number of people on board
• FSSA capability
• Avoiding weather indicator
• Fuel dumping indicator

The operation allows to:
• Modify the callsign of an existing ASPL or SFPL.

The operation allows to manually deleting an existing ASPL or SFPL from the system.

From an operational perspective, a DCT action can represent multiple cases. The interface definition has been considered to fulfil the op-erational scenarios listed below. For completeness reasons the required options to be passed in the RequestDCT input are given below:
• DCT to a (intermediate) Point
o to
Allows the sending of a single route point name (or coordinate) with optional intermediate point. In this case, the MSB-CB will automatically determine the most likely type of DCT instruction given (i.e. make the distinction between “to-original-route” and “to-trajectory” as given below). From an interface and client implementation perspective this option allows to perform DCT actions without the requirement for the client to reference to index in the trajectory. Also, this option allows also performing a DCT instruction for an ASPL for which no trajectory is available.
• DCT to Point on the Trajectory (Uplink = UM74)
o to-trajectory
 intermediate-point not sent
 end-point represents the index point and posi-tion in the trajectory
• DCT to Point on the Original Route (Uplink = UM74 + UM72)
o to-original-route
 intermediate-point not sent
 end-point represents the point name (located on the original route)
• DCT to (Intermediate) Point not located on the trajectory; in this case the end-point is on the trajectory (Uplink = UM79: "CLEARED TO [end-point] VIA [intermediate-point])
o to-trajectory
 intermediate-point represents the route point name or position of the intermediate point
 end-point represents the index point and posi-tion in the trajectory
• DCT to (Intermediate) Point not located on the trajectory; in this case the end-point is on the original route (Uplink = UM79: "CLEARED TO [end-point] VIA [intermediate-point] + UM72)
o to-original-route
 intermediate-point represents the route point name or position of the intermediate point
 end-point represents the point name (located on the original route)
• DCT to (Intermediate) Point not located on the trajectory, and no end-point specified. In this case, the DCT is considered to be a point completely off-route, which is not to be rejoined. A typical example is a DCT to a point outside the AoI, which is not located on the trajectory (Uplink = UM74).
o to-trajectory
 intermediate-point represents the route point name or position of the intermediate point
 end-point represents the null index point
Note 1: A current heading restriction will be removed upon receiving a DCT input.
Note 2: For ASPLs, a DCT to an Intermediate OR End Point is allowed (with whatever DctData option) provided any reference to a trajectory point is populated with the null-TrajectoryPointNumber. Inputs combining both Intermediate AND End Point will not be processed.

From an operational perspective, a change route action represents a re-routing of the flight across multiple waypoints (unlike a DCT where the flight is instructed to go to only one waypoint).
Note 1: A current heading restriction will be removed upon receiving Operation changeRoute.
Note 2: Only available for SFPLs.

The interface definition has been compiled taking into account the operational cases listed below. For completeness reasons the possible parameters, for such situations, to be passed in the RequestHeading input are indicated as well:
• Present Heading (uplink possible)
• Assigned Heading – relative or absolute true/magnetic heading (uplink possible)
• Non-specified Heading; use track direction as heading and update trajectory with this value (no uplink possible)
• Heading to avoid weather, for example CBs; use track direction as heading an generate an observed tactical trajectory with it (no uplink possible)
In the first three cases above, the type of heading closure is mandatory in the request. The following cases have been distinguished in case the application limit and trajectory resuming point are included in the request:
• No application limit and rejoining point specified in the input: a default application limit will be applied and the trajectory will be closed based on pre-defined closure rules.
• Application limit specified as distance and rejoining point present in the request: the specified distance and rejoining-point will be applied.
• Application limit specified as “Indefinite”: the system will auto-close the trajectory at AoR exit.
In all cases, the input heading is considered as magnetic heading.

The command allows resetting a previous heading instruction for ASPLs only. In case the command is requested for an SFPL, the result will be returned with an error.

To process the input of a cleared flight level, with application time/distance and/or ROCD restriction.

To process the input of an enroute cruising level. The ECL is applied until the exit of the AoI (i.e. propagated all the way), unless the ap-plication-limit is present in the request.

To process the input of a requested flightlevel as requested by the pilot or filed by the airline company.

To process the input of a planned flight level (PFL). The PFL is best described as an ECL, but only applied until the requesting sector’s exit.

The interface definition has been compiled taking into account the operational cases listed below:
• Present speed (uplink possible)
• Assigned speed, including route point until where the speed restriction should apply (uplink possible)
• Speed range, including route point until where the speed re-striction should apply (between a lower and upper speed)
• Minimum or Maximum speed instruction, including route point until where the speed restriction should apply (uplink possible)
• Keyword, to represent a pure textual speed instruction to the ATCO (e.g. CLEAN speed) without affecting the flight’s calculat-ed profile
• Resume speed, to cancel any previous speed restriction (uplink possible)

Behaviour
Interface Binding Description

AMQP 1.0 content-type header used to specify media type values

Interface Provision Side
TI Primitive Message Exchange Pattern
Service Interface Binding
Network Interface Binding