1. 1 Surface CDM Sub-team Concept of Operations Briefing Marshall Mowery (FAA CDM Lead) Dan Allen, FedEx Express (Industry CDM Lead) Carl Calcasola, ATM PBI Bernie Davis, ATC Manager US Airways Tuesday, May 3, 2011

2. 2 Metrics Provide a written summary describing the appropriate metrics that validate the benefits of the Surface CDM capabilities and are consistent with the FAA NextGen Implementation Plan. Provide recommendations for metrics that address the overall concept, as well as individually described capabilities.  Identified 31 items

3. 3 Policy Development of CONOPS Identified policy issues that need to be considered from FAA, DOT, Airlines and Airports Ongoing effort

4. 4 Concept of Operations February 2011 Delivered final submission of CONOPS after being vetted by CSG

5. 5 Background Intro to ConOps – What it is  Information sharing  Demand and capacity predictions  Queue management

6. 6 Additional needs Develop tool sets in order to gain a better understanding of the CONOPS Enhancement of Scenarios Development of Airport Categorization

7. 7 Scenario Overview Surface CDM capabilities may allow operators to manage planned delay in a more cost effective manner by holding aircraft at the gate to avoid excessive departure queues at the runway

8. 8 Plug and Play Concept

9. 9 Airport Surface CDM Scenario and Implementation Notional Airport

10. 10 Departure Metering Procedures will be Implemented 1300z: DRM receives departing flight info  Departure demand exceeds 32/hr capacity beginning at 1500z and is expected to continue for the next 6 hours 1315z: DRM develops spot allocation plan using Ration by Schedule, or other industry accepted alternatives

11. 11 Changes to the Allocation/Reallocation of Flights 1400z: Unscheduled maintenance will delay a 1500z allocated flight, Operator A notifies DRM that another flight will be reassigned to that time window. 1455z: 1st flight requests and receives pushback, others follow same process in order to meet 1500z allocation when demand exceeds capacity  1 st slots are managed but are not delayed Time period 1500-1514Z1515-1529Z1530-1544Z1545-1559Z SchAllocDelSchAllocDelSchAllocDelSchAllocDel Operator A54 1 5 4 2 54 3 5 4 4 Operator B5 4 1 54 2 5 4 3 54 4 Total10 82 84(1)10 8 (1) 6 10 8 8

12. 12 Changes to the Allocation/Reallocation of Flights 1514z: GA aircraft calls DRC for spot allocation 1515z: DRC assigned average delay to GA flight with a movement area entry time of 1530z 1530z: GA aircraft taxis to movement area entry location

13. 13 Changes to the Allocation/Reallocation of Flights 1615: EDCT or other TFM or ATC generated delays

14. 14 Capacity Change 1630z: Capacity exceeds demand due to rapidly improving weather or GA flights that never materialized 1745z: Runway configuration change due to weather

15. 15 Capacity Change 1800z: Deicing is conducted. DMP is in effect 1810z:A flight operator cannot meet allocation and does not notify the DRM. This is a “missed” allocation

16. 16 What’s Next? Define and gain consensus on a Work Plan to develop information exchange requirements per RTCA Task Force Recommendations  Types of data to be exchanged  Timing of data exchange, when data is to be sent and/or received  Opportunities for integrations  Human in the Loop analyses  Test site opportunities and locations  Timeframes  Funding information. (Who, what, where)

17. 17 Final Products Information Exchange Requirements Work Plan Revised Surface CDM System (SCS) Functional Requirements Document Updated Surface CDM Conops

18. 18 Questions? Thank You

19. 19 Suggestions for Variances

20. 20 Comment Iteration Process

21. 21 Final Delivery Deadline – May 6 th

22. 22 Airport Surface Categories Category 1  ATC handles all push-backs at an airport Category 2  ATC + 1 other surface stakeholder handle push-backs at an airport Category 3 (most complex)  ATC + 2 or more CDM stakeholders handle push-backs at an airport