...
Project Tasks
The project under the leadership coordination of EUROCONTROL is structured in different types of tasks that enable different stakeholders to perform different activities as part of the common project.
...
Organizations can participate in the project to any of the identified tasks, but at least contribute as a minimum is required contribution to the data completeness of EAD (either with task T2a or T2b unless not applicable i.e. airports). It is part of the project to contribute to define and validate what is expected in terms of Operational Data Completeness Completeness.
EUROCONTROL
As project coordinator and responsible for the common EAD service, EUROCONTROL participates in the project in the execution of the following tasks
...
Each project participant needs to indicate the specific tasks that is performing in the scope of the project, and the associated cost declared in the project. The below table identifies areas of activity in order to structure the tasks of participants.
Task Label | Description |
Local Digitalisation [T1] – Project Participant Name | 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 digitalisation. 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] – Project Participant Name | 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] – Project Participant Name | 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] – Project Participant Name | 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] – Project Participant Name | 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. |
Coordination milestones
The following milestones are applicable to all participants enabling to facilitate the coordination of the implementation among these.
- Implementation plan established. A detailed implementation plan is established identifying all parties involved (including information providers, consumers, and system providers) and detailing the working arrangements and work plan agreed with all these entities. The plan should consider the identification of dependencies, risks and mitigations put in place.
Date: By end of 2023
Applicability: AISPs/ANSPs involved in provision of SWIM Services (T3)
Means of verification: Implementation plan document available
- Service in development The service is in development and all preceding activities have been met including 1) specifications ready, 2) technical platform where the service will be deployed (possibly together with other services) is defined and 3) the information and means to produce this in digital form have been defined.
Date: By end of 2024
Applicability: AISPs/ANSPs involved in provision of SWIM Services (T3)
Means of verification: Verification means may include the availability of technical specifications, digital data completeness report, technical platform description.
- Service usage plan established. A detailed service usage plan is established identifying the technical systems, applications, functionalities, and business activities that will be impacted by the consumption of the service. The plan also identifies the implementing actors (e.g., system providers) and milestones agreed with these.
Date: By June 2024
Applicability: All planning consumption of SWIM Services (T4)
Means of verification: Service usage plan document available.