CCS OperationalConfigurationManagement

Abstract

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:

- 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

Note: Only civil flights are handled by CCS services.

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.

Service retired from 20/03/2023

Categorisation

Service Type

SERVICE_DESCRIPTION

Life Cycle Stage

RETIRED

Business Activity Type

INFORMATION_MANAGEMENT

Intended Consumer

CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER

Information Exchange Category

FLIGHT_INFORMATION_EXCHANGE

Provider

DSNA&ENAV

Description

DSNA: the French air navigation service provider

ENAV; the Italian air navigation service provider

Type

CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER

Point of Contact

Restricted

Contact Information

Restricted

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

Name

Update sector mapping

Description

Update sector mapping

Real World Effect

Change the operational configuration of the ATSU

Name

Activate sector mapping

Description

Activate sector mapping

Real World Effect

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

Real World Effect

Change and lock the activation status of the ARES

Name

Unlock ARES activation status

Description

Unlock ARES activation status

Real World Effect

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

Real World Effect

Change and lock the status of the CDR to open or closed.

Name

Unlock CDR activation status

Description

Unlock CDR activation status

Real World Effect

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

Real World Effect

Delete the next operational configuration of the ATSU, if any

Name

Load next sector mapping

Description

Load next sector mapping

Real World Effect

Change the next operational configuration of the ATSU (using an off-line pre-defined sector mapping)

Name

Create CDR timesheet

Description

Create CDR timesheet

Real World Effect

Add a timesheet to a CDR

Name

Delete ARES timesheet

Description

Delete ARES timesheet

Real World Effect

Remove an existing activation periods timesheet from an ARES timetable

Name

Delete CDR timesheet

Description

Delete CDR timesheet

Real World Effect

Remove an existing timesheet from a CDR

Name

Update ARES timesheet

Description

Update ARES timesheet

Real World Effect

Update an existing activation periods timesheet for an ARES

Name

Update CDR timesheet

Description

Update CDR timesheet

Real World Effect

Update an existing CDR timesheet

Name

Add a comment for an ARES

Description

Add a comment for an ARES

Real World Effect

Define a comment for an ARES

Name

Modify aerodrome runway configuration

Description

Modify aerodrome runway configuration

Real World Effect

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

Real World Effect

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

Real World Effect

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

Real World Effect

For a given aerodrome, modify the configuration parameters

Name

Delete a next aerodrome group configuration

Description

Delete a next aerodrome group configuration

Real World Effect

For a given aerodrome group, remove the next configuration

Name

Activate a new aerodrome group configuration

Description

Activate a new aerodrome group configuration

Real World Effect

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

Real World Effect

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

Real World Effect

Add a timesheet into an ARES timetable to define new activation periods

Information ownership

IPRIn 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).Access to the ServiceThis service is provided to Service Consumers under a contractual basis signed between the CCS Service Provider and the Service Consumer.
Dependencies with other CCS Services

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.
Alignment to SESAR Virtual Centre activity

This service will be updated to be as much as possible in line with the Service Definition produced by SESAR Virtual Centre activities
Service versioning

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.
KPIs monitoring

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.
Confidentiality and integrity

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.
Authentication and authorisation

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.

AC

Airspace Configuration
ACC

Area Control Centre
ADES

Aerodrome of Destination
ADSP

ATM Data Service Provider
AFTN

Aeronautical Fixed Telecommunication Network
AIRM

ATM Information Reference Model
ALRS

Alerting Service
AMQP

Advanced Message Queuing Protocol
ANSP

Air Navigation Service Provider
AOR

Area Of Responsibility
APL

Abbreviated Flight Plan
APOC

Airport Operator
ARES

Airspace Reservations
ASD

Airspace Status Distribution
ASM

Airspace Status Management
ATC

Air Traffic Control
ATCO

Air Traffic Control Officer
ATCS

Air Traffic Control Services
ATFCM

Air Traffic Flow and Capacity Management
ATM

Air Traffic Management
ATS

Air Traffic Services
ATSU

Air Traffic Service Unit
CCS

Coflight Cloud Services
CDM

Collaborative Decision Making
CDR

Conditional Route
CFMU

Central Flow Management Unit
CWP

Controller Working Position
DCB

Demand and Capacity Balancing
DSNA

Direction des Services de la Navigation A0xC3 0xA9rienne (French ANSP)
EAP

Extended ATC Planner
EATMA

European ATM Architecture
ENAV

Ente Nazionale Assistenza al Volo (Italian ANSP)
FAB

Functional Airspace Block
FABEC

Functional Airspace Block Europe Central
FDD

Flight Data Distribution
FDM

Flight Data Management
FDO

Flight Data Operator
FDPS

Flight Data Processing System
GAT

General Air Traffic
HMI

human machine Interface
ICAO

International Civil Aviation Organization
ID

Identifier
IFR

Instrument Flight Rules
IKE

Internet Key Exchange
INAP

Integrated Network Management and ATC planning
IP

Internet Protocol
IPSEC

Internet Protocol Security protocol
IPV4

Internet Protocol version 4
JU

Joint Undertaking
KPI

Key Performance Indicator
LTM

Local Traffic Manager
MB

Mega byte
MSA

Multi-sector area
NOP

Network Operation Plan
NTP

Network Time Protocol
OCSP

Online Certificate Status Protocol
OE

Operational Entity
OPSUP

Operational Supervision
PKCS

Public-Key Cryptography Standards
SDD

Service Definition Document
SESAR

Single European Sky Air Traffic Management Research
SFPL

System Flight Plan
SLA

Service Level Agreement
SSD

SWIM Service Description
SSI

Synchronous Serial Interface
SWIM

System Wide Information Management
TAD

Technical Architecture Description
TBC

To Be Confirmed
TBD

To Be Defined
TCP

Transfer Control Protocol
TDA

Temporary Danger Area
TI

Technical Infrastructure
TLS

transport level security
TSA

Temporary Segregated Area
UTC

Coordinated Universal Time

Name

Service Information Definition

Time synchronisation

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.
Provider-Customer interface-Exchange patterns

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://..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 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.
Provider-Customer interface-Connection management

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.
Provider-Customer interface-Queue management

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

AerodromeConfigurationManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify the Aerodrome Configuration Data.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- modifyRunwayConfiguration
  
  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..
  git
  Messages
  
  ModifyRunwayConfiguration
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- activateAerodromeGroupConfiguration
  
  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..
  git
  Messages
  
  ActivateAerodromeGroupConfiguration
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- deleteNextAerodromeGroupConfiguration
  
  Allows removing the fact that an aerodrome group configuration is identified as the next one..
  git
  Messages
  
  DeleteNextAerodromeGroupConfiguration
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- modifyAerodromeConfiguration
  
  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..
  git
  Messages
  
  ModifyAerodromeConfiguration
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- planifyNextAerodromeGroupConfiguration
  
  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..
  git
  Messages
  
  PlanifyNextAerodromeGroupConfiguration
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
Endpoints

Restricted
AirspacePlanningManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Planning data.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- createARESTimesheet
  
  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..
  git
  Messages
  
  CreateARESTimesheet
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- createCDRTimesheet
  
  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..
  git
  Messages
  
  CreateCDRTimesheet
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- deleteARESTimesheet
  
  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..
  git
  Messages
  
  DeleteARESTimesheet
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- deleteCDRTimesheet
  
  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..
  git
  Messages
  
  DeleteCDRTimesheet
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- updateARESTimesheet
  
  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..
  git
  Messages
  
  UpdateARESTimesheet
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- updateCDRTimesheet
  
  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..
  git
  Messages
  
  UpdateCDRTimesheet
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
Endpoints

Restricted
AirspaceStatusManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify on-line Airspace (ARES or CDR) Status data.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- unlockARESActivationStatus
  
  Enables to unlock a previous manual ARES activation status.The input parameters shall be the originator and the ARES name. .
  git
  Messages
  
  UnlockARESActivationStatus
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- updateARESActivationStatus
  
  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..
  git
  Messages
  
  UpdateARESActivationStatus
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- unlockCDRStatus
  
  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)..
  git
  Messages
  
  UnlockCDRStatus
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- updateCDRStatus
  
  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..
  git
  Messages
  
  UpdateCDRStatus
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- addARESComment
  
  Allows to define, update or remove a comment to a given ARES..
  git
  Messages
  
  AddARESComment
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
Endpoints

Restricted
RadioFrequencyAllocationManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify the Radio Frequency Allocation.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- updateFrequency
  
  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.
  git
  Messages
  
  UpdateFrequency
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- updateFrequencyPlan
  
  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.
  git
  Messages
  
  UpdateFrequencyPlan
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
Endpoints

Restricted
SectorConfigurationManagementProvider

This Service Interface exposes operations used by the Operational Supervisor to modify the Sector Configuration Data.

PROVIDER_SIDE

SYNCHRONOUS_REQUEST_RESPONSE
- activateSectorMapping
  
  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)..
  git
  Messages
  
  ActivateSectorMapping
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- updateSectorMapping
  
  Enables to modify a current mapping or a next mapping of a given ATSUSectorConfiguration..
  git
  Messages
  
  UpdateSectorMapping
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- loadNextSectorMapping
  
  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..
  git
  Messages
  
  LoadNextSectorMapping
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
- deleteSectorMapping
  
  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)..
  git
  Messages
  
  DeleteSectorMapping
  
  IN
  
  OperationalConfigurationResponse
  
  OUT
Endpoints

Restricted

CCS AIRM mapping OPSUPM service

AIRM traceability for CCS Operational Configuration Management service payload

AIRM_TRACE

1.0
CCS Validation evidence document - OperationalConfigurationManagement

Validation evidence for CCS Operational Configuration Management service

SERVICE_VALIDATION_REPORT

1.0
CCS_operationalConfigurationManagement.proto

Protobuf files describing the exchanged information

MACHINE_READABLE_SERVICE_DESCRIPTION

4.2.2.2
CCS_common.proto

Protobuf file describing the exchanged information common to two or more CCS Services

MACHINE_READABLE_SERVICE_DESCRIPTION

5.5.1.2
metadata.proto

Protobuf file describing the metadata used by the CCS Services

MACHINE_READABLE_SERVICE_DESCRIPTION

v1.2.0.0
CCS Operational Configuration Management Service Description

Complete service specification

SERVICE_SPECIFICATION

5.2.2.5
CCS Errors Management Document

Document that includes the list of all applicable error messages for CCS services

SERVICE_SPECIFICATION

2.0

Title

EUROCONTROL Specification for SWIM - Service Description

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION

Conformance Statement

Description of Service according to EUROCONTROL specifications

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

Title

EUROCONTROL Specification for SWIM - Information Definition

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_INFORMATION_DEFINITION

Conformance Statement

Information definition according to EUROCONTROL specifications

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.

Title

EUROCONTROL Specification for SWIM - Technical Infrastructure (TI) Yellow Profile

Standard Type

EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE

Conformance Statement

Implementation of service and network bindings

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

CCS OperationalConfigurationManagement v 2.0.0

Categorisation

Provider