{
  "informationService": {
    "descriptionInformation": {
      "abbreviations": [
        {
          "name": "AC",
          "description": "Airspace Configuration"
        },
        {
          "name": "ACC",
          "description": "Area Control Centre"
        },
        {
          "name": "ACH",
          "description": "ATC Change Message (ICAO format, CFMU special)"
        },
        {
          "name": "ADEP",
          "description": "Aerodrome of Departure"
        },
        {
          "name": "ADES",
          "description": "Aerodrome of Destination"
        },
        {
          "name": "ADEXP",
          "description": "ATS Data Exchange Presentation"
        },
        {
          "name": "ADS",
          "description": "Automatic Dependent Surveillance"
        },
        {
          "name": "ADSP",
          "description": "ATM Data Service Provider"
        },
        {
          "name": "AFTN",
          "description": "Aeronautical Fixed Telecommunication Network"
        },
        {
          "name": "ALRS",
          "description": "Alerting Service"
        },
        {
          "name": "ALTN",
          "description": "ALTerNate (Aerodrome)"
        },
        {
          "name": "AMQP",
          "description": "Advanced Message Queuing Protocol"
        },
        {
          "name": "ANSP",
          "description": "Air Navigation Service Provider"
        },
        {
          "name": "AOI",
          "description": "Area Of Interest"
        },
        {
          "name": "APL",
          "description": "Abbreviated Flight Plan"
        },
        {
          "name": "APOC",
          "description": "Airport Operator"
        },
        {
          "name": "APP",
          "description": "Approach"
        },
        {
          "name": "ARR",
          "description": "Arrival"
        },
        {
          "name": "ATC",
          "description": "Air Traffic Control"
        },
        {
          "name": "ATCO",
          "description": "Air Traffic Control Officer"
        },
        {
          "name": "ATCS",
          "description": "Air Traffic Control Services"
        },
        {
          "name": "ATFCM",
          "description": "Air Traffic Flow and Capacity Management"
        },
        {
          "name": "ATM",
          "description": "Air Traffic Management"
        },
        {
          "name": "ATS",
          "description": "Air Traffic Services"
        },
        {
          "name": "ATSU",
          "description": "Air Traffic Service Unit"
        },
        {
          "name": "AWY",
          "description": "Airway"
        },
        {
          "name": "CCS",
          "description": "Coflight Cloud Services"
        },
        {
          "name": "CFL",
          "description": "Cleared Flight Level"
        },
        {
          "name": "CHG",
          "description": "ICAO ATS Change Message"
        },
        {
          "name": "CLDM",
          "description": "Consolidated Logical Data Model"
        },
        {
          "name": "CNL",
          "description": "ICAO ATS Cancel Message"
        },
        {
          "name": "COP",
          "description": "Coordination Point"
        },
        {
          "name": "CWP",
          "description": "Controller Working Position"
        },
        {
          "name": "DCB",
          "description": "Demand and Capacity Balancing"
        },
        {
          "name": "DCT",
          "description": "Direct Routing"
        },
        {
          "name": "DEP",
          "description": "Departure"
        },
        {
          "name": "DLA",
          "description": "ICAO ATS Delay Message"
        },
        {
          "name": "DOF",
          "description": "Date of Flight"
        },
        {
          "name": "DSNA",
          "description": "Direction des Services de la Navigation A0xC3 0xA9rienne (French ANSP)"
        },
        {
          "name": "EAP",
          "description": "Extended ATC Planner"
        },
        {
          "name": "EATMA",
          "description": "European ATM Architecture"
        },
        {
          "name": "ECL",
          "description": "En-Route Cruise Level"
        },
        {
          "name": "EET",
          "description": "Estimated Elapsed Time"
        },
        {
          "name": "EFL",
          "description": "Entry Flight Level"
        },
        {
          "name": "ENAV",
          "description": "Ente Nazionale Assistenza al Volo (Italian ANSP)"
        },
        {
          "name": "EOBT",
          "description": "Estimated Off-Block Time"
        },
        {
          "name": "EQPT",
          "description": "Equipment"
        },
        {
          "name": "ETO",
          "description": "Estimated Time Over"
        },
        {
          "name": "FDD",
          "description": "Flight Data Distribution"
        },
        {
          "name": "FDM",
          "description": "Flight Data Management"
        },
        {
          "name": "FDO",
          "description": "Flight Data Operator"
        },
        {
          "name": "FDPS",
          "description": "Flight Data Processing System"
        },
        {
          "name": "FL",
          "description": "Flight Level"
        },
        {
          "name": "FNM",
          "description": "Flight Notification Message"
        },
        {
          "name": "FP",
          "description": "Flight Plan"
        },
        {
          "name": "FPL",
          "description": "Flight Plan"
        },
        {
          "name": "GAT",
          "description": "General Air Traffic"
        },
        {
          "name": "GEO",
          "description": "Geographical"
        },
        {
          "name": "HMI",
          "description": "human machine Interface"
        },
        {
          "name": "IACH",
          "description": "Individual ATC Modification Message"
        },
        {
          "name": "IAP",
          "description": "Instrument Approach Procedure"
        },
        {
          "name": "IAPL",
          "description": "Individual ATC Flight Plan Message"
        },
        {
          "name": "IARR",
          "description": "Individual Arrival Message"
        },
        {
          "name": "IAS",
          "description": "Indicated Airspeed"
        },
        {
          "name": "ICAO",
          "description": "International Civil Aviation Organization"
        },
        {
          "name": "ICD",
          "description": "Interface Control Document"
        },
        {
          "name": "ICHG",
          "description": "Individual Modification Message"
        },
        {
          "name": "ICNL",
          "description": "Individual Cancellation Message"
        },
        {
          "name": "ID",
          "description": "Identifier"
        },
        {
          "name": "IDEP",
          "description": "Individual Departure Message"
        },
        {
          "name": "IDLA",
          "description": "Individual Delay Message"
        },
        {
          "name": "IER",
          "description": "Interface Exchange Requirement"
        },
        {
          "name": "IFPL",
          "description": "Individual Flight Plan Message"
        },
        {
          "name": "IFR",
          "description": "Instrument Flight Rules"
        },
        {
          "name": "IKE",
          "description": "Internet Key Exchange"
        },
        {
          "name": "INAP",
          "description": "Integrated Network Management and ATC planning"
        },
        {
          "name": "IOP",
          "description": "Interoperability"
        },
        {
          "name": "IP",
          "description": "Internet Protocol"
        },
        {
          "name": "IPSEC",
          "description": "Internet Protocol Security protocol"
        },
        {
          "name": "IPV4",
          "description": "Internet Protocol version 4"
        },
        {
          "name": "JU",
          "description": "Joint Undertaking"
        },
        {
          "name": "KPI",
          "description": "Key Performance Indicator"
        },
        {
          "name": "LTM",
          "description": "Local Traffic Manager"
        },
        {
          "name": "MB",
          "description": "Mega byte"
        },
        {
          "name": "MEP",
          "description": "Message Exchange Pattern"
        },
        {
          "name": "MIME",
          "description": "Multipurpose Internet Mail Extensions"
        },
        {
          "name": "MSA",
          "description": "Multi-sector area"
        },
        {
          "name": "NOP",
          "description": "Network Operation Plan"
        },
        {
          "name": "NTP",
          "description": "Network Time Protocol"
        },
        {
          "name": "OAT",
          "description": "Operational Air Traffic"
        },
        {
          "name": "OCSP",
          "description": "Online Certificate Status Protocol"
        },
        {
          "name": "OE",
          "description": "Operational Entity"
        },
        {
          "name": "OLDI",
          "description": "On-Line Data Interchange"
        },
        {
          "name": "PBN",
          "description": "Performance Based Navigation"
        },
        {
          "name": "PKCS",
          "description": "Public-Key Cryptography Standards"
        },
        {
          "name": "RFL",
          "description": "Requested Flight Level"
        },
        {
          "name": "RNAV",
          "description": "Area Navigation"
        },
        {
          "name": "ROC",
          "description": "Rate of Climb"
        },
        {
          "name": "ROCD",
          "description": "Rate of Climb Descend"
        },
        {
          "name": "SDD",
          "description": "Service Definition Document"
        },
        {
          "name": "SESAR",
          "description": "Single European Sky Air Traffic Management Research"
        },
        {
          "name": "SFL",
          "description": "Supplementary Flight Level"
        },
        {
          "name": "SFPL",
          "description": "System Flight Plan"
        },
        {
          "name": "SID",
          "description": "Standard Instrument Departure "
        },
        {
          "name": "SLA",
          "description": "Service Level Agreement"
        },
        {
          "name": "SSD",
          "description": "SWIM Service Description"
        },
        {
          "name": "SSI",
          "description": "Synchronous Serial Interface"
        },
        {
          "name": "SSR",
          "description": "Secondary Surveillance Radar"
        },
        {
          "name": "STAR",
          "description": "Standard Instrument Arrival"
        },
        {
          "name": "SWIM",
          "description": "System Wide Information Management"
        },
        {
          "name": "TBC",
          "description": "To Be Confirmed"
        },
        {
          "name": "TBD",
          "description": "To Be Defined"
        },
        {
          "name": "TCP",
          "description": "Transfer Control Protocol"
        },
        {
          "name": "TI",
          "description": "Technical Infrastructure"
        },
        {
          "name": "TIP",
          "description": "Tactical Instructions Proposal message"
        },
        {
          "name": "TLS",
          "description": "transport level security"
        },
        {
          "name": "TP",
          "description": "Trajectory Prediction"
        },
        {
          "name": "UHF",
          "description": "Ultra-High Frequency"
        },
        {
          "name": "UTC",
          "description": "Coordinated Universal Time"
        },
        {
          "name": "VC",
          "description": "Virtual Centre"
        },
        {
          "name": "VFR",
          "description": "Visual Flight Rules"
        },
        {
          "name": "VRCD",
          "description": "Vertical Rate Climb Descent"
        },
        {
          "name": "XFL",
          "description": "Exit Flight Level"
        }
      ],
      "serviceDescriptionIdentification": {
        "serviceDescriptionTitle": "CCS FlightDataManagement Service Description",
        "serviceDescriptionEdition": "5.3.0.7",
        "serviceDescriptionReferenceDate": "14/06/2022"
      }
    },
    "name": "CCS FlightDataManagement",
    "serviceAbstract": "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). \r\nThe CCS FlightDataManagement service is consistent with the other CCS services.\r\nIt addresses the CWP manual interactions for managing Flight Plan updates related to inputs made by the controller or by the Flight Data Operator:  \r\n-\tThe CWP can request several functions of this service to process controller inputs related to Initial Flight Plan Data.\r\n-\tThe CWP can request another functions of this service to process controller\u0027s instructions that modifies Flight Plan Data.\r\n-\tThe FDO position can request the correction of AFTN messages.\r\n-\tThe CWP will receive a reply when the service request has been completed, indicating the status of the request.\r\n\r\nNote: Only civil flights are handled by CCS services.\r\n\r\nThis version of the service is intended to be used in \u0027test mission\u0027, which aims at providing services and support to the Customer(s) to enable them to test any version of their ATM system during development.\r\n\r\nPlease note that the use of CCS FlightDataManagement service implies the use of CCS FlightDataDistribution Service to get the output Flight Plan Data.\r\n",
    "serviceCategorisation": {
      "serviceType": "SWIM_COMPLIANT",
      "lifeCycleStage": "OPERATIONAL",
      "businessActivityType": [
        "INFORMATION_MANAGEMENT"
      ],
      "informationCategory": [
        "FLIGHT_INFORMATION_EXCHANGE"
      ],
      "intendedConsumer": [
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
      ],
      "applicationMessageExchangePattern": [
        "SYNCHRONOUS_REQUEST_REPLY"
      ]
    },
    "serviceDescriptionReferences": {
      "implementedStandard": [
        {
          "conformanceStatement": "Description of Service according to EUROCONTROL specifications",
          "description": "This specification contains requirements for describing information services in the context ofInitial System Wide Information Management (iSWIM). The requirements prescribe the minimum set of elements a service descriptionhas to contain",
          "isConformant": true,
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+documents\r\n\r\nNote: to request access to Confluence, please refer to the point of contact section.",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION",
          "title": "EUROCONTROL Specification for SWIM - Service Description ",
          "version": "2.0"
        },
        {
          "conformanceStatement": "Information definition according to EUROCONTROL specifications",
          "description": "This specification contains requirements forinformation definitions, meaning the formal descriptions of exchanged information, in the context of Initial System Wide Information Management (iSWIM). This contributes to semantic interoperability of information. ",
          "isConformant": true,
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+documents\r\n\r\nNote: to request access to Confluence, please refer to the point of contact section.",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION",
          "title": "EUROCONTROL Specification for SWIM - Information Definition",
          "version": "1.0"
        },
        {
          "conformanceStatement": "Implementation of service and network bindings",
          "description": "This specification contains requirements for system interfaces (e.g. protocols) and for IT infrastructure capabilities required to enable a reliable, secure and efficient exchange of information in the context of Initial System Wide Information Management (iSWIM).This contributes to technical interoperability",
          "isConformant": true,
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+documents\r\n\r\nNote: to request access to Confluence, please refer to the point of contact section.",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE",
          "title": "EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile",
          "version": "1.0"
        }
      ],
      "serviceDocument": [
        {
          "description": "AIRM traceability for CCS Flight Data Management service payload",
          "documentType": "AIRM_TRACE",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Management+Service \nNote: to request access to Confluence, please refer to the point of contact section",
          "title": "CCS AIRM mapping FDM service",
          "version": "1.0"
        },
        {
          "description": "Validation evidence for CCS Flight Data Management service",
          "documentType": "SERVICE_VALIDATION_REPORT",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Management+Service \nNote: to request access to Confluence, please refer to the point of contact section",
          "title": "CCS Validation evidence document - FlightDataManagement",
          "version": "1.0"
        },
        {
          "description": "Protobuf files describing the exchanged information",
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Management+Service",
          "title": "CCS_flightDataManagement.proto",
          "version": "5.1.0.4"
        },
        {
          "description": "Protobuf file describing the exchanged information common to two or more CCS Services",
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Management+Service",
          "title": "CCS_common.proto",
          "version": "5.5.1.2"
        },
        {
          "description": "Protobuf file describing the metadata used by the CCS Services",
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+Documents",
          "title": "metadata.proto",
          "version": "v1.2.0.0"
        },
        {
          "description": "Complete service specification",
          "documentType": "SERVICE_SPECIFICATION",
		  "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/CCS+Flight+Data+Management+Service",
          "title": "CCS FlightDataManagement Service Description",
          "version": "5.3.0.7"
        },
        {
          "description": "Document that includes the list of all applicable error messages for CCS services",
          "documentType": "SERVICE_SPECIFICATION",
          "reference": "https://confluenceccs.se-dmf.eu/display/CDFSR/Applicable+Documents",
          "title": "CCS Errors Management Document",
          "version": "2.0"
        }
      ]
    },
    "serviceProvision": {
      "dateInOperation": "2021-07-01",
      "provider": "DSNA\u0026ENAV",
      "providerDescription": "DSNA (Direction des Services de la Navigation Aerienne) is the national air navigation services provider of France. DSNA is entrusted with the provision of air traffic services, associated communication, navigation and surveillance services and aeronautical information services in all airspace under French responsibility and at designated airports. DSNA is member of A6, FABEC and SESAR JU.\r\nParis ACC : At the crossroads of the biggest European platforms, Paris ACC manage one of the most dense airspace in Europe. Paris ACC act to develop Paris airports capacity. The traffic handled by Paris ACC consists of 72% of flights departing or arriving at Parisian airports. With its 1.3 million controlled flights in 2018, Paris ACC is one the most important ACC in Europe.\r\n\r\nENAV S.p.A. (ENAV) is the Italian AIR Navigation Service Provider \r\nENAV\u0027s core business is to manage the regulated Air Traffic Control Services (ATCS), for which it is entrusted, allowing aircraft to fly within the assigned airspace with constantly enhanced levels of safety, optimizing the effectiveness of the service provided and the efficiency of the company",
      "providerType": [
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
      ],
      "pointOfContact": [
        {
          "name": "Andrea Quaresima",
          "description": "CCS Collaborative tools administrator - To request access to the CCS documentation",
          "email": "andrea.quaresima@enav.it",
          "phoneNumber": ""
        },
        {
          "name": "Guillaume Ramonet",
          "description": "Coflight Cloud Services Program Director - To request access to the CCS service",
          "email": "Guillaume.Ramonet@aviation-civile.gouv.fr",
          "phoneNumber": ""
        },
        {
          "name": "Service Desk",
          "description": "For Incidents on services in operation, contact the Service desk [working hours/opening days] as described in the related support service (incident management) supplied by CCS provider to CCS customer during the procurement phase\r\n",
          "email": "",
          "phoneNumber": ""
        }
      ]
    },
    "serviceGeneralDescription": {
      "operationalNeed": [
        {
          "name": " 1 General operational need",
          "description": "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.\r\nIt addresses operations related to:\r\n-\tthe System Flight Plan Data: Create, Cancel, Delete, Retrieve, Create Abbreviated, Non tactical modifications and Segment regression, \r\n-\tto ATC Instructions: Holding, Heading, Speed, CFL, ROCD, EFL, XFL, DirectTo, ClearedTo, RFL and ECL,\r\n-\tthe correction of erroneous AFTN messages,\t\r\n-\tWhatIf: Accept/Reject and Open/Close.\r\n\r\nNote: in this version of the document, CCS FDM contains all the operations listed above except those related to WhatIf.\r\n"
        }
      ],
      "functionality": [
        {
          "name": "Process a Cleared Flight Level instruction",
          "description": "Process a Cleared Flight Level instruction",
          "realWorldEffect": "The trajectory of the flight is updated accordingly."
        },
        {
          "name": "Process a Direct instruction",
          "description": "Process a Direct instruction",
          "realWorldEffect": "The trajectory of the flight is updated with the direct clearance."
        },
        {
          "name": "Process an en-route cruise Flight Level instruction",
          "description": "Process an en-route cruise Flight Level instruction",
          "realWorldEffect": "The trajectory of the flight is updated accordingly."
        },
        {
          "name": "Process an Entry Flight Level instruction",
          "description": "Process an Entry Flight Level instruction",
          "realWorldEffect": "The Exit Flight Level related to the concerned coordination is updated and the trajectory of the flight is updated."
        },
        {
          "name": "Process an Exit Flight Level instruction",
          "description": "Process an Exit Flight Level instruction",
          "realWorldEffect": "The Exit Flight Level related to the concerned coordination is updated and the trajectory of the flight is updated."
        },
        {
          "name": "Process a Heading instruction",
          "description": "Process a Heading instruction",
          "realWorldEffect": "The trajectory of the flight is updated with the heading clearance."
        },
        {
          "name": "Process a Holding instruction",
          "description": "Process a Holding instruction",
          "realWorldEffect": "The trajectory of the flight is updated with the holding clearance."
        },
        {
          "name": "Process a modification of Route",
          "description": "Process a modification of Route",
          "realWorldEffect": "The route and the trajectory of the flight are updated with the route amendment."
        },
        {
          "name": "Process a Requested Flight Level instruction",
          "description": "Process a Requested Flight Level instruction",
          "realWorldEffect": "The trajectory of the flight is updated accordingly."
        },
        {
          "name": "Process an ROCD instruction",
          "description": "Process an ROCD instruction",
          "realWorldEffect": "The trajectory of the flight is updated with the ROCD clearance."
        },
        {
          "name": "Process a Speed instruction",
          "description": "Process a Speed instruction",
          "realWorldEffect": "The trajectory of the flight is updated with the speed clearance."
        },
        {
          "name": "Process an abbreviated SFPL creation ",
          "description": "Process an abbreviated SFPL creation ",
          "realWorldEffect": "The APL is created."
        },
        {
          "name": "Process an SFPL cancelation",
          "description": "Process an SFPL cancelation",
          "realWorldEffect": "The SFPL status is set to TERMINATED."
        },
        {
          "name": "Process an SFPL creation",
          "description": "Process an SFPL creation",
          "realWorldEffect": "The SFPL is created in CCS."
        },
        {
          "name": "Process an SFPL deletion",
          "description": "Process an SFPL deletion",
          "realWorldEffect": "The SFPL is deleted from CCS."
        },
        {
          "name": "Process an SFPL update",
          "description": "Process an SFPL update",
          "realWorldEffect": "The impacted SFPL fields are updated in CCS."
        },
        {
          "name": "Process an SFPL(s) consultation request",
          "description": "Process an SFPL(s) consultation request",
          "realWorldEffect": "A summary of the SFPL(s) matching the given criteria are provided to the requestor."
        },
        {
          "name": "Process an AFTN message correction",
          "description": "Process an AFTN message correction",
          "realWorldEffect": "The corrected message is sent to the system for processing."
        },
        {
          "name": "Process an SFPL segment regression",
          "description": "Process an SFPL segment regression",
          "realWorldEffect": "The SFPL segment is turned from live or pending into monitored status."
        }
      ],
      "accessAndUseCondition": [
        {
          "description": "\u003cbold\u003eIPR\u003c/bold\u003e\r\nIn accordance with their internal contractual rules on IPRs, DSNA, ENAV and skyguide retain exclusive ownership of the information contained in this document, which is to be deemed as foreground of the Coflight Cloud Services project (aiming at delivering remote flight data processing).\r\n\r\n\u003cbold\u003eAccess to the Service\u003c/bold\u003e\r\nThis service is provided to Service Consumers under a contractual basis signed between the CCS Service Provider and the Service Consumer.",
          "name": "Information ownership",
          "type": "LEGAL_CONSTRAINT"
        },
        {
          "description": "If the service consumer also consumes other CCS services, this Service shall be consumed simultaneously with the other CCS SWIM Services that are part of the contractual agreement between the service consumer and CCS service provider.",
          "name": "Dependencies with other CCS Services",
          "type": "SERVICE_CONSUMPTION_CONSTRAINT"
        },
        {
          "description": "This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities",
          "name": "Alignment to SESAR Virtual Centre activity",
          "type": "SERVICE_POLICY"
        },
        {
          "description": "Both the SWIM Service Description documents / Protobuf files and the CCS Services are versioned.\r\nThe version assigned to SSDs and to Protobuf files is composed by four digits in the form x.y.z.w.\r\nNew releases are numbered according to the following rule (compared to the previous version): \r\n-\tw increased by one: means that some content that could be ignored by the developers changed and the changes do not affect the protobuf files generation. For example, changes in the comments or in the descriptions of services, fields and data structures.\r\n-\tz increased by one: means that some content is changed by adding (but not changing or removing) some messages and/or data types. The generated protobuf files are expected to be an extension of the previous one and as result they are backward compatible.\r\n-\ty increased by one: means that the file is changed by changing or removing some operations. The generated protobuf files are not expected to be compatible with the previous one.\r\n-\tx increased by one: means that the file contains a new baseline. Major changes are expected to be present.\r\n\r\nThe service version is composed by 3 digits a.b.c assigned according to the following rule:\r\n- a could be 0,1,2 depending on the status of the service with respect to the SWIM registration phase:\r\n0: before the service application (as candidate)\r\n1: if candidate\r\n2: if compliant\r\n- b Increments if major changes have been done with respect to the previous version (modify/remove). No backward compatibility.\r\n- c Increments if minor changes have been done with respect to the previous version (addition/description modified). Full backward compatibility.\r\n",
          "name": "Service versioning",
          "type": "SERVICE_POLICY"
        },
        {
          "description": "Services management reviews are regularly organized with CCS customers to monitor the usability of the services and the KPI related to the quality of service described in the SLA.",
          "name": "KPIs monitoring",
          "type": "SERVICE_POLICY"
        },
        {
          "description": "The interface of CCS business services is accessible from outside DSNA premises through Internet using IPV4. An IPSEC link (IKE v1 or IKE v2) is used between CCS provider and CCS customer terminal network equipment.",
          "name": "Confidentiality and integrity",
          "type": "SECURITY_CONSTRAINT"
        },
        {
          "description": "The CCS provider acts as a certificate authority to provide and validate X.509 certificates. Before service operation, a package including X509 certificate and private key, will be delivered to the customer using the PKCS#12 archive file format. \r\nMutual authentication with X509 certificates is used between the AMQP broker and its client. Prior to any exchanges of AMQP Messages, the CCS customer shall establish with CCS Provider a TLS session using TLS 1.2 version. \r\n-\tCCS customer shall provide its certificates when establishing the connection. The certificates shall be valid (nor corrupted, nor revoked). The certificates of the CCS customer allow its identification for the use of the different CCS services (CCS business services at lower level).\r\n-\tThe CCS provider transmit its complete certificate during the connection phase and allow OCSP stapling to allow the CCS customer to check if it is valid or not.\r\n-\tFor the cryptographic algorithms, the authorized cipher suites must be agreed between the CCS provider and the customer based on the standards.\r\nAs an ATSU, the CCS business services customer, once identified, has access to all CCS services.\r\nIn the case of a Customer that would fail to authenticate 3 times in less than 3 minutes, the IP address would be ban and has to trigger the incident management procedure.\r\n",
          "name": "Authentication and authorisation",
          "type": "SECURITY_CONSTRAINT"
        }
      ],
      "qualityOfService": [
        {
          "name": "Services level objectives",
          "description": "The service level objectives regarding the availability, response time, throughput and recoverability of CCS Services depend on the purpose (mission) for which the Customer intend to use them (e.g. integration, test, training, operational purpose).\r\nThese service level objectives are therefore negotiated with the Customers, based on their safety analysis, and are detailed in the specific Service Level Agreement established with each CCS Customer."
        },
        {
          "name": "Network performance",
          "description": "The minimum Bandwidth required to consume CCS services (hypothesis for the technical integration service of 300 simultaneous flight managed by the system) is 10MB/s."
        },
        {
          "name": "Rate limitation",
          "description": "Customer ATSU shall restrict the overall rate of requests to a maximum of 720 request/minutes. The detailed rate limitation per services is detailed in the associated swim service description of each service."
        }
      ],
      "validation": [
        {
          "description": "Prior to any Service publication in the European SWIM Registry, CCS partners organise a joint validation that involve both CCS Providers and the first CCS Customer. \r\nTest Cases dealing with several test topics are run using a happy flow of few flights to check that the services are consistent, compliant with the actual service description and meet the acceptance criteria formulated by the first CCS Customer.\r\nAny anomaly raised by the test case execution is conveyed into the CCS bug management process. For each anomaly, a criticality level is assigned:\r\n-\tCritical: blocking issue that prevents the usage of a service functionality\r\n-\tMajor: issue that prevents the usage of a service functionality for which a workaround has been identified\r\n-\tMinor: other anomalies neither Critical nor Major \r\nDepending on the impacts, the issue is addressed to the specific team(s) in charge of the resolution (specification team, software team, dataset team...).\r\nOnce fixed, the issue is verified during one of the next validation sessions and closed if the resolution is confirmed by the validation team.\r\n\r\nIn addition to the functional validation, CCS partners also organise performance validations. The objectives of such sessions are:\r\n-\tto measure the CCS system response times according to several Key Performance Indicators (KPI) and Non-Functional Requirements (NFR) agreed among parties\r\n-\tto indicate if the KPI target values are reached or not\r\nThe following KPI are evaluated:\r\n-\tMaximum Provider response time for receiving the related to a short process request triggered from the CCS Client\r\n-\tMaximum Provider response time for receiving the result related to a long process request triggered from the CCS Client\r\n-\tMaximum Provider response time for receiving the result Provider related to a SFPL external event processing\r\nWhile the following KPI is just monitored for information:\r\n-\tMaximum Provider response time for receiving an Acknowledge (or Reject) related to a request triggered from the CCS Client.\r\nIt is worth noting that the performance test cases involve only the operations from a subset of CCS services.\r\nThe response times from end to end are computed by costumer equipments. CCS reference platform internal traversal times are measured on provider side.\r\nThe details about executed test cases and related results are provided in the CCS Validation evidence document of this service.\r\n",
          "type": "COLLABORATIVE_VALIDATION"
        }
      ]
    },
    "serviceInformationDescription": {
      "exchangeSchema": [
        {
          "name": "requestProcessCFL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessDirect Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessHeading Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessRoute Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessSpeed Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessEFL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessXFL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessECL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessRFL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessROCD Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestProcessHolding Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestCancelSFPL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestCreateAbbreviatedSFPL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestCreateSFPL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestDeleteSFPL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestRetrieveSFPL Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "requestNonTacticalModification Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "revertToPending Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNChange Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNFlightPlan Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNAbbreviatedFlightPlan Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNAirborneChange Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNArrival Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNCancel Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNDelay Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        },
        {
          "name": "correctAFTNDeparture Exchange schema",
          "reference": "CCS_flightDataManagement.proto 5.1.0.4",
          "schemaLanguage": "Protocol buffer"
        }
      ],
      "informationDefinition": [
        {
          "airmConformant": true,
		  "airmVersion": "1.0.0",
          "description": "For the exchanged data model, please refer to the SWIM Service Description document (sections 2.1 and 2.2)",
          "name": "Service Information Definition"
        }
      ]
    },
    "serviceTechnicalDescription": {
      "securityMechanism": [
        {
          "description": "Mutual authentication with X509 certificates is used between the AMQP broker and its client established within a TLS session",
          "name": "Mutual authentication with X509 certificates",
          "type": [
            "AUTHENTICATION"
          ]
        },
        {
          "description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer.",
          "name": "TLS 1.2",
          "type": [
            "CONFIDENTIALITY",
            "INTEGRITY"
          ]
        },
        {
          "description": "IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer",
          "name": "IPsec v4",
          "type": [
            "CONFIDENTIALITY",
            "INTEGRITY",
            "AUTHENTICATION"
          ]
        }
      ],
      "serviceMonitoring": {
        "monitoringDescription": "CCS services and the servers, interfaces and infrastructure supporting them are supervised in real time by trained and licensed ATSEPS during CCS operational use.\r\nA dedicated service to obtain supervision information for the complete CCS swim services portfolio and the technical means supporting these services is available to the customer. For more information, please refer to the swim service description of the CCS technical supervision distribution service."
      },
      "technicalConstraint": [
        {
          "name": "Time synchronisation",
          "description": "CCS provider and CCS customer use the date and time for the operation of each service, and they must be able to date the traces and the information passed to the SSI log collector.\r\nNTP is the standard solution to synchronize time accurately. So, CCS Provider and CCS Customer shall use, each of them, at least one NTP server (stratum N), integrated in a NTP network containing a stratum 0 reference time clock. CCS customer may use a CCS provider server as a NTP server, however this usage is restricted to time synchronization test or monitoring purpose.\r\n"
        },
        {
          "name": "Provider-Customer interface-Exchange patterns",
          "description": "Each services interface of the CCS business services relies on the concept of AMQP queues and topics. \r\n-\tThe CCS customer shall use an implementation of the AMQP 1.0 specification to connect to the CCS provider AMQP 1.0 endpoint. \r\n-\tThe CCS provider endpoint is an AMQP 1.0 broker managing queue and topics. \r\nThe message payloads are encoded following a protobuf format. \r\nThe message exchange patterns used by the CCS services are request/reply and publish/subscribe. The CCS customer acts as requester and subscriber. The CCS provider acts as responder and publisher.\r\nConcerning publish-subscribe, the CCS customer subscribes to a CCS distribution service by directly listening to an appropriate AMQP topic, which name follows the CCS derivation rules.\r\nThe subscription to CCS Distribution Services is not performed via subscription operations, but by connecting to the appropriate AMQP Topic described in the .protobuf files as topic://\u003cNameSpaceName\u003e.\u003cServiceInterfaceName\u003e.\u003cLogicalOperation\u003e\r\nThe subscribers can filter the messages they want to receive by using the filter parameters, if any, defined for the subscription operation.\r\nPlease note that, after subscribing to a CCS Distribution Service, the current repository of messages needs to be obtained from CCS via the get\u003cMessageRepository\u003e operation defined for each CCS Distribution Service (see \"Subscription\" section of the distribution operation of the service).\r\nN.B:\r\n- If the CCS platform restarts while the Customer is connected to the AMQP Broker, the current repository of messages is published again.\r\n- The acknowledgement that a Customer receives to his request (\"RequestReport\") may be received after the data distribution that this request has triggered, as these two messages are managed asynchronously by AMQP Queues and Topics\r\n\r\nConcerning request-reply the CCS customer sends a request by sending a message to an appropriate AMQP queue, which name follows the CCS derivation rules, to make a request. The request message contains the name of the queue into the CCS customer listens and in which the reply from the CCS provider is expected.\r\n"
        },
        {
          "name": "Provider-Customer interface-Connection management",
          "description": "The Customer is the one that initiates the TCP connection and in case of a Network / Connection failure, it is the responsibility of the CCS customer to try to reconnect regularly."
        },
        {
          "name": "Provider-Customer interface-Queue management",
          "description": "The AMQP broker creates the physical resources associated with a destination (queue, topic) on demand when messages are actually sent to them.\r\nPermissions on queues and topics (read/write access) are granted based on intended usage. The CCS customer will have: \r\n-\tWrite access on the request queue\r\n-\tRead access on the reply queue \r\n-\tRead access on the topic for distribution service\r\n"
        }
      ]
    },
    "serviceInterface": [
      {
        "behaviour": [
          {
            "name": "Service behaviour",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "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:\r\n- ATC tactical Instructions: Holding, Heading, Speed, Cleared Flight Level (CFL),Rate Of climb/Descend (ROCD), Direct To and Cleared To,\r\n- System inputs: entry FL (EFL), exit FL (XFL), enCruiseFL (ECL) and requested Flight Level (RFL).",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessCFL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessDirect",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessHeading",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessRoute",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessSpeed",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessEFL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessXFL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessECL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessRFL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessROCD",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.ATCCommandsManagementProvider.requestProcessHolding",
                "type": "QUEUE"
              }
            ],
            "name": "ATCCommandsManagementProvider"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "ATCCommandsManagementProvider",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "Operation to process the input of a Cleared Flight Level given the flight identifier and the value of the level to be applied.\r\nThe input may contain applicationStart data that can be a route point, distance before/after a route point or after current position.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessCFL",
            "operationMessage": [
              {
                "description": "To process the input of a Cleared Flight Level given a FP identification and the value of the level.",
                "direction": "IN",
                "isFault": false,
                "name": "ClearedFlightLevel"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse"
              }
            ],
            "processingConsideration": [
              {
                "name": "climbDescendKind parameter",
                "description": "The climbDescendKind optional parameter is used to determine the expected behaviour of the aircraft to reach the Cleared Flight level:\r\n-\tit shall be filled in the input if the aircraft is expected to start its evolution immediately after the application start point\r\n-\tif it is filled, the CLIMB (resp. DESCEND) value is required if the Cleared Flight level is higher (resp. lower) than the actual flight level at the application point. In case the flight is holding, and if the CFL input application point is immediate, the actual flight level to consider is the one over the holding entry point\r\n-\tif it is filled, it is optional to input also a target point, which is the trajectory point at which the aircraft is expected to end its evolution (given via the applicationEnd.routePointId parameter)\r\n"
              },
              {
                "name": "clearedROCD and levelRestrictionKind parameters",
                "description": "Please note that the attributes clearedROCD and levelRestrictionKind are not processed by CCS (they are mentioned for interoperability purpose only). The consumer cannot input a clearedROCD via this operation."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight can be updated depending on the value in the input and the flight phase and, if it\u0027s the case, published using the FlightDataDistributionSubscriber Service Interface."
              },
              {
                "name": "applicationPoint parameter",
                "description": "If no application point is provided, CCS applies the constraint to the \"immediate\" application point, i.e. a projection of the last available track position on the expanded route (or, if not available, the current position of the flight in the planned trajectory, i.e. its 4D point which ETO is equal to the current system time)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "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). \r\nThe input may contain application data that can be a route point, distance before/after a route point or after current position.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessDirect",
            "operationMessage": [
              {
                "description": "Instruction to proceed directly to the specified position",
                "direction": "IN",
                "isFault": false,
                "name": "ProceedDirectTo"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight is updated and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "applicationData parameter",
                "description": "If no applicationData is provided, CCS applies the constraint to the \"immediate\" application point, i.e. a projection of the last available track position on the expanded route (or, if not available, the current position of the flight in the planned trajectory, i.e. its 4D point which ETO is equal to the current system time)."
              },
              {
                "name": "applicationPoint parameter",
                "description": "The application point is inserted in the expanded route as a new route point (if not already present) and tagged as \"application point\"."
              },
              {
                "name": "expanded route points tag",
                "description": "The expanded route points between the application point and the resuming point are tagged as BYPASSED_WAYPOINT (ie. route across points)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of a heading clearance.\r\nIt allows to assign either:\r\n-\tan absolute heading. To do this:\r\n\t-\troutePointId should not be filled\r\n\t-\tcontinueHeading should be either not filled or set to FALSE\r\n\t-\teither assignedHeading or application end point shoud be filled. If filled, the application end point should be expressed in the geographical point type\r\n-\ta relative heading. To do this:\r\n\t-\troutePointId should not be filled\r\n\t-\tcontinueHeading should be either not filled or set to FALSE\r\n\t-\tdirectionOfTurn and assignedHeading shoud be filled\r\n-\ta maintain order. To do this:\r\n\t-\troutePointId should not be filled\r\n\t-\tcontinueHeading should be set to TRUE\r\n-\ta resume own navigation order. To do this, routePointId should be filled.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessHeading",
            "operationMessage": [
              {
                "description": "Instruction to fly on the specified heading.",
                "direction": "IN",
                "isFault": false,
                "name": "FlightHeading"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "HeadingClearanceRestrictionKind parameter",
                "description": "The HeadingClearanceRestrictionKind attribute is not processed by CCS (it is mentioned for interoperability purpose only); "
              },
              {
                "name": "directionOfTurn parameter",
                "description": "The parameter directionOfTurn is relevant (and mandatory) only for RELATIVE heading (ignored for Maintain or ABSOLUTE heading), it indicates in which direction the flight shall turn to reach the heading."
              },
              {
                "name": "assignedHeading parameter",
                "description": "The assignedHeading corrresponds to a ground track in case of relative heading, and to a heading (degrees from North) in case of absolute heading."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight is updated and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "applicationPoint parameter",
                "description": "If no application point is provided, CCS applies the constraint to the \"immediate\" application point, i.e. the track position if given in the input, or the last available track position otherwise (the one in the last position report)"
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the modification of a route portion for a specified flight.      \r\nThe input shall contain:\r\n-\tthe flight identifier,\r\n-\tthe new portion of route.\r\nThe input may contain either an application end point (routePoint not overflown used to rejoin the old route) or a new destination aerodrome.\r\nThe input may also contain application start data that can be a route point, distance after/before a route point, distance after current position.\r\n. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessRoute",
            "operationMessage": [
              {
                "description": "Instruction to proceed via the specified route.",
                "direction": "IN",
                "isFault": false,
                "name": "ClearedTo"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "CCS limitation",
                "description": "CCS does not allow the input of the new route using the clearedRouteItem (it is mentioned for interoperability purpose only), only icaoRoute format is allowed (route textual description including significant points, airways...);"
              },
              {
                "name": "mutually exclusive parameters",
                "description": "the parameters application end point and newDestinationAerodrome are mutually exclusive."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight is updated and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "expected results",
                "description": "The expected results on the route of the flight are:\r\n- the insertion of the application point as a new route point,\r\n- the deletion of the existing route points between the application start point and the application end point (or new ADES),\r\n- the insertion of the new portion of route between the application point and the application end point (or new ADES)."
              },
              {
                "name": "applicationPoint parameter",
                "description": "If no application point is provided, CCS applies the constraint to the \"immediate\" application point, i.e. the track position if given in the input, or the last available track position otherwise (the one in the last position report)."
              },
              {
                "name": "undo action",
                "description": "Note: The operator will be able to undo a former route change by simply executing a new route amendment order providing the Previous Route as input (available in the flightDataInfo of the FlightData Message)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of a speed clearance.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessSpeed",
            "operationMessage": [
              {
                "description": "Manual Assigned Speed Input: Assign speed instruction.\r\nThe parameters assignedSpeed, maximumSpeed and minimumSpeed are mutually exclusive.\r\n\r\nNote: the controller cannot input a speed range (min and max at the same time).",
                "direction": "IN",
                "isFault": false,
                "name": "FlightSpeed"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "CCS limitations",
                "description": " CCS does not allow inputting the speedRestrictionKind in this operation (it is mentioned for interoperability purpose only). "
              },
              {
                "name": "mutually exclusive parameters",
                "description": "The parameters assignedAirspeed, maxAirspeed and minAirspeed are mutually exclusive (at least one of them shall be provided)."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight is updated and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "applicationPoint parameter",
                "description": "If no application point is provided, CCS applies the constraint to the \"immediate\" application point, i.e. a projection of the last available track position on the expanded route (or, if not available, the current position of the flight in the planned trajectory, i.e. its 4D point which ETO is equal to the current system time)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of the Entry Flight Level used for coordination between two logical positions. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessEFL",
            "operationMessage": [
              {
                "description": "Controller EFL input is used to change the coordination level for the transfer from the previous responsibility.",
                "direction": "IN",
                "isFault": false,
                "name": "EntryFlightLevel"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "coordinationPoint parameter",
                "description": "the coordinationPoint attribute is not processed by CCS (it is mentioned for interoperability purpose only);"
              },
              {
                "name": "mutually exclusive parameters",
                "description": "the attributes applicationStart and routePointId are mutually exclusive."
              },
              {
                "name": "applicationPoint parameter",
                "description": "If no application point is provided in the input, the system would automatically use the latest between immediate, the giving Logical CWP Entry Point, and the Exit Point of the last discontinuity inside the Logical CWP issuing the order."
              },
              {
                "name": "EFL input processing",
                "description": "An EFL input is processed like an XFL input requested from the upstream logical position."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight and the coordination data (XFL, SFL...) of the concerned transition are updated and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "SFL parameter",
                "description": "If the SFL (Supplementary Flight Level) is provided, then the input would typically result in a band between the SFL and the EFL, composed by 2 constraints, one at or below and one at or above."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of the Exit Flight Level used for coordination between two logical positions. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessXFL",
            "operationMessage": [
              {
                "description": "Controller XFL input is used to change the coordination level for the transfer to the next responsibility",
                "direction": "IN",
                "isFault": false,
                "name": "ExitFlightLevel"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "coordinationPoint parameter",
                "description": "The coordinationPoint attribute is not processed by CCS (it is mentioned for interoperability purpose only)."
              },
              {
                "name": "mutually exclusive parameters",
                "description": "The attributes pointLocation and routePointId are mutually exclusive."
              },
              {
                "name": "applicationPoint parameter",
                "description": "if no application point is provided in the input, the system would automatically use the latest between immediate, the giving Logical CWP Entry Point, and the Exit Point of the last discontinuity inside the Logical CWP issuing the order."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, the trajectory of the flight and the coordination data (XFL, SFL...) of the concerned transition are updated and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs. "
              },
              {
                "name": "revision case",
                "description": "If the downstream responsibility traversal coordination state was previously not \"nil\", the system performs a Revision."
              },
              {
                "name": "SFL parameter",
                "description": "If the SFL (Supplementary Flight Level) is provided, then the input would typically result in a band between the SFL and the XFL, composed by 2 constraints, one at or below and one at or above)"
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "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. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessECL",
            "operationMessage": [
              {
                "description": "EnRouteCruiseLevel is the planned FL agreed by the controller, which is mainly used during the Flight.",
                "direction": "IN",
                "isFault": false,
                "name": "EnRouteCruiseLevel"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "mutually exclusive parameters",
                "description": "Please note that the attributes applicationPoint (GeographicalPoint) and routePointId are exclusive."
              },
              {
                "name": "ECL input",
                "description": "On ECL input, CCS:\r\n- creates an En-Route Cruise Level constraint,\r\n- sets to INACTIVE other existing ECL constraints whose application point is located after this ECL Input application point and within the same ATSU AoR,\r\n- cancels each downstream XFL constraint within the same ATSU and with a level not within the level band delimited by the level at application point and the ECL value."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of a Requested Flight Level given the flight identifier and the value of the level to be applied. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessRFL",
            "operationMessage": [
              {
                "description": "Class supporting the input of a requestedFlightLevel to be applied on an indicated application point.",
                "direction": "IN",
                "isFault": false,
                "name": "RequestedFlightLevel"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "Successful request",
                "description": "If the request is successful, the constraints resulting from the RFL order are set as described below and the trajectory of the flight is updated. The flight plan ICAO F15 is updated, depending on the input location (regarding the flight phase). The updated SFPL is published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "mutually exclusive parameters",
                "description": "Please note that the attributes applicationPoint (GeographicalPoint) and routePointId are exclusive."
              },
              {
                "name": "RFL input",
                "description": "On RFL input, CCS:\r\n- creates an En-Route Cruise Level constraint,\r\n- sets to INACTIVE other existing ECL constraints whose Application Point is located after this RFL Input Application Point and within the same ATSU AoR.\r\n"
              },
              {
                "name": "applicationPoint parameter",
                "description": "By default, if no application point is provided, CCS applies the constraint to the \"immediate\" application point, i.e. a projection of the last available track position on the expanded route (or, if not available, the current position of the flight in the planned trajectory, i.e. its 4D point which ETO is equal to the current system time)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of an ROCD (Rate Of Climb or Descent) instruction.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessROCD",
            "operationMessage": [
              {
                "description": "Cleared information related to a ROCD",
                "direction": "IN",
                "isFault": false,
                "name": "ClearedROCD"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "ROCD range limitation",
                "description": "Please note that the controller cannot input an ROCD range (min and max at the same time)."
              },
              {
                "name": "Successful request",
                "description": "\r\nIf the request is successful, the constraints resulting from the ROCD order are set as described below and the trajectory of the flight is updated. The updated SFPL is published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs. \r\n"
              },
              {
                "name": "ROCD input",
                "description": "On ROCD input, CCS sets an open constraint if at least one of the following conditions is satisfied:\r\n- the application point of the input is in take-off or final approach phase,\r\n- if in climb/intermediate climb phase, the level at application point is greater than the CFL,\r\n- if in descent/intermediate descent, the level at application point is lower than the CFL.\r\n\r\nOn ROCD input, CCS sets a closed constraint if the following conditions are satisfied:\r\n- the application point of the input is in Initial climb phase, climb phase, Cruise phase, pre-descent phase, descent phase or Intermediate Approach phase,\r\n- and if in climb/intermediate climb phase, the level at application point is lower than the CFL or in descent/intermediate descent, the level at application point is greater than the CFL.\r\nIf no application point is provided, CCS applies the constraint to the \"immediate\" application point, i.e. the track position if given in the input or the last available track position otherwise (the one in the last position report)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the input of a holding clearance a holding exit clearance or a holding cancellation clearance.\r\nThe input shall contain the flight identifier.\r\n. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestProcessHolding",
            "operationMessage": [
              {
                "description": "Instruction to enter a holding pattern with the published characteristics at the specified position and level.",
                "direction": "IN",
                "isFault": false,
                "name": "FlightHolding"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "Successful request",
                "description": "If the request is successful, the constraints list and the trajectory of the flight are updated accordingly and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "Predefined holding area",
                "description": "Predefined Holding area :\r\n-\tHolding area : holdingVolumeIdentifier should be filled with the name of the predefined holding area.\r\n-\tEntry point: (applicationStart.point) :  it is the point of entry of the holding area. It can be either a point already in the route of the flight, or not. If not, it will be inserted in the route immediately after the application point (which is either applicationStart.routePointId if filled, or the current flight position otherwise).\r\n-\tExit point: (applicationEnd.point) : it is the point of exit of the holding area. It is optional in the input. If filled, it has to be a point already in the route of the flight, and it will be the next point after entry point (so, if other points are initially between entry and exit points, they will be automatically removed from the route). If not filled, the exit point one defined in dataset is used by the system as exit point. If not in the route, it is inserted immediately after the entry point."
              },
              {
                "name": "Non predefined holding area",
                "description": "Non predefined Holding area :\r\n-\tHolding area : holdingVolumeIdentifier should be filled with a dummy name.\r\n-\tEntry point: (applicationStart.point) :  it is the point of entry of the holding area. It can be either a point already in the route of the flight, or not. If not, it will be inserted in the route immediately after the application point (which is either applicationStart.routePointId if filled, or the current flight position otherwise).\r\n-\tExit point: (applicationEnd.point) : it is the point of exit of the holding area. It is optional in the input. If filled, it has to be a point already in the route of the flight, and it will be the next point after entry point (so, if other points are initially between entry and exit points, they will be automatically removed from the route). If not filled, the entry point is used by the system as exit point.\r\n"
              },
              {
                "name": "holdingCancellation input",
                "description": "If the input is a holding cancellation input (possible only if the holding entry point has not been overflown), holdingStatus shall be set to HOLDING. It shall contain the holding exit point identifier (given via the applicationEnd.routePointId parameter). It may also contain the holding entry point identifier (given via the applicationStart.routePointId parameter)."
              },
              {
                "name": "holdingExit input",
                "description": "If the input is a holding exit input (possible only if the holding entry point has been overflown), holdingStatus shall be set to CLEARED_TO_LEAVE_HOLD. No other parameter has to be filled."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "behaviour": [
          {
            "name": "Service behaviour ",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "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.",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.requestCancelSFPL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.requestCreateAbbreviatedSFPL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.requestCreateSFPL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.requestDeleteSFPL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.requestRetrieveSFPL",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.requestNonTacticalModification",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.FlightPlanModificationManagementProvider.revertToPending",
                "type": "QUEUE"
              }
            ],
            "name": "FlightPlanModificationManagementProvider"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "FlightPlanModificationManagementProvider",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "Operation to process the input of a manual SFPL cancellation.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestCancelSFPL",
            "operationMessage": [
              {
                "description": "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).",
                "direction": "IN",
                "isFault": false,
                "name": "CancelSFPL"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "Successful request",
                "description": "If the request is successful, the SFPL flightPlanStatus is set to TERMINATED and CCS will remove this SFPL automatically a pre-defined time after its end."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the creation of an abbreviated SFPL. . ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestCreateAbbreviatedSFPL",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation requestCreateAbbreviatedSFPL. ",
                "direction": "IN",
                "isFault": false,
                "name": "CreateAPLInfo"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "flightIdentifier parameter",
                "description": " the attribute flightIdentifier is not processed by CCS for this operation (it is inherited from FlightDataManagementRequest class, and mentioned for interoperability purpose only)."
              },
              {
                "name": "estimatedTimeOfArrival parameter",
                "description": "The attribute estimatedTimeOfArrival is not processed by CCS for this operation (it is mentioned for interoperability purpose only)."
              },
              {
                "name": "additional technical parameters",
                "description": "Additional technical parameters can be provided when the request is associated with an FDO correction."
              },
              {
                "name": "RDPS name",
                "description": "The name of the RDPS currently used is known and exchanged between CCS and the ATSU."
              },
              {
                "name": "trackSource and trackId parameters",
                "description": "trackSource and trackId shall be both present if one of them is set"
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, CCS creates an APL and stores all the valid ICAO data given as input without any processing (no profile computation...) in the APL. Then the APL is published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in the Controller HMIs."
              },
              {
                "name": "full SFPL creation",
                "description": "When all the SFPL required fields are provided, CCS creates a full SFPL (cf. requestCreateSFPL operation definition)."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "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.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestCreateSFPL",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation requestCreateSFPL.",
                "direction": "IN",
                "isFault": false,
                "name": "CreateSFPLInfo"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": " Required fields",
                "description": "The manual SFPL creation input shall contain the following required SFPL fields to be populated for a full SFPL creation:\r\nIFPL identifier, callsign aircraftIdentification (F7a), flightType (F8b), flightRules (F8a), aircraftTypeICAOIdentifier (F9b), NCAEquipment (F10a), departureAerodromeDesignator (F13a),  icaoRoute, requestedFlightLevel (F15b), enRouteCruiseSpeed (TAS or Mach) (F15a) and destinationAerodromeDesignator (F16a).\r\n\r\nThis input shall allow: \r\n-\tto request the immediate pre-activation or activation of the SFPL first internal segment of the system instance,\r\n-\tand to input optionally the entry time and/or entry Flight Level on the segment entry point.\r\n"
              },
              {
                "name": " Automatic computations",
                "description": "When not provided in the input, the following automatic computation is made:\r\n-\tif wakeTurbulenceCategory is not provided, if provided aircraft type is known, the system shall use the wake turbulence category of dataset aircraft performance characteristics\r\n-\tif estimatedOffBlockTime is not provided in the input, the system shall use by default the current time\r\n-\tif estimatedOffBlockDate is not provided in the input, the system shall determine the EstimatedOffBlockDate using a time window [-4h; +20h] around the current time\r\n-\tif flight duration is not provided by the manual SFPL creation input:\r\n-\tif ADEP and ADES are known, the system shall estimate the flight duration using the cruising speed,\r\n-\totherwise a default 3 hours duration is set.\r\n"
              },
              {
                "name": "flightIdentifier parameter",
                "description": " the attribute flightIdentifier is not processed by CCS for this operation (it is inherited from FlightDataManagementRequest class, and mentioned for interoperability purpose only)."
              },
              {
                "name": "estimatedTimeOfArrival parameter",
                "description": "The attribute estimatedTimeOfArrival is not processed by CCS for this operation (it is mentioned for interoperability purpose only)."
              },
              {
                "name": "additional technical parameters",
                "description": "Additional technical parameters can be provided when the request is associated with an FDO correction."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, a full SFPL is created (including the expanded Route, the trajectory, the Sector list, the flight states, the servedController list...) and published using the FlightDataDistributionSubscriber Service Interface in order to be displayed in FDO or Controller HMIs."
              },
              {
                "name": "EFL input or update",
                "description": "On input/update of an EFL for the first segment of the IOP area, the system shall update the CFL of the SFPL with the given entry level."
              },
              {
                "name": "Unsuccessful request",
                "description": "If required data are missing, the requestCreateSFPL input is rejected. \r\nA dedicated manual input shall be used to create an abbreviated SFPL (cf. requestCreateAbbreviatedSFPL).\r\nHowever a requestCreateSFPL input may degenerates into the creation of an abbreviated SFPL in the following 2 cases: \r\n1)\tfailure of any route semantic check\r\n2)\tpresence of all the mandatory data but impossibility to determine Initial Conditions, due to the flight never intersecting the TP Area.\r\nMoreover CCS creates abbreviated flight plans for SFPL related erroneous messages (received on external OLDI or AFTN lines or created manually by controllers), instead of referring erroneous messages to FDO, if at least the callsign is available (configurable option). The APL is created including the valid ICAO data given in the input.\r\n"
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the deletion of a specified Flight Plan from ADSP. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestDeleteSFPL",
            "operationMessage": [
              {
                "description": "To process the deletion of a specified Flight Plan from both CWP and ADSP. Hence, the deleted FP will not be available for retrieval",
                "direction": "IN",
                "isFault": false,
                "name": "DeleteSFPL"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "deleted SFPL retrieval",
                "description": "the deleted SFPL will not be published or available for retrieval."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, CCS removes immediately the SFPL."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process an SFPL(s) consultation request.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestRetrieveSFPL",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation requestRetrieveSFPL.",
                "direction": "IN",
                "isFault": false,
                "name": "ConsultInfo"
              },
              {
                "description": "Technical class\r\nMessage definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataConsultationResponse"
              }
            ],
            "processingConsideration": [
              {
                "name": "originator parameter",
                "description": "The originator is defined as mandatory for all FDM operations for interoperability purpose, but CCS ignores it for this operation.\r\nCCS ignores also the following parameters for this operation: flightIdentifier, techStamp and collectionVersion.\r\n"
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, a summary of each real SFPL matching the given criteria are provided to the requestor (the return SFPL(s) have to comply with all the requested criteria).\r\nIf not, CCS should send one of the error messages defined in the error messages tab hereafter. "
              },
              {
                "name": "no data fulfills criteria",
                "description": "In case no data fulfills the criteria of a getxxx request, a OK_BUT response will be sent to the customer, with an error description message."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Operation to process the modification of one or several SFPL fields. \r\nThe input shall contain the flight identifier, the originator and at least a field to modify.\r\nThe 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.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "requestNonTacticalModification",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation requestNonTacticalModification.",
                "direction": "IN",
                "isFault": false,
                "name": "NonTacticalModificationInfo"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "estimatedTimeOfArrival parameter",
                "description": "The attribute estimatedTimeOfArrival is not processed by CCS for this operation (it is mentioned for interoperability purpose only)."
              },
              {
                "name": "Additional technical parameters",
                "description": "Additional technical parameters can be provided when the request is associated with an FDO correction."
              },
              {
                "name": "Successful request",
                "description": "If the request is successful, CCS triggers the relevant processing as described below and published the updated SFPL data using the FlightDataDistributionSubscriber Service Interface in order to be displayed in FDO or Controller HMIs.      \r\nThe SFPL data are updated according to the rules described below.\r\n\r\nStandard rule:\r\nEach input optional elementary field shall replace the corresponding one in the SFPL if and only if this field is given in the parameter flightPlanInfo, otherwise the corresponding SFPL field shall be left unchanged:\r\n-\tfields set: the optional fields that are present in the input are updated in the SFPL.\r\n-\tfields unchanged: the optional fields that are not present in the input are not updated in the SFPL.\r\n\r\nOtherInformation and supplementaryInformation exceptions:\r\nThe parameter flightPlanInfo contains optional data otherInformation, supplementaryInformation corresponding to ICAO fields 18 and 19, both provided in a string format.\r\nThe operation allows modifying the complete fields 18 and 19.\r\nWhen otherInformation or supplementaryInformation input data are given, if an optional elementary (sub-)field is not defined in the input data, the corresponding one shall be removed from the SFPL:\r\n-\totherInformation (resp. supplementaryInformation) (sub-)fields unchanged: When F18 (resp. 19) is not at all present in the input; the complete corresponding SFPL F18 (resp. 19) field is not updated. I.e. all its (sub-)fields are kept unchanged.\r\n-\totherInformation (resp. supplementaryInformation) (sub-)fields set: When F18 (resp. 19) is present in the input; the optional (sub-)fields that are present in input are stored within the corresponding SFPL F18 (resp. 19) field.\r\n-\totherInformation (resp. supplementaryInformation) (sub-)fields reset: When F18 (resp. 19) is present in the input; the optional (sub-)fields that are not present in input are reset from the corresponding F18 (resp. 19) field.\r\n\r\nOn the change of fields which may lead to a new route (Route, ADEP, ADES, RFL, SID, STAR, OTH, ATYP, EQUIP...), CCS must perform the following operations:\r\n- compute the new route,\r\n- update the constraints, \r\n- perform the trajectory computation,\r\n- re-compute the crossed volumes, deduce the crossed ATSUs from the computed SFPL trajectory, \r\n- detect if some segments have been created or have disappeared,\r\n- check the SSR code for the new route,\r\n- update the SFPL and segment states,\r\n- determine the new control and informed responsibility list,\r\n- update the existing coordination data, and determine the coordination data for the new transitions, \r\n- determine the new served Controller list,\r\n- distribute the updated SFPL to the IOP partners if any.\r\n\r\nOn the change of EOBT/EOBD for a flight which has not departed, CCS re-assesses:\r\n- the delays on the ground,\r\n- the time shift on the computed trajectory,\r\n- the SFPL and segment states due to potential SFPL segment state regression.\r\n\r\nOn a change of SSR code:\r\n- the previous SSR code and the assigned SSR code are stored in the SFPL, for relevant SFPL segments.\r\n- CCS checks the validity of the new SSR code and the potential duplication.\r\n- CCS re-assesses the classification of the coordinations and potential automatic coordination rejections.\r\n\r\n\r\nRoute modification:\r\nIt is not possible to process a route amendment via this operation (for this purpose refer to the operation requestProcessRoute). \r\nThe requestNonTacticalModification operation allows changing the whole reference route (ICAO F15 c), not a portion of the route. The change of F15 C ICAO field, even if the change impacts only a portion of it, is processed by the system as a change of the whole reference route and makes invalid all the constraints input on the SFPL.\r\nThe trajectory is recomputed according to the new F15-C if the flight is non departed. If the flight is departed, the input is rejected by CCS (i.e. it is either rejected or sent to FDO as applicable).\r\nBoth F15a and F15b can be changed via this operation even if part of trajectory points are overflown.\r\n"
              },
              {
                "name": "Abbreviated SFPL",
                "description": "When the request is processed on an abbreviated SFPL, CCS shall upgrade the APL into a full SFPL or into an AFIL full SFPL (without the ICAO location indicator of the departure aerodrome), if all mandatory data are provided."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "Allows the operator to make a segment regression.\r\nIt turns a controlled segment from live or pending status into monitored status\r\nThe system keeps the segment in monitored state until a notification or activation message is received.\r\n\r\nThe input shall contain the flight identifier, the segment identifier and optionally the segment entry time (estimated time over the segment entry point).\r\nWhen filled, the segment entry time adjusts the time estimates over the trajectory points.\r\n\r\nCaveat: The operation name (coming from SESAR) is misleading in CCS context.. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "revertToPending",
            "operationMessage": [
              {
                "description": "Set of parameters for turning the segment state from live or pending to monitored status",
                "direction": "IN",
                "isFault": false,
                "name": "RevertToPending"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "processingConsideration": [
              {
                "name": "Successful request",
                "description": "If the request is successful, the segmentState is set to MONITORED."
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "behaviour": [
          {
            "name": "Service behaviour  ",
            "description": "The detailed behavior of the service is provided in each operation dedicated section"
          }
        ],
        "description": "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. \r\nIt covers the following cases:\t\r\n-\tAFTN Modification messages: CHG, CNL, DLA, ARR, DEP (ICAO format), ICHG, ICNL, IDLA, IARR, IDEP, IACH (ADEXP format). In this case, it may be necessary to associate a FP to these messages to be able to correct them successfully.\r\n-\tAFTN Creation messages: FPL (ICAO format), IFPL, IAPL (ADEXP format).\r\n",
        "endPoint": [
          {
            "address": "For security reasons, the addresses will be communicated only to Customers",
            "addressableResource": [
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNChange",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNFlightPlan",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNAbbreviatedFlightPlan",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNAirborneChange",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNArrival",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNCancel",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNDelay",
                "type": "QUEUE"
              },
              {
                "description": "Name of the queue",
                "name": "queue://ccs.protobuf.flightDataManagement.AFTNCorrectionManagementProvider.correctAFTNDeparture",
                "type": "QUEUE"
              }
            ],
            "name": "AFTNCorrectionManagementProvider"
          }
        ],
        "interfaceBindingDescription": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google\u0027s language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler. ",
        "interfaceProvisionSide": "PROVIDER_SIDE_INTERFACE",
        "name": "AFTNCorrectionManagementProvider",
        "networkInterfaceBinding": "IPV4_SECURE_UNICAST",
        "operation": [
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of a CHG or ICHG message. \r\nWhenever a change is made to the data contained in a Flight Plan message already sent to the ATSUs concerned with the flight, they must all be notified. It is particularly important to notify changes of Flight Level or Flight Rules, whether the change is made before departure or en-route. Such notification may be done by phone or ATS/DS when possible; otherwise it must be done by means of a modification message sent to AFTN.\r\n\r\nThe following CHG fields can be corrected through this operation:\r\nCHG content: callsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), otherInformation (F18), amendments of other ICAO fields (F22), alternativeDestinationAerodromeDesignator (F16c).\r\nIn CHG, F22 should only amend F7b/c, F8, F9, F10, F13b, F14, F15, F16, F18, F19.\r\n\r\nThe following ICHG fields can be corrected through this operation via decoded data: \r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD),\r\nestimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNChange",
            "operationMessage": [
              {
                "description": "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.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNChange"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of an FPL or IFPL message. \r\nThe FPL message is the flight plan as filed with an ATS unit by the pilot or a designated representative, without any subsequent changes.\r\nThe following FPL fields can be corrected through this operation:\r\ncallsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), flightRules (F8a), flightType (F8b), numberOfAircraft (F9a), aircraftTypeICAOIdentifier (F9b), wakeTurbulenceCategory (F9c), NCAEquipment (F10a), surveillance equipment (F10b), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), enRouteCruiseSpeed (TAS or Mach) (F15a), requestedFlightLevel (F15b), icaoRoute (F15c), destinationAerodromeDesignator (F16a), totalEstimatedElapsedTime (F16b), alternativeDestinationAerodromeDesignator (F16c), otherInformation (F18), supplementaryInformation (F19).\r\n\r\nThe following IFPL fields can be corrected through this operation via decoded data: \r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP),\r\n NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).\r\n \r\n Other fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNFlightPlan",
            "operationMessage": [
              {
                "description": "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.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNFlightPlan"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of an IAPL message (ICAO format message APL is not applicable CCS).\r\n\r\nThe following IAPL fields can be corrected through this operation via decoded data:\r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNAbbreviatedFlightPlan",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation correctAFTNAbbreviatedFlightPlan which allows to correct the erroneous fields upon the reception of an IAPL message.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNAPL"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields in the SFPL upon the reception of an IACH message (ICAO format message ACH is not applicable CCS). It is the modification message type distributed by the IFPS upon receipt and successful processing of an FNM, MFS, and AFP for which a valid associated flight plan exists in the IFPS.\r\n\r\nThe following IACH fields can be corrected through this operation via decoded data:\r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNAirborneChange",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation correctAFTNAirborneChange which allows to correct the erroneous fields upon the reception of an IACH message.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNAirborneChange"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of an ARR or IARR message. Where an Arrival message is required for an IFR/GAT flight or part thereof operating within the IFPZ, the appropriate air traffic services unit shall submit such to the IFPS for processing\r\n\r\nThe following ARR fields can be corrected through this operation:\r\ncallsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), destinationAerodromeDesignator and actualLandingTime (F17),  date of flight in otherInformation (F18).\r\n\r\nThe following IARR fields can be corrected through this operation via decoded data:\r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), actualLandingTime (ATA), destinationAerodromeDesignator (ADARR)\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNArrival",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation correctAFTNArrival which allows to correct the erroneous fields upon the reception of an ARR or IARR message.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNArrival"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of an CNL or ICNL message. When a schedule flight or a flight for which a Flight Plan Message has been sent, is subsequently cancelled, the ATSU at the point where the flight is cancelled shall send a Cancellation Message.\r\n\r\nThe following CNL fields can be corrected through this operation:\r\ncallsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).\r\n\r\nThe following ICNL fields can be corrected through this operation via decoded data:\r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE)\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNCancel",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation correctAFTNCancel which allows to correct the erroneous fields upon the reception of an CNL or ICNL message.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNCancel"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of an DLA or IDLA message. When a scheduled flight, or a flight for which a FPL was despatched, has not left the loading apron within 30 minutes after the scheduled or estimated time of departure; or where there is reason to believe that such a flight will not be in a position to leave within the 30 minutes due to the late arrival of the aircraft on the previous sector or for any other reason.\r\n\r\nThe following DLA fields can be corrected through this operation:\r\ncallsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).\r\n\r\nThe following IDLA fields can be corrected through this operation via decoded data:\r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR).\r\n\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNDelay",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation correctAFTNDelay which allows to correct the erroneous fields upon the reception of an DLA or IDLA message.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNDelay"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          },
          {
            "description": "This operation allows the operator to correct the erroneous fields upon the reception of a DEP or IDEP message. Departure message shall be sent immediately after take-off in respect of all flights for which a Flight Plan Message has been sent.\r\n\r\nThe following DEP fields can be corrected through this operation:\r\ncallsign aircraftIdentification (F7a), assignedSSRCode /Mode (F7b/c), departureAerodromeDesignator (F13a), estimatedOffBlockTime (F13b), destinationAerodromeDesignator (F16a), otherInformation (F18).\r\n\r\nThe following IDEP fields can be corrected through this operation via decoded data:\r\ndepartureAerodromeDesignator (ADEP), destinationAerodromeDesignator (ADES), aircraftIdentification (ARCID), aircraftTypeICAOIdentifier (ARCTYP), NCAEquipment (CEQPT), estimatedOffBlockDate (EOBD), estimatedOffBlockTime (EOBT), fillingTime (FILTIM), ifplid (IFPLDID), numberOfAircraft (NBARC), surveillance equipment (SEQPT), dataSourceId (SRC), assignedSSRCode/Mode (SSRCODE), wakeTurbulenceCategory (WKTRC), totalEstimatedElapsedTime (TTLEET), flightRules (FLTRUL), flightType (FLTTYP), alternativeDestinationAerodromeDesignator (ALTRN1/2), icaoRoute (ROUTE), requestedFlightLevel (RFL), enRouteCruiseSpeed (SPEED / MACH), rtepts (RTEPTS), sidDesignator (SID), starDesignator (STAR), actualTakeOffTime (ATD)\r\n\r\nOther fields managed by this operation are included in specificADEXPField, otherInformation and supplementaryInformation, and listed in previous section \"Operations\".. ",
            "idempotency": "NON_IDEMPOTENT",
            "name": "correctAFTNDeparture",
            "operationMessage": [
              {
                "description": "Class used to gather the input parameters of the operation correctAFTNDeparture which allows to correct the erroneous fields upon the reception of an DEP or IDEP message.",
                "direction": "IN",
                "isFault": false,
                "name": "CorrectAFTNDeparture"
              },
              {
                "description": "Message definition of the operation corresponding to the same class name.\r\nSpecialisation of the common RequestReport.\r\nFor AFTNCorrectionManagementProvider operations, only one RequestReport element is expected as it is assumed, that only one Coflight system instance can be involved and connected to FDO.",
                "direction": "OUT",
                "isFault": false,
                "name": "FlightDataManagementResponse "
              }
            ],
            "synchronicity": "SYNCHRONOUS",
            "tiProtocolMethod": [
              "transfer"
            ]
          }
        ],
        "serviceInterfaceBinding": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
        "tiPrimitiveMessageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      }
    ],
    "version": "2.0.0"
  }
}