Air Traffic Control: Observations on FAA's Modernization Program
Released: 1998-02-26T00:00:00

Letter

Background

As the principal component of the NAS, FAA’s ATC system must operate continuously—24 hours a day, 365 days a year. Under federal law, FAA has primary responsibility for operating a common ATC system—a vast network of radars; automated data processing, navigation, and communications equipment; and traffic control facilities. FAA meets this responsibility by providing such services as controlling takeoffs and landings and managing the flow of air traffic between airports. Users of FAA’s services include the military, other government users, private pilots, and commercial aircraft operators.

Projects in FAA’s modernization program are primarily organized around seven functional areas—automation, communications, facilities, navigation and landing, surveillance, weather, and mission support.

Over the past 16 years, FAA’s modernization projects have experienced substantial cost overruns, lengthy schedule delays, and significant performance shortfalls. To illustrate, the centerpiece of that modernization program—the Advanced Automation System (AAS)—was restructured in 1994 after estimated costs to develop the system tripled from $2.5 billion to $7.6 billion and delays in putting significantly less-than-promised system capabilities into operation were expected to run 8 years or more over original estimates.

FAA Has Fielded Some Equipment but Key Projects Continue to Experience Cost and Schedule Problems

The Congress has appropriated over $25 billion for ATC modernization between fiscal years 1982 and 1998. FAA estimates that it plans to spend an additional $11 billion through fiscal year 2003 on projects in the modernization program.

Of the over $25 billion appropriated to date, FAA has reported spending about $5.3 billion on 81 completed projects and $15.7 billion on about 130 ongoing projects. Of the remaining funds, FAA has reported spending about $2.8 billion on projects that have been cancelled or restructured and $1.6 billion for personnel-related expenses associated with systems acquisition. (See app. I for a list of completed projects.) FAA has fielded some equipment, most recently a new voice communications system. However, delays in other projects have caused the agency to implement costly interim projects. Furthermore, the agency is still having difficulties in acquiring new systems within agreed-to schedule and cost parameters.

New Equipment Is Being Fielded

FAA has been fielding new ATC systems. For example, in February 1997, FAA commissioned the last of 21 Voice Switching and Control System (VSCS) units. As one of the original projects in the 1983 modernization plan, the VSCS project encountered many difficulties during its early years. Since the project was restructured in 1992, FAA has been successful in completing the first phase of the project—installing the equipment into existing en route controller workstations. The second phase is now underway—making VSCS interface with the new display replacement equipment that is being installed in the en route centers.

During the past year, FAA has commissioned 183 additional systems or units of systems. For example, FAA commissioned an additional 97 units for its Automated Surface Observing System, which brings the total of commissioned units to 230 out of 597 that are planned. (See app. II for details on the implementation status of 17 major ongoing modernization projects and app. III for data on changes in their cost and schedules.)

Delays Have Led to Costly Interim Projects

Problems with modernization projects have caused delays in replacing FAA’s aging equipment, especially the automation equipment in the en route and terminal facilities. We found that FAA has added four interim projects—three for the TRACONs and one for the en route centers—reported to cost about $655 million—to sustain and enhance current automated air traffic control equipment. FAA began its first program for the TRACONs in 1987 and expects to complete its third program in 2000. In general, these programs provide new displays and software and upgrade hardware and data-processing equipment to allow TRACONs to handle increased traffic. One program for the en route centers—the Display Complex Channel Rehost—was completed in 1997. Under this program, FAA transferred existing software from obsolete display channel computers to new more reliable and maintainable computers at five en route centers.

The cost for interim projects could go even higher if FAA decides to implement an interim solution to overcome hardware problems and resolve year 2000 date requirements with the Host computer system. FAA is assessing the Host computer’s microcode—low-level machine instructions used to service the main computer—with a plan to resolve any identified year 2000 date issues, while at the same time preparing to purchase and implement new hardware—Interim Host—for each of its 20 en route centers before January 1, 2000. FAA expects to incur costs of about $160 million during fiscal years 1998 and 1999 for the Interim Host.

Major Acquisitions Continue to Face Delays and Cost Increases

Two key components of the modernization effort—the Wide Area Augmentation System (WAAS) and the Standard Terminal Automation Replacement System (STARS)—have encountered delays and cost increases.

In September 1997, FAA estimated total life cycle costs for WAAS at $2.4 billion ($900 million for facilities and equipment and $1.5 billion for operations). In January 1998, the estimate had increased by $600 million to $3 billion ($1 billion for facilities and equipment and $2 billion for operations). The increased costs for facilities and equipment are attributable to FAA’s including previously overlooked costs for periodically updating WAAS’ equipment. The revised cost estimate for operations and maintenance is largely attributable to higher than expected costs to lease geostationary satellites.

In developing WAAS, FAA has also encountered delays. When signing the original development contract with Wilcox Electric in August 1995, FAA planned for the initial system to be operational by December 1997. Because of concerns about the contractor’s performance, however, FAA terminated the original contract and signed a development contract with Raytheon (formerly Hughes Aircraft) in October 1996 that called for the initial system to be operational by April 1999. The 16-month schedule slippage was caused by problems with the original contractor’s performance, design changes, and increased software development.

Last year, we reported that the implementation of STARS—particularly at the three facilities targeted for operating the system before fiscal year 2000—will likely be delayed if FAA and its contractor experience any difficulties in developing the software. These difficulties have materialized. In January 1998, FAA reported that more delays are likely because software requirements could increase to resolve air traffic controllers’ dissatisfaction with the system’s computer-human interface.

FAA also reported an unexpected cost increase of $35 million for STARS during fiscal year 1998. It attributed the increase to such factors as adding resources to maintain the program’s schedule and the effects of any design changes to address new computer-human interface concerns. Also, the estimated size of software development—measured in source lines of code—is now 50 percent larger than the original November 1996 estimate. FAA has requested a reprogramming of fiscal year 1998 funds to address this cost increase.

FAA Has Begun to Implement Recommendations to Correct Root Causes of Modernization Problems

Our reviews have identified some of the root causes of long-standing problems with FAA’s modernization and have recommended solutions to them. Among the causes of these problems were the lack of a complete and enforced systems architecture, unreliable cost information, lack of mature software acquisition processes, and an organizational culture that did not always act in the agency’s long-term best interest. While FAA has begun to implement many of our recommendations, it will need to stay focused on continued improvement.

A Complete Systems Architecture Is Key to Guiding and Constraining ATC Modernization Investments

FAA has proceeded to modernize its many ATC systems without the benefits of a complete systems architecture, or overall blueprint, to guide their development and evolution. In February 1997, we reported that FAA has been doing a good job of defining one piece of its architecture—the logical architecture. That architecture describes FAA’s concept of operations, business functions, high-level descriptions of information systems and their interrelationships, and information flows among systems. This high-level architecture will guide the modernization of FAA’s ATC systems over the next 20 years. We identified shortcomings in two main areas. FAA’s system modernization lacked a technical architecture and an effective enforcement mechanism.

FAA generally agreed with the recommendation in our February 1997 report to develop a technical architecture and has begun the task. We will continue to monitor FAA’s efforts. Also, to be effective, the architecture must be enforced consistently. FAA has no organizational entity responsible for enforcing architectural consistency. Until FAA defines and enforces a complete ATC systems architecture, the agency cannot ensure compatibility among its existing and future programs.

We also recommended in the February 1997 report that FAA develop a management structure for enforcing the architecture that is similar to the provisions of the Clinger-Cohen Act of 1996 for department-level Chief Information Officers (CIO). FAA disagrees with this recommendation because it believes that the current location of its CIO, within the research and acquisition line of business, is effective. We continue to believe that such a structure is necessary. FAA’s CIO does not report directly to the Administrator and does not have organizational or budgetary authority over those who develop ATC systems or the units that operate and maintain them. Furthermore, the agency’s long history of problems in managing information technology projects reflects weaknesses in its current structure.

Reliable Cost Information Is Needed to Effectively Manage Modernization Projects

In January 1997, we reported that FAA lacks reliable cost-estimating processes and cost-accounting practices needed to effectively manage investments in information technology, which leaves it at risk of making ill-informed decisions on critical multimillion, even billion, dollar air traffic control systems. Without reliable cost information, the likelihood of poor investment decisions is increased, not only when a project is initiated, but also throughout its life cycle. We recommended that FAA improve its cost-estimating processes and fully implement a cost-accounting system.

Our recent review of the reliability of FAA’s reported financial information and the possible program and budgetary effects of reported financial statement deficiencies again highlights the need for reliable cost information. The audit of FAA’s 1996 financial statement disclosed many problems in reporting of operating materials and supplies and property and equipment. Many of these problems resulted from the lack of a reliable system for accumulating project cost accounting information. Although FAA has begun to institutionalize defined cost-estimating processes and to acquire a cost-accounting system, it will be awhile before FAA and other decisionmakers have accurate information to determine and control costs.

A Mature Software Acquisition Capability Is Important to the Success of FAA’s ATC Modernization Program

In March 1997, we reported that FAA’s processes for acquiring software—the most costly and complex component of ATC systems—are ad hoc, sometimes chaotic, and not repeatable across projects. As a result, FAA is at great risk of acquiring software that does not perform as intended and is not delivered on time and within budget. Furthermore, FAA lacks an effective approach for improving its processes for acquiring software.

In the March 1997 report, we recommended that FAA improve its software acquisition capabilities by institutionalizing mature acquisition processes and reiterated our prior recommendation that FAA establish a management structure similar to the department-level CIOs to instill process discipline. FAA concurred with part of our recommendation and has initiated efforts to improve its software acquisition processes. These efforts, however, are not comprehensive, are not complete, and have not yet been implemented agencywide. Furthermore, FAA disagrees with our recommendation related to its management structure. Without establishing strong software acquisition processes and an effective management structure, FAA risks making the same mistakes it did on failed systems acquisition projects.

Continued Management Attention Is Critical to Comprehensive Cultural Change

In August 1996, we reported that an underlying cause of FAA’s ATC acquisition problems is its organizational culture—the beliefs, the values, and the attitudes and expectations shared by an organization’s members that affect their behavior and the behavior of the organization as a whole.We found that FAA’s acquisitions were impaired when employees acted in ways that did not reflect a strong commitment to mission focus, accountability, coordination, and adaptability. We recommended that FAA develop a comprehensive strategy for cultural change that (1) addresses specific responsibilities and performance measures for all stakeholders throughout FAA and (2) provides the incentives needed to promote the desired behaviors and achieve agencywide cultural change.

In response to our recommendations, FAA issued a report outlining its overall strategy for changing its acquisition culture and describing its ongoing actions to influence organizational culture and improve its life cycle acquisition management processes. For example, the Acquisition and Research (ARA) organization has proposed restructuring its personnel system to tie pay to performance based on 15 measurable goals, each with its own performance plan. ARA’s proposed personnel system is under consideration by the Administrator.

In our August 1996 report, we also noted that the Integrated Product Development System, based on integrated teams, was a major FAA initiative to address the shortcomings with its organizational culture. According to an ARA program official, FAA has 15 integrated product teams, the majority of which have approved plans. The official indicated that all team members have received training to prepare them for their roles and that ARA is developing a set of standards to measure the performance of the integrated teams. However, the official also acknowledged that FAA has had difficulty in gaining commitment to the integrated team concept throughout the agency because offices outside of ARA have been resistant to integrated teams.

To help overcome institutional cultural barriers, FAA and external stakeholders have been discussing the establishment of a special program office responsible for the acquisition of free flight systems. Although, the details of how such an office would operate have not been put forward, one option would be for this office to have its own budget and the authority to make certifications and regulations and to determine system requirements. Such an office could be viewed as the evolutionary successor to the integrated product team system. Another approach being considered by FAA is the establishment of a single NAS manager at the level of associate administrator to eliminate traditional “stovepipes” between the acquisition and air traffic organizations.

As FAA considers recommendations to create a new structure, we believe that it would be advantageous for FAA to implement our recommendation to create a management structure similar to the department-level CIO as called for in the Clinger-Cohen Act. Having an effective CIO, with the organizational and budgetary authority to implement and enforce a complete, agencywide systems architecture would go a long way towards eliminating traditional “stovepipes” between integrated product teams, as well as between the acquisition and air traffic organizations. Furthermore, the agency could gain valuable insight from the experiences of other organizations that have implemented similar structures. Regardless of future direction, FAA recognizes that considerable work is needed to modify behaviors and create comprehensive cultural change. A continued focus on cultural change initiatives will be critical in the years ahead.

FAA Is Revising the Modernization Program and Implementing Acquisition Reform but Faces New Challenges

While FAA is involving external and internal stakeholders in revising its approach to the modernization program, it will need to stay focused on implementing solutions to the root causes of past problems, ensure that all aspects of its acquisition management system are effectively implemented, and quickly address the looming crisis with the year 2000 date requirements.

FAA Is Seeking Consensus From Stakeholders on an Achievable Modernization Program

The FAA Administrator has begun an outreach effort with the aviation community to build consensus on and seek commitment to the future direction of the agency’s modernization program. Similar to our findings on the logical architecture, a review of this program by the NAS Modernization Task Force concluded that the architecture under development builds on the concept of operations for the NAS and identifies the programs needed to meet the needs of the user community. However, the task force found that the architecture is not realistic because of (1) an insufficient budget; (2) the preponderance of risks associated primarily with certifying and deploying new equipment and with users’ cost to acquire equipment; and (3) unresolved institutional issues and a lack of user commitment.

The task force recommended a revised approach that would be less costly and would be focused more on providing near-term user benefits. Under this revised approach, FAA would (1) implement a set of core technologies to provide immediate user benefits; (2) modify the Flight 2000 initiative to address critical risk areas associated with key communications, navigation, and surveillance programs; and (3) proceed with implementing critical time-driven activities related to the Host computer and the year 2000 problems and with implementing such systems as STARS, surveillance radars, and en route displays to replace aging infrastructure.

The details on how FAA intends to implement the task force’s recommendations are not yet known. However, from our discussions with task force officials, their practical effect would be that the development and the deployment of some current programs would be accelerated while others would be slowed down. Meanwhile, FAA would continue developing programs like STARS and the Display System Replacement and work to ensure that its computers recognize the year 2000. For example, under the revised approach, the WAAS program would be slowed down after Phase I, which is scheduled to provide initial satellite navigation capabilities by 1999, to enable FAA to resolve technical issues and explore how costs could be reduced. Further development would be subject to review and risk mitigation under the expanded Flight 2000 initiative.

FAA faces both opportunities and challenges as it revises the modernization program. On the one hand, FAA has an opportunity to regain user confidence by delivering systems that benefit them. On the other hand, FAA is challenged to follow through with its investment management process improvements. We urge FAA to proceed cautiously as it attempts to expedite the deployment of key technologies to avoid repeating past practices, such as undue concern for schedules at the expense of disciplined systems development and careful, thorough testing. FAA will need to resist this temptation, as the results are typically systems that cost more than expected, are of low quality, and are late as well.

FAA Will Need to Continue Improving Its Acquisition Management Process

Concerned that burdensome procurement rules were a primary contributor to FAA’s acquisition problems, the Congress exempted FAA from many procurement rules. In response, the agency implemented its Acquisition Management System (AMS) on April 1, 1996, to improve its acquisition of new technology.

AMS is intended to provide high-level acquisition policy and guidance and to establish rigorous investment management practices. We are currently reviewing FAA’s investment management approach, including its practices and processes for selecting, controlling, and evaluating projects, and expect to report later this year. As FAA continues to implement AMS and embarks on a revised modernization approach, it will need to establish baselines for individual projects and performance measurements to track key goals.

Under AMS, an acquisition project should have a baseline, which establishes the performance, life-cycle cost, schedule, and benefit boundaries within which the program is authorized to operate. Having an effective investment analysis capability is important in developing these baselines. In its May 1997 report on AMS, FAA noted that it has focused more attention on investment management analyses. The agency reported that it has established several investment analysis teams of individuals with expertise in such areas as cost estimating, market analysis, and risk assessment to help prepare program baselines to use in determining the best way to satisfy mission needs.

Although FAA has begun efforts to establish new baselines for projects that were underway prior to AMS, program evaluation officials question the availability and the quality of operations and maintenance data that are being used to estimate life-cycle project costs. FAA’s history of unplanned cost increases, most recently seen with its STARS and WAAS programs, coupled with past deficiencies in cost estimating processes and practices point to the need to use reliable and complete data to establish realistic baselines.

As for performance measurements, FAA does not have a unified effort underway to effectively measure progress toward achieving acquisition goals. FAA has established a goal to reduce the time to field systems by 50 percent and to reduce the cost of acquisitions by 20 percent during the first 3 years under AMS. FAA also plans to measure performance in such other critical areas as customer satisfaction and the quality of products and services. According to FAA’s evaluation, while individual organizations are attempting to measure progress in meeting the two goals, a coordinated agencywide measurement effort is lacking.

FAA’s failure to field systems on time and within cost indicates the need for a comprehensive system of performance measurements that can help provide systematic feedback about accomplishments and progress in meeting mission objectives. The need for such measurements will become even more critical as FAA expedites the deployment of some projects.

Clearly identified performance measurements will help FAA, the Congress, and system users assess how well the agency achieves its goals.

Urgent Action Needed to Ensure Computers Recognize the Year 2000

On January 1, 2000, computer systems worldwide could malfunction or produce inaccurate information simply because the century has changed. Unless corrected, such failures could have a costly, widespread impact. The problem is rooted in how dates are recorded and computed. For the past several decades, systems have typically used two digits to represent the year, such as “97” for 1997, to save electronic storage space and reduce operating costs. This practice, however, makes 2000 indistinguishable from 1900, and the ambiguity could cause systems to malfunction in unforeseen ways or to fail completely.

FAA’s challenge is great. Correcting this problem will be difficult and expensive, and must be done while such systems continue to operate. In less than 2 years, hundreds of computer systems that are critical to FAA’s operations, such as monitoring and controlling air traffic, could fail to perform as needed unless proper date-related calculations can be made.

FAA’s progress in making its systems ready for the year 2000 has been too slow. We have reported that, at its current pace, it will not make it in time. The agency has been severely behind schedule in completing basic awareness and assessment activities—critical first and second phases in an effective year 2000 program. For example, just this month FAA appointed a program manager who reports to the Administrator.

Delays in completing the first two phases have left FAA little time for critical renovation, validation, and implementation activities—the final three phases in an effective year 2000 program. With less than 2 years left, FAA is quickly running out of time, making contingency planning for continuity of operations even more critical.

If critical FAA systems are not year 2000 compliant and ready for reliable operation on January 1 of that year, the agency’s capability in several areas—including the monitoring and controlling of air traffic—could be severely compromised. The potential serious consequences could include degraded safety, grounded or delayed flights, increased airline costs, and customer inconvenience. We have made a number of recommendations aimed at expediting the completion of overdue awareness and assessment activities.

Mr. Chairman, this concludes my statement. We will be happy to answer any questions from you or any Member of the Subcommittee.

Modernization Projects Completed Through August 1998

Automated Radar Terminal System (ARTS) IIIA Assembler (22-02)

Additional ARTS IIIA at FAA Technical Center (22-05)

Consolidated Notice to Airmen System (23-03)

Visual Flight Rules Air Traffic Control Tower Closures (22-14)

Altitude Reporting Mode of Secondary Radar (Mode-C) (21-10)

Enhanced Target Generator Displays (ARTS III) (22-03)

National Airspace Data Interchange Network IA (25-06)

Hazardous In Flight Weather Advisory Service (23-08) (continued)

En Route Automated Radar Tracking System Enhancements (21-04)

Sustain New York Terminal Radar Approach Control (TRACON) (22-18)

National Radio Communication System (26-14)

Direct Access Radar Channel System (21-03)

National Airspace Data Interchange Network II (25-07)

Modernization of Unmanned FAA Buildings and Equipment (26-08)

Large Airport Cable Loop Systems (26-05)

Interfacility Data Transfer System for Edwards Air Force Base Radar Approach Control (35-20)

Acquisition of Flight Service Facilities (26-10) (continued)

Radar Pedestal Vibration Analysis (44-43)

Low-Level Wind Shear Alert System (23-12)

Brite Radar Indicator Tower Equipment (22-16)

National Implementation of the “Imaging” Aid for Dependent Converging Runway Approaches (62-24)

Integrated Communications Switching System (23-13)

System Engineering and Integration Contract (26-13)

National Airspace Data Interchange Network II Continuation (35-07)

Instrument Landing System and Visual Navaids Engineering and Sparing (44-24)

Oceanic Display and Planning System (21-05)

Integrated Communications Switching System Logistics Support (43-14)

Replacement of Controllers Chairs (42-24)

ARTS IIIA-Expand 1 Capacity and Provide Mode C Intruder Capability (32-20) (continued)

Civil Aviation Registry Modernization (56-24)

Precision Automated Tracking System (56-16)

National Airspace Integrated Logistic Support (56-58)

Long Range Radar Radome Replacement (44-42)

Installed at en route centers to allow processing of existing air traffic control software on new equipment.

Project comprised a variety of tower and terminal replacement and modernization projects. Project was continued in the Capital Investment Plan under projects 42-13 and 42-14.

Also known as the Radio Communications Link project, it was designed to convert aging “special purpose” Radar Microwave Link System into a “general purpose” system for data, voice, and radar communications among en route centers and other major FAA facilities.

Project was activated to sustain and upgrade air traffic control operations and acquire eight terminal radars awaiting the full implementation of the Advanced Automation System.

Project comprised a variety of diverse support projects and has been continued in the Capital Investment Plan under Continued General Support (46-16).

Status of FAA’s Major Modernization Projects

Over the past decade, we have reported on FAA’s progress in meeting schedule commitments for last-site implementation, which signals completion of the project. Prior to this year, we have used the dates from the 1983 NAS modernization plan. This year, after discussions with FAA officials, we are measuring FAA’s progress against an interim date—which in most cases represents the date of contract award or investment decision. We will continue to show the original date, but will only measure progress against the interim date.

57 TDLS I57 TDLS IIStage 0: 21 Stage 1 and 2: 21 0 TDLS is the Tower Data Link Services. TDLS I (Predeparture Clearance/Flight Data Input/Output CRT/Rank Emulation) has been commissioned at all 57 sites; TDLS II (Digital-Automatic Terminal Information Service) has been installed at all 57 sites and commissioned at 48 sites.

The first copy of each GAO report and testimony is free. Additional copies are $2 each. Orders should be sent to the following address, accompanied by a check or money order made out to the Superintendent of Documents, when necessary. VISA and MasterCard credit cards are accepted, also. Orders for 100 or more copies to be mailed to a single address are discounted 25 percent.

U.S. General Accounting Office P.O. Box 37050 Washington, DC 20013 Room 1100 700 4th St. NW (corner of 4th and G Sts. NW) U.S. General Accounting Office Washington, DC Orders may also be placed by calling (202) 512-6000 or by using fax number (202) 512-6061, or TDD (202) 512-2537.

Each day, GAO issues a list of newly available reports and testimony. To receive facsimile copies of the daily list or any list from the past 30 days, please call (202) 512-6000 using a touchtone phone. A recorded menu will provide information on how to obtain these lists.