KSC Launch Processing System

ABOUT KSC LAUNCH PROCESSING SYSTEM

Despite its name, the Launch Processing System (LPS) was not an onboard avionics computer that flew aboard a rocket. It was a giant, computer-controlled system on the ground at NASA’s Kennedy Space Center (KSC) in Florida that tested, counted down, and launched the Space Shuttle.

Quick facts

• Type: A ground-based, computer-controlled launch system, not flight hardware.
• Location: Housed in the Launch Control Center (LCC), a four-story building attached to the Vehicle Assembly Building (VAB), where the Shuttle was stacked.
• Three subsystems: the Checkout, Control and Monitor Subsystem (the staffed firing-room consoles and computers); the Central Data Subsystem (large computers storing data and procedures, upgraded in 1999 and renamed the Shuttle Data Center); and the Record and Playback Subsystem (which recorded raw data for later study).
• Language: Tests were written in GOAL (Ground Operations Aerospace Language), a NASA-developed high-level test language.
• Scale: Roughly 40 minicomputers ran during a typical launch, with capacity for about 100; each console had on-line disk storage of about five million words.
• People: Needed less than half of the roughly 450 engineers required for an Apollo/Saturn launch.

What it is and how it works

The LPS tied people, computers, and hardware into one automated test-and-control loop. Test engineers sat at consoles (grouped keyboards and displays) in rooms called firing rooms inside the Launch Control Center. Those consoles connected over a data network to minicomputers, and then out to Hardware Interface Modules (HIMs) spread across KSC. A HIM is a remote module that acts as the system’s hands and senses at the actual hardware. They were placed in the Orbiter Processing Facility, the VAB high bays, the launch pads, and various checkout buildings.

The HIMs fed sensor readings back to the computers and sent commands out to the vehicle and ground equipment. Together they tracked thousands of measurements such as temperatures, pressures, flow rates, voltages, and the positions of valves and switches, sampled several times per second. To keep engineers from drowning in data, the LPS used exception reporting: instead of showing every value all the time, it flagged a measurement only when it fell outside its expected limits. Think of it like a smoke detector that stays silent until something is actually wrong, rather than a person staring at every wire. Test procedures written in GOAL let the computers run standardized checks automatically, sequence countdown events, and handle propellant loading and safing.

Why it matters

The LPS was the digital backbone that made fast, repeatable Shuttle processing possible. Apollo-era launches were largely manual and required about 450 engineers in the firing room. By automating most of the Orbiter checkout, along with much of the tank, booster, and engine work, the LPS cut the required staff by more than half and shortened the turnaround between missions. It was designed to process two or more Shuttles at once, supporting the program’s goal of a high flight rate (up to about 12 flights a year). By centralizing thousands of parameters with automatic exception reporting, it improved both safety, by catching problems quickly, and efficiency. Its design also marked a milestone in launch automation that influenced later ground systems.

Where it was used

• Orbiter checkout: The LPS automatically performed the bulk of pre-flight testing on the Orbiter, the most complex element it handled.
• Boosters and tank: It interfaced with the Solid Rocket Boosters (SRBs) and External Tank (ET) during stacking and integration in the VAB.
• Main engines: It tested and monitored the Space Shuttle Main Engines during processing and countdown.
• Propellant loading: During liquid oxygen loading, it monitored on the order of 150 measurements at once while controlling and safing the operation.
• Countdown control: From the firing rooms, it sequenced and monitored countdown events through liftoff for Shuttle missions across the program (1981 to 2011).

A note on the name and the future

The name can be misread as vehicle avionics, but the LPS was firmly a ground system. The Shuttle had its own separate flight computers (the General Purpose Computers) that the LPS simply talked to during checkout. Over time the 1970s-era hardware, such as the Honeywell mainframes in the Central Data Subsystem, needed modernizing; that subsystem became the Shuttle Data Center in 1999. A broader upgrade, the Checkout and Launch Control System (CLCS), aimed to monitor up to about 50,000 measurement changes per second and respond to a dangerous condition in under 20 milliseconds, but NASA canceled it in 2002 after costs rose and the promised savings failed to materialize.

OPERATING PRINCIPLE

VEHICLES USING THIS SYSTEM

SPECIFICATIONS

DETAILED SPECS