Space Defense: Management and Technical Problems Delay Operations Center Acquisition
IMTEC-89-18
Published: Apr 20, 1989. Publicly Released: Apr 20, 1989.
Skip to Highlights
Highlights
In response to a congressional request, GAO assessed the Air Force's progress in acquiring the first two blocks of its Space Defense Operations Center (SPADOC) modernization program, focusing on: (1) why Block A, intended to provide the hardware and software for automating the assessment of foreign activities affecting U.S. satellites, did not meet Air Force requirements and was significantly behind schedule; (2) whether Block B development, intended to improve space surveillance by making orbital position predictions for 400 satellites, could correct Block A problems; and (3) how effectively the Air Force managed the program.
Recommendations
Matter for Congressional Consideration
| Matter | Status | Comments |
|---|---|---|
| Congress should withhold further funding for the SPADOC acquisition until the Defense Acquisition Board (DAB) has submitted, and the Secretary of Defense has approved, program plans. | Congress did not withhold program funding. |
Recommendations for Executive Action
| Agency Affected | Recommendation | Status |
|---|---|---|
| Department of Defense | Due to the mission-critical nature of the SPADOC project, its high cost, its developmental difficulties, and its history of ineffective Air Force management, the Secretary of Defense should halt Block B development until the Air Force has complied with congressional requirements to submit North American Aerospace Defense Command modernization programs, including SPADOC, to DAB review. |
The Secretary allowed development to continue while it prepared for DAB review.
|
| Department of the Air Force | The Secretary of the Air Force should specifically submit to DAB recommendations on the ultimate disposition of the SPADOC Block A system. If the Secretary recommends continuing to use Block A as an interim improvement over the current, primarily manual system, these plans should include: (1) an evaluation of the capabilities and deficiencies of the Block A system as accepted; (2) an assessment of the incremental costs and benefits of changes and modifications required to make the system fully operational; and (3) recommendations on how Block A should be used based on careful analysis of costs incurred and benefits derived. |
The Air Force presented information related to this recommendation to DAB in September 1989. DAB approved the Air Force's approach on October 25, 1989.
|
| Department of the Air Force | The Secretary of the Air Force should specifically submit to DAB plans for the future SPADOC system. These plans should include a thorough analysis of the requirements for SPADOC and the feasibility of satisfying those requirements, in particular controlled mode security. Plans should also include identification and analysis of alternative technical and contractual approaches to meeting the requirements, and well-founded estimates of costs and benefits of the alternative approaches. |
The Air Force presented information related to this recommendation to DAB in September 1989. DAB approved the Air Force's approach on October 25, 1989.
|
Full Report
Public Inquiries
Topics
IT acquisitionsAir defense systemsAir Force procurementCost overrunsManagement information systemsMilitary satellitesProduct evaluationProgram managementSystems evaluationWarning systems