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
Process an SFPL(s) consultation request
Process a Cleared Flight Level instruction
Process a Direct instruction
Process a Heading instruction
Process a Holding instruction
Process a Requested Flight Level instruction
Process a Speed instruction
Process a modification of Route
Process an AFTN message correction
Process an Entry Flight Level instruction
Process an Exit Flight Level instruction
Process an ROCD instruction
Process an SFPL cancelation
Process an SFPL creation
Process an SFPL deletion
Process an SFPL update
Process an abbreviated SFPL creation
Process an en-route cruise Flight Level instruction
ATC Change Message (ICAO format, CFMU special)
ATS Data Exchange Presentation
ALTerNate (Aerodrome)
Area Of Interest
Arrival
Airway
ICAO ATS Change Message
Consolidated Logical Data Model
ICAO ATS Cancel Message
Coordination Point
Direct Routing
Departure
ICAO ATS Delay Message
Date of Flight
En-Route Cruise Level
Estimated Elapsed Time
Equipment
Estimated Time Over
Flight Notification Message
Flight Plan
Geographical
Individual ATC Modification Message
Instrument Approach Procedure
Individual ATC Flight Plan Message
Individual Arrival Message
Individual Modification Message
Individual Cancellation Message
Individual Departure Message
Individual Delay Message
Individual Flight Plan Message
Operational Air Traffic
On-Line Data Interchange
Performance Based Navigation
Requested Flight Level
Area Navigation
Rate of Climb
Supplementary Flight Level
Standard Instrument Departure
Standard Instrument Arrival
Trajectory Prediction
Ultra-High Frequency
Visual Flight Rules
Vertical Rate Climb Descent
8 LETTERS, being the 4-letter ICAO location indicator plus the 3-letter designator of the ATS unit followed by the letter X or, if applicable, the one-letter designator identifying the division of the ATS unit.
The designator(s) of the aircraft type(s) (e.g. B747).
Simple class providing an altitude value.
This class gathers all the possible parameters specifying the start (application) and end (targetEnd) of the application of an ATC Instruction.
These parameters can be specified by a point or a distance and their usage may be applicable depending on the type of ATC Instruction.
This class encompasses all the parameters related to the end of an application: time, point, duration.
The applicationEnd parameters are only applicable to CFL (routePointId), Route (routePointId), heading (point) and holding (point, absoluteTime, durationTime).
absoluteTime and durationTime are mutually exclusive.
Common class
This class encompasses all the parameters related to the start of an application: point (current position), routePoint, distance and relativeDistance.
Depending on the instructions, the applicationStart parameters can be either:
- a point and/or a distance,
or
- a routePointId,
or
- a routePointId and a relativeDistance.
Limitation CCS: the applicationStart parameters related to a time are not managed by CCS.
Type of AFTN message
Limitation CCS : ACH and APL are not applicable to Coflight.
Code describing how the boundary between two ATC volumes will be crossed.
Indicates the direction of a turn (left, right)
Enumeration indicating which equipment is available in an aircraft:
- EQUIPPED: the flight is equipped and the equipment is available for use by the flight
- NOT_EQUIPPED: the flight is not equipped or for any reason the equipment cannot be used by the flight.
- UNKNOWN: the capability is unknown.
To indicate the current status of the flight plan:
- ACTIVE: one of the internal SFPL segment is LIVE.
- TERMINATED: the flight plan status is set to TERMINATED when all internal and external SFPL segments of controlled sectors are LEFT.
- PASSIVE: when conditions to set it to ACTIVE or TERMINATED are not fulfilled.
To indicate the type of the flight plan:
- AFPL: the SFPL is an abbreviated flight plan (some ICAO basic fields only, no computed data).
- SFPL: the SFPL is a full SFPL (with all ICAO basic fields and all computed data such as profile, distribution...).
Indicates the status of the flight rules in each Route Point (VFR or IFR)
An indication of the flight rules which are applicable:
- IFR if ICAO rule is I
- VFR if ICAO rule is V
- IFR_FIRST if ICAO rule is Y
- VFR_FIRST if ICAO rule is Z
Flight category according to ICAO:
- SCHEDULED: if ICAO type is S (scheduled air transport)
- NOT_SCHEDULED: if ICAO type is N (non-scheduled air transport)
- GENERAL: if ICAO type is G (general aviation)
- MILITARY: if ICAO type is M (military flights)
- OTHER: if ICAO type is X (other flights)
Code indicating the kind of restriction associated to a flight heading ATC clearance
Enumeration which specifies the kind of heading of a clearance (absolute or relative)
Enumeration which indicates the status of a holding clearance (PLANNED_TO_HOLD, CLEARED_TO_HOLD, HOLDING, CLEARED_TO_LEAVE_HOLD)
NORMAL: Normal VRCD to use.
EXPEDITE: Expedite VRCD to use.
EMERGENCY: Emergency VRCD to use (only in descent).
Code indicating the kind of restriction associated to a flight level ATC clearance:
IMMEDIATE: this is a climb or descentCFL instruction.
WHEN_READY: this is an inputCFL instruction.
Format of the AFTN message. It can be ADEXP or ICAO
Enumeration which defines the class of a segment:
For internal segments:
CONTROLLED: Value for an internal segment corresponding to the traversal of a controlled ATSU.
REGION: Value for an internal segment corresponding to the traversal of an ATSU of the region not controlled by the system instance.
IOP: Value for an internal segment corresponding to the traversal of an ATSU of the IOP area not belonging to the region.
OLDI: Value for an internal segment corresponding to the traversal of an OLDI ATSU not belonging to the region.
AFTN: Value for an internal segment corresponding to the traversal of an AFTN ATSU not belonging to the region.
UNKNOWN: Default value.
For external segments:
CONTROLLED: Value for an external segment corresponding to the traversal (AoI) of a controlled ATSU.
NOT_CONTROLLED: Value for external segments other than CONTROLLED.
Type of a Segment:
- INTERNAL:
Traversal of an ATSU AoR by an SFPL, for one flight rule (IFR/VFR) and one flight type (OAT/GAT) applicable in the traversal.
- EXTERNAL:
- Traversal of an ATSU AoI by an SFPL that does not enter the AoR, for one flight rule (IFR/VFR) and one flight type (OAT/GAT) applicable in the traversal.
- Traversal of a military (resp. civil) ATSU AoI by a GAT (resp. OAT) flight.
The state value of a segment.
For internal segments:
- MONITORED: default value: the controlled segment is created.
- PENDING: the notification phase has been started for this controlled segment of the SFPL.
- LIVE: the coordination phase has been started for this controlled segment of the SFPL.
- LEFT: the transition to LEFT segment state occurs a delay (off-line predefined) after the flight has left the AOI of the controlled ATSU.
-NONE: this is the fixed value of all internal SFPL segments which are not controlled by the system instance (i.e. all internal segments which class is REGION, IOP, OLDI, AFTN or UNKNOWN).
For external segments:
- PENDING: default value: controlled external segment created
- LIVE: the flight is detected inside the controlled external segment AOI
- LEFT: the transition to LEFT segment state occurs a delay (off-line predefined) after the flight has left the AOI of the controlled ATSU.
- NONE: this is the fixed value of all external SFPL segments which are not controlled by the system instance (i.e. all external segment which class is NOT_CONTROLLED).
Code indicating the kind of restriction associated to a flight speed ATC clearance
Limitation CCS: the following values are not handled: DUAL_ASSIGNED, DUAL_MAXIMUM, DUAL_MINIMUM, KEYWORD, NONE.
Only the following values are applicable to the speedConstraint: ASSIGNED, MAXIMUM, MINIMUM, RANGE.
Only the following values are applicable to the speed ATC instruction: ASSIGNED, MAXIMUM, MINIMUM.
Enumeration indicating the wake turbulence category of an aircraft
Generic type to address comment/description/remark attributes within a long length frame.
A measure of the distance between two points in nautical miles.
It may be used as a negative value when relevant in the context it is used.
A term designating any electronic device - including its electrical part - for use in an aircraft, including radio, automatic flight control and instrument systems.
Number indicating the Erroneous message identifier in the queue
Type supporting a date, expressed in string ("DDHHMM").
Note: The computation of the value of the associated field must take into account the current month and year.
Level value expressed in Flight Level or in altitude.
Simple class providing an FL value.
Gives information about the application of the flight heading clearance
Holding Identifier in which the flight must be hold.
Type supporting an IFPLIdentifier.
Represents the IFPS allocated unique identifier received from the NM-IFPS (expressed as a string of a fixed number of alphanumeric that consists of 2 letters followed by 8 digits).
Type of restriction.
Gives information about the application of the level clearance
Generic type to address the logical AFTN message type.
Generic string type to address a raw message or the content of a long text field (otherInformation, specificADEXPField...).
Navigation, radio communication and approach aid equipment.
The number of aircrafts (greater than 1 in case of formation flights).
String identifying a route point.
This is the identifier of an expanded route point.
String to identify a segment
Gives information about the application of the flight speed clearance
Note: only applicable to CCS FDD, not to CCS FDM.
A string indicating the SSR and ADS capability of the aircraft.
SID or STAR designator
Duration or interval in minutes. Decimal part may be used to refine precision with additional seconds.
It may be negative when representing a time to lose.
Index identifying the trajectory point in string format.
A distinguishing label, term, abbreviation or acronym used to identify the Unit.
Class used to gather the input parameters of the AFTNCorrectionManagement operations.
Class supporting the generic data for the correction of AFTN messages
Directives issued by air traffic control for the purpose of requiring a pilot to take a specific action.
This class represents some Basic FP Information relevant for some FlightDataManagement operations.
Coordination point data.
To process the input of a manual SFPL cancellation (the SFPL is set to TERMINATED state. It will be removed automatically a defined time after its end).
To process the input of a Cleared Flight Level given a FP identification and the value of the level.
Cleared information related to a ROCD
Instruction to proceed via the specified route.
Class used to gather the input parameters of the operation requestRetrieveSFPL.
Class used to gather the input parameters of the operation correctAFTNChange which allows to correct the erroneous fields upon the reception of a CHG or ICHG message.
Class used to gather the input parameters of the operation correctAFTNFlightPlan which allows to correct the erroneous fields upon the reception of an FPL or IFPL message.
Class used to gather the input parameters of the operation requestCreateAbbreviatedSFPL.
Class used to gather the input parameters of the operation requestCreateSFPL.
To process the deletion of a specified Flight Plan from both CWP and ADSP. Hence, the deleted FP will not be available for retrieval
Class containing alternative destination aerodrome
EnRouteCruiseLevel is the planned FL agreed by the controller, which is mainly used during the Flight.
Controller EFL input is used to change the coordination level for the transfer from the previous responsibility.
Controller XFL input is used to change the coordination level for the transfer to the next responsibility
Technical class
Message definition of the operation corresponding to the same class name.
Specialisation of the common RequestReport.
Every input made by a controller should support:
- The identification of the controller
- The identification of the flight the controller wants to operate on
Specialisation of the common RequestReport.
Instruction to fly on the specified heading.
Instruction to enter a holding pattern with the published characteristics at the specified position and level.
Notes:
- In CCS when the holdingStatus is not clearedToLeaveHold : the parameters holdingVolumeIdentifier and applicationStart.point (entryPoint) are mandatory.
- When the holdingStatus is clearedToLeaveHold, only the flightIdentifier is processed (the other holding parameters are ignored by CCS).
Class used to gather the input parameters of some FlightDataManagement operations. It extends BasicFlightPlanInfo class, whose data is also used by the operations requiring FlightPlanInfo attributes as input parameters.
Manual Assigned Speed Input: Assign speed instruction.
The parameters assignedSpeed, maximumSpeed and minimumSpeed are mutually exclusive.
Note: the controller cannot input a speed range (min and max at the same time).
Class used to gather the input parameters of the operation requestNonTacticalModification.
Instruction to proceed directly to the specified position
The flight's cleared rate of climb or rate of descend.
The assignedROCD, maximumROCD and minimumROCD are mutually exclusive.
Note: the controller cannot input an ROCD range (min and max at the same time).
Class including the addressee of an AFTN message
Class supporting the input of a requestedFlightLevel to be applied on an indicated application point.
Technical class
SFPL data summary provided to the requester for each found flight:
Callsign, aircraft type, ADEP, ADES, take-off time...
Technical class
SFPL segment data summary for a flight
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
Protocol buffer
CCS_flightDataManagement.proto 4.0.0.0
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..
For security reasons, the adresses will be communicated only to Customers
Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.
The detailed behavior of the service is provided in each operation dedicated section
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 an SFPL(s) consultation request..
Operation to process the modification of one or several SFPL fields.
The input shall contain the flight identifier, the originator and at least a field to modify.
The fields that can be modified through this operation are related to static SFPL information (information of the SFPL independent of the modifications triggered by tactical instructions) such as: callsign aircraftIdentification (F7a), departureAerodromeDesignator (F13a), destinationAerodromeDesignator (F16a), flightType (F8b), flightRules (F8a), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), equipment status (F81), estimatedOffBlockTime (F13b), requestedFlightLevel (F15b), icaoRoute, enRouteCruiseSpeed (TAS or Mach) (F15a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), ssrCodeData, otherInformation (F18), supplementaryInformation (F19), sidDesignator, starDesignator.
.
For security reasons, the adresses will be communicated only to Customers
Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.
The detailed behavior of the service is provided in each operation dedicated section
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. .
For security reasons, the adresses will be communicated only to Customers
Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler.
The detailed behavior of the service is provided in each operation dedicated section