Viewing page 55 of 172

This transcription has been completed. Contact us with corrections.

3.  Middeck payload changes can be done for prepacked payloads. Some reflight payloads might be possible while first flight payloads are very questionable.

Since the KSC processing is at the "end of the line" for implementing changes, difficulties usually occur late in the process (L-5 month timeframe and during actual hardware processing).  The prevailing "can do" response results in impacts to budgets and manpower planning.  Late changes usually result in high overtime for some KSC personnel, some of which are already supporting a 7 day/week schedule.  Another significant impact is the shortening of the review cycle for the work authorization paperwork for hands-on personnel.

An additional source of problems in KSC Orbiter processing is longer, non-standard processing flows that do not fit the standard template for Orbiter processing (normally starts at L-2 months) and payload processing.  This causes KSC to absorb the extra work created when products are delivered according to the standard template.  Non-standard flows include DOD, Spacelab, and Centaur missions.  Another source is the requirement to absorb the workload bow-wave from launch delays of one or more missions to preserve a fixed launch date for an upcoming mission; i.e., Halley's comet rendezvous, STS 61-E.

3.  Flight Preparation Major Milestone History

a.  Overview of the Reconfiguration Process

The mission operations reconfiguration process is the means by which the JSC MOD builds the products required for support of a particular flight.  The products of significance include a flight-unique Mission Control Center release ("MCC"), a flight-unique Shuttle Mission Simulator release ("SMS"), a flight-unique Orbiter flight software release ("MMU"), a flight-unique crew activity plan, and flight-unique crew training.  (Refer to figure 12.)

The previously described products are built from requirements identified by the user community, which includes both the STS and the payload (customer).  These requirements are provided through standardized processes which will not be addressed here.  It should be noted, however, that the reconfiguration process is heavily dependent on receipt of these requirements in mature form at the specified need dates to enable production of the end products on time.  One of the most significant requirements with which the reconfiguration process must deal is the manifesting of the major payloads in the cargo bay.

The mission operations reconfiguration process is performed through several subelements (or "workstations").  Each workstation has distinct functions to perform leading to the major end products discussed previously.  Although the process is serial to a large degree, considerable interaction and coordination among all workstations is necessary throughout the process to ensure that all areas are working to the same baseline schedules.

-91-