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.
Operations
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..
Allows the operator to make a segment regression.
It turns a controlled segment from live or pending status into monitored status
The system keeps the segment in monitored state until a notification or activation message is received.
The input shall contain the flight identifier, the segment identifier and optionally the segment entry time (estimated time over the segment entry point).
When filled, the segment entry time adjusts the time estimates over the trajectory points.
Caveat: The operation name (coming from SESAR) is misleading in CCS context..
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.