The Structure of the Work Programme

1
The Structure of the Work Programme

• Patrick Ky Executive Director SJU
• Michael Standar Chief Concept Validation
• Ukraine, 25-26 June 2009

2
Foundations for the SESAR programme

• One programme for Europe
• 200M spent in ATM RD in Europe for the last
  10-15 years
• Average projects size 1.1M over 6 years
• 180 different operational concepts
• 85 projects claim their results will be
  implemented in the next 2-3 years
• (source EUROCONTROL ARDEP)
• New technologies and operational procedures
• Capacity increase through more precise traffic
  organisation and detailed operational procedures
• Certain basic technologies need to be replaced
• We are reaching the limits of the system (size
  of sectors, individual workload, runway capacity
  and environmental constraints)
• We have now a globally stable and harmonised
  level of systems capability in Europe, thanks in
  particular to EUROCONTROL actions
• RD resulting in actual implementation
• Track record for field implementation is low

3
The SESAR Governance for membership negotiations

• 16 partners, representing 36 companies
• 13 ANSPs
• 2 aircraft manufacturers
• 3 Avionics manufacturers
• 10 ground equipment manufacturers
• 9 airport organisations
• 2 Space systems manufacturers
• 1 research organisation
• EUROCONTROL
• The cooperation mechanism
• A technical bottom up process to ensure buy-in
• A steering group with one head negotiator by
  candidate, with sufficient authority to take
  binding decisions for his/her organisation
• Cooperative and transparent decision making
• The chairman of the steering group has decision
  making power in case of disagreement

4
Outcome of negotiations

• Description of Work done in 9 months (253
  projects)
• Agreement on budget distribution reached in 3
  months
• 92 coordinated offers (out of 1155) for the
  award of projects, average success rate of 88,
  for a total amount of activity of 1.3 B
• Strong Partnership spirit, in individual groups
  (e.g. ANSPs, ground industry) even between
  competitors, and across domains
• Dispute solving done at managerial level,
  willingness to change and to work together.
• Single Sky Committee (23/03/09) and SESAR JU
  Administrative Board (26/03/09) endorsed the
  accession of the 15 candidate members from
  industry
• Contracts to be signed in April-May, work kicked
  off in May-June.
• Cooperative decision-making is possible

5
The SESAR programme just started!
6
Key facts

• 250 projects
• 16 work packages
• Some WPs will soon be subject to calls for
  proposals (WPE, WP11)
• Leadership on work packages and project to SESAR
  partners
• Initiation phase 3-6 months starting in May 09
• Consistent engineering methodology
• Validation close to market
• Performance partnership

7
A WP for every step of the flight
WP16
WP15
WP B / C
WP9 / 11
WP3
WP7 / 13
WP4 / 10
ToC
ToD
WP5 / 10
WP5 / 10
CTA
WP8 / 14
WP6 /11/12
WP6 /11/ 12

• Key steps
• Time based operations
• 4 D Trajectory operations
• Performance based operations
• over a SWIM/IP network

8
The programme organisation in details
9
SOME KEY PRINCIPLES GOVERNING THE PROGRAMME
DECISION MAKING

• The following are the main principles governing
  the Programme
• The Deliverable D6 Work Programme serves as a
  basis for the SESAR Programme definition and
  organisational structure
• The Programme will be executed by SESAR JU
  Members under the supervision of the SJU
• The SJU will also award contracts with specific
  categories of stakeholders, such as Airspace
  users or Staff organisations
• The SJU has the the final decision for the
  Go/No-Go decision at the end of the Initiation of
  Projects and for the acceptance of deliverables
• The following are the main principles governing
  decision-making within the Programme

10
THE PROGRAMME STRUCTURE 3 DIMENSIONS TO INTEGRATE

• When defining the SESAR Programme structure, the
  3 following aspects needed to be taken into
  account
• RD activities management
• Operational ATM needs
• Technical coherence
• Hence, the SJU defined the Programme structure
  around three dimensions
• The Work Packages dimension (Work Breakdown
  Structure)
• Organising the RD activities into operational,
  systems or transversal groups or Projects
• The ATM Operational Services dimension
• Covering operational ATM needs, ensuring
  coherent design of the ATM Operational Services
  by Projects in accordance with the SESAR Concept
  Story Board
• The Clusters dimension
• Covering technical coherence by controlling the
  research and development deliverables from
  Projects which address an ATM common theme

1
2
3
Project
Each Project is part of each dimension of the
Programme
11
THE WPs DIMENSION ORGANISING THE RD ACTIVITIES
1/6
1

• The structure enabling the RD activities for the
  definition and validation of the ATM Target
  Concept has been built on this basis
• Identification of ATM operational domains and
  their related systems, defining the 4 threads
  Operational, SWIM, Systems, and Transverse and
  their joined Work Packages
• Identification of the needed RD activities and
  their related management activities per WP,
  defining the Sub-WPs and projects contents
• And finally, positioning of the members regarding
  the RD and project management activities to
  perform

SESAR Programme
WP B
WP C
WP D
Master Plan Maintenance
Target Concept Architecture Maintenance
ATM Network RD Programme
These 4 threads are classifying the activities
into 16 Work Packages (WPs) Overall
Transverse thread Operational thread SWIM
thread Systems thread
WP 16
WP 3
ValidationInfrastructure
RD TransversalAreas
WP 7
WP 5
WP 8
WP 14
W 11
WP 15
WP 13
NetworkOperation
TMAOperation
Network InformationManagement Systems(NIMS)
InformationManagement
F/WOC
CNS
SWIM
SWIM Thread
WP 4
WP 6
WP 10
WP 12
En RouteOperation
AirportOperation
WP 9
En-route APP ATC Systems
Airport Systems
Aircraft
First level of the Work Break down Structure and
its four threads
12
THE WPs DIMENSION ORGANISING THE RD ACTIVITIES
2/6
1
Overall Transversal thread WPs assigned to the
co-ordination, consistency check and validation
of the activities performed in the different
threads and involved in RD activities linked to
transversal improvements steps
SESAR Programme
WP B
WP C
WP D
Master Plan Maintenance
Target Concept Architecture Maintenance
ATM Network RD Programme
WP 16
WP 3
ValidationInfrastructure
RD TransversalAreas
WP 7
WP 5
WP 8
WP 14
W 11
WP 15
WP 13

• Key Figures
• 4 Work Packages B, C, 3, 16
• Maximum level of co-financing M 88,4

NetworkOperation
TMAOperation
Network InformationManagement Systems(NIMS)
InformationManagement
F/WOC
CNS
SWIM
SWIM Thread
WP 4
WP 6
WP 10
WP 12
En RouteOperation
AirportOperation
WP 9
En-route APP ATC Systems
Airport Systems
Aircraft
WP B
The scope of the of the Target Concept
Architecture maintenance is to Cover the
maintenance and refinement of the high-level ATM
Performance Target and Architecture including the
Concept of Operations (CONOPS). It defines and
ensures the consistency of the ATM Service
architecture for all SESAR WPs. WPB will also
conduct a performance analysis of the ATM Target
Concept throughout SESAR development phase
WP C
The scope of the Master Plan Maintenance Work
Package is to administrate the up-to-date
maintenance of the ATM Master Plan to monitor the
progress of development and of implementation. It
also maintains the standards and regulatory
roadmaps as well as the SESAR business cases
WP3
The scope of the Validation Infrastructure
Adaptation and Integration Work Package is to
build a comprehensive and integrated validation
infrastructure to fulfill the overall validation
needs for the SESAR ATM system. It coordinates
the development and deployment of the validation
infrastructure needed for all SESAR validation
activities including the system of systems aspects
WP16
The scope of the RD Transversal Areas Work
Package cover the improvements needed to adapt
the Transversal Area (TA) (safety, security,
environment, contingency (service continuity) and
human performance) management system practices to
SESAR as well as towards an integrated management
system. WP16 also provides support and
coordination for the consistent and coherent
application of the already existing as well as
newly developed TA-related practices to SESAR
operational and system Work Packages
13
THE WPs DIMENSION ORGANISING THE RD ACTIVITIES
3/6
1
Operational thread WPs related to the Operational
Contexts. Each Operational WP will be responsible
to analyse , develop the operational improvements
linked to the Operational Context, and validate
the solutions developed by the System Thread
Projects
SESAR Programme
WP B
WP C
WP D
Master Plan Maintenance
Target Concept Architecture Maintenance
ATM Network RD Programme
WP 16
WP 3
ValidationInfrastructure
RD TransversalAreas
WP 7
WP 5
WP 8
WP 14
W 11
WP 15
WP 13

• Key Figures
• 4 Work Packages 4,5,6,7
• Maximum level of co-financing M 167,2

NetworkOperation
TMAOperation
Network InformationManagement Systems(NIMS)
InformationManagement
F/WOC
CNS
SWIM
SWIM Thread
WP 4
WP 6
WP 10
WP 12
En RouteOperation
AirportOperation
WP 9
En-route APP ATC Systems
Airport Systems
Aircraft
WP4
Provides the operational concept description for
the En-Route Operations and perform its
validation. The term En-Route includes both
continental and oceanic applications (as
appropriate). This covers all phases of planning
and execution of flights/trajectories and the
identification of supporting functions necessary
for En-route operations. WP 4 is further
organised into 15 projects.
WP5
Manages and performs all Research, Development
and Validation activities required to define the
TMA ATM Target Concept (i.e. Concept of
Operations, and System Architecture). This covers
all phases of planning and execution of
flights/trajectories and the identification of
supporting functions necessary for TMA
Operations. The TMA Operations WP will address
the management of traffic from the top of descent
until landing and from take off until the top of
climb. WP 5 is further organised into 17 projects.
WP6
Refines and validates the concept definition, as
well as the preparation and coordination of its
operational validation process. The Airport
Operations Work Package will address developments
associated with the airside elements of airport
operations only. WP6 is further organised into 22
projects.
WP7
Covers the evolution of services taking place in
the business development and planning phases to
prepare and support trajectory-based operations
including airspace management, collaborative
flight planning and Network Operations Plan
(NOP). It encompasses the services included in
the execution phase to facilitate
trajectory-based operations in case of capacity
issues. WP 7 is further organised into 12
projects.
14
THE WPs DIMENSION ORGANISING THE RD ACTIVITIES
4/6
1
SWIM thread Defines and validates the evolutions
towards the Systems Wide Information Management.
It addresses both operational aspects and
technical aspects
SESAR Programme
WP B
WP C
WP D
Master Plan Maintenance
Target Concept Architecture Maintenance
ATM Network RD Programme
WP 16
WP 3
ValidationInfrastructure
RD TransversalAreas
WP 5
WP 7
WP 8
WP 14
W 11
WP 15
WP 13

• Key Figures
• 2 Work Packages 8, 14
• Maximum level of co-financing M 56,4

NetworkOperation
TMAOperation
Network InformationManagement Systems(NIMS)
InformationManagement
F/WOC
CNS
SWIM
SWIM Thread
WP 4
WP 6
WP 10
WP 12
En RouteOperation
AirportOperation
WP 9
En-route APP ATC Systems
Airport Systems
Aircraft
WP8
The scope of the Information Management Work
Package concerns the "Intranet for ATM". In order
to establish the ATM SWIM (System Wide
Information Management) needed to achieve
interoperability and inter-system seamless
operations, WP8 defines the ATM Information
Reference Model and the Information Service model
to be used by the various ATM services and
necessary to develop the SWIM specifications and
test platforms. WP 8 is further organised into 18
projects.
WP14
The SWIM Work Package is the follow-up of the
SWIM SUIT FP6 Commission project in the context
of SESAR. It will use as an input the SWIM-SUIT
deliverables and adapt them or further develop
them to cope with the SESAR Work Programme
components. WP 14 is further organised into 9
projects.
15
THE WPs DIMENSION ORGANISING THE RD ACTIVITIES
5/6
1
Systems thread Defines and validates the systems
that support the ATM Target Concept. Organised
according to the major systems/ platforms
SESAR Programme
WP B
WP C
WP D
Master Plan Maintenance
Target Concept Architecture Maintenance
ATM Network RD Programme
WP 16
WP 3
ValidationInfrastructure
RD TransversalAreas
WP 5
WP 7
WP 8
WP 14
W 11
WP 15
WP 13

• Key Figures
• 6 Work Packages 9, 10,11, 12, 13,15
• Maximum level of co-financing (except WP11)
  M299,2

NetworkOperation
TMAOperation
Network InformationManagement Systems(NIMS)
InformationManagement
F/WOC
CNS
SWIM
SWIM Thread
WP 4
WP 6
WP 10
WP 12
En RouteOperation
AirportOperation
WP 9
En-route APP ATC Systems
Airport Systems
Aircraft
WP9
The scope of the Aircraft System Work Package
covers the required evolutions of the aircraft
platform, in particular to progressively
introduce 4D Trajectory management functions in
mainline, regional and business aircraft to
provide very precise 4D trajectory management
capabilities (3 spatial dimensions time). The
work will address as well the progressive
development of Aircraft Separation Assurance and
the aircraft components required for the
improvement of surface movement operations. WP 9
is further organised into 26 projects.
WP10
The scope of En-Route Approach ATC Systems
includes all Research Development activities to
define, design, specify and validate the En-route
TMA ATC Systems evolutions for introducing and
enhancing Trajectory Management functions, new
Separation Modes, Controller Tools and
SafetyNets, Airspace Management supporting
functions, Management Complexity tools, Queue
Management and Route optimisation features. WP 10
is further organised into 23 projects.
WP11
The scope of the Flight Operations Centre Work
Package covers the development of the Airspace
Users operations systems required to support the
implementation of the various SESAR components
(e.g. adaptation to the 4D trajectory).
16
THE WPs DIMENSION ORGANISING THE RD ACTIVITIES
6/6
1
WP12
The scope of the Airport Systems Work Package
encompasses all Research Development activities
to define, design, specify and validate the
Airport Systems needed to support the SESAR ATM
target concept. It also addresses
system/technical aspects such as functional and
technical architecture, technical performance
safety requirements, technical interoperability
requirements, associated specifications,
models/simulation platforms and prototypes,
technical validation and the development of
inputs/proposals to technical standards
groups. WP 12 will undertake technical
developments and validation/verification,
providing the ground-based system support to the
new concepts, procedures and practices described
by WP 6. WP 12 is further organised into 29
projects.
WP13
The scope of the Network Information Management
System Work Package covers the System
and Technical RD tasks related to the Network
Information Management System (NIMS), the
Advanced Airspace Management System (AAMS) and
the Aeronautical Information management System
(AIMS). It addresses the NIMS system-level
definition and architecture concentrating on
interoperability with other systems, further
decomposes it into sub-systems from logical down
to physical layers. It addresses the impact of
new roles responsibilities on
local/sub-regional/regional systems considering
the mapping of system functions on the various
local/sub-regional/regional systems (namely NIMS,
AOC, Airport, en-route/approach ATC). The WP will
then undertake the NIMS sub-systems definition
and verification, addressing interoperability and
connection between sub-systems and coordinate the
management of common components between
sub-systems. WP 13 is further organised into 6
projects.
WP15
The Non Avionic CNS System Work Package addresses
CNS technologies development and validation also
considering their compatibility with the Military
and General Aviation user needs. It identifies
and defines the future mobile datalink systems to
serve communication and surveillance services,
the ground SWIM backbone system. It addresses
the best combination of GNSS and non- GNSS
Navigation technologies to support Performance
Based Navigation and precision approach
requirements. It proceeds to the enhancements of
the ground Surveillance systems, the introduction
of new Surveillance systems as well as the use of
future Surveillance applications including ADS-B
applications beyond Initial operational
capabilities. WP15 is further organised into 15
projects.
17
THE ATM OPERATIONAL SERVICES DIMENSION COVERING
THE OPERATIONAL ATM NEEDS ASPECT
2

• What is an ATM Operational Service?
• To respond to the need to develop a Service
  Oriented ATM System, ATM Operational Services
  are developed
• ATM Operational Services support the structuring
  of the SESAR Concept of Operations and Work
  Programme, focusing on meeting the business and
  operational needs of all ATM partners
• ATM Operational Services are the operational
  relationships between the actors involved in
  performing operational processes needed to
  conduct Flight Phases
• These services play a significant role in
  structuring the Single European ATM Architecture
• Performance expectations on ATM Operational
  Services will be derived from the SESAR
  performance objectives
• Some 300 projects will contribute to SESAR.
  Projects may have different operational
  dependencies
• A single Project may contribute to the
  development of many ATM Operational Services the
  development of a single ATM Operational Service
  may require the contribution of several projects

• Therefore grouping projects by Operational step,
  ATM Operational Service and by Flight Phase will
  bring coherency in design, validation and
  verification
• Work Package B defines and ensures the
  consistency of the ATM Operational Services
  architecture for all SESAR WPs, in accordance
  with the Roadmap defined in the SEMP

18
THE ATM OPERATIONAL SERVICES DIMENSION COVERING
THE OPERATIONAL ATM NEEDS ASPECT
2
Example

• There is a need to identify all the Projects that
  contribute to the design, validation and
  verification of a same common ATM theme
• In this illustration, the ATM Operational Service
  Queue Management for the Flight Phase Descent
  is isolated by linking the ATM Operational
  Service with the Flight Phase

Taxi/ Apron
Runway
Climb
Cruise
Descent
Traffic management
Long term planning
FLIGHT PHASES
Asset resources management
Asset resources management
Demand capacity balancing
Demand capacity balancing
Demand capacity balancing
Demand capacity balancing
Demand capacity balancing
Trajectory management
Trajectory management
Trajectory management
Trajectory management
Trajectory management
Trajectory management
Queue management
Queue management
Queue management
Queue management
Queue management
Queue management
Conflict management
Conflict management
Conflict management
Conflict management
Conflict management
Runway management
Surface management
Turn round management
Turn round management
Turn round management
Turn round management
Turn round management
Example
WP7 Network operations WP13 Network Management
WP15 Non-Avionics CNS Systems
WP9 Aircraft Systems WP11 Flight Operations
Centre

• The ATM Operational Service Queue Management
  for the Flight Phase Descent has contributions
  from various Projects under different WPs
  (Operational and System)
• These interdependencies must be identified to
  ensure coherent design, validation and
  verification, and to manage scheduling, changes,
  and defaults

WP5 TMA Operations WP10 Ground ATM Systems
WP8 Information Management WP 14 SWIM
WP6 Airport Operations WP11 Flight Operations
Centre WP12 Airport Operational Systems
Queue Management
WP B Target Concept and Architecture Maintenance
WP3 Validation infrastructure Adaptation and
Integration
WP16 RD Transversal areas
19
THE CLUSTERS DIMENSION COVERING THE TECHNICAL
COHERENCE ASPECT

3

• Clusters ensure Technical Coherence between
  Projects addressing a common ATM theme (e.g.
  Queue Management)
• The management of the SESAR Programme
  exclusively at the level of an ATM Operational
  Service will not guarantee the overall technical
  coherence of the Programme. Consequently,
  clusters have been created to ensure
  collaboration between interdependent projects to
  achieve overall technical coherence
• A common ATM theme is a combination of several
  ATM Operational Services in different Fight
  Phases. As an example, the Operational Service
  Queue Management in the Descent and the
  Runway Flight Phases address the same ATM
  theme and are clustered
• A Cluster groups Projects together virtually
• The ATM Operational Services clustered in a
  common ATM theme are developed by several
  Projects under various WPs
• This clustering ensures technical coherence of
  the RD activities, according to the System
  Engineering Methodology
• Projects documents will be peer reviewed in
  Cluster working sessions to check coherence and
  detect defaults
• A Project only ever belongs to one Cluster

• A structuring component for the Initiation Phase
• Clusters are also used to initiate the scheduling
  of project deliverables requested for the
  Initiation Phase, and will facilitate transversal
  peer reviews by members of projects contributing
  to the cluster

• The next slide shows a high level example of
• How different Projects contribute to the
  development of a single and common ATM theme
• And How the RD activities must be technically
  coherent

For the Cluster list, please refer to the Annex
B of the System Engineering Management Plan
20
THE CLUSTERS A WAY TO ENSURE THE TECHNICAL
COHERENCE
3
Example
Taxi/ Apron
Runway
Climb
Cruise
Descent
Traffic management
Long term planning
FLIGHT PHASES

• In this illustration, Projects x.1, y.3 and z.6,
  under different WPs, contribute to ATM
  Operational Services in the common ATM theme
  Queue Management. They should be developed in a
  technically coherent manner
• For this reason, Projects are grouped
• virtually into a Cluster in order to monitor
  technical coherence
• of RD activities

Asset resources management
Asset resources management
Demand capacity balancing
Demand capacity balancing
Demand capacity balancing
Demand capacity balancing
Demand capacity balancing
Trajectory management
Trajectory management
Trajectory management
Trajectory management
Trajectory management
Trajectory management
Common ATM Theme Queue Management
Queue management
Queue management
Queue management
Queue management
Queue management
Queue management
Conflict management
Conflict management
Conflict management
Conflict management
Conflict management
Runway management
Surface management
Turn round management
Turn round management
Turn round management
Turn round management
Turn round management
ATM OPERATIONAL SERVICES AXIS
Example
P x.1
P x.2
P y.1
P y.2
P z.1
P z.2
Virtual grouping of these Projects during a
Cluster working session
P x.3
P x.4
P y.3
P y.4
P z.3
P z.4
P x.5
P x.6
P y.5
P y.5
P z.5
P z.6
WP x
WP y
WP z
21
Conclusion

• Initiation
• Defines project scope and objectives
• Defines project charter
• Allows participant to start the RD work

• Programme vs. Project Lifecycle
• Projects focus on their activities and their
  results
• Projects are connected throught the gates to the
  programme lifecycle

• Organisation
• Responsibilities defined at different layers,
• Sub WP managers involved in Engineering
  Methodology
• Work Package working arrangement guidance
  provided by the PMP

• Governance
• Lean, 2 layers
• Contractual interface vs. Operational interface

22
Thank you for your attention
www.sesarju.eu