Communications Operating Concept

1
Communications Operating Concept Requirements
(COCR)- Status and Next Steps

• AGCFG/ICAO ACP WG-C
• Brussels
• September, 2006
• Brent Phillips - FAA
• Soren Dissing - EUROCONTROL

2
Outline

• Purpose of the COCR
• Producing Version 1.0
• History
• Comment process
• Acceptance of Version 1.0
• Development of Version 2.0
• Areas for further work
• Conclusions

3
Aircraft Traffic ? Communications
A Day in 2025

• More than double todays traffic
• Advanced ATC concept
• Data is Primary

• T -Throughput
• C - Continuity
• I - Integrity
• A - Availability

4
Overview of the COCR (1/3)

• Captures the operational requirements for Phase 1
  (from now to 2020) and Phase 2 (beyond 2020)
• Concept in Phase 1 is drawn largely from
  EUROCONTROL ATM concept document for 2008-11
  2020 and beyond
• Concepts in Phase 2 are based on more extensive
  use of Phase 1 services and NGATS operations
  (e.g. 4D Trajectory Management)
• Autonomous operations take place in some parts of
  the airspace
• Auto-EXECUTE has been added in line with NGATS
  concepts for wake vortex separation
• Based on postulated ATS operational concept using
  existing documentation and extending it into the
  future
• Provides traceability to information sources

5
Overview of the COCR (2/3)

• From the operational concepts, information flows
  have been identified in representative test
  volumes of airspace i.e. positions/sectors in
  Airport, TMA, En Route, Oceanic.
• Airport positions Radar sectors in Phase 1
  similar to today
• Radar sectors larger in Phase 2, perhaps 2-3x.
  Airport positions pretty much the same as Phase 1
• Covers all ATS and AOC air-to-ground and
  air-to-air voice and data communication
• Includes ADS-B and AOC applications
• Includes micro-jets UAVs (only ATC control
  element)
• Does not include Air Marshall, UAV Command
  Control, SWIM, or spacecraft communications

6
Overview of the COCR (3/3)

• Identifies all communication requirements based
  on safety and security analysis
• Availability, continuity, reliability and latency
• Requirements are technology independent
• Communication requirements are then used in a
  queuing model for communication loading (b/s per
  service volume)
• Aircraft numbers are grown over time using
  EUROCONTROL SAAM data in ECAC MLM in US
• At the end of the document a typical example use
  of the results volumes in a real world
  environment
• Will help technology assessment activity

7
COCR V1.0 Summary

• Overall
• In terms of capacity, future ATS air/ground data
  requirements appear to be relatively modest.
  However, this problem has more than one
  dimension, as delivery of air traffic services
  requires simultaneous achievement of many, often
  challenging, requirements.
• The safety-driven combination of capacity,
  integrity, reliability, latency and coverage
  requirements typically dictate unique solutions
  for aviation.
• While Phase 2 requirements appear to be beyond
  the capabilities of systems currently deployed,
  numerous advanced technologies, as well as
  options for further evolution of todays most
  capable systems, should meet all but the most
  demanding needs.
• To implement this two-phased vision affordably,
  careful examination of the services, especially
  those that drive requirements, will be necessary
  to balance costs and benefits.

8
Current Status

• Version 1.0 is mature
• Significant feedback from industry (over 300
  comments received)
• Comments incorporated into V1.0
• COCR V1.0 distributed at the beginning of March
  2006
• On the EUROCONTROL website
• Provided to SESAR
• Signed by FAA senior management and on their
  website
• Input to NGATS
• Some outstanding issues to be resolved in a new
  version of the COCR

9
COCR Version 2.0

• Activities to finalise COCR Version 2.0 include
• Ensuring satisfactory agreement among
  stakeholders with some of the more stringent
  services and the surrounding concept of their use
• Capture and definition of missing services
• Further definition of the services to ensure a
  more complete understanding of their operational
  use
• Categorisation of the services into groups based
  on likeness
• Assessment of the safety and security
  requirements associated with each group
• Assessment of the associated performance
  requirements impact
• Adding an Executive Summary
• Respond to comments received on COCR Version 1.0
  and clarify areas of ambiguity

10
Phase 2 Services

• Better description and operational definition of
  Phase 2 services e.g. COTRAC
• Clarification of their operational use
• Development of specimen OSEDs to better define
  safety requirements provide more accurate
  communication performance assumption
• Recognising that data services are the primary
  means of communication
• Clarify the use of service requirements in or at
  the boundary of Autonomous Operations Areas
• Understand the ramification of the operational
  scenarios on the technical performance
• Are they realistically achievable?

11
Iterative Loop Process
12
Conclusions

• COCR Version 1.0 was a major achievement
• Being widely reviewed
• Input to SESAR and NGATS
• Used in technology assessment
• Further refinement of the COCR
• Concepts being reviewed in the light of safety
  performance requirements
• Review feasibility of meeting the concept
  requirements
• Close co-operation between FAA and EUROCONTROL to
  complete tasks
• Progress will be reported to ACP and feedback
  sought
• COCR Version 2.0 targeted for completion in March
  2007

13
Thank You