Defense Acquisitions:

Significant Challenges Ahead in Developing and Demonstrating Future Combat System's Network and Software

GAO-08-409: Published: Mar 7, 2008. Publicly Released: Mar 7, 2008.

Additional Materials:

Contact:

Michael J. Sullivan
(202) 512-2811
contact@gao.gov

 

Office of Public Affairs
(202) 512-4800
youngc1@gao.gov

The Army's Future Combat System (FCS) requires a software-based advanced information network to meld people, sensors, and weapons into a cohesive fighting force. As software controls 95 percent of FCS's functionality, it determines the success or failure of the program. The Army contracted with the Boeing Company as a lead systems integrator (LSI) to define, develop and integrate FCS, including software development. GAO must by law report annually on FCS. This is one of two reports to meet this requirement. It addresses risks facing the development of network and software, the practices being used to manage software, and the timing of key network demonstrations. In conducting our work, GAO has contacted numerous DOD, Army, and contractor offices; reviewed technical documents on software and network development and plans; attended meetings; and spoken to Army and other officials on various aspects of FCS network and software development. GAO also performed detailed work at five FCS software developers.

Almost 5 years into the program, it is not yet clear if or when the information network that is at the heart of the FCS concept can be developed, built, and demonstrated by the Army and LSI. Significant management and technical challenges have placed development of the network and software at risk. These risks include, among others, network performance and scalability, immature network architecture, and synchronization of FCS with Joint Tactical Radio System and Warfighter Information Network Tactical programs that have significant technical challenges of their own. Software being developed for the network and platforms is projected to total 95.1 million lines of computer code, almost triple the size since the program began in 2003. FCS's software is about four times larger than the next two largest software-intensive defense programs. Although several disciplined practices are being used to develop FCS's network and software, the program's immaturity and aggressive pace during development have delayed requirements development at the software developer level. For example, software developers for 5 major software packages that GAO reviewed report that high-level requirements provided to them were poorly defined, late, or omitted in the development process. This caused the software developers to do rework or defer functionality out to future builds. In turn, these poor or late requirements had a cascading effect that caused other software development efforts to be delayed. It is unclear when or how it can be demonstrated that the FCS network will work as needed, especially at key program junctures. For example, in 2009, network requirements, including software, may not be adequately defined nor designs completed at the preliminary design review; and at the FCS milestone review later that year, network demonstration is expected to be very limited. The first major FCS network demonstration--the limited user test in 2012--will take place at least a year after the critical design review and only a year before the start of FCS production. That test will seek to identify the impact of the contributions and limitations of the network on the ability to conduct missions. This test will be conducted after the designs have been set for the FCS ground vehicles, which poses risks because the designs depend on the network's performance. A full demonstration of the network with all of its software components will not be demonstrated until at least 2013 when the fully automated battle command system is expected to be ready.

Recommendations for Executive Action

  1. Status: Closed - Not Implemented

    Comments: DOD concurred with this recommendation and stated that the FCS program would finalize and release network and software requirements prior to each build. However, in 2009, DOD decided to terminate major portions of the FCS program and to execute the remaining portions, including the network, in drastically different ways. Hence, this recommendation is no longer applicable.

    Recommendation: The Secretary of Defense should direct the FCS program to stabilize network and software requirements on each software build to enable software developers to follow disciplined software practices, including having realistic and synchronized test schedules.

    Agency Affected: Department of Defense

  2. Status: Closed - Not Implemented

    Comments: DOD concurred with this recommendation and stated that they would establish criteria for each of the key program events. However, in 2009, DOD decided to terminate major portions of the FCS program and to execute the remaining portions, including the network, in drastically different ways. Hence, this recommendation is no longer applicable.

    Recommendation: The Secretary of Defense should establish a clear set of criteria for acceptable network performance at each of the key program events including the 2009 milestone review, platform and system-of-system critical design reviews, major network demonstration in 2012, and Milestone C for core FCS program.

    Agency Affected: Department of Defense

  3. Status: Closed - Not Implemented

    Comments: DOD concurred with this recommendation and stated that expectations for the 2009 milestone review would include an analysis of network technical feasibility and risks. However, in 2009, DOD decided to terminate major portions of the FCS program and to execute the remaining portions, including the network, in drastically different ways. Hence, this recommendation is no longer applicable.

    Recommendation: The Secretary of Defense should, in setting expectations for the 2009 milestone review, include a thorough analysis of network technical feasibility and risks.

    Agency Affected: Department of Defense

  4. Status: Closed - Not Implemented

    Comments: DOD concurred with this recommendation and stated that manned ground vehicle and network development and demonstration would be synchronized in the areas where there are interfaces and interdependencies. However, DOD has subsequently decided to restructure the FCS program and this recommendation is no longer applicable.

    Recommendation: The Secretary of Defense should, in setting expectations for the 2009 milestone review, include sysnchronization of network development and demonstration with that of other elements of FCS such as the manned ground vehicles.

    Agency Affected: Department of Defense

  5. Status: Closed - Not Implemented

    Comments: DOD concurred with this recommendation and stated that the 2009 Milestone Review would evaluate the network and software cost estimates and cost risks identified for development, integration, and testing of the FCS network and software. However, DOD has subsequently decided to restructure the FCS program and this recommendation is no longer applicable.

    Recommendation: The Secretary of Defense should, in setting expectations for the 2009 milestone review, include a reconciliation of the differences between independent and Army estimates of network and software development scope and cost.

    Agency Affected: Department of Defense

 

Explore the full database of GAO's Open Recommendations »

Jan 21, 2021

Jan 19, 2021

Jan 14, 2021

Jan 12, 2021

Dec 10, 2020

Dec 2, 2020

Nov 20, 2020

Nov 19, 2020

Looking for more? Browse all our products here