Nancy Graham International Technical Representative - Europe, Africa and Middle East ATN2002 - IEE Conference - London,

1. FAA Oceanic ATM/CNS Plans & Experience Nancy Graham International Technical Representative - Europe, Africa and Middle East ATN2002 - IEE Conference - London, September 24-25, 2002

2. ATM/CNS Experience

3. The Evolution of FANS-1 • A core group of airlines who participated in the Pacific Engineering Trials (PET) determined that a significant reduction in operating costs were achievable by flying optimized flexible tracks on trans-Pacific routes • Reduced operating time • Reduced fuel burn • Increased payload • Increased range • From their experience with the PET, they determined that they needed an avionics upgrade that would provide the required CNS capabilities to support the daily use of a Dynamic Air Route Planning System (DARP) on their trans-Pacific routes • These airlines approached Boeing and Honeywell in June, 1993, with requirements and constraints for a FANS-1 upgrade to the 747-400 • Must support DARP operation • Must be operational by early 1995 • Airline implementation costs must not outstrip near-term benefits

4. FANS-1 Benefits:Boeing Perspective • Targeted benefits: • Dynamic Air Route Planning System (DARP) • Reduced Separation (Latitudinal/Longitudinal, Vertical and Preferred Tracks) • Avoid crossing track altitude loss • Enhanced ATC communications • More timely altitude changes • Configuration ground rules • Interim ARINC 622 system will have extended lifetime • Maximum FANS-1 benefits requires integration of functions • Message integrity issues must be addressed at the system level

5. Benefits: More Than the Sum of the Parts Main Benefits

6. Recipe for Success

7. Recipe for SuccessBaseline the Expectations • Data link technology is not perfect • Don’t oversell it • Data link cannot provide order of magnitude ATC changes • There is no “big bang” • Must satisfy the accountants as well as the operational and technology proponents • All players must sign up to the risk and inevitable changes

8. Recipe for SuccessProgrammatic Commitment • FAA • Must align accountability, responsibility, authority and funding • Unified vision from top to bottom AND laterally • Empowerment and boundaries must be clear • Leadership in international working groups • Industry • Benefits and schedule must support a business case • All airspace users must be active partners • All providers must be active partners • Both • Partnership and interdependency is essential • Commitments must be preceded by a full understanding of the technical, schedule and funding requirements • ATC service changes must be linked to fleet modifications

9. Recipe for SuccessComplexity of SYSTEMS Integration • ICAO • RTCA • Airlines • Avionics • Contractor • Program Office • Service Provider • Joint Working Group

10. Recipe for SuccessEstablish Industry Interoperability Team • Technical operating environment is not seamless • Standards interpretation varies • Ground and avionics systems have unique limitations • Comm service implementations vary • Operational requirements vary between domains • FIR to FIR variations • Airline to airline variations • Benefit validation and visibility • Levels the playing field • ATM/CNS versus ATM/CNS

11. Recipe for SuccessAcknowledge That Technology is Not Perfect • Recognize that emulating voice with data has limitations and complications • Slower in direct applications • Same type problems probable • Restricts multi-tasking for controllers and pilots • Workload must be weighed against benefits • Must provide distinct advantages for controllers and pilots • Keep it simple

12. Recipe for SuccessPlan for Change • Development paradigm must accommodate change • Recognize that requirements will change with incremental development • Unforeseen problems are a normal part of evolutionary development and should redirect technical efforts, not be considered as failure • Testing is iterative and must be scheduled as such • Legacy systems integration must be adequately scoped • End-to-end systems developer/integrator is essential

13. Recipe for SuccessAppreciate Integration Efforts Into Legacy Operational Environment • Data link technology is the easy part • Integration into Legacy environment is difficult • Must also understand • Legacy systems • Operations • Human Factors • Programmatic/political challenges • Change management • Iterative development • Systems integration

14. Recipe for SuccessNever Underestimate Training • Technology implications must be explained (behind the glass) • Procedures in system training must be complementary and developed together • Incremental implementation adds to training burden and causes proficiency concerns for pilots and controllers • End-to-end training is required to ensure controllers and pilots understand the ramifications of actions on the other end

15. Recipe for SuccessQuality Assurance • Initial operations are only the beginning – follow-up! • Must be candid and include all components • Avionics • Ground automation (all segments) • Comm service (all segments) • Must have non-partisan structure • End-to-end systems perspective • Identify problem and determine which component can best solve it • Track performance for further investment justification • Continuous improvement

16. For More Information… • Nancy Graham, International Technical Representative - Europe, Africa, and Middle East • Brussels, Belgium • E-mail: Nancy.Graham@faa.gov • Terry Moore, Acting Oceanic & Offshore Acting IPT Lead • Washington, DC • E-mail: Terry.Moore@faa.gov • John McCarron, ATOP Product Team Lead • Washington, DC • E-mail: John.McCarron@faa.gov • Kevin Grimm, Oceanic & Offshore Chief Engineer • Washington, DC • E-mail: Kevin.Grimm@faa.gov