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 | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
|
Info | ||
---|---|---|
| ||
Some fields in the template are left empty. This means that no requirement is specified for it and it is left to the service provider to decide. |
Service Definition Identification
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
service definition identification | title | Service Definition for the Digital NOTAM Subscription and Request Service |
---|---|---|
edition | 00.00.01 | |
reference date | 2023-02-09 |
Service Identification
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
service identification | service name | Digital NOTAM Subscription and Request Service |
---|
Service Abstract
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
service abstract | The Digital NOTAM Subscription and Request Service allows the service consumer to get aeronuatical information in accordance with the Digital NOTAM specification. The aeronautical information conforms to the event scenarios that are supported by Digital NOTAM such as runway closures. The service consumer may subscribe to the service, specifying the event scenarios in which it is interestedof interest. It is also possible to send a direct request to the service to get the aeronautical information. The information returned is in the form of an AIXM 5.1.1 message. This supports the integration of the latest information into the various ATM systems. |
---|
Service Definition Provider
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
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
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
geographical extent of information |
---|
Service Categories
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-095, SWIM-DEFN-100 |
service categories | category | category name | regulated information exchange |
---|---|---|---|
value | AERONAUTICAL_INFORMATION_EXCHANGE | ||
scheme | |||
category | category name | information domain | |
value | AERONAUTICAL_INFORMATION | ||
scheme | https://reference.swim.aero/information-services/service-categories/CodeInformationDomainType.html | ||
category | category name | business activity | |
value | INFORMATION_MANAGEMENT | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeBusinessActivityType.html | ||
category | category name | intended service consumer | |
value | |||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | intended service provider | |
value | AERONAUTICAL_INFORMATION_SERVICE_PROVIDER | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeStakeholderType.html | ||
category | category name | service type | |
value | AERONAUTICAL_INFORMATION_SUBSCRIPTION_SERVICE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeServiceType (for the moment use https://ext.eurocontrol.int/swim_confluence/display/SCOI/Service+Categories+-+Service+Type). | ||
category | category name | service type | |
value | AERONAUTICAL_FEATURE_ACCESS_SERVICE | ||
scheme | http://reference.swim.aero/information-services/service-categories/CodeServiceType (for the moment use https://ext.eurocontrol.int/swim_confluence/display/SCOI/Service+Categories+-+Service+Type). |
Service Standard Reference
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-120 |
service standard reference | reference | Digital NOTAM Specification (https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Overview) |
---|---|---|
implemented options | The information scope offered by the service supports the requirements of the Digital NOTAM Specification. | |
deviations/additions |
Operational Environment
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-130 |
operational environment | operational needs | Air traffic management is defined as the "dynamic, integrated management of air traffic and airspace including air traffic services, airspace management and air traffic flow management - safely, economically and efficiently - through the provision of facilities and seamless services in collaboration with all parties and involving airborne and ground-based functions". It is provided by the air traffic management system that, amongst other things, relies on the collaborative integration of information and services.Stakeholders involved in air traffic management need aeronautical 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 for flight operations. This service satisfies this need by allowing clients to subscribe to be notified when such aeronautical events occur. The aeronautical data can be used e.g. in pre-flight information bulletins. It can also be used to improve decision making thus positively impacting the efficiency of their planning and flight executions, enabling through automatic data verification and graphical visualisation. The aeronautical data is also used in other systems such as those used for airspace reservations (ARES). A complete list of these is available as a High level description of the service offerin Appendix C. This service satisfies this need by offering aeronautical data (in the form of event features) as regulated by ICAO Annex 15 - Aeronautical Information Services. The scope covers the event encodings outlined in the EUROCONTROL Digital NOTAM Specification including aerodrome data for the 18 airports listed in EU Implementing Regulation 2021/116 - Common Project One. |
---|---|---|
capabilities | The service offers notification in messages about the changes to aeronautical data about features. | |
information exchange requirements |
Service Functions
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-140 |
service functions | function | name | Subscribe to event scenario |
---|---|---|---|
description | The service consumer shall be able to subscribe/unsubscribe to topics in order to receive information based on an event scenario(s). | ||
real-world effect | Service consumer subscribes to topics offered by the service. | ||
function | name | Request a Digital NOTAM | |
description | The service consumer shall be able to request aeronautical information in the form of a Digital NOTAM based on criteria sent to the server. | ||
real-world effect | Service consumer receives the Digital NOTAM. | ||
function | name | Distribution | |
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 distribution list | |
description | There shall be a mechanism by which a given subscriber can check if he has received all the distributions expected to be received. | ||
real-world effect | Service consumer has an understanding of the distributions. | ||
function | name | Request Digital NOTAM reissue | |
description | There shall be a mechanism by which a subscriber requests a Digital NOTAM reissue (due to not reception, lose, etc.) | ||
real-world effect | Service consumer receives a Digital NOTAM. |
Service Access and Use Conditions
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-150 |
service access and use conditions | legal constraints | ||
---|---|---|---|
service policies | business policy | ||
operational policy | |||
technical policy | |||
service consumption constraints |
Security Constraints
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-160 |
security constraints | authentication | The service may offer unauthenticated/public use. It In the case of authenticated use, the service shall ensure provider consumer authentication in accordance with SWIM TIYP through the EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate .It shall ensure consumer or the use of a username/password (SASL). The service shall ensure provider authentication in accordance with SWIM TIYP through EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of a X.509 certificate or the use of a username/password (SASL). |
---|---|---|
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 ensures shall ensure point-to-point confidentiality in accordance with SWIM TIYP through EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above. | |
integrity | The service ensures shall ensure point-to-point integrity in accordance with SWIM TIYP through EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile through the use of Transport Layer Security (TLS) 1.2 or above. |
Quality of Service
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-180 |
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 | ||
recoverability | reliable enough to meet the user needs to be informed of hazards... | ||
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 | Confidentiality shall be shall be ensured using SWIM TIYP The service shall ensure confidentiality by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. | |
integrity | Integrity shall be shall be ensured using SWIM TIYP The service shall ensure integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. |
Quality of Data
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-185 |
quality of data | The aeronautical data offered by the service shall satisfy the applicable sections of Commission Implementing Regulation (EU) 2017/373 of 1 March 2017. The aeronautical data offered by the service shall be encodes according to the Event Encoding Specification. The aeronautical data offered by the service shall apply the AIXM 5.1.1 coding guidance is applied to the data. See:guidelines. This includes:
|
---|
Source of Information
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-190 |
source of information | source | Data is The aeronautical data offered by the services shall be received from the appropriate authorised originating sources, e.g. , |
---|
Service Validation Information
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-200 |
service validation information | prototyping |
---|
Application Message Exchange Pattern
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-210 |
application message exchange pattern |
---|
Service Behaviour
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-220 |
service behaviour | typical behaviour | The service behaviour is shall be in accordance with the patterns detailed in Message Exchange Patterns: Identification Guidelines. The two interfaces have different behaviours.behaviour. A combination of an AMQP 1.0 implementation and an OGC Web Feature Service 2.0 Interface Standard implemetation shall be used for the basic behaviour. The typical behaviour for PUBLISH_SUBSCRIBE means that:
The OGC Web Feature Service 2.0 Interface Standard defines the basic behaviour. Synchronous Request/Replythe typical behaviour is as follows:
|
---|
Service Monitoring
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-230 |
service monitoring | A service monitoring mechanism shall be made available to service consumers. |
---|
Service Interfaces
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-240 |
service interfaces | interface | name | Digital NOTAM Subscription and Request Service Subscription Interface |
---|---|---|---|
description | Allows the service consumer to select and subscribe to event scenarios of interest. | ||
provider/consumer side | Provider side | ||
interface | name | Digital NOTAM Subscription and Request Service Distribution Interface | |
description |
Distributes AIXM Basic Messages based on the event scenario |
that has triggered the need for the service consumer to be updated. | ||
provider/consumer side | Provider side | |
---|---|---|
interface | name | Digital NOTAM Subscription and Request Service Request Interface |
description |
Allows the service consumer to request an AIXM Basic Message based on filters which are linked to the event feature. | |
provider/consumer side | Provider side |
---|
SWIM TI Profile and Interface Bindings
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-250, SWIM-DEFN-255 |
Info | ||
---|---|---|
| ||
SAT 2023-01-30: This needs to be split up. Dedicated entry per interface is needed. |
Digital NOTAM 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 | Shall The service shall use the network bindings of the SWIM TIYP. See 3.1.2 for the options: IPV4, etc. | |
supported optional requirements | AMQP 1.0 is used to publish messages in the service's publish-subscribe implementation. This is
Digital NOTAM 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 | ||
selected network interface binding | The service shall use the network bindings of the SWIM TIYP. | |
supported optional requirements | AMQP 1.0 is used to distribute messages as explained in: https://reference.swim.aero/technical-infrastructure/guidance-for-pub-sub-push-implementation.htmlSYNCHRONOUS_REQUEST_REPLY/technical-infrastructure/guidance-for-pub-sub-push-implementation.html |
Digital NOTAM 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 | ||
selected network interface binding | The service shall use the network bindings of the SWIM TIYP. | |
supported optional requirements | The OGC Web Feature Service 2.0 Interface Standard is shall be used in the service 's request-reply implementation. The standardised operations for a Basic WFS are shall be implemented. The temporal extension (WFS-TE) is shall be used to support advanced temporal filtering. The ISO 19143 - Geographic Information - Filter encoding specification is shall be applied for spatial and logical operators. |
Service Interface Protocols and Data Format
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-260 |
service interface protocols and data format | transport / messaging protocols | Shall be The service shall use TLS1.2 or later in accordance with SWIM TIYP: TLS1.2 or laterEUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile. | |
---|---|---|---|
data format |
|
Service Operations
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-270 |
Service operations | operation | operation name | subscribe operation - see if there is a standard that gives us a list of operation names. |
---|---|---|---|
description | |||
messages | |||
operation | operation name | request | |
description | Event features can be queried. | ||
messages |
Service Messages
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
SWIM-DEFN-280 |
service messages | message | name | AIXM Basic Message |
---|---|---|---|
description | The basic messages is a collection of A collection of aeronautical features with timeslices. It contains the event feature and any related AIXM 5.1.1. features. The structure is explained in the EUROCONTROL Event Encoding Specification. The message serves the purpose of Digital NOTAM. | ||
type | Out | ||
data format | AIXM 5.1.1 including the event extension | ||
message | name | ||
description | |||
type | |||
data format |
Information Definition (Minimum) and (Extended)
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
information definition | The service exposes shall expose a topic tree . The topics are based on the event scenarios found in Appendix B. These reflect the Digital NOTAM Specification (https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+Specification). The event scenarios use features that are in the Aeronautical Aeronautical Information Exchange Model (AIXM) 5.1.1 and the AIXM Event Extension. The AIXMBasicMessage that is returned by the service shall contain an event feature and the related AIXM features. See (https://www.aixm.aero/schema/5.1.1/AIXM_Features.xsd) and the AIXM Event Extension (. https://www.aixm.aero/schema/5.1.1/event/version_ 5.1.1-i/Event_Features.xsdhttps://airm.aero/developers/aixm-.1-to-airm-1.0.0-index for the semantic correspondences with the AIRMThe AIXMBasicMessage that is returned by the service shall contain an event feature and the related AIXM features. |
---|
Filter Encoding
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
filter encoding | The request-reply service interface supports Digital NOTAM Subscription and Request Service Request Interface shall support filtering based on (a subset of the) the operators defined in the OGC Filter Encoding 2.0 Encoding Standard (equivalent to ISO 19143 - Geographic Information - Filter encoding). The temporal extension (WFS-TE) is shall be used to support advanced temporal filtering. The publish-subscribe service interface allows Digital NOTAM Subscription and Request Service Subscription Interface shall allow for the selection of topicsevent scenarios of interst. These can should be organised around e.g. a specific aerodrome or airspace. The considerations on https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/General+Principles will help AISP decide which topic an event concerns. |
---|
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 |
Appendix A: References
Status | ||||
---|---|---|---|---|
|
Info | ||
---|---|---|
| ||
This is not traced to a requirement. |
references | reference | title | CP1 |
---|---|---|---|
version | |||
description | |||
url | |||
document type | |||
reference | title | Digital NOTAM Specification (https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Overview) | |
version | |||
description | |||
url | |||
document type | |||
reference | title | Event Encoding Specification ensures the messages are encoded correctly | |
version | |||
description | |||
url | |||
document type | |||
reference | title | Commission Implementing Regulation (EU) 2017/373 of 1 March 2017 | |
version | |||
description | |||
url | |||
document type | |||
reference | title | AIXM 5.1.1 coding guidance is applied to the data. See: | |
version | |||
description | |||
url | |||
document type | |||
reference | title | https://aixm.aero/page/data-coding-guidelines | |
version | |||
description | |||
url | |||
document type | |||
reference | title | Use of Geography Markup Language (GML) for Aviation Data | |
version | |||
description | |||
url | |||
document type | |||
reference | title | https://www.aixm.aero/schema/5.1.1/AIXM_Features.xsd. | |
version | |||
description | |||
url | |||
document type | |||
reference | title | https://www.aixm.aero/schema/5.1.1/event/version_5.1.1-i/Event_Features.xsd | |
version | |||
description | |||
url | |||
document type | |||
reference | title |
| |
version | |||
description | |||
url | |||
document type | |||
reference | title | OGC Filter Encoding 2.0 Encoding Standard (equivalent to ISO 19143 - Geographic Information - Filter encoding | |
version | |||
description | |||
url | |||
document type | |||
reference | title | temporal extension (WFS-TE) | |
version | |||
description | |||
url | |||
document type | |||
reference | title | https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/General+Principles will help AISP decide which topic an event concerns. | |
version | |||
description | |||
url | |||
document type |
Appendix B: Information Definition for Digital NOTAM Subscription and Request Service
Status | ||||
---|---|---|---|---|
|
AIXM 5.1.1. feature allocated to supported event scenario | Digital NOTAM Subscription and Request Service
| ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AD.CLS | AD.LGT | AD.LIM | AGS.UNS | APE.CLS | APE.LIM | APN.CLS | APN.LIM | ATSA.ACT | ATSA.NEW | DEI.IOP | FFS.CHG | GNSS.UNS AIXM 5.2 only | LVP.IOP | NAV.UNS | OBL.UNS | OBS.NEW | RTE.CLS | RTE.OPN | RWY.CLS | RWY.LIM | SAA.ACT | SAA.NEW | SFC.CON | STAND.CLS | STAND.LIM | TWY.CLS | TWY.LIM | WLF.HZD | |||||
AerialRefuelling | |||||||||||||||||||||||||||||||||
AeronauticalGroundLight | |||||||||||||||||||||||||||||||||
AircraftGroundService | y | ||||||||||||||||||||||||||||||||
AircraftStand | y | y | y | ||||||||||||||||||||||||||||||
AirportClearanceService | |||||||||||||||||||||||||||||||||
AirportHeliportCollocation | |||||||||||||||||||||||||||||||||
AirportHeliport | y | y | y | y | y | y | y | y | y | y | y | y | y | y | y | y | y | y | y | ||||||||||||||
AirportHotSpot | |||||||||||||||||||||||||||||||||
AirportProtectionAreaMarking | |||||||||||||||||||||||||||||||||
AirportSuppliesService | y | ||||||||||||||||||||||||||||||||
AirspaceBorderCrossing | |||||||||||||||||||||||||||||||||
Airspace | y | y | y | y | |||||||||||||||||||||||||||||
AirTrafficControlService | |||||||||||||||||||||||||||||||||
AirTrafficManagementService | |||||||||||||||||||||||||||||||||
AltimeterSource | |||||||||||||||||||||||||||||||||
AngleIndication | |||||||||||||||||||||||||||||||||
ApproachLightingSystem | y | ||||||||||||||||||||||||||||||||
ApronElement | y | y | |||||||||||||||||||||||||||||||
ApronLightSystem | |||||||||||||||||||||||||||||||||
ApronMarking | |||||||||||||||||||||||||||||||||
Apron | y | y | y | y | y | y | |||||||||||||||||||||||||||
ArrestingGear | |||||||||||||||||||||||||||||||||
ArrivalFeederLeg | |||||||||||||||||||||||||||||||||
ArrivalLeg | |||||||||||||||||||||||||||||||||
AuthorityForAirspace | |||||||||||||||||||||||||||||||||
Azimuth | |||||||||||||||||||||||||||||||||
ChangeOverPoint | |||||||||||||||||||||||||||||||||
CheckpointINS | |||||||||||||||||||||||||||||||||
CheckpointVOR | |||||||||||||||||||||||||||||||||
CirclingArea | |||||||||||||||||||||||||||||||||
DeicingAreaMarking | |||||||||||||||||||||||||||||||||
DeicingArea | y | ||||||||||||||||||||||||||||||||
DepartureLeg | |||||||||||||||||||||||||||||||||
DesignatedPoint | |||||||||||||||||||||||||||||||||
DirectionFinder | |||||||||||||||||||||||||||||||||
DistanceIndication | |||||||||||||||||||||||||||||||||
DME | |||||||||||||||||||||||||||||||||
Elevation | |||||||||||||||||||||||||||||||||
FinalLeg | |||||||||||||||||||||||||||||||||
FireFightingService | y | ||||||||||||||||||||||||||||||||
FlightRestriction | |||||||||||||||||||||||||||||||||
FloatingDockSite | |||||||||||||||||||||||||||||||||
GeoBorder | |||||||||||||||||||||||||||||||||
Glidepath | |||||||||||||||||||||||||||||||||
GroundTrafficControlService | |||||||||||||||||||||||||||||||||
GuidanceLineLightSystem | |||||||||||||||||||||||||||||||||
GuidanceLineMarking | |||||||||||||||||||||||||||||||||
GuidanceLine | |||||||||||||||||||||||||||||||||
HoldingAssessment | |||||||||||||||||||||||||||||||||
HoldingPattern | |||||||||||||||||||||||||||||||||
InformationService | |||||||||||||||||||||||||||||||||
InitialLeg | |||||||||||||||||||||||||||||||||
InstrumentApproachProcedure | |||||||||||||||||||||||||||||||||
IntermediateLeg | |||||||||||||||||||||||||||||||||
Localizer | |||||||||||||||||||||||||||||||||
MarkerBeacon | |||||||||||||||||||||||||||||||||
MarkingBuoy | |||||||||||||||||||||||||||||||||
MissedApproachLeg | |||||||||||||||||||||||||||||||||
Navaid | y | ||||||||||||||||||||||||||||||||
NavigationAreaRestriction | |||||||||||||||||||||||||||||||||
NavigationArea | |||||||||||||||||||||||||||||||||
NDB | |||||||||||||||||||||||||||||||||
NonMovementArea | |||||||||||||||||||||||||||||||||
ObstacleArea | |||||||||||||||||||||||||||||||||
OrganisationAuthority | |||||||||||||||||||||||||||||||||
PassengerLoadingBridge | |||||||||||||||||||||||||||||||||
PassengerService | y | ||||||||||||||||||||||||||||||||
PilotControlledLighting | |||||||||||||||||||||||||||||||||
PrecisionApproachRadar | |||||||||||||||||||||||||||||||||
PrimarySurveillanceRadar | |||||||||||||||||||||||||||||||||
ProcedureDME | |||||||||||||||||||||||||||||||||
RadarSystem | |||||||||||||||||||||||||||||||||
RadioCommunicationChannel | |||||||||||||||||||||||||||||||||
RadioFrequencyArea | |||||||||||||||||||||||||||||||||
Road | |||||||||||||||||||||||||||||||||
RouteDME | |||||||||||||||||||||||||||||||||
RouteSegment | y | y | |||||||||||||||||||||||||||||||
Route | |||||||||||||||||||||||||||||||||
RulesProcedures | |||||||||||||||||||||||||||||||||
RunwayBlastPad | |||||||||||||||||||||||||||||||||
RunwayCentrelinePoint | |||||||||||||||||||||||||||||||||
RunwayDirectionLightSystem | y | ||||||||||||||||||||||||||||||||
RunwayDirection | y | y | y | ||||||||||||||||||||||||||||||
RunwayElement | |||||||||||||||||||||||||||||||||
RunwayMarking | |||||||||||||||||||||||||||||||||
RunwayProtectAreaLightSystem | |||||||||||||||||||||||||||||||||
RunwayProtectArea | y | ||||||||||||||||||||||||||||||||
Runway | y | y | y | ||||||||||||||||||||||||||||||
RunwayVisualRange | |||||||||||||||||||||||||||||||||
SafeAltitudeArea | |||||||||||||||||||||||||||||||||
SDF | |||||||||||||||||||||||||||||||||
SeaplaneLandingArea | |||||||||||||||||||||||||||||||||
SeaplaneRampSite | |||||||||||||||||||||||||||||||||
SearchRescueService | |||||||||||||||||||||||||||||||||
SecondarySurveillanceRadar | |||||||||||||||||||||||||||||||||
SignificantPointInAirspace | |||||||||||||||||||||||||||||||||
SpecialDate | |||||||||||||||||||||||||||||||||
SpecialNavigationStation | |||||||||||||||||||||||||||||||||
SpecialNavigationSystem | |||||||||||||||||||||||||||||||||
StandardInstrumentArrival | |||||||||||||||||||||||||||||||||
StandardInstrumentDeparture | |||||||||||||||||||||||||||||||||
StandardLevelColumn | |||||||||||||||||||||||||||||||||
StandardLevelSector | |||||||||||||||||||||||||||||||||
StandardLevelTable | |||||||||||||||||||||||||||||||||
StandMarking | |||||||||||||||||||||||||||||||||
SurveyControlPoint | |||||||||||||||||||||||||||||||||
TACAN | |||||||||||||||||||||||||||||||||
TaxiHoldingPositionLightSystem | |||||||||||||||||||||||||||||||||
TaxiHoldingPositionMarking | |||||||||||||||||||||||||||||||||
TaxiHoldingPosition | |||||||||||||||||||||||||||||||||
TaxiwayElement | y | y | |||||||||||||||||||||||||||||||
TaxiwayLightSystem | y | ||||||||||||||||||||||||||||||||
TaxiwayMarking | |||||||||||||||||||||||||||||||||
Taxiway | y | y | y | y | |||||||||||||||||||||||||||||
TerminalArrivalArea | |||||||||||||||||||||||||||||||||
TouchDownLiftOffLightSystem | |||||||||||||||||||||||||||||||||
TouchDownLiftOffMarking | |||||||||||||||||||||||||||||||||
TouchDownLiftOffSafeArea | |||||||||||||||||||||||||||||||||
TouchDownLiftOff | |||||||||||||||||||||||||||||||||
Unit | |||||||||||||||||||||||||||||||||
UnplannedHolding | |||||||||||||||||||||||||||||||||
VerticalStructure | y | y | |||||||||||||||||||||||||||||||
VisualGlideSlopeIndicator | y | ||||||||||||||||||||||||||||||||
VOR | |||||||||||||||||||||||||||||||||
WorkArea |
Appendix C: Operational Needs
Status | ||||
---|---|---|---|---|
|
Transversal
- Collaborative information sharing is essential for decision making involving multiple actors. Automatic taxi with time and path information on the ground, collaborative decision making during emergencies, de-icing operations and infrastructure availability information are examples that involve multiple actors including the aircraft crew.
By service consumer role
Stakeholder/Role | Description of stakeholder/role | Needs for DNOTAM | 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. |
| Aircraft covers UAV. |
MILITARY_AIRSPACE_USER | Airspace User under the authority of a military organisation. |
| There is an assumption that these will be working in DMZ under yellow profile. The AISP needs to meet the security needs. In general, they have the same needs as civil airspace users. |
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. | Ensure safe operations by responding to changes in the status of the infrastructure | |
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). | No needs have been identified. | |
REGULATED_METEOROLOGICAL_SERVICE_PROVIDER | An office designated to provide meteorological service for international air navigation. | No needs have been identified. | |
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. | No needs have been identified. | |
A provider of CNS services. | No needs have been identified. | ||
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. | No needs have been identified. | |
MILITARY_DEFENCE_CENTRE | A military defence centre. Note: these centres, e.g., check for diplomatic clearance. | No needs have been identified. |