| Table of Contents |
|---|
...
Task Label | Description |
Local Digitalisation [T1] | The project generic expectation is that AISP information is transformed in a digital form, enhanced to ensure ‘Operational Data Completeness’, and enabling generation of AIXM 5.1 data. It may include the automation and digitalization of exchanges with AISP data providers (Airports). In the context of this task each partner will need to describe and execute the local data digitalization. In doing so the project expectation on digital data delivery for each contributing partner will be met. Whilst this is an individual partner effort, it is however not excluded joining effort in terms of mutual support and sharing expertise at the technical level. The rationale for this is that digital data provision and exchange will require expert level exchanges on topics and questions emerging at the local level whilst not excluding the European ATM network level viewpoint. |
Automated Exchange via EAD B2B [T2A] | The project generic expectation is that AISP information is shared with EAD via the B2B interfaces. The information addresses ‘Operational Data Completeness’ and is in AIXM 5.1 format. Each partner will need to describe this task in detail when opted for as the means to provide digital data to the EAD. |
Digitalization via EAD HMI [T2b] | The project generic expectation is that AISP information is transformed in a digital form via the EAD HMI and enhanced to ensure ‘Operational Data Completeness’. Each partner will need to describe this task in detail when opted for as the means to provide digital data to the EAD. |
Local SWIM Service Provision [T3b] | The project generic expectation is that AISP systems are enhanced to provide the Digital NOTAM, AIFS and Aerodrome mapping SWIM services. Each partner will need to describe this task in detail. Each partner will manage their system evolution to provide and implement SWIM services that realize the service definitions as elaborated within the A3SG (Aeronautical SWIM Services Subgroup) under the umbrella of the EUROCONTROL IMT working arrangement. These service definitions will cover the Digital NOTAM, AIFS and Aerodrome mapping SWIM services as a minimum, not excluding additional service definitions used locally whilst conforming to the SWIM requirements at the European ATM network level. |
SWIM Service Consumption [T4] | The project generic expectation is that the Digital NOTAM, AIFS and Aerodrome mapping SWIM services are consumed and the data they provide is used in operations. The task captures activities related to the final step in the digital transformation which is the integrated use of SWIM services in SWIM enabled applications used in operations. The burden of the task is on those consuming clients that feed from SWIM services, however this task activity is there to enable consuming IP partners to achieve the migration to a state with SWIM services being consumed. The means thereto may take multiple forms (eg. Purchase of tools, purchase of expertise, technical interchanges, etc..) Each partner will need to describe this task in detail. |
Project management
Planning Milestones
Used for collaborative planning purposes.
...
| Milestone | Applicability | Implementation Date | Milestone Description | Means of Verification |
| Aerodrome information digitalization. | Airports (AOs) | 31-12-2025 | Information in digital form is made available by the aerodrome in support of the aeronautical information SWIM services to be implemented by the AISP. | Digital data completeness report. |
...
| Milestone | Applicability | Implementation date | Milestone Description | Means of verification |
| Consume Aeronautical Information Feature service | ANSPs, AOs (optional) | 31-12-2025 | Implement an interface that consumes the information provided by the service | Service consumption report. This describes the systems and applications that make use of the information provided by the service. |
| Consume Digital NOTAM Service | ANSPs, AOs (optional) | 31-12-2025 | Implement an interface that consumes the information provided by the service | Service consumption report. This describes the systems and applications that make use of the information provided by the service. |
| Consume Aerodrome SWIM Service | ANSPs, AOs (optional) | 31-12-2025 | Implement an interface that consumes the information provided by the service | Service consumption report. This describes the systems and applications that make use of the information provided by the service. |
| Operational use - Aerodrome Service Information | ANSPs, AOs (optional) | 31-12-2025 | Integrate the information obtained via the service into an application that makes use of it in support of the organization operations. | Service operational Use report. Describes the applications, and business activities that make use of the information provided by the service. |
| Operational use - Aeronautical Information features Exchange | ANSPs, AOs (optional) | 31-12-2025 | Integrate the information obtained via the service into an application that makes use of it in support of the organization operations. | Service operational Use report. Describes the applications, and business activities that make use of the information provided by the service. |
| Operational use - Digital NOTAM | ANSPs, AOs (optional) | 31-12-2025 | Integrate the information obtained via the service into an application that makes use of it in support of the organization operations. | Service operational Use report. Describes the applications, and business activities that make use of the information provided by the service. |
FAQ
Question | Reply |
Is it possible to join ACADIA as an industrial partner? | The ACADIA project is primarily focused on coordinating the implementation of operational stakeholders. Industry can participate when introduced by a specific operational stakeholder in support of ACADIA implementation activities. |