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
DRAFT
Trace
service definition identification | title | Service definition for the En-route Significant Weather Information Subscription and Request Service |
---|---|---|
edition | 00.00.01 | |
reference date | 2023-06-22 |
Service Identification
REVIEWED
Trace
service identification | service name | En-route Significant Weather Information Subscription and Request Service |
---|
Service Abstract
DRAFT
Trace
service abstract | The En-route Significant Weather Information Subscription and Request Service provides the service consumer with information concerning en-route weather phenomena which may affect the safety of aircraft operations. The service consumer may subscribe to the service to be notified of new information. It is also possible to send a direct request to the service to get the information. The information is issued by the designated Meteorological Watch Office and contains the phenomena such as thunderstorms and severe turbulence as defined in ICAO Annex 3. |
---|
Service Definition Provider
DRAFT
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
DRAFT
Trace
geographical extent of information | The service shall offer information concerning its own FIR at a minimum. The service may offer information concerning other FIRs. |
---|
Service Categories
DRAFT
Trace
service categories | category | category name | regulated information exchange |
---|---|---|---|
value | |||
scheme | |||
category | category name | information domain | |
value | METEOROLOGICAL_INFORMATION | ||
scheme | https://reference.swim.aero/information-services/service-categories/CodeInformationDomainType.html | ||
category | category name | business activity | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeBusinessActivityType.html | ||
category | category name | intended service consumer | |
value | |||
scheme | https://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | intended service provider | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | service type | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeServiceType.html |
Service Standard Reference
DRAFT
Trace
Explanatory note
This field is left empty.
service standard reference | reference | |
---|---|---|
implemented options | ||
deviations/additions |
Operational Environment
DRAFT
Trace
operational environment | operational needs | ATM needs to know about the occurrence or expected occurrence of specified en-route weather and other phenomena in the atmosphere 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 data as regulated by ICAO Annex 3. The scope of the aeronautical data satisfies the EU Implementing Regulation 2021/116 - Common Project One. | |
---|---|---|---|
capabilities | The service provides high quality, up-to-date, trusted, regulated meteorological data in digital form for use in air traffic management systems and other systems. | ||
information exchange requirements |
|
Service Functions
DRAFT
Trace
service functions | function | name | Request en-route significant weather information |
---|---|---|---|
description | The service consumer shall be able to request en-route significant weather information filtered by FIR, phenomenon, and according to spatial, temporal and logical operators. | ||
real-world effect | The en-route significant weather information is received and can be used in ATM and other systems. | ||
function | name | Subscribe to en-route significant weather information | |
description | The service consumer shall be able to subscribe/unsubscribe in order to receive information based on given criteria such as the severity/threshold of the weather phenomenon. | ||
real-world effect | Service consumer subscribes to information offered by the service. | ||
function | name | Distribute en-route significant weather information | |
description | When new data is available, it shall be distributed to the subscribers. | ||
real-world effect | Service consumer is sent a message containing the relevant en-route significant weather information. |
Service Access and Use Conditions
DRAFT
Trace
Explanatory note
This field is left empty.
service access and use conditions | legal constraints | ||
---|---|---|---|
service policies | business policy | ||
operational policy | |||
technical policy | |||
service consumption constraints |
Security Constraints
DRAFT
Trace
security constraints | authentication | The service may offer unauthenticated/public use. If the use is authenticated, 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
DRAFT
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
DRAFT
Trace
quality of data | The meteorological data offered by the service shall satisfy the applicable sections of Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 |
---|
Source of Information
DRAFT
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
DRAFT
Trace
Explanatory note
This field is left empty.
service validation information | description |
---|
Application Message Exchange Pattern
DRAFT
Trace
application message exchange pattern |
---|
Service Behaviour
DRAFT
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 En-route Significant Weather Information Subscription and Request Service Request Interface) is as follows: Synchronous Request/Reply
|
---|
Service Monitoring
DRAFT
Trace
service monitoring | A service monitoring mechanism should be made available to service consumers. |
---|
Service Interfaces
DRAFT
Trace
service interfaces | interface | name | En-route Significant Weather Information Subscription and Request Service Request Interface |
---|---|---|---|
description | |||
provider/consumer side | Provider side | ||
interface | name | En-route Significant Weather Information Subscription and Request Service Subscription Interface | |
description | |||
provider/consumer side | Provider side | ||
interface | name | En-route Significant Weather Information Subscription and Request Service Distribution Interface | |
description | |||
provider/consumer side | Provider side |
SWIM TI Profile and Interface Bindings
DRAFT
Trace
En-route Significant Weather 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 one of the following OGC standards:
|
En-route Significant Weather 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 |
En-route Significant Weather 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
DRAFT
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 | 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
Service operations | operation | operation name | |
---|---|---|---|
description | |||
messages |
Service Messages
DRAFT
Trace
service messages | message | name | En-route Significant Weather Information (Message) |
---|---|---|---|
description | The output message containing the en-route significant weather information. | ||
direction | Out | ||
data format |
En-route Significant Weather Information Message
The output message containing the en-route significant weather information.
Property Name | Type, multiplicity | Definition |
---|---|---|
geographicalExtent | relativeLocation [1..*] | Location defining the scope of the information. |
responsibleOrganisation | source [1..1] | Name of entity or organisation that supplied data. |
observationPosition | position [0..1] | |
observationTime | lastRevision [0..1] | |
weatherPhenomenon | WeatherPhenomenon [0..*] | |
weatherCondition | WeatherCondition [0..*] |
Information Definition (Minimum) and (Extended)
DRAFT
Trace
information definition | The service shall offer information available in accordance with Appendix B. The service shall offer information as defined in the Information aspects of the service. |
---|
Filter Encoding
DRAFT
Trace
filter encoding | The En-route Signification Weather Information Subscription and Request Service Request Interface shall support the During temporal operator defined in the OGC Filter Encoding 2.0 Encoding Standard. The En-route Signification Weather Information Subscription and Request Service Request Interface shall support filtering based on the name and ICAO location indicator of the aerodrome of interest.. The En-route Signification Weather 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 En-route Signification Weather Information Subscription and Request Service Subscription Interface shall allow for the selection of subscription based on a topic tree:
|
---|
Machine-Readable Service Interface Definition
DRAFT
Trace
Explanatory note
This field is left empty. No machine-readable service interface definition is provided.
machine-readable service interface definition | reference |
---|
Model View
DRAFT
Trace
Explanatory note
This field is left empty. No model view is provided.
model view | reference |
---|
Abbreviations and Acronyms
DRAFT
Trace
abbreviations and acronyms | abbreviation | code | |
---|---|---|---|
term | |||
abbreviation | code | ||
term | |||
abbreviation | code | ATM | |
term | Air Traffic Management | ||
abbreviation | code | ATS | |
term | Air Traffic Services | ||
abbreviation | code | EU | |
term | European Union | ||
abbreviation | code | ICAO | |
term | International Civil Aviation Organization | ||
abbreviation | code | OGC | |
term | Open Geospatial Consortium | ||
abbreviation | code | SESAR | |
term | Single European Sky ATM Research | ||
abbreviation | code | SWIM | |
term | System Wide Information Management | ||
abbreviation | code | TI | |
term | Technical Infrastructure | ||
abbreviation | code | TLS | |
term | Transport Layer Security | ||
abbreviation | code | WFS | |
term | Web Feature Service | ||
abbreviation | code | WFS-TE | |
term | Web Feature Service - Temporality Extension |
Appendix A: References
TBD
Trace
references | reference | title | |
---|---|---|---|
version | |||
description | |||
url | |||
document type | |||
reference | title | ||
version | |||
description | |||
url | |||
document type |
Appendix B: Information Definition
DRAFT
Weather Phenomenon | The message shall include information about the following meteorological phenomena when relevant:
|
Appendix C: Operational Needs
DRAFT
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. |
| This role is recognised in the SESAR Deployment Programme as a recommended service consumer of the aerodrome and en-route services. |
MILITARY_AIRSPACE_USER | Airspace User under the authority of a military organisation. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services. Although the military is not obliged to use SWIM, they currently rely on civil weather information and therefore it will be essential for their operations to use SWIM-services. |
CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for general air traffic. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services. The real-time aspects will have an impact on the service architecture. |
MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER | Any public or private entity providing air navigation services for military air traffic. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services. Although the military is not obliged to use SWIM, they currently rely on civil weather information and therefore it will be essential for their operations to use SWIM-services. |
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). |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome and en-route services under the term of ANSP. |
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. |
| Some equipment e.g. ground radar at airports have to be shut down if the wind rises above a certain windspeed threshold to avoid damage | |
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. |
| This role is recognised (as ATFM) in the SESAR Deployment Programme as a service consumer of the en-route services. |
AIRPORT_OPERATOR | The civilian or military agency, group or individual which exercises control over the operations of the civil airport or military airfield. |
| This role is recognised in the SESAR Deployment Programme as a service consumer of the aerodrome services. |
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. |
|