DSNA: the French air navigation service provider
ENAV; the Italian air navigation service provider
This Service is part of Coflight Cloud Services (CCS), which are primarily designed to support the Virtual Centre concept. As such, these CCS Services support the interactions between the CCS ATM Data Service Provider (ADSP) and Virtual Centre Air Traffic Service Units (ATSUs). The CCS FlightDataManagement service is consistent with the other CCS services. It addresses the CWP manual interactions for managing Flight Plan updates related to inputs made by the controller or by the Flight Data Operator:
- The CWP can request several functions of this service to process controller inputs related to Initial Flight Plan Data.
- The CWP can request another functions of this service to process controller's instructions that modifies Flight Plan Data.
- The FDO position can request the correction of AFTN messages.
- The CWP will receive a reply when the service request has been completed, indicating the status of the request. This version of the service is intended to be used in 'test mission', which aims at providing services and support to the Customer(s) to enable them to test any version of their ATM system during development. Please note that the use of CCS FlightDataManagement service implies the use of CCS FlightDataDistribution Service to get the output Flight Plan Data.
DSNA: the French air navigation service provider
ENAV; the Italian air navigation service provider
CCS FlightDataManagement Service addresses the CWP manual interactions for managing Flight Plan updates related to inputs made by the controller or by the Flight Data Operator. It addresses operations related to:
- the System Flight Plan Data: Create, Cancel, Delete, Retrieve, Create Abbreviated and Non tactical modifications,
- to ATC Instructions: Holding, Heading, Speed, CFL, ROCD, EFL, XFL, DirectTo, ClearedTo, RFL and ECL,
- the correction of erroneous AFTN messages,
- WhatIf: Accept/Reject and Open/Close.
Note: in this version of the document, CCS FDM contains all the operations listed above except those related to WhatIf.
This Service Interface encompasses the different operations performed by the ATCO and modifying the Flight Plan Data. These operations can be divided in two sets of operations: the tactical instructions and the system inputs performed to modify the planed route:
- ATC tactical Instructions: Holding, Heading, Speed, Cleared Flight Level (CFL),Rate Of climb/Descend (ROCD), Direct To and Cleared To,
- System inputs: entry FL (EFL), exit FL (XFL), enCruiseFL (ECL) and requested Flight Level (RFL).
Operation to process the input of a Cleared Flight Level given the flight identifier and the value of the level to be applied.
Operation to process the input of a direct instruction given the flight identifier and the target point of the direct (not overflown point already belonging to the route).
Operation to process the input of a heading clearance. The input shall contain the flight identifier and the assigned heading.
Operation to process the modification of a route portion for a specified flight.
Operation to process the input of a speed clearance.
Operation to process the input of the Entry Flight Level used for coordination between two logical positions
Operation to process the input of the Exit Flight Level used for coordination between two logical positions
Operation to process the input of an En-Route cruise level (ATC planning constraint) given the flight identifier and the value of the level to be applied
Operation to process the input of a Requested Flight Level given the flight identifier and the value of the level to be applied
Operation to process the input of an ROCD (Rate Of Climb or Descent) instruction.
Operation to process the input of a holding clearance.
This operation has been identified as stretched objective in the context of CCS Program. For this reason it has not implemented at Software level, despite it is defined at SSD and protobuf ones.
This Service Interface encompasses the different operations performed by the ATCO and modifying the Flight Plan Data: tactical instructions and system inputs performed to modify the planed route.
Operation to process the input of a manual SFPL cancellation.
Operation to process the creation of an abbreviated SFPL.
Operation to process the creation of a full SFPL whatever is the type of flight (OAT/GAT, VFR/IFR), according to the given initial FP fields.
Operation to process the deletion of a specified Flight Plan from ADSP
Operation to process the modification of one or several SFPL fields.
Operation to process an SFPL(s) consultation request.
This operation has been identified as stretched objective in the context of CCS Program. For this reason it has not implemented at Software level, despite it is defined at SSD and protobuf ones.
The AFTNCorrectionManagementProvider Service Interface manages the operations performed by the FDO to correct erroneous AFTN messages concerning in-coming flight plan that cannot be processed automatically by the system. It covers the following cases:
- AFTN Modification messages: CHG (ICAO format), ICHG (ADEXP format). In this case, it may be necessary to associate a FP to these messages to be able to correct them successfully.
- AFTN Creation messages: FPL (ICAO format), IFPL (ADEXP format).
This operation allows the operator to correct the erroneous fields upon the reception of a CHG or ICHG message.
This function allows the operator to correct the erroneous fields upon the reception of an FPL or IFPL message.
Service Description Document (SDD) from PJ.16-03 on which the CCS Service is based
Protobuf files describing the exchanged information
Complete service specification