PANSA Digital NOTAM Subscription and Request Service allows the service consumer to get aeronautical 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 of 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 an existing aeronautical information store in the various ATM systems.
Categorisation
SERVICE_DESCRIPTION
PROSPECTIVE
- INFORMATION_MANAGEMENT
- AIRPORT_OPERATOR
- CIVIL_AIR_NAVIGATION_SERVICE_PROVIDER
- CIVIL_AIRSPACE_USER
- MILITARY_AIR_NAVIGATION_SERVICE_PROVIDER
- MILITARY_AIRSPACE_USER
- NETWORK_MANAGER
- PROVIDER_OF_DATA_SERVICES
- AERONAUTICAL_INFORMATION_EXCHANGE
- SYNCHRONOUS_REQUEST_REPLY
- PUBLISH_SUBSCRIBE
- BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM
- FIR WARSZAWA
FIR EPWW
Provider
PANSA
PANSA is responsible for air traffic management and navigation services in Poland. The key activities of the organisation include airspace management and ensuring safe and efficient flow of air traffic. Every day, the Polish Air Navigation Services Agency (PANSA) takes care of the safety of passengers of about 2 500 aircraft moving over Poland, and coordinates thousands of drone flights out of nearly 1 million registered in the PansaUTM system. The airspace we supervise and control covers more than 334 000 square kilometers and is one of the largest in Europe. PANSA is the only institution in Poland that trains and employs civilian air traffic controllers.
- AERONAUTICAL_INFORMATION_SERVICE_PROVIDER
PANSA
Restricted
Restricted
Operational Needs
Air traffic management is defined by ICAO 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". 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 event scenarios and to be notified when the aeronautical data described in the event scenario is affected. 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, enabled 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 list of these is available in Appendix C. This service satisfies this need by offering the aeronautical data (in the form of event features) as regulated by ICAO Annex 15 - Aeronautical Information Services.
-
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+Definition#Appendix-C%3A-Operational-NeedsAppendix C
Information Exchange Requirements
IER 1 - Digital NOTAM Exchange (A3SG-IER-05) (A3SG-IER-05 Digital NOTAM Data Exchange - Aeronautical SWIM Services - SWIM Confluence (atlassian.net))
-
https://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031194/A3SG-IER-05+Digital+NOTAM+Data+ExchangeA3SG-IER-05 Digital NOTAM Data Exchange - Aeronautical SWIM Services - SWIM Confluence (atlassian.net)
Capabilities
The service offers subscription and request capabilities to distribute aeronautical data based on event scenarios.
Subscribe to event scenario
The system provides Publish-Subscribe functionality for service consumers to subscribe/unsubscribe to receive Digital NOTAMs using filtering criteria:- event scenario(s)- series- Digital NOTAM publisher(s)- event scenario provider(s)- aeronautical feature(s)-- aerodrome(s)-- airspace(s)
Service consumer subscribes to information offered by the service. AMQP Queue Name is returned in the subscription response.
Distribution
When new Digital NOTAM is generated, the system distributes the message containing Digital NOTAM in AIXM 5.1.1 format to subscribed service consumers according to the stored subscription filters.
Service consumer receives Digital NOTAM message when a change happens based on an event scenario. Distribution mechanism is AMQP 1.0 based Publish-Subscribe using AMQP Message Broker, which handles distribution to AMQP Queues.
Request a Digital NOTAM
The service consumer is able to request aeronautical information in the form of a Digital NOTAM through WFS GetFeature query.
The service consumer receives data.
-
Response timeResponse Time of Digital NOTAM Subscription and Request Service Subscription Interface is less or equal to 1 second. Response Time of Digital NOTAM Subscription and Request Service Request Interface is designed in function of the operation complexity.- Low Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 6 seconds- Medium Complexity filter criteria in an AIS Data Query, the average response time is less or equal to 9 seconds- High Complexity filter criteria in Data Query, the average response time is less or equal to 22.5 seconds- Very High Complexity filter criteria in an Data Query, the average response time is less or equal to 75 seconds- Low complexity query parameters:-- (Dynamic) Feature Filter--- Validity - validTime--- Identifier--- ADMExtension.DataSource--- Interpretation--- NaturalDescriptorExtension-- Time slice Projection--- relevantTime--- Interpretation- Medium complexity query parameters:-- Any combination of Low complexity filter conditions and-- (Dynamic) Feature Filter--- By Feature time slice Simple Properties-- Time slice Projection--- By Feature time slice Simple Properties- High complexity query parameters:-- Any combination of filter conditions with:--- Low complexity--- Medium complexity and-- (Dynamic)Feature Filter--- By Feature time slice complex properties--- One Spatial Filter Condition-- Time slice Projection--- By Feature time slice complex properties- Very high complexity query parameters:-- Any combination of filter conditions with:--- Low complexity--- Medium complexity--- High complexity and-- (Dynamic)Feature Filter--- multiple Spatial Filter Condition
-
CapacityThe throughput of the service has a capacity of 22000 WFS requests per work day an 2000 subscription requests per work day (to be updated).
-
AvailabilityThe availability of the service is at least 99,975%.
-
RecoverabilityThe unplanned unavailability of the services shall not exceed 30 minutes (RTO = 30 minutes). In case of incidents the service ensures that no data is lost (RPO = 15) followed by operational procedures to recover potential data losses.
-
ConfidentialityThe service ensures confidentiality through TLS 1.2/1.3 encrypted connections and implemented security mechanisms, including mTLS, SASL, and OAuth access tokens issued by Microsoft Entra ID.
-
IntegrityThe service ensures integrity by using SWIM Technical Infrastructure (TI) Yellow Profile bindings. Data integrity is maintained, no messages or critical queries are lost.
-
AccessIn order to be able to access and use PANSA Digital NOTAM Subscription and Request Service, Consumers need to sign the Agreement.
-
PolicyPANSA Digital NOTAM Subscription and Request Service consumers may use data in order to integrate it in data products or facilitate their operations. Reselling data is prohibited.
-
Fair UseCustomers can be negatively impacted when data usage is disproportionate and for extended periods. As protection mechanism, PANSA Digital NOTAM Subscription and Request Service will restrict excessive requests originated from the same client.
-
AuthenticationThe authentication requires all users to sign the requests using an X.509 certificate.
-
AuthorisationTo consume the services, the Data Consumer must be authorised and have approved access. The service ensures that service consumption is permitted if and only if authorisation is successful, in accordance with EUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile requirement SWIM-TIYP-0070.
-
Service Desk Contact Form and EmailCustomer Service for general information and service support.
-
https://www.ais.pansa.pl/en/about-ais/contact/
SELF_VALIDATION
The validation process is part of software development methodology covered in an assessment and verification management plan. Validation Steps: * SQT (Software Quality Test) / FAT (Factory Acceptance Test) dry run * FAT (Factory Acceptance Test) * SAT (Site Acceptance Test). The whole process is subject to EASA oversight and is formalised with a letter of acceptance.
Validation and acceptance are concluded with reports as per each validation test step.
Validation reports are available upon request. Due to the confidentiality status of the documents a non-disclosure agreement may be required.
-
AIMAeronautical Information Management
-
AIPAeronautical Information Publication
-
AISAeronautical Information Service
-
AISPAeronautical Information Service Provider
-
AIXMAeronautical Information Exchange Model
-
AMQPAdvanced Message Queuing Protocol
-
ARESAirspace Reservation
-
ATMAir Traffic Management
-
B2BBusiness to Business
-
CRUDCreate, Read, Update, Delete
-
EASAEuropean Union Aviation Safety Agency
-
FATFactory Acceptance Testing
-
FESFilter Encoding Standard
-
HTTPHypertext Transport Protocol
-
HTTPSSecure HTTP
-
ICAOInternational Civil Aviation Organization
-
ICDInterface Control Document
-
IERInformation Exchange Requirements
-
MEPMessage Exchange Pattern
-
mTLSMutual TLS
-
NOTAMNotice To Air Missions
-
OGCOpen Geospatial Consortium
-
RESTRepresentational State Transfer
-
SASLSimple Authentication and Security Layer
-
SESARSingle European Sky ATM Research
-
SATSite Acceptance Testing
-
SQTSystem Quality Testing
-
SWIMSystem-Wide Information Management
-
TITechnical Infrastructure
-
TLSTransport Layer Security
-
URLUniform Resource Locator
-
WFSWeb Feature Service
-
WFS-TEWeb Feature Service - Temporality Extension
-
WSWeb Service
-
XMLExtensible Markup Language
-
Event-based filtering for subscription serviceThe subscription service allows a client to subscribe either to selected event scenarios or to the full event context. This supports both targeted event consumption and broader event monitoring according to consumer needs. The AIXM 5.1 data and digitalNOTAM are returned together with the referencing time slice, which contains the actual feature change (TEMPDELTA or PERMDELTA) and the underlying BASELINE of the feature change. This allows clients to receive the full scope of the DNOTAM.
-
PANSA AIM System
-
https://aixm.aero/page/aixm-51-511The service shall expose the event scenarios found in Appendix B. These reflect the Digital NOTAM Specification. The event scenarios use features that are in the 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 and time slices.
-
Queue NameThe queue name is represented exclusively by a UUID. This UUID is included as part of the AMQP broker address through which the connection is established. Queue name is generated by the system and is returned in Subscription reply message. AMQP Queue Name convention/pattern is:
-
Duplicate subscriptionsService consumer is responsible for creating subscriptions for selected/specific Digital NOTAM scenarios. The system allows service consumer to create multiple subscription with same filter.
-
Normal ConditionsThe service behaviour is in accordance with the patterns detailed in Message Exchange Patterns: Identification Guidelines. A combination of an AMQP 1.0 implementation and an OGC Web Feature Service 2.0 Interface Standard implementation is used. Regarding message exchange patterns the service consists of- SYNCHRONOUS_REQUEST_REPLY - RESTful interfaces handle the subscription and request for Digital NOTAM.- BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM - an AMQP 1.0 implementation handles the distribution of the messages. The behaviour of Digital NOTAM Subscription and Request Service Subscription Interface under normal conditions: - The service consumer sends RESTful request message to subscribe (subscription request contains valid filter)- The service consumer remains blocked while awaiting the reply- The service remains blocked while processing the reply- The service sends response message with AMQP Queue name, subscription filters and subscription status to the service consumer (subscription is by default created with status "PAUSED", i.e. subscription will not receive any Digital NOTAM messages yet)- The service consumer sends RESTful request message to activate subscription- The service consumer remains blocked while awaiting the reply- The service remains blocked while processing the reply- The service sends response message to the service consumer, informing about subscription status change The behaviour of Digital NOTAM Subscription and Request Service Distribution Interface under normal conditions: - event scenario is triggered, this causes change of aeronautical data in the system- the system generates Digital NOTAM message- the system distributes the message to AMQP Queues based on subscriptions and their stored filters (handled by AMQP Message Broker) - the service consumer connects to their AMQP Queue and consumes the message- the service consumer sends acknowledgement to AMQP Message Broker, the message is removed from the queueThe behaviour of Digital NOTAM Subscription and Request Service Request Interface under normal conditions: - The service consumer sends RESTful request message with WFS GetFeature query- The service consumer remains blocked while awaiting the reply- The service remains blocked while processing the reply- The service sends response message with data.
-
Technical messagesImplementation of SYNCHRONOUS_REQUEST_REPLY - RESTful interfaces handle the subscription and request for Digital NOTAM using REST API. BROKERED_PUBLISH_SUBSCRIBE_WITH_PUSH_MECHANISM- an AMQP 1.0 protocol uses technical messages to inform the service consumer about: update or deletion of AMQP Queue linked to subscription
-
Error Messages and Error HandlingAll RESTful responses provide feedback of type information, warning or error depending on the processing result.
-
Error Codes and Expected EffectsThe complete list of error, informational, and warning messages may be provided in a separate reference document. Additional details may be provided separately
-
A service monitoring mechanism is not available to service consumers.
-
PANSA Digital NOTAM Subscription and Request Service Subscription InterfaceAllows the service consumer to select and subscribe to event scenarios of interest. It allows the service consumer to manage the subscriptions e.g. to pause a subscription, or to unsubscribe.PROVIDER_SIDE
-
subscribeThis operation allows a service consumer to subscribe to event scenarios of interest.gitMessages
-
SubscriptionsRequest - REST POSTIN
-
SubscriptionsReply - REST POSTOUT
-
-
unsubscribeThis operation allows a service consumer to deactivate the subscription permanently.gitMessages
-
SubscriptionsRequest - REST DELETEIN
-
SubscriptionsReply - REST POSTOUT
-
-
pauseThis operation allows a service consumer to pause the subscription.gitMessages
-
SubscriptionsRequest - REST PUTIN
-
SubscriptionsReply - REST PUTOUT
-
-
resumeThis operation allows a service consumer to resume a subscription that had been paused.gitMessages
-
SubscriptionsRequest - REST PUTIN
-
SubscriptionsReply - REST PUTOUT
-
-
getSubscriptionsThis operation allows a service consumer to obtain the list of subscriptions.gitMessages
-
SubscriptionsRequest - REST GETIN
-
SubscriptionsReply - REST POSTOUT
-
-
getSubscriptionDetailsThis operation allows a service consumer to obtain information on a specific subscription.gitMessages
-
SubscriptionDetailsRequest - REST GETIN
-
SubscriptionDetailsReply - REST GETOUT
-
-
getTopicsThis operation allows a service consumer to request the list of topics (which represent type Digital NOTAM scenarios) available for subscriptiongitMessages
-
TopicsRequest - REST GETIN
-
TopicsReply - REST GETOUT
-
-
getTopicDetailsThis operation allows a service consumer to obtain information on a specific topic (filter criteria).gitMessages
-
GetTopicRequest - REST GETIN
-
GetTopicReply - REST GETOUT
-
EndpointsRestricted
-
SWIM_TI_YP_1_1_WS_LIGHTThe web service is bound to the REST architectural style.
-
IPV4_UNICASTThe service uses the network bindings of the SWIM TIYP IPv4 Secure Unicast.
-
SubscriptionRequestRequest message to subscribe to an event scenario of interest.
-
SubscriptionReplyReply message to a subscription request.
-
UnsubscribeRequestRequest message to deactivate the subscription.
-
UnsubscribeReplyReply message to an unsubscribe request.
-
PauseRequestRequest message to pause a subscription.
-
PauseReplyReply message to an pause request.
-
ResumeRequestRequest message to resume a subscription.
-
ResumeReplyReply message to a resume request.
-
GetSubscriptionsRequestRequest message to get a list of subscriptions.
-
GetSubscriptionsReplyReply message to a get subscriptions request.
-
GetSubscriptionDetailsRequestRequest message to get the details on a specific subscription.
-
GetSubscriptionDetailsReplyReply message to a get subscription details request.
-
GetTopicsRequestRequest message to get a list of Digital NOTAM scenarios that are available for subscription.
-
GetTopicsReplyReply message to a get topics request.
-
GetTopicRequestRequest message to get the details on a specific topic.
-
GetTopicReplyReply message to a get topic request.
-
-
PANSA Digital NOTAM Subscription and Request Service Distribution InterfaceAllows the service provider to distributes Digital NOTAM Messages based on the event scenario that has triggered the need for the service consumer to be updated.PROVIDER_SIDE
-
publishThis operation allows the service provider to publish Digital NOTAM messages to service consumers based on their subscriptions. Implementation is handled through AMQP 1.0 protocol and the published message is distributed to service consumers through AMQP Queues.git
EndpointsRestricted
-
SWIM_TI_YP_1_1_AMQP_MESSAGINGThe web service is bound to the AMQP 1.0 messaging protocol.
-
IPV4_UNICASTSWIM TI Yellow Profile specification
-
-
PANSA Digital NOTAM Subscription and Request Service Request InterfaceAllows the service consumer to request an AIXM Basic Message based on filters which are linked to the event feature.PROVIDER_SIDE
-
GetCapabilitiesGenerates a service metadata document describing the WFS service provided by the server.gitMessages
-
GetCapabilitiesRequest - REST POSTIN
-
GetCapabilitiesReplyOUT
-
-
GetFeatureThe GetFeature operation returns a selection of features from a data store.gitMessages
-
GetFeatureRequest - REST POSTIN
-
GetFeatureReply - REST ResponseOUT
-
EndpointsRestricted
-
SWIM_TI_YP_1_1_WS_LIGHTEUROCONTROL Specification for SWIM Technical Infrastructure (TI) Yellow Profile
-
IPV4_UNICASTSWIM TI Yellow Profile specification
-
wfs:ServiceExceptionReportServiceExceptionReport container for error messages. Exception reporting.
-
-
Appendix A: Referenceshttps://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+DefinitionINFORMATION_DEFINITION1.0
-
Appendix B: Information Definition for Digital NOTAM Subscription and RequestServicehttps://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+DefinitionINFORMATION_DEFINITION1.0
-
Appendix C: Operational Needshttps://swim-eurocontrol.atlassian.net/wiki/spaces/ASW/pages/60031402/Digital+NOTAM+Subscription+and+Request+Service+-+Service+DefinitionSERVICE_BEHAVIOUR_DESCRIPTION1.0
Digital NOTAM Specification
SERVICE_STANDARD
Not applicable.
1.0
The information scope offered by the service supports the requirements of the Digital NOTAM Specification.
-
https://ext.eurocontrol.int/aixm_confluence/display/DNOTAM/Digital+NOTAM+SpecificationDigital NOTAM Specification
OGC Web Feature Service
SERVICE_STANDARD
The service is partially conform with the standard as per Technical Constraints section of the current service description.
2.0
This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions.
OGC Web Feature Service - Temporal Extension (WFS-TE)
SERVICE_STANDARD
The system partially supporting WFS-TE. Supporting use cases are 3,4,5,6,8.
3.0
The temporality extension has been developed in order to align the OGC WFS 2.0 and FES 2.0 standards with the AIXM 5.1.1 Temporality Concept. It allows retrieving data in AIXM 5.1.1 format via OGC WFS 2.0 requests.
-
https://portal.ogc.org/files/?artifact_id=58922OGC 12-027r3
XML
EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE
The Service Interface Binding supports the Extensible Mark-up Language (XML) 1.0. (as per SWIM-TIYP-0029 requirement)
1.0
Extensible Markup Language (XML) is a markup language and file format for storing, transmitting, and reconstructing arbitrary data. It defines a set of rules for encoding documents in a format that is both human-readable and machine-readable.
WS Light
EUROCONTROL_SPECIFICATION_FOR_SWIM_TECHNICAL_INFRASTRUCTURE
The Service Interface Binding supports WS Light.
-
url:standards.restREST (Representational State Transfer) is a set of constraints for designing and developing web-based systems that are scalable, reliable, and loosely coupled. REST APIs use HTTP methods (such as GET, POST, PUT, DELETE) to define actions that can be performed on resources. These methods align with CRUD (Create, Read, Update, Delete) operations, which are used to manipulate resources over the web.
AMQP
EUROCONTROL_SPECIFICATION_FOR_SWIM_SERVICE_DESCRIPTION
The Service Interface Binding supports AMQP 1.0 (as per SWIM-TIYP-0036 requirement).
1.0
-
https://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdfOASIS Advanced Message Queuing Protocol (AMQP) Version 1.0