airport surface cdm scenario and implementation：机场地面清洁发展机制方案与实现

Surface CDM Sub-team,Concept of Operations Briefing,Marshall Mowery (FAA CDM Lead)Dan Allen, FedEx Express (Industry CDM Lead)Carl Calcasola, ATM PBIBernie Davis, ATC Manager US AirwaysTuesday, May 3, 2011,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,Policy,Development of CONOPSIdentified policy issues that need to be considered from FAA, DOT, Airlines and AirportsOngoing effort,Concept of Operations,February 2011Delivered final submission of CONOPS after being vetted by CSG,Background,Intro to ConOps What it isInformation sharingDemand and capacity predictionsQueue management,Additional needs,Develop tool sets in order to gain a better understanding of the CONOPSEnhancement of ScenariosDevelopment of Airport Categorization,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,Plug and Play Concept,Airport Surface CDM Scenario and Implementation,Notional Airport,Departure Metering Procedures will be Implemented,1300z: DRM receives departing flight infoDeparture demand exceeds 32/hr capacity beginning at 1500z and is expected to continue for the next 6 hours1315z: DRM develops spot allocation plan using Ration by Schedule, or other industry accepted alternatives,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 capacity1st slots are managed but are not delayed,Changes to the Allocation/Reallocation of Flights,1514z: GA aircraft calls DRC for spot allocation1515z: DRC assigned average delay to GA flight with a movement area entry time of 1530z1530z: GA aircraft taxis to movement area entry location,Changes to the Allocation/Reallocation of Flights,1615: EDCT or other TFM or ATC generated delays,Capacity Change,1630z: Capacity exceeds demand due to rapidly improving weather or GA flights that never materialized1745z: Runway configuration change due to weather,Capacity Change,1800z: Deicing is conducted. DMP is in effect1810z:A flight operator cannot meet allocation and does not notify the DRM. This is a “missed” allocation,Whats Next?,Define and gain consensus on a Work Plan to develop information exchange requirements per RTCA Task Force Recommendations Types of data to be exchangedTiming of data exchange, when data is to be sent and/or receivedOpportunities for integrationsHuman in the Loop analysesTest site opportunities and locationsTimeframesFunding information. (Who, what, where),Final Products,Information Exchange Requirements Work Plan Revised Surface CDM System (SCS) Functional Requirements Document Updated Surface CDM Conops,Questions?,Thank You,Suggestions for Variances,Comment Iteration Process,Final Delivery Deadline May 6th,Airport Surface Categories,Category 1ATC handles all push-backs at