{
  "informationServiceDescription": {
    "title": "CoordinationAndTransferManagement Service",
    "referenceDate": "2026-05-22",
    "edition": "1.4.3",
    "serviceAbstract": "<p>This SWIM Service addresses the manual interactions between the 4-Flight ATM Data Service Provider (ADSP) and the CWP in the context of Virtual Centre, for managing Coordination and Transfer operations. The CWP will receive a reply when the service request has been completed, indicating the status of the request.</p><p>Please note that the use of CoordinationAndTransferManagement service implies the use of FlightDataDistribution Service to get the output Flight Plan Data.</p>",
    "serviceIdentification": {
      "name": "CoordinationAndTransferManagement Service",
      "version": "1.4.3"
    },
    "serviceProvider": {
      "name": "DSNA",
      "abbreviation": "DSNA",
      "description": "<p>DSNA (Direction des Services de la Navigation Aerienne) is the national air navigation services provider of France.</p><p>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.</p><p>Paris ACC : At the crossroads of the biggest European platforms, Paris ACC manage one of the densest 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.</p><p>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\"</p>",
      "type": [
        "PROVIDER_OF_DATA_SERVICES"
      ],
      "pointOfContact": [
        {
          "name": "DSNA FlightData Services Customer Relations",
          "role": "To request information about this service",
          "contactInformation": [
            {
              "type": "EMAIL",
              "address": "bertrand.morvan@aviation-civile.gouv.fr"
            }
          ]
        }
      ]
    },
    "serviceCategorisation": {
      "businessActivityType": [
        "INFORMATION_MANAGEMENT"
      ],
      "intendedConsumer": [
        "AIR_TRAFFIC_SERVICE_PROVIDER",
        "CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER",
        "CIVIL_AIRSPACE_USER",
        "PROVIDER_OF_DATA_SERVICES"
      ],
      "informationCategory": [
        "FLIGHT_INFORMATION_EXCHANGE"
      ],
      "applicationMessageExchangePattern": [
        {
          "name": "SYNCHRONOUS_REQUEST_REPLY"
        }
      ],
      "geospatialCategorisation": {
        "countryCode": [
          "LF"
        ]
      },
      "other": [
        {
          "name": "Service Type: FLIGHT_INFORMATION_FEATURE_MANAGEMENT_SERVICE",
          "value": "FLIGHT_FEATURE_MANAGEMENT_SERVICE"
        }
      ],
      "lifeCycle": [
        {
          "lifeCycleStage": "PROSPECTIVE",
          "from": "2026-06-01",
          "to": "2027-02-09"
        },
        {
          "lifeCycleStage": "OPERATIONAL",
          "from": "2027-02-09"
        }
      ]
    },
    "generalDescription": {
      "operationalEnvironment": {
        "operationalNeeds": [
          {
            "name": "Coordination And Transfer management",
            "description": "<p>The CoordinationAndTransferManagement Service addresses a set of basic APP/TWR operations needed for Coordination and Transfer. It addresses operations related to:</p><p>- activate a Coordination,</p><p>- point out a flight,</p><p>- close a Point session.</p>"
          }
        ]
      },
      "functionality": [
        {
          "name": "Activate Coordination",
          "description": "Process a manual coordination before the automatic event",
          "realWorldEffect": "Triggering of the coordination event for a given transition between two responsibility traversals prior to the automatic coordination event.This is an OLDI ACT (Activate) message equivalent."
        },
        {
          "name": "Point out",
          "description": "Point out  a flight to another controller",
          "realWorldEffect": "The Point message is sent to highlight (ou point out) a flight to another controller(s) within the same ATSU or in adjacent ATSU, in order to facilitate verbal coordination, irrespective of whether co-ordination has taken place.This is a PNT msg equivalent."
        },
        {
          "name": "Close Point out",
          "description": "End a PointOut notification",
          "realWorldEffect": "Used in response to a pointOut notification for formally notifying the system that the notification has been processed by the receiver.This remains a local action between the receiver and his system without any OLDI equivalent message.The originator controller is capable of ending the point session or remove one or some of the target operational entities (eq. OEs) of the Point session, while the designated controller is capable only to remove his OEs from the recipient list (if there is no more recipient, the point session is ended)."
        }
      ],
      "accessAndUseConditions": [
        {
          "name": "Subscription",
          "type": "SERVICE_CONSUMPTION_CONSTRAINT",
          "description": "Consumers needs to contact DSNA to register administratively to this service."
        },
        {
          "name": "Aviation users",
          "type": "SERVICE_POLICY",
          "description": "Only service consumers within the aviation domain can use this service."
        },
        {
          "name": "Non aviation users",
          "type": "SERVICE_POLICY",
          "description": "The service consumers cannot pass the information obtained from the service to non-aviation users without prior authorisation from DSNA."
        },
        {
          "name": "Dependencies with DSNA Services",
          "type": "SERVICE_CONSUMPTION_CONSTRAINT",
          "description": "If the service consumer also consumes other DSNA services, this Service shall be consumed simultaneously with the other DSNA SWIM Services that are part of the contractual agreement between the service consumer and DSNA service provider."
        },
        {
          "name": "Dependency with FDD DSNA Service",
          "type": "SERVICE_CONSUMPTION_CONSTRAINT",
          "description": "The use of this CoordinationAndTransferManagement service implies the use of the FlightDataDistribution DSNA Service to get the output Flight Plan Data."
        },
        {
          "name": "Service versioning",
          "type": "SERVICE_POLICY",
          "description": "At least 2 versions of this swim service could be maintained in the same time, taking benefit the capacities of technologies used in DSNA such as protobuf."
        },
        {
          "name": "Service reviews",
          "type": "SERVICE_POLICY",
          "description": "Services management review are regularly organized with customers to monitor the usability of the services and the KPI related to the quality of service described in the SLA."
        },
        {
          "name": "Internet Accessibility",
          "type": "SECURITY_CONSTRAINT",
          "description": "The interface of DSNA business services is accessible from outside DSNA premises through Internet using IPV4. An IPSEC link (IKE v1 or IKE v2) is used between DSNA provider and customer terminal network equipment."
        },
        {
          "name": "Mutual authentication with X509 certificates",
          "type": "SECURITY_CONSTRAINT",
          "description": "Authentication is required - Mutual authentication with X509 certificates is used between the AMQPS broker and its client established within a TLS session. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer."
        },
        {
          "name": "Confidentiality",
          "type": "SECURITY_CONSTRAINT",
          "description": "The service relies on TLS 1.2 to provide integrity and confidentiality."
        },
        {
          "name": "Integrity",
          "type": "SECURITY_CONSTRAINT",
          "description": "The service relies on TLS 1.2 to provide integrity and confidentiality."
        }
      ],
      "qualitiesOfService": {
        "performance": [
          {
            "name": "Services level objectives",
            "description": "The service level objectives regarding the availability, response time, throughput and recoverability of DSNA Services depend on the purpose (mission) for which the Customer intend to use them (e.g. test, training, operational purpose).These 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 DSNA Customer."
          },
          {
            "name": "Network performance",
            "description": "The minimum Bandwidth required to consume DSNA services (hypothesis for the technical integration service of 300 simultaneous flight managed by the system) is 10MB/s."
          },
          {
            "name": "Rate limitation",
            "description": "Customer 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."
          }
        ],
        "reliability": [
          {
            "name": "Recoverability",
            "description": "The service level objectives regarding the recoverability of the Service depend on the purpose (mission) for which the Customer intend to use it (e.g. test, training or operational purpose).These 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 Customer."
          },
          {
            "name": "Availability",
            "description": "The service level objectives regarding the availability of the Service depend on the purpose (mission) for which the Customer intend to use it (e.g. test, training or operational purpose).These 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 Customer."
          }
        ],
        "security": [
          {
            "name": "Confidentiality",
            "description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer"
          },
          {
            "name": "Integrity",
            "description": "TLS 1.2 is used to provide confidentiality and integrity at transport layer. IPsec is used to provide confidentiality, authentication and integrity at network (internet) layer"
          }
        ]
      },
      "dateInOperation": "2027-02-09",
      "serviceSupport": [
        {
          "name": "Customer Service Support",
          "role": "Customer Support for more information on the service [Business Hours]",
          "contactInformation": [
            {
              "type": "PHONE",
              "address": "+33169577209"
            },
            {
              "type": "PHONE",
              "address": "+33699513411"
            },
            {
              "type": "EMAIL",
              "address": "bertrand.morvan@aviation-civile.gouv.fr"
            },
            {
              "type": "POSTAL",
              "address": "DSNA/DO Batiment 1611 9, rue de Champagne Boite postale 91205 91200 ATHIS-MONS - France"
            }
          ]
        }
      ],
      "validation": [
        {
          "type": "COLLABORATIVE_VALIDATION",
          "description": {
            "evidence": "Prior to any Service publication in the European Swim Registry, this service has been prototyped and validated in the context of SESAR Virtual Centres activities and through the operational 4-FLIGHT program.\r\nDSNA and THALES shall ensure that the interfaces comply with the specifications stated in the ICDs and that the interfaces are adequately tested by both parties as defined in the Interface Responsibility Definition sections of these ICDs."
          }
        }
      ],
      "abbreviations": [
        {
          "name": "ADSP",
          "description": "ATM Data Service Provider"
        },
        {
          "name": "AMQP",
          "description": "Advanced Message Queuing Protocol"
        },
        {
          "name": "ANSP",
          "description": "Air Navigation Service Provider"
        },
        {
          "name": "AOR",
          "description": "Area Of Responsibility"
        },
        {
          "name": "ATC",
          "description": "Air Traffic Control"
        },
        {
          "name": "ATM",
          "description": "Air Traffic Management"
        },
        {
          "name": "ATS",
          "description": "Air Traffic Services"
        },
        {
          "name": "ATSEP",
          "description": "Air Traffic Safety Electronics Personnel"
        },
        {
          "name": "ATSU",
          "description": "Air Traffic Service Unit"
        },
        {
          "name": "CTM",
          "description": "Coordination and Transfer Management"
        },
        {
          "name": "CWP",
          "description": "Controller Working Position"
        },
        {
          "name": "C&T",
          "description": "Coordination And Transfer"
        },
        {
          "name": "DO",
          "description": "Direction des Operations"
        },
        {
          "name": "DSNA",
          "description": "Direction des Services de la Navigation Aerienne (French ANSP)"
        },
        {
          "name": "FDD",
          "description": "Flight Data Distribution"
        },
        {
          "name": "FP",
          "description": "Flight Plan"
        },
        {
          "name": "HTTP",
          "description": "Hypertext Transfer Protocol"
        },
        {
          "name": "IP",
          "description": "Internet Protocol"
        },
        {
          "name": "IPV4",
          "description": "Internet Protocol version 4"
        },
        {
          "name": "KPI",
          "description": "Key Performance Indicator"
        },
        {
          "name": "NTP",
          "description": "Network Time Protocol"
        },
        {
          "name": "SDD",
          "description": "Service Definition Document"
        },
        {
          "name": "SESAR",
          "description": "Single European Sky Air Traffic Management Research"
        },
        {
          "name": "SLA",
          "description": "Service Level Agreement"
        },
        {
          "name": "SSD",
          "description": "SWIM Service Description"
        },
        {
          "name": "SWIM",
          "description": "System Wide Information Management"
        },
        {
          "name": "TCP",
          "description": "Transfer Control Protocol"
        },
        {
          "name": "TI",
          "description": "Technical Infrastructure"
        },
        {
          "name": "TLS",
          "description": "Transport Level Security"
        },
        {
          "name": "URL",
          "description": " Uniform Resource Locator "
        },
        {
          "name": "UTC",
          "description": "Universal Time Coordinated"
        },
        {
          "name": "XML",
          "description": "Extensible Markup Language"
        }
      ]
    },
    "informationDescription": {
      "informationDefinition": [
        {
          "name": "CoordinationAndTransferManagement Service Information Definition",
          "definition": "see SESAR PJ32-WP3 SDD CoordinationAndTransferManagement",
          "airmCorrespondence": "see SESAR SDD C&T - 4.1.0 AIRM Conformance Declaration"
        }
      ]
    },
    "technicalDescription": {
      "technicalConstraint": [
        {
          "name": "Time synchronization",
          "description": "NTP is the standard solution for accurately synchronizing systems to UTC time. So, DSNA Provider and DSNA 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": "Technical behaviour",
          "description": "Each service interface of the DSNA business services relies on the concept of AMQP queues and topics. -The customer shall use an implementation of the AMQP 1.0 specification to connect to the DSNA provider endpoint. -The DSNA provider endpoint is an AMQP 1.0 broker managing queue and topics. The message payloads are encoded following a protobuf format.  The customer acts as requester and subscriber. The DSNA provider acts as responder and publisher.Concerning publish-subscribe, the customer subscribes to a DSNA distribution service by directly listening to an appropriate AMQP topic, which name follows the DSNA derivation rules.The customer requests on the Subscription management queue the creation of a new subscription. The DSNA provider returns on the Reply queue, the address of the Publication queue(s) to receive data (one queue per type of subscribed data).The subscribers can filter the messages they want to receive by using the filter parameters defined for each subscription operation.N.B:-If the DSNA 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 Topics.-More generally, since the distribution events from different services are asynchronous (independent topics), they may be received in a few ms before reaching consistency.Concerning request-reply (used for subscription technical operations or management operations) the DSNA customer sends a request by sending a message to an appropriate AMQP queue, which name follows the DSNA derivation rules, to make a request. The request message contains the name of the queue into the DSNA customer listens and in which the reply from the DSNA provider is expected."
        },
        {
          "name": "Reconnection",
          "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 DSNA customer to try to reconnect regularly."
        },
        {
          "name": "Permission on Topic",
          "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 DSNA customer will have: -Write access on the request queue-Read access on the reply queue -Read access on the topic for distribution service"
        }
      ],
      "serviceMonitoring": {
        "monitoringDescription": "DSNA services are supervised in real time by trained and licensed ATSEPs."
      },
      "behaviour": [
        {
          "name": "Typical Data Management Behaviour",
          "description": "The detailed behaviour of the service is provided in each operation dedicated section"
        }
      ]
    },
    "references": {
      "serviceDocument": [
        {
          "documentType": "SERVICE_STANDARD",
          "title": "SESAR PJ32-WP3 SDD CoordinationAndTransferManagement",
          "version": "V1.0",
          "reference": {
            "description": "CoordinationAndTransferManagement Service Information Definition",
            "url": "https://www.sesarju.eu/sites/default/files/documents/solution/SolPJ.10-W2-93%20TS-IRS%20V3.pdf"
          }
        },
        {
          "documentType": "SERVICE_SPECIFICATION",
          "title": "SWIFT Services Coordination and Transfer Management Service",
          "version": "V1.4.3",
          "description": "SWIM Service Description document (SSD) from 4-FLIGHT SWIFT on which the DSNA CTM Service is based"
        },
        {
          "documentType": "SERVICE_SPECIFICATION",
          "title": "SWIM INTERFACE CONTROL DOCUMENT FOR 4-FLIGHT",
          "version": "02 SW30",
          "description": "Complete service specification"
        },
        {
          "documentType": "SERVICE_STANDARD",
          "title": "ICAO4444 PANS-ATM, Procedures for Air Navigation Services, Rules of the Air and the Air Traffic Services",
          "version": "15th - 2007"
        },
        {
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "title": "CCS_coordinationAndTransferManagement.proto",
          "version": "1.4",
          "description": "<p>Protobuf file describing the exchanged information</p>"
        },
        {
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "title": "CCS_common.proto",
          "version": "1.4.3",
          "description": "Protobuf file describing the exchanged information common to two or more DSNA Services"
        },
        {
          "documentType": "MACHINE_READABLE_SERVICE_DESCRIPTION",
          "title": "metadata.proto",
          "version": "v1.2",
          "description": "Protobuf file describing the metadata used by the DSNA Services"
        }
      ],
      "implementedStandard": [
        {
          "title": "EUROCONTROL Specification for SWIM - Service Description",
          "version": "2.0",
          "description": "Description of Service according to EUROCONTROL specifications",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION",
          "conformanceStatement": "Is compliant"
        },
        {
          "title": "EUROCONTROL Specification for SWIM - Information Definition",
          "version": "1.0",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION",
          "conformanceStatement": "Is compliant"
        },
        {
          "title": "EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile",
          "version": "1.0",
          "standardType": "EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE",
          "conformanceStatement": "Is compliant"
        }
      ]
    },
    "serviceInterface": [
      {
        "name": "CoordinationAndTransferManagementProvider",
        "description": "<p>This Service Interface definition exposes the APP/TWR operations allowing the consumer to perform basic operations needed for Coordination and Transfer. It addresses operations such as: - activateCoordination, - pointOut, - closePointOut.</p>",
        "provisionSide": "PROVIDER_SIDE",
        "operations": [
          {
            "name": "activateCoordination",
            "description": "Allows the operator to trigger a manual coordination before the automatic event",
            "messages": [
              {
                "name": "ActivateCoordination",
                "direction": "IN"
              },
              {
                "name": "CoordinationAndTransferResponse",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "pointOut",
            "description": "Allows the operator to highlight a flight to another controller",
            "messages": [
              {
                "name": "PointOut",
                "direction": "IN"
              },
              {
                "name": "CoordinationAndTransferResponse",
                "direction": "OUT"
              }
            ]
          },
          {
            "name": "closePointOut",
            "description": "Allows the operator to end a PointOut notification",
            "messages": [
              {
                "name": "ClosePointOut",
                "direction": "IN"
              },
              {
                "name": "CoordinationAndTransferResponse",
                "direction": "OUT"
              }
            ]
          }
        ],
        "endpoints": [
          {
            "name": "Endpoint",
            "description": "<p>For security reasons, the addresses will be communicated only to Customers</p>",
            "url": "amqps://"
          }
        ],
        "serviceInterfaceBinding": {
          "name": "SWIM_TI_YP_1_0_AMQP_MESSAGING",
          "description": "Information is exchanged in Protobuf format. Protocol buffers or Protobuf are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data similar to XML, but smaller, faster, and simpler."
        },
        "networkInterfaceBinding": {
          "name": "IPV4_SECURE_UNICAST"
        },
        "messageExchangePattern": "SYNCHRONOUS_REQUEST_RESPONSE"
      }
    ]
  }
}