Title: Episode 3 Operational Concept Detailing
1Episode 3 Operational Concept Detailing
Episode 3 - CAATS II Final Dissemination Event
Ros Eveleigh Eliana Haugg EUROCONTROL
DFS Episode 3
Brussels, 13 14 Oct 2009
2Content
- Objective of Concept Detailing
- Documentation Produced
- Concept Detailing Process
- Example results
- Operational Scenario example
- OS-35 High density TMA Arrival Flying CDA
Merging - Lessons Learnt
- Conclusions
3Objective of Concept Detailing
- Support implementation of SESAR Target Concept
- Production of specifications
- Need comprehensive coverage
- Sufficient level of detail
- Future OSED production
DODs
Process Model
Detailed Operational Descriptions
- Supporting validation activities
- Concept descriptions for exercises
Operational Scenarios
Storyboards
4The ATM Process Model
SESAR Operational Concept
Detailed Operational Descriptions
OSED Template
5Scope of DODs
POST
Cooperative planning
EXECUTION
FLIGHT
MID/ SHORT TERM
LONG TERM
General and Lexicon
Long Term Planning
Network Management in Execution
Short/Medium Network Planning
Collaborative Airport Planning
DODs
Conflict Management in En Route
Years to 6 months
6 months to 15 min
6DOD Development Process
SESAR sources e.g. Concept of Operations (D3),
Operational Improvement Steps (D5)
Initial DODs (Jan 08)
Expert Reviews
Exercise Needs
Interim DODs (Jan 09)
DODs
Expert Reviews
Exercise Results
Final DODs (Dec 09)
7Review Process
- DODs Reviewed by Experts
- Current Operations in ANSPs, ATFCM, Airlines,
Military - SESAR Definition Phase CONOPS (222)
- Some new material added through review
- Early user of Review Room
- Allowing potentially contradictory comments to be
easily identified - Hot topics identified debated
- Via Email difficult to record transparency v
spam effect - Via Discussion Room good
- Answers by Exercises or escalated to
Co-ordination Cell - Development of a Lexicon
- Developed agreed definitions for over 20 SESAR
terms - Available as document and on www.episode3.aero
8Additional Concept Detail
- Lexicon Definitions
- Paraphrasing text from 222
- Target Time of Arrival, Shared Business
Trajectory, Revision - Proposed in Episode 3
- Arrival Management, Constraint, Tolerance Window
- New text in the DODs
- SBT to RBT agreement
- 222 gives time, Episode 3 proposed set of
conditions - New Roles and Descriptions of Responsibilities
- Airport driver role, complexity manager
responsibilities - Hot Topics deferred for S-JU activities
- Successive authorisation v increased workload
AUO-0302 - Extent and meaning of CDM in execution phase
222/D.2
9DODs, Scenarios Storyboards
- DODs
- Specifications of main ATM processes
- Operational Scenarios
- Descriptions of how processes work together in an
operation - Operational scenarios fundamental to expert
groups, prototyping and gaming - Importance increased over time v Use Cases
- Storyboards
- Diagrammatic representation of parts of ATM
operations - Developed or reviewed in Expert Groups
- New in Episode 3
10- Concept wide view
- now
- Zoom in to the TMA
11General Development Process
- Operational Scenarios primarily developed to meet
Episode 3 Validation Exercise needs - Update with Episode 3 validation exercise results
and Episode 3 Expert Group comments where
available
12Operational Scenario Example
- OS-35 High density TMA Arrival Flying CDA
Merging - Input from SESAR
- Section F3.5 of SESAR ConOps refers to aircraft
that "as far as possible, fly their individual
optimum descend profiles" in medium/low
complexity TMAs - Section H2.3 of SESAR ConOps refers to high
complexity TMAs where a trade-off between
throughput, punctuality and environmental
performances will be made - The Operational Improvement steps (OI-steps)
addressed are - AOM-0701 Continuous Descent Approach (CDA)
- AOM-0702 Advanced Continuous Descent Approach
(A-CDA)
13Operational Scenario Example
- Input from early interim DOD G-General
- Contained initial high level CDA scenario Flying
CDA merging without Structured Routes - Input from additional sources used (EUROCONTROL
and ICAO documents, European and international
studies) - Operational Scenario was composed
- The TMA described in this scenario consists of
medium/low complexity and high traffic density - Aircraft have ATM Service and Capability Level 2,
scenario is set around 2015 time frame
14Operational Scenario Example
- The CDA scenario is set in a Point Merge airspace
structure - Scenario describes the processes and interactions
between human actors and systems for the
following cases
- Nominal CDA procedure
- CDA procedure with tactical ATC controller
intervention - CDA procedure with wind impact
IAF
IAF
15Operational Scenario Example
- Scenario was updated with Episode 3 Validation
Exercise results and comments from Episode 3 TMA
Expert Group - Scenario contains hop topic discussion boxes with
open issues. Example from case with tactical
intervention - Hot Topic How can the CTA and RTA of an aircraft
be revised? - Expert discussion Next generation of AMAN tools
should dynamically and continuously compute
revised CTA and a place in the arrival sequence - Scenarios will be disseminated as an annex of
Detailed Operational Descriptions
16- Zoom from the detail
- to
- Big Picture
17Lessons Learnt
- No Concept Authority
- Same topic discussed repeatedly
- But discussion needed for understanding
- Difficult to integrate exercise results
- Process defined, but difficult to agree
responsibilities - Consistency across DODs, Scenarios Storyboards
- In progress at the moment
- Hot Topics identified described
- Difficult, contentious or ambiguous problems
- Resolution, escalation or deferred for SESAR-JU
- Review Room and Discussion Room
- Management of discussion
- Debates recorded
18Conclusions
- Developed a Concept Detailing Process
- ATM Process Model DODs
- Operational Scenarios Storyboards
- Checks for completeness coherence
- Identification of Hot Topics
- Concept detailing started from SESAR D3
- Input from operational experts (incl airlines)
- DODs, Scenarios and Storyboards available
- Lessons Learnt