| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This template allows for the documentation of service definitions based on the requirements found at: /wiki/spaces/SCOI/pages/59605116 General requirements to remember:
|
| Table of Contents | ||||
|---|---|---|---|---|
|
| Info | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
Service Definition Identification
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| service definition identification | title | Service Definition for Aeronautical Events Service |
|---|---|---|
edition | 00.00.01 | |
reference date | 2022-04-27 |
Service Identification
| Status | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| service identification | service name |
|
|---|
Service Abstract
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| service abstract | The ... 8.3.10:The main purpose of the AeronauticalInformationNotification service is to provide notifications (alerts) to consumers providing them with a simple mechanism to maintain their systems updated to the latest information available. SNOW: The SNOWTAM is special series NOTAM |
|---|
Service Definition Provider
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
service definition provider | name | EUROCONTROL |
|---|---|---|
| abbreviated name | ||
| description | EUROCONTROL is an intergovernmental organisation with 41 Member and 2 Comprehensive Agreement States. |
Geographical Extent of Information
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| geographical extent of information | Sol34: ensure the availability of world-wide Digital NOTAM data and digital MET data |
|---|
Service Categories
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-095, SWIM-DEFN-100 |
| Info | ||
|---|---|---|
| ||
SAT 2022-11-11: Service provider can be aerodrome operators in some cases. They still have the AISP role. |
service categories | category | category name | Regulated Information Exchange |
|---|---|---|---|
| value | AERONAUTICAL_INFORMATION_EXCHANGE | ||
| scheme | http://reference.swim.aero/information-services/service-categories/CodeRegulatedInformationExchangeType | ||
| category | category name | Business Activity | |
| value | |||
| scheme | http://reference.swim.aero/information-services/service-categories/CodeBusinessActivityType | ||
| category | category name | intended service consumer | |
| value | |||
| scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType | ||
| category | category name | intended service provider | |
| value | AERONAUTICAL_INFORMATION_SERVICE_PROVIDER | ||
| scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType |
Service Standard Reference
| Status | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-120 |
service standard reference | reference | |
|---|---|---|
| implemented options | ||
| deviations/additions |
Operational Environment
| Status | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-130 |
| Info | ||
|---|---|---|
| ||
SAT 2022-11-11: Look to https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+Specification for scenarios that will help write the operational need. It was agreed that this service focuses on what the AISP makes available to the next intended user. Therefore it will not cover: These will be looked at later and in the context of a different service. To discuss: does the term NOTAM cover SNOWTAM and ASHTAM. All of these are available in the Event Extension for AIXM. |
| operational environment | operational needs | Stakeholders involved in air traffic management need aeronautical data concerning the establishment, condition or change in any aeronautical facility, service, procedure or hazard, the timely knowledge of which is essential to personnel concerned with flight operations. This service satisfies this need by allow clients to register for notification about aeronautical events. When an event occurs, the subscription service sends notification to all clients who have registered an interest in the event. The changes notified can be used immediately - re-routings, on board navigational databases could be potentially updated on flight with new digital NOTAM messages being issued., etc. They can also be used to improve their decision making process thus positively impacting the efficiency of their planning and flight executions, enabling through automatic data verification and graphical visualisation The scope covers the event encodings including aerodrome data for the 18 airports listed in EU Implementing Regulation 2021/116 - Common Project One. |
|---|---|---|
| capabilities | The service offers notification in the changes to aeronautical data about features. and/or This identified service will provide structured digital aeronautical information that can be processed. | |
information exchange requirements |
Service Functions
| Status | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-140 |
| Info | ||
|---|---|---|
| ||
SAT 2022-11-11: Options
scenarios come from the digital NOTAM spec including aerodrome data for the 18 airports. Service providers declare which ones their service supports. |
| service functions | function | name | subscription |
|---|---|---|---|
| description | There shall be a mechanism to subscribe/unsubscribe | ||
| real-world effect | Service consumer subscribes to topics offered by the service. | ||
| function | name | topic selection | |
| description | There shall be filtering mechanisms to only subscribe to specific contents. | ||
| real-world effect | |||
| function | name | notification | |
| description | When new data is available, it shall be distributed to the subscribers. | ||
| real-world effect | Service consumer is notified when a change happens to a topic of interest. | ||
| function | name | check notification list | |
| description | There shall be a mechanism by which a given subscriber can check if he has received all sent notifications. | ||
| real-world effect | Service consumer has an understanding of the notifications. | ||
| function | name | request notification reissue | |
| description | There shall be a mechanism by which a subscriber requests a notification reissue (due to not reception, lose, etc.) | ||
| real-world effect | Service consumer receives a notification. |
Service Access and Use Conditions
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-150 |
service access and use conditions | legal constraints | 8.3.10: one aspect that is worth mentioning is related to the legal framework for data distribution. To really achieve all benefits from digital data distribution, all aspects related to copyright, use rights of data and liabilities need to be clearly stated. | |
|---|---|---|---|
service policies | business policy | TBD | |
operational policy | TBD | ||
technical policy | TBD | ||
service consumption constraints | TBD |
Security Constraints
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-160 |
security constraints | authentication | Consumer side authentication: TBD Provider side authentication: Authentication is required |
|---|---|---|
authorisation | ||
confidentiality | ||
integrity |
Quality of Service
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-180 |
quality of service | performance | capacity | |
|---|---|---|---|
| response time | <= 1 second | ||
| reliability | availability | >= 99.95 % | |
| recoverability | |||
| security | confidentiality | ||
| integrity | >= 99.999 % |
Quality of Data
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-185 |
| quality of data | PANS-AIM, EU 373 as amended by 2022/938 |
|---|
Source of Information
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-190 |
source of information | source | AIRPORT_OPERATOR |
|---|
Service Validation Information
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-200 |
service validation information | prototyping | The service was prototyped in SESAR Sol34: An initial verification exercise has focused on the provision of Digital NOTAM in a SWIM compliant manner. This has addressed data origination, collection and provision aspects in the Digital NOTAM data chain, which is a key enabler for Digital Integrated Briefing. |
|---|
Application Message Exchange Pattern
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-210 |
Service Behaviour
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-220 |
service behaviour | typical behaviour | 8.3.10: the AeronauticalInformationNotification service will only send updates to current features properties or new features. Thus, to properly interpret the data received, it is paramount that a previous call to appropriate service operation to obtain the data is performed. The AeronauticalInformationNotification service shall expose such an operation and provide to immediately start the notifications messages after its call. So the process will look like this: The consumer subscribes, the subscription is then moved to a latency state. Then the consumer retrieves the latest available baseline data, together with currently available notifications that apply to that baseline. At that moment, new data changes will be notified, the subscription moves to an active status. Scheduled Information. ... For retrieving the full data a call to the AeronauticalFeatureService will need to be performed Digital NOTAMs... the complete data change within the notification message 8.3.10: The diagram below depicts the service dynamic behaviour of both interfaces. |
|---|
Service Monitoring
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-230 |
service monitoring | There is no expectation that a service monitoring mechanism is made available to service consumers. |
|---|
Service Interfaces
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-240 |
service interfaces | interface | name | 8.3.10: AINSInterfacePull implements Publish/Subscribe Pull MEP. |
|---|---|---|---|
| description | 8.3.10: A synchronous call to obtain specific notifications that where published in the past. | ||
| provider/consumer side | |||
| interface | name | 8.3.10: AINSInterfacePush implements Publish/Subscribe via Push messages. | |
| description | 8.3.10: This interfaces differs from the one described above only in one way. It implements Publish/Subscribe via push notifications instead of client triggered requests. Hence the interfaces are very similar. | ||
| provider/consumer side | |||
| interface | name | SNOW: The SNOWTAMPublisher service interface definition allows the consumer to subscribe or unsubscribe to the data, while the SNOWTAMSubscriber service interface definition allows the service provider to publish the message containing the data. | |
| description | |||
| provider/consumer side |
SWIM TI Profile and Interface Bindings
| Status | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-250, SWIM-DEFN-255 |
SWIM TI profile and interface bindings | profile name | TI Yellow Profile specification |
|---|---|---|
profile version | Edition Number 1.0 | |
| selected service interface binding | ||
| selected network interface binding | ||
| supported optional requirements |
Service Interface Protocols and Data Format
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-260 |
service interface protocols and data format | transport / messaging protocols | ||
|---|---|---|---|
| data format |
|
Service Operations
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-270 |
Service operations | operation | operation name | |
|---|---|---|---|
description | |||
messages | |||
| operation | operation name | ||
description | |||
messages |
Service Messages
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-280 |
service messages | message | name | AeronauticalInformationNotification |
|---|---|---|---|
| description | Message concerning the establishment, condition or change in any aeronautical facility, service, procedure or hazard, the timely knowledge of which is essential to personnel concerned with flight operations. | ||
| type | Out | ||
| data format | AIXM 5.1.1 | ||
| message | name | NOTAM, SNOWTAM, ASHTAM | |
| description | 8.3.10: Moving to the digital sharing of aeronautical information, a NOTAM will be an event (as AIP AMDTs and SUPs will also be), for easing the transition period to a digital environment, the event that represent the digitalNOTAM is linked to the traditional NOTAM that is provided as text. | ||
| type | |||
| data format |
Information Definition (Minimum) and (Extended)
| Status | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| information definition | Sol34:Aeronautical Information Exchange Model (AIXM), on which the Digital NOTAM concept is based 8.3.10: relies on AIXM 5.1 standard for data exchange of aeronautical information |
|---|
Filter Encoding
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| filter encoding | Sol34: develop semantic data filtering rules in order to identify strictly the events that are relevant for each specific flight |
|---|
Machine-Readable Service Interface Definition
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
machine-readable service interface definition | reference |
|---|
Model View
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
model view | reference |
|---|
Abbreviations and Acronyms
| Status | ||
|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| SWIM-DEFN-350 |
| abbreviations and acronyms | abbreviation | code | SWIM |
|---|---|---|---|
| term | System Wide Information Management | ||
| abbreviation | code | ||
| term |