13 10 221426 a sju dow wp11 v2 0 final by SESAR JU

WP 11.1 â&#x20AC;&#x201C; Flight and Wing Operations Centre Description of Work (DoW)

Version 2.0

Released 02/08/2010

SJU DoW WP11 v2.0

Page 1 of 72

Table of contents WP 11

Flight Operations Centre-Wing Operations Centre / Meteorological Services .................................................................................................... 4

Sub-Work Package 11.1 FOC/WOC and Projects overview .................................. 11 SWP 11.1 Flight and Wing Operations Centres ................................................... 12 P 11.1.0 Co-ordination and Management.......................................................... 17 P 11.1.1 Transversal Consistency of Business/Mission Trajectory Requirements (across WPs)........................................................................................................... 19 P 11.1.2 FOC/WOC Operational Requirements Definition ............................... 23 P 11.1.3 System Specification & Architecture ................................................... 28 P 11.1.4 Prototype(s) Specification, Development & Verification ..................... 33 P 11.1.5 Pre-Operational Validation .................................................................. 40 Sub-Work Package 11.2 MET Services and Projects overview ............................. 46 SWP 11.2 Meteorological Services ....................................................................... 47 P 11.2.0 P 11.2.1 P 11.2.2

Co-ordination and Management.......................................................... 53 Requirements for MET Information ..................................................... 55 MET Information Systems Development, Verification & Validation .... 64

SJU DoW WP11 v2.0 Page 2 of 72

Level 1 â&#x20AC;&#x201C; Work Package Description

SJU DoW WP11 v2.0 Page 3 of 72

WP 11

Flight Operations Centre-Wing Operations Centre / Meteorological Services

Introduction WP11 addresses Flight/Wing Operations Centres and Meteorological Services in two Sub-Work Packages. Both are treated as “standalone” for the purposes of the Description of Works, the Call for Tender, Contract Awards and the subsequent works performed. The Management and Co-ordination for each Sub-Work Package (SWP) addresses both the Work Package Leader role and Sub-work Package Manager role combined (as defined within the SESAR Programme Methodologies). This section of the Description of Works (DoW) will provide a brief overview of the Context for Work Package 11, the high level Work Breakdown Structure, the applicable SESAR Programme methodologies and the generic typology of expertise for WP11. Within each Sub-Work package, the DoW will describe the required: 

Management & Coordination



Expertise



Concept and Objectives



Work Breakdown Structure



Main Deliverables



Risks Management



Work Flow and Dependencies



Projects

For each Project within a SWP, the DoW will detail the: 

Necessary Expertise



Concept and Objectives



Description of Work



Work Flow and Dependencies



Deliverables



Indicative EUROCONTROL/SJU Furnished Input



Risks Management

Context The SESAR target Concept of operations is a Trajectory-based Concept. All partners in the ATM Network will share in real time trajectory information with the required precision in all 4 dimensions (latitude, longitude, altitude and time) to to the extent required from the earliest trajectory planning phase through execution and post-execution activities. SJU DoW WP11 v2.0 Page 4 of 72

The Business/Mission Trajectory expresses the specific intentions of Airspace Users. The Airspace Users own the Business/Mission Trajectory, thus in normal circumstances they have primary responsibility over their operations. In circumstances where ATM constraints need to be applied, the resolution that achieves the best business/mission outcome within these constraints is left to individual users. A trajectory integrating ATM constraints has to be collaboratively elaborated and agreed for each flight resulting in the trajectory that the user agrees to fly and the ANSPs and Airports agree to facilitate in line with performance requirements. As part of the overall ATM System, innovative Flight Operations Centres (FOC)/Wing Operations Centres (WOC) features need to be defined and validated together with other ATM solutions developed within the other Work-Packages of SESAR Programme. One of the major uncertainties in operating the trajectory-based concept is the effect of Meteorological conditions on the predictability of agreed 4D trajectories. As a consequence, it was decided to address the meteorological service component (MET) seen from a transversal perspective throughout the SESAR Work Programme in this procurement procedure. As weather conditions can seriously restrict aircraft operations and levels of service available to system users, the manner by which weather-related information is collected, managed, disseminated and utilised in decision-making is of paramount importance. In the context of this DoW: “FOC/WOC” scope covers the following processes and supporting systems: 

Aircraft/Mission Scheduling



Flight Planning



Operations Control



Post flight performance analysis and reporting

"Airspace User" scope includes both Civil and State Airspace Users (AUs): 

Civil Airspace Users are commercial airlines (Scheduled Mainline, Regional, Low Fare, Charter/Leisure and Cargo), business and general aviation.



State Airspace Users are grouped into 4 categories: o

Military Airspace Users as defined in accordance with the main categories of aircraft they use i.e. operators of large aircraft (military transport type aircraft),

Operators of fighter aircraft,

Operators of light aircraft (light civil and military aircraft, helicopters, paramilitary aircraft),

Different types of UAS.

“Airport” scope includes: 

Civil Airports,



Heliports,



Military Airports.

SJU DoW WP11 v2.0 Page 5 of 72

“ATM Network” addresses suitably equipped civil aircraft and state aircraft including UAS (operated by Airspace Users) flying through regulated airspace following SESAR compliant concepts of operation and procedures. Work Breakdown Structure

The following diagram shows the WP11 Work Breakdown Structure:

Applicable Methodology and Reference Documents WP11 shall adopt the SESAR Joint Undertaking (SJU) Programme methodologies applied in the rest of the programme. It shall apply the Programme steering documents, and in particular the Programme Management Plan (PMP), the System Engineering Management Plan (SEMP) and strategies to perform its work. The SESAR Programme has to marry the top down approach linked to the management of the ATM Master Plan, the Strategies and Policies, with bottom up innovative thinking from WP11. The SESAR Programme lifecycle is divided into three main SESAR Concept Storyboard Steps: 

Step 1: Time Based Operations (quick wins)



Step 2: Trajectory Based Operations



Step3: Performance Based Operations.

In order to achieve overall Programme objectives 3 deadlines are set for 2011, 2013, and 2015 setting the pace for the entire programme community. These deadlines are called “Definition Maturity Targets” (DTMs) and can be described as follows: 



At the latest before the end of 2011: o

Step 1 maturity V3 (Step 1 validation completed)

Step 2 maturity V1

At the latest before the end of 2013:

SJU DoW WP11 v2.0 Page 6 of 72



Step 2 maturity V2

Step 3 maturity V1

At the latest before the end of 2015: o

Step 2 maturity V3 (Step 2 validation completed)

Step 3 maturity V2 to V3 (Step 3 validation completed)

The general sequence of R&D activities for each of the three Concept Storyboard Steps is depicted in the diagram below:

WP11 is expected to deliver within the following deadlines: 

At the latest before the end of 2011: o



At the latest before the end of 2013: o



Step 1 validation completed (quick wins)

Step 2 validation completed

At the latest before the end of 2015: o

Step 3 validation completed

WP11 deliverables must be linked with the 3 Concept Steps and be delivered before the programme deadlines (DMT’s). Validation and Verification All the operational R&D activities require moving the operational improvements of the SJU DoW WP11 v2.0 Page 7 of 72

Business/Mission Trajectory operating context and supporting system developments in FOC/WOC and MET to the maturity level V3. Depending on the maturity level of the operational/system improvements, different validation techniques may be used. The R&D activities to be performed and the associated main deliverables shall be aligned with the SJU V&V strategy and supporting reference documentation (see section below).

A System Engineering, Enterprise Architecture (EA) and Service Oriented Approach (SOA) are integral to the SESAR development phase and are further described in the Programme Management Plan (PMP) and System Engineering Management Plan (SEMP). Reference Documentation applicable to WP11 SESAR Programme Management covers the overall management activity of the SJU Work Programme, and is responsible for the definition, planning and organisation of the SESAR Programme and the monitoring of its execution according to the agreed objectives (results, financial, planning, etc). As the SESAR Programme has started, WP11 shall align to the guidance and policies already in place. Related reference documents are listed hereafter (references are indicative including lattest available versions. Note that reference documentation will be brought to evolve over the life time to achieve the objectives of the SESAR Work Programme): 

SESAR Steering Documents o SESAR PMP v01.00.00 – SESAR Programme Management Plan, Edition 01.00.00 o SESAR SEMP V2.0 – SESAR System Engineering Management Plan V2.0



SESAR Policies and Strategies o SESAR Architecture Strategy 01_00_00 o SESAR Validation and Verification Strategy 01_00_00



SESAR Framework Description Documents o WP3 Revision Framework V 01.01.00

SJU DoW WP11 v2.0 Page 8 of 72

Generic typology of expertise For performing WP11 activities the following generic type of expertises has been identified. 1) Operations:  SESAR ConOps,  Aircraft performance modelling (incl. environmental impact),  Aircraft/Mission scheduling,  Flight planning,  Operations control,  Post flight performance analysis and reporting,  Applicable regulations and standards. 2) System:  System engineering, prototyping and verification for Aircraft/Mission Scheduling, Flight Planning and Operations Control systems,  System Architecture, SOA (Service Oriented Architecture),  Applied mathematics, optimization algorithms, aircraft performance modelling,  Datalink/data communication,  SWIM technical infrastructure,  Information modelling. 3) Management and coordination:  Understanding of SESAR Programme objectives and work breakdown structure, ATM Master Plan and Target Concept & Architecture,  Safety, security and environment performance measurement,  Performance management and analysis, business case analysis,  Project management,  Quality management. 4) Meteorological Expertise:  ATM Network operations and supporting systems,  SWIM technical infrastructure,  Aviation Meteorology addressing global, regional and local applications,  Ground, Airborne and Space MET sensing and observation systems,  Environment and physics of the atmosphere,  Numerical assimilation, analysis and forecasting techniques,  Applicable regulations and standards.

SJU DoW WP11 v2.0 Page 9 of 72

Level 2 & 3 â&#x20AC;&#x201C; Work-Package Description

SJU DoW WP11 v2.0

Page 10 of 72

Sub-Work Package 11.1 FOC/WOC and Projects overview Sub Work package n째

Sub Work Package title

Project n째

Project title

SWP 11.1

Type of activity (MGT/Project)

Flight and Wing Operations Centres

P11.1.0

Co-ordination & Management

P11.1.1

Transversal consistency of Business/Mission Trajectory Requirements (across WPs)

Project

P11.1.2

FOC/WOC Operational Requirements Definition

Project

P11.1.3

System Specification & Architecture

Project

P11.1.4

Prototype(s) Specification, Development & Verification

Project

P11.1.5

Pre-Operational Validation

Project

SJU DoW WP11 v2.0

MGT

Page 11 of 72

SWP 11.1 Flight and Wing Operations Centres SWP 11.1

Title: Flight and Wing Operations Centres

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise for the Operational Requirements definition: 

Airspace Users requirements o

Scheduled (Main) Airlines

Regional Airlines

Low Fare Airlines

Charter/Leisure Airlines

Cargo operators

Business Aviation

General Aviation

State aircraft operators



SESAR ConOps



Aircraft performance



Fuel/environmental impact optimization



Aircraft/Mission Scheduling



Flight Planning



Operations Control



Post flight performance analysis and reporting



Applicable regulations and standards.

Specific expertise for the System Definition & Development: 

System engineering, prototyping and verification for Aircraft/Mission Scheduling, Flight Planning and Operations Control systems



Mathematical programming, optimization algorithms



Aircraft performance modelling



System Architecture, SOA (Service Oriented Architecture)



Data-link/data communication



Information modelling.

SJU DoW WP11 v2.0

Page 12 of 72

FOC/WOC Concept & Objectives

The SESAR target concept of operations is trajectory-based. The System Wide Information Management (SWIM) will allow all entitled ATM Network partners to share and manage real time 4D trajectory data during Sharing (SBT) and Reference (RBT) Business trajectory Phases:

YEARS

ATM PLANNING PHASES

DAYS

6 MONTHS

HOURS

Mid/Short Term

Long Term

MINUTES

Execution

BDT

Business LIFECYCLE OF THE Development BUSINESS TRAJECTORY Trajectory

SBT

Shared Business Trajectory

SBT

L F

RBT

Reference Business Trajectory

S ASAS

R D

Time-critical Actions

• Forecasts • Airline Plans • Schedule Dev. • Military Exercises • Major Events • Airspace Design

Negotiations on: • Schedules • Airspace • Routes • Resources

SWIMNet

• Local Capacity Mgt. • Traffic Balancing • Real-time Queue Mgt • Tactical De-confliction Plan refinement: • Arrival Capacity • Departure Planning • Impacting Events • Weather

This is in contrast to the existing, mainly point-to-point, information flows where most ATM Network partners have only partially complete information. Airspace Users (AU) will be responsible for managing the trajectories. As ATM trajectory constraints arise, each Airspace User eliminates them resulting in an efficient Network Operations Plan (NOP) that ANSPs and Airports agree to facilitate in line with performance requirements. Aim The aim of SWP11.1 is to define and validate FOC/WOC processes and supporting system(s) allowing all Airspace Users to plan and execute the most efficient Business/Mission Trajectory in line with performance requirements. Objectives Considering the Airspace Users’ needs, the objective of this Sub-Work Package is to address the integration and the validation of several concept elements in order to support the ATM Master Plan objectives. In particular, the specific objectives of the Sub-Work Package FOC/WOC are:  To define and validate the requirements for the Business/Mission Trajectory planning

SJU DoW WP11 v2.0

Page 13 of 72



 

and execution processes from an airspace user perspective, by ensuring its overall consistency; To define and validate the operational requirements for FOC/WOC in the SESAR target context, its role, responsibilities, interactions and exchanges with other ATM Network actors (in conjunction with the other connected WPs, SWPs and projects as required) and taking into account the FOC/WOC system definition and the context from a system architecture point of view. Due consideration has to be made to capture the needs of those Airspace Users that do not have an Operations Control Centre of their own; To prototype and validate the FOC/WOC identified capabilities for the SESAR target context and their interactions with the ATM Network; To integrate the FOC/WOC platform in the overall SESAR context to support integrated validation exercises with a particular attention to integration with SWIM.

All system development activities must be driven by defined operational requirements and interactions with related work in other Work Packages of the SESAR Programme. The SWP FOC/WOC is broken-down into a number of Projects whose objectives and detailed deliverables are described hereafter in the DOW. Work Breakdown Structure

SWP11.1 Flight and wing Operations Centres

MGT11.1.0 Co-ordination & Management

P11.1.1 Transversal Consistency of BT/MT requirements

P11.1.2 FOC/WOC Operational Requirements Definition

Operational Requirements Definition

P11.1.3 System Specification & Architecture

P11.1.4 Prototype(s) Specification, Development & Verification System Definition & Development

P11.1.5 Pre-Operational Validation

Pre-Operational Validation

SJU DoW WP11 v2.0

Page 14 of 72

Deliverables Deliverables from the projects within SWP11.1, in reference with the E-OCVM development model, will be the results of the Phase V1, V2 and V3 for the development of the core subsystems of the FOC/WOC. Main identified deliverables for each of the 3 Story Board Steps are the following: 

Definition of operational and performance requirements (requirements documents)



Prototype development and verification (prototypes, specifications)



Pre-Operational validation (validation test plan, validation reports).

The list of deliverables per project is further detailed in SWP11.1 projects’ descriptions. Risks The risk identified hereafter has to be considered as an initial list to be complemented by the bidders. Risk Management and detailed risks identification, opportunities and mitigation are expected to be taken into account and developed within the final proposal: 

Lack of synchronization with WP6, WP7, WP4 and WP5 (e.g. due to project starts in different timeframes) would contribute to the risk of Work Packages taking different assumptions. Reconciling at a too late stage would lead to inefficiency and difficulty to reach WP11 objectives.

Work Flow and dependencies Major external SWP11.1 dependencies with other WPs are depicted in this section.

SJU DoW WP11 v2.0

Page 15 of 72

Transversal Thread 

WP16 The goal of WP16 is to ensure a coordinated, integrated and consistent approach of Transversal Areas (TA) to facilitate the application of TA practices throughout the SESAR Development Phase. WP16 provides guidance and consolidates Safety, Security, Environment, Human Performance and Business Cases based on inputs from SWP 11.1.



WP3 Validation Infrastructure will capture, analyse and monitor the validation infrastructure requirements versus the capabilities of the existing validation infrastructure, recommending and managing the necessary adaptations and developments. Depending on WP11 validation needs (both SWP11.1 and SWP11.2), WP3 will be fed with V&V needs identifying validation infrastructure requirements and will coordinate the availability of the validation platforms or tools. When elements are missing for satisfying a validation need, WP3 and SWP11.1 will agree on the most appropriate way to develop them.



WPB Target Concept and Architecture Maintenance will maintain the related definitions and descriptions, set performance requirements and consolidate the performance results from validation exercises, increasing the maturity of the Target Concept & Architecture by taking into account SWP11.1 inputs, among others.



WPC The interface with WPC is foreseen to be handled primarily through WPB. According to the validation results, SWP11.1 will continuously elaborate recommendations on changes to be brought to the Target Concept by WPB and the ATM Master Plan by WPC Master Plan Maintenance.

Operational Thread 

SWP 11.1 receives and provides necessary inputs from/to Operational Work Packages (WP4, 5, 6, 7 and SWP 11.2.) to define and validate a consistent set of WP11 operational requirements System Thread 

SWP 11.1 receives and provides necessary inputs from/to System Work Packages (WP9, 10, 12, 13, 15 and SWP 11.2.) to define and validate a consistent set of WP11 system requirements.

SWIM Thread 

Development of Information Services and the harmonisation of relevant SWIM aspects will be conducted with respect to the needs of all Users: o

WP8 Information Management, development of relevant Information Services based on operational requirements consolidated by P11.1.1, reflected in the ATM Shared Information Services Reference Model (ISRM) and ATM Information Reference Model (AIRM). The prime interaction between SWP11.1 and WP8 is with P08.03.03 and P08.03.06 and potentially with the project P08.03.07.

WP14 SWIM, to harmonise the technical architecture and as such to develop SWIM compliant technical solutions.

SJU DoW WP11 v2.0

Page 16 of 72

P 11.1.0

Co-ordination and Management

P 11.1.0

Title: Co-ordination and Management

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise:   

Significant experience in large Programme Management. Multi cultural management experience. Comprehensive understanding of the SESAR Programme and of the ATM Network.

Concept & Objectives The Project 11.1.0 “Co–ordination & Management”, by the FOC/WOC SWP11.1 Leader, has the objective to carry out the management activities at SWP level. It monitors and controls the progress of the SWP and Projects activities for ensuring the achievement of the objectives and for delivering on time, with the required quality and making the best possible use of available resources by defining and applying relevant project management practices. It organises the review process leading to the acceptance in the view of delivering the Deliverable to EUROCONTROL/SJU. It coordinates the work of the different partners involved in the SWP. It reports progress, issues to EUROCONTROL/SJU and proposes mitigation actions as necessary. It ensures application of common SESAR methodologies and tools across the WP and provides assistance to that aim to all SWP11.1 projects. It ensures the interface with WP B, WP C to propose update to the concept of operation or architecture and to the Master Plan and the work program. It also ensures interfaces with any other appropriate Work Packages and SWP11.2 to ensure consistency across WPs. Description of Work The Sub-Work Package 11.1 shall comply with the Programme Management Plan (PMP) for the SESAR Programme. WP11 shall be integrated within the SESAR Programme and shall apply the same methodologies.

SJU DoW WP11 v2.0

Page 17 of 72

SJU engineering methodologies are the procedures, processes and tools that will be uniformly applied to ensure an overall consistency and coherence throughout the SESAR Work Programme. Each WP has to comply with the engineering methodologies defined within the SEMP (see reference documents). The SJU will ensure consistency of the activities within and between the Operational Work Packages (WP), the SWIM WP, and the System WP, and consolidate their results throughout the development lifecycle at the program level. In implementing the methodologies, SWP11.1 has to ensure its representation at the required level of expertise in working arrangements as defined by the SJU. Generic Work Package, SWP, and Project Leader role and responsibilities are described within the SESAR PMP (see referenced documents list). Without affecting the Project Leader roles the SWP11.1 Leader role differs from the SESAR PMP in the sense that it combines both Work Package and SWP Leader roles. Deliverables The following deliverables have been identified: 

D11.1.0-1: Management Initiation Report (within 60 calendar days after awarding of the Contract)



D11.1.0-2: Project Management Plan (including detailed Work Plan)



D11.1.0-3: Risk Management Plan



D11.1.0-4: Quarterly Progress Reports.

The list of deliverables will be subject to refinement during the Initiation Phase for final agreement. Risks The procedures and rules guiding risks identification, management and mitigation will be gathered in the SWP11.1 Risk Management Plan. The Risk Management Plan shall be in line with the risk management procedures described within the SESAR PMP. A draft version of it will be provided as part of the final offer and will be updated during the Initiation Phase.

SJU DoW WP11 v2.0

Page 18 of 72

P 11.1.1 Transversal Consistency Requirements (across WPs) P 11.1.1

Business/Mission

Trajectory

Title: Transversal Consistency of Business/Mission Trajectory Requirements (across WPs)

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise:        

SESAR ConOps, Aircraft performance Capacity/Demand balancing and optimization algorithms Traffic flow management Aircraft/Mission Scheduling Flight Planning Operations Control Post flight performance analysis and reporting.

Concept & Objectives Agreed 4D trajectories, specifically the RBT, are key items in SWIM. The information content of the Business/Mission trajectories is therefore a key element of the success of the Programme. Project P11.1.1 aims at contributing to consistency of trajectory requirements throughout the SESAR programme, though also acknowledging that changes to the already defined format may be required to facilitate requirements of SWP11.1. In addition, consistency of trajectory requirements need also to be established with other global initiatives, including efforts currently ongoing at ICAO, EUROCAE and RTCA as well as the US NextGen programme. The main objectives of this project are to ensure overall consistency and standardization in the definition of the Business/Mission Trajectory Management. As a consequence, the scope of this project will be: 

Define and consolidate performance and operational requirements as well as interoperability specifications from and Airspace User perspective;



Identify the gaps, if any, between the already existing set of operational requirements and the defined trajectory definition.



Identify the gap, if any, between the capabilities of currently available systems and technology solutions and the operational requirements and processes defined.

SJU DoW WP11 v2.0

Page 19 of 72

Description of Work

P11.1.1 Transversal Consistency of BT/MT requirements

Concept Consolidation Gap Analysis

Support to Standardisation

This project will address and solve this situation by collecting the different concept elements for Trajectory Management developed within the operational Work Packages, refining them, and contributing to defining an overall consolidated view of the Business/Mission Trajectory Management concept while ensuring consistency, coherency and supporting standardization. For this activity, the following main task has been identified: Concept Consolidation & Gap Analysis This task will consolidate and refine the operational and system requirements for the Business/Mission Trajectory Management as developed within the SESAR Work Packages from an Airspace User perspective (for example but not limited to):  Definition of the SBT including: content, management life-cycle, bidding processes, differences in SBT between Airspace Users, performance requirements.  Definition of the RBT including: content, management life-cycle and transition from SBT, performance requirements. This task will also identify the gaps between the Airspace Users’ requirements for a FOC/ WOC operations for the Business/Mission Trajectory and the requirements from the other SESAR Work Packages:: 

Undertaking a Gap analysis of the Overall Trajectory Management concept consolidation from the Airspace Users perspective.



Contribute to SEMP process to ensure technical coherence of Business/Mission Trajectory within the Programme.



Ensure technical coherence of Business/Mission Trajectory within the Programme from an Airspace User’s perspective.

Finally, the task will prepare deliverables to be checked by the Operational Requirements Definition and the other operational WPs for the overall consolidation within SWP11.1. Support to Standardisation While it is clearly recognised that standardisation is itself outside of the scope of the SESAR programme, it is no less clear that Standards and Regulatory acceptance are important prerequisites to implementation. This task is expected to identify and consolidate future standardisation requirements and thereby contribute material in support of the standardisation work in external bodies such as EUROCAE, RTCA, the ARINC hosted AEEC and CENELEC for:  Trajectory information: the content of the SBT, RBT. It is by definition in line with what should be expected for example from advanced flight planning systems and airborne flight management systems (in close cooperation with WP9 in particular).

SJU DoW WP11 v2.0

Page 20 of 72



Other FOC/WOC standardization needs to be identified during the Initiation and later Execution of the project.

Many SESAR projects are expected to provide material which will support standards activities. Specific coordination will have to be identified, as required, from SESAR projects to an ongoing or planned standards development. SESAR funded project effort is restricted to that required for the necessary coordination to achieve a coherent link between projects and standardisation. The funding of defined tasks within this project to support this coordination is restricted to one of the project partner’s participation at relevant meetings where 11.1.1 should clearly represent the SESAR project in this activity, rather than their own individual organisation. The funding to attend such external meetings is restricted to meetings where SESAR developed material is being presented or discussed, or where there is specific need for the project to support comments made on a document being developed within the standards working group. “Passive” participation will not be supported. It is assumed that widespread participation to standards activities however will still be encouraged and supported directly by industry, including SESAR Partners. Without this type of ‘voluntary’ participation important standardisation developments e.g. in EUROCAE may not be sufficiently resourced. Work Flow and Dependencies P11.1.1 is dependent on the following operational Work Packages: WP4, WP5, WP6, WP7, WP8 and WP9 as well as WPB, from which it needs to collect and then consolidate the documentation specifying operational, performance requirements, as well as interoperability specifications in order to ensure overall consistency of the Business/Mission Trajectory. 6.1. WPC is the focal point for standardisation planning for the development of the roadmap. P11.1.1 should feed their identification of justified standardisation needs through the relevant federating projects and thereby into WP B. The outputs of this project, to be assessed by WPB, will be used by P11.1.2, P11.1.3, P11.1.4 and P11.1.5 to perform their activities. Deliverables The following final deliverables will be produced iteratively for each Step: 

D11.1.1-1: Definition of the Trajectory requirements for Step 1, including gap analysis, support to standardization report from Airspace Users perspective and outlook for Step 2 and 3.



D11.1.1-2: Definition of the Trajectory requirements for Step 2, including gap analysis, support to standardization report from Airspace Users perspective including outlook for Step 3.



D11.1.1-3: Definition of the Trajectory requirements for Step 3, including gap analysis, support to standardization report from Airspace Users perspective.

The list of identified deliverables will be subject to refinement during the Initiation Phase for final agreement. EUROCONTROL/SJU Input EUROCONTROL Furnished Input EUROCONTROL proposes to support the execution of this project by providing contribution in areas/tasks where EUROCONTROL believe the expertise brought will be the most useful to the

SJU DoW WP11 v2.0

Page 21 of 72

project and adequate with EUROCONTROL resource availability. The activities identified and proposed to perform are the following : 

Support to coordination with WPB for the overall consistency of the Business/Mission Trajectory Management concept from the various Operational Work Packages



Contribution to the civil/military Business/Mission Trajectory Management concept from the ATM and AU perspective.

The technical proposals are expected to provide a first view of when and how this proposed contribution would best fit their plan. These activities will be performed by EUROCONTROL staff under the control of the selected Contractor, and the effort would not exceed the average value of ~1,1 FTE per year, for the whole duration of the project, spread over the following expertise: 

Network Operations



Military Operations (ATM)



Airport Operations



TMA Operations

Final agreement and planning will be achieved between EUROCONTROL and the Contractor during the Initiation Phase. SJU Furnished Input The SJU proposes to support the execution of this project where necessary by providing contributions of civil Airspace User expertise in areas/tasks where the SJU believe the expertise brought will be the most useful to the project. The SJU resources will be provided through the SJU Airspace User Framework Contract (Tasking Contract) subject to availability. The Project Manager, in co-ordination with the Sub-Work Package Leader, shall define the Airspace User Task Requirements, Deliverables, Deadlines and the respective Airspace User Categories, Expertise type and associated Effort. On an annual basis these shall be agreed between the SJU and the Project. Any execution of these activities will be under the control of the SJU, but co-ordinated by the Project. The estimated effort required by the Project should be identified during the call for tender and refined with the SJU during the Initiation Phase. Risks The risks identified hereafter have to be considered as an initial list to be complemented by the bidders. Risk Management and detailed risks identification, opportunities and mitigation are expected to be taken into account and developed within the final proposal:  

Needed input from the Operational Work Packages not available, not complete, or not at the level of detail or maturity needed (lack of synchronization would contribute to the risk of WPs taking different assumptions) Lack of coordination on standardisation activities.

Management See P11.1.0 “Co-ordination & Management” for additional information.

SJU DoW WP11 v2.0

Page 22 of 72

P 11.1.2

FOC/WOC Operational Requirements Definition

P 11.1.2

Title: FOC/WOC Operational Requirements Definition

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise:        

Concept & Objectives Project P11.1.2 focuses on FOC/WOC operational requirements and aims at defining the requirements from an Airspace User’s perspective and comparing them against already developed requirements within the SESAR programme. Emphasis is placed on capturing the specific and sometimes unique operational requirements from users with and without FOCs, including general aviation, business aviation, commercial aviation, as well as military aviation, operating within and outside European airspace. The main objectives of this project are:  

 

Define FOC/WOC operational and performance requirements for all Airspace Users categories including for MET services. To ensure that the different sets of operational requirements deliver compelling business/mission advantages to the Airspace Users and are compliant with SESAR objectives. To manage the integration of new operational requirements into other operational work packages to solve the gap, if any, identified in the Project 11.1.1. Analyse Military specific topics within the context of WP11 in terms of impact on WOC and interface between WOC and SESAR.

Considering the deadlines set for the programme the following initial prioritization has been indentified and shall be further developed and agreed during the Initiation Phase: Aircraft/Mission Scheduling Flight Planning Operations Control Post flight performance analysis and reporting function

SJU DoW WP11 v2.0

Step 1 X X

Step 2 X X X

Step 3 X X X X

Page 23 of 72

Description of Work P11.1.2 FOC/WOC Operational Requirements Definition

FOC Ops Requirements

WOC Ops Requirements

As this project addresses specific operational issues depending on the different Airspace Users categories, the two major tasks hereafter have been identified. However, the two tasks should be closely coordinated to ensure the greatest possible level of alignment between civil and military requirements. Task 11.1.2.1 FOC Ops Requirements Requirements Definition This activity shall define the operational requirements for all categories of civil Airspace Users, while ensuring consistency and coherency of the Business Trajectory Management concept. The operational requirements shall cover the main aspects of FOC operations:  Aircraft scheduling  Flight planning  Operations control  Post flight performance analysis and reporting. The operational requirements shall also support/solve the gap, if any, identified in the project 11.1.1. Requirements Definition for MET  The activity will be performed for addressing all the operational requirements for MET services and ensure that these requirements are well taken into account in SWP11.2 (MET Services). Ops Interoperability This activity will address the definition of those essential requirements for all global operators flying outside European airspace. The objective will be to guarantee a globally optimised trajectory with a multi-mode capability built into all the essential trajectory management functions. The following key interoperability issues will be addressed:  Optimising Business Trajectories including outside European Airspace  Filing and negotiating multi-Region Business Trajectories  Inputs to international Standardisation. Support to presentation & acceptance of the operational requirements by the broader community of Civil Airspace Users The objective of this task is to support the global acceptance by the Airspace Users community of the concepts developed in the previous activities. The acceptance of those new concepts is to be reached through iterative collegial reviews of the operational requirements and in close coordination with the SJU. Task 11.1.2.2 WOC Ops Requirements Requirements Definition

SJU DoW WP11 v2.0

Page 24 of 72

This activity will be closely coordination with Task 11.1.2.1 and will define military specific requirements. The operational requirements shall cover the main aspects of WOC operations:  Mission scheduling  Flight planning  Operations control  Post flight performance analysis and reporting. The operational requirements shall also support/solve the gap, if any, identified in the project 11.1.1. Requirements Definition for MET  The activity will be performed for addressing all the operational requirements for MET services and ensure that these requirements are well taken into account in SWP11.2 (MET Services). Ops Interoperability This activity will address the definition of those essential requirements for all international military operators flying outside European Airspace. The objective will be to guarantee a globally optimised trajectory with a multi-mode capability built into all the essential trajectory management functions. The following key interoperability issues will be addressed:  Ensuring interoperability between FOC and WOC Trajectories o Definition of key functions, e.g. moving Safety corridor around the 4D Trajectory for training missions o Description of 4D Trajectory modelling including moving safety corridor o Airspace security issues  Optimising Mission Trajectories including outside European airspace  Filing and negotiating multi-Region Mission Trajectories  Ensuring interoperability between WOC Trajectories and Airspace Users without Ops Centres  Inputs to international Standardisation  Ensure addressing all relevant Military platforms (fighter, fighter bomber, transport etc), including UAS. Support to presentation & acceptance of the operational requirements by the broader community of military Airspace Users The objective of this task is to support the global acceptance by the Airspace Users community of the concepts developed in the previous activities. The acceptance of those new concepts is to be reached through iterative collegial reviews of the operational requirements and in close coordination with the SJU.

Work Flow and Dependencies P11.1.2 receives and provides necessary inputs from/to Operational Work Packages (WP4, 5, 6, 7 and SWP 11.2.) to define and validate a consistent set of operational requirements. The dependencies have to be further developed in the proposals from PQIPs and, after contract award, during the initiation phase.

SJU DoW WP11 v2.0

Page 25 of 72

Deliverables The following deliverables will be produced iteratively for each Step (1 to 3) and will include Operational Service and Environment Descriptions (OSEDs), MET Operational requirements document, Safety and Performance Requirements (SPR), Operational Interoperability (INTEROP) Specifications. Clear distinction has to be made for Aircraft Scheduling (SBT), Flight Planning (initial RBT), Operations Control (management of adjustments from initial RBT) and Post flight performance analysis and reporting: 

D11.1.2-1: FOC/WOC operational and performance requirements for Step 1 (Quick Wins) including outlook for Step 2 and 3



D11.1.2-2: FOC/WOC operational and performance requirements for Step 2 including outlook for Step 3.



D11.1.2-3: FOC/WOC operational and performance requirements for Step 3.

Contribution to the definition of operational Specificities for the main aspects of the FOC operations - Task 11.1.2.1



Coordination of the definition of Military operational Specificities - Task 11.1.2.2



Contribution to the operational Interoperability between Business and Mission Trajectory - Task 11.1.2.2

Final technical proposals are expected to provide a first view of when and how this proposed contribution would best fist their plan. These activities will be performed by EUROCONTROL staff under the control of the selected Contractor, and the effort would not exceed the average value of ~0,5 FTE per year, for the whole duration of the project, spread over the following expertise: 

Network Operations



Airport Operations



Military Operations (ATM).

SJU DoW WP11 v2.0

Page 26 of 72

Categories, Expertise type and associated Effort. On an annual basis these shall be agreed between the SJU and the Project. Any execution of these activities will be under the control of the SJU, but co-ordinated by the Project. The estimated effort required by the Project should be identified during the call for tender and refined with the SJU during the Initiation Phase. Risks The risks identified hereafter have to be considered as an initial list to be complemented by the bidders. Risk Management and detailed risks identification, opportunities and mitigation are expected to be taken into account and developed within the final proposal: Given the diversity of Airspace Users operating in European airspace and Non-European airspace: 

Operational requirements of all categories of Airspace Users not adequately taken into account



Stability of the operational requirements: Multi loops of development generating costs & delays



Too large and complex range of operational requirements.

Management See P11.1.0 “Co-ordination and Management” for additional information.

SJU DoW WP11 v2.0

Page 27 of 72

P 11.1.3

System Specification & Architecture

P 11.1.3

Title: System Specification & Architecture

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise: 

System engineering for Aircraft/Mission Scheduling, Flight Planning, Operations Control systems and Post Flight Analysis systems



System Architecture, SOA (Service Oriented Architecture)



Applied mathematics, algorithm development and optimisation, aircraft performance modelling



Datalink/data communication



Information modelling



Methodologies of general system/software engineering (system requirements definition, enterprise and system architecture design and development).

Concept & Objectives The scope of ‘System Specification’ is more fully defined in the SESAR SEMP and includes: 

System Requirement Definition



Interface Requirement Definition



System Performance Requirement Definition

System Architecture activities are defined in the SESAR SEMP and are conducted in close cooperation with WPB4.3 (consistency with other WPx.7 projects). Considering the Airspace Users’ and the ATM network stakeholder needs in the SESAR target concept context, the following high-level Systems have been identified as core to be developed within the scope of SWP11.1 (including interface with SWIM): 

Aircraft/Mission Scheduling



Flight Planning



Operations Control



Post flight performance analysis and reporting function

As a consequence, the following Systems (and their respective functions/processes), internal to FOC/WOC business model, are recognised as important elements, but considered outside the direct scope of P11.1.3: 

Network Management systems



Crew scheduling systems



Passenger handling systems

SJU DoW WP11 v2.0

Page 28 of 72

P11.1.3 covers the definition of System, performance and architecture requirements for a FOC/WOC. The main objectives of this project are: 

To consolidate the system specifications and to define the functional and non-functional requirements for FOC/WOC systems. These functions will describe sets of inputs, processing and the outputs.



To use the output of the previous P11.1.1 and P11.1.2 for driving the definition of the logical and technical reference architecture for FOC/WOC systems.



To define the internal and external interface requirements for FOC/WOC core functionalities/systems.



To define Performance functionalities/systems.



To ensure the traceability between the operational and technical/system requirements.



To develop the overall FOC/WOC Architecture, system decomposition and document the services provided/consumed; in cooperation with WPB4.3.

Requirements

for

the

identified

FOC/WOC

core

Considering the deadlines set for the programme and related to the high-level system descriptions described above the following initial prioritisation has been indentified and shall be further developed and agreed during the Initiation Phase: Aircraft/Mission Scheduling Flight Planning Operations Control Post flight performance analysis and reporting function

Step 1 X X

Step 2 X X X

Step 3 X X X X

Description of Work P11.1.3 System Specification & Architecture

- FOC/WOC System Specification -FOC/WOC Architecture

The definition of the functional and non-functional requirements along with the reference architecture will enable the Airspace Users to assess if all defined and consolidated operational requirements have been fulfilled. The functional requirements will describe sets of inputs, behaviour, and the outputs, including interfaces. Once defined, they will drive the following activities: 

The detailing of the core components of future FOC/WOC systems



The detailing of the future core components of Airspace Users not operating FOCs



The identification of the WOC components impacted by SESAR concept and operations integration (including functional requirements for military missions like operations, missions, Unmanned Aerial Systems (UAS) and training)



The definition of the target logical and technical architecture for FOC/WOC systems



The definition of internal and external interfaces requirements



The definition of the performance target requirements for future FOC/WOC systems

SJU DoW WP11 v2.0

Page 29 of 72

The project is divided into the following tasks: Task T11.1.3.1 FOC/WOC System Specification Core components of future FOC/WOC and AU systems not operating FOCs This (sub-) task identifies and details the core components of the future FOC/WOC. Interfaces Definition This (sub-) task identifies and details the internal and external interfaces requirements for the core components/systems of the future FOC/WOC. Use Cases This (sub-) task will cover ď&#x201A;ˇ

The definition of Use Cases addressing the business/performance area and the operational needs of the future FOC/WOC

ď&#x201A;ˇ

The functional requirements definition for the Cost Benefit Analysis on the performance of a future FOC/WOC system

Task T11.1.3.2 FOC/WOC Architecture Target Architecture This (sub-) task defines the target logical and technical architecture for future FOC/WOC. The approach to the described activities (production of the deliverables) will be iterative due to the interaction within the SWP11.1. Work Flow and Dependencies This project will be relying on the inputs provided by P11.1.1 and P11.1.2, as well as those coming from SWPB4.3 (High-Level Target Architecture), WP9 (Air-Ground Infrastructure and Airborne AIS/MET Services), WP8 (P8.1.3 and P8.3.10), WP14 (P14.1.4), and on WP3 for the overall integration requirements. The output of this project will serve as a basis for the full specification, development and verification of the FOC/WOC Systems to be performed in P11.1.4. Deliverables

SJU DoW WP11 v2.0

Page 30 of 72

The following deliverables will be produced iteratively: 

D11.1.3-1: Step 1 Use Cases and System Requirements for FOC/WOC systems



D11.1.3-2: Step 1 FOC/WOC Systems interfaces requirements



D11.1.3-3: Step 1 FOC/WOC Architecture



D11.1.3-4: Step 2 Use Cases and System Requirements for FOC/WOC systems



D11.1.3-5: Step 2 FOC/WOC Systems interfaces requirements



D11.1.3-6: Step 2 FOC/WOC Architecture



D11.1.3-7: Step 3 Use Cases and System Requirements for FOC/WOC systems



D11.1.3-8: Step 3 FOC/WOC Systems interfaces requirements



D11.1.3-9: Step 3 FOC/WOC Architecture

Supporting documentation tasks include refinement of concept of operations, SEMP sessions and reviews’ recommendations. The list of identified deliverables will be subject to refinement during the Initiation Phase for final agreement. EUROCONTROL/SJU Input EUROCONTROL Furnished Input None SJU Furnished Input The SJU proposes to support the execution of this project where necessary by providing contributions of civil Airspace User expertise in areas/tasks where the SJU believe the expertise brought will be the most useful to the project. The SJU resources will be provided through the SJU Airspace User Framework Contract (Tasking Contract) subject to availability. The Project Manager, in co-ordination with the Sub-Work Package Leader, shall define the Airspace User Task Requirements, Deliverables, Deadlines and the respective Airspace User Categories, Expertise type and associated Effort. On an annual basis these shall be agreed between the SJU and the Project. Any execution of these activities will be under the control of the SJU, but co-ordinated by the Project. The estimated effort required by the Project should be identified during the call for tender and refined with the SJU during the Initiation Phase. Risks The risks identified hereafter have to be considered as an initial list to be complemented by the bidders. Risk Management and detailed risks identification, opportunities and mitigation are expected to be taken into account and developed within the final proposal: 

4D trajectory definition will change the existing systems for flight planning. Without a consolidated definition of 4D trajectory at this time there might be an high probability that re-work might be needed during the early phases of this project



Scope of requirements received too large or too complex



Non appropriate integration of military specificities



Unstable or evolving requirements.

SJU DoW WP11 v2.0

Page 31 of 72

Management See section P11.1.0 “Co-ordination and Management” for additional information.

SJU DoW WP11 v2.0

Page 32 of 72

P 11.1.4

Prototype(s) Specification, Development & Verification

P 11.1.4

Title: Prototype(s) Specification, Development & Verification

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise: 

System engineering, prototyping and verification for Aircraft/Mission Scheduling, Flight Planning, Operations Control systems and Post Flight Analysis systems



System Architecture, SOA (Service Oriented Architecture)



Applied mathematics, algorithm development and optimisation, aircraft performance modelling



Datalink/data communication



Information modelling



Methodologies of system/software engineering (system requirements definition, enterprise and system architecture design and development),



SWIM technical infrastructure.

Concept & Objectives As already highlighted within P11.1.3, considering the Airspace Users’ and the ATM Network stakeholder needs in the SESAR target concept context, the following high-level Systems have been identified as core to be developed within the scope of SWP11.1 (including interface with SWIM): 

Aircraft/Mission Scheduling



Flight Planning



Operations Control



Post flight performance analysis and reporting function

P11.1.4 covers the full technical specification, development, verification and integration with SWIM Infrastructure of the identified Systems for the future FOC/WOC, which can be used to validate operational requirements, System specification and architecture for the Business/Mission Trajectory throughout its entire life cycle, for all categories of Airspace Users in 3 steps. The main objectives of this project are: 

Fully translate the System specification and architecture from P11.1.3 into technical specifications regarding the core functionalities of each future FOC/WOC System.



The development and verification of the identified core functionalities as (sub-)systems



To define the technical specification for the FOC/WOC System/sub-system/core functionality including interfaces with the SWIM Infrastructure



To develop the FOC/WOC systems interfaces with the SWIM network and technical infrastructure

SJU DoW WP11 v2.0

Page 33 of 72



To verify and validate the exchange of data elements both to and from the SWIM network



To consolidate results into a verification report documenting and validating the target architecture, technical integration approach and data exchange between FOC/WOC systems and the SWIM network.

The (sub-) system prototype(s) (integrated with SWIM) delivered by this project will provide the ability to fully validate the performance of FOC/WOC systems. Considering the deadlines set for the programme and related to the high-level system descriptions described above the following initial prioritisation functions/components has been indentified and shall be further developed and agreed during the Initiation Phase: Aircraft/Mission Scheduling Flight Planning Operations Control Post flight performance analysis and reporting function

Step 1 X X

Step 2 X X X

Step 3 X X X X

Description of Work Aircraft/Mission Scheduling

P11.1.4 Prototype(s) Specification, Development & Verification

Flight Planning

Operations Control

Post Flight Performance Analysis & Reporting

Once the FOC/WOC core components are identified (output from P11.1.3), the proposed work plan is to move towards the full development of System/sub-system/core functionality to be verified and then integrated in the SWIM network. For this reason this project shall synchronise with the SWIM progress and activities within SWIM Work Packages through an iterative development of the needed interfaces for the FOC/WOC prototype with the SWIM Infrastructure as corresponding SWIM services become available through SWIM thread Work Packages (WPB, WP8, WP14): 

SWIM ground-ground limited services development phase o



E.g., MET, Aeronautical, Surveillance information sharing

SWIM ground-ground extended services development phase o

E.g., NOP related services, SBT, RBT, Mission Trajectory information sharing.

As far as the integration of WOC with SWIM Infrastructure is concerned, some constraints will be taken into account: the WOC (and higher levels) are integrated, on the military side, within a military structure which provides its own constraints (e.g. security and decision making process to modify a mission, civil-military co-ordination). It has to be highlighted that this military

SJU DoW WP11 v2.0

Page 34 of 72

structure is an element of national sovereignty, and can therefore significantly vary from one Nation to another. The development activities will not develop from scratch, but build to the greatest extent possible on the capabilities of the project contributors, verify (where and when relevant) their mutual connections/interfaces, then proceed with FOC/WOC systems verification and their integration within the SWIM network. For each of the task domains below one or maximum two prototypes will be developed. The project is divided into the following tasks: Task T11.1.4.1 Aircraft/Mission Scheduling Prototype Development & Verification Within this task the following activities have been identified for each V cycle (3 steps):     

Turn operational, systems and architectural requirements into innovative technical specifications for developing software solutions for FOC/WOC systems Develop the future FOC/WOC core sub-systems and proceed to their verification Define optimisation algorithms and refine aircraft performance modelling as appropriate Integrate and Verify the FOC/WOC system Consolidate the results into a coherent integrated verification report (including recommendations regarding the FOC/WOC system architecture and interface components)

Integration with SWIM Technical Infrastructure The following main activities have been identified:       

Analysis of FOC/WOC information management demand Analysis of the SWIM information models, services and interfaces provided by WP8 and WP14 FOC/WOC system interfaces technical specification Development of the FOC/WOC (sub-)system interfaces to the SWIM infrastructure Verification of the FOC/WOC system integrated with the SWIM network Consolidate results into a coherent integrated verification report (including recommendations regarding the FOC/WOC system architecture) Support the operational validation as undertaken by P11.1.5.

Task T11.1.4.2 Flight Planning Prototype Development & Verification Within this task the following activities have been identified for each V cycle (3 steps):     

Integration with SWIM Technical Infrastructure

SJU DoW WP11 v2.0

Page 35 of 72

The following main activities have been identified:       

Task T11.1.4.3 Operations Control Prototype Development & Verification Within this task the following activities have been identified for each V cycle (3 steps):     

Turn operational, systems and architectural requirements into innovative technical specifications for developing software solutions for FOC/WOC systems Develop the future FOC/WOC core sub-systems and proceed to their verification Define optimisation algorithms Integration and Verification of the FOC/WOC system Consolidate the results into a coherent integrated verification report (including recommendations regarding the FOC/WOC system architecture and interface components)

Integration with SWIM Technical Infrastructure The following main activities have been identified:       

Task T11.1.4.4 Post Flight Performance Analysis & Reporting Prototype Development & Verification Within this task the following activities have been identified for each V cycle (3 steps):    

Turn operational, systems and architectural requirements into innovative technical specifications for developing software solutions for FOC/WOC systems Develop the future FOC/WOC core sub-systems and proceed to their verification Integrate and Verify the FOC/WOC system Consolidate the results into a coherent integrated verification report (including recommendations regarding the FOC/WOC system architecture and interface components)

Integration with SWIM Technical Infrastructure The following main activities have been identified: 

Analysis of FOC/WOC information management demand

SJU DoW WP11 v2.0

Page 36 of 72

     

Analysis of the SWIM information models, services and interfaces provided by WP8 and WP14 FOC/WOC system interfaces technical specification Development of the FOC/WOC (sub-)system interfaces to the SWIM infrastructure Verification of the FOC/WOC system integrated with the SWIM network Consolidate results into a coherent integrated verification report (including recommendations regarding the FOC/WOC system architecture) Support the operational validation as undertaken by P11.1.5.

The approach to the described activities (production of the deliverables) will be iterative due to the interaction within the SWP11.1. Work Flow and Dependencies This project will be relying on the inputs provided by P11.1.3, as well as those coming from WPB (High-Level Target Architecture), WP9 (Air-Ground Infrastructure and Airborne AIS/MET Services), WP8 (P8.1.3 and P8.3.10), WP14 (P14.1.4), and on WP3 for the overall integration requirements. In particular, the implementation of FOC/WOC functions that exchange information with other stakeholders will need to be aligned with the information models and services defined in 8.1.3 (AIRM) and 8.3.10 (ISRM). For the connection to the SWIM middleware, the interfaces provided by P14.01.04 need to be implemented. Project 14.04 will provide support to other technical projects on implementing these interfaces. While some ‘factory integration’ between the FOC/WOC prototypes and the SWIM middleware prototypes is foreseen to take place in WP11, the actual integration of all SESAR prototypes in validation platforms is planned to be performed by WP3. The prototype(s), output of this project, will serve as a basis for the pre-operational validation in P11.1.5. Deliverables

SJU DoW WP11 v2.0

Page 37 of 72

Within each task, the following deliverables will be produced iteratively: 

D11.1.4-1: Step 1 System Specification for FOC/WOC (sub-) system development



D11.1.4-2: Step 2 System Specification for FOC/WOC (sub-) system development



D11.1.4-3: Step 3 System Specification for FOC/WOC (sub-) system development



D11.1.4-4: Step 1 FOC/WOC (sub-) system-to-SWIM interfaces specifications



D11.1.4-5: Step 2 FOC/WOC (sub-) system-to-SWIM interfaces specifications



D11.1.4-6: Step 3 FOC/WOC (sub-) system-to-SWIM interfaces specifications



D11.1.4-7: Step 1 verified FOC/WOC (sub-) system available for operational validation



D11.1.4-8: Step 2 verified FOC/WOC (sub-) system available for operational validation



D11.1.4-9: Step 3 verified FOC/WOC (sub-) system available for operational validation



D11.1.4-10: Consolidated Verification Report.

SJU DoW WP11 v2.0

Page 38 of 72



Scope of requirements received too large or too complex



Non appropriate integration of military specificities



Unstable or evolving requirements



SWIM network not established/built and, as a consequence, not available for SWP11.1 integration and testing activities.

Management See P11.1.0 “Co-ordination and Management” for additional information.

SJU DoW WP11 v2.0

Page 39 of 72

P 11.1.5

Pre-Operational Validation

P 11.1.5

Title: Pre-Operational Validation

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise: 

SESAR ConOps



Aircraft/Mission Scheduling



Flight Planning



Operations Control



Post flight performance analysis and reporting

  

Applicable regulations and standards Good validation expertise (methodologies, techniques and associated tools) Broad knowledge of Enterprise Architecture.

Concept & Objectives Project P11.1.5 aims at demonstrating that the Business/Mission Trajectory concepts developed in SWP11.1, and implemented in the FOC/WOC prototype(s) systems, are performing in line with end user expectations. In particular, it will:  Elaborate the SWP11.1 Validation Plan in line with the Overall Validation strategy defined by the SJU, and the detailed validation needs.  Ensure that the various validation activities e.g. operational feasibility assessment, Transversal Areas assessments (safety, security, environment; Human Performance), performance assessment and data supporting CBA are planned appropriately in the validation lifecycle steps.  Plan validation exercises considering in particular levels of maturity, dependencies, resources (e.g. platform, experts).  Co-ordinate with WP3 the integrated validation related activities.  Perform the pre-operational validation of solutions developed within SWP11.1. This project mainly participates to the R&D validation part with regards to the V cycle.

SJU DoW WP11 v2.0

Page 40 of 72

Description of Work

P11.1.5 Pre-Operational Validation

Validation Plan definition

Pre-Operational Validation (FOC/WOC stand-alone)

Integrated Pre-Operational Validation (across WPs)

Pre-Operational Validation

This project will address: 

The integration and the compatibility of the various operational concept elements or functions of the FOC/WOC operating context.



The interoperability of the various operational concept elements or functions of the FOC/WOC operating context with other operational context such as Network, En-Route, TMA and Airport.

In order to accomplish its Validation related objectives, the main tasks for this project are: Task T11.1.5.1 Validation Plan Definition This task will cover the following activities: 

Application of the Overall Validation Strategy by: o

Production of the initial baseline documents regarding the WP Validation Strategy and prepare the validation plans and scenarios for the operational and system activities (E-OCVM step 1).

Manage a common validation framework by (E-OCVM step1 and 2)  Establishing common indicators and metrics to support integration.  Consolidating and sharing of best practice in measurement methods and tools.  Consolidating requirements for simulation platforms, modelling tools and pre-industrialised prototypes.  Defining the validation assumptions and hypothesis.  Identifying the means of achieving suitable coverage of the concept and representativeness in studies.  Linking dependencies between validation activities. Ensure that the detailed validation plan produced is coherent with the Overall validation strategy (E-OCVM step 2).

o 

Identification of validation requirements to match performance targets.

As far as the WOC Validation is concerned, some Military Ops specificities will be also validated; as a consequence, the detailed validation plan will include:  Confidentiality of Military Missions

SJU DoW WP11 v2.0

Page 41 of 72

  

Performance of military communication Interoperability Data security.

Task T11.1.5.2 Pre-Operational Validation (FOC/WOC stand-alone) This task will cover the following activities: 

Planning and execution of large scale trials validations based on pre-industrial prototype(s) developed by the system projects (within WP11.1).



Performance and safety assessments incl. Cost-Benefit data supporting CB Analysis



Interoperability assessment



Production of detailed validation reports.

Task T11.1.5.3 Integrated Pre-Operational Validation (across WPs) This task will cover the following activities: 

Participation to pre-operational validation exercises across all other SESAR Work Packages.



Production of detailed validation reports.

Work Flow and Dependencies The inputs to this project will be the prototype(s) developed within P11.1.3 and P11.1.4 (and other validation tools), which will be the artefacts used to conduct the validation exercises. A strong coordination shall be in place with the others SESAR Work Packages and in particular with WP3. WP16 will provide the framework and support to build the TA cases. Deliverables The following deliverables will be produced iteratively for each Step (1 to 3): 

D11.1.5-1: Validation Plan for SWP11.1 FOC/WOC.



D11.1.5-2: Validation Reports for stand-alone FOC/WOC validation (including input to Deployment Scenarios and consolidated input to TA Cases)



D11.1.5-3: Validation Reports for Integrated Validation across WPs (including input to Deployment Scenarios and consolidated input to TA Cases).

SJU DoW WP11 v2.0

Page 42 of 72



Set-up and potential use of the DARTIS* platform for Pre-Operational Validation across Work Packages (WP7&13/WP11) - Task 11.1.5.2&3



Support to the execution of validation exercises for Pre-Operational Validation across Work Packages (WP7&13/WP11) - Task 11.1.5.3

PQIPs final technical proposals are expected to provide a first view of when and how this proposed contribution would best fist their plan. These activities will be performed by EUROCONTROL staff under the control of the selected Contractor, and the effort would not exceed the average value of ~0,8 FTE per year, for the whole duration of the project, spread over the following expertise: 

Network Operations



Airport Operations



Military Operations (ATM).

Validation plan not fully compliant with the overall SESAR validation plan: lack of maturity



Stability of the prototypes and completeness of the validation strategy



Interoperability with the deliverables of other Work Packages.



Complex & too large range of interfaces and data sources.

Management See P11.1.0 “Co-ordination and Management” for additional information.

SJU DoW WP11 v2.0

Page 43 of 72

* DARTIS application has been initially developed by EUROCONTROL in the frame of the Future ATFM (FAM) concept, in support of CAMES project (CO-OPERATIVE ATM MEASURES FOR A EUROPEAN SINGLE SKY) so as to perform real-time simulations and on site trials. The CAMES project objectives were to develop operational procedures requiring dynamic traffic flow co-ordination across more than one ACC in order to reduce sector overloads (or demand/capacity unbalances). The DARTIS platform offers proper HMI and functionalities to address these objectives in a collaborative manner with the concerned ACC’s, the CFMU (Netwotk Manager) and the Aircraft Operators. In the context of the SESAR programme, the DARTIS platform will evolve to support gaming, real-time and shadow mode Demand and Capacity Balancing (DCB) simulations covering the entire ECAC region or specific sub-regions. To perform SESAR validation the DARTIS platform may run in stand-alone  network level or may be integrated with other simulation platforms  Network and Flight Operations Centre  Network and airport CDM  Network and En-route and TMA This distributed agent-based architecture allows conducting human-in-the-loop gaming simulations related to the elaboration, negotiation and implementation of dynamic Demand and Capacity Balancing (DCB) measures including queuing. The main features are:  Network Operation Plan (NOP) with Business Trajectory Management,  Network monitoring functions,  Flight Operations Centre Modelling and its associated Human Machine Interface,  Human Machine Interface for the regional, sub-regional and local (APOC) network manager levels,  Edition of predefined dynamic DCB scenarios,  Airspace configuration modification,  Functions to support the assessment and negotiation of dynamic DCB measures (including what-if functions),  Queue management function (for en-route, arrival and AMAN). Demonstration and documentation about DARTIS platform can be made available upon request.

SJU DoW WP11 v2.0

Page 44 of 72

Level 2 & 3 â&#x20AC;&#x201C; Work-Package Description

SJU DoW WP11 v2.0

Page 45 of 72

Sub-Work Package 11.2 MET Services and Projects overview Sub Work package n째

Sub Work Package title

Project n째

Project title

Type of activity (MGT/Project)

SWP11.2

Meteorological Services (MET)

P11.2.0

Co-ordination & Management

P11.2.1

Requirements for MET Information

Project

P11.2.2

MET Information System Development, Verification & Validation

Project

SJU DoW WP11 v2.0

MGT

Page 46 of 72

SWP 11.2 Meteorological Services SWP 11.2

Title: Meteorological Services

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise for the Operational Requirements Definition: 

Good knowledge of Operational Concepts developments, and in particular of the SESAR Concept of Operations Document (CONOPS).



Comprehensive understanding of the ATM Network (actors, operations, architecture and business drivers).



Broad experience in operational concept analysis.



Good knowledge of the Airspace Users, Network Operations, En-Route, TMA, and Airport operational context.



Good knowledge of procedures, processes and systems relevant to this SWP.

Specific expertise for the System Definition & Development: 

Methodologies of system/software engineering (system definition, enterprise architecture design and development).



Organisation and management principles, structures & processes.



Business process design & modelling.



Verification and validation expertise



ATM system manufacturing

Specific expertise for Pre-Operational Validation: 

Aviation Meteorology, Meteorology in ATM operations and ATM systems;



Meteorology addressing global, regional and local applications;



Numerical assimilation, analysis and forecasting techniques;



High level of experience in concept and operational validation.



Good validation expertise (methodologies, techniques and associated tools).



Comprehensive understanding of the civil and military ATM Network (actors, operations, architecture and business drivers).

SJU DoW WP11 v2.0

Page 47 of 72

Concept & Objectives The provision and utilisation of Meteorological Services needs to be enhanced to achieve the performance requirements of the future ATM system. Within WP11, the MET SWP is created to define and validate those needed Meteorological Service improvements and the way to integrate these MET services into the different processes and systems that will support the future ATM system. This needs to be done in all phases of trajectory management, from planning to execution. This SWP needs to ensure that the development of the MET infrastructure and services that support reliable MET Information Services data from multiple contributors can be integrated into the various User decision support systems. The general objectives of the MET SWP are to: 

Consolidate and ensure consistency of the operational and system requirements for MET (across all the SESAR Work Packages);



Develop prototypes ensuring the provision of the required MET Information Services to all ATM stakeholders;



Integrate MET into the SWIM ATM Network;



Contribute to the Validation of MET infrastructure and (information) services.

In particular, the MET Sub-Work Package activities should be conducted in adherence with the defined concept architecture by WPB and include: 

Consolidation of the Operational requirements for MET information from the Operational Work Packages (4, 5, 6, 7, and 11.1) across the whole scope of the SESAR Operations (Airport, ATC, Network, FOC/WOC, Aircraft);



Consolidation of the System requirements on MET Information Services integration for all System Work Packages (9, 10, 11.1, 12 and 13)on the SESAR programme;



Development of prototypes of MET infrastructure and services ensuring the provision of the required MET Information in support of MET Information Services to all ATM users;



Integration of MET infrastructure and services into the SWIM ATM Network and such in support of WP8 and WP14 ;



Contribution to the Validation of MET infrastructure and (information) services into the ATM system in under WP3 co-ordination.

The chosen structure provides a clear separation of concerns and associated roles and responsibilities. This is a structure fully in line with the Enterprise Architecture (EA) and Service Oriented Approach (SOA) adopted in the scope of the SESAR development phase and the deployment phase to follow. The figure below provides an illustration of the SESAR ATM System against the MET infrastructure & services, and their interactions through the SWIM network (the “4D Weather Data Cube” within similar initiatives outside SESAR):

SJU DoW WP11 v2.0

Page 48 of 72

ATFM Flow Management ATC En-Route, Approach

MET infrastructure & services 4D Weather Data Cube

Airports

Aircraft

SWIM network

FOC/WOC Airspace Users

Work Breakdown Structure SWP11.2 Meteorological services

MGT11.2.0 Co-ordination & Management

P11.2.1 Requirements for MET Information

Requirements Definition

P11.2.2 MET Information Systems Developemnt, Verfication & Validation

System Definition, Development & Pre-Operational Validation

SJU DoW WP11 v2.0

Page 49 of 72

It’s important to note that the following activities are not in the scope of SWP11.2: 

The activities required to integrate MET Information Services requirements in operational concept components both from an operational and systems perspective. This is primarily the responsibility of the respective Operational, SWIM and System projects in the SESAR Work Programme;



The development and prototyping of generic MET infrastructure & services (capabilities) that have no clear demonstrated link in supporting MET Information Services for ATM;



The development and prototyping of 'solutions that are tied to a single provider’ capability and restricts interoperability from a MET information delivery perspective in the deployment phase.

Deliverables Deliverables from the projects within SWP11.2, in reference with the E-OCVM development model, will be the results of the Phase V1, V2 and V3 for the development of the core sub-systems of the FOC/WOC. Main deliverables for each of the 3 Story Board Steps are the following: 

Definition of operational and performance requirements (reports)



Prototype development and verification (prototypes, reports)



Pre-Operational validation (validation exercises, reports).

The list of deliverables per project is further detailed in SWP11.2 projects’ descriptions. Risks Detailed information about risks identification, opportunities and mitigation are expected within the Final technical proposal. Work Flow and Dependencies Major external SWP11.2 dependencies with other WPs are depicted in this section.

SJU DoW WP11 v2.0

Page 50 of 72

Transversal Thread 

WP16 The direct dependency of SWP11.2 is two-fold. Firstly, WP16 will provide guidance on the Safety, Security, Environment, Human Performance and Business Case issues with respect to developing MET Systems and Infrastructures that are envisaged to be deployed in an ATM setting. The second tier of dependency is related to the tasks on Environmental sustainability in WP16, these projects could have a direct impact on the required MET Information (Services).



WP3 Validation Infrastructure will capture, analyse and monitor the validation infrastructure requirements versus the capabilities of the existing validation infrastructure, recommending and managing the necessary adaptations and developments. Depending on WP11 validation needs (both SWP11.1 and SWP11.2), WP3 will be fed with V&V needs identifying validation infrastructure requirements and will coordinate the availability of the validation platforms or tools. When elements are missing for satisfying a validation need, WP3 and the concerned SWP11.1 & 11.2 will agree on the most appropriate way to develop them.



WPB High Level Target Concept and Architecture Maintenance will maintain the related definitions and descriptions, increasing the maturity of the Target Concept & Architecture by taking into account work conducted in the context of SWP11.2. SWP11.2 has no direct responsibility for the integration of MET information in operational concept component and associated architecture. As such, the results of the associated activities in operational and system projects are the main driver for assessing and consolidating the Overall ATM Network

SJU DoW WP11 v2.0

Page 51 of 72

performance requirements by means of the Performance Framework trough the performance results from associated Work Packages' validation activities. With respect to the MET Infrastructure and Systems and interfaces with SWIM validation, it is the responsibility of SWP11.2 to provide the required feedback for WPB. 

WPC The interface with WPC is foreseen to be handled primarily through WPB. According to the validation results, SWP11.2 will continuously elaborate recommendations on changes to be brought to the Target Concept by WPB and the ATM Master Plan by WPC Master Plan Maintenance.

Operational Thread 

SWP 11.2 receives and provides necessary inputs from/to Operational Work Packages (WP4, 5, 6, 7 and SWP 11.1.) to define and validate a consistent set of WP11 MET operational requirements

System Thread 

SWP 11.2 receives and provides necessary inputs from/to System Work Packages (WP10, 12, 13 and SWP 11.1.) to define and validate a consistent set of WP11 MET system requirements

SWIM Thread 

Development of Information Services and the harmonisation of relevant SWIM aspects will be conducted with respect to the needs of all Users: o

WP8 Information Management, development of relevant MET Information Services based on operational requirements consolidated by P11.2.1, reflected in the ATM Shared Information Services Reference Model (ISRM) and ATM Information Reference Model (AIRM). The prime interaction between SWP11.2 and WP8 is with P08.01.06 and P08.03.03 and potentially with the projects P08.03.04 – P08.03.07.

WP14 SWIM, to harmonise the technical architecture and as such to develop SWIM compliant technical solutions.

SJU DoW WP11 v2.0

Page 52 of 72

P 11.2.0

Co-ordination and Management

P 11.2.0

Title: Co-ordination and Management

Necessary expertise For general expertise please refer to overall WP description, section “Generic typology of expertise”. Specific expertise:    

Significant experience in large Programme Management. Multi cultural management experience. Comprehensive understanding of SESAR Programme and of the ATM Network. Comprehensive understanding of procedures, processes and systems relevant to this Sub-Work Package both from an ATM and MET domain’ perspective.

Concept & Objectives The Project 11.2.0 “Co–ordination & Management”, by the MET Services SWP11.2 Leader, has the objective to carry out the management activities at SWP level. It monitors and controls the progress of the SWP and Projects activities for ensuring the achievement of the objectives and for delivering on time, with the required quality and making the best possible use of available resources by defining and applying relevant project management practices. It organises the review process leading to the acceptance in the view of delivering the Deliverable to EUROCONTROL/SJU. It coordinates the work of the different partners involved in the SWP. It reports progress, issues to EUROCONTROL/SJU and proposes mitigation actions as necessary. It ensures application of common SESAR methodologies and tools across the WP and provides assistance to that aim to all SWP11.2 projects. It ensures the interface with WP B, WP C to propose update to the concept of operation or architecture and to the Master Plan and the work program. It also ensures interfaces with any other appropriate Work Packages and SWP11.1 to ensure consistency across WPs. Description of Work The Sub-Work Package 11.2 shall comply with the Programme Management Plan (PMP) for the SESAR Programme. WP11 shall be integrated within the SESAR Programme and shall apply the same methodologies. SJU engineering methodologies are the procedures, processes and tools that will be uniformly applied to ensure an overall consistency and coherence throughout the SESAR Work Programme. Each WP has to comply with the engineering methodologies defined within the SEMP (see reference documents).

SJU DoW WP11 v2.0

Page 53 of 72

The SJU will ensure consistency of the activities within and between the Operational Work Packages (WP), the SWIM WP, and the System WP, and consolidate their results throughout the development lifecycle at the program level. In implementing the methodologies, SWP11.2 has to ensure its representation at the required level of expertise in working arrangements as defined by the SJU. Generic Work Package, SWP, and Project Leader role and responsibilities are described within the SESAR PMP (see referenced documents list). Without affecting the Project Leader roles the SWP11.2 Leader role differs from the SESAR PMP in the sense that it combines both Work Package and SWP Leader roles. Deliverables The following deliverables will be provided: 

D11.2.0-1: Management Initiation Report (within 60 calendar days after awarding of the Contract)



D11.2.0-2: Project Management Plan (including detailed Work Plan)



D11.2.0-3: Risk Management Plan



D11.2.0-4: Quarterly Progress Reports.

Risks The procedures and rules guiding risks identification, management and mitigation will be gathered in the SWP11.2 Risk Management Plan. The Risk Management Plan shall be in line with the risk management procedures described within the SESAR PMP. A draft version of it will be provided as part of the final offer and will be updated during the Initiation Phase.

SJU DoW WP11 v2.0

Page 54 of 72

P 11.2.1

Requirements for MET Information

P 11.2.1

Title: Requirements for MET Information

Necessary expertise For general expertise please refer to overall WP11 description. Specific expertise:           

Good knowledge of Operational Concepts developments, and in particular of the SESAR Concept of Operations Document (CONOPS). Comprehensive understanding of the ATM Network (actors, operations, architecture and business drivers). Broad experience in operational concept analysis. Good knowledge of the Network Operations, En-Route, TMA, Airport, and Airspace Users operational context. Good knowledge of procedures, processes and systems relevant to this Work Package. Meteorology (more specifically Aviation Meteorology including associated areas of expertise ATM Operations and Systems Ground and Space MET sensing and observation systems Knowledge of the environment and physics of the atmosphere Numerical assimilation and forecasting techniques International regulations and standards in the MET domain



Methodologies of system/software engineering (system definition, enterprise architecture design and development).



Organisation and management principles, structures & processes.



Business process design & modelling.

Concept & Objectives Whilst it is clearly recognised that weather is a significant factor to consider in air transport today and weather and knowledge on the state of the atmosphere will become even more important in time-based, trajectory based and performance based operations, it remains to be non trivial to develop operational concepts that could benefit from using weather information; and as such contribute to an overall performance improvement of the ATM System. Consequently, it is seen necessary to raise the awareness and understanding of the contributors to the Operational and System Work Packages with respect to the current and foreseen capabilities of MET service providers. Not only from a MET phenomena perspective, such as convective weather, low visibility, etc., but also from the perspective how-to potentially handle non deterministic information (intrinsic to meteorology) in an ATM environment and how real-time weather monitoring applications could improve situational awareness and as such improve performance and safety. Based on the raised awareness, a dialogue with the Operational Work Packages’ contributors needs to be established to explore conjointly the potential of integrating MET information in the Operational Work Packages’ contributions to operational ATM concept component. Operational Work Packages are responsible for their contributions to the different ATM Service Levels and

SJU DoW WP11 v2.0

Page 55 of 72

associated Story Board Steps. The decision to include MET information in such a concept and the exploration of associated MET expertise to do so does not change these roles and the responsibilities. Likewise, the start-up of new or alteration of existing projects to include MET information or processes to accommodate the use of MET information remains in the scope of the respective Operational Work Packages’ projects. The role of project P11.2.1 is in the support the Operational Packages in the development of their contribution to an ATM operational concept component with respect to the integration of MET information. A key component in P11.2.1 is to assist in the development of requirements for MET Information Services by Operational Work Packages’ projects. However, the responsibility to formally list requirements remains with the respective projects of the Operational Work Packages. The P11.2.1 leadership will list and report on potential improvements seen from the P11.2.1 perspective but not acknowledged by a respective Operational Work Package. Together with already known requirements for MET Information Services, identified in existing DoWs, PIRs or project deliverables, the newly derived requirements for MET Information Services need to be consolidated and integrated into an Operational Analysis Document. The Operational Analysis Document will be used by WPB, WP8 and other SWP11.2 projects to respectively keep the overarching system architecture consistent, to support the development of appropriate MET Information Services and to develop the MET service provision capability to support the required (MET) Information Service. The development of operational requirements for MET Information Services will potentially lead to new or changed operational concept components and as such new or revised requirements for the supporting system of systems. The role of project P11.2.1 is also to support to System Packages in the development of the contribution of the System Packages to ATM system components with respect to the integration of MET information. Together with the already known system requirements for the integration of MET Information Services, identified in existing DoWs, PIRs or project deliverables, the newly derived system requirements for the integration of MET Information Services need to be consolidated and integrated into a System Analysis Document for MET Information Services and the integration of these services in systems. The System Analysis Document will be used by WPB, WP14 and P11.2.2 to respectively keep the overarching system architecture consistent, to support the development of appropriate system integration of (MET) Information Services and to develop the systems required to support defined (MET) Information Service. The responsibility for system developments and Information Service integration from a system’ perspective remains with the respective projects of the System Work Packages. Furthermore, the project liaises between already identified MET system capabilities developments (initiated or dormant) for meteorology in the SESAR programme and P11.2 as a whole. This ties the developments on MET sensing capabilities for the TMA and Airport environment and the aircraft being utilised as a ‘MET sensor’ with the overall context provided by SWP11.2 in developing the best fit for purpose MET capability for the MET Information Services required to be integrated in operational ATM decision making processes. Consequently, the main objectives of this project are to: 

Provide a first order of priorities for developing required MET capabilities and as such

SJU DoW WP11 v2.0

Page 56 of 72

the associated MET Information System(s); 

Perform an analysis of the MET interfaces and functions that SESAR Programme will require from WPB and the following Operational Work Packages: o

WP4

WP5

WP6

WP7

WP11.1;



Support the definition of operational, performance & safety requirements and interoperability specifications by the Operational Work Packages with respect to required MET Information Services;



Consolidate the MET Information Services requirements including coordination with already performed activities within the Programme;



Support the definition of system, performance & safety requirements and interoperability specifications by the System Work Packages with respect to the required MET Information Services and the system integration of these services;



Consolidate the system integration requirements with respect to MET Information Services including coordination with activities already performed within the Programme;



Liaise between the existing projects within the System Work Packages on ‘MET’ sensor capabilities in the widest sense and SWP11.2.

In order to achieve this, it will be necessary to: 1. Raise awareness with respect to current and foreseen MET services capabilities that potentially could improve the overall performance – including safety - of the ATM System;

2. Establish a co-operative dialogue between MET and ATM and as such between the Operational Work Package leads and contributors and P 11.2.1.

Description of Work

P11.2.1 Requirements for MET Information

Utilisation of MET Information

Operational Requirements Definition for MET Info Services

System Integration – Definition of MET Info Services

Requirements Definition

The need for MET information supporting the SESAR concept of operations across the multiple ATM Service Levels will be extensively explored. The following main tasks have been identified: Task 11.2.1.1 Utilisation of MET Information: raising awareness

SJU DoW WP11 v2.0

Page 57 of 72



Initial prioritisation of required MET capabilities and associated MET Information services The (sub-) task will provide an initial mapping and prioritisation of required MET information needs versus needed MET Information services and the required MET capability. This will provide an initial focus for the formal requirements gathering activities and provides an initial prioritisation on the high level themes for the development of meteorological capabilities in a P11.2.2 context before executing P11.2.2. The activity will be based on raising the awareness with respect to current and foreseen MET services capabilities that potentially could improve the overall performance –including safety- of the ATM System and the co-operative dialogue between MET and ATM and as such between the Operational and System Work Package leads and contributors and P11.2.1. It is recognised that the outcome of the initial prioritisation could impact the three themes currently selected and listed below as important to raise awareness. One of the three topics for the ‘raising awareness’ themes could, as a consequence, be replaced by a higher demanding topic as an outcome of the initial prioritisation after approval by the Programme leadership.



Convective Weather information for ATM The focus of the (sub-) task is on facilitating the process of making available operational requirements for convective weather information by operational projects by introducing, promoting and educating about the current and foreseen MET service provider capabilities with respect to convective weather. Over the last years, a significant rise in en-route delays for parts of the core airspace of Europe have been observed, where convective weather appears to be the main contributor. Whilst the extent of convective phenomena and its impact on air transport is not comparable with the US, climate change trends and today’s experiences over Europe indicate that a better use of convective weather information could improve ATM performance significantly over summer time. The task should deliver insights in the sensitivity of the ATM System for convective weather from a MET service providers’ perspective and will be used in subsequent tasks on stimulating debate in an Operational Concept environment with the end-goal to develop the consolidated requirements for the (MET) Information Services needed.



Use of Probability Forecasts in ATM The focus of the (sub-)task is in contributing to the awareness about the ‘nature’ of MET information, especially the intrinsic uncertainty associated with MET information, how operational concepts could handle better the uncertainty and how this needs to be reflected in requirements for MET Information Services. Important to address is also the relationship between uncertainties in general, risk (or cost/lost) distributions and some MET phenomena that can only be classified as an extreme but were we are extremely interested in from an ATM perspective. The outcome will be used in subsequent tasks on stimulating debate in an Operational Concept environment with the end-goal to develop the consolidated requirements for the (MET) Information Services needed.



Real-Time weather monitoring in ATM The focus of the (sub-)task is to demonstrate the capabilities with respect to real-time monitoring (and associated short-term forecasting) of hazardous weather, the potential utilisation in an ATM environment and providing insights on how the use of these applications could improve situational awareness for all stakeholders involved and as such contribute to the performance and safety. The outcome will be used in subsequent tasks on stimulating debate in an Operational Concept environment with the end-goal to develop the consolidated requirements for the (MET) Information Services needed.

Task 11.2.1.2 Operational Requirement Definition for MET Information Services

SJU DoW WP11 v2.0

Page 58 of 72



Logical Architecture Consolidation The (sub-) task will deliver consolidated requirements at the level of Logical Architecture’ Operational Domains per Step (1 to 3). Providing an oversight of the Information Services requirements for: o

MET Information for En Route Operations

MET Information for TMA Operations

MET Information for Airport Operations

MET Information for Network Operations

MET Information for Flight and Wing Operations Centres

It includes: o

Review Operational Work Packages SESAR Operational Work Packages (WP 4, 5, 6, 7 and 11.1) will be reviewed in depth in order to identify the nature of MET information which would enable (or improve) any of SESAR operational concept or procedure. A cooperative dialogue between the project and the Operational Work Package contributors will be conducted in order to avoid a pure top-down or pure bottomup approach, but foster a real exchange between the two communities. This includes potential requirements as such, but also clears indications for the priorities to be applied in the rest of the project and associated (S)WPs in the Programme. Based on an initial analysis of the actual impact of weather but also on the state of ‘readiness’ to integrate weather in a considered operational concept component. The right of initiative for the set-up of the cooperative dialogue is with P11.2.1. This is envisaged to be meetings between the project contributors and the identified Operational Work Packages’ leadership. The work packages leadership are responsible for the communication within their package, the selection of the key contributors to these meetings and follow-up activities;

Airspace Users Requirements Expectations from the stakeholders will be refined through a wider consultation of Airspace Users (Airlines, Business/General Aviation, State Aviation and Military) through the framework arrangement between SJU and Airspace Users. P11.2.1 has the right of initiative to request SJU for meetings or other forms of support in consolidating Airspace Users requirements for MET Information Services; Special emphasis should be put on identifying the MET information needs which will allow for a) the accurate management of the Business Trajectory, at any stage of its lifecycle, from the flight planning to execution process (e.g. prediction of waypoints and arrival time, determination of the best trade-off for a route being simultaneously safe, environment friendly, and economically efficient,…) and b) an efficient collaborative decision making process, especially at airports. This will relate to parameters impacting on e.g. AMAN / DMAN procedures, taxi routing, etc.

Existing standards Identified needs will be put in perspective with the current and foreseen status of ICAO and WMO and other relevant international and European standards and guidelines, regarding the provision and use of MET information to aviation; gaps

SJU DoW WP11 v2.0

Page 59 of 72

will be identified and potential resolutions proposed. Task 11.2.1.3 System (Integration) Requirements - Definition for MET Information Services 

Logical Architecture Consolidation The (sub-) task will deliver consolidated requirements at the level of Logical Architecture’ Operational Domains per ATM Service Level. Providing an oversight of the system requirements for the Information Services and services integration of: o

MET Information for En Route Operations

MET Information for TMA Operations

MET Information for Airport Operations

MET Information for Network Operations

MET Information for Flight and Wing Operations Centres

It includes: o

Review System Work Packages SESAR System Work Packages (WP 9, 10, 12, 13 and 15) will be reviewed in depth in order to identify the nature of how MET Information Services could be integrated in systems that answer the Operational needs of the Programme described by the Operational Work packages and delivered by the System Work Packages. A cooperative dialogue between the project and the System Work Package contributors will be conducted in order to avoid a pure top-down or pure bottom-up approach, but foster a real exchange between the two communities;

Airspace Users Requirements Expectations from the stakeholders will be refined through a wider consultation of Airspace Users (Airlines, Business/General Aviation, State Aviation and Military …) through the framework arrangement between SJU and Airspace Users; Special emphasis should be put on identifying the integration of MET Information Services in the systems which will allow for a) the accurate management of the Business Trajectory, at any stage of its lifecycle, from the flight planning to execution process (e.g. prediction of waypoints and arrival time, determination of the best trade-off for a route being simultaneously safe, environment friendly, and economically efficient,…) and b) an efficient collaborative decision making process, especially at airports. This will relate especially to parameters impacting on e.g. AMAN / DMAN procedures, taxi routing, etc.

Existing standards

Identified needs will be put in perspective with the current and foreseen status of ICAO and WMO and other relevant international or European standards and guidelines, regarding the provision and use of MET information to aviation; gaps will be identified and potential resolutions proposed. This activity needs to be aligned with P08.01.06. Deliverables

SJU DoW WP11 v2.0

Page 60 of 72

The deliverables related to task 11.2.1.1 are in the form of reports and by their nature should be considered as V1 Initial Business Case Reports according to the E-OCVM development model and will be supporting the three identified (Story Board) Steps. The deliverables include at least: 

D11.2.1-1: Report containing the MET service provision’ perspective on the potential impact of convective weather on ATM performance and how improved information could improve the overall performance. The intended audience for the report is in principal the contributors to all the operational work packages inclusive of the subpackages and projects.



D11.2.1-2: Report containing the MET service provision’ perspective on the potential use of uncertainty/probability with respect to MET information for ATM. The intended audience for the report is in principal the contributors to all the operational work packages inclusive of the sub-packages and projects.



D11.2.1-3: Report containing the MET service provision’ perspective on the potential use of real-time weather monitoring applications, the foreseen impact on ATM decision making and how these applications will improve ATM performance and safety. The intended audience for the report is in principal the contributors to all the operational work packages inclusive of the sub-packages and projects.



D11.2.1-4: Report on MET Capability development prioritisation providing an initial mapping and prioritisation of required MET information needs versus needed MET Information services and the required MET capability. The intended audience for the report is in principal SESAR Programme management and P11.2 management and contributors.

The deliverables related to task 11.2.1.2 are in the form of operational and performance requirements reports and reports that reflect the outcomes of the coordination activities with the Operational Work packages, sub-package or project. Per Step (1 to 3) there will be at least the delivery of a V2 Preliminary Operational Requirements document and a V3 Final Operational Requirements Document (according E-OCVM) per Logical Architecture Operational Domains (Route Operations, TMA Operations, Airport Operations, Network Operations and Flight and Wing Operations Centres). The foreseen structure of deliverables is: 

D11.2.1-5: [Step 1 Preliminary Operational and Performance Requirements document and high level outlook on Step 2 and 3]



D11.2.1-6: [Step 1 Final Operational and Performance Requirements document and high level outlook on Step 2 and 3]



D11.2.1-7: [Step 2, Preliminary Operational and Performance Requirements document and high level outlook on Step 3]



D11.2.1-8: [Step 2, Final Operational and Performance Requirements document and high level outlook on Step 3]



D11.2.1-9: [Step 3, Preliminary Operational and Performance Requirements document]



D11.2.1-10: [Step 3, Final Operational and Performance Requirements document].

The deliverables related to task 11.2.1.3 are in the form of system requirements reports and reports that reflect the outcomes of the coordination activities with the System Work packages, sub-package or project. Per Step (1 to 3) level there will be at least the delivery of a V2 Preliminary Technical Specification document and a V3 Final Technical Specification document (according E-OCVM) per Logical Architecture Operational Domains. The foreseen structure of deliverables is:

SJU DoW WP11 v2.0

Page 61 of 72



D11.2.1-11: [Step 1, Preliminary System Specifications document]



D11.2.1-12: [Step 1, Final System Specifications document]



D11.2.1-13: [Step 2, Preliminary System Specifications document]



D11.2.1-14: [Step 2, Final System Specifications document]



D11.2.1-15: [Step 3, Preliminary System Specifications document]



D11.2.1-16: [Step 3, Final System Specifications document]

Provide the SESAR Programme with general MET-ATM expertise; Provide support to consolidating Operational and System requirements; Provide support to the SESAR Programme regulatory (roadmap) activities with respect to MET service provision and in close coordination with other relevant work packages such as WP8, this includes the provision of the appropriate liaison for the SESAR Programme with: o ICAO on all aeronautical meteorology related aspects o World Meteorological Organisation (WMO) and other intergovernmental organisations such as ECMWF and EUMETSAT on the non-technical MET capability aspects of service provision, and;



US NextGen Programme (FAA, NOAA, etc.) on the non-technical MET capability aspects of service provision.

Final technical proposals are expected to provide a first view of when and how this proposed contribution would best fist their plan. Final agreement and planning will be achieved during the initiation phase. These activities will be performed by EUROCONTROL staff under the control of the selected Contractor, and the effort would not exceed the average value of ~0,4 FTE per year, for the whole duration of the project, spread over the following expertise: 

Aeronautical Information Management (AIM-MET).

SJU DoW WP11 v2.0

Page 62 of 72

Airspace User Task Requirements, Deliverables, Deadlines and the respective Airspace User Categories, Expertise type and associated Effort. On an annual basis these shall be agreed between the SJU and the Project. Any execution of these activities will be under the control of the SJU, but co-ordinated by the Project. The estimated effort required by the Project should be identified during the call for tender and refined with the SJU during the Initiation Phase. Risks Risk Management and detailed risks identification, opportunities and mitigation are expected to be taken into account and developed within the final proposal. Management See P11.2.0 â&#x20AC;&#x153;Co-ordination and Managementâ&#x20AC;? for additional information.

SJU DoW WP11 v2.0

Page 63 of 72

P 11.2.2

MET Information Systems Development, Verification & Validation

P 11.2.2

Title: MET Information Systems Development, Verification & Validation

Necessary expertise For general expertise please refer to overall WP11 description. Specific expertise: 

Methodologies of system/software architecture design and development).



Organisation and management principles, structures & processes.



Business process design & modelling.



Verification and validation expertise



Meteorology (more specifically Aviation Meteorology)



ATM Operations and Systems



Ground and Space MET sensing and observation systems



Knowledge of the environment and physics of the atmosphere



Numerical assimilation and forecasting techniques



International regulations and standards in the MET domain.

engineering

(system

definition,

enterprise

Concept & Objectives Whilst P11.2.1 supports the development of the required MET Information Services to be integrated in operational concept components and associated systems, the information/data required for these MET Information Services needs a corresponding capability from a MET services provider’s perspective. This needed MET capability is inclusive of the appropriate MET infrastructure and services and including the potentially required MET application services and data store/management aspects. This enables the required MET Information Services and its connectivity with the ATM System Wide Information Management (SWIM) environment. This notional combination of MET infrastructure, (application) services and data management aspects like (virtual) data stores is commonly referred to as the ‘4D-Weather Cube’.1

SWIM Infrastructure connectivity and Information Management Underpinning the entire ATM system, and essential to its efficient operation, it is a SWIM 1

Note: The 4D-Weather Cube is a notion used in the US NextGen context and picked up by the aeronautical meteorology domains within ICAO and the World Meteorological Organization (WMO) to reflect the system of systems and associated infrastructure, applications and information services that collectively make available meteorological information for aeronautical applications. The exact scope and definition of the 4D Weather Cube is not set and will probably have a different meaning in a different architectural and geo-political context. Thus the 4D WX Cube for Europe is probably not identical to the 4D WX Cube for the US. However, for the moment it is the only notional description that captures the fact that the solutions to be developed need to be open, transparent, flexible interoperable and not tied to a single provider’ capability and the information made available should really support the 4 dimensions of the flight/business trajectory, other operational ATM concepts and support activities.

SJU DoW WP11 v2.0

Page 64 of 72

environment that includes the aircraft and ground facilities in order to provide an enabler to systems’ interconnection in line with SESAR concepts. SWIM is not in itself an ATM end-user application: it is an enabler of end-user applications that is needed in the ATM world. Thus, SWIM concept will make the information available to the end-user applications and will not constrain the implementation of end-user applications. SWIM will allow the exchange of data and ATM services across the whole European ATM System, integrating both Air-Ground (to manage the participation of the aircraft in SWIM and Ground-Ground data and ATM services exchange. With respect to meteorology, this will be instantiated by making available MET Information Services that can be accessed over the SWIM network by the relevant SWIM actors. These MET Information Services will be used by the appropriate operational services and supporting application (services) and systems (infrastructure). The MET Information Services will require a supporting MET Infrastructure and Services (‘4D WX Cube’) to deliver the data for the MET Information Services. As such, the 4D WX Cube is one of the ‘systems’ to be connected to SWIM. Key to the successful development of MET Information Services, which are in the prerogative of WP8 (SWP8.3), is the appropriate level of interfacing and integration between the ATM Operational and System requirements, the required MET infrastructure and services and the connecting concept of SWIM. MET Capability, Infrastructure and Systems P11.2.2 supports the development of requirements for MET capabilities that will deliver the MET data that can be turned into the required MET Information Services by the appropriate projects in the Programme, i.e WP8. The project includes the prototype development and validation of several MET infrastructural and service concept elements in support of the MET Information Services required for ATM. Furthermore, it includes the previously discussed connectivity between these developed components and the SWIM infrastructure and its adherence to the information management principles developed by the Programme. The required MET capability and associated infrastructure and systems will be prototyped and verified. As such, it will provide evidence, or otherwise, that these MET capabilities and the supporting infrastructure and services contribute to the safe and efficient delivery of the required MET Information Services in support of the SESAR concept elements. Furthermore, evidence will be provided that the MET infrastructure and services solutions developed (the ‘4D Weather Cube’) are truly interoperable and will not restrict (future) providers and user of information in using and accessing the infrastructure, services and contained information. The associated deliverable(s) will be a prototype(s) of a ‘system of systems’ capable to deliver the required meteorological information services based on P11.2.1 requirements. The prototype(s) could consist of specific development for aviation of a numerical weather prediction capability, to make the data from this capability available and to translate the information in an information service available on the SWIM network. As such, it could be a joining of existing and new capabilities and associated new and existing systems. Support to Pre-Operational Validation P11.2.2 supports the demonstration that the defined requirements for MET information, translated into developed MET Information services can be integrated within operational improvements of Airspace Users, Network, En-Route, TMA and Airport operating context. These MET Information Services are made available by using the SWIM network,

SJU DoW WP11 v2.0

Page 65 of 72

interconnected with an underpinning MET infrastructure and its services and as such making available the required MET capability. To demonstrate that this system will function in a pre-operational environment in conjunction with the operational concept component prototype and the required MET Information Service is one of the main objectives of the project. The ‘role’ is to support pre-operational validation as a whole, the responsibility however lies only at the level of the MET capability and underpinning infrastructure and services and the interfaces with SWIM whilst the responsibility of the validation of MET Information Integration solutions and required Information Services is with the Operational, System and (SW)IM work packages concerned. Consequently, the main objectives of this project are to: 

Address the coordination between P8.3 (and supporting packages in WP8) responsible for developing the appropriate (MET) Information Services and P11.2.1 with respect to translating the operational requirements for MET information in a MET Information Service(s) description;



Identify existing and quickly emerging generic MET capabilities that could potentially be utilised by ATM and integrated in associated MET Information (Services) requirement of deliverable D11.2.1-4 (11.2.1);



Define and consolidate the operational, system, performance & safety requirements and interoperability specifications for the MET infrastructure and services; Develop a consolidated MET infrastructure and services prototype, the “4D Weather Cube”, with priority on Quick Wins (e.g. Short term benefits for Initial 4D Trajectory Management and Airport CDM) and the integration with SWIM. This needs to address the interfacing and integration of the MET infrastructure and services system prototype with the SWIM network from a technical infrastructural perspective and from an ATM information management perspective and in close cooperation with the relevant WP8 projects. The latter includes issues such as data security, access, governance, etc.;



 

Develop successive versions of the ‘4D Weather Cube’ prototype to provide incremental coverage of the final targeted “4D Weather Cube” to meet successive Steps;

Develop underpinning MET capabilities as part of the overall required MET infrastructure and services that support the required MET Information Services defined (P11.2.1 in close cooperation with the relevant WP8 projects); Coordination with work already performed including the infrastructure and services development initiatives by existing Work Packages that could support the 11.2.2 activities; Elaborate the Validation Strategy for the WP 11.2 components in line with the overall validation strategy defined by the SJU. Contribute to the operational validation in close coordination with Operational Work Packages and SWIM Work Packages, including: o Ensure that the various validation activities e.g. operational feasibility assessment, safety assessment, performance assessment and CBA are planned and coordinated appropriately in the validation lifecycle steps. o Plan and coordinate validation exercises. o Set up a trade off process for identifying the possible changes on the concept and for adjusting the scope and objectives of validation.

SJU DoW WP11 v2.0

Page 66 of 72

Description of Work

P11.2.2 MET Information Systems Developemnt, Verfication & Validation

Prototype Specification, Development & Verification

Integration with SWIM Technical Infrastructure

Support to Pre-Operational Validation

System Definition, Development & Pre-Operational Validation

To address the development of MET capabilities that will meet the foreseen requirements by P11.2.1, main tasks have been identified based on the following core principles to: 

Explore existing and emerging generic MET capabilities that could potentially be utilised by ATM in the required MET Information Services to improve ATM decision-making;



Explore the most cost efficient separation of MET Information Services and potential MET application services in function of ATM capability level and associated Story Board Step;



Focus on the development of the required MET infrastructure and services required for specified MET Information Services that serve the ATM Operational, ATM System and Aviation Stakeholder needs;



Consolidate and coordinate the MET infrastructure and services development with initiatives by existing Work Packages that could support the 11.2.2 activities;



Design and prototype solutions that are in principal interoperable from the MET information delivery perspective and as such not tied to a single provider’ capability.

Identified Main tasks are: Task 11.2.2.1 Prototype Specification, Development & Verification 

MET Infrastructure and services definition (‘4D WX Cube’) The needed infrastructure and services to meet required MET Information Services will be defined taking into account considerations with respect to the required Information Services and the MET capabilities providing the data. The definition should appreciate the generic principles of Service Orientation and the notion of Information and Application Services and accepting the idea that data could reside within many systems and repositories and what will be required is standardised access to the data. By enabling applications (services) to access the data via (open) standards, service requestors can access the data regardless of provider or system. An important consideration will be to define the most efficient way to distinguish between Information Services that solely provide access to core MET information and application services that use Information Services to integrate and fuse the information of different nature and to make it fit for a user purpose application (service). When a MET application service is used by many users it could be efficient to expose this service as a common service and not restrict it for one specific use case.

SJU DoW WP11 v2.0

Page 67 of 72



Consolidated MET capabilities definition A grouping of the required MET Information (Services) requirements (P11.2.1) according to Logical Architecture Operational Domains is valid from a Programme Perspective. However, applying this structure on the corresponding required MET capabilities definition activity could include the intrinsic risk of duplication of activities. Consolidation of the defined MET capabilities is therefore required to align the required capability and therefore the defined infrastructure, services. The initial consolidation proposed is based on two distinct different ‘user behaviours’ and as such in two subtasks per Step (1 to 3): o

MET capabilities for immediate decision making (hazard): Based on the requirements for the Information (Services) set by P11.2.1, corresponding MET capability needs to be defined. Capabilities required for the ATM Service shall focus on data for hazardous weather Information Services. This requires data and associated services updated rapidly, focused on shortterm forecasting capabilities and tailored to trigger immediate response of stakeholders concerned. Examples of the phenomena/parameters expected to be considered are: convective weather and associated phenomena such as lightning, turbulence, downburst, etc., in-flight icing conditions and strong (surface) winds, low-level wind shear.

MET capabilities for near term decision making and planning (refinement, adherence and modification of the trajectory): Based on the requirements for the Information (Services) set by P11.2.1, corresponding MET capability needs to be defined. Capabilities required for the ATM Service shall focus on data for weather Information Services that facilitate the refinement of, adherence to and modification of the flight trajectory to contribute to the overall performance. This requires data and associated services that not necessarily translate into having high update cycles but more in having a right balance between the confidence level of the data, the update frequency and the impact. The focus is on generic forecasting capabilities and tailored to ensure situational awareness and the ingestion of information in decision support systems to support e.g. CDM processes. Examples of the phenomena/parameters expected to be considered are: wind, temperature and other relevant parameters for green approaches/CDA, convective weather and associated phenomena such as lightning, turbulence, downburst, etc., weather for wake-vortex separation, winter conditions, low visibility and cloud conditions. With respect to Demand and Capacity Balancing services, data for weather Information Services that facilitate all stages of planning and associated demand and capacity balancing processes will need to be the focus of this development activity. The decision horizon could be distinctively different than for Traffic Synchronisation and Trajectory Conformance Monitoring services and as such the forecasting capabilities and characteristics could differ, capabilities such as seasonal forecasting could become important. Examples of the phenomena/parameters expected to be considered are: wind, temperature, prevailing winter conditions and prevailing low visibility and cloud conditions.



Utilising new sensors for MET capabilities In support of the previous activity, the definition of required MET capabilities, it is extremely valuable to review the potential impact of using sensors and/or other means of observation currently not utilised in the specific aeronautical application of meteorology, completely new or are under development by other projects in the

SJU DoW WP11 v2.0

Page 68 of 72

Programme. This also includes using the aircraft as a sensor and the downlink of relevant information improving or in addition to the existing WMO AMDAR Programme. As such, the task is the interface between SWP11.2 and the respective projects working or envisaged to work on MET sensor developments, e.g. P15.04.09. The review will identify the potential improvement of MET capabilities by the enhanced exploitation of (remote) sensing techniques. It should provide a qualitative analysis of the improvement linked to the foreseen capabilities by the previous activity to justify future deployment or utilisation of these (remote) sensing techniques. 

MET infrastructure and services prototype development and verification The task comprises of the development of MET infrastructure and services, supporting applications and services, where and when relevant their integration into a single test platform, and integration with the SWIM environment. The following main activities with respect to prototype development, connectivity with the SWIM environment and verifications have been identified: o Develop and provide the required ‘interfaces’ with WP8 and WP14 on MET Information Services, Information Management functions in general and underpinning information models, more specific:  Liaise between the project and the relevant (SW)IM projects on the translation between MET Information Services requirement gathered in P11.2.1, the development of the Information Service itself in WP8 and the required data as an output of the developed MET capability o Develop the MET infrastructure and services prototype o Develop the required MET core functionalities and integrate them when relevant into a single test platform prototype, the ‘4D Weather Cube’ prototype; o Perform ‘4D Weather Cube’ system verification; o Consolidate results into a coherent integrated verification report (including recommendations regarding the MET infrastructure and services architecture); o Provide verification results and recommendations regarding changes on the architecture and system requirements for further improvement of the related deliverables.

Task 11.2.2.2 Integration with SWIM Technical Infrastructure  Integration with SWIM This activity comprises the integration of the MET platform with the SWIM environment, and as such demonstrating the core MET components to make available the MET Information Services required by the Operational and System Work Packages. The following main activities with respect to the prototype connectivity with the SWIM environment and verifications have been identified: o Develop the MET infrastructure and services prototype’ interfaces with the SWIM infrastructure o Perform ‘4D Weather Cube’ full system verification; o Proceed to the verification of the ’4D WX Cube’ integrated with the SWIM network o Consolidate results into a coherent integrated verification report (including recommendations regarding the MET infrastructure and services architecture); o Provide verification results and recommendations regarding changes on the architecture and system requirements for further improvement of the related deliverables. Task 11.2.2.3 Support to Pre-Operational Validation This task will cover the following activities: 

Application of the Overall Validation Strategy by:

SJU DoW WP11 v2.0

Page 69 of 72

Production of the initial baseline documents regarding the WP Validation Strategy and prepare the validation plans for the operational and system activities (E-OCVM step 1).

o 

Identification of validation requirements to match performance targets.



Planning and execution of live trials validations based on pre-industrial prototype(s) developed by the system projects (within System Work Packages).



Performance and safety assessments incl. Cost-Benefit data supporting CB Analysis



Interoperability assessment



Participation to pre-operational validation exercises across all other SESAR Work Packages according to the test plan established in the Validation Strategy.



Production of detailed validation reports.

Deliverables

SJU DoW WP11 v2.0

Page 70 of 72

The following deliverables will be produced iteratively for each Step (1 to 3): 

D11.2.2-1: Step 1 System and Architecture Requirements for Prototype (quick wins?)



D11.2.2-2: Step 1 System-to-SWIM interfaces specifications (quick wins?)



D11.2.2-3: Step 1 verified prototype available for operational validation (quick wins?)



D11.2.2-4: Step 2 System and Architecture Requirements for Prototype



D11.2.2-5: Step 2 System-to-SWIM interfaces specifications



D11.2.2-6: Step 2 verified prototype available for operational validation



D11.2.2-7: Step 3 System and Architecture Requirements for Prototype



D11.2.2-8: Step 3 System-to-SWIM interfaces specifications



D11.2.2-9: Step 3 verified prototype available for operational validation



D11.2.2-10: Step 1 Validation o Validation Plan for SWP11.2 MET Services.



Execution of the validation plan (large scale, shadow mode, live trials validations, etc.) in co-ordination with WP3

Validation Reports for stand-alone validation (including input to Deployment Scenarios and consolidated input to TA Cases)

Validation Reports for Integrated validation across WPs (including input to Deployment Scenarios and consolidated input to TA Cases)

D11.2.2-11: Step 2 Validation o Validation Plan for SWP11.2 MET Services. o

Execution of the validation plan (large scale, shadow mode, live trials validations, etc.) in co-ordination with WP3

Validation Reports for stand-alone validation (including input to Deployment Scenarios and consolidated input to TA Cases)

Validation Reports for Integrated validation across WPs (including input to Deployment Scenarios and consolidated input to TA Cases)

D11.2.2-12: Step 3 Validation o Validation Plan for SWP11.2 MET Services. o

Execution of the validation plan (large scale, shadow mode, live trials validations, etc.) in co-ordination with WP3

Validation Reports for stand-alone validation (including input to Deployment Scenarios and consolidated input to TA Cases)

Validation Reports for Integrated validation across WPs (including input to Deployment Scenarios and consolidated input to TA Cases).

The list of identified deliverables will be subject to refinement during the Initiation Phase for final agreement. EUROCONTROL/SJU Input

SJU DoW WP11 v2.0

Page 71 of 72

EUROCONTROL Furnished Input EUROCONTROL proposes to support the execution of this project by providing contribution in areas/tasks where EUROCONTROL believe the expertise brought will be the most useful to the project and adequate with EUROCONTROL resource availability. The activities identified and proposed to perform are the following :   

Provide the SESAR Programme with general MET-ATM expertise; Providing support to MET Information System(s) Development & Verification; Providing support to SESAR regulatory (roadmap) activities with respect to MET service provision and in close coordination with other relevant work packages such as WP8, this includes the provision of the appropriate liaison for the SESAR Programme with: o ICAO on all aeronautical meteorology related aspects o World Meteorological Organisation (WMO) and other intergovernmental organisations such as ECMWF and EUMETSAT on the non-technical MET capability aspects of service provision, and; o US NextGen Programme (FAA, NOAA, etc.) on the non-technical MET capability aspects of service provision.

PQIPs final technical proposals are expected to provide a first view of when and how this proposed contribution would best fist their plan. These activities will be performed by EUROCONTROL staff under the control of the selected Contractor, and the effort would not exceed the average value of ~0,3 FTE per year, for the whole duration of the project, spread over the following expertise: 

Aeronautical Information Management (AIM-MET).

Final agreement and planning will be achieved between EUROCONTROL and the Contractor during the Initiation Phase. SJU Furnished Input The SJU proposes to support the execution of this project where necessary by providing contributions of civil Airspace User expertise in areas/tasks where the SJU believe the expertise brought will be the most useful to the project. The SJU resources will be provided through the SJU Airspace User Framework Contract (Tasking Contract) subject to availability. The WP11 Project Manager, in co-ordination with the Work Package Leader, shall define the Airspace User Task Requirements, Deliverables, Deadlines and the respective Airspace User Categories, Expertise type and associated Effort. On an annual basis these shall be agreed between the SJU and the Project. Any execution of these activities will be under the control of the SJU, but co-ordinated by the Project. The estimated effort required by the Project should be identified during the Call for Tender and refined with the SJU during the Initiation Phase. Risks Risk Management and detailed risks identification, opportunities and mitigation are expected to be taken into account and developed within the final proposal. Management See P11.2.0 “Co-ordination and Management” for additional information.

SJU DoW WP11 v2.0

Page 72 of 72