{
  "informationServiceDescription": {
    "title": "CCS OperationalConfigurationManagement",
    "referenceDate": "2022-06-13",
    "edition": "2.0.0",
    "serviceAbstract": "<p>This Service is part of Coflight Cloud Services (CCS), which are primarily designed to support the Virtual Centre concept. As such, these CCS Services support the interactions between the CCS ATM Data Service Provider (ADSP) and Virtual Centre Air Traffic Service Units (ATSUs). The CCS OperationalConfigurationManagement service is consistent with the other CCS services. It allows the ACC/Approach operational supervisor to manage the operational configuration in the ATSU by processing his input on the following on-line data:</p><p>- the mapping of control roles and responsibilities (control volume, ADES, set of runways,...) to Control Working Positions - Airspace status management (ARES/CDR activation...)</p><p>- Airspace planning management (ARES/CDR timesheets)</p><p>- Aerodrome configuration management</p><p>- RadioFrequency allocation plan management</p><p>Note: Only civil flights are handled by CCS services.</p><p>This version of the service is intended to be used in 'test mission', which aims at providing services and support to the Customer(s) to enable them to test any version of their ATM system during development. Please note that the use of CCS OperationalConfigurationManagement Service implies the use of CCS OperationalConfigurationDistribution Service for sector mappings, aerodrome configuration and radio frequency allocation and of CCS AirspaceStatusDistribution Service for ARES/CDR.</p><p>&nbsp;</p><p>Service retired from 20/03/2023</p>",
    "serviceIdentification": {
      "name": "CCS OperationalConfigurationManagement",
      "version": "2.0.0"
    },
    "serviceProvider": {
      "name": "DSNA&ENAV",
      "description": "<p>DSNA: the French air navigation service provider</p><p>ENAV; the Italian air navigation service provider</p>",
      "type": [
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
      ]
    },
    "serviceCategorisation": {
      "businessActivityType": [
        "INFORMATION_MANAGEMENT"
      ],
      "intendedConsumer": [
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER"
      ],
      "informationCategory": [
        "FLIGHT_INFORMATION_EXCHANGE"
      ],
      "lifeCycle": [
        {
          "lifeCycleStage": "RETIRED"
        }
      ]
    },
    "generalDescription": {
      "operationalEnvironment": {
        "operationalNeeds": [
          {
            "name": " 1 General operational need",
            "description": "CCS OperationalConfigurationManagement Service allows the ACC/Approach operational supervisor to manage the operational configuration in the ATSU by processing his input on the following on-line data:-the mapping of control roles and responsibilities (control volume, ADES, set of runways,...) to Control Working Positions-Airspace status management (ARES/CDR activation...)-Airspace planning management (ARES/CDR timesheets)-Aerodrome configuration management-RadioFrequency allocation plan management"
          }
        ]
      },
      "functionality": [
        {
          "name": "Update sector mapping",
          "description": "Update sector mapping",
          "realWorldEffect": "Change the operational configuration of the ATSU"
        },
        {
          "name": "Activate sector mapping",
          "description": "Activate sector mapping",
          "realWorldEffect": "Change the current operational configuration of the ATSU (using a next or an off-line pre-defined sector mapping)"
        },
        {
          "name": "Update ARES activation status",
          "description": "Update ARES activation status",
          "realWorldEffect": "Change and lock the activation status of the ARES"
        },
        {
          "name": "Unlock ARES activation status",
          "description": "Unlock ARES activation status",
          "realWorldEffect": "Unlock a previous manual ARES activation status: the activation status of the ARES is unlocked and automatically updated by the system from ARES timesheets, information off-line defined and information issued from the CFMU."
        },
        {
          "name": "Update CDR activation status",
          "description": "Update CDR activation status",
          "realWorldEffect": "Change and lock the status of the CDR to open or closed."
        },
        {
          "name": "Unlock CDR activation status",
          "description": "Unlock CDR activation status",
          "realWorldEffect": "Unlock a previous manual CDR status: the status of the CDR is unlocked and automatically updated by the system from CDR timesheets, information off-line defined and information issued from the CFMU."
        },
        {
          "name": "Delete next sector mapping",
          "description": "Delete next sector mapping",
          "realWorldEffect": "Delete the next operational configuration of the ATSU, if any"
        },
        {
          "name": "Load next sector mapping",
          "description": "Load next sector mapping",
          "realWorldEffect": "Change the next operational configuration of the ATSU (using an off-line pre-defined sector mapping)"
        },
        {
          "name": "Create CDR timesheet",
          "description": "Create CDR timesheet",
          "realWorldEffect": "Add a timesheet to a CDR"
        },
        {
          "name": "Delete ARES timesheet",
          "description": "Delete ARES timesheet",
          "realWorldEffect": "Remove an existing activation periods timesheet from an ARES timetable"
        },
        {
          "name": "Delete CDR timesheet",
          "description": "Delete CDR timesheet",
          "realWorldEffect": "Remove an existing timesheet from a CDR"
        },
        {
          "name": "Update ARES timesheet",
          "description": "Update ARES timesheet",
          "realWorldEffect": "Update an existing activation periods timesheet for an ARES"
        },
        {
          "name": "Update CDR timesheet",
          "description": "Update CDR timesheet",
          "realWorldEffect": "Update an existing CDR timesheet"
        },
        {
          "name": "Add a comment for an ARES",
          "description": "Add a comment for an ARES",
          "realWorldEffect": "Define a comment for an ARES"
        },
        {
          "name": "Modify aerodrome runway configuration",
          "description": "Modify aerodrome runway configuration",
          "realWorldEffect": "Modify the current configuration of the runways for an aerodrome of a given Aerodrome Group"
        },
        {
          "name": "Update radio frequency allocation for a responsibility",
          "description": "Update radio frequency allocation for a responsibility",
          "realWorldEffect": "Modify the radio frequency assigned to control responsibility(ies), either by selecting a new radio frequency, or by reverting back to the predefined value"
        },
        {
          "name": "Planify the next aerodrome group configuration",
          "description": "Planify the next aerodrome group configuration",
          "realWorldEffect": "For a given aerodrome group, save a predefined configuration as the next one, together with a planned activation time "
        },
        {
          "name": "Modify aerodrome configuration",
          "description": "Modify aerodrome configuration",
          "realWorldEffect": "For a given aerodrome, modify the configuration parameters"
        },
        {
          "name": "Delete a next aerodrome group configuration",
          "description": "Delete a next aerodrome group configuration",
          "realWorldEffect": "For a given aerodrome group, remove the next configuration"
        },
        {
          "name": "Activate a new aerodrome group configuration",
          "description": "Activate a new aerodrome group configuration",
          "realWorldEffect": "For a given aerodrome group, make as the current configuration, either the one identified as the next one, or another predefined one"
        },
        {
          "name": "Update radio frequency allocation for all the responsibilities of the ATSU",
          "description": "Update radio frequency allocation for all the responsibilities of the ATSU",
          "realWorldEffect": "Change the current radio frequency allocation, either by selecting a new radio frequency allocation plan, or by reverting back to the predefined default radio frequency configuration"
        },
        {
          "name": "Create ARES timesheet",
          "description": "Create ARES timesheet",
          "realWorldEffect": "Add a timesheet into an ARES timetable to define new activation periods"
        }
      ],
      "accessAndUseConditions": [
        {
          "name": "Information ownership",
          "type": "LEGAL_CONSTRAINT",
          "description": "<bold>IPR</bold>In 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).<bold>Access to the Service</bold>This service is provided to Service Consumers under a contractual basis signed between the CCS Service Provider and the Service Consumer."
        },
        {
          "name": "Dependencies with other CCS Services",
          "type": "SERVICE_CONSUMPTION_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": "Alignment to SESAR Virtual Centre activity",
          "type": "SERVICE_POLICY",
          "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": "Service versioning",
          "type": "SERVICE_POLICY",
          "description": "Both the SWIM Service Description documents / Protobuf files and the CCS Services are versioned.The version assigned to SSDs and to Protobuf files is composed by four digits in the form x.y.z.w.New releases are numbered according to the following rule (compared to the previous version): -w 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.-z 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.-y 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.-x increased by one: means that the file contains a new baseline. Major changes are expected to be present.The service version is composed by 3 digits a.b.c assigned according to the following rule:- a could be 0,1,2 depending on the status of the service with respect to the SWIM registration phase:0: before the service application (as candidate)1: if candidate2: if compliant- b Increments if major changes have been done with respect to the previous version (modify/remove). No backward compatibility.- c Increments if minor changes have been done with respect to the previous version (addition/description modified). Full backward compatibility."
        },
        {
          "name": "KPIs monitoring",
          "type": "SERVICE_POLICY",
          "description": "Services management review 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": "Confidentiality and integrity",
          "type": "SECURITY_CONSTRAINT",
          "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": "Authentication and authorisation",
          "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. Mutual 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. -CCS 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).-The 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.-For the cryptographic algorithms, the authorized cipher suites must be agreed between the CCS provider and the customer based on the standards.As an ATSU, the CCS business services customer, once identified, has access to all CCS services.In 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."
        }
      ],
      "dateInOperation": "2020-07-01",
      "abbreviations": [
        {
          "name": "AC",
          "description": "Airspace Configuration"
        },
        {
          "name": "ACC",
          "description": "Area Control Centre"
        },
        {
          "name": "ADES",
          "description": "Aerodrome of Destination"
        },
        {
          "name": "ADSP",
          "description": "ATM Data Service Provider"
        },
        {
          "name": "AFTN",
          "description": "Aeronautical Fixed Telecommunication Network"
        },
        {
          "name": "AIRM",
          "description": "ATM Information Reference Model"
        },
        {
          "name": "ALRS",
          "description": "Alerting Service"
        },
        {
          "name": "AMQP",
          "description": "Advanced Message Queuing Protocol"
        },
        {
          "name": "ANSP",
          "description": "Air Navigation Service Provider"
        },
        {
          "name": "AOR",
          "description": "Area Of Responsibility"
        },
        {
          "name": "APL",
          "description": "Abbreviated Flight Plan"
        },
        {
          "name": "APOC",
          "description": "Airport Operator"
        },
        {
          "name": "ARES",
          "description": "Airspace Reservations"
        },
        {
          "name": "ASD",
          "description": "Airspace Status Distribution"
        },
        {
          "name": "ASM",
          "description": "Airspace Status Management"
        },
        {
          "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": "CCS",
          "description": "Coflight Cloud Services"
        },
        {
          "name": "CDM",
          "description": "Collaborative Decision Making"
        },
        {
          "name": "CDR",
          "description": "Conditional Route"
        },
        {
          "name": "CFMU",
          "description": "Central Flow Management Unit"
        },
        {
          "name": "CWP",
          "description": "Controller Working Position"
        },
        {
          "name": "DCB",
          "description": "Demand and Capacity Balancing"
        },
        {
          "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": "ENAV",
          "description": "Ente Nazionale Assistenza al Volo (Italian ANSP)"
        },
        {
          "name": "FAB",
          "description": "Functional Airspace Block"
        },
        {
          "name": "FABEC",
          "description": "Functional Airspace Block Europe Central"
        },
        {
          "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": "GAT",
          "description": "General Air Traffic"
        },
        {
          "name": "HMI",
          "description": "human machine Interface"
        },
        {
          "name": "ICAO",
          "description": "International Civil Aviation Organization"
        },
        {
          "name": "ID",
          "description": "Identifier"
        },
        {
          "name": "IFR",
          "description": "Instrument Flight Rules"
        },
        {
          "name": "IKE",
          "description": "Internet Key Exchange"
        },
        {
          "name": "INAP",
          "description": "Integrated Network Management and ATC planning"
        },
        {
          "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": "MSA",
          "description": "Multi-sector area"
        },
        {
          "name": "NOP",
          "description": "Network Operation Plan"
        },
        {
          "name": "NTP",
          "description": "Network Time Protocol"
        },
        {
          "name": "OCSP",
          "description": "Online Certificate Status Protocol"
        },
        {
          "name": "OE",
          "description": "Operational Entity"
        },
        {
          "name": "OPSUP",
          "description": "Operational Supervision"
        },
        {
          "name": "PKCS",
          "description": "Public-Key Cryptography Standards"
        },
        {
          "name": "SDD",
          "description": "Service Definition Document"
        },
        {
          "name": "SESAR",
          "description": "Single European Sky Air Traffic Management Research"
        },
        {
          "name": "SFPL",
          "description": "System Flight Plan"
        },
        {
          "name": "SLA",
          "description": "Service Level Agreement"
        },
        {
          "name": "SSD",
          "description": "SWIM Service Description"
        },
        {
          "name": "SSI",
          "description": "Synchronous Serial Interface"
        },
        {
          "name": "SWIM",
          "description": "System Wide Information Management"
        },
        {
          "name": "TAD",
          "description": "Technical Architecture Description"
        },
        {
          "name": "TBC",
          "description": "To Be Confirmed"
        },
        {
          "name": "TBD",
          "description": "To Be Defined"
        },
        {
          "name": "TCP",
          "description": "Transfer Control Protocol"
        },
        {
          "name": "TDA",
          "description": "Temporary Danger Area"
        },
        {
          "name": "TI",
          "description": "Technical Infrastructure"
        },
        {
          "name": "TLS",
          "description": "transport level security"
        },
        {
          "name": "TSA",
          "description": "Temporary Segregated Area"
        },
        {
          "name": "UTC",
          "description": "Coordinated Universal Time"
        }
      ]
    },
    "informationDescription": {
      "informationDefinition": [
        {
          "name": "Service Information Definition",
          "definition": "",
          "airmCorrespondence": ""
        }
      ]
    },
    "technicalDescription": {
      "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. NTP is the standard solution to synchronize time accurately. So, CCS Provider and CCS Customer should use, each of them, at least one NTP server (stratum N), integrated in a NTP network containing a stratum 0 reference time clock."
        },
        {
          "name": "Provider-Customer interface-Exchange patterns",
          "description": "Each services interface of the CCS business services relies on the concept of AMQP queues and topics. -The CCS customer shall use an implementation of the AMQP 1.0 specification to connect to the CCS provider AMQP 1.0 endpoint. -The CCS provider endpoint is an AMQP 1.0 broker managing queue and topics. The message payloads are encoded following a protobuf format. The 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.Concerning 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.The 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://<NameSpaceName>.<ServiceInterfaceName>.<LogicalOperation>The subscribers can filter the messages they want to receive by using the filter parameters defined for each subscription operation.Please note that, after subscribing to a CCS Distribution Service, the current repository of messages needs to be obtained from CCS via the get<MessageRepository> operation defined for each CCS Distribution Service (see \"Subscription\" section of the distribution operation of the service).N.B:- If the CCS platform restarts while the Customer is connected to the AMQP Broker, the current repository of messages is published again.- 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 TopicsConcerning 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."
        },
        {
          "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.Permissions on queues and topics (read/write access) are granted based on intended usage. The CCS customer will have: -Write access on the request queue-Read access on the reply queue -Read access on the topic for distribution service"
        }
      ]
    },
    "references": {
      "serviceDocument": [
        {
          "documentType": "AIRM_TRACE",
          "title": "CCS AIRM mapping OPSUPM service",
          "version": "1.0",
          "description": "AIRM traceability for CCS Operational Configuration Management service payload"
        },
        {
          "documentType": "SERVICE_VALIDATION_REPORT",
          "title": "CCS Validation evidence document - OperationalConfigurationManagement",
          "version": "1.0",
          "description": "Validation evidence for CCS Operational Configuration Management service"
        },
        {
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "title": "CCS_operationalConfigurationManagement.proto",
          "version": "4.2.2.2",
          "description": "Protobuf files describing the exchanged information"
        },
        {
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "title": "CCS_common.proto",
          "version": "5.5.1.2",
          "description": "Protobuf file describing the exchanged information common to two or more CCS Services"
        },
        {
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "title": "metadata.proto",
          "version": "v1.2.0.0",
          "description": "Protobuf file describing the metadata used by the CCS Services"
        },
        {
          "documentType": "SERVICE_SPECIFICATION",
          "title": "CCS Operational Configuration Management Service Description",
          "version": "5.2.2.5",
          "description": "Complete service specification"
        },
        {
          "documentType": "SERVICE_SPECIFICATION",
          "title": "CCS Errors Management Document",
          "version": "2.0",
          "description": "Document that includes the list of all applicable error messages for CCS services"
        }
      ],
      "implementedStandard": [
        {
          "title": "EUROCONTROL Specification for SWIM - Service Description ",
          "version": "2.0",
          "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",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION",
          "conformanceStatement": "Description of Service according to EUROCONTROL specifications"
        },
        {
          "title": "EUROCONTROL Specification for SWIM - Information Definition",
          "version": "1.0",
          "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. ",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION",
          "conformanceStatement": "Information definition according to EUROCONTROL specifications"
        },
        {
          "title": "EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile",
          "version": "1.0",
          "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",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE",
          "conformanceStatement": "Implementation of service and network bindings"
        }
      ]
    },
    "serviceInterface": [
      {
        "name": "AerodromeConfigurationManagementProvider",
        "description": "This Service Interface exposes operations used by the Operational Supervisor to modify the Aerodrome Configuration Data.",
        "provisionSide": "PROVIDER_SIDE",
        "operations": [
          {
            "name": "modifyRunwayConfiguration",
            "description": "Allows to modify the current configuration of the runways for an aerodrome of a given Aerodrome Group.This operation enables an eligible user (normally a supervisor) to modify the following data of a given runway or of the runway(s) of an aerodrome: landing and/or take-off rates, IAP in operation and operating mode (open or closed).It is also possible to revert to default rate values of runway(s) if no rate value is provided in the operation.. ",
            "messages": [
              {
                "name": "ModifyRunwayConfiguration",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "activateAerodromeGroupConfiguration",
            "description": "Allows replacing the current Aerodrome Group Configuration with another given aerodrome group configuration.The user may activate an offline predefined aerodrome group configuration, activate the one previously defined as the Next one or revert back to the default one.When the aim of this operation is to :-activate an offline predefined aerodrome group configuration, aerodromeGroupConfigName should be filled with the name of the configuration,-activate the next aerodrome group configuration, aerodromeGroupConfigName should not be filled,-revert back to the default aerodrome group configuration, aerodromeGroupConfigName should not be filled and aerodromeConfigurationOrigin should be DEFAULT.. ",
            "messages": [
              {
                "name": "ActivateAerodromeGroupConfiguration",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "deleteNextAerodromeGroupConfiguration",
            "description": "Allows removing the fact that an aerodrome group configuration is identified as the next one.. ",
            "messages": [
              {
                "name": "DeleteNextAerodromeGroupConfiguration",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "modifyAerodromeConfiguration",
            "description": "Allows modifying the configuration parameters of an aerodrome.The 3 possibilities given by this operation are :-revert to default the aerodrome Altitude Correction-revert to default the aerodrome Transition Level. In this case, defaultAltitudeCorrection should be set to FALSE-modify one or several of the following parameters : transitionLevel, altitudeCorrection, modeSCapabilityState. In this case, revertToDefault should not be filledaerodromeGroup is ignored by CCS.. ",
            "messages": [
              {
                "name": "ModifyAerodromeConfiguration",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "planifyNextAerodromeGroupConfiguration",
            "description": "Allows changing the next configuration to be applied for an aerodrome group by selecting another aerodrome configuration from a predefined configuration list, and/or to change the date and time that the configuration is planned to be activated.. ",
            "messages": [
              {
                "name": "PlanifyNextAerodromeGroupConfiguration",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          }
        ],
        "endpoints": [
          {
            "name": "AerodromeConfigurationManagementProvider",
            "url": "For security reasons, the addresses will be communicated only to Customers"
          }
        ],
        "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "name": "AirspacePlanningManagementProvider",
        "description": "This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Planning data.",
        "provisionSide": "PROVIDER_SIDE",
        "operations": [
          {
            "name": "createARESTimesheet",
            "description": "Allows to add a timesheet into an ARES timetable to define new activation periods.The input parameters shall be the originator, the ARES name and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity.. ",
            "messages": [
              {
                "name": "CreateARESTimesheet",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "createCDRTimesheet",
            "description": "Allows to add a timesheet to a CDR.The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the timesheet data containing an activation time period, and optionally the activation levels and/or a periodicity.. ",
            "messages": [
              {
                "name": "CreateCDRTimesheet",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "deleteARESTimesheet",
            "description": "Allows to remove an existing activation periods timesheet from an ARES timetable.The input parameters shall be the originator, the ARES name and the identifier of the timesheet to remove.. ",
            "messages": [
              {
                "name": "DeleteARESTimesheet",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "deleteCDRTimesheet",
            "description": "Allows to remove an existing activation periods timesheet from a CDR timetable.The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the identifier of the timesheet to remove.. ",
            "messages": [
              {
                "name": "DeleteCDRTimesheet",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "updateARESTimesheet",
            "description": "Allows to update an existing activation periods timesheet for an ARES.The input parameters shall be the originator, the ARES name, the identifier of the timesheet to update and the timesheet data containing the activation levels, an activation time period, and optionally a periodicity.. ",
            "messages": [
              {
                "name": "UpdateARESTimesheet",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "updateCDRTimesheet",
            "description": "Allows to update an existing CDR timesheet.The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR), the identifier of the timesheet to update and the timesheet data containing an activation time period, and optionally the activation levels and/or periodicity.. ",
            "messages": [
              {
                "name": "UpdateCDRTimesheet",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          }
        ],
        "endpoints": [
          {
            "name": "AirspacePlanningManagementProvider",
            "url": "For security reasons, the addresses will be communicated only to Customers"
          }
        ],
        "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "name": "AirspaceStatusManagementProvider",
        "description": "This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Status data.",
        "provisionSide": "PROVIDER_SIDE",
        "operations": [
          {
            "name": "unlockARESActivationStatus",
            "description": "Enables to unlock a previous manual ARES activation status.The input parameters shall be the originator and the ARES name. . ",
            "messages": [
              {
                "name": "UnlockARESActivationStatus",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "updateARESActivationStatus",
            "description": "Enables to update the following ARES data:- the status (activated or deactivated),- the comment associated to the ARES.The input parameters shall be the originator, the ARES name and the ARES status.. ",
            "messages": [
              {
                "name": "UpdateARESActivationStatus",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "unlockCDRStatus",
            "description": "Enables to unlock a previous manual CDR status.The input parameters shall be the originator and the CDR identifier (airway name and names of the start and last points of the CDR).. ",
            "messages": [
              {
                "name": "UnlockCDRStatus",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "updateCDRStatus",
            "description": "Enables to lock the CDR status to open or closed.The input parameters shall be the originator, the CDR identifier (airway name and names of the start and last points of the CDR) and the CDR status.. ",
            "messages": [
              {
                "name": "UpdateCDRStatus",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "addARESComment",
            "description": "Allows to define, update or remove a comment to a given ARES.. ",
            "messages": [
              {
                "name": "AddARESComment",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          }
        ],
        "endpoints": [
          {
            "name": "AirspaceStatusManagementProvider",
            "url": "For security reasons, the addresses will be communicated only to Customers"
          }
        ],
        "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "name": "RadioFrequencyAllocationManagementProvider",
        "description": "This Service Interface exposes operations used by the Operational Supervisor to modify the Radio Frequency Allocation.",
        "provisionSide": "PROVIDER_SIDE",
        "operations": [
          {
            "name": "updateFrequency",
            "description": "Allows a consumer to modify the radio frequency assigned to control responsibility(ies):-either by selecting a new radio frequency,-or by reverting back to the predefined value (off-line defined) of the radio frequency assigned to the given control responsibility (if it has been on-line updated before).The input parameters shall be:-the value of the new radio frequency and the controlResponsibility(ies) where the indicated frequency shall be assigned,-or the controlResponsibility(ies) where the default frequency shall be assigned.When the aim of this operation is to :-apply a new frequency to one or several Responsibilities, frequency should be filled-revert to default frequency for one or several Responsibilities, revertToDefaultFreq should be set to TRUE and frequency shouldn't be filled. ",
            "messages": [
              {
                "name": "UpdateFrequency",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "updateFrequencyPlan",
            "description": "Allows a consumer to change the current radio frequency allocation:-either by selecting a new radio frequency allocation plan among the predefined radio frequency configurations,-or by reverting back to the predefined default radio frequency configuration (offline defined). The input parameters shall be:-the name of the requested ATSUSectorConfiguration,-and the name of the radio frequency configuration to load in place of the current one (except on the operation of reverting back to the default one: in this case this is the default radio frequency configuration which will be loaded).When the aim of this operation is to :-apply a new plan to an ASTUSectorConfiguration, radioFrequencyAllocationName should be filled-revert to default frequency plan an ASTUSectorConfiguration, revertToDefaultPlan should be set to TRUE and radioFrequencyAllocationName shouldn't be filled. ",
            "messages": [
              {
                "name": "UpdateFrequencyPlan",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          }
        ],
        "endpoints": [
          {
            "name": "RadioFrequencyAllocationManagementProvider",
            "url": "For security reasons, the addresses will be communicated only to Customers"
          }
        ],
        "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      },
      {
        "name": "SectorConfigurationManagementProvider",
        "description": "This Service Interface exposes operations used by the Operational Supervisor to modify the Sector Configuration Data.",
        "provisionSide": "PROVIDER_SIDE",
        "operations": [
          {
            "name": "activateSectorMapping",
            "description": "Enables to activate a sector mapping: the supervisor selects a mapping (next or pre-defined mapping) that will replace the current mapping of the concerned ASTUSectorConfiguration.The supervisor may also choose to revert back to the pre-defined default sector mapping. If not, the input parameters shall be the identifier and the state (next or pre-defined) of the origin sector mapping. As a consequence, the parameter sectorMappingId is MANDATORY when the parameter revertToDefaultMapping is not filled or set to FALSE (but if revertToDefaultMapping is set to YES, sectorMappingId is not needed).. ",
            "messages": [
              {
                "name": "ActivateSectorMapping",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "updateSectorMapping",
            "description": "Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration.. ",
            "messages": [
              {
                "name": "UpdateSectorMapping",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "loadNextSectorMapping",
            "description": "Enables to load a pre-defined mapping as being the next mapping of a given ASTUSectorConfiguration.The input parameters shall be:-the ATSUSectorConfigurationIdentifier,-the identifier of the sectorMapping.. ",
            "messages": [
              {
                "name": "LoadNextSectorMapping",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "deleteSectorMapping",
            "description": "Enables to delete a given sector mapping. Only the next sector mapping can be deleted.The input parameter is the identifier of the concerned ATSUSectorConfiguration (sufficient to delete a next mapping knowing that only one next sector mapping per ATSUSectorConfiguration).. ",
            "messages": [
              {
                "name": "DeleteSectorMapping",
                "direction": "IN"
              },
              {
                "name": "OperationalConfigurationResponse ",
                "direction": "OUT"
              }
            ]
          }
        ],
        "endpoints": [
          {
            "name": "SectorConfigurationManagementProvider",
            "url": "For security reasons, the addresses will be communicated only to Customers"
          }
        ],
        "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      }
    ]
  }
}