ATTACHMENT J-1

**SPACE FLIGHT OPERATIONS CONTRACT**

**SCOPE OF WORK**

**ATTACHMENT J-1-A**

**SPACE FLIGHT OPERATIONS CONTRACT**

**STATEMENT OF WORK**

1.0 SPACE FLIGHT OPERATIONS CONTRACT

1.1 PROGRAM AND BUSINESS MANAGEMENT

1.1.1 PROGRAM MANAGEMENT

1.1.1.1 PLANNING

1.1.1.2 MANAGEMENT REVIEWS

1.1.1.2.1 CONTRACT MANAGEMENT REVIEWS

1.1.1.2.2 PROGRAM REVIEWS

1.1.1.2.3 FLIGHT READINESS

1.1.1.3 RESERVED

1.1.1.4 RISK MANAGEMENT

1.1.1.5 NEW TECHNOLOGY

1.1.2 FINANCIAL RESOURCES AND PERFORMANCE MANAGEMENT

1.1.2.1 FINANCIAL RESOURCES MANAGEMENT

1.1.2.2 PERFORMANCE MEASUREMENT

1.1.3 CONTRACT MANAGEMENT

1.1.3.1 PRIME CONTRACT MANAGEMENT

1.1.3.2 SUBCONTRACT MANAGEMENT 6

1.1.4 INFORMATION AND DOCUMENT MANAGEMENT

1.1.4.1 INFORMATION MANAGEMENT

1.1.4.2 DOCUMENT MANAGEMENT 7

1.1.4.3 YEAR 2000 COMPLIANCE

1.1.5 CONFIGURATION AND VERIFICATION MANAGEMENT

1.1.5.1 CONFIGURATION MANAGEMENT

1.1.5.2 VERIFICATION MANAGEMENT

1.1.6 GOVERNMENT FACILITY, PROPERTY AND SECURITY MANAGEMENT

1.1.6.1 FACILITY MANAGEMENT

1.1.6.2 PROPERTY MANAGEMENT

1.1.6.3 SECURITY AND TECHNOLOGY PROTECTION MANAGEMENT

1.1.7 MANIFESTS AND SCHEDULES

1.2 SYSTEM AND CARGO INTEGRATION

1.2.1 ENGINEERING

1.2.1.1 POST FLIGHT ANALYSIS

1.2.1.2 ASCENT MARGINS ASSESSMENT

1.2.1.3 CARGO INTEGRATION ENGINEERING ANALYSIS

1.2.1.4 CARGO INTEGRATION HARDWARE

1.2.1.5 CONFIGURATION ENGINEERING

1.2.1.6 LAUNCH SYSTEMS EVALUATION ADVISORY TEAM (LSEAT) CONFIGURATION
AND DATABASE MAINTENANCE

1.2.1.7 RESERVED

1.2.2 INTEGRATION

1.2.2.1 INTEGRATED MASS PROPERTIES

1.2.2.2 TRAJECTORY DESIGN DATA PACKAGES (TDDP)

1.2.2.3 FLIGHT DESIGN INTEGRATION

1.2.2.4 ENGINEERING INTEGRATION PLAN (PIP) ANNEXES

1.2.2.5 ELEMENT INTERFACE CONTROL DOCUMENT (ICD)

1.2.2.6 PAYLOAD UNIQUE ICD's

1.2.2.7 PAYLOAD OMRS TEST REQUIREMENTS

1.2.2.8 TECHNICAL INTEGRATION ANALYSIS

1.2.2.9 RESERVED

1.2.2.10 INTEGRATED AVIONICS

1.2.2.11 SSV DATABOOKS 21

1.2.3 PROJECT INTEGRATION LIAISON

1.2.4 RESERVED

1.3 SAFETY, MISSION ASSURANCE AND PRODUCT AWARENESS 23

1.3.1 SAFETY

1.3.1.1 SYSTEMS SAFETY

1.3.1.2 OPERATIONS SAFETY

1.3.2 RELIABILITY AND MAINTAINABILITY

1.3.3 QUALITY ASSURANCE

**1.3.3.1 PRODUCT AND SERVICE QUALITY**

**1.3.3.2 PROCESS QUALITY**

1.4 FLIGHT ELEMENTS

1.4.1 ORBITER

1.4.1.1 MISSION AND TURNAROUND REQUIREMENTS

> 1.4.1.1.1 MEDS OPERATIONAL SUPPORT 34
>
> 1.4.1.1.2 MEDS OEM HARDWARE ENGINEERING SUPPORT 34

1.4.1.2 ORBITER LOGISTICS

1.4.1.3 ORBITER TURNAROUND PROCESSING

1.4.1.4 ORBITER FERRY OPERATIONS

1.4.1.5 ORBITER HARDWARE PRODUCTION

1.4.1.5.1 RESERVED.

1.4.1.5.2 HARDWARE, MODIFICATIONS, AND SUPPORT

1.4.1.5.3 ORBITER OMDP

1.4.1.5.4 ORBITER/EXTERNAL TANK UMBILICALS

1.4.1.5.5 CAPABILITY DEVELOPMENT 40

1.4.2 SOLID ROCKET BOOSTER (SRB) 40

1.4.2.1 SRB ELEMENT PROCESSING 40

1.4.2.1.1 MULTIPLEXER -DEMULTIPLEXER (MDM) DEVELOPMENT 40

1.4.2.2 SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT 40

1.4.2.2.1 Cable
Tests.........................................................................................40

1.4.2.3 SRB STAND ALONE LOGISTICS 40

1.4.2.3.1 Cable
Quantities...................................................................................40

1.4.2.4 INTEGRATED LOGISTICS 40

1.4.2.5 SRB FLIGHT SYSTEMS DESIGN RESPONSIBILITY 41

1.4.2.6 SRB ELEMENT PROCESSING, GROUND SYSTEMS DESIGN RESPONSIBILITY 42

1.4.2.7 SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT, GROUND SYSTEMS
DESIGN RESPONSIBILITY 42

1.4.2.8 SRB RECOVERY OPERATIONS 42

1.4.2.9 RSRM STATIC FIRING SUPPORT 42

1.4.2.10 SRB MODIFICATIONS 42

1.4.2.11 SRB FACILITY TOOLING, EQUIPMENT, AND MINOR CONSTRUCTION,
ALTERATION, AND REPAIR (MCAR) 43

1.4.2.12 ACQUISITION SUPPORT 43

1.4.3 FLIGHT SOFTWARE 43

1.4.3.1 ORBITER AND BFS FLIGHT SOFTWARE PROCESSING AND TOOLS 43

1.4.3.2 FLIGHT SOFTWARE TESTING 44

1.4.3.3 AVIONICS AND SOFTWARE SYSTEM SUPPORT 45

1.4.3.4 BFS FLIGHT SOFTWARE RECONFIGURATION 47

1.4.3.5 BFS FLIGHT SOFTWARE MODIFICATIONS 48

1.4.3.6 FLIGHT OPERATIONS SUPPORT 49

1.4.3.7 PASS FLIGHT SOFTWARE PROCESSING 49

1.4.3.8 PASS FLIGHT SOFTWARE TOOLS 50

1.4.3.9 PASS FLIGHT SOFTWARE IMPLEMENTATION 51

1.4.3.10 PASS FLIGHT SOFTWARE RECONFIGURATION AND MMU INTEGRATION 52

1.4.3.11 GROUND FACILITY DATA PROCESSING SYSTEM 53

1.4.3.12 PASS FLIGHT SOFTWARE MAINTENANCE 53

1.4.3.13 MEDS MODIFICATION AND MAINTENANCE 54

1.4.3.14 MEDS SOFTWARE TEST OPERATIONS SUPPORT 55

1.4.3.15 PORTABLE COMPUTER SOFTWARE SYSTEMS FOR SPACEFLIGHT 56

1.4.3.16 VEHICLE AND PAYLOAD DATA COLLECTION/RECONFIGURATION 56

1.4.3.17 SHUTTLE AVIONICS INTEGRATION LABORATORY (SAIL) 57

1.4.4 EXTERNAL TANK (ET) 59

1.4.4.1 ET ELEMENT PROCESSING 60

1.4.4.2 ET LOGISTICS 60

1.4.4.3 RESERVED 60

1.4.4.4 ET TRANSPORTATION 60

1.4.4.5 ET MODIFICATIONS 60

1.4.4.6 RESERVED 61

1.4.4.7 ET TRANSITION PLAN 61

1.4.5 REUSABLE SOLID ROCKET MOTOR (RSRM) 61

1.4.5.1 RSRM ELEMENT PROCESSING 61

1.4.5.2 RSRM LOGISTICS 61

1.4.5.3 RSRM RECOVERY OPERATIONS 62

1.4.5.4 RESERVED 62

1.4.5.5 RSRM MODIFICATIONS 62

1.4.5.6 RESERVED 62

1.4.5.7 RSRM TRANSITION PLAN 62

1.4.6 SPACE SHUTTLE MAIN ENGINE (SSME) 62

1.4.6.1 SSME ELEMENT PROCESSING 62

1.4.6.2 SSME LOGISTICS 62

1.4.6.3 SSME LANDING OPERATIONS 63

1.4.6.4 RESERVED 63

1.4.6.5 SSME MODIFICATIONS 63

1.4.6.6 RESERVED 63

1.4.6.7 SSME TRANSITION PLAN 63

1.4.7 RESERVED 64

1.4.8 RESERVED 64

1.4.9 EXTRAVEHICULAR ACTIVITY (EVA) AND FLIGHT CREW EQUIPMENT 64

1.4.9.1 ELEMENT PROCESSING 64

1.4.9.2 EVA AND FLIGHT CREW EQUIPMENT LOGISTICS 65

1.4.9.3 TRAINING HARDWARE PROCESSING 66

1.4.9.3.1 MAINTENANCE AND REPAIR OF NBL TRAINING TOOLS 66

1.4.9.4 SHUTTLE REMOTE MANIPULATOR SYSTEM (SRMS) PROCESSING 66

1.5 INTEGRATED LAUNCH & LANDING OPERATIONS 66

1.5.1 VEHICLE INTEGRATION 68

1.5.1.1 ELEMENT/CARGO PLANNING & INTEGRATION 68

1.5.1.2 PAYLOAD INSTALLATION AND TESTING 69

1.5.1.3 INTEGRATED TEST EXECUTION 69

1.5.2 LAUNCH PREPARATIONS 69

1.5.2.1 LAUNCH REQUIREMENTS 69

1.5.2.2 LAUNCH PLANNING 69

1.5.2.3 LAUNCH TEAM TRAINING 69

1.5.2.4 LAUNCH READINESS 70

1.5.3 LAUNCH EXECUTION 70

1.5.3.1 RESERVED 70

1.5.3.2 LAUNCH OPERATIONS 70

1.5.4 POST LAUNCH 71

1.5.4.1 INTEGRATED LANDING OPERATIONS 71

1.5.4.2 MISSION SUPPORT 71

1.5.4.3 PAYLOAD ELEMENT REMOVAL 72

1.5.4.4 SOLID ROCKET BOOSTER & REUSABLE SOLID ROCKET MOTOR RECOVERY &
DISASSEMBLY 72

1.5.5 SYSTEMS, FACILITIES AND EQUIPMENT 72

1.5.5.1 OPERATIONS 72

1.5.5.2 MAINTENANCE 73

1.5.5.3 SUSTAINING ENGINEERING 74

1.5.5.4 LOGISTICS 75

1.5.5.4.1 ACQUISITION 75

1.5.5.4.2 MATERIAL MANAGEMENT 76

1.5.5.4.3 SUPPORT 77

1.6 FLIGHT OPERATIONS 77

1.6.1 TRAINING 78

1.6.1.1 TRAINING ADMINISTRATION AND MANAGEMENT 79

1.6.1.1.1 TRAINING RECORDS 79

1.6.1.1.2 CURRICULUM AND LESSON DEVELOPMENT 79

1.6.1.1.3 TRAINING SCHEDULING 80

1.6.1.1.4 INSTRUCTORS 80

1.6.1.2 FLIGHT CONTROLLER TRAINING 80

1.6.1.3 FLIGHT CREW TRAINING 81

1.6.1.4 FLIGHT TRAINING HARDWARE 82

1.6.2 FLIGHT PREPARATION 82

1.6.2.1 FLIGHT RULES/OPERATIONS DOCUMENTATION/FLIGHT DATA FILE (FDF) 83

1.6.2.1.1 FLIGHT RULES 83

1.6.2.1.2 OPERATIONS DOCUMENTATION 83

1.6.2.1.3 FLIGHT DATA FILE AND OPERATIONS DATA FILE (ODF) 83

1.6.2.2 FLIGHT DESIGN 84

1.6.2.2.1 FLIGHT DESIGN REQUIREMENTS 84

1.6.2.2.2 FLIGHT DESIGN PRODUCTS 84

1.6.2.2.3 FLIGHT DESIGN SOFTWARE 85

1.6.2.3 FLIGHT PLANNING 85

1.6.2.4 PAYLOAD INTEGRATION 86

1.6.2.5 FLIGHT CREW 86

1.6.2.5.1 PROGRAM REQUIREMENTS DEVELOPMENT/CHANGE TECHNICAL ASSESSMENTS
87

1.6.2.5.2 SHUTTLE-MIR DOCKING INTEGRATION 88

1.6.2.5.3 SHUTTLE LANDING AND ROLLOUT TECHNIQUE DEVELOPMENT 88

1.6.2.5.4 FLIGHT CREW EQUIPMENT (FCE) INTEGRATION 88

1.6.2.5.5 OPERATIONS DEVELOPMENT FOR ISS 89

1.6.2.5.5.1 FLIGHT CREW TRAINING DEVELOPMENT 89

1.6.2.5.5.2 FLIGHT CREW SUPPORT 89

1.6.2.5.5.3 ISS ASSEMBLY, SYSTEM AND UTILIZATION OPERATIONS ASSESSMENT
AND TESTING 89

1.6.2.5.5.4 RESERVED 90

1.6.2.5.5.5 COMMON DISPLAY DEVELOPMENT 90

1.6.2.5.5.6 ASTRONAUT ANALYSIS AND INTEGRATION TEAM (AIT) 90

1.6.2.5.5.7 RESERVED 90

1.6.2.5.6 SHUTTLE/ISS INTEGRATION 90

1.6.2.5.7 LIBRARY, DATABASE, AND DOCUMENTATION MAINTENANCE 90

1.6.2.6 CREW/VEHICLE INTEGRATION AND TESTING 90

1.6.2.7 DATA COLLECTION/ RECONFIGURATION 91

1.6.2.8 PCS PROJECT SUPPORT 92

1.6.3 RESERVED 92

1.6.4 FLIGHT OPERATIONS SYSTEMS AND EQUIPMENT 92

1.6.4.1 MISSION CONTROL CENTER (MCC) 96

1.6.4.1.1 MCC-OSHA STANDARDS 96

1.6.4.1.2 APOLLO MOCR 97

1.6.4.2 INTEGRATED TRAINING FACILITY (ITF) 97

1.6.4.3 INTEGRATED PLANNING SYSTEM (IPS) 97

1.6.4.4 SOFTWARE PRODUCTION FACILITY (SPF) 97

1.6.4.4.1 DATA RECONFIGURATION (SPF UNIQUE) 98

1.6.4.4.2 SPF-UNIQUE INSTALLATION SERVICES 98

1.6.4.5 SHUTTLE AVIONICS INTEGRATION LABORATORY (SAIL) 98

1.6.4.5.1 SAIL UNIQUE MAINTENANCE 98

1.6.4.5.2 SAIL INTEGRATED OPERATIONS 98

1.6.4.6 RESERVED 98

1.6.4.7 RESERVED 98

1.6.4.8 RESERVED 98

1.6.4.9 OPERATIONS SUPPORT SYSTEMS 98

1.6.5 NASA MANAGED MISSION EXECUTION SUPPORT 98

1.6.5.1 FLIGHT SYSTEMS 99

1.6.5.2 FLIGHT PLANNING/PAYLOADS/ASSEMBLY 100

1.6.5.3 FLIGHT DESIGN AND DYNAMICS 101

1.6.5.4 FLIGHT OPERATIONS DEVELOPMENT 101

1.7 NASA MANAGED ACTIVITIES 101

1.7.1 DEVELOPMENT 101

1.7.1.1 KSC SHUTTLE DEVELOPMENT ACTIVITIES 102

1.7.1.2 KSC CONSTRUCTION OF FACILITIES (CofF) ACTIVITIES 102

> 1.7.2.5.1 ISS CARGO CONFIGURATION REQUIREMENTS 102
>
> 1.7.2.5.2 ISS CARGO UNIQUE ICD'S 102

1.7.3 ISSPO SUPPORT 102

1.7.4 PROGRAM REIMBURSEABLES 103

1.7.5 SRB DEVELOPMENT ACTIVITIES 103

1.8 INTERNATIONAL SPACE STATION PROGRAM (ISSP) 103

1.8.1 ISSP MANAGEMENT INFORMATION SYSTEMS 103

1.8.2 ISS SAFETY AND MISSION ASSURANCE (S&MA) 104

1.8.3 ISS CONFIGURATION MANAGEMENT 104

1.8.4 ISS SUSTAINING ENGINEERING (SE) - HARDWARE HISTORY RETRIEVAL
SYSTEM (HHRS) 104

1.8.5 ISS MEETING/MISSION EVALUATION ROOM (MER) SUPPORT 105

1.8.6 ISS LOGISTICS AND MAINTENANCE (L&M) 105

2.0 SPACE SHUTTLE UPGRADES DEVELOPMENT (SSUD) 106

2.1 PROGRAM AND BUSINESS MANAGEMENT 106

2.2 SYSTEMS ENGINEERING AND INTEGRATION 106

2.3 CHANGE IMPACT ASSESSMENT 106

2.4 COCKPIT AVIONICS UPGRADE PHASE II 107

2.5 EAPU 107

2.5 1 EAPU Phase III 107

2.5.2 EAPU Phase
IIIA...............................................................................................107

2.6 THRUST VECTOR CONTROL (TVC) UPGRADE 107

2.6.1 THRUST VECTOR CONTROL (TVC) UPGRADE PHASE II, FORMULATION 107

2.7 KU-BAND COMMUNICATION SYSTEM 108

2.8 RENDEZVOUS PROXIMITY SENSOR SYSTEM
PRE-FORMULATION......................... 108

2.9 Communication and Tracking System 108

2.11 AVIONICS INSTRUMENTATION SYSTEM (AIS) 108

2.12 COMMAND RECEIVER DECODER (CRD) PRODUCTION 108

2.13 ALTITUDE SWITCH ASSEMBLY (ASA) DESIGN, DEVELOPMENT QUALIFICATION &
PRODUCTION 108

2.14 X-Ray Exposure Cell Phase I 109

2.15 Small Boat Davit System 109

2.16 Enhanced Diver Operated Plug 109

2.17 Real Time Visualization 109

2.18 Virtual Reality Simulations -- Orbiter Temporary Access
Improvements (IES project) 113

2.19 Anti-Roll System 114

2.20 Oxygen Enriched Air (NITROX) 114

2.21 Task Analysis Tool Development 114

2.22 New Hypalon Paint Formulation Qualification
(IES)................................................\....114

2.25 Supportability Infrastructure Upgrade
Studies...........................................................115

2.25.1 Refurbish FSS & RSS, Pads A & B
......................................................\................115

2.25.2 Upgrade Orbiter Weather Protection for --Y and +Y Sides, Pads A &
B. ......................115

2.25.3 Rebuild White Room/Orbiter Access Arms, Pads A &
B.................................\..........115

2.26 CPA \# MSFC-080 -- IEA Supportability Upgrade, Implementation
Phase............\..........115

2.27 Advanced Health Management System (AHMS) Upgrades
.....................\..................115

2.27.1 AHMS Phase 1 116

2.27.2 AHMS Phase 2A 116

2.27.3 AHMS Phase 2B.1 116

# 1.0 SPACE FLIGHT OPERATIONS CONTRACT

This Statement of Work (SOW) defines the tasks to be performed by the
contractor, including management and integration of efforts to be
performed by subcontractors. The scope of work to be performed under
this contract consists of overall responsibility as the prime contractor
to include all Space Shuttle Program (SSP) and International Space
Station Program (ISSP) activities defined herein. This required work
shall be performed so that all missions manifested by NASA (or to be
manifested within the period of performance, including any options
exercised), as specified in Table 1, are successfully accomplished.

Table 1

SPACE TRANSPORTATION SYSTEM MANIFESTED FLIGHTS

Refer to the current version (and subsequent revisions) of National
Aeronautics and Space Administration (NASA) Space Transportation System
(NSTS) 07700-VOL-III, Space Shuttle Flight Definition and Requirements
Directive and NSTS 08178, SSP Schedules for:

o Overall flight definition and planning guidelines

o Near-term flight assignments, characteristics, and configuration

o Flight preparation configuration freeze point definitions

o Follow-on flight rate requirements by fiscal year

o Required capability enhancements in support of flight missions

o Orbiter Maintenance and Down Period (OMDP) Schedule

Refer to the current version (and subsequent revisions) of ISSP
Implementation Plan 50200-02, Vol. II.

The contractor shall perform all work during the contract period
necessary and appropriate to support scheduled missions pursuant to the
mission profile set forth on Table 1. However, in the accomplishment of
the flights specified in Table 1, events are anticipated and
historically supported which will cause a reasonable variation in the
manifest (reference clause H.33, *Launch Schedule Variations*).

The Space Shuttle Vehicle (SSV) elements for which the contractor has
overall responsibility consist of the fleet of Orbiter Vehicles; the
Solid Rocket Boosters (SRB's) and Reusable Solid Rocket Motors (RSRM's);
the External Tank (ET); the Space Shuttle Main Engines (SSME's); Flight
Crew Equipment; ground support systems, flight software, and integration
of payloads manifested by NASA.

In carrying out its responsibilities under this contract, the contractor
shall maintain the current conformance with the program description and
requirements of the NSTS 07700 series of documentation, and the
derivatives thereto, the ISSP Joint Management Plans (JMP), the ISSP
Concept of Operations & Utilization (COU) series of documentation, the
Space Station Implementation Plan (SPIP) series of documentation, and
the applicable documents defined in the SOW.

## 1.1 PROGRAM AND BUSINESS MANAGEMENT

This section defines the program and business management tasks that are
to be performed by the contractor in order to develop and deliver the
required SSP and ISSP operations services. The contractor is to effect
these management functions through management approach, organization,
and controls that are determined by the contractor to be optimum. The
contractor shall provide and maintain program management systems, as
outlined below, for the planning, organization, control, and reporting
of all activities required by this contract. These systems shall be
adequate to assure accomplishment of program technical and schedule
requirements, and cost objectives.

### 1.1.1 PROGRAM MANAGEMENT

The contractor shall provide for planning, management reviews, manifests
& schedules, and risk management in support of contract requirements.

#### 1.1.1.1 PLANNING

The contractor shall provide and maintain a Management Plan (DR.
1.1.1.1‑a). The contractor's management structure shall fully integrate
all related plans and systems, including those of subcontractors and
major vendors. The plan shall address the systems, functions, and data
requirements described in this SOW.

The contractor shall provide the Work Breakdown Structure (WBS)
(DR 1.1.1.1‑b). This WBS shall serve as the framework for contract
planning, budgeting, cost reporting and schedule status to the NASA.
Major elements of subcontracted work shall be identified in the WBS.

The contractor shall produce and maintain a strategic Space Flight
Operations transition plan (DR 1.1.1.1‑c). This planning activity shall
provide strategies and schedules for effecting transition, and the
contractor's metrics for determining the effectiveness of the transition
for all Space Flight Operations elements and functions including the
transition from the existing contractor/government relationship and
responsibilities to the contractor's planned approach to manage this
contract. The plan shall include the approach for increasing the
contractor's accountability by translating NASA requirements into
auditable plans, system procedures and work instructions. The contractor
shall provide pre-transition contract programmatic assessment, and
process evaluation/integration associated with Phase II contracts listed
in Attachment J-1-C. In addition to its annual update, DRD 1.1.1.1-c
will be updated upon transition of any Phase II contract (see Clause
H.30).

In order to establish a baseline, the contractor shall provide
controlled work characterization descriptions as described in DR
1.1.1.1-f and DR 1.1.1.1-j.

The contractor shall provide master planning and space utilization for
assigned areas of responsibility.

A privatization development plan shall be provided describing a general
approach for potential involvement in providing SSP and ISSP type
operations services to other customers and the business approach for
potential commercial customers of the SSP (DR 1.1.1.1‑d).

The contractor shall develop and update plans for contingency situations
(DR 1.1.1.1‑e). These plans shall include planning for natural
disasters; launch delay situations, off nominal landings, major hardware
failure safing/recovery situations and crew evacuations. A current list
of contingency plans is included in Exhibit 1.1.1.1.

The Contractor shall provide white papers detailing significant program
management decisions in accordance with the scope and requirements of DR
1.1.1.1-k

#### 1.1.1.2 MANAGEMENT REVIEWS

##### 1.1.1.2.1 CONTRACT MANAGEMENT REVIEWS

The Contractor shall conduct Contract Management Reviews (CMR) to
provide NASA with current status of the contractor's financial, work
force, and technical activities. CMR's shall be conducted in accordance
with an agreed to schedule.

##### 1.1.1.2.2 PROGRAM REVIEWS

The contractor shall participate in and support program meetings and
reviews. This shall include presentations covering the contractor's
areas of responsibility; identification of impacts due to proposed
requirements changes; the planning and implementation of the program
meetings and reviews; and the coordination and resolution of action
items with NASA and other contractor representatives. Examples of these
meetings and reviews are: Flight Readiness Review (FRR), the Prelaunch
MMT Review, program level control/change boards, anomaly resolution
meetings, and government and non-contractor design reviews that impact
the contractor's area of responsibility. The Contractor will provide an
off-site conference facility at JSC capable of supporting multiple
simultaneous meetings and teleconferences. The facility must have the
capacity to support at least one teleconference accommodating 150
participants.

##### 1.1.1.2.3 FLIGHT READINESS

The Contractor shall review flight preparations to ensure flight
readiness in accordance with NSTS 08117, Requirements and Procedures for
Certification of Flight Readiness, and SSP 50108, Certification of
Flight Readiness for Space Station. The contractor shall develop and
implement an auditable approach to verify and ensure that flight
preparation responsibilities and requirements are met and all problems
dispositioned. This approach shall include as a minimum open item
reviews, Flight Readiness Reviews (FRRs), prelaunch MMT Reviews,
pre-test briefings, and presentation of an integrated SFOC Certificate
of Flight Readiness (CoFR) endorsement. This CoFR shall be prepared in
accordance with DRD 1.1.1.2.3 and will include readiness statements that
cover all processes and products required to satisfy the contractor's
responsibilities and readiness to support launch, mission, and landing
operations as defined in the above referenced documents.

#### 1.1.1.3 Reserved

#### 1.1.1.4 RISK MANAGEMENT

The contractor shall develop a risk management plan (DR 1.1.1.4‑a) which
details how the contractor will integrate safety, reliability,
maintainability and quality issues and correlate those issues with cost,
schedule and probability of mission success such that the contractor
routinely considers risk in the planning and day-to-day decision making
processes. The contractor shall provide a risk assessment (DR 1.1.1.4‑b)
with the complete relationship of the assurance issues (safety,
reliability, maintainability and quality) to program goals (cost,
schedule and mission success) with each topic and issue brought to
program management for resolution. The risk assessment shall include the
contractor's recommended means to mitigate the risk.

The contractor shall report to the government all anomalies that
potentially impact or constrain flight or key processing milestones and
anomalies that represent safety, mission success, major program schedule
milestones, or cost risks to the government. The contractor shall obtain
government approval of out-of-family anomaly dispositions (DR 1.1.1.4‑c)
which are defined as anomalies which involve one or more of the
following:

\- involve the first-time occurrence of a failure mode

\- limit hardware life

\- restrict hardware or software use

\- affect the performance or reliability of safety or mission success
critical hardware functions

\- affect hazard control

\- result in a weight change in excess of 2 pounds (equivalent weight to
orbit)

\- affect flight or ground operating procedures that are controlled by
the government

\- change software or hardware configuration

\- allow use of hardware that does not meet performance specifications,
exceeds certification limits, or surpasses time, age, or cycle life
limits (waivers/exceptions)

\- close or defer resolution of an unexplained anomaly

\- requires government design element analysis or assistance

\- affect critical hardware manufacture or repair processes

Required Service: Reporting anomalies to the appropriate government
interface.

Standard: All anomalies reported in accordance with applicable NSTS
08126 and SSP 30229 requirements.

MER: 2% of anomalies reported late but in no case greater than 2 day
beyond specified requirements, and no out-of-family anomalies reported
late.

Standard: All anomalies and non conformances that occur during or
constrain launch countdown and flight operations reported as soon as
practical.

MER: 0%

#### 

#### NEW TECNOLOGY

The contractor shall develop, maintain, and operate a new technology
program in accordance with NFS clauses 18-52.227-70 and 18-52.227-72 and
clause G-15 of the contract. The contractor shall report new technology
in accordance with DRD 1.1.1.1-i.

### 1.1.2 FINANCIAL RESOURCES AND PERFORMANCE MANAGEMENT

The contractor shall provide and maintain a resource management system
for the accumulation, documentation, and analysis of cost and work force
data. The resources management system will be the basis for
communication with NASA concerning financial planning and control,
accounting of accrued expenditures and other liabilities, evaluation of
cost performance, and forecasting of cost and work force requirements
(reference SOW section 1.1.2.1). The financial management system shall
provide the baseline of financial parameters to be input and assessed in
the integrated Performance Measurement System (PMS).

#### 1.1.2.1 FINANCIAL RESOURCES MANAGEMENT

The contractor's financial reporting (DR 1.1.2.1‑a) shall be provided in
accordance with NPG 9501.2C. These financial reporting requirements are
applicable to all tiers of subcontractors with annual expenditures of
\$5 million or more or with a total contract value of \$10 million or
more. In addition, the contractor shall provide an on-line database (DR
1.1.2.1-b) accessible to NASA which provides accurate and timely
resource information such as resource plans, staffing, and actuals. The
contractor shall manage and control work and resources within discrete
program fund sources and program funding levels approved by NASA.

The contractor shall provide financial planning as required to support
the government budget process (i.e., Program Operating Plan \[POP\]
budget calls, monthly operating plan budget calls, and CofF budget
calls), and to support special requests for budget impacts. The format
and content of the contractor's inputs and supporting rationale shall be
in accordance with the budget or special request guidelines and
reporting format specified by the NASA.

The contractor shall conduct monthly (normally one day prior to the CMR)
Resources Management Reviews (RMR) providing NASA with insight into the
contractor's, subcontractors', and vendors' overall work progress and
financial status. The contractor shall track and report facilities
maintenance costs (DR 1.1.2.1‑c), energy utilization and consumption
(DR 1.1.2.1‑d), on-site and off-site headcount (DR 1.1.2.1‑e), and
geographical economic impacts (DR 1.1.2.1‑f).

#### 1.1.2.2 PERFORMANCE MEASUREMENT

For operations activities, the contractor shall develop and maintain a
PMS (DR 1.1.2.2‑b). The level of detail for this system shall be
consistent with the maturity and stability of the program elements.
Performance measurement reporting is also required on subcontracts that,
based on risk, schedule criticality, or dollar value, have the potential
to impact the successful fulfillment of this contract

The contractor shall develop and maintain performance metrics which
effectively indicate the level of success in execution of the contract
requirements, including definition/development of the metrics,
correlation of the metrics to the requirements, and measurement of
management responsiveness to the performance indicated by the metrics.

For development and production efforts which may be authorized in this
contract, the contractor shall provide PMS reporting (DR 1.1.2.2‑a) in
accordance with NMI 9501.1 which correlates work accomplished and actual
costs against baseline cost plans and schedules.

A summary of the PMS report shall be provided in the monthly RMR. The
contractor shall provide NASA direct electronic access to the contractor
PMS system. Technical issues and accomplishments, analysis of cost and
schedule performance, and corrective actions in problem areas shall be
provided.

### 1.1.3 CONTRACT MANAGEMENT

The contractor shall provide overall management of the contract
requirements.

#### 1.1.3.1 PRIME CONTRACT MANAGEMENT

The contractor shall perform those tasks associated with administering
the contract.

#### 1.1.3.2 SUBCONTRACT MANAGEMENT

The contractor shall accomplish the management and technical control of
interdivisional, subcontractor, and major vendor activities required to
fulfill the contract. The plan for managing the subcontract effort is
described in the management plan (DR 1.1.1.1‑a).

The PMS shall provide appropriate management visibility into all aspects
of interdivisional, subcontractor, and major vendor activities and shall
be integrated with other required management systems and reporting
requirements of the prime contractor. A system of management reviews and
reports shall be incorporated to provide a reliable status of progress
and performance measurement.

### 1.1.4 INFORMATION AND DOCUMENT MANAGEMENT

The contractor shall provide information management, and document
management in support of contract requirements.

#### 1.1.4.1 INFORMATION MANAGEMENT

The contractor shall develop, maintain, and operate and secure
information systems which provide for the management, preparation,
publication, control and dissemination of information and data required
by this contract. These systems shall be described in an information
management plan (DR 1.1.4.1.-a) and a data management plan (DR
1.1.4.1-e) which define an integrated approach to the information
management activities of this contract and include the management of
documentation ( in any media ), automated databases, and related
products. The contractor shall describe the areas of the contractor's
internal systems where NASA access will be permitted and shall define
access and interface requirements and provide NASA the required training
to be able to access and use these systems. The government systems that
are currently being used will be made available to the contractor and
are identified in Attachment J-9.

The contractor's information management activities shall include
operating and maintaining a data repository or repositories, as
required, for originals in any media including classified and
proprietary documents. The contractor shall maintain files of the
documentation required to perform all the tasks in this SOW. The
contractor shall establish a formal documentation release system and a
system for rapid retrieval of all records.

The contractor shall establish and implement a program-wide (i.e.
contract-wide) information technology (I/T) planning and reporting
process (DR 1.1.4.1‑b).

#### 1.1.4.2 DOCUMENT MANAGEMENT

The contractor shall maintain accurate originals and shall prepare and
distribute NASA approved changes to SSP and operations baseline
documentation. This includes the NSTS 07700 documentation series.

1.1.4.3 YEAR 2000 COMPLIANCE

"Year 2000 compliant," as used herein, means that the information
technology (hardware, software and

firmware, including embedded systems or any other electro-mechanical or
processor-based systems used in accordance with its associated
documentation) accurately processes date and date-related data
(including, but not limited to, calculating, comparing, and sequencing)
from, into, and between the twentieth and twenty-first centuries, and
the years 1999 and 2000 and leap year calculations, to the extent that
other information technology, used in combination with the information
technology being acquired, properly exchanges date and date-related data
with it.

Any information technology provided, operated and/or maintained under
this contract must be Year 2000 compliant. To ensure this result, the
Contractor shall prepare Year 2000 documentation describing how the IT
items or services demonstrate Year 2000 compliance. Clause H.30,
Consolidation of Phase II Contract Requirements, contemplates the
consolidation of additional contract requirements into this contract
over time. The contractor is not responsible for Year 2000 compliance
for the following Phase II contracts: NAS 8-36200, External Tanks; NAS
8-38100, Reusable Solid Rocket Motors; and, NAS 8-45000, Space Shuttle
Main Engines.

Milestones for Renovation, Validation and Implementation: Any IT
determined to be non-Year 2000 compliant shall be replaced, retired, or
repaired in accordance with the following schedule:

-   "Renovation" includes making and documenting software and hardware
    changes, developing replacement systems, and decommissioning systems
    to be retired. The Contractor must complete renovation of affected
    software, hardware and firmware by September 30, 1998.

-   "Validation" includes unit, integration, system, and end-to-end
    testing for Year 2000 compliance. The Contractor must complete
    validation and testing of converted or replaced systems by January
    31, 1999.

-   "Implementation" includes acceptance testing and integration of
    converted and replaced systems into a production environment. The
    Contractor must complete implementation by March 31, 1999.

    At a minimum, the Contractor shall provide documentation, including
    project plans and status reports, which demonstrate that the
    Contractor is meeting the milestones listed above.

### 1.1.5 CONFIGURATION AND VERIFICATION MANAGEMENT

The contractor shall provide a configuration management system and a
verification management program as described in SOW sections 1.1.5.1 and
1.1.5.2.

#### 1.1.5.1 CONFIGURATION MANAGEMENT

The contractor shall, in accordance with NSTS 07700, provide a
configuration management (CM) system including identification, control,
verification, and accounting for facilities, hardware and
software/firmware for which the contractor is responsible. The
contractor shall also provide configuration management products for the
NASA change evaluation and control process. This will include action
item status; preparing and coordinating Program Requirements Control
Board Directives (PRCBD's), other program level control/change board
directives, and Project level change board directives; maintaining
accurate, complete, and current CM data in the appropriate databases to
ensure implementation and verification of program direction. The
contractor shall also distribute, coordinate, and track NASA change
evaluations for the engineering Directorate.

A configuration management plan shall be provided (DR 1.1.5.1).

#### 1.1.5.2 VERIFICATION MANAGEMENT

The contractor shall implement a verification management program in
accordance with NSTS 07700 to ensure hardware/software processing and
configuration requirements are accomplished. A verification management
plan shall be provided (DR 1.1.5.2‑a).

The contractor shall track, satisfy and verify the flight element
processing requirements, integrated processing requirements, flight
operations requirements, facilities and systems requirements; and verify
that the as built configuration is in accordance with the approved
engineering and program direction. In addition, the contractor shall
administer the documentation of requirements in the requirement system.
These requirements are currently managed through such systems as the
Operations and Maintenance Requirements Specification Document (OMRSD)
system, Baseline Accounting and Reporting System (BARS), Configuration
Verification Accounting System (CVAS), MSFC Baseline Accounting and
reporting System (MBARS), Mission Requirements Control System (MRCS),
Configuration Verification (CV), Problems Action Data System(PADS),
Shuttle Integrated Accounting Status System (SIASS), Time, Age, Cycle
Control System (TACCS), and Tile Information Processing System (TIPS).

The contractor shall be responsible for the development, implementation,
maintenance, and operation of the shuttle configuration requirements
application support software databases and systems (e.g. In-Flight
Anomalies \[IFA\], TACCS, Technical Document Management System
\[TDMS\]). The contractor shall provide software and hardware sustaining
engineering for client-server based applications (e.g. OMRSCP, DCMS,
LMS, CMMDB and WebPCASS) including IT security and Export compliance (DR
1.1.5.2-d).

The contractor shall maintain the configuration requirements database
for program level baselined configuration requirements to support
configuration verification (DR 1.1.5.2‑b).

Combined element (integrated vehicle) verification will be accomplished.
This activity requires that the contractor provide support to verify
combined-element compliance with Master Verification Plan volumes MVP‑01
and MVP‑02 and Orbiter compliance with MJ072‑0004‑3A. Update MVP‑02 and
MJ072‑0004‑3A as required. In addition, the contractor shall publish
reports concerning verification status for each element relative to the
NSTS 07700, Volume 10 requirements baseline.

### 1.1.6 GOVERNMENT FACILITY, PROPERTY AND SECURITY MANAGEMENT

The contractor shall perform facility, property and security management
as described herein. The contractor shall manage, operate, maintain and
provide engineering for the Government Furnished Property (GFP)
delineated in Attachment J-9. GFP will be transitioned to the contractor
in accordance with Attachment J-9. Additional KSC site specific
requirements for facilities operations, maintenance and sustaining
engineering are included in SOW section 1.5.5.

#### 1.1.6.1 FACILITY MANAGEMENT

The contractor shall provide a Facility Management Plan (DR 1.1.6.1-a)
which shall describe the contractor's approach to managing facilities
responsibilities. The contractor shall conduct semi-annual Facility
Management Reviews (FMR) providing NASA with insight into the
contractor's and subcontractors' facility management status. The
contractor shall manage assigned facility space to accommodate
contractor, NASA, other Government agencies and non-Government tenants
as required. The contractor shall provide planning, development and
integration of facility projects required in the performance of this
contract.

The contractor shall analyze, design, construct, acquire, relocate,
install, modify and improve contractually obligated facilities as
required and provide required facility project reporting. (DR 1.1.6.1-b)
Requests for facility projects not anticipated and identified in prior
submissions shall be submitted when identified and include project
prioritization and documentation. Project requests shall include a
comprehensive requirements document, as required, in sufficient detail
to allow for an independent cost estimate of all scope and related
issues identified to accomplish the project. All siting plans must be
approved by the Government.

Required Service: Deliver specified end products on schedule and stay
within negotiated budget

Standard: All end products are delivered on schedule

Expected: 85% of all end products delivered on schedule

MER: 70% of all end products delivered on schedule

\* End products referred to in this metric are studies, designs,
facility project construction completion, financial completion.

The contractor shall provide a quarterly review of all facility projects
to include requirements documents, studies, Preliminary Engineering
Reports (PER), design, construction, activation, environmental issues,
schedule (including completion milestones), change orders, potential
scope growth, and access/support.

The contractor shall provide engineering support for project studies,
design, implementation, activation and turnover related to NASA managed
facility modifications in accordance with SOW section 1.7.1.

The contractor shall implement a comprehensive proactive maintenance
program incorporating reliability centered maintenance in accordance
with NHB 8831.2, as required, and submit a maintenance plan (DR 1.5.5.2)
for assigned facilities and facility systems. The contractor shall
provide systems, facilities and equipment hardware/software/firmware
sustaining engineering that meets the original design intent, develop
the applicable engineering documentation, implement the appropriate
modifications, and maintain this documentation current.

Required Service: Maintain systems, software, firmware, facilities and
equipment.

Standard: Perform 100% of all planned maintenance tasks delineated in
the yearly maintenance plan (ref DR 1.5.5.2).

Expected: Perform 90% of all maintenance tasks delineated in the yearly
maintenance plan

MER: 15% of tasks not completed, 85% completed but in no case impact
safety, mission success or major program schedule milestones.

The contractor shall provide a transition plan (DR 1.1.1.1-c) which
shall include the facility responsibilities to be transitioned to SFOC.

#### 

#### 

1.1.6.2 PROPERTY MANAGEMENT

The contractor shall provide a fully operational Property Management
Plan (DR 1.1.1.1-h). The contractor shall provide quarterly Property
Status Reviews providing NASA with insight into the contractor's and
subcontractors' property management status.

Required Service: Maintain approved property management systems and
satisfactory ratings for each category in accordance with NFS Tables
18-45-1 and -2B to subpart 18-45.72.

Standard: Meet criteria for satisfactory rating in all rating
categories.

Expected: Satisfactory rating in 80% of all rating categories with
recovery of each unacceptable within 60 days.

MER: Satisfactory rating in 65% of all rating categories with recovery
of each unacceptable within 90 days.

Within the contract, the loan or transfer of property between NASA
centers or remote sites shall be processed in accordance with procedures
identified in the Property Management Plan (DR 1.1.1.1-h) insuring
management and engineering reviews and approvals are obtained prior to
movement, as appropriate. The contractor shall insure appropriate
property, tracking and statusing records are adjusted accordingly as
such transfers and movements are authorized.

1.1.6.3 SECURITY AND TECHNOLOGY PROTECTION MANAGEMENT

The contractor shall establish an effective and comprehensive program
that encompasses classified controlled information/material and
unclassified controlled information, material, and services (including
Export Controlled, and also proprietary data/material as appropriate).

The contractor\'s security program shall encompass Industrial, Physical,
Administrative, Information, Communication and AIS security programs in
accordance with the National Industrial Security Program Operating
Manual, NASA Site Specific Regulations, SFOC Security Management Plan
(DRD 1.1.6.3-a), SFOC Technology Protection Control Plan (DRD
1.1.6.3-b), and DD Form 254. The Contractor will provide
protection/safeguarding of personnel, facilities, assets, equipment,
classified information/materials, and unclassified
sensitive/technological data/information as required. The contractor
will support secure flight, engineering, and operations of secure
facilities and systems through the implementation and adherence to SFOC
requirements. In accordance with NASA, DoD, DOS, and DOC regulations
governing National Security, National Resource Protection, and
Technology Protection the Contractor shall provide security engineering,
maintenance, and operations for systems protecting classified controlled
and unclassified controlled information transmitted or processed by
electronic means, and for Orbiter and Space Station communications,
information and personnel security, configuration management and the
application of risk assessment techniques. The contractor will act as
the COMSEC controlling authority for certain encrypted communications,
and provide technicians certified to perform limited cryptographic
maintenance and operations.

The contractor\'s technology protection program shall encompass
classified controlled information/material and unclassified controlled
information, materials, and services (including Export Controlled, and
proprietary data/material as appropriate). The contractor shall provide
the methodology and processes to be implemented for the application of
risk assessment to technology protection, and the integration of
Security and Technology Protection Management across the SFOC contract
and its subcontractors.

Required Service: [Security]{.underline} - Provide physical
access/egress, IT security industrial/administrative which includes
classified (CI) Information, unclassified controlled information,
processes, systems, data, and violence/damage control.

> [Technology Protection]{.underline} - Provide adequate measures of
> control of classified and unclassified controlled information,
> material, and services.

Standard: [Security]{.underline} - No (preventable) security violations,
anomalies, i.e., unauthorized CI disclosures, unclassified controlled
information, and preventable security incidents.

> [Technology Protection]{.underline} - No disclosure violations of
> classified or unclassified controlled information, material, and
> services.

MER: [Security]{.underline} - No (preventable) violations or incidents
that result in compromises, disclosures, serious personal injury or
intentional physical damage.

> [Technology Protection]{.underline} - No violations or incidents that
> result in compromises of classified or unclassified controlled
> information, material or services.

The contactor shall conduct quarterly management reviews providing NASA
with insight into the contractor\'s and subcontractor\'s security
management program, and technology protection program including
processes and controls.

### 1.1.7 FLIGHT INTEGRATION, MANIFEST AND SCHEDULES

1.  FLIGHT INTEGRATION

The contractor shall perform flight integration duties as specified to
facilitate the implementation of flight requirements.

The contractor shall provide an SFOC Representative to support the
Flight IPTs.

This representative shall interface with SSP & ISS organizations to
resolve flight preparation process implementation issues. The contractor
representative shall direct studies, assessment activities, and assign
action items to resolve flight preparation process issues. The
contractor representative shall provide the SSP with insight into flight
preparation progress including issues and issue resolution activities.

The contractor shall manage the Flight Requirements Documents (FRDs)
including the FRD Blank Book, the FRD ISS Standard, and the flight
specific FRDs. The contractor shall interface with all organizations to
implement timely and coordinated inputs to the FRD, ensure consistency
between flight specific FRDs, and ensure distribution to the appropriate
SSP community (DR# 1.1.7-f).

### 1.1.7.2 MANIFESTS AND SCHEDULES

The contractor shall provide timely analysis and data to support the
government managed manifest planning efforts by providing data relative
to processing plans and timelines, launch rate capability, schedules,
flight hardware/software/equipment utilization plans, facility/equipment
utilization plans, prioritization assessments, ascent performance
margins, downweight determinations, cargo mass properties and
payload/cargo compatibility. The contractor shall assess the viability
of government provided manifests and manifest options. This includes
risk mitigation (cost and schedule), assessing potential impact to
mission performance, conducting internal studies to reduce turnaround
times, and requirements analysis.

The contractor shall support the NASA working groups in the development,
definition, assessment, and modification of the Shuttle manifest and the
top-level program schedules and deliver products (DR's 1.1.7-a, &
1.1.7-d).

The contractor shall provide support to the manifest and mission
integration process through the support of payload and mission
integration schedule documentation development and maintenance. This
includes the program documentation developed to acknowledge program
commitments to customers for integrating their payloads and
establishment of mission requirements/objectives for each flight,
preparation of NASA interfacing schedule documentation with payload
customers, and customer support room (CSR) service for payload
customers.

The contractor shall demonstrate schedule performance by accomplishment
of the manifest and established Program milestones. The contractor shall
demonstrate schedule performance based on the degree the planned and
scheduled work for a particular element activity, flow or integrated
flow correlates to the actual work (as run data) performed during that
element activity or flow. The contractor shall analyze major variances
to these measures, identify causes for these variations and make
recommendations or refinements to the applicable processes to improve
schedule performance and reduce schedule risk.

The contractor shall perform all scheduling activities (detail near term
and long range) to support all flight element activities, integrated
processing, flight operations activities and assigned systems,
facilities, and equipment activities. The contractor shall utilize a
planning and scheduling process that provides the necessary
identification, coordination, sequencing, control and tracking of
operational activities at all operational sites. The contractor shall
provide accurate and reliable scheduling information and other
performance metrics (DR's 1.1.7‑b and 1.1.7‑c) that provides the
government sufficient insight into the contractor's ability to fully
analyze, mitigate and control scheduling risks, maximize schedule
stability, minimize milestone impacts and optimize resource utilization.

Required Service: Meet major program schedule milestones as defined in
NSTS 07700, Vol. III, NSTS 08178, and SSP 50200-02, Vol. II .

Standard: Meet major program schedule milestones.

MER: No impacts to these dates due to contractor performance.

The Contractor will assume Payload Integration Management (PIM)
responsibility for all GAS payloads; and other assigned payloads. The
contractor shall prepare integration Plans (IP's) in accordance with the
requirements of DRD 1.1.7-e.

## 1.2 SYSTEM AND CARGO INTEGRATION

"The contractor shall plan, control, and perform SSV flight systems and
cargo integration activities. In addition, the contractor shall provide
PIP annex 1; and crew compartment integration hardware to accommodate
stowage and cabling."

### 1.2.1 ENGINEERING

The contractor shall provide engineering support for ascent design,
cargo engineering, flight support, and post flight analysis of SSV
flight systems performance.

#### 1.2.1.1 POST FLIGHT ANALYSIS

The contractor shall plan, control, and perform all post flight analyses
of the actual SSV flight systems. The contractor shall provide the post
flight analyses of the SSV to validate engineering preflight prediction
tools and methodologies and to provide the SSP visibility on and
resolution of in-flight anomalies and anomalous flight history trends.
The required analyses include, but are not limited to SSD92D0050,
Requirements Definition Document for Post Flight
Analysis/Reconstruction. To support flight derived dispersions database
updates, DR 1.2.1.1-a will be required.

Required Service: Completion of all post flight analyses in all
technical areas.

Standard: All products 100% technically accurate.

MER: No errors that require rework of analyses.

Standard: All products delivered on or before due date.

MER: No major program schedule milestones missed.

#### 1.2.1.2 ASCENT MARGINS ASSESSMENT

"The contractor shall plan, control, and perform a pre-flight evaluation
of the SSV flight systems and integrated subsystems. The contractor
shall provide the ascent flight verification assessment based on the
latest available Trajectory Design Data Package (TDDP) and the flight
cycle I-loads. Results of the evaluation shall be coordinated with the
Ascent Flight Systems Integration Group and presented to the Program
Integration Flight Readiness Program Milestone Reviews. The contractor
shall maintain documentation of the Flight Readiness Verification
methodology and shall obtain NASA approval prior to changing the
methodology. Specific missions may require unique contractor assessments
beyond those specified in NSTS 08349, Systems Integration Plan for
Integrated Mission Support and SSD9D033, Flight Readiness Verification
Criteria Document. NASA will define requirements for those assessments.
The contractor shall maintain the ability to perform a complete Flight
Margins Assessment in support of Day-of Launch I-Load Update 1 (DOLILU1)
or mission unique designs.

Required Service: Provide Ascent Flight Verification Assessment.

Standard: All products 100% technically accurate.

MER: 0% errors leading to incorrect CoFR positions that affect safety,
mission success, or major program schedule milestones.

Standard: All products delivered on or before due date.

MER: No major program schedule milestones missed."

#### 1.2.1.3 CARGO INTEGRATION ENGINEERING ANALYSIS

The contractor shall provide all assessments and analyses necessary to
assure compatibility between the Shuttle and cargo manifest
requirements, to verify readiness for all flight phases, and to support
the Payload Safety Review Panel (DR 1.2.1.3-c). Shuttle generic math
models shall be maintained by the contractor with changes approved by
NASA. Payload math models will be government furnished.

The contractor shall provide payload customers Shuttle math models
(DR 1.2.1.3‑a) and engineering data (DR 1.2.1.3‑b).

The contractor shall perform all assessments and issue resolution to
assure the Shuttle elements and cargo manifest integrated interfaces and
environments are safe to fly and there is no environmental impact threat
from the manifested cargo. The contractor shall provide a Payload
Environmental Impact Statement (DR 1.2.1.3-d).

Required Service: Provide all assessment and analysis necessary to
assure compatibility between Shuttle and cargo.

Standard: 100% complete by Orbiter rollout review.

MER: All compatibility completed prior to FRR and in no case impact
cargo mission objectives or major program milestones.

Required Service: Shuttle models provided to payload customer.

Standard: All models provided within 30 working days after request.

MER: Models delivered 5 working days late but in no case not support
payload customer design verification negotiated need date.

Standard: All models are 100% technically accurate.

MER: No errors will cause any impact to safety, mission success, or
major program schedule milestones.

Required Service: Engineering data to payload customer.

Standard: 100% of data delivered 5 months prior to launch.

MER: Data may be delivered 2 weeks late but in no case not support
payload customer negotiated need date to support major program schedule
milestones.

Standard: All engineering data is 100% technically accurate.

MER: No errors will cause any impact to safety, mission success, or
major program schedule milestones.

#### 1.2.1.4 CARGO INTEGRATION HARDWARE

The contractor shall produce and maintain cargo integration hardware
user documentation (DR 1.4.1.5.2).

The contractor shall store and maintain the inventory of Government-and
contractor-furnished cargo integration hardware. The contractor shall
install and remove cargo integration hardware as required to meet
mission manifest and cargo integration requirements. The current
inventory of cargo integration

hardware will be furnished by the Government and become
Government-owned, contractor-maintained hardware.

#### 1.2.1.5 CONFIGURATION ENGINEERING

The contractor shall develop and maintain the vehicle systems drawings
and the set of mission engineering products needed to configure the
Orbiter vehicle for payload accommodations and support flight operations
for each Shuttle flight. The contractor shall provide products
(DR's 1.2.1.5‑a and 1.2.1.5‑b).

A payload walkdown inspection shall be performed during processing which
mitigates the Space Shuttle Program (SSP) risk in the COFR process for
Internation Space Station (ISS) Cargo Elements, where accurate final CAD
models defining the Cargo Elements moldline are late. The walkdown is a
close inspection of the Cargo Element in its final configuration prior
to canister installation.

Required Service: Shuttle systems-level drawings and reconfiguration
products complete for each Shuttle flight.

Standard: 100% of all engineering products delivered in accordance with
mission schedule.

MER: 1% may be delivered late but in no case not support negotiated need
dates for compatibility with launch processing.

Standard: Engineering products contain no contractor induced technical
errors.

MER: The average error/flight shall be 6 or less. All technical errors
must be dispositioned by Orbiter Rollout for OPF processed payloads and
L-2 for pad installed payloads with no errors impacting safety, mission
success, or major program schedule milestones..

#### 1.2.1.6 LAUNCH SYSTEMS EVALUATION ADVISORY TEAM (LSEAT) CONFIGURATION AND DATABASE MAINTENANCE

The contractor shall plan, control, and perform all analyses required to
update and maintain the LSEAT configuration and databases. The
contractor shall provide the following: load indicator algorithms;
flight regime envelope databases; ET protuberance envelopes; trajectory,
loads, and end-to-end dispersions, gust, and wind persistence databases;
data evaluation and problem analysis; independent confirmation and
evaluation (audit) of LSEAT process, processors, and databases; a
comprehensive data package reflecting the effect of Day-of-Launch
I‑Loads on ascent trajectory; and an independent processor to assess the
DOLILUI-Load.

The contractor shall maintain databases, computer hardware, and software
required to support LSEAT activities in accordance with NSTS 08211 LSEAT
Integrated Support Plan. The contractor shall be provided the data
required (e.g., wind data file) to support its LSEAT activities. The
data input format shall comply with the LSEAT Integrated Support Plan.
The contractor shall participate as a voting member of the LSEAT. The
required DR's are as follows: 1.2.1.6‑a and 1.2.1.6‑b.

Required Service: Provide LSEAT configuration and database maintenance
and mission support.

Standard: All products 100% technically correct.

MER: No errors that could result in incorrect launch recommendations.

Standard: All products delivered on or before due date in support of
major program schedule milestones.

MER: No missed major program schedule milestones.

#### 1.2.1.7 RESERVED

### 1.2.2 INTEGRATION

The contractor shall provide integration engineering for mass
properties, trajectory, flight design requirements, and integration
analysis. The contractor shall interface with payload customers for
developing cargo engineering requirements, then implement and verify the
requirements have been accurately reflected in launch processing and
flight operations documentation.

#### 1.2.2.1 INTEGRATED MASS PROPERTIES

The contractor shall plan, control, compile and maintain an integrated
database system of current weights and centers of gravity for all
vehicle elements for all missions baselined in the Flight Definition and
Requirements Directive (FDRD), as well as reference missions and special
requests. The contractor shall provide the integrated mass property
products and maintenance of the database system after a 12 month
training transition period.

The database products shall provide integrated vehicle mass properties
at SRB ignition for inclusion in the TDDP. The database products shall
provide integrated vehicle mass properties at Main Engine Cut Off (MECO)
for ascent performance margin reporting. The database products shall
provide integrated vehicle mass properties at various entry trajectory
points for reporting downweights and center of gravity data. The
contractor shall utilize the best available data which will typically be
official data sources but, at times will include the exercise of
engineering judgment by the contractor for component weight and/or
performance impact estimates. The contractor shall publish reports as
electronic files accessible by all SIASS users and provide paper copies
as required. The contractor shall provide formal mass properties and
performance evaluations for all change requests affecting PIP Annex 1,
NSTS 07700, Volume III, Space Shuttle FDRD, and NSTS 17462‑XX, STS‑XX
Flight Requirements Document (FRD) ( DR 1.2.2.1‑a).

Required Service: Provide integrated mass property products.

Standard: All products are implemented and delivered in accordance with
program template milestones.

MER: 1% of the products are late but in no case impact safety, mission
success, or major program schedule milestones.

#### 1.2.2.2 TRAJECTORY DESIGN DATA PACKAGES (TDDP)

The contractor shall plan, control, and publish the TDDP using approved
baselined documentation. The contractor shall publish TDDP's which
define the required Space Shuttle systems and mission content
requirements for mission specific ascent flight design (DR's 1.2.2.2‑a
and 1.2.2.2‑b).

Required Service: Provide TDDP publication.

Standard: All TDDP products are implemented and delivered in accordance
with program template milestones.

MER: 1% of products can be late but in no case impact safety, mission
success, or major program schedule milestones.

Standard: 100% of all TDDP products are technically accurate.

MER: 0% errors that affect safety, mission success, or major program
schedule milestones.

#### 1.2.2.3 FLIGHT DESIGN INTEGRATION

The contractor shall support definition of ascent flight design criteria
and constraints based on vehicle performance. The contractor shall
provide analyses and documentation required to periodically update the
generic Main Propulsion System (MPS) inventory/budget in response to
systems or element changes affecting MPS loading or consumption (DR's
1.2.2.3‑a and 1.2.2.3‑b).

#### 1.2.2.4 ENGINEERING INTEGRATION PLAN (PIP) ANNEXES

"The contractor shall interface with payload customers and develop,
baseline, and maintain unique PIP Annex 1 in accordance with the PIP
schedule. The contractor shall maintain generic blank books. The
contractor shall provide the annexes (DR 1.2.2.4‑a).

All generic blank book changes shall be approved by NASA.

The contractor shall develop, baseline and maintain the required Mission
Integration Plans (MIPs) annexes as the ISS elements are manifested for
launch.

Required Service: Develop and baseline Integration Plan (IP) Annexes 1
(Payload Data Package)

Standard: 100% Annexes baselined in accordance with IP schedule.

MER: 10% of Annexes may be baselined late but not later than Flight

> Planning and Stowage Review, and in no case impact major

program schedule milestones

#### 1.2.2.5 ELEMENT INTERFACE CONTROL DOCUMENT (ICD)

The contractor shall maintain program level systems Interface Control
Documents (ICD's), NSTS 21000‑IDD‑ISS, NSTS 07700 Vol. XIV, Attachment 1
(ICD‑2‑19001), and NSTS 21000‑IDD‑MDK (DR 1.2.2.5). The contractor shall
prepare changes, coordinate technical review, resolve issues with the
technical community, and present changes to NASA for disposition.

Required Service: Provide maintenance of baselined ICD's.

Standard: 100% of submitted changes have all needed contractor technical
concurrences.

MER: 1 change annually may not have all contractor technical
concurrences, but in no case impact flight schedules.

#### 1.2.2.6 PAYLOAD UNIQUE ICD's

The contractor shall interface with Shuttle users and develop, approve,
publish, and maintain ICD's, Installation Requirement Documents (IRD's),
and associated drawings. Exceedances outside the experience base, and
waivers or deviations outside the requirement of NSTS 07700, Volume XIV,
NSTS 21000‑IDD‑ISS, NSTS 21000‑IDD‑MDK or NSTS 21000-IDD-SML for payload
ICD's shall be presented to NASA for disposition. The contractor shall
deliver ICD's and IRD's (DR 1.2.2.6).

Required Service: Develop and baseline ICD's and IRD's.

Standard: 100% ICD's and IRD's are baselined in accordance with flight
production schedule.

MER: 5% of ICD's/IRD's may be baselined later than the negotiated
schedules, but in no case impact major program schedule milestones.

Standard: ICD's and IRD's are 100% technically accurate.

MER: ICD's and IRD's contain no more than an average of 5 contractor
induced technical errors per ICD/IRD with all errors corrected by
Orbiter Rollout Review and in no case impact safety, mission success, or
major program schedule milestone.

#### 1.2.2.7 PAYLOAD OMRS TEST REQUIREMENTS

The contractor shall interface with the payload customer and develop all
test requirements to verify the payload interfaces with the Orbiter
vehicle. The contractor shall present these requirements to the payload
Operations and Maintenance, Requirements and Specifications (OMRS) board
for approval (DR 1.2.2.7). The contractor shall maintain these
requirements through the board change process.

Required Service: Develop and provide test requirements for OMRS
baselining.

Standard: 100% known OMRS requirements approved 10 working days prior to
LSRR program milestones.

MER: Requirements may be approved 5 working days late.

#### 1.2.2.8 TECHNICAL INTEGRATION ANALYSIS

The contractor shall provide integrated analysis of technical
requirements, problems and issues. This effort shall include, but is not
limited to, ICD, OMRS, Launch Commit Criteria (LCC), ground systems
integration and Launch Processing System (LPS) software requirements;
Program Material Review Board (PMRB), Unexplained Anomaly (UA) board
daily PRCB agenda items, Launch Site Requirements Review (LSRR), Launch
Site Flow Review (LSFR), Delta Launch Site Review (DLSR), and launch
support.

Required Service: Integrated analysis of technical changes associated
with OMRS, LCC, etc.

Standard: 100% assessments provided prior to program review milestones.

MER: 0% of assessment may be provided at program review milestone.

#### 1.2.2.9 RESERVED

#### 1.2.2.10 INTEGRATED AVIONICS

The contractor shall perform systems engineering for all SSV elements in
the areas of avionics, and electromagnetic effects (EME). This includes
Orbiter avionics, middeck experiments, cargo, cargo interfaces, and
associated ground interfaces.

The contractor shall conduct conceptual studies, system analyses and
synthesis, trade studies and perform preliminary designs, essential to
the specification of requirements for the integrated avionics system.
Also included will be the allocation of requirements among the Shuttle
hardware elements and their interface relationships. In addition, the
contractor shall review and evaluate analytical and test data from
development and flight articles to assure compliance and compatibility
with the integrated Shuttle system requirements. The required DR's are
as follows: DR 1.2.2.10‑b and 1.2.2.10‑c.

The contractor shall perform functional compatibility analyses of the
systems software, and avionics interfaces to verify that proper fault
tolerance requirements are satisfied and that proper compatibilities
exist. The contractor shall perform EME, lightning, ionizing radiation,
and electrostatic discharge compatibility analysis for all SSV elements,
including Orbiter avionics, middeck experiments, payloads, and
associated ground interfaces. The required DR is DR 1.2.2.10‑a.

11. SSV DATABOOKS

The contractor shall integrate and publish (in electronic format)
updates to all systems integration design environment data books. The
contractor shall also document all systems certification analyses in
system analysis data books. The contractor shall integrate and publish
updates to the Contingency Abort Data Book.

### 1.2.3 PROJECT INTEGRATION LIAISON

The contractor shall provide a technical liaison to SSP. The contractor
shall monitor element changes relative to compliance with SSP
requirements, coordinate project changes, and provide task plans which
detail responsibilities and schedules required to resolve identified
issues within the projects.

### 1.2.4 RESERVED

(Next page is J-1-A-24)

1.3 SAFETY, MISSION ASSURANCE AND PRODUCT ASSURANCE

The contractor shall develop, provide, and implement a management system
which is certified by third party audit to the requirements of the
ISO 9000 series of documents, including ANSI/ASQC Q9001-1994 or
equivalent within 18 months of contract award.

The contractor shall develop, document and implement the approaches to
ensure that all safety and mission assurance (safety, reliability,
maintainability, and quality) activities are implemented and are
effective in the mitigation of risk for the program, including methods
to measure their performance. The contractor shall develop an approach
to risk management which integrates safety, reliability,
maintainability, and quality issues and correlates those issues with
probability of mission success such that the contractor routinely
considers risk in day-to-day decision making and is integrated with SOW
section 1.1.1.4.

The contractor shall develop a plan, including schedule, that
demonstrates and measures the transition from the existing
contractor/government relationship and responsibilities to the
contractor's planned approach to safety and mission assurance for this
contract. The plan shall include the approach for increasing the
contractor's accountability by translating NASA policy and requirements
into auditable plans, system procedures, work instructions and the
products produced and services performed for this contract.

The contractor shall support government audit/surveillance of contractor
plans, procedures, and processes when deemed necessary by the
government. These audits/surveillances will provide understanding and
insight of processes and procedures that have been identified as
critical, out of control or have the potential for impact to future
launch schedules. Government audits/surveillances will include but are
not limited to all disciplines and tasks which are involved with or
support Shuttle launch and landing operations, hardware and software
production and maintenance, safety and quality assurance, logistics,
procurement and financial operations.

The following metrics will be used to assist in the evaluation of the
contractor performance. All performance metrics will be collected by the
contractor unless otherwise stated. Insight metrics will be available to
the Government, but will not be assigned standards of excellence,
expectations, or maximum error rates.

Risk Assessment Metrics:

These metrics will be provided for each of the following risk assessment
functions:

a\. Integration Risk Assessment

b\. System Risk Assessment

c\. Operations Risk Assessment

d\. Nonconformances Risk Assessment

Performance Metrics:

Required Service: Contractor to accurately identify and provide
information on increased risk to the Government and present to the
Government for acceptance. (Government will collect this metric.)

Standard of Excellence: 95% of risk packages presented to the Government
are accepted.

Expectation: 85% of risk packages presented to the Government are
accepted.

MER: 80% of risk packages presented to the Government are accepted.

Required Service: Contractor will correctly assess risk and may
disposition those items which pose no additional risk to the Government.

Standard of Excellence: 95% of items correctly assessed as no increased
risk validated through use, Government audit, or Government
surveillance.

Expectation: 85% of items correctly assessed as no increased risk
validated through use, Government audit, or Government surveillance.

MER: 80% of items correctly assessed as no increased risk validated
through use, Government audit, or Government surveillance.

Insight Metrics:

Percent of apparent first time successes through contractor's internal
screening process of risk assessments.

Percent of risk assessment rework that is effective (1- (number of
reworked assessments/number of rework attempts))

Assurance Metrics:

The following metrics will be provided for the quality assurance
function:

Performance Metrics:

Required Service: Assure that all critical hardware meets inspection
requirements. (Government will collect this metric.)

Standard of Excellence: 98% of all mandatory Government inspections are
accepted.

Expectation: 95% of all mandatory Government inspections are accepted.

MER: 92% of all mandatory Government inspections are accepted.

Required Service: Assure that all hardware that have designated
inspection points meet requirements.

Standard of Excellence: Success rate of SFOC work volume greater than
95%.

Expectation: Success rate of SFOC work volume greater than 90%.

MER: Success rate of SFOC work volume greater than 85%.

Insight Metrics:

Contractor Inspection Acceptance Rate (percent contractor work accepted
by contractor inspection)

Ratio of contractor surveillance acceptance rate to NASA surveillance
acceptance rate (perfect correlation is 1.0, more or less than 1.0 is
less than perfect).

The following metrics will be provided for the safety assurance
function:

Performance Metrics:

Required Service: Contractor will assure that neither non-SFOC
contractor personnel are injured nor NASA property damaged by
accidents/incidents during processing.

Standard of Excellence: 10 mishaps per year (updated quarterly)

Expectation: 15 mishaps per year (updated quarterly)

MER: 20 mishaps per year (updated quarterly)

Insight Metrics:

Ratio of contractor safety surveillance acceptance rate to NASA
surveillance acceptance rate (perfect correlation is 1.0, more or less
than 1.0 is less than perfect).

### 1.3.1 SAFETY

The contractor shall develop documented and auditable approaches to
achieve safe program operations and assure flight safety. The contractor
shall provide support to NASA safety review processes including
independent program reviews.

The contractor shall review Government Industry Data Exchange Program
(GIDEP) Alerts for their applicability to contractor sustained program
hardware. For those Alerts having an impact thereto, the contractor
shall initiate and disposition a problem report as described in SOW
Section 1.3.3.1.

#### 1.3.1.1 SYSTEMS SAFETY

The contractor shall develop and implement an approach which ensures the
identification, elimination, or control of hazards throughout the
complete life cycle (design, development, manufacture, test, operations,
maintenance, and disposal) of the program. The approach shall include
but not be limited to, analytical methods, both quantitative and
qualitative as appropriate (e.g., hazard analyses and Critical Item risk
assessments), to assess program flight and ground support hardware and
software, facilities and facilities systems and facilitate the decision
process for risk identification and mitigation; provisions for the
program approval, by the appropriate government interface, of risk
associated with hazards and critical items not eliminated by design; and
program approval, by the appropriate government interface, of
exceptions, deviations or waivers from safety requirements or other
requirements with safety or mission success impact. The approach and
results shall be documented by the contractor and auditable by the
government.

#### 1.3.1.2 OPERATIONS SAFETY

The contractor shall develop and implement an approach in which testing,
flight and ground operations and maintenance activities are assessed for
hazards and the process which NASA and other non-contractor personnel
and property will be protected from injury or harm as a result of
exposure to these hazards. The approach shall include flight design and
procedurally controlled activities. The risk assessment of operations or
task performed by persons and equipment and considers (1) the planned
system configurations at each phase of activity; (2) the facility
interfaces; (3) the planned ground and space environment; (4) the
supporting equipment; (5) task sequence; (6) the regulatory safety and
health requirements; and (7) the potential for human error. The
contractor shall report and investigate accidents resulting in damage to
NASA property or injuries to NASA or other non-contractor personnel, to
include assessments of accident impacts to cost, schedule and mission
performance, and remedial and corrective actions performed. The approach
shall cover operations both by the contractor and by other government
and non-government organizations within operational facilities
controlled by the contractor. The approach shall include provisions for
program approval, by the appropriate government interface, of risk
associated with hazards not eliminated or controlled. The approach and
results shall be documented by the contractor and auditable by the
Government.

The contractor is responsible for assuring the SSP Hazard Report
Configuration Management process conforms to NSTS 22254. This task
includes tracking of Hazard Report revisions, closure classification,
risk changes, and baseline counts; and Program Compliance Assurance and
Status System (PCASS verification.

The contractor shall provide summary data on accidents (DR 1.3.1.2‑b).

The contractor shall support the NASA Managed Safety Program for
Pressure Vessels and Pressure Systems in accordance with NMI 1710.3, NHB
1700.6, KHB 1710.15, JHB 1710, MHB 1710.10, & NASA/SSC Operations
Procedure 83-1 (DR 1.3.1.2‑c).

### 1.3.2 RELIABILITY AND MAINTAINABILITY

The contractor shall develop and implement an approach in which the
availability objectives of the program will be achieved. The approach
will include but not be limited to, assessments of reliability and
maintainability performance against baseline allocations; preparation,
maintenance, and control of reliability assessments such as Failure
Modes and Effects Analyses and assessments of materials and parts in
support of operational integrity. Reliability assessments shall identify
critical items and the operational impacts of hardware failure modes.
The approach shall be documented by the contractor and auditable by the
government.

The contractor is responsible for managing and publishing all approved
FMEA/CILs which are submitted to the Space Shuttle Program (SSP) per
NSTS 07700, Volume V, Information Management Requirements, IR 2SR-22,
CIL, IR 2SR-23 CHL, and NSTS 22206, Space Shuttle Requirements for
Preparation and Approval of FMEA/CIL in accordance with DRD 1.3.2, NSTS
08399, SSP Critical Items List and Critical Hardware List.

The contractor shall support program development efforts, as required,
to develop system reliability, availability, and maintainability
requirements and assess the designs to assure that the requirements are
met.

### 1.3.3 QUALITY ASSURANCE

The contractor shall develop and implement an approach which describes
the establishment and maintenance of a quality management system as
specified in SOW section 1.3. The approach shall include methods for the
establishment of quality goals and performance measurement and shall be
documented by the contractor and auditable by the government.

#### **1.3.3.1 PRODUCT AND SERVICE QUALITY**

The contractor shall collect and compile information derived from
empirical data (test results, analysis reports, inspection records,
delivery logs, etc.) to demonstrate that the products and services
delivered to the government are in compliance with the requirements and
specifications as specified in this contract. The delivery of the
compliance information shall be at the request of the government, either
specifically through this contract or on request of the appropriate
government interface.

The contractor shall provide and maintain, for those items that the
contractor has custody, an Acceptance Data Package in accordance with
SN-S-0008, SN-C-0007, and SSP 30695 (DR 1.3.3.1) for HW/SW delivery or
transfer to the government.

The contractor shall provide for the identification, reporting, and
elimination/disposition of non-conformances/problems/anomalies/failure
analysis in accordance with NSTS 07700 and NSTS 08126; or SSP 30223
Problem Reporting and Corrective Action (PRACA) requirements, as
appropriate, including recording anomalous system performance and
material conditions identified, providing rationale for resolution, the
remedial action performed, the recurrence control and corrective actions
taken to preclude recurrence, and determining the effectiveness of
corrective actions. The contractor shall provide access to PRACA
documentation, data, databases, analysis, and related information to the
government. The contractor shall create and sustain an open
communication with employees and subcontractors to identify, track, and
resolve non-conformances/ problems/ anomalies including close calls. The
contractor shall have a data system that allows NASA real time access to
this problem data. Initially, the contractor shall use the existing
PRACA system, but may propose improvements to the system or an alternate
system and a transition from PRACA. The contractor shall provide for
appropriate government insight, into the disposition of nonconformances/
problems/anomalies, including notifying the government of the occurrence
and, as appropriate, obtaining government approval of the disposition as
specified in SOW 1.1.1.4. The contractor shall initiate (including
requesting government approval) action to change or eliminate
requirements that non-conformance data analysis indicates are
unreasonable or unnecessary, and to improve or change processes which
produce products or services that fail to meet requirements.

#### **1.3.3.2 PROCESS QUALITY**

The contractor shall identify those fabrication, assembly, integration,
and management processes which control key product characteristics. Key
characteristics are the features of a material, part, or process whose
variation has a controlling influence on product fit, service life, or
performance, including safety or reliability. The contractor shall
measure, verify, and control the variability and stability of these
processes. The contractor shall manage the Orbiter and Cargo Integration
Certification Process associated with the certification of Contractor
Furnished Equipment (CFE), including operating and maintaining a
Certification Library.

The contractor shall, as requested, provide data or access to data, on
product and service production processes. The data shall provide insight
into product and service cost characteristics of product or service
components; product and service component delivery or receipt schedules;
and product and service component quality, including workmanship errors
and rework. The government may request this data, or access to the data,
on a continuous basis for critical processes or may request data, or
access to data, based on product cost, schedule, or quality trends. For
the processes designated as critical, the contractor shall document and
propose auditable approaches to collect, compile, analyze, and report
the data that provides government insight into the process.

## 1.4 FLIGHT ELEMENTS

**General Processing Requirements**

Flight element processing consists of all testing and maintenance
(planned and unplanned) required to verify flight element system
condition and performance is within specified limits and to ready the
flight element for integrated processing in preparation for launch.
Integrated processing consists of all testing and maintenance required
to bring the flight elements together ready for launch. The transition
from integrated processing to flight element processing is at the last
operation after element de-integration (e.g., Orbiter wheel stop in the
Orbiter Processing Facility \[OPF\] or Mate Demate Device at Dryden
Flight Research Center \[DFRC\], SRB/RSRM ready for shipment after
disassembly).

The contractor shall develop and maintain procedures (DR 1.4‑a). The
contractor shall perform all flight element processing activities in
accordance with approved work authorization documents to assure that
these elements operate within all the design specifications, drawings,
and OMRS. Procedure development and distribution metric is covered in
SOW Section 1.5.

The contractor shall provide Safety, Mission Assurance and Product
Assurance for all element hardware and software as defined in SOW
section 1.3.

The contractor shall implement the planning and control and perform
contingency operations that may arise during the flight element's
processing to support unplanned program contingencies (e.g., hurricanes,
launch abort/turnarounds, etc.) as identified in SOW Section 1.1.1.1 and
Exhibit 1.1.1.1.

The contractor shall report and resolve anomalies in compliance with
NSTS 07700 and NSTS 08126, or SSP 30223 PRACA Requirements, as specified
in SOW section 1.3. The contractor shall refer to SOW section 1.1.1.4
for out of family anomaly reporting requirements.

The contractor shall develop troubleshooting and analysis plans, repair
dispositions, and acceptance rationale. The contractor shall perform
troubleshooting, analysis, repair, retest, failure analysis, corrective
action, trend analysis and follow-up to determine effectiveness of
corrective actions. The contractor may perform approved standard repair
procedures, repairs which restore hardware to specification, and
hardware removal and replacement in accordance with SOW section 1.1.1.4.

The contractor shall ensure all Government and contractor personnel are
properly trained or certified, as required, by providing required
training or certification before participation in operations or in work
areas.

**General Logistics Requirements**

The contractor shall provide a fully operational logistic system that
improves productivity and minimize organizations providing like kinds of
products and services.

The contractor shall procure hardware items from certified suppliers,
manufacture hardware items if certified as a supplier, or repair failed
hardware using a certified facility. In addition, to maintaining flight
equipment assigned to flight element contractors, the contractor shall
maintain flight and flight-type equipment assigned to ground support
equipment, simulators, and off-line laboratories. Manufacturing,
procurement, and repair of hardware items shall be consistent with
Program requirements and directives. The contractor shall utilize
existing certification plans for all manufacturers, repair depots, and
support laboratories. The plans shall comply with Program requirements
and directives. As the SFOC acquires additional work through subsequent
phases, new plans or changes to the existing plans shall be submitted to
the Government for approval. Procurement, manufacture, and repair
performance shall be reported (DR 1.4‑c).

The contractor shall provide spares and consumables required to support
the hardware, support equipment, and processing activities. The
contractor shall provision these assets at the line replaceable unit
(LRU), shop replaceable unit (SRU), and piece-part/consumable levels.
The contractor shall monitor and document hardware spares balances. The
contractor shall provide a forecast for Government Furnished Materials
(GFM) (DR 1.4‑d). Spares & consumables replenishment performance shall
be reported (DR 1.4‑c).

The contractor shall identify and resolve hardware and component
obsolescence issues and loss of failure analysis, production and repair
capabilities in compliance with Program management and control
requirements (DR 1.4‑e). Loss of capabilities includes, but is not
limited to, loss of skills or a supplier going out of business. The
contractor shall obtain government approval for hardware changes as
required by NSTS 07700 and SSP 41170.

The contractor shall provide the engineering for hardware that includes,
but is not limited to, initial parts requirements, logistics support
analysis, and maintenance planning. Included in logistics engineering
support is test equipment, tooling, process certification, and repair
documentation. Test equipment shall be maintained (DR 1.5.5.2). The
contractor shall report unresolved maintenance action issues to the
government (DR 1.4‑c).

The contractor shall provide transportation, shipping ,receiving
,storage, warehousing and distribution services. Transportation services
shall include

hardware and equipment transportation for routine and contingency
operations. Transportation, shipping & receiving performance shall be
reported (DR 1.4‑c).

The contractor shall provide service with no hardware damage due to
transportation or storage. Minor damage judged to be in the range of the
acceptable wear and tear specification or able to be repaired on-site by
standard repair or Material Review action is acceptable, but in no case
shall minor damage impact safety, mission success or major program
schedule milestones. Damage shall be reported in accordance with SOW
Section 1.3.1.2.

The contractor shall maintain an inventory management system.

The contractor shall maintain inventory levels throughout the contract
period and report the levels (DR 1.4‑c).

The contractor shall minimize hazardous waste materials and report in DR
1.4-c. For hazardous waste generated by processes in this program but
not under the control of the contractor, the contractor shall initiate
and coordinate with NASA reduction efforts.

Required Service: Provide hazardous waste material weight reduction for
hazardous waste under the control of the contractor.

Standard: Reduce hazardous waste material weight no less than 10% over
each year.

Expectation: Reduce hazardous waste material weight no less than 5% over
each year.

MER: No reduction in hazardous waster material weight.

The contractor shall identify excess or obsolete assets and initiate
excessing action. Receipt and disposal of excess property is a
government provided service identified in Attachment J-10. Property
excessing performance shall be reported (DR 1.4‑c).

The contractor shall provide training and certification for all
personnel, including Government and contractors, who participate in
operations or in work areas. Certification when required shall verify
that individuals are fully knowledgeable of the laws, regulations and
NASA directives concerning their task(s).

The contractor shall participate in the ALERT System and prepare and
provide ALERTs to the Government. The contractor shall identify the
affected hardware and start an analysis of the problem with
recommendations and/or corrective actions as part of their response.

### 1.4.1 ORBITER

The contractor shall plan, control, and perform Orbiter engineering
processing activities.

#### 1.4.1.1 MISSION AND TURNAROUND REQUIREMENTS

The contractor shall perform mission and vehicle compatibility analyses
in preparation for flight support and provide real-time mission
execution engineering support. The contractor shall evaluate Orbiter
system performance from the start of launch countdown through completion
of the postlanding checklist and crew egress to verify Orbiter hardware
and system performance is as expected, and to provide assessments for
"go/no-go" launch decisions to the Government. The contractor shall
evaluate prelaunch and in-flight anomalies, provide assessments of the
systems' ability to safely launch and complete mission objectives, and
provide pre-launch or in-flight corrective, remedial, or contingency
action recommendations including in-flight maintenance or changes to the
flight plan or crew procedures to the Government. The contractor shall
retain in-flight checkout data for all completed flights and provide
access to NASA. The contractor shall evaluate all documented Orbiter
flight verification requirements performed during flight operations and
report all requirements not accomplished to NASA. The contractor shall
identify, document and provide NASA with access to all
out-of-specification flight verification results. The contractor shall
provide systems engineering to sustain operational performance
validation, anomaly resolution, corrective action disposition and
mission analysis efforts as required to support the certificate of
flight readiness.

The contractor shall coordinate facility, communications and telemetry
requirements for flight operations support activities conducted at
NASA's flight operations support sites with NASA. The contractor may
support flight operations from remote sites.

The contractor shall provide accurate Orbiter vehicle configuration
engineering and verification requirements for each flight as required to
support the mission manifest. The contractor shall establish and
document Orbiter turnaround maintenance requirements and specifications
(DR 1.4.1.1.3-a). The contractor shall submit changes to the JSC 08934
Shuttle Operational Data Book (DR 1.4.1.6.1-a). The contractor shall
analyze Orbiter vehicle configuration, mass properties, certification
status, and anomaly dispositions (DR 1.4.1.6.1-d) to determine whether
the requirements for each pending mission have been complied with. The
contractor shall prepare or evaluate launch commit criteria and flight
rule changes. The contractor shall prepare vehicle configuration and
measurement information (DR's 1.4.1.6.1-f and 1.4.1.6.1-g) for launch
and flight support. The contractor shall provide Orbiter engineering and
technical support

for the Orbiter processing operations identified in SOW paragraphs
1.4.1.2, 1.4.1.3, 1.4.1.4, and 1.5. These activities shall encompass
vehicle subsystems, including the Waste Collection System.

Required Service: Obtain timely product deliveries from the Orbiter
Element Subcontractor.

Standard: A score of 105% or better for the product delivery metric.

Expectation: A score of 97% or better for the product delivery metric.

MER: A score of 90% or better for the product delivery metric.

The product delivery metric is computed by initializing the metric at
100%, then adjusting as follows:

Adding 1% for each product delivered 1-5 days early.

Adding 2% for each product delivered 6 or more days early.

Subtracting 2% for each product delivered 1-5 days late.

Subtracting 4% for each product delivered 6 or more days late.

Any product defined as a DRD in the subcontract is considered a product
for computing the metric. "As required" products are considered on time
when delivered.

**1.4.1.1.1 MEDS OPERATIONAL SUPPORT**

 

The Contractor shall provide the required engineering resources to
support resolution of MEDS hardware issues/anomalies, which may be
identified during vehicle turnaround activities, SAIL/JAEL testing,
SMS simulations or mission operations. The Contractor shall provide
engineering support to (1) functional design change analysis, (2)
verification of MEDS compatibility with Orbiter avionics systems and,
(3) resolution of interface compatibility issues.

**1.4.1.1.2 MEDS OEM HARDWARE ENGINEERING SUPPORT**

The Contractor shall proceed with effort required to support the MEDS
OEM Hardware Engineering support activity.

The Contractor shall provide engineering technical oversight of all
test, tear-down & evaluation (TT&E), failure analysis, repair, and
acceptance test activities with MEDS hardware at the OEM. The Contractor
shall conduct vulnerability analysis and supportability planning
activities.

This effort shall provide support for MEDS hardware, which has been
formally transferred to the SFOC prime contract.

#### 1.4.1.2 ORBITER LOGISTICS

The contractor shall provide Orbiter logistics functions in a manner
consistent with SOW section 1.4 for hardware element accountability and
general logistics requirements. The contractor shall obtain government
approval before cannibalizing Orbiter hardware to fill requests or
removing hardware prior to OMDP to support fill requests. Performance
shall be reported in accordance with DR 1.4‑c. Hardware provisioning
shall include all spares and consumables for Orbiter processing and
flight, including the Waste Collection System. High Value Spares,
replacement parts with a unit cost of \$1M or more, shall be subject to
the procedures of Article H.35, [Program Provisioning
Procedures]{.underline}. Hardware configuration management shall be in
compliance with the requirements specified in JSC 09082 with
implementation as defined in SOW section 1.4.1.1 and 1.4.1.5.
Replacement/Upgrades of Orbiter Logistics special test equipment (STE)
with a unit cost of more than \$500K shall be subject to the procedures
of Article H. 35, Program Provisioning Procedures.

Required Service: Provide reparable hardware required for Orbiter
processing and flight.

Standard: 97.0% of all reparable Orbiter hardware requirements satisfied
by the negotiated need date.

Expectation: 96.0% of all reparable Orbiter hardware requirements
satisfied by the negotiated need date.

MER: No less than 90.0% of all reparable Orbiter Hardware requirements
satisfied by the negotiated need date.

Required Service: Provide nonreparable hardware required for Orbiter
processing and flight.

Standard: 98.7% of all nonreparable Orbiter hardware/consumable
requirements satisfied by the negotiated need date.

Expectation: 97.7% of all nonreparable Orbiter hardware/consumable
requirements satisfied by the negotiated need date.

MER: No less than 96.7% of all nonreparable Orbiter hardware/consumable
requirements satisfied by the negotiated need date.

Required Service: The contractor shall identify to the Government any
LRU's with the potential for cannibalization within the next 6-month
period. Each cannibalization of hardware shall be reported to the
Government no more than 8 hours after occurrence.

Standard: Fewer than 0.075% of all Orbiter hardware requirements
satisfied by cannibalization.

Expectation: Fewer than 0.1% of all Orbiter hardware requirements
satisfied by cannibalization.

MER: No more than 0.2% of all Orbiter hardware requirements satisfied by
cannibalization.

Required Service: The contractor shall provide hardware which is
suitable for use upon receipt at the Kennedy Space Center or other
locations where Shuttle processing/servicing is conducted.

Standard: 100.0% of received hardware passes physical and functional
interfaces.

Expectation: At least 99.7% of received hardware passing physical and
functional interfaces.

MER: No less than 99.5% of received hardware passing physical and
functional interfaces.

Required Service: Provide TPS hardware required for Orbiter processing
and flight.

Standard: 99.0% of all Orbiter TPS requirements satisfied by the
negotiated need date.

Expectation: 95.0% of all Orbiter TPS requirements satisfied by the
negotiated need date.

MER: 93.0% of all Orbiter TPS requirements satisfied by the negotiated
need date.

#### 1.4.1.3 ORBITER TURNAROUND PROCESSING

The contractor shall plan, control and perform all turnaround processing

activities in a manner consistent with SOW section 1.4 for hardware

accountability and general processing requirements. The contractor shall

prepare the Orbiter for flight, including special action requirements
(DR

1.4.1.1.2-a) and support for integrated operations as specified in SOW
section 1.5.

This shall include off-line turnaround processing of LRUs. The
contractor

shall accomplish all documented Orbiter ground turnaround configuration
and verification requirements and report all requirements not
accomplished to NASA. The contractor shall identify, document and
provide NASA with access to all out-of-specification turnaround
verification results. The contractor shall assess, plan, prepare, and
execute modification and mission kit installation work authorization
documents and conduct subsystem and system verification testing.

Required Service: Verification of vehicle and systems performance
readiness.

Standard: All ground verification requirements completed or
dispositioned through appropriate NASA forums.

Expectation: No processing operations executed without properly
completed or dispositioned verification of pre-requisite requirements.

MER: No processing operations executed without properly completed or
dispositioned verification of pre-requisite requirements.

#### 1.4.1.4 ORBITER FERRY OPERATIONS

The contractor shall plan, control, and perform operations required to
prepare and ferry the Orbiter. These processing tasks include the
planned and unplanned work performed on the Orbiter, and integration
with the government-provided Shuttle Carrier Aircraft (SCA) in the
Mate/Demate Device (MDD) or other lifting fixtures/devices required to
prepare the vehicle and disposition anomalies for ferry flight. These
processing tasks shall include routine, planned and unplanned processing
and maintenance operations and verification procedures which determine
the operational status and condition of the flight element's systems
prior to ferry flight. Also included are the ground support operations
performed at intermediate stopovers. If the Orbiter is ferried to or
from the OMDP site, the contractor shall perform pre-ferry deservicing
preparations and post-ferry reconfiguration activities encountered
during OMDP.

5.  ORBITER HARDWARE PRODUCTION

The contractor shall plan Orbiter design changes, perform impact
assessments, produce modification and mission kits, prepare and execute
installation work authorization documents, and conduct subsystem and
system verification testing. Hardware configuration management shall be
in compliance with the requirements specified in JSC 09082 with
implementation in accordance with a NASA approved implementation plan.
The contractor shall plan and perform inspections and verification
testing specified for accomplishment during OMDP. The contractor shall
manage and maintain Production assets.

Required service: Provide high quality Orbiter modification hardware,
OMDP, and ET umbilicals.

Standard: The absence of Inflight Anomolies (IFAs) of Orbiter
modification hardware, OMDP, and ET umbilicals attributed to the
Contractor's performance which preclude accomplishment of major mission
objectives.

MER: Successful accomplishment is evidenced by the absence of IFAs's
attributed to the Contractor's performance which preclude accomplishment
of major mission objectives.

##### 1.4.1.5.1 RESERVED.

##### 1.4.1.5.2 HARDWARE, MODIFICATIONS, AND SUPPORT

The effort defined herein shall be specifically authorized under the
Program Provision Procedure as defined in Schedule Article H.35,
entitled Program Provisioning. The contractor shall provide engineering
design capability to

accomplish any necessary changes required to preserve original design
requirements compatibility and certification, and to support assessment
of new capability developments as might be initiated by NASA. The
contractor shall perform operational and implementation impact
assessments of all proposed or approved Orbiter (hardware/software)
design changes.

The contractor shall design, develop, produce, verify and deliver
certified Orbiter hardware, Orbiter hardware mission kits embedded
software, and system modifications (DR's 1.4.1.5.1‑a, 1.4.1.5.1‑b, and
1.4.1.5.1‑c). The contractor shall produce engineering drawings and
associated lists, configuration documentation, performance verification
requirements and specifications, and acceptance data packages (DR
1.3.3.1) for the mission and modification kits that comply with the
Orbiter Vehicle End Item Specification, MJ070-0001-1D. The contractor
shall produce and submit Orbiter engineering design (DR 1.4.1.1.1-b) and
specification (DR 1.4.1.1.1-c) changes for approval. The contractor
shall control and track all Orbiter materials (DR 1.4.1.1.1-d).

Required Service: Ensure vehicle modification product quality

Standard: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non- conformances per 1000 direct labor hours) shall be no more
than 3.0/KDLH.

Expectation: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non- conformances per 1000 direct labor hours) shall be no more
than 4.5/KDLH.

MER: Product assurance (inspection) verification of hardware attributes
during manufacturing as reported in the product quality report (non-
conformances per 1000 direct labor hours) shall be no more than
6.0/KDLH.

##### 1.4.1.5.3 ORBITER OMDP

The contractor shall perform operational impact assessments of Orbiter
design changes, prepare the work authorization documents, install the
changes during Orbiter Maintenance Down Periods (OMDP), and conduct
subsystem testing. The contractor shall assess, perform and validate
modifications; kit installations and Special Action Requests (SAR). The
contractor shall plan and perform inspections and verification testing
specified for accomplishment during OMDP.

The work required for the OV-104 OMDP is included in the SFOC as a
result of Modification 271 and as defined by the latest Program
Requirements Control Board Directive (PRCBD) S063124DR5 that baselines
mods performed during OMDP for OV-104.

##### The work required for the OV-102 (J3) OMM/OMDP is included in the SFOC as a result of modification 707 and as defined by the latest Program Requirements Control Board Directive (PRCBD) S063132 that baselines mods performed during OMM/OMDP for OV-102 (J3). 

The work required for preparation and submission of initial budgetary
estimates, Not-To-Exceed estimates for Pre-Planning efforts, and
provision of a decision package for the accomplishments of the OV-103
(J3) OMM at Palmdale is included in the SFOC as documented in Decision
Package MV-INC-02-02.

The Contractor shall perform OMDPs as core contract effort, as defined
in the latest Program Requirements Control Board Directive (PRCBD) that
baselines the mods for each OMDP.

##### 1.4.1.5.4 ORBITER/EXTERNAL TANK UMBILICALS

The contractor shall develop, produce, and deliver Orbiter/External Tank
umbilicals. The delivery schedule for the Orbiter/External Tanks
umbilical disconnects LO2/LH2 ship sets is listed in contract Attachment
J-20.

Required Service: Provide ET umbilicals.

Standard: All ET umbilicals delivered by the negotiated delivery date.

Expectation: No more than 1 ET umbilical shipset delivered more than 15
days after the negotiated delivery date.

MER: No more than 1 ET umbilical shipset delivered more than 30 days
after the negotiated delivery date.

Required Service: ET umbilical product quality.

Standard: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non-conformance's per 1000 direct labor hours) shall be no more
than 4.0/KDLH.

Expectation: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non-conformance's per 1000 direct labor hours) shall be no more
than 5.5/KDLH.

MER: Product assurance (inspection) verification of hardware attributes
during manufacturing as reported in the product quality report
(non-conformance's per 1000 direct labor hours) shall be no more than
7.0/KDLH.

The contractor shall provide for the production and assembly of shipsets
140 through 179, provide 10 shipsets of GSE/storage containers, 100
shipsets of follower arm torsion bars and 100 shipsets of main drive arm
torsion bars. Production and delivery of shipsets 140 to 179 and
ancillary components shall occur as described in attachment J-20.

##### 1.4.1.5.5 CAPABILITY DEVELOPMENT

The contractor shall provide the capability to assess, develop, design,
produce, and certify selected hardware.

#### 

### 1.4.2 SOLID ROCKET BOOSTER (SRB)

The Contractor shall acquire, refurbish, manufacture, assemble, and
checkout SRB flight hardware and associated hardware; as well as plan,
control and perform SRB processing activities, in support of Schedule
Article H.33.

#### 1.4.2.1 SRB ELEMENT PROCESSING

The contractor shall perform SRB processing using hardware and the
associated certified documentation. The contractor shall perform all
processing activities associated with the SRB hardware in support of the
integrated operations phase of the STS as specified in SOW section 1.5.
The contractor shall support acceptance reviews, test requirements,
stacking, anomaly resolution and deviations/waivers. . The contractor
shall perform processing impact assessments, process requirements,
install, validate and test modification kits. DRD's: 1.4.2.1-a,
1.4.2.1-b, 1.4.2.1-d, 1.4.2.1-e, 1.4.2.1-f, and 1.4.2.1-g.

1.  MULTIPLEXER -- DEMULTIPLEXER (MDM) DEVELOPMENT

In accordance with CPA Package MSFC M-037, 51 flight MDM and 11
non-flight MDM's shall be modified with a redesigned circuit card which
has a relocated solder lug that eliminates the possibility of contact
with adjacent circuit cards in the MDM. These modified MDM's will be
installed in Integrated Electronic Assemblies (IEA) except one of the 11
non-flight IEA is an engineering unit that does not require an MDM. The
modified MDM's and IEA's shall be identified with new nameplates to
identify the new configuration.

#### 1.4.2.2 SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT

The contractor shall refurbish, manufacture, test, assemble and perform
acceptance checkout (ACO), on the SRB hardware/systems.

In addition Forward Skirts S/N 1 and 2, which have not previously flown,
shall be refurbished and reconfigured in accordance with Certification
Plan USB-STR-001, Rev. 3 in order to enter the flight inventory.

1.  CABLE TESTS

In accordance with CPA Package MSFC M-073, Paragraph 2.1 Work
Description, the contractor shall perform dynamic continuity (flex or
wiggle) tests on all cables except for coax, perform NDE X-ray on all
new purchased cables, and perform make/buy analysis on cables.

#### 1.4.2.3 SRB STAND ALONE LOGISTICS

The Contractor shall provide the necessary level of stand alone, SRB
unique logistics to support all SRB tasks. The contractor shall conduct
a periodic review of stand alone, SRB unique logistics to identify areas
where performing an integrated logistics function would enhance the
efficiency or effectiveness of the overall SRB logistics activity.

1.  CABLE QUANTITIES

In accordance with CPA MSFC M-073, the contractor shall provide cables
based on converting ETA Ring Cables to expendable, reduce Forward and
Aft Tunnel cables to a five mission use for STS-105 through STS-115
transitioning to expendable for STS-116 and subsequent missions, and
Forward Separation Bolt Cable mission life from 20 to 5.

#### 1.4.2.4 INTEGRATED LOGISTICS

The Contractor shall be free to migrate any or all SRB stand alone
logistics activities into their overall integrated logistics process.
The contractor shall provide this integrated logistics function in a
manner consistent with SOW section 1.4 for hardware element
accountability and general logistics requirements. The contractor shall
obtain government approval before cannibalizing SRB hardware to fill
requests. Performance shall be reported in accordance with (DR 1.4
Modified).

Required Service: Provide reparable hardware required for SRB processing
and flight.

Required Service: Provide nonreparable hardware required for SRB
processing and flight.

Required Service: The contractor shall identify to the Government any
LRU's with the potential for cannibalization within the next 6-month
period. Each cannibalization of hardware shall be reported to the
Government no more than 8 hours after occurrence.

Required Service: The contractor shall provide hardware which is
suitable for use upon receipt at the Kennedy Space Center or other
locations where Shuttle processing/servicing is conducted.

####  1.4.2.5 SRB FLIGHT SYSTEMS DESIGN RESPONSIBILITY

The Contractor shall be responsible for the design, performance,
configuration control and certification of SRB Flight hardware delivered
and refurbished under this Contract, as defined in PART 1 CEI
Specification 10CEI‑0001, latest approved revision. The Contractor\'s
design responsibility for SRB hardware, excludes the Reusable Solid
Rocket Motor (RSRM) and the associated RSRM Ignitor/Heater Power Cables,
and NASA Standard Initiator's (NSI's) and NASA Standard Detonator's
(NSD's).

The Contractor shall be responsible for the technical integration of all
elements of the booster, including the RSRM.

The Contractor shall be responsible for SRB Loads & Environments
criteria and requirements. Responsibility includes development,
analyses, update & control activities of the following products: SRB
Design Loads, SRB Integrated Thermal Environments, SRB Decent Trajectory
Database, SRB Structural Math Models, SRB/RSRM Interface Loads, SRB
Thermal Design Data, SRB Load Indicator Equations, and Vibration, Shock,
& Acoustic Design/Test Criteria. Effective 10/1/99, responsibility for
the following products will be added: SRB Ascent & Descent Venting
Environments, Descent Thermal Environments, High-Frequency Component
Loads, Ascent & Descent Aerodynamics, and Descent Acoustic Environments.

The Contractor shall be responsible for integrating, preparing and
maintaining complete SRB mass properties. Electronic data files are to
be supplied to NASA JSC for Space Shuttle Vehicle Integration.

The Contractor shall perform sustaining engineering to maintain the \"as
designed\" configuration of SRB hardware, and to assure that the designs
for flight hardware items are functionally and physically compatible
with interfacing elements of the Shuttle vehicle, ground support
equipment, checkout equipment, and associated handling and launch
equipment.

The contractor shall continue to perform all authorized SRB Hardware
Upgrades, GSE Upgrades, Process Improvement Initiatives, Materials
Replacement Initiatives, and Environmental Compliance Initiatives that
have been initiated by agreement between USBI and NASA, prior to
contract ATP. The contractor shall continue these tasks without change
to requirements, schedules, or deliverables, unless specifically
authorized by NASA.

#### 1.4.2.6 SRB ELEMENT PROCESSING, GROUND SYSTEMS DESIGN RESPONSIBILITY

The contractor shall perform sustaining engineering for SRB facilities,
facility systems, and Ground Support Equipment (GSE), which are used to
support SRB Element Processing. This sustaining engineering support
shall be provided in accordance with the requirements of SOW paragraph
1.5

#### 1.4.2.7 SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT, GROUND SYSTEMS DESIGN RESPONSIBILITY

The contractor shall perform facilities sustaining engineering for the
ARF (Assembly Refurbishment Facility) and the PRF (Parachute
Refurbishment Facility). The contractor shall perform sustaining
engineering on all SRB unique facility systems, and SRB unique Ground
Support Equipment (GSE), used in the ARF, PRF, and in the SRB hardware
refurbishment areas of Hangars AF, M, and S.

#### 1.4.2.8 SRB RECOVERY OPERATIONS 

The contractors shall support integrated operations as identified in SOW
section 1.5.4.4.

#### 1.4.2.9 RSRM STATIC FIRING SUPPORT

The Contractor shall provide on‑site labor, equipment, spare/repair
parts, components, and materials to the RSRM Contractor necessary to
support readiness reviews, equipment servicing, assessment of hardware
subjected to motor static firings, and repair/replacement of failed SRB
equipment components for static firings.

#### 1.4.2.10 SRB MODIFICATIONS

The element contractor shall provide SRB modification kits required for
ground processing to support the operations phase of the STS. The
contractor shall perform operational impact assessments, process
requirements, install, validate and test modification kits.

#### 1.4.2.11 SRB FACILITY TOOLING, EQUIPMENT, AND MINOR CONTRUCTION, ALTERATION, AND REPAIR (MCAR)

The Contractor shall acquire and utilize facilities equipment and
tooling, and provide for minor construction, alteration and repair to
existing facilities.

#### 1.4.2.12 ACQUISITION SUPPORT

The Contractor shall procure Aft Separation Bolts and NSI pressure
cartridges for the Tail Service Mast. In addition, the Contractor shall
procure and ship System Tunnel Floor Plates and Nozzle Rain Shield
Attach Strips to the RSRM Contractor to support each mission.

### 1.4.3 FLIGHT SOFTWARE

The contractor shall develop, verify, and implement flight software for
the SSP. The Primary Avionics Software System (PASS), back-up flight
system (BFS), *Multifunction Electronics Display Subsystem (MEDS)*, and
avionics system support activities are to be managed by the contractor
with the direct involvement of the government in accordance with the
baselined software processes (SCR 89050-SASCB Process Documentation
Overview).The contractor shall perform requirements analysis, design,
development, certification, testing, and maintenance of the avionics
software for the Data Processing System (DPS) of the Space Shuttle
Orbiter. The contractor shall establish general and specific interfaces
with other NASA selected contractors for coordination and data exchanges
necessary in the formulation, execution, and verification of Shuttle FSW
and FSWAT ground software.

#### 1.4.3.1 ORBITER AND BFS FLIGHT SOFTWARE PROCESSING AND TOOLS

"The contractor shall provide development and maintenance of individual
software packages and integrated software systems necessary to provide
for avionics flight software (FSW) development, certification,
reconfiguration, testing, and verification in accordance with the
current baseline process (SCR 89057-Flight Software Application Tools
\[FSWAT\] Process). The contractor shall develop and maintain all FSW
application tools unique to the development, reconfiguration, and
maintenance of the Shuttle onboard BFS FSW. DR's associated with this
activity are: DR 1.4.3.1‑a, 1.4.3.1‑b, and 1.4.3.1‑c.

"The contractor shall maintain configuration control of all FSW products
delivered to NASA. Configuration control shall provide full traceability
from NASA approved requirements to the individual items delivered and
shall be applied to each operational increment (OI) or Shuttle FSW
build. The contractor shall utilize a configuration management database
to support the configuration control and coordination of the contractor
and NASA boards. This support shall include report generation,
configuration audits, control board administration, and control
documentation. The DR's associated with this activity are: 1.4.3.1‑d,
and 1.4.3.1‑g.

"The contractor shall support computer access security, data integrity,
implementation, test, and maintenance of the Software Development
Facility (SDF) for all coding of BFS and FSW application tools. The
overall computer security and data integrity requirements shall be
consistent with the Automated Information System Security Manual
(JSC-2410.11).

"The contractor shall maintain the MAST database including definition
and incorporation of hardware component calibration coefficients and
curves, measurement channelization, and telemetry format requirements in
accordance with current baseline process CR 89053-MAST II/STAR
Reconfiguration. The Contractor shall resolve payload data interleaver
compiler bandwidth and instruction issues encountered as a result of SSV
hardware modifications. The contractor shall provide a "help desk"
capability to facilitate user interaction. DR's associated with this
activity are: DR 1.4.3.1‑k, 1.4.3.1‑n, and 1.4.3.1-q.

"The contractor shall be provided GFE flight software products, perform
pre-installation processing, install as a total or partial load and
perform memory dumps and compares to ensure proper installation.
Included is the assessment of the software delivery to determine any
GOAL application/procedure impacts and the provision of test support and
procedure execution.

Required Service: Provide BFS Software Approval Sheet (SAS) and test
patches.

Standard: Released software patches are 100% technically accurate,
complete in content and delivered on the negotiated schedules.

Expectation: Slips or redelivery caused by BFS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in released test patches caused by BFS for crew training
or testing which cause impacts to mission safety, mission success or
scheduled launch date."

#### 1.4.3.2 FLIGHT SOFTWARE TESTING

The contractor shall verify that performance of the integrated SSV
avionics system hardware, software, and its associated interfaces meets
program requirements. Elements included in the integrated avionics are
the PASS, the BFS, and all SSV avionics hardware/software elements
including the SSME controller.

The contractor shall prepare avionics system verification test
requirements which utilize SAIL, Software Reconfiguration Facility
(SRF), audits, or other appropriate methods to assess system compliance
with requirements. Verification requirements shall be provided for:
Mission verification, new OI testing, SAIL regression testing, Shuttle
hardware upgrade verification, SAIL site acceptance, and system
integration verification. Mission unique testing shall include software
patches, DTO's, and general purpose computer memory patches (GMEMS)
(DR's 1.4.3.2‑a, 1.4.3.2‑b, 1.4.3.2‑c, and 1.4.3.2‑d.).

The contractor shall provide real-time support to SAIL testing or
verification testing at other sites as applicable to confirm that the
verification test requirements are properly executed, anomalies
identified, and the appropriate data products are produced. The
contractor shall post process, analyze test data, report anomalous
results, and participate in discrepancy resolution. The contractor shall
track, review, and provide technical support/expertise for closure of
flight system/software anomalies, interim discrepancy reports, and
discrepancy reports resulting from integrated avionics verification
testing. For each flight, the contractor shall prepare and present a
summary of open SAIL anomalies and avionics system discrepancy reports
and identify constraints to flight (DR 1.4.3.2‑f).

The contractor shall provide closed loop accounting of all avionics
system change verification and make reports to the SSP on a flight to
flight basis and for each new OI release. The contractor shall provide
verification flight readiness inputs to NASA (DR's 1.4.3.2‑g and
1.4.3.2‑h).

#### 1.4.3.3 AVIONICS AND SOFTWARE SYSTEM SUPPORT

The contractor shall be responsible for all aspects of the associated
principal function (PF) software design as defined in the STS Flight
Software Functional Subsystem Software Requirements (FSSR), Space
Shuttle Computer Program Development Specifications (CPDS), and Program
Requirements Document (PRD). This role is designated as Principal
Function Manager with the responsibility to serve as the primary expert
for all aspects of each FSW PF. The contractor shall be responsible for
all aspects of the design, definition, and mission selection of I-load
categories and occurrences for associated PF as defined in the FSSR and
PRD. This role is designated as I-load Manager with the responsibility
for one or more I-load categories. SASCB SCR 89350, SASCB FSW
Requirements Management Assignment Baseline, and SCR 89049, JSC and
Contractor I-load Owner Assignment, governs the individual designations.

The contractor shall develop and establish flight software change
requirements for STS missions, Orbiter Maintenance Modification
processing, and pre- and post-launch ground checkout. The contractor
shall prepare FSW change proposals and change requests and provide
recommendations for long term definition of OI changes as defined in the
Shuttle Avionics Software Control Board (SASCB) 3 year plan. The
contractor shall provide impact assessments and recommendations to the
SASCB in response to FSW changes proposed by FCP, SCR, I-Load DCR, DR,
RIT, SSME Software Authorization Notice (SAN), or Requirement Change
Notice (RCN) in accordance with the current baselined software
processes, SCR 89051 - Space Shuttle Software Change Request (SCR)
Process, SCR 89052 - Space Shuttle Flight Software Discrepancy Report
Procedures, SCR 89054 - I-Load Data Change Request (DCR), and SCR
89056 - SSMEC FSW process (DR's 1.4.3.3‑c, 1.4.3.3‑f, and 1.4.3.3‑y).

The contractor shall develop the payload and vehicle requirements needed
to reconfigure the appropriate software for Shuttle vehicle and ground
facilities in support of SSP mission. The contractor shall work with
payload suppliers and the Shuttle community in order to develop the
requirements necessary to perform flight specific data reconfiguration.
The contractor shall maintain a detailed flight specific requirements
document that defines the design requirements and constraints for each
flight (DR's, 1.4.3.3‑e, 1.4.3.3‑g, 1.4.3.3‑k, and 1.4.3.3‑y).

The contractor shall maintain FSW requirements documentation including
the CPDS, FSSR, and PRD. The contractor shall update this documentation
and the PASS/BFS Interface Control Documents for each approved OI. The
contractor shall maintain an I-load Selection Criteria data book with
which to perform an independent selection of I-loads for mission
reconfigurable parameters. The contractor shall provide Software Version
Description Documentation for each BFS data set delivered (DR's
1.4.3.3.‑o, 1.4.3.3‑p, 1.4.3.3‑q, 1.4.3.3‑s, 1.4.3.3‑t, 1.4.3.3‑u, and
1.4.3.3-w).

Required Service: Provide I-load Selections

Standard: Delivered I-loads 100% accurate.

Expectation: No errors requiring redelivery which impacts I-load
development schedules or requiring patch for flight.

MER: No errors which impact safety, mission success, or major program
schedule milestones.

The contractor shall perform functional compatibility analyses of the
DPS hardware, systems software and avionics interfaces to verify that
proper fault tolerance requirements are satisfied and that proper
compatibility exists. The contractor shall establish/evaluate the
requirements for the DPS software including Flight Computer Operating
System (FCOS), User Interface (UI), Systems Control (SC)-redundancy
management, and generic Uplink (UL) for proper control and performance
of the DPS. The contractor shall perform integrated DPS related systems
assessments, and present recommendations for preflight/flight/postflight
technical issues, anomalies, and problems potentially affecting flight
readiness, flight safety, or mission success (DR's 1.2.1.7‑a, 1.2.1.7‑c,
*1.4.3.3-z, and 1.4.3.3-aa*).

"The contractor shall interface with payload customers and develop,
baseline, and maintain unique PIP Annex 4 in accordance with the PIP
schedule. The contractor shall maintain generic blank books. All generic
blank book changes shall be approved by NASA. The contractor shall
provide the annex (DR 1.4.3.3-v).

Required Service: Develop and baseline Integration Plan (IP) Annex 4
(Command and Data Requirements)

Standard: 100% Annex baselined in accordance with IP schedule

MER: 10% of Annex may be baselined late but not later than Flight
Planning and Stowage Review, and in no case impact major program
schedule milestones.

The contractor shall be responsible for coordinating the technical
content of vehicle DCR's and mission I-Loads and will load the STAR/MAST
systems with data in support of JSC/Engineering Directorate. The
contractor will coordinate these data entries at the SASCB Shuttle Data
and Reconfiguration Data Boards for DCR's affecting engineering
accountable hardware subsystems and I-Loads (DR 1.4.3.3-x).

#### 1.4.3.4 BFS FLIGHT SOFTWARE RECONFIGURATION

The contractor shall prepare and verify the content of the flight
configured BFS software and I-loads using certified tools. The
contractor shall verify that the software has been properly reconfigured
and is ready to be applied to the vehicle and to support flights. The
detailed mass memory content and deliverables shall be defined by JSC
24954, FSW Build Specification ICD, and JSC 08338, Shuttle Avionics Mass
Memory Unit Computer Integration Plan, respectively and the processes
described by these documents shall be adhered to for all FSW builds.

The contractor shall provide, manage, and document the processes
utilized in the production of all BFS products. Any products generated
with procedures not contained in the process documentation must have an
authorizing management waiver and must be reported to NASA. The
contractor shall establish the development and maintenance of software
necessary to produce the products. The contractor shall provide for
government approval, a configuration management plan for maintenance of
requirements, tools, and documentation used in the production of FSW
reconfiguration products (DR's 1.4.3.4‑d).

Required Service: Provide BFS reconfiguration deliverables to support
flight manifest.

Standard: All products affecting the BFS flight software configuration
will be delivered 100% accurate.

Expectation: Slips or redelivery caused by BFS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the BFS flight software configuration caused by BFS
which impact flight safety, mission success or the applicable scheduled
launch date."

#### 1.4.3.5 BFS FLIGHT SOFTWARE MODIFICATIONS

The contractor shall produce BFS FSW for on-board space systems,
including the data processing system of the Orbiter. The contractor
shall receive and review requirements and implement all software
resident in the Orbiter avionics backup computer. Implementation of the
software shall be accomplished by OI source code deliveries, source code
changes to flight systems, or as address patches to flight systems.
After the completion of the FACI, the contractor shall complete an
additional and independent verification of all FSW and FSWAT developed
under this contract in accordance with NSTS 08271, FSW Verification and
Validation Requirements. This verification shall also include analysis
of computer performance, prediction, and measurement (DR's 1.4.3.5‑a,
1.4.3.5‑b, 1.4.3.5‑c, 1.4.3.5.‑d, 1.4.3.5‑e, 1.4.3.5‑g, 1.4.3.5‑h,
1.4.3.5‑i, 1.4.3.5‑j, 1.4.3.5‑k, 1.4.3.5‑l, 1.4.3.5‑m, 1.4.3.5‑n,
1.4.3.5‑o, 1.4.3.5‑p, 1.4.3.5‑q, 1.4.3.5-r, 1.4.3.5-s, 1.4.3.5-u, and
1.4.3.5-v).

Delivery of major computer program updates shall be accomplished by the
contractor completing delivery at CI of all documentation and products
as defined by JSC 22320, Flight Software Class 1 Integration Plan (CIP).

Required Service: BFS Applications Tools OI deliverables

Standard: The BFS flight software applications tools code development
process will maintain an error rate of less than or equal to .5 per 1000
lines of code change in an OI which affected at least 2000 lines. Errors
will be calculated from the CI of that OI and will count all contractor
introduced code error DRs only. A 100% accuracy will be expected for
associated data files, configuration control files and supporting
product reports which would impact the BFS flight software quality or
configuration.

Expectation: Slips or redelivery caused by not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the BFS Tools OI deliverables caused by BFS Tools
which impact flight safety, mission success or scheduled launch date.

Required Service: BFS OI deliverables

Standard: The BFS flight software code development process will maintain
an error rate of no greater than one error per release for releases with
less than 2000 lines of code change. Or, less than or equal to .5 per
1000 lines of code change in an OI which affected at least 2000 lines.
Errors will be calculated from the first SRR of that OI and will count
all Severity 1, 2 and 3 DRs only. A 100% accuracy will be expected for
associated data files, configuration control files and supporting
product reports which would impact the BFS flight software quality or
configuration.

Expectation: Slips or redelivery caused by BFS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the BFS OI deliverables caused by BFS which impact
flight safety, mission success or scheduled launch date.

Required Service: Provide Flight System and In-Flight patches for BFS
Code, Data, and Reconfiguration

Standard: Delivered 100% correct in content and accuracy for MMU memory
locations.

Expectation: No errors requiring redelivery of patch which impacts
verification and mass memory build schedules.

MER: No errors which require program waivers, or impacts safety,

> mission success or major program schedule milestones.

#### 1.4.3.6 FLIGHT OPERATIONS SUPPORT

The contractor shall provide mission support from pre-launch countdown
through all flight phases to vehicle powerdown on the runway. The
contractor flight support team, under the direction of the NASA team
lead, shall provide technical consultation concerning flight software
related issues and perform analysis, data collection, and resolution of
anomalies.

1.4.3.7 PASS FLIGHT SOFTWARE PROCESSING

The contractor shall manage and perform the requirements definition,
analysis, design, implementation, verification, certification,
configuration control, test, and maintenance of the PASS Space Shuttle
software for the DPS of the Space Shuttle Orbiter. Included in this
responsibility is the DPS performance and systems analyses that are
essential for the software design. The contractor shall perform internal
software quality assurance of the processes and procedures used to
generate the PASS FSW products.

The contractor shall maintain configuration control of all FSW products
delivered to NASA. Configuration control shall provide full traceability
from NASA approved requirements to the individual items delivered and
shall be applied to each Operational Increment (OI) or Shuttle FSW
build. The contractor shall utilize a configuration management database
to support the configuration control and coordination of the contractor
and NASA boards. This support shall include report generation,
configuration audits, control board administration and logistical
support, coordination support for Engineering Directorate review
processes and control documentation.

The contractor shall support computer security, data integrity,
implementation, test and maintenance of the Software Development
Facility (SDF) to be used for all coding of Flight Software (FSW) and
the Flight Software Application Tools (FSWAT). The contractor shall
provide RACF profiles and administer user access for NASA and contract
users. The overall computer security and data integrity requirements
shall be with the Automated Information System Security Manual
(JSC-2410.11). The overall requirements, implementation, and maintenance
shall be consistent with all SDF policies and procedures approved by the
SPF Configuration Control Board.

DR's: 1.4.3.7-a, 1.4.3.7-b, 1.4.3.7-c, 1.4.3.7-d, 1.4.3.7-e, 1.4.3.7-f,
1.4.3.7-g, 1.4.3.7-h, 1.4.3.7-i, 1.4.3.7-j"

1.4.3.8 PASS FLIGHT SOFTWARE TOOLS

The contractor shall perform the requirements analysis, design,
implementation, verification, configuration control, and maintenance of
the software and hardware tools required to generate, verify, deliver,
and maintain configuration control of avionics software products. These
tools include those used by the contractor and NASA in the Software
Development Facility (SDF) and the ASDEP Networked Computers. The tools
used for reconfiguration shall be delivered to NASA for use in the
Software Reconfiguration Facility (SRF). This delivery shall occur at CI
of each OI and as needed for late changes as defined in the Flight
Software Frontroom/Backroom Interface Control Document (JSC 22303) and
the CIP document (JSC 22320).

The contractor shall perform impact analyses of the proposed tool
changes relative to flight software OI's, considering compatibility with
other Support Software Change Request (SSCR's) and Support Software
Discrepancy Reports (SSDR's). The contractor shall support the
processes, procedures, documentation, and databases for the Support
Software Configuration Control Board.

The contractor shall develop, verify, and maintain all Flight Software
Application Tools (FSWAT) unique to the development, reconfiguration,
and maintenance of the Shuttle onboard FSW (SCR 89057 - Flight Software
Application Tools (FSWAT) process). These FSWAT elements shall be
located and used primarily in the SDF and SRF. Workstation and facility
(SAIL, SMS, KSC, etc) tools shall be subject to configuration control
when used directly for access to, reporting on, or modification of the
FSW. These capabilities shall be defined and developed in close
coordination with the hardware and the Commercial Off-The-Shelf (COTS)
equipment in the SDF. The contractor will also be required to develop
the HAL/S compiler upgrades for all OI's. All change requests are
coordinated with the users and approved or dispositioned by the NASA
Control Board.

Facility management of the Avionics Software Development Environment
Pathfinder (ASDEP) shall be supported, including computer security,
system assurance, user support, and requirements, implementation,
verification, and configuration control of the system tools.

SDF user support shall be provided for the Multiple Virtual Storage
(MVS) and UNIX operating systems plus any unique supporting software or
hardware (compilers, assemblers, linkage editors, utilities, databases,
and FEIDS) used in support of the software development activities. The
contractor shall support operating systems System Generation (SYSGEN),
consultation, and general system support to the users.

The contractor shall be responsible for the NASA ADP (Automated Data
Processing) Consolidation Center (NACC) insight for the Space Shuttle
Program Office. This will include Shuttle Program Office NACC (SPON)
system integration (data base administration, system assurance,
change/risk management), Application Support (resource management), and
User Support (ID administration, Help Desk support).

DR's: 1.4.3.8-a, 1.4.3.8-b, 1.4.3.8-c, 1.4.3.8-d, 1.4.3.8-e, 1.4.3.8-f,
1.4.3.8-g, 1.4.3.8-h, 1.4.3.8-i

Required Service: PASS Applications Tools OI deliverables

Standard: The PASS flight software applications tools code development
process will maintain an error rate of less than or equal to .5 per 1000
lines of code change in an OI which affected at least 2000 lines. Errors
will be calculated from the CI of that OI and will count all contractor
introduced code error DRs only. A 100% accuracy will be expected for
associated data files, configuration control files and supporting
product reports which would impact the PASS flight software quality or
configuration.

Expectation: Slips or redelivery caused by not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the PASS Tools OI deliverables caused by PASS Tools
which impact flight safety, mission success or scheduled launch date.

1.4.3.9 PASS FLIGHT SOFTWARE IMPLEMENTATION

The contractor shall prepare FSW change proposals and change requests
and provide recommendations for long term definition of OI changes as
defined in the Shuttle Avionics Software Control Board (SASCB) three
year plan. The contractor shall provide impact assessments and
recommendations to the SASCB in response to FSW changes proposed by SCR
or FSW DR's in accordance with the current baselined software processes,
SCR 89051-CR process and SCR 89052-DR procedures.

The contractor shall be responsible for the development of the PASS
Flight Software by performing requirements definition, requirements
analysis, functional and detailed design, code and implementation, test
and verification, performance analysis, and build and integration of
software as a result of baseline changes. The development phase includes
all CR work through CI, including all testing, all DR source changes
through FACI and all compiler UAT's.

Implementation of the software shall be accomplished by OI source code
deliveries. After the completion of the FACI, the contractor shall
complete an additional and independent verification of all FSW developed
under this contract in accordance with NSTS 08271, FSW Verification and
Validation Requirements. This verification shall also include analysis
of computer performance, prediction, and measurement.

Software delivery shall occur at Configuration Inspection (CI) of each
FSW Operational Increment (OI) and as needed for late changes as defined
in the Flight Software Class 1 Integration Plan (CIP) (JSC 22320).

DR's: 1.4.3.9-a, 1.4.3.9-b, 1.4.3.9-c, 1.4.3.9-d, 1.4.3.9-e, 1.4.3.9-f,
1.4.3.9-g, 1.4.3.9-h, 1.4.3.9-i, 1.4.3.9-j, 1.4.3.9-k, 1.4.3.9-l,
1.4.3.9-m, 1.4.3.9-n, 1.4.3.9-o, 1.4.3.9-p

Required Service: PASS FSW OI deliverables

Standard: The PASS flight software code development process will
maintain an error rate of no greater than one error per release for
releases with less than 5000 lines of code change. Or, less than or
equal to .2 per 1000 lines of code change in an OI which affected at
least 5000 lines. Errors will be calculated from the first SRR of that
OI and will count all Severity 1, 2 and 3 DRs only. A 100% accuracy will
be expected for associated data files, configuration control files and
supporting product reports which would impact the PASS flight software
quality or configuration.

Expectation: Slips or redelivery caused by PASS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the PASS OI deliverables caused by PASS which impact
flight safety, mission success or scheduled launch date.

1.4.3.10 PASS FLIGHT SOFTWARE RECONFIGURATION AND MMU INTEGRATION

The contractor shall generate and verify the contents of the
reconfigured primary software loads and an integrated MMU loads for
flight. The contractor shall ensure that the software has been properly
reconfigured and is ready to be applied to the vehicle and to support
Space Shuttle flights. The contractor shall provide the support and
services to accomplish the planning, analysis, implementation, and
testing associated with the reconfiguration of the mission unique data
incorporated against a FSW Operational Increment release system. Test
plans specifications, performance test reports, and audits shall be
included in this process.

Performance testing requirements will be approved by SCR 89044, Software
Reconfiguration Performance Test Plan, approved by the SASCB.
Reconfiguration reporting will be accomplished via MOD metrics
reporting, as well as performance test reports, release notes and other
reports. The detailed process and deliverable requirements shall be
defined in the Mission Integration Plan (MIP) (JSC 08338) and shall be
adhered to for all FSW reconfigurations builds. The detailed mass memory
deliverables content shall be defined by JSC 24958, FSW Build
Specification ICD.

DR's: 1.4.3.10-a, 1.4.3.10-b, 1.4.3.10-c, 1.4.3.10-d, 1.4.3.10-e,
1.4.3.10-f

Required Service: Provide PASS reconfiguration deliverables to support
flight manifest.

Standard: All products affecting the PASS flight software configuration
will be delivered 100% accurate.

Expectation: Slips or redelivery caused by PASS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the PASS flight software configuration caused by PASS
which impact flight safety, mission success or the applicable scheduled
launch date.

1.4.3.11 GROUND FACILITY DATA PROCESSING SYSTEM

The contractor shall perform the maintenance, modification, and testing
of the Data Processing System (DPS) components used in the listed ground
facilities including, but not limited to, the General Purpose Computers,
MCDS Display System, Simulation Interface Device (SID), Flight Equipment
Interface Devices (FEIDS), and Mass Memory Unit Simulator (MMUS). The
contractor shall also provide systems expertise for the resolution of
hardware and related software problems in the facilities listed below.

a.  Shuttle Avionics Integration Laboratory Shuttle Test Station (SAIL
    STS)

b.  JSC Avionics Engineering Laboratory (JAEL)

c.  Software Production Facility (SPF)

d.  Shuttle Mission Simulator-Moving Base (SMS-MB)

e.  Shuttle Mission Simulator-Fixed Base (SMS-FB)

f.  Guidance and Navigation Simulator (GNS)

g.  Shuttle Training Aircraft (STA)

h.  KSC Avionics Test Station (KATS)

DR's: 1.4.3.11-a, 1.4.3.11-b, 1.4.3.11-c, 1.4.3.11-d

1.4.3.12 PASS FLIGHT SOFTWARE MAINTENANCE

The contractor shall perform the flight software maintenance through DR
analysis, DR code development and testing, and associated paperwork for
software discrepancies and changes after FACI. The maintenance support
shall cover all analysis, recommendation, and corrective actions
necessary to close flight software code and reconfiguration DRs at the
SASCB as defined in SCR 89052. The contractor will be required to
maintain and update the FSW maintenance specification documents
including correction of errors introduced during FSW development and
other maintenance actions to the FSW and FSW documentation which insure
software quality. The contractor will support problem analysis of
special field releases or T&O issues, perform audits as a result of
Compiler or other tool DR's, review Program Notes and waivers for OI
applicability, update documentation such as FSW User Guide, and prepare
FSW notes and waivers.

The contractor shall perform Flight Software mission maintenance which
includes all flight preparation and in-flight activities required to
support NASA sites which use released Flight Software. The contractor
will be responsible for supporting Site unique patch development and
testing for each applicable released flight system, GMEM procedure
development and testing for applicable released flight system, mission
support staffing in the Mission Evaluation Room, support of all SASCB
control boards for actions and deliverables needed on a flight to flight
basis, compiler and other audits on flight loads, data value patches
required post-reconfiguration as a result of SASCB direction, and source
or patch fixes authorized by CR or DR when required in support of the
flight-to-flight recon process. The contractor will provide
consultation, problem analysis, corrective action and configuration
control support of contractor delivered software at JSC, KSC, and other
locations as directed.

DR's: 1.4.3.12-a, 1.4.3.12-b, 1.4.3.12-c, 1.4.3.12-d, 1.4.3.12-e,
1.4.3.12-f, 1.4.3.12-g, 1.4.3.12-h, 1.4.3.12-i

1.4.3.13 MEDS MODIFICATION AND MAINTENANCE

The contractor shall perform the requirements analysis, design,
implementation, verification, certification, configuration control, and
maintenance of the MEDS software in accordance with the SASCB baselined
software processes SCR 98016-MEDS Flight Software Process. The
contractor's responsibility includes the IDP software, the MDUF
software, the ADCF firmware, the IDP-BSL firmware, the MDU-UDI firmware,
MTS software, IDP support software, MDUF FQT software, MOM, ADCF FQT
Test Scripts, and the Portable Loader software.

The contractor shall prepare and present MEDS software change proposals,
change requests, and FSW DRs in accordance with the current baselined
software processes, CR 89051-CR process and CR 890-52-DR procedures. The
contractor shall provide recommendations for long term definition of
version increments. The contractor shall be responsible for
configuration management of the MEDS documentation, media, and tools
required to maintain the software.

The contractor shall be responsible for the design, development,
verification, configuration control, and maintenance of the non-flight
software and hardware tools used for MEDS software product generation,
verification, delivery, maintenance, configuration control, performance
analysis, and problem investigation.

Required Services: MEDS Software Version Increment Deliverables

Standard: The MEDS flight software code development process will
maintain an error rate of no greater than one error per release for
release with less than 5000 lines of code changed. Or, less than or
equal to 0.2 per 1000 lines of code change in a version increment which
affected at least 5000 lines. Errors will be calculated from the
Software Acceptance Review of that version and will count all Severity
1, 2, and 3 DRs only. 100% accuracy will be expected for associated
documentation, data files, configuration control files, and supporting
products that would impact the MEDS flight software quality or
configuration.

Expectation: Slips or redelivery caused by MEDS Software not meeting
negotiated schedules or due to a redelivery to correct an error are
allowed if no additional resource impact to outside organizations is
incurred.

### MER No errors in the MEDS Version Increment deliverables which impact flight safety, mission success, or scheduled launch date.

1.4.3.14 MEDS SOFTWARE TEST AND OPERATIONS SUPPORT

The contractor shall provide Test and Operations (T&O) support for
facilities responsible for software engineering evaluation,
software/hardware integration, software validation, crew training, and
preflight/postflight testing. The contractor shall provide problem
analysis of special field and T&O issues, prepare and maintain MEDS
Program Notes and Waivers, and provide T&O support for operational
missions.

The contractor shall perform the design, implementation, and maintenance
of specific test software (interim releases) required by avionics system
facilities, such as the Shuttle Avionics Integration Laboratory (SAIL),
Shuttle Mission Simulator (SMS), Shuttle Training Aircraft (STA), and
Kennedy Space Center (KSC) facilities in support of checkout and
turnaround operations.

Required Services: MEDS Software Interim Release Deliverables

Standard: The delta code changes for the interim release software are
100% technically accurate, complete in content, and delivered on the
negotiated schedules. 100% accuracy will be expected for associated
documentation.

Expectation: Slips or redelivery caused by MEDS Software not meeting
negotiated schedules or due to a redelivery to correct an error are
allowed if no additional resource impact to outside organizations is
incurred.

### MER No errors in the interim release deliverables which impact flight safety, mission success, or scheduled launch date.

1.4.3.15 PORTABLE COMPUTER SOFTWARE SYSTEMS FOR SPACEFLIGHT

The contractor shall provide and maintain software for use on the
Payload and General Support Computer (PGSC) platform. All software
generated or maintained as part of this section shall follow a
contractor developed/government approved software development plan.
Software/firmware provided as Government Furnished Equipment (GFE) or
from an Original Equipment Manufacturer (OEM) shall not be held to
standards specified in the software development plan.

The contractor shall deliver software which reads decommutated downlist
data generated by the Pulse Control Modulated Master Unit (PCMMU) in a
format and timetable specified in the Data Requirements Description
(DRD) document for PGSCs. Contractor shall also be responsible for
system definition development for future PCMMU functions that are
compatible with present and future Space Shuttle portable computer
platforms. Related PGSC software may be provided and/or maintained in
addition to the decommutation software upon concurrence with the Space
Shuttle Program Office. (DR 1.4.3.16-a)

1.4.3.16 VEHICLE AND PAYLOAD DATA COLLECTION/RECONFIGURATION

The contractor shall perform assessments of vehicle, Orbiter Interface
Unit (OIU), and payload avionics and change requests submitted by the
Shuttle community and payload suppliers in order to determine the
feasibility and impacts of the request with respect to cost, schedule,
content and quality of contractor activities.

The contractor shall review all flight software Change Requests (CR)
related to Shuttle onboard displays for technical correctness.

The contractor shall provide the reconfiguration products to users as
specified in the Data Integration Plan (DIP) and the Shuttle Avionics
Mass Memory Unit Computer Integration Plan in the correct format.
Products shall be delivered in support of mission specific schedules.
The contractor shall provide manifest assessments in support of the SSP.
Products shall be delivered as required for: Recon 1 (R1), Final Load
(FL), PVL, One Cycle to Flight (OCTF), Special Build or Patch
(DR 1.4.3.16-a).

The contractor shall provide assessments of reconfiguration data change
requests submitted to the SASCB by the payload suppliers and the Shuttle
community. NASA shall determine which SASCB data change requests to
implement. The contractor shall determine the manner of SASCB/DCR
implementation, based on resources and priorities providing such
implementation does not impact cost or schedule and the change is agreed
to by all impacted parties.

The contractor shall ensure data integrity and configuration control of
mission data and conform to the SASCB configuration management process
defined by NASA.

The contractor shall provide the I-load baseline and coordination
support in order to provide I‑loads inputs into the Flight Software
Reconfiguration Process.

The contractor shall develop and maintain the reconfiguration tools
necessary to produce the data reconfiguration products. (DR 1.4.3.16-b)

Required Service: Data Reconfiguration Deliverables

Standard of Excellence: 100% of the data products are error free

Expectation: 2.5% of the data products delivered during the previous
year contain errors, with all errors dispositioned prior to the start of
flight specific simulations, and in no case impact safety, mission
success or major program schedule milestones.

MER: 5% of the data products delivered during the previous year contain
errors, with all errors dispositioned prior to the start of flight
specific simulations, and in no case impact safety, mission success or
major program schedule milestones.

1.4.3.17 SHUTTLE AVIONICS INTEGRATION LABORATORY (SAIL)

The contractor shall provide management, integration, and system
engineering functions for all SAIL systems and equipment. The contractor
shall develop, implement and maintain a Management Plan that addresses
all systems and key operations tasks. The contractor shall provide an
Information Technology Acquisition Plan (DR 1.1.4.1‑b).

The contractor shall modify, upgrade, and/or improve the performance of
the systems and equipment in the SAIL facility. The contractor shall
obtain NASA approval for all modifications resulting in an architectural
change. The contractor shall, as directed by the government, provide
project management and development plans and implement system upgrades
and/or new capabilities required by vehicle/mission changes additions,
obsolete and NME equipment replacements, and/or operational
efficiencies.

The contractor shall establish agreements with non-SFOC users of SAIL
Systems and Equipment for services required to satisfy SSP program
requirements. These agreements shall be documented and signed by all
participants.

Required Service: SAIL operations system availability.

####### Standard of Excellence: 100% SAIL operations system availability 

Expectation: 5% SAIL operations system non-availability with no impact
to safety, mission success or major program schedule milestones.

MER: No significant impact to safety, mission success or major program
schedule milestones.

Required Service: Provide sustaining engineering and maintenance and
operations support for SAIL system and equipment.

Std of Excellence: Complete and adequate Closure of Sustaining
Requirements and Discrepancy Reports within negotiated and agreed upon
user need dates and in no case impact safety, mission success or major
program schedule milestones.

Expectation: 5% late, but in no case impact safety, mission success, or
major program schedule milestones.

MER: No significant impact to safety, mission success or major program
schedule milestones.

The contractor shall provide maintenance of the Government computer
systems and shall operate the computer equipment including any computer
equipment added or changed during the contract period. The contractor
shall operate the tape libraries and tape silo automated storage
systems, and coordinate data information retention and accountability
with other libraries or archival facilities provided and operated by
other JSC contractors or Government personnel.

The contractor shall maintain all SAIL flight hardware and software,
incorporating modifications to maintain flight vehicle configuration and
supporting development activities as directed by the government. The
contractor shall plan tests, execute and resolve anomalies.

The contractor shall provide sustaining engineering and modification of
the systems hardware in the SAIL facility. The contractor shall design
modifications to the baseline systems including requirements, functional
design, and documentation. The modifications shall be based on
vehicle/mission changes/additions, obsolete equipment/component
replacement, and operational efficiency improvements. The contractor
shall conduct and schedule design reviews for all appropriate levels of
change and provide a Functional Design Review (FDR) Report. System or
configuration changes that do not affect the functional capability of a
system or the hardware or software architecture do not require formal
design reviews. The contractor shall provide continuing system
engineering support for systems during their operational lifetime. This
support shall encompass all technical support beyond normal operation
and maintenance.

The contractor shall maintain commercial off-the shelf software (COTS)
and maintain and modify custom software for the flight operations
systems in the SAIL facility. The contractor shall conduct and schedule
functional design reviews (FDR) for all appropriate levels of changes
and provide a FDR report. System or configuration changes that do not
affect the functional capability of a system or the hardware or software
architecture do not require formal design reviews. The contractor shall
maintain software documentation throughout the development and
maintenance of software systems.

The contractor shall define procedures to establish and maintain
software configuration control, discrepancy resolution, and modification
definition and implementation. The contractor shall provide sufficient
detail to establish the applicability or exceptions of the plan to the
various types of software (mission/non-mission, systems/applications,
etc.).

Required Service: Management of software critical discrepancies to
enable the system to support integrated verification and flight
operations.

Std of Excellence: No critical discrepancies in mission support software
after the scheduled start of integrated verification and mission
support.

Expectation: No critical discrepancies after the start of integrated and
mission specific verification that impact safety, mission success or
major program schedule milestones.

MER: More than 1 critical discrepancy(s) after the start of integrated
and mission specific verification that impact(s) safety, mission success
or major program schedule milestones.

The contractor shall integrate and install equipment, software, and
reconfiguration products for the operations systems in SAIL facility.
The contractor shall determine integration schedules that ensure
facility availability and installation schedules are sufficient to
support the integrated verification and mission support activities. The
contractor shall integrate support during all phases of a development
project which will require multiple interfaces with the Government and
the development contractor. The contractor shall work with development
contractors to establish an agreement that defines the division of roles
and responsibilities regarding installation, integration, maintenance,
and operation activities, and that defines the services that will be
provided to development contractors. Agreements shall be documented and
signed by all participants.

The contractor shall conduct and execute integration and verification
tests of the STS avionics and related hardware or simulation of
hardware, flight software, flight procedures and associated ground
support hardware and software. The Flight Crew may participate as
cockpit operators during the execution of verification test activities
at NASA's discretion (DR 1.4.3.17-a).

### 1.4.4 EXTERNAL TANK (ET)

The contractor shall plan, control, and perform ET processing
activities. A Memorandum of Understanding shall be established between
the contractor and the ET element contractor that reflects the interface
relationships as defined in Memorandum of Understanding, LSOC/MMC-001,
latest revision.

#### 1.4.4.1 ET ELEMENT PROCESSING

The contractor shall perform ET processing using hardware and associated
documentation certified and furnished by the ET element contractor in
support of the operations phase of the STS including the integrated
operations as specified in SOW Section 1.5. The contractor shall perform
routine, planned/unplanned processing/maintenance operations, test and
check out procedures. The contractor shall obtain the ET element
contractor's concurrence as necessary to establish an agreement that the
integrated operations meet element contractor requirements prior to the
scheduled launch.

#### 1.4.4.2 ET LOGISTICS

Reference SOW section 1.4 for general logistics requirements.

The contractor shall define, assess, and ensure that spare parts and
consumables are procured or supplied for the ET and the related support
equipment for hardware processing at KSC. The contractor shall obtain
from the ET MAF element contractor an agreement on the requirements
including total quantity, parts numbers, and consumption or failure
rate.

#### 1.4.4.3 RESERVED

#### 1.4.4.4 ET TRANSPORTATION

The contractor shall transport the ET by barge from the Michoud Assembly
Facility (MAF) to the launch site (KSC). The ET element contractor shall
transport the ET and its related equipment from the point of final
assembly to the point of barge embarkation and loading to include that
effort required to load, tie down and secure the hardware on marine
vessels and ballast the barge for sea. The contractor shall schedule all
transportation functions and obtain an agreement with the ET element
contractor that the ET loaded barge configuration is acceptable for
shipment. The contractor shall determine and communicate to the ET
element contractor the required number of days prior to the scheduled
launch that the ET barge must be loaded and available for shipment. A
The contractor shall accomplish marine surveys and shipyard maintenance
required to maintain American Bureau of Shipping and U.S. Coast Guard
vessel certifications on the two Government Furnished barges identified
in attachment J-9C-1 (Government Furnished Property) of this document.
The contractor shall make the barges available for other NASA
requirements on a non-interference basis with the ET shipments and barge
repair schedules.

#### 1.4.4.5 ET MODIFICATIONS

The element contractor shall provide ET modification kits required for
ground processing to support the operations phase of the STS. The
contractor shall perform operational impact assessments, process
requirements, and install, validate and test modification kits. The
contractor shall obtain the ET element contractor's concurrence as
necessary to establish the correct installation and configuration of ET
modifications for each mission.

1.4.4.6 Reserved

7.  ET TRANSITION PLAN

The contractor shall conduct Phase II transition planning to provide
timely, orderly, and effective transfer of responsibility for the MAF as
a GOCO facility and MSFC ET contracts. The transition planning shall
demonstrate the contractor's technical knowledge and managerial strategy
necessary to ensure successful management of the ET production and
facilities maintenance. The contractor shall assume responsibility for
ET contracts after four successful super lightweight tank flights.

5.  Reusable Solid Rocket Motor (RSRM)

The contractor shall plan, control, and perform RSRM processing
activities. A Memorandum of Understanding shall be established between
the contractor and the RSRM element contractor that reflects the
interface relationships as defined in Memorandum of Understanding, RSRM
Launch Support Services Contractor/Space Flight Operations Contractor,
Revision E, dated Aug. 24, 2001.

#### 1.4.5.1 RSRM ELEMENT PROCESSING

The contractor shall perform RSRM processing using hardware and
associated documentation certified and furnished by the RSRM element
contractor. The contractor shall perform all processing activities
associated with the RSRM hardware in support of the integrated
operations phase of the Shuttle Transportation System as specified in
SOW section 1.5. The contractor shall obtain the RSRM element
contractor's concurrence as necessary to establish an agreement that the
integrated operations meet element contractor requirements prior to the
scheduled launch.

#### 1.4.5.2 RSRM LOGISTICS

Reference SOW section 1.4 for general logistics requirements.

The contractor shall define, assess, and ensure that spare parts and
consumables are procured or supplied for the RSRM and its related
support equipment for hardware processing at KSC. The contractor shall
obtain from the RSRM element contractor, an agreement on the total
quantity, configuration control, parts numbers, and consumption or
failure rate.

Required services: Spare parts and consumable requests filled from
inventory

Standard: 100% spare parts/consumables delivered on time to support
schedule.

MER: 3% of total transactions late with no unfilled orders 5 days prior
to start of ET/SRB mate.

#### 1.4.5.3 RSRM RECOVERY OPERATIONS

The contractor shall support integrated operations as identified in SOW
section 1.5.4.4.

#### 1.4.5.4 RESERVED

#### 1.4.5.5 RSRM MODIFICATIONS

The element contractor shall provide RSRM modification kits required for
ground processing to support the operations phase of the STS. The
contractor shall perform operational impact assessments, process
requirements, and install, validate and test modification kits. The
contractor shall obtain the RSRM element contractor's concurrence as
necessary to establish the correct installation and configuration of
RSRM modifications for each mission.

Required Service: Approved closeout verification from element contractor
for each modification/change.

Standard: 100% verification within 5 days of completion of modification.

MER: 5% late but no incomplete work at ET/SRB mate.

#### 1.4.5.6 RESERVED 

#### 1.4.5.7 RSRM TRANSITION PLAN

The contractor shall conduct Phase II transition planning to provide
timely, orderly, and effective transfer of responsibility for the MSFC
RSRM contracts. The transition planning shall demonstrate the
contractor's technical knowledge and managerial strategy necessary to
ensure successful management of RSRM hardware consistent with the
maturity of the RSRM design and production process.

### 1.4.6 SPACE SHUTTLE MAIN ENGINE (SSME)

The contractor shall plan, control, and perform SSME processing
activities. A Memorandum of Understanding shall be established between
the contractor and the SSME element contractor that reflects the
interface relationships as defined in Memorandum of Understanding,
LSOC/ROC-001, latest revision.

#### 1.4.6.1 SSME ELEMENT PROCESSING

The contractor shall perform SSME processing activities at KSC in
support of the operations phase of the STS including the integrated
operations as specified in SOW section 1.5. The contractor, shall
provide managerial, engineering, hands-on and other resources necessary
to manage, coordinate, and perform routine, planned/unplanned processing
and maintenance operations, test and check out procedures, launch
activities, postlanding inspections and processing, transportation, and
handling of the SSME'S during removal and installation, problem
resolution, and implementation of waiver and deviations. The contractor
shall obtain the SSME element contractor's concurrence as necessary

to establish an agreement that the integrated operations meet element
contractor requirements prior to the scheduled launch.

Required Service: Agreement from the element contractor that the
baseline configuration has been certified and is ready for launch.

Standard: 100% baseline configuration certified prior to integration.

MER: 5% late but no incomplete work at integration from baseline
configuration.

#### 1.4.6.2 SSME LOGISTICS

Reference SOW section 1.4 for general logistics requirements.

The contractor shall receive, inspect, and provide warehousing of
government furnished engine parts), and related equipment at KSC for its
related support for the operational phase of the STS. The contractor
shall transport all SSME hardware shipments to Rocketdyne at Canoga Park
or Stennis Space Center (SSC) , or other designated locations.

#### 1.4.6.3 SSME LANDING OPERATIONS

The contractor shall perform the activities associated with landing
(i.e. installation of plugs, adapters and locks) and support integrated
operations as identified in SOW section 1.5 and SOW section 1.4.6.1.

#### 1.4.6.4 RESERVED

#### 1.4.6.5 SSME MODIFICATIONS

The element contractor shall provide SSME modification kits required for
ground processing to support the operations phase of the STS. The
contractor shall perform operational impact assessments, process
requirements, and install, validate and test modification kits. The
contractor shall ensure that the SSME element contractor is accountable
for the installation/verification of the SSME modification kits and its
impact to the final SSME stacked configuration.

#### 1.4.6.6 RESERVED

#### 1.4.6.7 SSME TRANSITION PLAN

The contractor shall conduct Phase II transition planning to provide
timely, orderly, and effective transfer of responsibility for the MSFC
SSME contracts. The transition planning shall demonstrate the
contractor's technical knowledge and managerial strategy necessary to
ensure successful management of the SSME. The contractor shall assume
responsibility for the SSME Contracts after delivery of the fifteenth
block II engine. The contractor shall also include transition planning
for SSME related SSC contracts associated with engineering and hardware
assembly in support of the SSME test operations at SSC.

### 1.4.7 RESERVED

### 1.4.8 RESERVED

### 1.4.9 EXTRAVEHICULAR ACTIVITY (EVA) AND FLIGHT CREW EQUIPMENT

The contractor shall process, ship, repair, modify and provide logistics
for all flight and Training Flight Crew Equipment. The flight crew
equipment is described in Exhibit 1.4.9. The contractor shall provide
processing of late/low cost ISSP mission critical requirements for
flights 2A.1, 1R, 2A.2A, 2A.2B, 3A, 4A, 3P, 5A, 4P, 5A.1, 250, 5P, 6A,
7A, 7A.1, UF1, 8A, UF2, 9A, 11A, ULF1, 12A, 9A.1, and 12A.1. The
contractor shall perform acceptance testing, burn-in and maintenance of
data packs for up to 900 new Class I Commercial Off The Shelf (COTS)
International Space Station (ISS) Laptops and 1,450 accessories. The
Contractor shall perform pre and post flight activities for ISS/HAB
flights 9A (post flight only), 11A, UFL1, 12A, 12A.1, 13A, and 13A.1 as
outlined in DP FCE-079.

#### ELEMENT PROCESSING

The contractor shall provide launch preparation, and post launch
activities related to the overall processing of flight crew equipment
required to support the SSP and ISSP programs. The contractor shall
maintain, prepare, and supply the individual equipment and provide
expendable items in preparation for each mission in accordance with a
contractor provided CCCD or SSCCD. This document shall contain reference
to data contained in contractor provided camera equipment lists, food
menus, clothing lists, and annexes as defined in SOW sections 1.2.2.4
(DR's 1.4.9.1-a, 1.4.9.1-b, 1.4.9.1-c, 1.4.9.1-e, 1.4.9.1-f, and
1.4.9.1-g). The contractor shall provide an Extravehicular Mobility Unit
(EMU) flight data report (DR 1.4.9.1).The Contractor shall assume
responsibility for processing liquid Cooling Garments(LCG) provided for
interface with the Crew Escape Equipment Launch Entry Suits (LES) and
Advance Crew Escape Suits (ACES) for Space Shuttle flight and training
activities. The Contractor shall perform crew ingress/egress for all
crew training, Terminal Countdown Demonstration Test (TCDT), launch, and
landing activities requiring use of the Crew Escape Equipment (CEE)
hardware. The Contractor shall provide CEE hardware briefings to various
groups, participate in Search and Rescue team simulations requiring use
of CEE, and provide technical support to the contractor processing CEE
Personal Parachute Assemblies at Ellington Field. The contractor shall
provide ISS Food Support and Crew Provisioning Hardware for Expeditions
2 thru 9. The contractor shall design, fabricate, test and certify for
flight an adapter cable that will convert the Orbiter Direct Current
(DC) power connector to interface to the ISS Express Payload Connector.
The contractor shall provide maintenance and processing support for ISS
Select-A-Dock Chassis. The contractor shall provide and process 50 desk
top plates and 50 multi-use brackets. The contractor shall create and
maintain 3000 series documents for control of Photo/TV items to be
transferred to the ISS. The contractor shall provide, process and
maintain the camera hardware described in DP FCE-041. The contractor
shall assume responsibility for maintenance and repair for the current
inventory of Pistol Grip Tools (PGT's) which currently includes 6 class
I PGT's and 1 engineering unit. The contractor shall also fabricate and
provide subsequent maintenance and repair for 3 class III Neutral
Buoyancy Lab (NBL) PGT's and 2 engineering units. The contractor shall
also fabricate 10 class III NBL PGT battery packs, 20 class I PGT
battery packs, and 6 test support equipment cables to support Space
Environmental Simulation Lab chamber runs and certification of a new
RS-422 PGT programming cable. The contractor shall provide six (6)
laptop computers and associated hardware for the Japanese Experiment
Module (JEM) scheduled to fly on STS-98. The contractor shall provide
for the interim modifications to the pan tilt units to support STS-92,
STS-97, and STS-102. The contractor shall provide 25 class I launch
entry pressure helmets, helmet cables, and pigtails. The contractor
shall provide for the disassembly, re-assembly, test, packaging and
shipment of the 12 chrysene contaminated CCTV cameras. The contractor
shall provide the packing support necessary for the MPLM on mission
7A.1, UF-1, UF-2 and ULF-1 scheduled for STS-105, STS-108, STS-111 and
STS-114. The contractor shall fabricate 10 CWC assemblies and provide
the processing of 20 CWC assemblies for reflight on ISS support
missions. The contractor shall process and maintain the phase VI gloves
and the associated hardware for flight and training activities. The
contractor shall provide for the processing and maintenance of EHIP
lights and the associated hardware. The contractor shall update 155
Class I and 17 Class III UOP 120V DC power cable assemblies. The
contractor shall design, fabricate, qualify, and perform acceptance
testing for nineteen (19) new Pan Tilt Unit's, one (1) new qualification
test unit, and one (1) engineering unit. The Contractor shall process
and maintain Portable Computer System (PCS)/Space Station Computers
(SSC) and Payload & General Support Computer (PGSC) Hardware to support
ground design and In-Vehicle Testing (IVT) at KSC. The Contractor shall
perform the Sustaining Subsystem Engineer (SSE) function for all
hardware on the Non-Complex Hardware List.

Required Service: Processing and delivery of flight crew equipment.

Standard: All crew equipment listed in the CCCD and SSCCD for each
flight is provided on time to meet program flight crew training and
flight planning milestones.

MER: All crew equipment is provided within 2 working days of scheduled
facility need dates, but in no case impact safety, mission success, or
major program schedule milestones."

#### 1.4.9.2 EVA AND FLIGHT CREW EQUIPMENT LOGISTICS

The contractor shall perform all logistical tasks required to ensure the
availability of all flight crew equipment required to support the SSP
and ISSP. Hardware logistical provisioning shall include all spares,
consumables and repair required by these programs. The contractor shall
provide an equipment inventory report (DR 1.4.9.2).

#### 1.4.9.3 TRAINING HARDWARE PROCESSING

The contractor shall provide training hardware for on-site and off-site
training. The contractor shall ensure training hardware shall support
training activities.

Required Service: Processing, delivery and maintenance of flight crew
equipment in support of crew training activities.

Standard: All training hardware is properly configured.

MER: 1% of the training hardware is improperly configured to support
training, but in no case impact safety, mission success or crew training
objectives.

Standard: All training hardware is provided by negotiated need date.

MER: All training hardware is provided within 2 working days of the
negotiated need date but in no case impact safety, mission success, or
crew training schedules.

1.4.9.3.1 MAINTENANCE AND REPAIR OF NBL TRAINING TOOLS

The contractor shall maintain, repair and replenish the tools used to
support events at the Neutral Buoyancy Laboratory (NBL) identified in
Attachment J-26 of the contract. The initial Government transfer shall
consist of ISS operational training tools in sufficient quantity to
support ISS training events. Thereafter, the contractor shall provide
these training tools, in the quantities identified in Attachment J-26,
to support NBL training activities. The contractor shall also prepare
and release class III drawings of the tools specified in Attachment J-26
of the contract.

#### 1.4.9.4 SHUTTLE REMOTE MANIPULATOR SYSTEM (SRMS) PROCESSING

The contractor shall process the SRMS in accordance with established
SRMS or MSD requirements. This includes off-line testing, installation,
or turnaround testing. Prior to rollout, the contractor shall provide
that the SRMS is capable of supporting the mission or identifying issues
and providing recommendations for resolution.

Required Service: Prepare SRMS for flight

Standard: SRMS processing tasks scheduled and completed on time in
accordance with program requirements.

MER: 1% of processing milestones missed with no incomplete work at FRR
for baseline configuration and no impact to safety, mission success, or
major program schedule milestones.

## 1.5 INTEGRATED LAUNCH & LANDING OPERATIONS

The contractor shall control and perform all integrated operations
(planned and unplanned) required to ready the SSV, associated facilities
and support equipment, for launch and landing activities. The contractor
shall conduct all integrated activities in accordance with approved
procedures to assure that these systems operate within all design
specifications, drawings, and OMRS requirements. Procedures development
and maintenance shall be per (DR 1.4‑a). The contractor shall support
the KSC launch and landing flight preparation plan - KPD 8630.3 and
participate in related reviews and forums to assure the proper
visibility, progress and launch readiness for ground processing tasks.

The contractor shall plan and perform integrated vehicle contingency
operations that may arise during integrated processing to support
unplanned program contingencies (i.e. hurricanes, launch abort/
turnarounds, etc.) as identified in SOW section 1.1.1.1 and Exhibit
1.1.1.1.

Integrated Orbiter operations begin with the connection of the Orbiter
sling assembly to the Orbiter for Orbiter to ET mate operations in the
Vehicle Assembly Building (VAB) transfer aisle. Integrated booster
operations begin with the SRB aft skirt and RSRM aft segment mate and
buildup in the Rotational, Processing and Support Facility (RPSF).
Integrated SSME operations begin with engine installation into the
Orbiter. Integrated ET operations begin with ET delivery to the VAB.
However, stand‑alone ET operations in the checkout cell shall be
accounted for under SOW section 1.4.4.1. Integrated payload operations
begin with payload removal from the payload canister for installation
into the Orbiter for horizontal or vertical payload installation and
experiment arrival at the OPF/Pad for middeck experiments. The
contractor shall support PGOC in Payload operations at KSC.

Launch countdown and Orbiter landing/recovery operations at the launch
site and planned contingency landing sites, including emergency
management at those locations, shall be performed under the management
and direction of the NASA Launch, Mission, and Orbiter Landing Recovery
Teams. The contractor's organization and personnel shall be fully
responsive to the Team's requirements and direction.

For purposes of this SOW, integrated landing operations terminate at
Orbiter wheel stop in the OPF at KSC or Mate-Demate Device at DFRC. SSME
post launch-integrated operations terminate after engine removal from
the Orbiter in the OPF. Payload integrated operations terminate after
removal from the Orbiter. RSRM and SRB integrated operations terminate
at the completion of preparations for shipment.

The contractor shall provide Safety, Mission Assurance and Product
Assurance for all integrated hardware and software as defined in SOW
section 1.3. The contractor shall refer to SOW section 1.1.1.4 for
out-of-family anomaly reporting requirements.

The contractor shall report and resolve anomalies in compliance with
NSTS 07700 and NSTS 08126 PRACA Requirements, as specified in SOW
section 1.3.

The contractor shall develop troubleshooting and analysis plans, repair
dispositions, and acceptance rationale. The contractor shall perform
troubleshooting, analysis, repair, retest, failure analysis, corrective
action, trend analysis and follow-up to determine effectiveness of
corrective actions. The contractor may perform approved standard repair
procedures), repairs which restore hardware to specification, and
hardware removal and replacement without explicit government approval of
the work documentation when disposition approval is not required in
accordance with SOW section 1.1.1.4.

The contractor shall ensure all Government and contractor personnel are
properly trained or certified, as required, by providing required
training or certification before participation in operations or in work
areas.

Required Service: Ensure Category 1 OMID procedures are current and
available.

Standard: 100% of Category 1 procedures on shelf 10 days prior to test
start for new procedures, 7 days prior to start for revised procedures,
and 3 days prior to start for minor or dash changes to the procedure

Expectation: 96% of Category 1 procedures on shelf 10 days prior to test
start for new procedures, 7 days prior to start for revised procedures,
and 3 days prior to start for minor or dash changes to the procedure.

MER: 6% late, but in no case impact safety, mission success, or major
program schedule milestones.

Required Service: Meet baselined integrated test schedules.

Standard: 100% of all integrated tests are conducted within baselined
schedule timelines.

Expectation: All integrated tests are conducted within 95% of baselined
scheduled timelines.

MER: An integrated test may vary 7% from the planned baseline, but in no
case impact major program schedule milestones.

### 1.5.1 VEHICLE INTEGRATION

The contractor shall plan, control and perform all tasks associated with
the integration, assembly and testing of an integrated SSV.

#### 1.5.1.1 ELEMENT/CARGO PLANNING & INTEGRATION

The contractor shall plan and integrate all element/cargo operations
associated with vehicle/payload integration including element readiness
reviews, requirement completion status, and open or transferred work
assessments. This effort shall also include plans, schedule development,
and distribution to the users to support integrated task execution.

#### 1.5.1.2 PAYLOAD INSTALLATION AND TESTING

The contractor shall perform horizontal and vertical payload element
installation into the Orbiter, and support the PGOC in payload interface
verifications, servicing, and close-out activities (DR 1.5.1.2). This
effort shall also include any approved payload optional services related
to ground operations.

#### 1.5.1.3 INTEGRATED TEST EXECUTION

The contractor shall perform all processing operations and testing
involved in the assembly and servicing of an integrated vehicle. These
tasks shall include as a minimum SRB/RSRM stacking operations in the
VAB, ET mate to the SRBs, Orbiter to ET mate, SSV transport and mate to
the launch pad, launch pad interface testing, hypergolic propellant
servicing, ordnance installation, Extravehicular Mobility Unit
installation/servicing/checkout, and Orbiter aft compartment close-outs.
Flight element design support (i.e., Orbiter, SSME, ET, SRB, RSRM, FSW,
EVA, and FCE) to integrated testing is covered in SOW section 1.4.

### 1.5.2 LAUNCH PREPARATIONS

The contractor shall perform all launch preparation tasks to determine
launch readiness.

#### 1.5.2.1 LAUNCH REQUIREMENTS

The contractor shall develop and maintain integrated launch procedures
and work authorization documents. The contractor shall maintain and
update the mission unique Ground Launch Sequencer (GLS) Configurations
document to support launch operations (DR 1.5.2.1).

#### 1.5.2.2 LAUNCH PLANNING

The contractor shall provide work control functions such as launch
procedures, plans, and schedule development; and distribution of these
items to the users for execution. The contractor shall support the NASA
Countdown Working Group (CDWG) efforts to define and resolve specific
countdown issues. The contractor shall provide auditable performance
metrics development and utilization of approaches to improve problem
resolution, ensure schedule adherence, identify, mitigate and control
risks; optimize resource utilization, and improve other launch support
capabilities.

1.5.2.3 LAUNCH TEAM TRAINING

The contractor shall train, qualify and certify its launch team for the
launch countdown and provide flight crew pad emergency egress training.
(The portions of flight crew training related to fire & rescue
operations will be provided by the Government.) The contractor's Launch
Team Certification Plan shall be approved by NASA (DR 1.5.2.3). These
training services and products shall include as a minimum training
procedures, training materials, unique training software, Tier One, Tier
Two, and Tier Three simulation training, tanking and launch simulations,
and Terminal Countdown Demonstration Tests (TCDT).

#### 1.5.2.4 LAUNCH READINESS

The contractor shall develop and implement an auditable approach to
verify and ensure contractor launch and landing readiness with all
requirements met and all problems dispositioned. This approach shall
include, as a minimum, open item reviews, , pre-test briefings, ,
facility/equipment/flight element readiness walkdowns, closed loop
tracking, verification and satisfaction of configuration, OMRS and
PVIS/ACOMC requirements.

Required Service: All work items identified on the initial Launch
Countdown constraints list either completed, closed or scheduled to be
worked.

Standard: 100% of all items on the initial Launch Countdown constraints
list completed and closed prior to Launch Countdown Call-to-Stations.
(Except work items that must be either performed during the countdown
due to technical constraints or are in the final documentation closure
process.)

Expectation: 97% of all items on the initial Launch countdown
constraints list completed and closed prior to Launch Countdown
Call-to-Stations. (Except work items that must be either performed
during the countdown due to technical constraints or are in the final
documentation closure process.).

MER: 3% of items open until start of ET tanking, but in no case any work
open that impacts the remainder of launch countdown or safety.

### 1.5.3 LAUNCH EXECUTION

The contractor shall perform launch countdown activities and initial pad
safing and securing operations.

#### 1.5.3.1 \[Reserved\]

#### 1.5.3.2 LAUNCH OPERATIONS

The contractor shall assemble, qualify and certify its launch control
team to provide overall assessment and execution of launch countdown
activities, contractor launch team performance, problem resolution and
launch requirement satisfaction under the direction and management of
the NASA launch team. The contractor's organization and personnel shall
be fully responsive to the team's requirements and direction. The final
responsibility for launch commitment will continue as a NASA function.

The contractor shall perform activities required to ensure and verify
final launch readiness, requirement satisfaction, and problem
resolution; complete remaining vehicle/payload/ISS/pad close-out
activities, support PGOC in Payload/ISS/pad/closeout activities, and
conduct launch countdown with a certified and qualified launch control
team. Launch countdown activities shall include as a minimum integrated
propulsion system integrity verification, final
facility/pad/equipment/flight element walkdowns, reactant servicing,
Rotating Service Structure (RSS) securing, late access/conditioned cargo
installation activities, flight crew equipment stowage, flight crew
support, ET loading, flight crew ingress and cabin close-out, terminal
count, launch and initial pad safing/securing in accordance with the
OMRS and LCC requirements. Flight element design support to integrated
launch operations is covered in SOW section 1.4.

### 1.5.4 POST LAUNCH

The contractor shall provide an integrated landing support capability,
provide KSC and DFRC contingency mission support, transatlantic abort
site support, payload/ISS element removal efforts, and SRB recovery and
disassembly operations. This effort shall be performed under the
direction and management of the NASA Mission and Orbiter
Landing/Recovery Teams.

#### 1.5.4.1 INTEGRATED LANDING OPERATIONS

The contractor shall perform planned and unplanned Orbiter landing
operations, including site readiness preparations and post-landing
operations at the Primary Landing Site, Secondary Landing Site,
Contingency Landing Site locations, and Transatlantic Abort Landing
sites (except Banjul, Gambia) under the direction and management of the
NASA landing team. This effort shall include the integration of efforts
to recover and tow the Orbiter to either the Orbiter Processing Facility
or the DFRC Mate-Demate Device; payload element destow/early access
operations; Return to Launch Site (RTLS) convoy support; and,
transportation of equipment, material, rentals, and freight to these
sites. Orbiter and SSME element standalone recovery operations and
preparations for ferry flight are covered in SOW section 1.4. Integrated
landing operations shall be conducted (DR 1.5.4.1).

#### 1.5.4.2 MISSION SUPPORT

The contractor shall provide integrated Orbiter landing support for
unplanned, early mission termination at the primary and secondary
landing sites. Convoy support at DFRC and White Sands Space Harbor
consists of initial Orbiter safing, flight crew egress and towing the
Orbiter to the Mate-Demate Device/Orbiter Deserving Area. Orbiter, SSME
and other element mission support is covered under SOW section 1.4. The
contractor shall also provide contingency mission control center support
via the Launch Processing System (LPS) in the KSC Launch Control Center
as specified in SSP Emergency Mission Control Center Activations and
Operations Procedures (534-CAP-EMCC) and SOW section 1.1.1.1.

#### 1.5.4.3 PAYLOAD ELEMENT REMOVAL

The contractor shall perform payload/middeck
experiment/pallet/module/ISS element removal operations from the
Orbiter.

#### 1.5.4.4 SOLID ROCKET BOOSTER & REUSABLE SOLID ROCKET MOTOR RECOVERY & DISASSEMBLY

The contractor shall recover and retrieve the spent boosters, parachutes
and frustums from the Atlantic Ocean and transport them to the CCAS
Hanger AF. The contractor shall safe and disassemble the hardware,
conduct post-flight

inspections, document anomalies and prepare the hardware for shipment
off-site and deliver parachute assemblies on-site for processing. .

### 1.5.5 SYSTEMS, FACILITIES AND EQUIPMENT

The contractor shall manage, operate, maintain and provide sustaining
engineering and logistics for the systems, facilities, and equipment,
delineated in Attachment J-9 Sections A, B, and D, including applicable
software/firmware which includes multiple categories of KSC ground
application software. Systems, facilities and equipment will be
transitioned to the contractor in accordance with Attachment J-9.

The contractor shall review site support, make/buy decisions and
services and aggressively pursue subcontracting and outsourcing
opportunities. The contractor should be innovative in effectively using
the marketplace and challenge the current paradigm of keeping the work
in house. The ultimate goal is to have safe, cost effective site support
and services while balancing reliability and risk.

#### 1.5.5.1 OPERATIONS

The contractor shall develop, plan, schedule and perform all systems,
facilities, and equipment operations required in the performance of this
contract. The contractor shall provide operational services to NASA and
other KSC users, for the contractor assigned systems, such as data,
voice, video, complex control systems, and the Hypergol Maintenance
Facility (HMF) Deluge Pump House which interface with systems assigned
to others. The contractor shall provide operators for all equipment
maintained by others and used by the contractor, such as life support.
Training and certification of contractor operators for life support will
be provided by the Government. The contractor operators of critical
cranes shall comply with NSS-GO-1740.9.

The contractor shall provide all support to contractor operations at KSC
and the Contingency Landing Sites, except support furnished by the
Government as described in Attachment J-10. Support provided by the
contractor includes operational laboratories (NDE except radiography,
Calibration (except standards), Sampling and Analysis and Component
Cleaning/Refurbishment), janitorial, and Non-productive supply in
contractor operational areas.

Required Service: Provide operational services scheduled on Kennedy
Integrated Control Schedules, Payload Integrated Control Schedules or
system outages to NASA and other KSC users for contractor assigned
systems which interface with others.

Standard: 100% of user requests met by due date negotiated between the
contractor and the requester.

Expectation: 95% of user requests met by due date negotiated between the
contractor and the requester.

MER: 10% late, with all requests met within 30 days of due date, but in
no case impact major program schedule milestones.

The contractor shall be responsible for the software utilized to support
checkout and processing of flight elements and mission unique
application software development. This software executes on the
appropriate systems identified in SOW section 1.5.5 and Attachment J-9.

Exhibit 1.5.5.1-B identifies the SPDMS and IWCS applications. The
contractor shall continue to refine and enhance these key capabilities
as appropriate or propose alternative concepts/approaches to integrated
work control management

The contractor shall support the development of the Integrated Data
System (IDS) to incorporate the functionality of various operational
data acquisition, control, record, and monitor systems (i.e., CCMS, CDS,
RPS, PMS, etc.) into an integral open architecture data system
consisting primarily of COTS equipment supported by a minimum of custom
hardware/software. The contractor shall provide development support in
accordance with SOW section 1.7.1.

#### 1.5.5.2 MAINTENANCE

The contractor shall implement a comprehensive proactive maintenance
program incorporating reliability centered maintenance in accordance
with NPG 8831.2 for assigned facilities and facility systems. The level
of maintenance provided shall assure the reliability, cost
effectiveness, and serviceability and longevity of the assigned systems
and equipment. The contractor shall, as a minimum, assure the systems,
facilities, and equipment are maintained in a condition which assures
reliability and prevents degradation. The contractor shall maintain all
applicable software/firmware for the assigned systems, facilities, and
equipment. In addition to maintaining the systems and equipment as
delineated in Attachment J-9, the contractor shall maintain and support
flight and flight-type equipment assigned to ground support equipment,
simulators, and off-line laboratories. The contractor shall budget,
prioritize, and approve all facility support requests affecting
JBOSC-managed facility systems or grounds that impact contractually
obligated facilities or facility projects. The contractor shall submit a
maintenance plan (DR 1.5.5.2).

Required Service: Maintain systems, software, firmware, facilities, and
equipment

Standard: Perform 100% of all planned maintenance tasks delineated in
the yearly maintenance plan (DR 1.5.5.2.)

Expectation: 90% of all maintenance tasks delineated in the yearly
maintenance plan (DR 1.5.5.2) completed.

MER: 15% of tasks not completed (85% completed), but in no case impact
safety, mission success or major program schedule milestones.

#### 1.5.5.3 SUSTAINING ENGINEERING

The contractor shall provide systems, facilities and equipment
hardware/software/firmware sustaining engineering that meets the
original design intent (i.e. form, fit and function). The contractor
shall develop the applicable sustaining engineering documentation,
implement the appropriate modifications, and maintain this documentation
current in accordance with SOW section 1.1.5.1. The contractor shall
list all planned hardware and software modifications to configured
systems (DR 1.5.5.3). The contractor shall comply with NHB 8820.2.

Required Service: Document changes to configured facilities, systems and
equipment.

Standard: 100% of all contractor generated changes documented prior to
implementation need.

Expectation: 98% of all contractor-generated changes to facilities,
systems and equipment documented prior to implementation need.

MER: 5% backlog (of contractor-generated changes) to facilities, systems
and equipment late, but in no case impact safety or delay critical
milestones.

Required Service: Document changes to CCMS system/applications
software/firmware.

Standard: 100% of all contractor generated CCMS system/applications
software/firmware changes documented prior to software production.

Expectation: 98% of all pre-planned contractor-generated CCMS
system/applications

software/firmware changes documented prior to implementation need.

MER: 5% backlog (of configured products which document generated
changes) to software/firmware, but in no case impact specific user need.

Required Service: Configuration engineering documentation for
facilities, systems and equipment is released complete and with minimal
errors.

Standard: 100% of contractor changes to facilities, systems and
equipment requires no documentation correction or production
re-releases.

Expectation: 95% of contractor changes to facilities, systems and
equipment requires no documentation correction or production
re-releases.

MER: No more than 10% of contractor changes to facilities, systems and
equipment requires correction to released documentation or production
re-releases.

Required Service: Configuration engineering documentation and code for
CCMS system/applications software is released complete and with minimal
errors.

Standard: 100% of contractor changes to CCMS system/applications
software requires no documentation correction or immediate production
code re- releases as a result of coding errors.

Expectation: 98% of CCMS system/applications software changes requires
no correction to released documentation or immediate production code re-
releases as a result of coding errors.

MER: 95% of CCMS system/applications software changes requires no
correction to released documentation or immediate production code re-
releases as a result of coding errors.

#### 1.5.5.4 LOGISTICS

The contractor shall provide a fully operational logistics system that
improves productivity and minimizes organizations providing like kinds
of products and services. Performance shall be reported (DR 1.4‑c).

Required Service: Provide parts, hardware, and materials for processing
and launch systems, facilities, and equipment.

Standard: 98% of requirements satisfied on or before the negotiated need
date.

Expectation: 96% of requirements satisfied on or before the negotiated
need date.

MER: No less than 92% of requirements satisfied on or before the
negotiated need date.

Required Service: Provide needed hardware, parts, and materials for
processing and launch systems, facilities and equipment so that
cannibalization does not become necessary.

Standard: No more than 0.075% of hardware requirements satisfied by
cannibalization.

Expectation: No more than 0.1% of hardware requirements satisfied by
cannibalization.

MER: No more than 0.2% of hardware requirements satisfied by
cannibalization.

Required Service: The contractor shall provide processing or launch
systems, facilities, or requirement hardware, which is suitable for use
upon delivery.

Standard: No less than 99% of hardware provided suitable for use.

Expectation: No less than 97% of hardware provided suitable for use.

MER: No less than 95% of hardware provided suitable for use.

##### 1.5.5.4.1 ACQUISITION

The contractor shall procure all hardware/items. These procurements
shall be consistent with Program requirements and directives (DR 1.4‑b).
Procurement performance shall be reported (DR 1.4‑c).

The contractor shall serve as the common item inventory control point
(ICP) for transducers, pyro connectors, KC fittings (GP-425), Buttweld
fittings (GP-425, KSC designed), and stainless steel tubing (KSC
SPEC-Z-0007) that are common to the program. These items shall be
provided to all other NASA centers, DOD agencies, other KSC contractors,
and local DOD contractors as authorized by the NASA Technical Manager
Representative (TMR).

The contractor shall manufacture or repair hardware when cost effective.
The contractor shall use existing certification plans complying with
Program requirements and directives. As the SFOC acquires additional
work through subsequent phases, new plans or changes to the existing
plans shall be submitted to the Government for approval. Manufacture and
repair performance shall be reported (DR 1.4‑c).

The contractor shall provide spares and CFM required to support the
hardware, equipment, and processing activities. The contractor shall
provision these assets at the LRU, SRU, and piece-part/consumable
levels. The contractor shall monitor and document hardware zero
balances. The contractor shall provide a forecast for GFM (DR 1.4‑d).
Spares & consumables replenishment performance shall be reported
(DR 1.4‑c).

The contractor shall identify, provide immediate notification in writing
to NASA and resolve loss of failure analysis, production, and repair
capabilities. Initial notification may be verbal for timeliness. Loss of
capability includes, but is not limited to, obsolescence, loss of
skills, and a critical supplier going out of business. The contractor
shall provide a recovery plan and obtain NASA approval for qualified
hardware and/or qualified supplier changes.

The contractor shall provide the engineering for hardware that includes,
but is not limited to, initial parts requirements, logistics support
analysis, and maintenance planning. Included in logistics engineering
support is test equipment, tooling, process certification, and repair
documentation. Test equipment shall be maintained (DR 1.5.5.2). The
contractor shall report unresolved maintenance action issues to the
government (DR 1.4‑c).

##### 1.5.5.4.2 MATERIAL MANAGEMENT

The contractor shall provide transportation, shipping, receiving,
storage, warehousing and distribution services. Transportation services
shall include hardware and equipment transportation for routine and
contingency operations. Planning for an off-site contingency shall be
provided as specified in SOW section 1.1.1.1. Transportation, shipping &
receiving performance shall be reported (DR 1.4‑c). The contractor shall
provide hardware with no damage due to transportation or storage, unless
the damage is minor and judged to be in the range of the acceptable wear
and tear specification or able to be repaired on-

site by a standard repair or a Material Review action. The contractor
shall report all incidents (SOW 1.3.1.2).

The contractor shall maintain an inventory management system.

The contractor shall maintain inventory levels throughout the contract
period and report the levels (DR 1.4‑c).

The contractor shall minimize hazardous waste materials and report in DR
1.4-c. For hazardous waste generated by processes in this program but
not under the control of the contractor, the contractor shall initiate
and coordinate with NASA reduction efforts.

Required Service: Provide hazardous waste material weight reduction for
hazardous waste under the control of the contractor.

Standard: Reduce hazardous waste material weight no less than 10% over
each year.

Expectation: Reduce hazardous waste material weight no less than 5% over
each year.

MER: No reduction in hazardous waste material weight.

The contractor shall identify excess or obsolete assets and initiate
excessing action. Property excessing performance shall be reported
(DR 1.4‑c).

##### 1.5.5.4.3 SUPPORT

The contractor shall provide training and certification for all
personnel including Government and contractors who participate in
operations or in work areas. Certification shall verify that individuals
are knowledgeable of the laws, regulations and NASA directives
concerning their task(s). The contractor shall provide a training and
certification plan as well as training schedules (DR 1.5.5.4.3‑a).
Training performance shall be reported (DR 1.4‑c).

The contractor will participate in the ALERT System and prepare and
provide ALERTs to the Government. The contractor shall identify the
affected hardware and start an analysis of the problem with
recommendations and/or corrective actions as part of their response.

## 1.6 FLIGHT OPERATIONS

The contractor shall prepare for and execute SSP flight operations and
ISS mission operations. The contractor shall develop alternatives that
are more efficient and/or effective by taking advantage of synergy's
across the Program(s), utilization of new technology and tools,
implementation of Reinvention (as defined in the approved VECP
#00USA0577 dated 09/08/2000), consolidation of functions, or by other
means. For the purposes of SOW section 1.6 flight operations are
equivalent to SSP flight operations and ISS mission operations.

The Government will lead and is responsible for mission execution and
requisite mission preparation tasks, new capability development
(including X-38 and other projects), non-mission specific Programmatic
support tasks, and out-of-family anomaly resolution. The new capability
development tasks for FY98 and FY99 reflect the reduction in content
necessary to accomplish the Integrated Planning Systems Upgrade Project.
As mission execution and preparation tasks become more stable and
standardized, they will, at the discretion of the Government, transition
from Civil Service to contractor responsibility. The contractor shall
perform flight controller tasks for SSP and ISS flight control
responsibilities as documented in the Fiscal Year (FY) Government
Accountable Functions Directive (GAFD). Contractor participation shall
be specified via Technical Direction and reported consistent with Flight
Operations Metrics requirements. The skill mix and size of the
Government/contractor participation will be established through
concurrence with the annual operating plan. The contractor shall perform
the tasks necessary to assist NASA in the definition, integration, and
implementation of the Interim Control Module (ICM) requirements
(including SMTF/SSTF integrated training capabilities, mission
preparation and real-time mission operations, but excludes tasks for ICM
Archive in ODRC and MCC ICM Operations Support which as of February 28,
1999 are the responsibility of the NASA CSOC Contractor).

The contractor shall utilize the standard metric (SI) system and/or U.S.
Customary System of measurement for all ISS displays, crew interfaces
(decal, placards, etc.), and operations/training documentation
developed. The Contractor shall develop individual crew/flight
controller displays using a mixture of both the SI and U.S. Customary
System of measurement. Current versions of documentation, hardware, or
software will not be affected. Contractor shall maintain minimum
interface requirements for SSTF until work is transitioned fully to SFOC
contract in FY05.

### 1.6.1 TRAINING

The contractor shall provide SSP and ISS crew training and flight
controller training and associated processes. This training is defined
as technical training required to execute flight operations for flight
controller personnel defined in SOW section 1.6.1.2 and flight crew
training defined in SOW section 1.6.1.3. The contractor shall train
civil service training personnel in training concepts and flight
operations as agreed to between the contractor and NASA.

The Government will lead and is responsible for overall ISS training and
training processes and the Crew On-Orbit Support System (COSS) which
will be developed and implemented by Government and contractor
personnel. The Government will transition ISS training to the contractor
when stable and

standardized ISS training processes have been established. During the
development period, the contractor participation shall be specified via
Technical Direction and reported consistent with Flight Operations
Metrics requirements. The size and skill mix of the contractor
participation will be established through concurrence of the annual
operating plan. The contractor shall provide for the development and
implementation of identified ISS training responsibilities. The
contractor will develop, implement, and operate the Crew On-Orbit
Support Systems (COSS) software to support on-orbit requirements on ISS,
including participation in training activities. The contractor shall
perform tasks for the training of onboard computer networks required to
meet PGSC mission objectives.

#### 1.6.1.1 TRAINING ADMINISTRATION AND MANAGEMENT

The contractor shall provide for execution of overall training processes
to assure flight crews and controllers are prepared to carry out their
assigned flight tasks.

The contractor shall establish and implement training requirements based
on SSP and ISS manifests and vehicle configurations. The contractor
shall manage and implement flight or increment specific training in
accordance with established program templates with a goal to
reduce/optimize the overall training template to increase management
scheduling flexibility, training effectiveness, and efficiencies. The
contractor shall establish an agreement with payload customers that
defines scope and assigns responsibility of SSP Payload training
(DR 1.6.1.1). When requested, the contractor shall provide flight
specific and increment specific training feasibility assessments in
support of defining mission specific production schedules and planning.
The contractor shall perform tasks to transition the MOD ISS Payload
Training Capability (PTC) Training Tasks from the Space Flight
Operations Contract (SFOC) to the Marshall Space Flight Center (MSFC)
subcontractor Teledyne-Brown Engineering (TBE). The following tasks will
be deleted from the SFOC contract as the responsibility of USA Flight
Operations: ISS PTC task descriptions, training requirements, and
maintenance of certification guides for ISS Payload Instructors.

##### 1.6.1.1.1 TRAINING RECORDS

The Contractor shall maintain Contractor Accountable Functions (CAF)
training and certification records in support of Flight Controller
Certification, Mission Controller Certification, and Crew Readiness.

##### 1.6.1.1.2 CURRICULUM AND LESSON DEVELOPMENT

The contractor shall manage and document the training processes utilized
in the production of all flight specific and generic training products
in accordance with the Training Development and Support Plan, JSC 36049
(DR 1.6.1.1.2‑a). The contractor shall coordinate with appropriate NASA
and external organizations (e.g., International Partners, Payload
Customers) to implement training requirements based on configuration of
the vehicles, flight software, flight plans, flight procedures, and
cargo. Training curriculum and lessons shall meet flight crew and flight
controller requirements. The contractor will provide avionics, system,
and robotics training for the Russian Segment Trainer (RST) and
participate in RST requirements development, curriculum development and
conducting training exercises. The contractor shall collect data
documenting the quality of delivered training (DR 1.6.1.1.2‑b).

Required Service**:** Flight Operations curriculum and training flows.

Standard of

Excellence**:** Curriculum or training flow contains 100% of performance
objectives required for certification or flight readiness.

Expectation**:** 1.5% errors or omissions in performance objectives
required for certification or flight readiness and no error impacts
safety, mission success or major program schedule milestones.

MER**:** 2% errors or omissions in performance objectives required for
certification or flight readiness and no error impacts safety, mission
success or major program schedule milestones.

Required Service**:** Flight operations lessons

Standard of

Excellence**:** Lesson execution accomplishes 100% of the required
performance objectives.

Expectation**:** 1% of lessons are repeated in order to accomplish
performance objectives and in no case impact safety, mission success or
major program schedule milestones.

MER**:** 2% of lessons are repeated in order to accomplish performance
objectives and in no case impact safety, mission success or major
program schedule milestones.

##### 1.6.1.1.3 TRAINING SCHEDULING

The contractor shall accomplish training scheduling in accordance with
SOW section 1.1.7

##### 1.6.1.1.4 INSTRUCTORS

The contractor shall provide and utilize certified instructors for the
conduct of all assigned training activities. The government will lead
and is responsible for multi-segment training including Russian segment
training and interfaces, as required. The government will transition
Russian segment training, hardware and software responsibilities, to the
contractor when stable and standardized processes have been established.
During the transition period, the contractor support requirements will
be determined by NASA in the annual operating plan. The contractor shall
maintain instructor training and certification plans and
discipline-specific certification guides (DR 1.6.1.1.4). The contractor
shall provide training functions at foreign locations as required,
\[e.g., the Gagarin Cosmonaut Training Center (GCTC) at Star City,
Russia for the Houston Training Support Group)\].

#### 1.6.1.2 FLIGHT CONTROLLER TRAINING

The contractor shall develop and maintain the SSP Flight Controller and
the ISS Mission Controller Certification Guides (DR 1.6.1.2-a and DR
1.6.1.2-b) for positions identified in SOW Section 1.6.5. The contractor
shall develop, maintain and conduct training for SSP Flight Controllers
and ISS Mission controllers in accordance with SOW section 1.6.1.1.2.
The contractor shall develop and conduct Integrated Simulations
(includes generic, advanced, flight specific, and increment specific).
Contractor shall perform Japan Segment Trainer (JST) training and
operator functions to train Expedition crews for ISS missions.
Contractor shall add an eighth SSTF for generic integrated simulations
and flight specific SSTF load development and training for ISS missions.
The contractor shall provide continuation of extensive paper production
for procedures being processed by the CDPA editing and word processing
function as well as the quantity of procedures being received late in
the process.

#### 1.6.1.3 FLIGHT CREW TRAINING

The contractor shall develop and maintain the SSP Crew Training (JSC
22359) and the ISS Crew Certification Guide (DR 1.6.1.3‑a). The
contractor shall develop, maintain, and conduct SSP and ISS flight crew
training in accordance with SOW section 1.6.1.1.2. (DR 1.6.1.3‑b). The
contractor shall develop, manage and execute flight specific or
increment specific crew training based on flight or increment specific
requirements (DR 1.6.1.3‑c). The contractor shall provide Astronaut
Candidate Training in accordance with the Astronaut Candidate Training
plan and schedule (DR 1.6.1.3-d). Contractor shall perform Japan Segment
Trainer (JST) training and operator functions to train Expedition crews
for ISS missions. Contractor shall add an eighth SSTF for generic
integrated simulations and flight specific SSTF load development and
training for ISS missions.

Required Service**:** Management and implementation of the Astronaut
Candidate Training Program.

Standard of

Excellence**:** All Astronaut Candidates complete program before
completion date identified in DR 1.6.1.3-d.

Expectation**:** 1 month late but in no case impact flight crew
assignments.

MER**:** 2 months late but in no case impact flight crew assignments.

Required Service**:** Management and implementation of the flight or
increment specific crew training program.

Standard of

Excellence**:** Crew training accomplished within 16 hours/week average
SMS flight specific or SSTF increment specific facility time for any
individual crew person.

Expectation: +.75 hours/week average and in no case impact safety,
mission success or major program schedule milestones.

MER: +1 hours/week average and in no case impact safety, mission success
or major program schedule milestones.

Standard of

Excellence: Crew training accomplished within 25 hours/week average
formal catalog training time for any individual crew person.

Expectation**:** +2 hours/week average and in no case impact safety,
mission success or major program schedule milestones.

MER: +3 hours/week average and in no case impact safety, mission success
or major program schedule milestones.

Standard of

Excellence: All required training accomplished at the time the crew
departs to KSC for launch and in no case impact safety, mission success
or major program schedule milestones.

Expectation: All required training accomplished at the time the crew
departs to KSC for launch and in no case impact safety, mission success
or major program schedule milestones.

MER: All training critical to safety and mission success completed at
the time the crew departs to KSC for launch and in no case impact
safety, mission success or major program schedule milestones.

#### 1.6.1.4 FLIGHT TRAINING HARDWARE

The contractor shall provide Extravehicular Activity (EVA) and Crew
equipment required for crew training in accordance with requirements
stated in the SSP Crew Training Catalog and ISS Crew Certification
Guide. Reference SOW section 1.4.9 for details of flight crew equipment.

### 1.6.2 FLIGHT PREPARATION

The contractor shall provide flight preparation products and services.
This includes flight rules/operations documentation/flight data file,
flight design, flight planning, payload integration, flight crew
integration, data collection and reconfiguration.

#### 1.6.2.1 FLIGHT RULES/OPERATIONS DOCUMENTATION/FLIGHT DATA FILE (FDF)

The contractor shall provide products and services for the production,
maintenance, and distribution of flight rules, operations documentation,
FDF and Operations Data File (ODF). The Contractor will provide the
Systems Operations Data File (SDOF) in hardcopy media (includes: provide
full editorial, word-processing, fabrication and maintenance of SODF
procedures in paper format).

Required Service: Flight critical operations documentation/data

Standard of Excellence: No significant errors detected real-time in
critical flight

operations documentation or data.

Expectation: 1 significant documentation or data error for each flight,
but in

no case impact safety, mission success or major program

schedule milestones

MER: 2 significant documentation or data errors for each flight, but in

no case impact safety, mission success or major program

schedule milestones

Standard of Excellence**:** On time delivery of all agreed upon
operations documentation

for crew review.

Expectation: One document per flight delivered late based on the agreed

upon delivery content, but in no case impact safety, mission

success, or major program schedule milestones

MER: Two documents per flight delivered late based on the agreed

upon delivery content, but in no case impact safety, mission

success, or major program schedule milestones

##### 1.6.2.1.1 FLIGHT RULES

The contractor shall provide Flight Rules documentation, publication and
change processing for All Flight and Flight Specific Flight Rules
(DR 1.6.2.1.1). The ISS Flight rules content and director office
integration activities reflects the ISS Revision C Manifest. The
contractor shall provide tracking and collecting of program requirement
changes to integrate and coordinate these changes with the flight rules.
The contractor shall develop documentation for Flight Rule Control
Board, Flight Techniques Panels, Joint Operations Panels and other
related forums.

##### 1.6.2.1.2 OPERATIONS DOCUMENTATION

The contractor shall develop procedures, publish and process changes to
operations documentation (DR 1.6.2.1.2).

##### 1.6.2.1.3 FLIGHT DATA FILE AND OPERATIONS DATA FILE (ODF)

The contractor shall develop flight crew procedures, process changes and
publish/distribute revisions for the FDF (SSP) and ODF (ISS)
(DR 1.6.2.1.3‑a). The contractor shall conduct Procedure Validation (PV)
sessions, provide PV/Data Source Information records and prepare
simpacks. The contractor shall provide flight quality fabricated FDF/ODF
to support flights and training (DR 1.6.2.1.3‑a).

The contractor shall develop and maintain POC applications software and
provide associated crew training (DR 1.6.2.1.3-C). The contractor will
develop and maintain POC management documentation.

The contractor shall provide SSP and ISS procedures and POC control
board members who participate in control board actions relative to their
tasks. The contractor shall provide an evaluation of all FDF/ODF/POC
change requests.

#### 1.6.2.2 FLIGHT DESIGN

The contractor shall manage and execute the overall flight design
processes for mission operations for the SSP and ISSP. Including
development, integration, and real-time monitoring of automated vehicles
which are associated with the ISS. These processes include flight design
requirements development, flight design products generation, flight
design post flight reconstruction, flight design process integrity data
generation, and flight design software sustaining engineering. The
contractor shall develop and integrate new capability into these
processes to support current program requirements.

##### 1.6.2.2.1 FLIGHT DESIGN REQUIREMENTS

The contractor shall provide detailed flight design requirements
development, definition, and implementation required to meet the NASA
defined mission specific requirements. When required for feasibility
assessment, the contractor shall provide specific trajectory analysis
and specific standard trajectory products to NASA, in support of the
process of defining mission specific design requirements.

The contractor shall provide adequate representation at all appropriate
technical and programmatic forums as required to maintain currency on
detailed flight specific requirements. The contractor shall develop,
implement and maintain all Flight Operations Panel (FOP) documentation.

##### 1.6.2.2.2 FLIGHT DESIGN PRODUCTS

The contractor shall deliver certified standard flight design products
resulting in a basic flight trajectory and consumables profile that
meets the requirements of the SSP and ISSP; including all associated
mission specific analysis and integration activities. The contractor
shall ensure the quality and integrity of the flight design products.
The contractor shall also provide a process for evaluation of proposed
process changes from an integrated contractor/NASA perspective. The
reconfiguration process shall also provide clear traceability of
production procedures and methods to design requirements. The contractor
shall document the training and certification process used in the
generation of the flight design products (DR 1.6.2.2.2‑b). The
contractor shall train NASA selected civil service flight design
personnel in flight design concepts and the use of flight design tools
as agreed to between the contractor and NASA.

Products shall be delivered for the functional areas of: Ascent, Orbit
(including rendezvous and proximity operations), Descent, Navigation
(ground and on-board), Flight Integration, and post flight
reconstruction. Currently these products are fully described in JSC
M8600, Flight Design Product Glossary: Flight and Cycle Specific
Products. The contractor shall develop improvements and efficiencies in
product development processes and shall provide complete product
definitions and development processes in a Flight Design Handbook and
Product Glossary (DR 1.6.2.2.2‑c). The contractor shall provide
recommendations for new capability development based on the resolutions
of in-flight anomalies.

Products shall be delivered per an appropriate number of cycles
consistent with the mission requirements as defined by NASA: mission
specific Early Assessments, Conceptual Flight Profile (CFP), Engineering
Cycle (EC), Previously Verified Load (PVL), Flight Cycle (FC), One Cycle
to Flight (OCTF) or FRR Cycle. Changes can occur during the flight
production template process, and this may require all or part of the
production process cycles to be repeated.

##### 1.6.2.2.3 FLIGHT DESIGN SOFTWARE

The contractor shall sustain all flight design and analysis software,
including software used in Mission Control in support of flights. The
contractor shall provide software standards (DR 1.6.2.2.3‑a) and
configuration management plans (DR 1.6.2.2.3‑b). The contractor shall
provide documentation for individual software applications and document
changes to these applications as they are required (DR 1.6.2.2.3‑c). The
contractor shall provide a Flight Design and Dynamics (FDD) Data
Management System Data Administration Database Administration Plan for
how FDD manages data and databases owned by FDD, residing on the IPS and
MCC computer platform(DR 1.6.2.2.3‑d). The contractor shall develop,
implement and maintain a Flight Design and Dynamics Software Engineering
Strategic Plan which sets forth goals and strategies for improving these
systems (DR 1.6.2.2.3‑e).

#### 1.6.2.3 FLIGHT PLANNING

The contractor shall generate/maintain all generic planning databases,
flight specific planning databases and increment planning databases
(ISS). The contractor shall generate the Attitude Timeline (ATL) and
develop pointing procedures/techniques and pointing data (DR 1.6.2.3-b).
The contractor shall provide ATL compatibility assessment reports (DR
1.6.2.3-b). The contractor shall document pointing and Orbiter Text and
Information System (OTIS) system software requirements and develop
required applications. The contractor shall provide planning tool
development requirements and system user testing. The Contractor will
provide institutional attitude and pointing support for ISS and STS
planning and real-time operations for MOD requirements.

The contractor shall prepare for flight/mission execution. Preparation
for fight execution includes vehicle design and operations integration,
with respect to flight design, requirements development for selected
flight control/training tools and facilities, requirements for
operations application software development, user verification and
checkout of selected application software, development and review of
flight selected operations console procedures. The contractor shall
perform flight design related Orbiter consumable analysis (propulsive
and non-propulsive), thermal analysis, robotics analysis in support of
multi-program flight design, ISS resource analysis, and ISS electrical
power analysis. The contractor shall sustain all flight systems
operations user application software, including software used in support
of systems flight design, analysis, planning, training, and flight
control. The contractor shall perform flight control systems technical
assessments for the required technical forums. The contractor shall
provide the applicable products (DR 1.6.2.3‑d). The contractor shall
develop and sustain all flight systems operations user applications
software, including software used in support of systems flight design,
analysis, planning, training, flight control and ISS ground and Flight
Portable Computer Systems (PCS) displays. The contractor shall perform
the tasks for the transition and sustaining engineering of the SFS User
applications for the Generic Command Server of the ISS.

#### 1.6.2.4 PAYLOAD INTEGRATION

The contractor shall provide Shuttle payload technical assessments
(DR 1.6.2.4). The contractor shall develop payload and cargo test
assessments and reports. The contractor shall develop documentation for
technical payload forums and develop payload annex requirements
(DR 1.6.2.4).

The contractor shall provide the dissemination and review of all payload
and ISS safety data packages, including development and dissemination of
the Integrated Cargo Hazard Assessment (ICHA) and the Integrated Safety
Verification Reports (DR 1.6.2.4). The contractor shall provide safety
assessments to the Shuttle MIR Mission safety assessment process.

The contractor shall document mission control payload facilities
requirements definition and perform requirement implementation
(DR 1.6.2.4).

#### 1.6.2.5 FLIGHT CREW

The Flight Crew is responsible to the Shuttle and ISS Programs for
certain in-line tasks. These tasks include providing Flight Crews to
execute the missions planned in the Shuttle and ISS manifest; providing
Flight Crew input to the development and assessment of new or changing
requirements in the two Programs, including participating in
development, execution, and evaluation of human piloted tests in
simulators; and providing Flight Crew input to the resolution of
operations related issues in the Programs. The contractor shall provide
specific products and services for the Flight Crew to use in the
accomplishment of these in-line tasks.

The government will lead and be accountable for new capability
development and certain non-mission specific programmatic support. The
contractor shall provide support of such government accountable
functions which include but are not limited to Shuttle upgrades, NASA's
Astronaut appearance function (including Lead and PAO Coordination
responsibilities), JSC's Flight Crew Scheduling function, NASA
requirements documented in the Space Shuttle Family Support Document
(JSC 23275), and the Payload Specialist Operations and Integration Plan
(JSC 19936). The Contractor shall further support government accountable
functions by providing the products and services described in sections
1.6.2.5.5 and its subparagraphs, 1.6.2.5.6, and 1.6.2.5.7. Contractor
participation in these functions shall be specified via technical
direction.

The contractor shall develop alternatives to those products and support
tasks that are more efficient and/or effective by taking advantage of
synergies across the Program(s), by utilization of new technology and
tools, by consolidation of functions, or by other means. The contractor
shall provide in-depth technical evaluations of the crew operational and
safety impacts of specific, identified changes to the ISS Flight
software. The contractor shall perform the tasks for the transition,
maintenance, and sustaining engineering for the Online Appearance
Scheduling Information System (OASIS) and the Astronaut Online
Scheduling System (AOSS).

##### 1.6.2.5.1 PROGRAM REQUIREMENTS DEVELOPMENT/CHANGE TECHNICAL assessments

The contractor shall provide reports, assessments, and technical
evaluations of Program changes that have potential impact to crew
procedures, safety, or operations.

The contractor shall manage the Change Request (CR) review process for
the Flight Crew, including routing of CR's for Flight Crew evaluations
and maintaining an existing database of all such reviewed CR's for
boards (or their successors) as specified in DR 1.6.2.5‑a.

The contractor shall be aware of Flight Crew official positions on
systems level hardware, software and operational procedures changes
affecting the crew.

The contractor shall evaluate all flight software discrepancy reports
and user/operational notes for crew operational and safety impacts.
During the conceptual design of each new OI, the contractor shall
evaluate the crew operational and safety impacts of concept proposals
for software changes. The contractor shall determine the flight software
code and other resource impacts of Flight Crew proposed changes to allow
the Flight Crew to develop its priorities for changes prior to the
baselining of each new OI.

The contractor shall provide in-depth technical evaluations of the crew
operational and safety impacts of specific, identified changes to Space
Shuttle hardware or operations.

For primary payloads, the contractor shall deliver the payload
requirements for on-board crew displays.

The contractor shall initiate and present changes for a wide range of
hardware, software and operations that affect the crew.

The contractor shall deliver briefings to assigned Flight Crew as
specified in DR 1.6.2.5‑a.

##### 1.6.2.5.2 SHUTTLE-MIR DOCKING INTEGRATION

The contractor shall inform the Flight Crew of all Shuttle-Mir
integration issues and assess their operational impacts. The Flight Crew
will develop positions based on these assessments which the contractor
shall document and input into the development of Shuttle-Mir operations
procedures. The contractor shall ensure that Flight Crew inputs based on
these assessments are made available to relevant Integrated Product Team
(IPT) and technical interchange meetings (TIM), including the
Rendezvous/Proximity Operations Working Group.

The contractor shall develop and review test plans for Shuttle-Mir
docking and operations ground-based tests. The contractor shall
coordinate crew participation in such tests and document the results
(DR 1.6.2.5‑a).

##### 1.6.2.5.3 SHUTTLE LANDING AND ROLLOUT TECHNIQUE DEVELOPMENT 

The contractor shall reduce the data from the Ames Vertical Motion
Simulator (VMS) Shuttle landing and rollout simulations to provide
visualizations of the simulator test results per the test and post-test
presentation requirements to be specified( DR 1.6.2.5‑a).

##### 1.6.2.5.4 FLIGHT CREW EQUIPMENT (FCE) INTEGRATION

The contractor shall manage the requirements of the Flight Crew for FCE
and establish and maintain coordination between the Flight Crew and
hardware suppliers for FCE (DR 1.6.2.5.4‑a).

The contractor shall initiate Flight Crew requested changes and present
FCE CR's representing the assigned flight crew FCE requirements to the
appropriate boards, and shall provide status to the crew members on CR's
affecting their equipment.

The contractor shall deliver to each assigned flight crew a government
furnished equipment (GFE) portable onboard computer with the training
software load for crew training. The contractor shall update the GFE
software on the computer to the flight software load with each new
release.

##### 1.6.2.5.5 OPERATIONS DEVELOPMENT FOR ISS

The contractor shall produce specific products for the Flight Crew to
use in the accomplishment of the ISS in-line tasks.

###### 1.6.2.5.5.1 FLIGHT CREW TRAINING DEVELOPMENT

The contractor shall coordinate Flight Crew input into all crew training
plans, flows, curricula, and facilities, identify and document crew
issues and crew positions, disseminate Flight Crew positions to the
relevant IPT and propose areas requiring developmental test objectives
(DTO) or risk mitigation experiments (RME). The contractor shall ensure
that the Assembly Training Plan (ATP) for the ISS accurately reflects
positions taken by Flight Crew. The contractor shall provide reports and
assessments of operational impacts of training issues.

1.6.2.5.5.2 FLIGHT CREW SUPPORT

The effort defined herein shall be specifically authorized under the
Program Provisioning Procedure as defined in Schedule Article H.35,
entitled Program Provisioning. The contractor shall perform tasks as
defined in specific supplemental agreements and PPCO's, and as
documented in the Program Provisioning Task Book (PPTB).

###### 

###### 1.6.2.5.5.3 ISS ASSEMBLY, SYSTEM AND UTILIZATION OPERATIONS ASSESSMENT AND TESTING

The contractor shall provide the Flight Crew with reports, assessments,
and technical evaluations of all ISS assembly operations and concepts,
plans, tasks, and procedures; integrated operations scenarios; flight
rules; system, module, and payload designs including functional
descriptions, drawings and schematics; change notices that affect
crew-related requirements or implementation; Flight Crew equipment
support systems including habitability support; and crew displays and
controls.

The contractor shall develop and review test plans for ISS systems,
payloads, tools, and procedures that require ground-based testing. The
contractor shall coordinate crew participation in such tests and
document the results.

The contractor shall prepare DTO or RME flight documentation and
postflight test results for ISS systems, payloads, tools, and procedures
that require a flight demonstration.

###### 1.6.2.5.5.4 RESERVED

###### 1.6.2.5.5.5 COMMON DISPLAY DEVELOPMENT

The contractor shall coordinate and consolidate all Flight Crew
requirements and deliver the results to the Common Display Development
Team (CDDT). The contractor shall ensure the resultant requirements are
in accordance with CDDT specifications.

###### 1.6.2.5.5.6 ASTRONAUT ANALYSIS AND INTEGRATION TEAM (AIT)

The contractor shall maintain an existing Astronaut AIT Action Item
database (as part of the ISS Action Tracking Application (ATA) database)
and an existing crew position database. The contractor shall update
crew-related items in the Risk Database Management Application (RDMA).
The contractor shall prepare each month a risk status report for the
Astronaut AIT, and will track the status of all crew-related risks in
the RDMA. The contractor shall manage the ISS Change Memo Review process
for the Flight Crew, including routing of documentation for evaluations
and maintaining a database of reviewed memos.

###### 1.6.2.5.5.7 RESERVED

##### 1.6.2.5.6 SHUTTLE/ISS INTEGRATION

The contractor shall provide the Flight Crew with on-orbit capability
assessments for ISS assembly and operations tasks involving the Shuttle.
These assessments shall include evaluations. The contractor shall
develop and review test plans for any SSP/ISS operations that have been
identified as requiring ground-based tests (including but not limited to
EVA, robotics, rendezvous/proximity operations). The contractor shall
coordinate crew participation in such tests and document the results.

The contractor shall prepare DTO/RME flight documentation and flight
test results reports for flown DTO/RME's.

##### 1.6.2.5.7 LIBRARY, DATABASE, AND DOCUMENTATION MAINTENANCE

The contractor shall provide support for the Flight Crew databases and
library.

##### 1.6.2.6 CREW/VEHICLE INTEGRATION AND TESTING

The government will lead and be accountable for new capability
development. That portion of 1.6.2.6 - Crew/Vehicle Integration and
Testing related to the ISS will require and consist of such new
capability development. Contractor participation shall be specified via
technical direction. As these tasks mature and become more standardized,
they can, at the discretion of the government, be transitioned from
government to contractor accountability. The contractor shall be
accountable for the Space Shuttle portion of 1.6.2.6 due to its
maturity.

The contractor shall provide the operations interface between JSC flight
operations in-line tasks and processing or launch operations at KSC and
ISSP international partner sites (DR 1.6.2.5‑a). The contractor shall
implement the Vehicle Integration Plan for the Shuttle Operational Phase
(JSC 17519).

The contractor shall coordinate and review the airlock close-out
photographs to ensure the proper configuration of EMU hardware in time
to resolve any discrepancies before final airlock close-out.

NASA Astronaut Support Personnel will continue to perform the vehicle
preparation for flight including the final switch configuration.

The contractor shall provide on-site staff at the prime and back-up
landing sites to assure arrangements for NASA approved post-landing
activities such as crew physicals, crew accommodations, crew clothing,
crew transportation, crew guests and other very important persons (VIP).
The contractor shall coordinate support requirements with the NASA
elements supporting the landing operations such as Astronaut Support
Personnel, flight surgeons, Shuttle Training Aircraft (STA) pilots, NASA
management, and public affairs.

The contractor shall, as required by NASA, provide on-site staff in
Kazahkstan, Russia, and at facilities of the international partners in
support of prelaunch testing, integration and other activities
preparatory to the launch of ISS elements.

#### 1.6.2.7 DATA COLLECTION/ RECONFIGURATION

The contractor shall operate and maintain the ISS MOD Avionics
reconfiguration tools and processes that will generate command,
telemetry, and display products required to reconfigure flight, Orbiter
Interface Unit (OIU), and ground facilities, shall provide sustaining
engineering support once tools are transitioned by the developer, and
shall support the development of recon tools through development of
operations concepts document, RID review of Level B requirements, and
User Acceptance Test/Operations Readiness Review (UAT/ORR). Production
processes include data management services, production and operations
support, and development and maintenance of related documentation. Until
ISS MOD Avionics Reconfiguration Systems (IMARS) tools are released for
production support, the contractor will provide support to the existing
manual process by providing configuration management services including
transfer of files to the IPS platform. Effective February 28, 1999, the
tasks to implement, maintain, and operate a reconfiguration platform
environment to support data and applications testing, process
development and certification and problem assessment for ISS
reconfiguration activities is the responsibility of the NASA CSOC
Contractor. Effective February 28, 1999, the tasks associated with the
operations and maintenance of the ISS MOD Avionics Reconfiguration
System (IMARS) platform is the responsibility of the NASA CSOC
Contractor.

The Contractor shall provide for the collection of requirements and
generation of products for the Mission Control Center (MCC) and provide
POCC requirements and configuration coordination.

The contractor shall support rapid development of technology prototypes
for proof of concept studies and small software development efforts
specifically relating to ISS space and ground systems displays and
controls, and advanced shuttle displays and controls. Included in this
activity are analysis and evaluation of advanced technology, and command
and control concepts.

The contractor will implement, maintain, and operate a reconfiguration
platform environment to support data and applications testing, process
development and certification, and problem assessment for ISS
reconfiguration activities. The contractor shall integrate MOD inputs to
ISS Avionics Flight Software and data to include both issues resolution
and change traffic processing; and shall perform associated technical
schedule integration. The contractor will incorporate and integrate all
IMARS tool updates as defined by NASA. The contractor will perform tasks
for data and applications testing, process development and
certification, procedure/product generation and problem assessment for
ISS Avionics Reconfiguration activities.

1.6.2.8 PCS PROJECT SUPPORT

The Government will lead and is responsible for the overall Portable
Computer System (PCS) development. The contractor shall participate in
the development and testing of the PCS interface software and core
systems displays for the on board ISS laptops. This activity will
include development of the hardware and software acquisition plans;
procurement; development and certification of a PCS test system;
configuration management (both Change Request and Discrepancy Requests)
and general engineering (i.e., maintaining Project Web site); System
administration of the PCS lab, Solaris Operating System (OS)
customization; PCS software load builds, Test and Operations (T&O)
support to the SSTF for PCS; Onboard Operations Crew Interface (OOCI)
software sustaining engineering; and PCS software porting. This activity
also includes PCS Display development; project integration tasks;
Software Formal Qualification Testing tasks; and the execution of
MEIT/HIS Testing.

### 1.6.3 RESERVED

### 1.6.4 FLIGHT OPERATIONS SYSTEMS AND EQUIPMENT

The contractor shall manage, operate, and maintain the systems in
Exhibit 1.6.4‑A in support of flight operations in the SSP and ISSP. The
contractor shall ensure flight readiness for all flight operations
systems and equipment (DR 1.5.2.4).

The contractor shall modify, upgrade, and/or improve the performance of
the systems and equipment in Exhibit 1.6.4‑A. The contractor shall
obtain NASA approval for all modifications resulting in an architectural
change. The contractor shall, as directed by the government, provide
project management and development plans (DR 1.6.4‑a) and implement
system upgrades and/or new capabilities required by vehicle/mission
changes additions, obsolete and NME equipment replacements, and/or
operational efficiencies.

The contractor shall establish agreements with non-SFOC users of Flight
Operations Systems and Equipment for services required to satisfy SSP
and ISS program requirements. These agreements shall be documented and
signed by all participants.

The contractor shall provide software sustaining engineering and perform
specific programming related tasks, including documentation development
for the advanced Control Center Technology (ACCT) project.

**Management and Integration**

The contractor shall provide management, integration, and system
engineering functions for all flight operations systems and equipment in
Exhibit 1.6.4-A. The contractor shall develop, implement and maintain a
Management Plan that addresses all systems and key operations tasks. The
contractor shall provide an Information Technology Acquisition Plan
(DR 1.1.4.1‑b).

The contractor shall establish external management interfaces and
external interface agreements as well as any other management interfaces
necessary for operations. (DR 1.6.4‑c). Also, the contractor shall
provide a FCR support position for management of the ground flight
control services.

The contractor shall develop, implement and maintain a metrics package
(DR 1.6.4‑d), that addresses each system, for measuring key aspects of
the process performance.

Required Service**:** Flight operations system availability.

Std of Excellence**:** 100% flight operations system availability for
the, SMS, SSTF, and SPF.

Expectation**:** 1.5% flight operations system non-availability for the
SPF with no impact to safety, mission success or major program schedule
milestones.

Expectation**:** 3% flight operations system non-availability for the
SMS & SSTF with no impact to safety, mission success or major program
schedule milestones.

####### MER: Significant impact to safety, mission success or major 

program schedule milestones.

Required Service: Provide sustaining engineering and maintenance and
operations support for flight operations system and equipment.

Std of Excellence: Complete and adequate Closure of Sustaining
Requirements and Discrepancy Reports within negotiated and agreed upon
user need date and in no case impact safety, mission success or major
program schedule milestones.

Expectation: 5% late, but in no case impact safety, mission success, or
major program schedule milestones.

MER**:** Significant impact to safety, mission success or major

program schedule milestones.

**Maintenance and Operations**

The contractor shall provide maintenance and operations services for all
flight operations systems and equipment in Exhibit 1.6.4-A, and the
software applications for the MCC Electronic Document project (EDP)
System .

The contractor shall provide maintenance of the Government computer
systems and shall operate the computer equipment including any computer
equipment added or changed during the contract period. The contractor
shall operate the tape libraries and tape silo automated storage
systems, and coordinate data information retention and accountability
with other libraries or archival facilities provided and operated by
other JSC contractors or Government personnel.

**Hardware Sustaining Engineering**

The contractor shall provide sustaining engineering and modification of
the flight operations systems hardware in Exhibit 1.6.4-A. The
contractor shall design modifications to the baseline systems including
requirements, functional design, and documentation. The modifications
shall be based on vehicle/mission changes/additions, obsolete
equipment/component replacement, and operational efficiency
improvements.

The contractor shall conduct and schedule design reviews for all
appropriate levels of change. The contractor shall provide a Functional
Design Review (FDR) Report (DR 1.6.4‑e). System or configuration changes
that do not affect the functional capability of a system or the
hardware/software architecture do not require formal design reviews.

The contractor shall provide continuing system engineering support for
systems during their operational lifetime. This support shall encompass
all technical support beyond normal operation and maintenance.

**Software Sustaining Engineering**

The contractor shall maintain commercial off-the shelf software (COTS)
and maintain and modify custom software for the flight operations
systems in Exhibit 1.6.4-A. This includes selected flight controller
user software and the transition and software sustaining engineering of
the MSC User applications.

The contractor shall conduct and schedule functional design reviews for
all appropriate levels of changes. The contractor shall provide a FDR
report (DR 1.6.4‑e). System or configuration changes that do not affect
the functional capability of a system or the hardware/software
architecture do not require formal design reviews. The contractor shall
maintain software documentation throughout the development and
maintenance of software systems.

The contractor shall define procedures to establish and maintain
software configuration control, discrepancy resolution, and modification
definition and implementation. The contractor shall provide sufficient
detail to establish the applicability or exceptions of the plan to the
various types of software (mission/non-mission, systems/applications,
etc.). The contractor shall provide integration of software and
associated mission reconfigurations as development is completed.

Required Service: Management of software critical discrepancies to
enable the system to support flight operations.

Std of Excellence: No critical discrepancies in mission support software
after the scheduled start of mission specific training.

Expectation: No critical discrepancies after the start of mission
specific training that impact safety, mission success or major program
schedule milestones.

MER: More than 1 critical discrepancy(s) after the start of mission
specific training that impact(s) safety, mission success or major
program schedule milestones.

**Integration and Installation**

The contractor shall integrate and install equipment, software, and
reconfiguration products produced or procured by the development
contractor for flight operations systems in Exhibit 1.6.4-A. The
contractor shall determine integration schedules that ensure facility
availability and installation schedules are sufficient to support the
delivery commitments of the development contractor. The contractor shall
integrate support during all phases of a development project which will
require multiple interfaces with the Government and the development
contractor. The contractor shall work with development contractors to
establish an agreement that defines the division of roles and
responsibilities regarding installation, integration, maintenance, and
operation activities, and that defines the services that will be
provided to development contractors. Agreements shall be documented and
signed by all participants.

**Flight Operations Logistics**

The contractor shall perform logistics for flight operations (DR 1.4-c).
The contractor shall provide a fully operational logistics system that
improves productivity and minimizes organizations providing like kinds
of products and services. The contractor shall provide transportation,
shipping, receiving, warehousing, and distribution services.

The contractor shall perform the tasks required for hardware
replacement, software porting and validation on the Integrated Planning
System (IPS) platform, denoted as the Equipment Replacement Phase II
project, and upon project completion (scheduled for FY99) will be
transitioned to the CSOC contractor.

#### 1.6.4.1 MISSION CONTROL CENTER (MCC)

The contractor shall develop, maintain and modify user interfaces
vehicle-specific user application software and configuration scripts for
user-configurable software required to support command and control
capabilities for mission operations for SSP and ISSP \[including Group
Administration functions for the HSG in Mission Control Center-Moscow
(MCC-M), and development and maintenance of software applications to
monitor crew health and environment aboard the ISS\]. The contractor
shall ensure SFOC-generated software to be integrated in the MCC is
compliant with MCC standards. The contractor shall ensure that critical
software is compliant with NASA critical processor policies. The
contractor shall sustain the ICC/mainframe systems of the MCC. The
contractor shall provide mission specific baseline management and
control. (See exhibit 1.6.4-A, Flight Operations Systems.) The
contractor shall perform integration tasks for the ISS Program in the
areas of network requirements. The Program Requirements Document (PRD)
analysis function transitioned to the CSOC contractor and will no longer
be a requirement of the SFOC contractor. The ISS NACAIT function
transitioned to the CSOC contractor and will no longer be a requirement
of the SFOC contractor.

The contractor shall perform additional Software Sustaining Engineering
tasks for Manual Procedures Viewer (MPV) and Workflow applications with
extended development periods and subsequent delay in transition to SFOC.

1.  MCC-OSHA STANDARDS

The contractor shall perform the necessary tasks (e.g., procurement,
integration, installation, maintenance and operations) to ensure the MCC
facility meets the required OSHA standards.

2.  **APOLLO MOCR**

The contractor shall develop, procure, install, and maintain a
multimedia network system (e.g., lighting control, projection displays,
time displays consoles, event indicators, in room audio) for providing
continuous tour presentations of Apollo era.

#### 1.6.4.2 INTEGRATED TRAINING FACILITY (ITF)

The ITF consists of hardware, platform software (custom and COTS), and
mission specific application software required to provide flight crew
and mission controller part task training, standalone and integrated
simulations and testing capabilities for the mission operations in
support of the SSP and ISSP. The Contractor shall document procedures
for maintenance and operations of training facilities within the ITF (DR
1.6.4.2-a). The contractor shall develop the software interface to route
SMTF video to the SSTF training facility and SSTF video to the SMTF
training facility. The Contractor as of October 1, 2001 (FY02) will no
longer have the responsibility to maintain and operate the MDF.
Contractor transition reconfiguration and sustaining engineering
activities for the SSI and ICM software applications to SFOC and perform
SSE tasks for the SSI software. The contractor shall perform the tasks
required to produce three lightweight payload mockups per year for FY00
and FY01, and monitor MRMDF operations to gain insight to facility
operations for future transition. The contractor shall upgrade the SMS
(GNS & FB) visual Image Generators (IGs) to ensure the SMS has adequate
visual fidelity for training astronauts for ISS assembly.

#### 1.6.4.3 INTEGRATED PLANNING SYSTEM (IPS)

The contractor shall develop, maintain and modify user interfaces,
vehicle-specific user application software and configuration scripts for
user-configurable software required to support planning and analysis for
mission operations for SSP and ISSP. The contractor shall ensure
SFOC-generated software to be integrated in the IPS is compliant with
IPS standards. The contractor shall provide mission specific baseline
management and control. (See exhibit 1.6.4-A, Flight Operations
Systems.)

#### 1.6.4.4 SOFTWARE PRODUCTION FACILITY (SPF)

The SPF consists of hardware, platform software (custom and COTS), and
mission specific application software required to provide
payload/vehicle requirement collection, integration and validation
support; MCC console information reconfiguration; SMS training
information reconfiguration; flight software development support, and
data and flight software reconfiguration and testing capabilities for
the mission operations in support of the Space Shuttle.

Changes to SPF hardware and software shall be coordinated with affected
SPF users. Change concurrence shall be obtained prior to implementation
from affected non-SFOC SPF users.

##### 1.6.4.4.1 RESERVED

##### 1.6.4.4.2 SPF-UNIQUE INSTALLATION SERVICES

The contractor shall provide installation services for flight software
development. The estimated minimum standard for notification by the
development contractor, of the requirement for installation is 30 days.

1.6.4.5 RESERVED

1.6.4.5.1 RESERVED

1.6.4.5.2 RESERVED

#### 1.6.4.6 RESERVED

1.6.4.7 RESERVED

#### 1.6.4.8 RESERVED

#### 1.6.4.9 OPERATIONS SUPPORT SYSTEMS

The contractor shall provide the services and materials required to
support the management and operations for all technical systems used in
flight operations. Examples of these are, Flight Planning System (FPS),
MOD Information System (MODIS), and Attitude & Pointing Flight
Production Facility (APFPF).

#### 1.6.5 NASA MANAGED MISSION EXECUTION SUPPORT

The Government will lead and is responsible for the technical execution
of all operations related activities of flight control teams (FCT) which
will be comprised of both government and contractor personnel. The
contractor shall participate in flight control teams for both the SSP
and ISSP. Real time console support provided by those teams during
mission periods shall be either on-call or continuous
[mission]{.underline} support. Real time support encompasses all aspects
of flight control, from selected prelaunch planning through ascent,
orbit, and landing for Shuttle flights, and for continuous operations
for ISS increments. The contractor's organization and personnel shall be
fully responsive to the FCT\'s requirements and direction.

Contractor flight control team participation includes both Contractor
Accountable Functions (CAF) and Government Accountable Functions (GAF)
for the flight control team positions. Nothing herein shall be deemed to
limit the contractor's obligations under the contract. The contractor
will supply all personnel required to support CAF flight control team
positions. Those personnel will be fully trained and certified in
accordance with established training and certification requirements. The
contractor shall prepare a Mission Support Plan for CAF flight control
team positions and shall document CAF accountable console products and
processes. NASA/Contractor agreements for GAF task execution shall be
specified in the Government Accountable Functions Directive (GAFD) and
reported consistent with Flight Operations Metrics requirements. The
skill mix, size and split between government and GAF contractor
participation will be established through concurrence with the annual
operating plan. The contractor shall perform flight control functions
for SSP and ISS missions as documented in the Fiscal Year (FY)
Government Accountable Functions Directive (GAFD).

The contractor shall participate in the following flight control team
functional areas: Flight Systems, Flight Planning/Payloads/Assembly,
Flight Design and Dynamics, International partners' coordination,
International Operations and other areas as specified by the government.
This participation includes both execution of flight and mission
operations and requisite flight preparation. Specific examples of
contractor participation include development and execution of flight
plans and ISS mission plans; Mir payload integration and operations; ISS
integrated testing and verification; development and maintenance of the
ISS Lexicon; development, training, and execution of operational generic
and flight-specific EVA's; vehicle design and operations integration;
operations requirements development for flight controller training tools
and facilities; operations application software verification and
checkout; development of console reference and real-time support
products; EVA/Robotics and payloads mission integration; FDF/POC/Safety
Process Integration; development and execution of flight controller
mentor training; pre- and post- flight analysis; pre-mission facility
checkout; and ISS assembly Integration. Flight controllers shall also
participate in the development of new operations concepts and
requirements for the SSP and ISSP, including the development of new
technology prototypes and advanced flight control software applications.
Training for all flight controller personnel is specified in SOW section
1.6.1.2. Both government and contractor (CAF and GAF) flight controllers
shall be directly involved in the definition of training requirements.
The government will also certify flight controllers for specific MCC
real-time monitoring, analysis, command, and control operations. In
addition to government certification requirements, the contractor shall
certify flight controllers for CAF FCT positions. The contractor shall
provide **limited** flight control team functions **(the CATO, PHALCON,
and THOR disciplines will be eliminated)** at Mission Control Center -
Moscow (MCC-M) for the Houston Support Group (HSG) through the period of
the contract \[(including providing Operations Data File (ODF)
coordination to integrate the joint data file requirements for
implementation for ISS missions.

#### 1.6.5.1 FLIGHT SYSTEMS

The contractor shall provide flight control team functions to accomplish
vehicle and flight systems operations as required to assure safety and
mission success (including systems design and operations integration for
CRV). Requisite vehicle and flight systems flight control team functions
include: Data Processing Systems; Command and Data Management Systems;
Communications and Tracking Systems; EVA; Robotics Systems; Mechanical
Systems; Booster Systems; Guidance Navigation and Control Systems;
Propulsion Systems; Guidance and Controls/Prop systems; Electrical Power
Systems; Environmental Control, Life Support, Thermal Systems;
Mechanical/Structures, Logistics and Maintenance Systems; Shuttle
In-flight Maintenance; and ISS Resource Analysis. inherent in these
functions are the maintenance and development of associated ground and
crew procedures and ground computer operations. Also, flight controllers
shall participate in EVA design and training, Spacelab systems, and new
operational capability projects. Provide continuous MCC flight control
support at the Communications and Tracking position commencing with ISS
mission 2A. The contractor shall perform Integrated Verification and
Testing for ISS vehicle and ops facilities. The contractor shall develop
ISS Operational products to support ISS (including Ground and Flight
display and computation development; Flight software reconfiguration
product development; command and telemetry definition; development of
ISS ground and onboard procedures). The contractor shall perform
integration tasks for the ISS Program in the areas of robotics
requirements. The contractor shall perform tasks for the development of
ISS procedures, flight rules, handbook drawings and display; Integrated
Verification and Testing (IVT) per the manifest baseline defined in the
ISS Integrated Flight Schedule, Revision F, which re-baselines ISS
Assembly completion to 2006. The contractor will perform ISS Mission
Integration and schedule management tasks to include mitigation of SSTF
load development tasks (i.e. problem mitigation, work flow analysis, and
assessment). The contractor will perform the Ops Lead function for the
ISS activities in FY01. In FY02, the Ops Lead functions for the ISS
activities will transition from the contractor and be performed by civil
servants. The contractor shall perform the tasks for the integration and
management of the mitigation of SSTF load development, ISS flight
specific Mission Configuration Tests and perform the role of focal point
for IP mission preparation activities.

#### 1.6.5.2 FLIGHT PLANNING/PAYLOADS/ASSEMBLY

The contractor shall provide flight control team functions to accomplish
flight planning, payloads, ISS Inventory development and maintenance,
both pre-increment and real-time support; ISS Operations Planning
activities and assembly operations as required to assure safety and
mission success. Requisite flight planning, payloads, and assembly
flight control team functions include: flight and mission activity
planning; payload operations and associated integration; assembly and
checkout plan and operations; specialty flight phase support; attitude
timeline and pointing; on-orbit inventory and storage. inherent in these
functions are the maintenance and development of associated ground and
crew procedures and ground computer operations (including RF LAN for
ISS). The contractor shall perform Integrated Verification and Testing
for ISS vehicle and ops facilities. The contractor shall also perform
mission operations design integration for related automated vehicles
\[i.e., Crew Return Vehicle (CRV)\]. The contractor shall provide ISO
and CIO activities for real-time operations of the ISS during crew wake
up. Perform off-console inventory management and updates to the IMS
databases for both ground and on-orbit computer system including
response to critical discrepancy reports and modifications to improve
on-board efficiency of the IMS. Contractor ISO activities will include,
but not limited to tracking manifested hardware, stowage, transfer
processes, database maintenance, Russian and US software integration,
and crew concerns resolution. Contractor CIO tasks will include, but not
limited to the PLugin UTilization Officer (PLUTO) backroom position.

#### 1.6.5.3 FLIGHT DESIGN AND DYNAMICS

The contractor shall provide flight control team functions to accomplish
flight design and dynamics operations as required to assure safety and
mission success. Requisite flight design and dynamics flight control
team functions include: flight dynamics and trajectory control; onboard
guidance and navigation; ground navigation and tracking; launch, ascent,
and abort analysis; entry, landing and winds analysis; rendezvous and
proximity operations analysis; landing operations coordination. inherent
in these functions are the maintenance and development of associated
ground and crew procedures and ground computer operations. The
contractor will provide system administrative responsibilities and
software programming in conjunction with the ISS Trajectory Operations
Planning Officer, the Contractor shall restore the TOPO staffing
position to required level to perform tasks for ISS assembly and real
time operations dictated by the original Station Assembly sequence plan.
The contractor shall provide a dedicated team for performing independent
verification testing (IVT) for Flight Design and Dynamics MCC
ascent/entry/orbit displays and applications maintained within the
Trajectory Operations Computer Software Support (TOCSS) laboratory.

1.6.5.4 FLIGHT OPERATIONS DEVELOPMENT

The effort defined herein shall be specifically authorized under the
Program Provisioning Procedure as defined in Schedule Article H.35,
entitled Program Provisioning. The contractor shall perform tasks as
defined in specific supplemental agreements and PPCO's, and as
documented in the Program Provisioning Task Book (PPTB).

## 1.7 NASA MANAGED ACTIVITIES

The contractor shall participate in NASA-managed activities as addressed
in the following subsections. Such participation shall be as specified
in appropriate

technical direction, including concurrence with annual SSP and ISSP
operating plans.

### 1.7.1 DEVELOPMENT 

The contractor shall participate, when required, in Government-initiated
SSP special studies and development projects, as follow:

Development of requirements for initial concept development; design
reviews providing technical assessments and evaluations as appropriate
to insure that the design meets the requirements.

Engineering services (including design), procurement, fabrication,
installation, support to installation by another contractor, activation,
validation, and/or turnover activation related to safety, performance
and obsolescence upgrades; e.g., , GSE.

Engineering services supporting NASA management of contract efforts to
be transitioned to SFOC responsibility in Phase II. SFOC will assume
management responsibility for these services in concert with the Phase
II contract transitions.

Non-repetitive tasks and efforts such as requirements development,
analysis, and assessments related to SSV/Cargo, SSV/ISS and SSV/MIR
integration and to integrated SSV enhancements. Included in this
activity are analyses required to define generic induced environment
design and certification envelopes and all systems analyses required to
demonstrate compliance with all SSP requirements. The contractor shall
provide for the design, development, fabrication, certification, and
delivery of all cargo integration hardware (DR 1.4.1.5.1-a, 1.4.1.5.1-b,
and 1.4.1.5.1.-c). The contractor shall conduct design studies, produce
engineering drawings and associated list, configuration documentation,
installation instructions, performance verification requirements and
specifications, and acceptance data packages for the hardware that
comply with NSTS 07700-10-MVP-01, Space Shuttle Master Verification
Plan.

#### 1.7.1.1 KSC SHUTTLE DEVELOPMENT ACTIVITIES

The contractor shall participate, as required, in Government initiated
SSP program special studies and development projects.

#### 1.7.1.2 KSC CONSTRUCTION OF FACILITIES (CofF) ACTIVITIES

The contractor shall participate, as required, in Government initiated
CofF special studies and development projects.

1.7.3 ISSPO SUPPORT

The effort defined herein shall be specifically authorized under the
Program Provisioning Procedure as defined in Schedule Article H.35,
entitled Program Provisioning. The contractor shall perform tasks as
defined in specific supplemental agreements and PPCO's, and as
documented in the Program Provisioning Task Book (PPTB):

ISS Operation Requirements Development & Integration

ISS Cargo Integration

ISS Assembly & Manifest

ISS Vehicle Integrated Performance & Resources

ISS Launch Package & Increment Integration

ISS Payloads

ISS Program Integration

ISS Cargo Compatibility Analysis

### 1.7.4 PROGRAM REIMBURSEABLES 

The effort defined herein shall be specifically authorized under the
Program Provisioning Procedure as defined in Schedule Article H.35,
entitled Program Provisioning. The Contractor shall participate, when
required, in Government initiated projects ancillary to the SFOC.

#### 1.7.5 SRB DEVELOPMENT ACTIVITIES

The contractor shall participate, as required, in Government-initiated
SRB program element special studies and development projects.

1.8 International Space Station Program (ISSP)

The contractor shall provide support to the ISSPO in the areas of
Management Information Systems, Safety and Mission Assurance,
Configuration Management, Sustaining Engineering, Meetings/Mission
Evaluation Room, and Logistics and Maintenance.

1.8.1 ISSP MANAGEMENT INFORMATION SYSTEMS

The contractor shall provide information systems expertise to integrate
and resolve administrative hardware, software, and network related
issues for the ISSP and the International Partner (IP) representatives.
The contractor shall provide technical coordination for IP access to ISS
applications and to resolve IP user problems. The contractor shall
coordinate the development of an overall International Space Station
(ISS) network architecture plan, and perform ad hoc trade studies for
ISS networking issues. The contractor shall conduct and/or participate
in technical meetings to complete the identified products.

The contractor shall provide Information Technology (IT) security
management for ISSP Information System resources and IT
facilities/systems. The contractor shall review and make recommendations
for the Information Systems Analysis and Integration Contract (ISAC)
Disaster Recovery and Continuity of Operations Plan, the ISAC Security
Plan and the Software Development and Integration Lab (SDIL) Security
Plan. The contractor shall perform security audits, handle and report IT
security incidents.

The contractor shall provide move and facilities coordination for
personnel and property controlled by the ISSP. The contractor shall also
provide points of contact for administrative actions associated with
ISSP telephone services and maintain the internal ISSP Equipment
Database.

The contractor shall provide the primary point of contact for ISSP
Service Request (SR) coordination. The contractor shall maintain and
status the internal database for ISSP SRs, and provide submission of
ISSP SRs to the JSC Information System Directorate (ISD). The contractor
shall participate in weekly Information System (IS) boards, meetings and
forums and provide technical administrative support. The contractor
shall provide data inputs to the Johnson Space Center (JSC) CIO database
on ISSP IS technology related procurement transactions. The contractor
shall assist in compiling information for ISS IT requirements and the
fiscal year Information Technology Plan.

1.8.2 ISS SAFETY AND MISSION ASSURANCE (S&MA)

The contractor shall provide program-level quantitative risk analysis
for the ISSPO Safety and Mission Assurance function. The contractor
shall provide data entry for the ISS Risk Data Management Application
(RDMA) for the Program Risk Advisory Board (PRAB), and perform
probability risk assessments. The contractor shall develop and maintain
the program-level Risk Posture Report; document the risk analysis
process; and perform special study risk analysis as requested by Program
Management. The contractor shall also perform quality assurance tasks,
including bilateral contract reviews, documentation audits, and meeting
participation.

The contractor shall integrate the requirements definition and
administration of the ISS Problem Reporting and Corrective Action
(PRACA) database. The contractor shall prioritize PRACA database
requirements, and define and coordinate release schedules with ISS PRACA
database developers. The contractor shall define the process for data
exchange, problem tracking, and problem resolution for NASA and IPs
ground and on-orbit issues. The contractor shall perform database
training for new ISS PRACA users.

The contractor shall perform quality assurance assessments of contractor
and IP non-conformance processes, including the review, disposition and
approval of non-conformances. The contractor shall participate in
Functional Configuration Audits (FCA)/ Physical Configuration Audits
(PCA) for ISS facility class payloads as coordinated with the customer,
reviewing as-built versus as-designed documentation against customer
provided criteria for ISS S&MA impacts.

1.8.3 ISS DOCUMENTATION MANAGEMENT

The contractor shall provide documentation management required for
processing of baselines, revisions and changes other than to ISS NAS
15-10000 documents.

1.8.4 ISS SUSTAINING ENGINEERING (SE) -- HARDWARE HISTORY RETRIEVAL
SYSTEM (HHRS)

1.8.5 ISS MEETING SUPPORT

The contractor shall provide technical administrative support for ISSP
meetings, teleconferences, and forums for ISSP.

1.8.6 ISS LOGISTICS AND MAINTENANCE (L&M)

The contractor shall perform crew provisioning tasks for ISS crew items
identified by the Flight Crew equipment office and IPs as defined in SSP
50409, Crew Provisioning Management Plan (CPMP). The contractor shall
coordinate individual crew requirements\' inputs (US and Russian)
developing inputs to the manifesting process for each flight at Launch
minus (L-) 12 months (final delivery) for the Increment Definition and
Requirements Document (IDRD) Annex 1, On-orbit Manifest Requirements.
The required source data is provided as Government Furnished Data (GFD).

The contractor shall perform Government Furnished Equipment (GFE) L&M.
The contractor shall provide Logistics Support Analysis (LSA) and
Logistics Support Analysis Report (LSAR) as defined by MIL-STD1388-2A
and in accordance with the Integrated Logistics Support Plan
D684-10041-1, Volume 1 through 10. The contractor shall develop manual
fault detection/fault isolation (FD/FI) up to the interface point of the
GFE; however, the contractor shall not be responsible for FD/FI from the
interface into NAS 15-10000 integrated systems. The contractor shall
develop LSAR products for GFE ORUs identified in the ORU List dated
6/30/99.

The contractor shall provide manifest surveillance for bar code label
production, distribution, and database inputs. The contractor shall
process requests for ISS hardware bar code labels based on manifesting
documentation, and in compliance with SSP 50007, IMS Label Specification
Document. The contractor shall participate to identify new equipment and
technology that improves IMS processes.

The contractor shall develop for each planning period an IDRD Annex 2,
On-orbit Maintenance Plan, and provide maintenance requirements to IDRD
Annex 3, Imagery Requirements. The contractor shall track on-orbit
maintenance requirements as set forth in the Integrated Logistics
Support Plan, D684-10041-1 Volumes 1 through 10. The contractor shall
perform assessments of new tools, test equipment, and flight support
equipment for on-orbit maintenance. The contractor shall coordinate
on-orbit maintenance activities and monitor flight hardware by serial
number.

The contractor shall perform logistics engineering analysis. The
contractor shall provide reviews/analysis of ISS logistics products
delivered to NASA, recommend acceptance or rejection, and recommend
recovery plans for rejected products except for spares. Performance is
established in the Integrated Logistics Support Plan D684-10041-1,
Volume 1, Books 1 through 10. The contractor process shall provide
review/analysis for ORU's identified in the ORU List dated 6/30/99. The
contractor shall support up LSAR reviews biannually. The contractor
shall participate in ISS element level FCA's.

The contractor shall coordinate logistics requirements between the IPs
and NASA. The contractor shall provide technical inputs for the
development of Bilateral Data Exchange Agreement Lists (BDEALs),
Memorandums of Understanding (MOU), Memorandums of Agreement (MOA), and
International Government Agreements (IGAs).

The contractor shall monitor quantities, location, and certification
data packages for spares. The contractor shall participate in ISS
element level PCA's. The contractor shall also provide Fleet Resource
Management (FRM) coordination between JSC, fleet resource users, and
Kennedy Space Center (KSC) FRM assets. The contractor shall provide
'on-call' technical expertise to the MER Manager and Operation Support
Officer (OSO) for ISS hardware. The contractor shall provide 24 hour
scheduled physical staffing during assembly flights and as required for
anomaly resolution.

2.  Space Shuttle Upgrades Development (SSUD)

This section defines the tasks to be performed by the contractor in the
development and implementation of SSP upgrade projects, including
management and integration of efforts to be performed by subcontractors.
The contractor shall manage projects, as described in the sections
below, for SSP upgrades development in accordance with the Space Shuttle
Program Upgrades Management Plan (NSTS 37400).

2.1 Program and Business Management

The contractor shall provide program and business management for SSP
upgrades and development efforts through FY 03. This includes management
and reporting of technical, cost and schedule performance of the design,
integration, production, certification, and transition to operations.

2.2 Systems Engineering and Integration

The contractor shall provide system integration, safety, quality and
mission assurance coordination across all SFOC program elements,
ensuring successful integration between operations and development
efforts through FY 03.

3.  Change Impact Assessment

The contractor shall perform studies to assess the impacts of a project
or projects, and/or develop early ROM cost estimates. These efforts will
be directed under Exhibit H of Attachment J-19, Program Provisioning.

4.  Cockpit Avionics Upgrade Phase II

The contractor shall perform activities to develop system requirements
for the Cockpit Avionics Upgrade from the Cockpit Council and other
sources, project management support, acquisition and procurement
activities, hardware and software prototyping, and ground facilities
integration for SPF, SMS, and SAIL in accordance with SOW included in
paragraph 2.1 of CPA \# SUD-005R1.

Cockpit Avionics Upgrade Phase III

As defined in CPA SUP-011 paragraph 4.1, the Contractor shall provide
Cockpit Avionics Upgrade (CAU) Increment 1, which includes design,
development, certification, and delivery of hardware and software for
four Orbiters, CAU Project Development Plan (PDP), a lifetime purchase
of spares, and hardware and software for ground support facilities at
the Johnson Space Center and the Kennedy Space Center. Additionally, the
Contractor shall provide requirements definition for CAU Increment 2,
Enhanced Caution and Warning (ECW).

Cockpit Avionics Upgrade Phase III

As defined in CPA SUP-038 paragraph 4.3.1, the Contractor shall provide
the Cockpit Avionics Upgrade Scar Option, which includes design,
Electrical Changes Notices (ECN) and Engineering drawing revisions,
preparation of Engineering Orders (EO) incorporations, parts procurement
and kitting, procurement of scar mod kit unique hardware, hardware
extracted from baseline CAU kits, inspections of Scar kitting, and Scar
Mod kit Ship-set Delivery for OV-102, OV-103, OV-104, and OV-105.

2.5 EAPU

The contractor shall perform additional tasks to support final design
requirements prior to implementation of the EAPU. These tasks include,
among others, EAPU planning and test requirements, battery analysis and
mock-up, EPD&C system (brass board) support for the second EHDU and
cooling systems, system requirements review, and the Phase IV ROM. The
contractor shall comply with the complete task description as contained
in paragraph 4.3 of Change Partnering Agreement (CPA) #SUP-003.

2.5.1 EAPU Phase III

The contractor shall perform EAPU Phase III, beginning flight design
activities and bringing the EAPU Project to a level of maturity to
support a NASA Program Commitment Authorization.

2.5.2 EAPU Phase III

The contractor shall perform EAPU Phase IIIA which includes a technical
risk reduction evaluation of the requirements and design concept and
brings the project to a level of maturity to support a NASA decision to
continue into the implementation-planning phase.

2.6 Thrust Vector Control (TVC) Upgrade

In accordance with the Statement of Work contained in Exhibit A of CPA
package CPA-MSFC-027, the Alternate TVC Upgrade Initiative overall
effort shall identify an enhanced second generation SRB Thrust

Vector Control System, thereby eliminating the use of hydrazine as a
system fuel. An in-depth trade study of candidate systems, supplemented
by technology demonstrations on Electric APU, Helium Powered APU, Solid
Propellant Gas Generator, and Thermal Batteries shall be conducted to
determine the optimum system for SRB application."

1.  Thrust Vector Control (TVC) Upgrade Phase II, Formulation

In accordance with the Statement of Work contained in Exhibit A of CPA
MSFC M-049, the Formulation Phase will take the 'feasible' upgrade
concept selected through the Advanced SRB Concept Selection Process and
develop sufficient detail to produce a 'functional' baseline from which
a Preliminary Design can be generated; and firm cost, schedule, and
technical commitments can be established. Major Milestones include SSP
Panel Review, USA&SSP Review Boards, Program Requirements Review (PRR),
System Requirements Review (SRR), System Definition Review (SDR), and
Program Commitment Agreement (PCA). In addition to Helium Auxiliary
Power Unit and Helium Distribution Assembly requirements definition and
Helium blowdown tests, other major tasks include Water Impact Risk
Mitigation and Helium Mass/ Margin Risk Mitigation.

2.7 Ku-Band Communications System

The contractor shall perform trade studies activities required to
evaluate functional requirements options, identify options, provide
recommendations, and begin preliminary functional requirements
definition of the Ku-Band Communications System in accordance with the
SOW included in CPA \# SUD-008 paragraph 2.2.

8.  Rendezvous Proximity Sensor System Pre-Formulation

The contractor shall perform trade study activities required to evaluate
functional requirements options. The results of the trade studies will
be used to provide options and recommendations to the Space Shuttle
Program in accordance with paragraph 2.1 of the CPA \# SUD-013.

9.  Communications and Tracking System

2.9.1 The contractor shall complete the Formulation Phase of the
activities required to upgrade to an integrated Orbiter Communication
and Tracking System, from Program Requirement Review (PRR) through
completion of the System Requirements Review (SRR).

11. Avionics Instrumentation System (AIS)

The contractor shall provide the definition of a replacement system for
the MADS/OEX function on the orbiter in accordance with the SOW included
in CPA \# SUD-012 paragraph 2.3.

2.12 Command Receiver Decoder (CRD) Production

In accordance with Exhibit F to CPA Package MSFC M--024, 32 (8 Flight
Sets) next generation Command Receiver Decoder to replace the current
Range Safety Distributor (RSD) and Integrated Receiver Decoder (IRD)
elements of the SRB Range Safety System will be produced. Specifications
are 10SPC-0232, Rev 1; and CEI Part 1, Integrated SRB, 10CEI-001. The
new design replaces the Pyrotechnic Initiator Card (PIC) with Direct
Current Firing Circuit (DCFC).

2.13 Altitude Switch Assembly (ASA) Design, Development Qualification &
Production

In accordance with CPA Package MSFC M--016, 24 next generation Altitude
Switch Assemblies to replace the current ASA will be designed,
developed, qualified and produced. The design, development,
construction, and test requirements should be in accordance with
preliminary Specification 10SPC-0242 dated November 29, 2000, and
Contract End Item Specification 10CEI-0001. This activity will include a
Preliminary Design Review, Critical Design Review, and a Design
Certification Review with NASA participation. This ASA task is
predicated on using Configuration A Sensor (GP:50 sensor with CMCEC
interface board). One configuration B Sensor (GP:50 sensor with integral
compensation electronics) will be procured with no testing as a risk
mitigator.

2.14 X-Ray Exposure Cell Phase I

Phase I of the project is to study feasibility of design, fabrication
and installation of a radiation containment cell, x-ray equipment
robotics, and filmless radiographic technology. USA shall develop a
solicitation to several vendors for their recommendations for an
automated X-Ray exposure cell located in three potential locations. The
vendors shall provide sketches of their recommendations and cost for
implementation. In support of the solicitation, USA shall develop a
Statement of Work for the vendor that identifies the Engineering
criteria for the cell. This shall include, but not be limited to
Quality, Safety, NDE, M & P, and Facility Engineering requirements. As a
result of the study, USA shall provide an Engineering assessment, site
recommendation and develop a cost for implementation. USA shall develop
a presentation package to be given to MSFC for concurrence prior to
submitting to the IES Board requesting implementation funding.

2.15 Small Boat Davit System

USA shall procure two type PIV 3.0 A Davit Systems or equivalent,
analyze decks for required modifications, reinforce/modify decks as
required, and install and test one of the Davit Systems on each of the
two SRB recovery ships."

2.16 Enhanced Diver Operated Plug

USA shall develop and fabricate four (4) booster dewatering plugs that
streamline the design for installation, reduces the workload on divers
at depth, and automates the locking leg action. The design will be based
on Prototype EDOP currently in work, the existing DOP design, and
existing hardware where practical."

2.17 Real Time Visualization

The contractor shall perform a pilot study of the Human Factors,
Personnel Safety, and Flight Hardware Safety aspects related to the
Orbiter & GSE Configuration, and develop the technical process for
utilization of real time visualization using current computer
visualization technology.

2.18. Virtual Reality Simulations -- Orbiter Temporary Access
Improvements (IES project)

USA Design Engineering will provide 3D models of platforms and rails in
I-DEAS format that will be converted by VAMS for use in development of
VR simulations. USA Design Engineering will generate conceptual models
for the following:

> ESR K16997 -- OMS Pod leading edge access when vertical at 35' @ HMF
> M7-961
>
> ESR K16993 -- Stinger/Up-firing Thruster access at the Y-web for OPF 2
> & 3
>
> ESR K17001 -- OMS Pod access to flat side when vertical at 19' @ HMF
> M7-961

ESR K16996 -- Orbiter Forward Electrical Manifold access in OPF 3 only

ESR K16964 -- Orbiter access to Engine Cavity #1 in OPF\'s 2 & 3

ESR K17000 -- Orbiter Elevon fall protection barrier in OPF\'s 2 & 3

> ESR K16994 -- Orbiter access between OMS Pods & vertical stabilizer in
> OPF 2 only.

USA VAMS will create Virtual Reality simulations of the Platforms and
barrier for OPF 3 and the HMF. USA VAMS will convert 3D I-DEAS models of
OPF 2 items into IGES format and transfer them to Boeing KSC Design
Visualization Group for their use in developing VR simulations for OPF 2
items. USA will provide miscellaneous software and hardware items to
support the project and increase 3D modeling and VR capabilities to meet
the project schedule. USA will increase 3D modeling and VR simulation
capabilities to support the project schedule. USA will deliver VR
simulations of HMF and OPF 3 conceptualized designs in VRML format on
CD. 3D conceptualized models will be provided in I-DEAS and IGES format
on CD. A videotape and demonstration of the USA developed VR simulations
will also be provided.

2.19 Anti-Roll System

The contractor shall design and install a passive anti-roll system on
each of the SRB Recovery Ships while they are in dry dock for other
projects and routine maintenance. The design shall conform to that
contemplated by PRCBD No. S061696R1 and that contained in Paragraph 2.1
of CPA MSFC --071, dated July 27, 2001.

2.20 Oxygen Enriched Air (NITROX)

The contractor shall procure and install a commercial, off-the-shelf
NITROX membrane filter system for use with existing SCUBA compressors
aboard each of the two recovery ships. The contractor shall procure 46
SCUBA regulators qualified for use with NITROX and 25 NITROX compatible
dive computers as stated in Paragraph 2.1 of CPA MSFC-M078 dated March
13, 2002.

2.21 Task Analysis Tool Development

The Contractor shall provide the following:

1\. Participate in the development of a PFMEA/Task Analysis Tool.

2\. Perform qualification/acceptance testing to validate the NASA
provided prototype tool through comparing the results of a PFMEA of a
Shuttle Processing activity performed manually against the same task
analyzed utilizing the tool.

3\. Assess the usability of the software tool for its intended
application and document USA feedback, as well as suggested enhancements
to the tool.

4\. Provide a summary report to NASA Principle Investigator and IES
Program that includes the task analysis recommendations, task analysis
prototype improvement recommendations, usability testing results,
lessons learned, and technology barriers/challenges to performing task
analysis.

2.22 New Hypalon Paint Formulation Qualifications (IES)

USA shall qualify a replacement Hypalon coating which is environmentally
compliant and offers improved personnel safety via elimination of
Perchloroethylene. The following products are part of this activity:

1\. Qualification Plan

2\. Qualification Testing

3\. Qualification Report

4\. Certificate of Qualification

5\. ECP/Material Implementation

2.23 ABACS Supportability Upgrade , Formulation Phase

In accordance with the Statement of Work contained in Exhibit A of CPA
MSFC M-084, the contractor shall take all actions necessary to complete
the Formulation Phase and obtaining cost estimates in preparation for an
authorization to proceed into the implementation phase of this project.
The primary objective of the ABACS Supportability Upgrade is to provide
an updated checkout system that eliminates obsolete and problematic
hardware with a goal of assuring, with appropriate follow on
maintenance, and logistical support, SRB capability to support the SSP
flight manifest through the year 2020.

2.24 IEA Supportability Upgrade , Formulation Phase

In accordance with the Statement of Work contained in Exhibit A of CPA
MSFC M-085, the contractor shall take all actions necessary to complete
the Formulation Phase and obtaining cost estimates in preparation for an
authorization to proceed into the implementation phase of this project.
The primary objective of the IEA Supportability Upgrade is to reduce
operational risk. The primary means to accomplish this reduction is by
improving IEA distributor and signal conditioner harness assembly
supportability by replacing existing harnesses with new harnesses of
similar design.

2.25 Supportability Infrastructure Upgrade Studies

2.25.1 Refurbish FSS & RSS, Pads A & B

The contractor shall evaluate the condition of the columns, diagonal
bracing and main beams for all Fixed Service Structure (FSS) levels of
Pads A & B. This study will also evaluate the truss members of the
Remote Service Structure (RSS) as well as the main structure elements on
the 107, 115, 135, and 207 foot levels. It will evaluate the External
Tank -- Internal Tank, Orbiter Weather Protection, Emergency
embarkation, and hammer head crane areas. The evaluations will outline
the requirements for the design and make recommendations based on
ensuring the structure will support the program to 2020.

2.25.2 Upgrade Orbiter Weather Protection for --Y and +Y Sides, Pads A &
B

The contractor shall review the existing Orbiter Weather Protection for
Pads A & B for design flaws, manufacturing flaws, potential upgrades,
and cost effective program life cycle goals. Establish
design/implementation options to eliminate near term reported problems
and long-term survivability goals. This study will assume a program life
cycle of 20 more years to CY 2022. The study will be broken down into 3
options for each category of reported faults.

2.25.3 Rebuild White Room/Orbiter Access Arms, Pads A & B

The contractor shall perform a study and produce a preliminary
engineering report to refurbish/replace the Orbiter Access Arms (OAAs)
Environmental Chamber's structures for Pads A & B. During the study the
launch acoustical loads will be reviewed. The acoustical loads will be
from the pressure and strain gage data recorded during launches. Once
the data is reviewed it will be used as input into Finite Element Models
(FEMs). The FEMs will be used to write the design requirements for the
refurbishment/replacement of the OAA Environmental Chamber structure.
The interior and exterior envelopes including all interfaces, cabinets
and equipment shall remain the same.

2.26 CPA \# MSFC-080 - IEA Supportability Upgrade, Implementation Phase

In accordance with the Statement of Work contained in Exhibit A of CPA
MSFC-080, the Contractor shall perform all work, either directly or
through subcontract pursuant to the requirements referenced in the SRB
Integrated Electronics Assembly (IEA) Upgrade Statement of Work (SOW).
Work performed by NASA that supports Project objectives and completion
of tasks described in the SOW shall be documented and agreed to by NASA
and USA.

Task Summary:

1\) Pursue minor IEA Harness Assembly design changes as outlined in
paragraphs 2 and 3. No other design changes are included in the scope of
this upgrade project.

> 2\) Conduct a study to determine the feasibility of replacing 26-gauge
> wire with 24-gauge wire in the distributor harnesses. If the
> Contractor and NASA approve the results of the study, the Contractor
> will implement the wire change in production chassis assemblies.
>
> 3\) Redesign the MPU #2 wiring in the Aft IEA harnesses to remove
> unnecessary Deutsch block connections. Implement the change in all
> production chassis assemblies.
>
> 4\) Conduct a qualification program for the IEA.
>
> 5\) Produce harness sets for 56 IEAs (30 Aft and 26 Fwd).
>
> 6\) Retrofit two (2) Qualification IEAs (1 Aft, 1 Fwd) and 51 flight
> IEAs (27 Aft, 24 Fwd) with new harness sets.

7\) During retrofit activities, insulate IEA tie bars per approved
engineering.

2.27 Advanced Health Management System (AHMS) Upgrades

1.  AHMS Phase I

The Contractor shall perform the Implementation Phase activities of AHMS
Phase 1 which includes providing systems integration support for the
certification and integration of the AHMS Space Shuttle Main Engine
Controller (SSMEC) into the shuttle flight system, and modification of
ground facilities for checkout and verification of the SSMEC in support
of a Design Certification Review (DCR).

2.  AHMS Phase 2A

The Contractor shall support the Formulation Phase activities of AHMS
Phase 2A which are required to mature the project requirements to
support a NASA decision to implement Phase 2 of the project. These
activities include, vehicle integration impact analysis and review of
the initial Health Management Computer (HMC) designs, system impact
analysis and review of the initial development of an Optical Plume
Anomaly Detection (OPAD) Flight Experiment, review and additional input
into the definition of AHMS Phase 2B system requirements and the
development and negotiation of a Decision Package (DP) for AHMS Phase
2B.

3.  AHMS Phase 2B.1

The Contractor shall perform AHMS Phase 2B.1 which includes a
preparation and negotiation of a Decision Package (DP) for Phase 2B.1,
the development of a preliminary design for an Orbiter Mod Kit for
installation of the Health Management Computer (HMC) into the aft
compartment and completion of a Orbiter Mod Kit Preliminary Design
Review (PDR).

**ATTACHMENT J-1-A**

**SPACE FLIGHT OPERATIONS CONTRACT**

**STATEMENT OF WORK**

**EXHIBITS**

> 1.1.1.1 Contingency Plans
>
> 1.4.9 Flight Crew Equipment Groups
>
> 1.5.5.1-B SPDMS/IWCS Applications
>
> 1.6.4 Flight Operations Systems

**ATTACHMENT J-1-A**

**EXHIBIT 1.1.1.1**

**Contingency Plans**

  ------------------------------ ----------------------------------------
  NMI 1040.3C                    Emergency Preparedness Program

  NMI 1040.4A                    Headquarters Contingency Plan

  NMI 1382.3                     Release of Mishap Investigation Reports

  NMI 1382.4                     Release of Information Concerning
                                 Mishaps and Casualties

  NMI 8821.1                     Mishap Reporting and Investigation

  NHB 1700.1 (V1-B)              NASA Safety Policy and Requirements
                                 Documents

  NHB 1700.1 (V2)                Guidelines for Mishap Investigating

  OSF SFO CAP                    Space Flight Operations Contingency
                                 Action Plan

  NSTS Directive 96B             Shuttle Contingency & Operations

  NSTS 07700, Vol. 8, App. D     Space Shuttle Operations: Mission
                                 Management Team

  NSTS 07700, Vol. 8, App. G     Space Shuttle Operations: Shuttle
                                 Ingress Landing and Post-landing
                                 Operations Responsibility

  NSTS 07700, Vol. 8, App. H     Space Shuttle Operations: Shuttle
                                 Contingency Planning and Operations

  NSTS 07700, Vol. 8, App. I     Space Shuttle Operations: Orbiter
                                 Prelaunch and Landing Contingency/Rescue
                                 Operations Responsibilities

  NSTS 07700, Vol. 8, App. R     Space Shuttle Operations: Contingency
                                 Landing Response Plan

  NSTS 07700, Vol. 8, App. S     Space Shuttle Operations: Transoceanic
                                 Abort Landing Orbiter Recovery Plan

  NSTS 08218                     NSTS Program Intercenter Photographic
                                 and Television Analysis Contingency
                                 Action Plan

                                 STS Security Classification Guide

  STDN No. 508.21                NSTS Emergency MCC Interface Procedures

                                 STS Public Affairs Contingency Plan

  JSC 14273                      Space Shuttle Program Contingency Plan
                                 for JSC (Rev B)

  JSC 23275                      FCOD-Family Support Document

  JSC 23616                      FCOD- Space Shuttle Contingency Action
                                 Plan

                                 MER Contingency Response Procedure

  534-CAP-EMCC                   SSP Emergency MCC Activation's &
                                 Operations Procedures

  SSC-PTO-001                    Stennis Space Center Contingency Action
                                 Plan

  MSFC-SSCP-5-77                 Space Shuttle Contingency Action Plan

  K-STSM-09.3.02                 KSC NSTS Data Impoundment and Handling
                                 Plan

  K-STSM-09.3.1                  Flight and Ground Crew Rescue

  K-RQ-0001.2A                   NSTS Contingency Action Plan for Kennedy
                                 Space Center

  K-RQ-0001.2B                   Space Shuttle Program Contingency Plan
                                 for KSC

  K-RQ-0001.21                   KSC Mishap Investigation Board and
                                 Committee Supporting Personnel

  K-RQ-0004.3                    KSC Index of Contingency Related
                                 Documents

  K-SF-0005.7                    National Resource Protection Plan for
                                 KSC

  K-STM-9.3.02                   NSTS Data Impoundment & Handling Plan

  K-STM-09.3.1                   KSC Operations Plan, Flight Crew Rescue

  K-STM-12.4                     KSC Off-site Transportation Plan/DFRG

  KVT-PL-0004                    Operations Plan for the STS Emergency
                                 Egress System

  KVT-PL-0008                    Operations Plan for Post-Cryogenic
                                 Loading Pad Access

  KVT-PL-0014                    KSC Off-site Operations Plan

  KVT-PL-0015                    Convoy Operations Plan

  KVT-PL-0016                    STS Operations Plan, Shuttle Emergency
                                 OTV

  KVT-PL-0021                    NSTS Salvage Plan

  KHB 1711.1C                    Reporting and Investigation of Mishaps

  KHB 1040.1                     KSC Comprehensive Emergency Preparedness
                                 Plan

  KPH-HB-1040.1                  PH Emergency Preparedness/Hurricane Plan

  OMI S0003                      ET Demate Operations

  OMI S0007, Volume 5            SSV Launch Countdown Contingency

  OMI S0030                      Orbiter Demate from SRBs

  OMI S0038                      SSV Preparations for Rollback to VAB

  OMI B5303                      SRB Destacking Operations

  EPD S9904                      OPF Emergency Procedure Document

  EPD S9905                      HMF Emergency Procedure Document

  EPD S9906                      EAFB/DFRC Shuttle Landing Site Emergency
                                 Procedure Document

  EPD S9907                      Non-CONUS CLS Emergency Procedure
                                 Document

  EPD S9908                      Launch Pad Emergency Procedures Document

  EPD S9909                      VAB Emergency Procedures Document

  EPD S9910                      Emergency Preparedness Document for the
                                 O&C

  EPD S9911                      Emergency Preparedness Document for the
                                 VPF

  EPD S9925                      Shuttle Back-up Landing site - WSSH,
                                 N.M. Emergency Procedure Document

  EPD S9926                      Hangar AF Emergency Procedure Document

  EPD S9929                      RPSF Emergency Procedure Document

  EPD A9902                      SLF Emergency Procedure Document

  EPD A9903                      LCC Emergency Procedure Document

                                 DOD Manager's Contingency Review Plan

                                 DOD Manager's STS Contingency Support
                                 Procedures Document

  DOD 5200.1R                    Information Security Program Regulations

  ESMC Operations Directive (OD) Search & Salvage
  No. 001                        

  ESMC Operations Directive (OD) ESMC Contingency Support
  No. 004                        

                                 
  ------------------------------ ----------------------------------------

**ATTACHMENT J-1-A**

**EXHIBIT 1.4.9**

**FLIGHT EQUIPMENT GROUPS**

The typical groups of flight crew equipment used for flight and training
are as follows.

1\. All EMU softgoods/hardware, tools standard and unique, Tethers,
restraints, mobility aids, side wires, and winches, etc.

2\. All camera equipment including television, camcorders, 35mm, 70mm,
Hasselblad, Arriflex, electronic still camera, and vision enhancement
equipment, etc.

3\. Food (flight and ground) \[pre and post flight\]

4\. Clothing

5\. Galley system

6\. Auxiliary equipment - calculators, binoculars, portable computer,
battery chargers, etc.

7\. Operational Bioinstrumentation system

8\. Air sample equipment

9\. Film - many types

10\. Orbiter AFT fuselage gas sampler (OAFGS)

11\. Batteries - Li BCX, EMU, NICAD, Alkaline, etc.

12\. Crew Escape equipment - except parachute package (furnished GFE)

13\. Stowage provisions (cushions, etc.)

14\. Thermal electronic cooling equipment includes personal suit
ventilation equipment.

15\. Shuttle Emergency Breathing System (SEBS)

16\. Quick Don Mask Assembly

17\. Microbial check valves

18\. Adhesive - Backed hook and loop fastener provisioning

19\. Consumables

\- Wet trash linens

\- Wet & dry wipes

\- Toilet tissue

\- Gloves

\- Wet trash bags

\- etc.

20\. Docking Hardware (Lidars)

21\. Crew Entertainment Hardware - CD and cassette players, etc.

22\. Grapple fixture processing

23\. Remote Manipulation System (KSC processing only)

**ATTACHMENT J-1-A**

EXHIBIT: 1.5.5.1-B

SPDMS/IWCS APPLICATIONS

+------------------------+---------------------------------------------+
| **BUSINESS ELEMENT**   | **APPLICATIONS**                            |
+------------------------+---------------------------------------------+
| Flow Requirements      | IDMRD - Intermediate & Depot-level          |
| Management             | maintenance Requirements system             |
|                        |                                             |
|                        | OMRSD - OMRS Documentation                  |
|                        |                                             |
|                        | OMRS/CP - OMRS Change Processing            |
|                        |                                             |
|                        | OMRS/FP - OMRS Flow Planning                |
+------------------------+---------------------------------------------+
| Support Requirements   | ASRS - Automated Support Requirements       |
| Management             | System                                      |
+------------------------+---------------------------------------------+
| Flow Planning          | OMRS/RA - OMRS RCN Assessment               |
|                        |                                             |
|                        | CAPSS - Computer Aided Planning and         |
|                        | Scheduling System                           |
+------------------------+---------------------------------------------+
|                        | GPSS - Ground Processing Scheduling System  |
+------------------------+---------------------------------------------+
| Work Instruction       | OMID - Operations and Maintenance           |
| Development            | Instruction Development                     |
|                        |                                             |
|                        | PWE 1.2 - Paperless Work Environment        |
|                        |                                             |
|                        | PWE 2.1 - Paperless Work Environment        |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Work Instruction       | DILS - Deviation Index Logging System       |
| Management             |                                             |
|                        | OMID - Operations and Maintenance           |
|                        | Instruction Development                     |
|                        |                                             |
|                        | OMIE - Operations and Maintenance           |
|                        | Instruction Engineering                     |
|                        |                                             |
|                        | OMIT - Operations and Maintenance           |
|                        | Instruction Tracking                        |
|                        |                                             |
|                        | PWE/CM - Paperless Work Environment         |
|                        | Configuration Management                    |
|                        |                                             |
|                        | WILMA - Wire List Maintenance System        |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Task Scheduling        | GPSS - Ground Processing Scheduling System  |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Task Status and        | IOS - Integrated Operations Systems         |
| Tracking               |                                             |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Work Package Build     | OMID - Operations and Maintenance           |
|                        | Instruction Development                     |
|                        |                                             |
|                        | PWE - Paperless Work Environment            |
+------------------------+---------------------------------------------+
| Work Package           | AMDCS - Automated Management Document       |
| Management             | Control System                              |
|                        |                                             |
|                        | DACS - Document Accountability and Control  |
|                        | System                                      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Work Package Execution | SFC/DC - Shop Floor Control/ Data           |
|                        | Collection                                  |
|                        |                                             |
|                        | SFC/PAR - Shop Floor Control/ Performance   |
|                        | Analysis Reporting                          |
|                        |                                             |
|                        | TSG - Tile Step and Gap                     |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Parts & Materials      | ALRUTS - Automated Line Replaceable Unit    |
| Management             | Tracking System                             |
|                        |                                             |
|                        | AOCS - Automated Ordnance Control System    |
|                        |                                             |
|                        | MSS - Materials Support System              |
|                        |                                             |
|                        | IVD - Item Validation Database              |
|                        |                                             |
|                        | BARS interface - Baseline Accounting and    |
|                        | Reporting System                            |
|                        |                                             |
|                        | KIMS interface - Kennedy Inventory          |
|                        | Management System                           |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Support Equipment      | GRMRS - Global Repetitive Maintenance       |
| Management             | Recall System                               |
|                        |                                             |
|                        | SFC/RT - Shop Floor Control/ Resource       |
|                        | Tracking                                    |
|                        |                                             |
|                        | CMDS interface - Configuration Management   |
|                        | Data System                                 |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Non-conformance        | NCDI - Non-Conformance Data Interface       |
| Management             |                                             |
|                        | PRACA - Problem Reporting and Corrective    |
|                        | Action                                      |
|                        |                                             |
|                        | IMIC interface - Integrated Management      |
|                        | Information Computer interface              |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Workforce Training     | CBT - Computer-Based Training               |
| Management             |                                             |
|                        | OICW - On-line Interactive Courseware       |
|                        |                                             |
|                        | TTSS - Tech Training Scheduling System      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Business Process       | CIP - Continuous improvement Process        |
| Re-Engineering         |                                             |
|                        | MAP - Management Awareness Process          |
+------------------------+---------------------------------------------+

**ATTACHMENT J-1-A**

**EXHIBIT 1.6.4**

**Flight Operations Systems**

**SYSTEM MAINTENANCE HARDWARE SOFTWARE MGMT & INGR &**

**AND OPS SUSTAINING SUSTAINING INTGR INSTALLATION**

Mission Control

Center (MCC) **X X X X X**

1.6.4.1

Integrated Training

Facility (ITF) **X X X X X**

1.6.4.2

Integrated Planning

System (IPS) **X X X X X**

1.6.4.3

Software Production

Facility (SPF) **X X X X X**

1.6.4.4

Mock-up &

Trainer Facilities **X X X X X**

1.6.4.7

Operations Support **X X X X X**

Systems (OSS)

1.6.4.9