...
- The need to exchange information is based (triggered) on the need of the information provider to communicate to the information consumer that there is an event.
- There is no exchange frequency determined, as the information is exchanged based on unplanned events.
Non Functional Requirements
There is no non functional requirement identified.
Constraints
This exchange of information is constraint to be performed as follows:
...
| Expand |
|---|
It captures all requirements related to digital NOTAM service, but excluding the IER does not focus on the exchanges between the AO and the AISP, as these are covered in A3SG-IER-04 Aerodrome Events Data Exchange | A3SG-REF-003 | CP1/AF5.1.3 | DNOTAM | Operational stakeholders R/T digital NOTAM | Operational stakeholders must implement... digital NOTAM… that support the exchange of the aeronautical information… as described in the deployment programme |
|
...
| Expand |
|---|
It extends the roles stated in the SDP, that do not consider event data originators origination beyond the airports. | A3SG-REF-025 | SDP/AF5.3 | DNOTAM | Digital NOTAM Service roles | The Digital NOTAM information exchange shall be implemented by: • AISPs that are the intended provider of the service • Airports that are the originator of the event data • ANSPs (pre-flight bulletin) that are the intended consumers of the service and the information it provides |
It fully covers the functionality stated in the SDP. | A3SG-REF-026 | SDP/AF5.3 | DNOTAM | Digital NOTAM Service functionality | The provider of the Digital NOTAM Service ensures that systems implementing the service: • Shall enable the sharing of various event information |
It covers the technical aspects stated in the SDP. | A3SG-REF-027 | SDP/AF5.3 | DNOTAM | Digital NOTAM Service technical aspects | The provider of the Digital NOTAM Service ensures that systems implementing the service: • Shall conform to EUROCONTROL Digital NOTAM specification • Shall output event information encoded in AIXM 5.1.1 |
|
...