Return to Human Space Flight home page

KSC- Checkout and Launch Control System (CLCS)

Problem: Costs to operate and maintain the aging Launch Processing System (LPS) at Kennedy Space Center have been escalating. Increasing obsolescence of equipment will continue to drive costs upward and degrade reliability. LPs system architecture and antiquated software prevents flexibility and expansion to support Shuttle upgrades.
Solution: CLCS will replace the current Launch Processing System with state-of the art technology, redefining the Space Shuttle processing environment to improve checkout efficiencies, and providing the building blocks for future endeavors.

The CLCS Project is a NASA managed, re-engineering activity, with contractor support provided under existing NASA contracts to capitalize on available expertise.

Initial Operation Date: CLCS has an aggressive, success driven, product oriented, five-year schedule with deliveries to the end user every six months. Each incremental delivery provides an additional system capability that is built on top of the previously delivered.
Technology Goal:
  • Improve system reliability and supportability
  • Increase mean time between failures from 70 to 10,000 hours
  • Utilize state-of -the-art COTS systems
  • Reduce system complexity
  • Reduce custom software from 12 million lines of code to 3.3 million
  • Utilize open system architecture
  • Design for system components to be returned to vendor while maintaining 100% support capability
  • Reduce programmatic risk of delivering flawed systems
  • Utilize available expertise from LPs and MCC systems development operation, and maintenance
  • Leverage technology from MCC and other similar checkout and control systems
  • Utilize independent verification and validation (IV&V;) to assure quality of processes and reduce the risk of flawed software and hardware
  • Reduce procedural complexity and associated risk of procedural errors
  • Reduce control room paper documentation by 50%
  • Utilize 50% fewer engineers on console for daily power up operations
  • Redefine Shuttle processing environment to improve checkout efficiencies, e.g.
  • Separate command and monitor data
  • Provide multi-discipline testing from a single console
  • Provide multi-orbiter control from a single control room
  • Provide local command and consolidated data capability
  • Develop a system that is readily adaptable to other applications
  • To support payload checkout function, including Space Station
  • To support future space vehicles
  • To support Moon and Mars ground based applications for Lunar/Mar
Goals Supported: 1) Fly Safely
2) Meet the Manifest
3) Improve Supportability
4) Reduce Cost


Curator: Kim Dismukes | Responsible NASA Official: John Ira Petty | Updated: 04/07/2002
Web Accessibility and Policy Notices