The overall project management structure is organised as the figure below illustrates.

Work Packages

The management structure is supported by a “traditional” Work Package structure where all the work of the project is being conducted. The NUP II+ project consists of 5 Work Packages and is illustrated in the following figure.

WP 200 – Project Management
The objective of WP 200 is to be responsible for the overall management of the project in accordance with the Commission decision and the partners contract. The responsibility includes Commission reporting, contractual issues, co-ordination with external bodies and administration of documentation, support and preparations to the Steering Committee and information related to the project.

WP 240 – Application Development
The objective of WP 240 is to manage the definition and development of the application requirements for the NUP II+ applications as well as analyse the user benefits. Moreover, it shall align these with the overall C-ATM concept currently being defined in Europe.

Since the applications will be developed at local sites in NUP II+, the actual Work Items will be executed by two separate Application Teams. These two teams are located in Sweden (Arlanda airport) and Austria (Vienna airport).

WP 270 – Aircraft systems & functionality
The objective of WP 270 is to develop and modify the technical platform on the aircraft to meet the application requirements of NUP II+. This includes everything from hardware and software development to installations and certification to the required level.

WP 310 – Ground systems & functionality
The objective of WP 310 is to develop and modify the technical platform in the ground systems to meet the application requirements of NUP II+. This includes everything from hardware and software development to installations and certification to the required level.

WP 360 – Validation
This objective of WP 360 is to perform the validation of each application in accordance with the project validation approach (i.e. OCVM).

This work will also be executed at the local sites by the Application Teams in the same manner as for WP 240.

Build Management

To ensure that the local applications reach the level of implementation defined within the project a so-called Build Management will be created as well. In NUP II+, the Build Management should be considered as the “filter“ that makes sure that nothing “slips” through or is forgotten to fulfil the project objectives. In the project structure, this will be a horizontal function compared to the vertical Work Packages.

The Build Management will be assembled locally (i.e. in the same way as for the Application Teams) and in two Teams to be able to handle the applications and systems considered in the project. These two Build teams will be Build 1 and Build 2.

Build 1 – Initial 4D Trajectory Downlink

Applications
In Build 1 initial trials and validation will be performed for Green Approaches, CDM and AMAN applications. The applications will address the strategic use of the downlinked airborne generated 4D Trajectory.

Systems and Technology
On the airborne side Build 1 will use ACARS as datalink for linking down the 4D Trajectory data. This data is based on the FMS 10.6 upgrade.

On the groundside updates will be made to the systems enabling the operations of CDA, CDM and AMAN slot reservations possibilities required for on time first served operations.

Build 2 – Full Applications

Applications
The second Build will include all applications planned for NUP II+, i.e. A-CDA, CDM, the subset of ADS-B Package 1 and AMAN/DMAN with the use of both strategic planning and set-up (based on the entire remaining 4DT to touchdown) as well as tactical follow-up (based on ADS-B and near term 4DT with higher update rate and resolution).

Systems and Technology
The second Build VDL Mode 4 will be used as the datalink for transmitting ADS-B and 4D Trajectory data. The VMMR, the EFB, the network and the Ground System updates will form the technical platform, all based on available standards to create a sustainable solution that provides End-to-End connectivity for the users involving all domains.

Support Managers

Both safety and validation consumes a lot of time and dedicated work. In NUP II+ both safety and the validation plays an important role for the success of the project.

The necessary safest work related to applications and system development shall be taken care of by the appointed entities (e.g. the local Application Teams). However, to make sure that the work runs as planned a Safety Manager will support the work to ensure that safety objectives are met.

For the validation work that is to be performed by the local Application Teams, a Validation Manager will support with expertise knowledge to ensure that the work runs “smoothly”.

The following figure illustrates the relationship between the Work Packages, Application Teams, the Builds, the Validation Manager, the safety Manager and the PMG.