Task Status
This page is part of the ongoing SWIM communities of interest discussions. The content is working material. It should not be treated as final as it is still subject to review, comment and change.
Guidance
This template allows for the documentation of service definitions based on the requirements found at: /wiki/spaces/SCOI/pages/59605116
General requirements to remember:
SWIM-DEFN-010 | Service definition coverage | A service definition shall define a single service | Note: This concerns the definition of a service that can be implemented by service providers. It is not used to describe a running service - use a service description in that case. Note: This requirement uses "define" rather than "describe". |
SWIM-DEFN-020 | Service definition language | The textual descriptions in a service definition shall be written in English using the spelling listed as the primary British spelling when conflicting spellings exist. | - |
Status Key
- TBD - No work has started
- WORKING - Content is being worked on, comments discussed
- DRAFT - Draft is ready, comments resolved
- REVIEWED - Group has reviewed, edited the final draft
- AGREED - Content is finalised and agreed
Service Definition Identification
TBD
Trace
service definition identification | title | Service definition for the Quantitative Volcanic Ash Information Subscription and Request Service |
---|---|---|
edition | 00.00.01 | |
reference date | 2024-01-23 |
Service Identification
TBD
Trace
service identification | service name | Quantitative Volcanic Ash Information Subscription and Request Service |
---|
Service Abstract
TBD
Trace
service abstract | The Quantitative Volcanic Ash Information Subscription and Request Service provides the service consumer with .... tbd The service consumer can subscribe to the service, specifying what sort of information is of interest, and receive information as it becomes available. It is also possible to send a direct request, using a request-reply mechanism, to the service to get the relevant meteorological information. The meteorological information is issued by the designated Volcanic Ash Advisory Centre (VAAC). The meteorological information is only intended to be used by service consumers within the aviation domain. |
---|
Service Definition Provider
TBD
Trace
service definition provider | name | EUROCONTROL |
---|---|---|
description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. | |
point of contact | swim@eurocontrol.int |
Geographical Extent of Information
WORKING
Trace
geographical extent of information | The service shall offer meteorological information concerning volcanic eruptions occurring in its area of responsibility. The service shall offer the equivalent meteorological information for the areas of responsibility it acts as back-up for when there is an outage based on mutual agreements between service providers. Check air navigation plan for the back-ups. Note: the ash cloud may extend beyond the area of responsibility. |
---|
Service Categories
TBD
Trace
Service Standard Reference
TBD
Trace
Explanatory note
This field is left empty.
service standard reference | reference | |
---|---|---|
implemented options | ||
deviations/additions |
Operational Environment
WORKING
Trace
operational environment | operational needs | Agreed at MET Panel IAVW (international ariways volcano watch). T+24 time. -- Flyer: the quantitative volcanic ash (QVA) concentration information (hereafter referred to as ‘QVA information’) that is planned to be provided by volcanic ash advisory centres (VAAC) as part of the International Civil Aviation Organization’s (ICAO) International Airways Volcano Watch (IAVW). QVA information offers operators the opportunity to move away from traditional discernible/visible ash criteria and instead use certified engine susceptibility for flight route planning and inflight replanning. -- QVA information provides users with a high-resolution four-dimensional representation of a volcanic ash cloud, providing a more realistic depiction of the ash cloud. The 3-hourly timesteps of QVA information provides users with more accurate forecast positions of the ash cloud, compared to the 6-hourly timesteps of the VAA/VAG. QVA information will likely have its greatest utility with ash cloud events that have a widely dispersed ash cloud with mostly lower levels of ash concentration. Operators with approval and procedures/practices, e.g., maintenance for planned flight into select thresholds of ash concentration, will be able to use QVA information to fly more efficient routes in accordance with their safety management program. Probabilistic QVA information is intended for use in operator’s flight planning and decision support systems. Operators will use probabilistic QVA information in conjunction with their safety management program to optimise airspace and plan more efficient routes during significant volcanic ash cloud events. -- ATM needs to know about the occurrence or expected occurrence of specified ... that may affect the safety of aircraft operations, and of the development of those phenomena in time and space. A list of operational needs that this service contributes to satisfying is available in Appendix C. This service satisfies these by offering meteorological information as regulated by Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 and ICAO Annex 3. The scope of the meteorological information satisfies the EU Implementing Regulation 2021/116 - Common Project One. | |
---|---|---|---|
capabilities | The service provides high quality, up-to-date, trusted, regulated meteorological information in digital form for use by service consumers within the aviation domain. | ||
information exchange requirements | The service shall take into account the following...
|
Service Functions
WORKING
Trace
service functions | function | name | Request ... meteorological information |
---|---|---|---|
description | The service consumer shall be able to request ... meteorological information filtered by erupting volcano number, forecast timesteps and logical (e.g. severity threshold) operators. ... and selection of payload type IWXXM polygons gridded data deterministic gridded data probablistic | ||
real-world effect | The meteorological information is received and can be used in ATM and other systems. | ||
function | name | Subscribe to ... meteorological information | |
description | The service consumer shall be able to subscribe/unsubscribe in order to receive information based ... when a significant ash cloud | ||
real-world effect | The service consumer subscribes to information offered by the service. | ||
function | name | Distribute ... warning | |
description | When new ... meteorological information is available, it shall be distributed to the subscribers or via a warning with details on how to access the information | ||
real-world effect | The service consumer is sent a message |
Service Access and Use Conditions
TBD
Trace
service access and use conditions | legal constraints | ||
---|---|---|---|
service policies | business policy | ||
operational policy | There shall be a service policy to ensure that only service consumers within the aviation domain can use the service. The service policy shall include a requirement that service consumers cannot pass the information obtained from the service to non-aviation users without prior authorisation from the service provider. | ||
technical policy | |||
service consumption constraints |
Security Constraints
TBD
Trace
security constraints | authentication | The service shall ensure consumer authentication in accordance with the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate or the use of a username/password. The service shall ensure provider authentication in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate. |
---|---|---|
authorisation | The service shall ensure that satisfactory authorisation is put in place according to EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070. | |
confidentiality | The service shall ensure point-to-point confidentiality in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above. | |
integrity | The service shall ensure point-to-point integrity in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above. |
Quality of Service
TBD
Trace
quality of service | performance | capacity | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. |
---|---|---|---|
response time | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | ||
reliability | availability | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | |
recoverability | The service shall achieve a quality that is sufficient to ensure the service is fit for purpose. | ||
security | confidentiality | The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. | |
integrity | The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. |
Quality of Data
TBD
Trace
quality of data | The meteorological information offered by the service shall satisfy the applicable sections of Commission Implementing Regulation (EU) 2017/373 of 1 March 2017, taking into account the specific requirements for providers of meteorological services in the Acceptable Means of Compliance (AMC) and Guidance Material (GM) to Part-MET. The meteorological information offered by the service shall satisfy the quality requirements expressed in ICAO Annex 3. |
---|
Source of Information
TBD
Trace
source of information | source | The service provider shall ensure that the meteorological data offered by the services is received from the appropriate authorised originating sources. This includes:
|
---|
Service Validation Information
TBD
Trace
Explanatory note
This field is left empty.
service validation information | description |
---|
Application Message Exchange Pattern
TBD
Trace
application message exchange pattern |
---|
Service Behaviour
TBD
Trace
service behaviour | typical behaviour | The service behaviour shall be in accordance with the patterns detailed in the Message Exchange Patterns: Identification Guidelines. The interfaces have different behaviour. A combination of an AMQP 1.0 implementation and an OGC implementation shall be used for the basic behaviour. The typical behaviour for PUBLISH_SUBSCRIBE means that:
The typical behaviour for REQUEST_REPLY (as used in Quantitative Volcanic Ash Information Subscription and Request Service Request Interface) is as follows: Synchronous Request/Reply
|
---|
Service Monitoring
TBD
Trace
service monitoring | A service monitoring mechanism should be made available to service consumers. |
---|
Service Interfaces
TBD
Trace
service interfaces | interface | name | Quantitative Volcanic Ash Information Subscription and Request Service Request Interface |
---|---|---|---|
description | Allows the service consumer to request filtered meteorological information. Note: This interface is used to group the operations offered by the chosen OGC standard. | ||
provider/consumer side | Provider side | ||
interface | name | Quantitative Volcanic Ash Information Subscription and Request Service Subscription Interface | |
description | Allows the service consumer to select and subscribe to meteorological information of interest. It allows the service consumer to manage the subscriptions e.g. to unsubscribe. Note: This is an optional interface. Many service providers will prefer to receive subscription requests by email. | ||
provider/consumer side | Provider side | ||
interface | name | Quantitative Volcanic Ash Information Subscription and Request Service Distribution Interface | |
description | Allows the service provider to distribute updated meteorological information meeting the need of the service consumer that has subscribed for updates. | ||
provider/consumer side | Provider side |
SWIM TI Profile and Interface Bindings
TBD
Trace
Quantitative Volcanic Ash Information Subscription and Request Service Request Interface
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile |
---|---|---|
profile version | 1.1 | |
selected service interface binding | WS_LIGHT | |
selected network interface binding | The service shall use the network bindings of the SWIM TIYP. | |
description | The interface shall use at least one of the following OGC standards:
Note: It is expected that the service will implement the OGC API – Environmental Data Retrieval Standard by November 2026. |
Quantitative Volcanic Ash Information Subscription and Request Service Subscription Interface
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile |
---|---|---|
profile version | 1.1 | |
selected service interface binding | ||
selected network interface binding | The service shall use the network bindings of the SWIM Technical Infrastructure (TI) Yellow Profile. | |
description |
Quantitative Volcanic Ash Information Subscription and Request Service Distribution Interface
SWIM TI profile and interface bindings | profile name | EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile |
---|---|---|
profile version | 1.1 | |
selected service interface binding | SWIM_TI_YP_1_1_AMQP_MESSAGING | |
selected network interface binding | The service shall use the network bindings of the SWIM TIYP. | |
description | AMQP 1.0 shall be used to distribute messages as explained in the Publish/Subscribe Push MEP: Implementation Guidance. |
Service Interface Protocols and Data Format
TBD
Trace
service interface protocols and data format | transport / messaging protocols | The service shall use TLS1.2 or later in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile. |
---|---|---|
data format | QVA information will be provided in two file formats. Objects will be provided in ICAO’s Meteorological Information Exchange Model (IWXXM) format. Check version number. Gridded data will be provided NetCDF. This is captured at Service Message level (see below). WS_LIGHT does not mandate a data format. The header expresses what is used. |
Service Operations
TBD
Trace
Quantitative Volcanic Ash Information Subscription and Request Service Request Interface
Explanatory note
The OGC Web Feature Service 2.0 Interface Standard is used to implement the service operations. It is not the intention to repeat the standardised operations here. However, the table below illustrates how the GetFeature operation would look in the context of this service.
Service operations | operation | operation name | GetFeature |
---|---|---|---|
description | The GetFeature operation returns a selection of features from a data store. It responds to a GetFeature Request message with a Quantitative Volcanic Ash Information Message that satisfies the query expressions specified in the request. | ||
messages | Request, En-route Significant Weather Information Message |
Quantitative Volcanic Ash Information Subscription and Request Service Subscription Interface
Service operations | reference | url | Meteorological SWIM Services Subscription Interface Standard |
---|---|---|---|
description | The standard operations for subscription and subscription management. |
Quantitative Volcanic Ash Information Subscription and Request Service Distribution Interface
Service operations | operation | operation name | publish |
---|---|---|---|
description | This operation allows the service provider to publish Quantitative Volcanic Ash Information Message to service consumers based on their subscriptions. | ||
messages | Quantitative Volcanic Ash Information Message |
Service Messages
TBD
Explanatory note
The OGC Web Feature Service 2.0 Interface Standard details the basic messages such as request and response messages. It is not the intention to repeat the standardised messages here. The table below provides extra details for the Meteorological Aerodrome Forecast Message.
Trace
service messages | message | name | Reply Add:
|
---|---|---|---|
description | The output message containing the ... meteorological information. | ||
direction | Out | ||
data format | IWXXM: sets of features/objects for the 4 thresholds below.
This is an update from the Flyer: The QVA information in IWXXM form will be provided as ‘objects’ (i.e. IWXXM features) for the very high, high, medium, and low concentration ranges. --- Gridded just gives the concentration - there is no assignment to low, medium, etc. | ||
message | name | Request | |
description | Request message submitted to the service containing query expressions for the GetFeature or EDR quivalent (http get) operation. can select data format | ||
direction | In | ||
data format | |||
message | name | Distribution QVA notification message | |
description | The alert and way to access the request | ||
direction | Out | ||
data format | JSON and/or XML | ||
reference | url | Meteorological SWIM Services Subscription Interface Standard | |
description | The standard messages for subscription and subscription management. |
Information Definition (Minimum) and (Extended)
TBD
Trace
information definition | The service shall offer information available in accordance IWXXM QVA schema. Note: expected to be 2025-2. + for gridded, Clear up NetCDF 4 specification - containing volcanic ash (trace to AIRM). with Appendix B. Flyer: Significant volcanic ash clouds QVA information will be issued for significant volcanic ash clouds. Significant in this context means an ash cloud that poses a widespread impact to aircraft operations and air navigation. |
---|
Filter Encoding
TBD
Trace
filter encoding | The Quantitative Volcanic Ash Information Subscription and Request Service Request Interface shall support the During temporal operator defined in the OGC Filter Encoding 2.0 Encoding Standard. The Quantitative Volcanic Ash Information Subscription and Request Service Request Interface shall support filtering based on the name and ICAO location indicator of the aerodrome of interest.. The Quantitative Volcanic Ash Information Subscription and Request Service Request Interface should support filtering based on the operators defined in the OGC Filter Encoding 2.0 Encoding Standard. The Quantitative Volcanic Ash Information Subscription and Request Service Subscription Interface shall allow for the selection of subscription based on clearly defined criteria. |
---|
Machine-Readable Service Interface Definition
TBD
Trace
Explanatory note
This field is left empty. No machine-readable service interface definition is provided.
machine-readable service interface definition | reference |
---|
Model View
TBD
Trace
Explanatory note
This field is left empty. No model view is provided.
model view | reference |
---|
Abbreviations and Acronyms
TBD
Trace
abbreviations and acronyms | abbreviation | code | AMQP |
---|---|---|---|
term | Advanced Message Queuing Protocol | ||
abbreviation | code | API | |
term | Application Programming Interface | ||
abbreviation | code | CTA | |
term | Control area | ||
abbreviation | code | EU | |
term | European Union | ||
abbreviation | code | FIR | |
term | Flight information region | ||
abbreviation | code | ICAO | |
term | International Civil Aviation Organization | ||
abbreviation | code | MEP | |
term | Message Exchange Pattern | ||
abbreviation | code | OGC | |
term | Open Geospatial Consortium | ||
abbreviation | code | SIGMET | |
term | Information concerning en-route weather phenomena which may affect the safety of aircraft operations. | ||
abbreviation | code | TI | |
term | Technical Infrastructure | ||
abbreviation | code | TIYP | |
term | Technical Infrastructure Yellow Profile | ||
abbreviation | code | TLS | |
term | Transport Layer Security | ||
abbreviation | code | UIR | |
term | Upper flight information region |
Appendix A: References
TBD
Trace
references | reference | title | EU Implementing Regulation 2021/116 - Common Project One |
---|---|---|---|
version | 1 February 2021 | ||
description | Commission Implementing Regulation (EU) 2021/116 of 1 February 2021 on the establishment of the Common Project One supporting the implementation of the European Air Traffic Management Master Plan provided for in Regulation (EC) No 550/2004 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 409/2013 and repealing Commission Implementing Regulation (EU) No 716/2014. | ||
url | https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32021R0116 | ||
document type | |||
reference | title | Commission Implementing Regulation (EU) 2017/373 | |
version | 1 March 2017 (as amended) | ||
description | Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 laying down common requirements for providers of air traffic management/air navigation services and other air traffic management network functions and their oversight, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011, (EU) No 1035/2011 and (EU) 2016/1377 and amending Regulation (EU) No 677/2011. | ||
url | https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02017R0373-20230126 | ||
document type | |||
reference | title | Acceptable Means of Compliance (AMC) and Guidance Material (GM) to Part-MET | |
version | 14/03/2022 | ||
description | |||
url | https://www.easa.europa.eu/en/document-library/acceptable-means-of-compliance-and-guidance-materials/group/part-met#part-met | ||
document type | |||
reference | title | OGC API – Environmental Data Retrieval Standard | |
version | 1.1 | ||
description | OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. | ||
url | https://www.ogc.org/standard/ogcapi-edr/ | ||
document type | |||
reference | title | OGC Web Coverage Service (WCS) Interface Standard | |
version | version 2.1 | ||
description | A Web Coverage Service (WCS) offers multi-dimensional coverage data for access over the Internet. WCS Core specifies a core set of requirements that a WCS implementation must fulfill. | ||
url | https://www.ogc.org/standard/wcs/ | ||
document type | |||
reference | title | OGC API - Coverages | |
version | |||
description | The OGC API - Coverages draft specification defines a Web API for accessing coverages that are modeled according to the Coverage Implementation Schema (CIS) 1.1 | ||
url | https://ogcapi.ogc.org/coverages/ | ||
document type | |||
reference | title | OGC Web Feature Service 2.0 Interface Standard | |
version | |||
description | WFS offers direct fine-grained access to geographic information at the feature and feature property level. Note: This is equivalent to ISO 19142 - Geographic Information - Web Feature Service. | ||
url | https://www.ogc.org/standard/wfs/ | ||
document type | |||
reference | title | OGC API – Features | |
version | |||
description | OGC API Features provides API building blocks to create, modify and query features on the Web. | ||
url | https://www.ogc.org/standard/ogcapi-features/ | ||
document type | |||
reference | title | OGC Filter Encoding 2.0 Encoding Standard | |
version | |||
description | This jointly developed OGC and ISO TC/211 International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. These components are modular and intended to be used together or individually by other standards which reference this International Standard. Note: This is equivalent to ISO 19143 - Geographic Information - Filter encoding. | ||
url | https://www.ogc.org/docs/is | ||
document type | |||
reference | title | Message Exchange Patterns: Identification Guidelines | |
version | JULY 2nd, 2019 | ||
description | Document intended to facilitate the understanding of message exchange patterns from an application and Technical Infrastructure perspective. | ||
url | https://reference.swim.aero/technical-infrastructure/message-exchange-patterns-identification-guidelines.html | ||
document type | SERVICE_BEHAVIOUR_DESCRIPTION | ||
reference | title | Publish/Subscribe Push MEP: Implementation Guidance | |
version | JULY 2nd, 2019 | ||
description | This document intends to serve as implementation guidance of the Publish/Subscribe Push Message Exchange Pattern using SWIM-TI Yellow Profile Service Bindings. | ||
url | https://reference.swim.aero/technical-infrastructure/guidance-for-pub-sub-push-implementation.html | ||
document type |
Appendix B: Information Definition
TBD
The message shall include the following metadata:
- Location covered by the message
- Responsible organisation
- Validity of the message
The message shall include the following meteorological information when relevant:
- Volcanic ash (including volcano name, if known)
Appendix C: Operational Needs
TBD
Transversal
- Support integration of existing and/or tailored weather information with operational processes to aid decision-making and improve understanding of the operational impact of adverse weather.
By service consumer role
Stakeholder/Role | Description of stakeholder/role | Needs for en-route significant weather information | Notes |
---|---|---|---|
CIVIL_AIRSPACE_USER | A generic term designating an organization operating aircraft and its pilots, the flight operations centres (FOC) responsible for the strategic planning of a flight and the entity responsible for the execution of a flight which is traditionally a flight deck. | ||
MILITARY_AIRSPACE_USER | Airspace User under the authority of a military organisation. | ||
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for general air traffic. | ||
MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for military air traffic. | ||
AIR_TRAFFIC_SERVICE_PROVIDER | A generic term meaning variously, flight information service, alerting service, air traffic advisory service, air traffic control service (area control service, approach control service or aerodrome control service). | ||
REGULATED_METEOROLOGICAL_SERVICE_PROVIDER | An office designated to provide meteorological service for international air navigation. | This role is not recognised by the SESAR Deployment Program as a service consumer. However, it is recognised in ATM Master Plan (https://atmmasterplan.eu/data/enablers/20417016.) Moreover, looking at the EU Reg. 2017/373, a MET Service Provider has to support stakeholders and for that MET-data is needed from other MET-providers. Also such MET-data is needed for their own purpose to evaluate the correctness of forecasts. | |
AERONAUTICAL_INFORMATION_SERVICE_PROVIDER | A service established within the defined area of coverage responsible for the provision of aeronautical information/data necessary for the safety, regularity and efficiency of air navigation. |
| |
A provider of CNS services. |
| ||
PROVIDER_OF_DATA_SERVICES | A public or private entity responsible for the management of a Data Service Provision (e.g. to one or several Virtual Centre). | ||
NETWORK_MANAGER | The organization responsible for enabling the optimum use of airspace and ensure that Airspace Users can operate preferred trajectories while allowing maximum access to airspaces and air navigation services. | ||
AIRPORT_OPERATOR | The civilian or military agency, group or individual which exercises control over the operations of the civil airport or military airfield. |
| |
AIRSIDE_GROUND_HANDLER | A stakeholder involved in the services necessary for an aircraft's arrival at, and departure from, an airport, other than air traffic services. | ||
MILITARY_DEFENCE_CENTRE | A military defence centre. Note: these centres, e.g., check for diplomatic clearance. |
|