Substitution Rules and Data Quality

1. Substitution Rules and Data Quality Deliberations and Recommendations CDM Arrival/Departure subgroup 8 NOV 00

2. Background Meetings were conducted on two separate occasions. 18 OCT and 2 NOV. First meeting consisted of Users and FAA. - Participants were asked to define “gaming” - Participants were offered an opportunity to describe the uniqueness of their operations. Reasoning was to gain a understanding of how and why ad-hoc flights occur. Second meeting was ATA member only - Review the findings of the first meeting - Provide an opportunity for those not in attendance at the first meeting to offer input.

3. Prime Indicators Alteration of ETE field in a Adjust/Exchange CDM message Flights that were cancelled in ETMS yet Flew Flights added after a Ground Delay program was in effect. Flights created before a Ground Delay program is iniated. Slots that are exempt from deicing airports White Hat requests

4. Alteration of ETE field in adjust exchange message Recommendation Identify flights in which an adjust/exchange message is communicated that differs from the filed time enroute. • 25% or more for flights less than 120 minutes. • 40% for flights over 120 minutes

5. Canceled flights that Flew Flights cancelled by substitution message that ended up flying. There is no logical reason for this to occur!! Recommendation Identify and seek explanation for each occurrence.

6. Flights created before GDP in effect There are many legitimate business needs for these to occur. Users need to retain the flexibility of substitution into these slots. Recommendation Flights created for the sole purpose of substitution to gain an advantage should not be allowed to occur.

7. Flights created after GDP in effect Creates Havoc in the system. Resulting in extensions and revisions that increase delays. May be instances where warranted Recommendation Flights created after GDP in effect shall not be eligible for substitution. Note: The software will be automated so as not to allow this to occur when simplified substitution rules become effective. Target date Jan 01.

8. White Hats White hats cause increased unknown demand into the system. There are legitimate cases for whitehats Quite often they are used because they offer the path of least resistance Recommendations Need to devise a means of tracking requests and whitehats that are granted Direction needs to come from ATC steering committee to AOC level that these are only to be requested for extreme extenuating circumstances.

9. Conclusion’s All rules for Disincentive need to be incorporated into the new CDM MOA. A user who shows a consistent pattern of abuse should of the substitution process should be counseled. More severe penalties should be assessed if the pattern continues.

10. Issue’s Who police’s this? What penalties and the severity of such should be assessed?

11. Data Quality A Defense Mechanism Critical success factor Problems are multi-faceted - Volpe - ETMS - NAS Users

12. Data Quality “Dark Greenies” Flights that are scheduled to depart and for some reason have not departed. The perception is that this causes lack of confidence in the data. Result -- Local Augmentation of restrictions.

13. Data Quality The data gathered pertaining to the Revised EDCT compliance window should shed some light on the problem. Concern -- This test will not begin until Mid - Jan 01. We need to gain a better understanding of how these occur Prior to the beginning of this test.

14. Data Quality Recommendation Conduct a thorough analysis of a given days “dark Greenies” during a GDP. Require all entities to provide follow-up as to how these occurred.

15. Data Quality Getting a handle on data quality will be no easy task. A major problem is the architecture of the system. - ETMS - HOST - Local FAA Facility Procedures