1. ACG Workshop, 17 Feb 2004 – OATA project Concept of Operations (ConOps) ACG Workshop, 17 February 2004 Jose Varela and Ian Ramsay, SD/ESC

2. ACG Workshop, 17 Feb 2004 – OATA project Concept of Operations Background The OCD Development Process The CONOPS Scenarios Use Cases

3. ACG Workshop, 17 Feb 2004 – OATA project OCD (ConOps) Vol. 2 OCD (The Vision) Vol. 1 Background

4. ACG Workshop, 17 Feb 2004 – OATA project 2002 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 2020 2002200320042005200620072008200920102011201220132014201520162017201820192020 OCD The Vision ConOps 2020 Issue 1 ConOps 2007 Issue 1 ConOps 2020 Issue 2 ConOps 2011 Issue 2 ConOps 2007 Issue 2 ConOps 2011 Issue n ConOps 2020 Issue... V1V2V3V4V5 V3V4V5 OI x validation lifecycle V1V2V3V4V5 OI x validation lifecycle ATM 2000+ Strategy OATA 2011 ConOps 2020 Issue n ConOps 2011 Issue 1

5. ACG Workshop, 17 Feb 2004 – OATA project ConOps 2020 ConOps 2007 ConOps 2011 OATA OCD Vol. 2 (CONOPS) Concept of Operations (CONOPS)

6. ACG Workshop, 17 Feb 2004 – OATA project A detailed description of how an operational concept is applied. It identifies the functions and processes, and their corresponding interactions and information flows, concerned actors, their roles and responsibilities. Concept of Operations (Definition)

7. ACG Workshop, 17 Feb 2004 – OATA project Concept of Operations 2011: Description of the ATM System in 2011 The Layered Planning Process The Actors The Actors Roles and Responsibilities The Scenarios The Use Cases The Impact Statements The Operational Improvements Introduction: Scope Need for Change Assumptions Concept of Operations (CONOPS)

8. ACG Workshop, 17 Feb 2004 – OATA project Description of the ATM System in 2011 Planned Route Structure User Preferred Trajectory Free Route Operations Harmonised Airspace Categories Dynamic Sectorisation Enhanced FUA Airspace 2011 Integrated AMAN/DMAN is used in some DMAN is used in many AMAN is used Standard MTCD is used Standard MONA is used Standard Initial CORA 2 is used in some Controller Tools 2011

9. ACG Workshop, 17 Feb 2004 – OATA project > 1 Year> 1 Week> 1 Day> 1 Hour ASM Airspace structure design & Modus Operandi ATFCM Optimised Capacity Management Daily Operations Plan Capacity Plans Aeronautical Information data Decision ~ RPL ATFCM FPL X Days before Operation CPL Decision Updated Airspace User Plan Tactical Flow & Capacity Management X Hours before EOBT or Operation X Months before Operation Actual Status Mil. ATSUs ACCs CP L Airspace User Plan Decision ASMASM / ATFCM Airspace re-allocation/Re-consider scenarios FPL re-processed FPL Airspace Users ~RPL IFPS FPL PLANNING ANTICIPATING REACTIN G EXECUTING ATC Update Current Flight Plan Airspace activation/de-activation Implement scenarios StrategicPre-TacticalTactical ATC Strategic Flow & Capacity Planning Airspace allocation Allocate (scenarios) OPERATION Airspace Users CDM AIRPORTS Layered Planning Process

10. ACG Workshop, 17 Feb 2004 – OATA project Aeronautical Information Data Scenario & Modus Operand i SectorsRoutesAreas Daily Operations Plan Forecast Demand Sectorisation Planning Traffic Demand ASM Military Operations Airspace Users Airspace Requirements Flight Requirements ~ RPL* Capacity Plans Data Forecast Traffic Demand Airspace Demand OrganisationManagement ACCs Military ATSUs ATS Air Traffic Demand CDM Airports CFMUFMPs ATFCM Strategic Flow & Capacity Planning Capacity Planning Sectorisation Planning Strategic

11. ACG Workshop, 17 Feb 2004 – OATA project 2011 Strategy ATM 2000+ OCD (Vision) Volume 1 Operational Scenarios Use Cases 2020 Logical Architecture OCD (ConOps) Volume 2 OCD - OATA Relationship

12. ACG Workshop, 17 Feb 2004 – OATA project Flight Phases considered as described in the OCD

13. ACG Workshop, 17 Feb 2004 – OATA project Example of Actors Matrix for Planning and Execution of Flight Phases 2011 2011

14. ACG Workshop, 17 Feb 2004 – OATA project Example of Actors Matrix for En-route Scenario 2011 2011

15. ACG Workshop, 17 Feb 2004 – OATA project Scenario (Definition) Within the context of an operational concept, scenarios are a description of how a future system should work. Each scenario describes the behavior of Users and the future System, interaction between the two, and the wider context of use. From a detailed scenario a user should be able to identify user requirements and potential business cases.

16. ACG Workshop, 17 Feb 2004 – OATA project MTCD Sector A 245-UNL Sector A 245-UNL Sector B 245-UNL Sector B 245-UNL Sector C 245-UNL Sector C 245-UNL DLH0002 FL 270 cleared FL 350 Fix C1 Fix B1 Fix B3 Fix B2 Fix C2 IBE0001 FL 330 cruise JKK0003 FL 270 cruise MTCD R/T DLH0002 FL 350 cruise IBE0001 FL 330 cruise Sector A 245-UNL Sector A 245-UNL Sector B 245-UNL Sector B 245-UNL Sector C 245-UNL Sector C 245-UNL DLH0002 FL 270 cleared FL 350 Fix C1 Fix B1 Fix B3 Fix B2 Fix C2 IBE0001 FL 330 cruise JKK0003 FL 270 cruise DLH0002 FL 350 cruise IBE0001 FL 330 cruise FL 350 CFL = 320 FL Proposed Solution: Stop climb at FL 320. AFR0004 FL 320 cruise 10:28 10:24 10:25 10:29 FL 330 10:24 MTCD warning disappears 10:22 Ellbow Communication 10:24 No conflict with proposed solution 10:22 DLH 0002 Stop climb at FL 320 09:50 09:51 09:52 09:53 09:54 09:55 09:56 09:57 09:58 09:59 10:00 10:01 10:02 10:03 10:04 10:05 10:06 10:07 10:08 10:09 10:10 10:11 10:12 10:13 10:14 10:15 10:16 10:17 10:18 10:19 10:20 10:21 10:22 10:23 10:24 10:25 10:26 10:27 10:28 10:29 10:30

17. ACG Workshop, 17 Feb 2004 – OATA project A Use Case captures a contract between the stakeholders (actors) of a system about its behaviour. It describes the systems behaviour under various conditions as the system responds to a request from one of the stakeholders (the primary actor). The primary actor initiates an interaction with the system to accomplish some goal. The system responds protecting the interests of all stakeholders. Use Case (Definition)

18. ACG Workshop, 17 Feb 2004 – OATA project Content of a Use Case A formal and rigid template comprising: Scope Level Summary Actors Pre- and Post-conditions Notes Trigger Main flow Alternative and Failure flows

19. ACG Workshop, 17 Feb 2004 – OATA project Use Case Realisation

20. ACG Workshop, 17 Feb 2004 – OATA project European ATM 2000+ Strategy Strategic Objectives: Safety; Capacity; Efficiency; Environment Airports Human Aspects; Procedures; Systems; Institutional Issues; Environment Business Impact Business Impact and Benefits Illustration

21. ACG Workshop, 17 Feb 2004 – OATA project Questions?