**SCIENCE, ENGINEERING, ANALYSIS, AND TEST (SEAT)**

**CONTRACT**

**CONSOLIDATED**

**STATEMENT OF WORK (SOW)**

**Table of Contents**

**Top Tier**

**INTRODUCTION** 1

**STATEMENT OF WORK COMPLIANCE MATRIX** 7

**PART I - AREAS OF SUPPORT** **Part I - 1**

**SECTION A: ENGINEERING** **Section A-1**

1\. SYSTEMS ENGINEERING 1-1

> 2\. BIOMEDICAL HARDWARE DEVELOPMENT AND ENGINEERING 2-1
>
> 3\. CREW AND THERMAL SYSTEMS 3-1
>
> 4\. AEROSCIENCE AND FLIGHT MECHANICS 4-1
>
> 5\. MANUFACTURING, MATERIALS, AND PROCESS TECHNOLOGY 5-1
>
> 6\. ENERGY SYSTEMS 6-1
>
> 7\. AUTOMATION, ROBOTICS, AND SIMULATION 7-1
>
> 8\. STRUCTURES AND MECHANICS 8-1
>
> 9\. AVIONICS SYSTEMS 9-1
>
> 10\. ADVANCED DEVELOPMENT 10-1

**SECTION B: SPACE AND LIFE SCIENCES Section B-1**

> 11\. MEDICAL AND MISSION SCIENCE 11-1
>
> 12\. SCIENCE PAYLOADS MANAGEMENT 12-1
>
> 13\. EARTH SCIENCE AND SOLAR SYSTEM EXPLORATION 13-1

**SECTION C: SPACE SHUTTLE PROGRAM Section C-1**

> 14\. SPACE SHUTTLE VEHICLE ENGINEERING 14-1

**SECTION D: OTHER ENGINEERING & SCIENCE AREAS Section D-1**

> 15\. OTHER ENGINEERING & SCIENCE AREAS 15-1

**PART II - PERFORMANCE BASED STATEMENT OF WORK** **Part II -- 1**

0\. INTRODUCTION C-II-1

1\. TEST, FACILITY, MAINTENANCE, AND OPERATIONS C-II-1

2\. ENGINEERING AND SCIENCE ANALYSIS C-II-9

3\. OTHER ENGINEERING & SCIENCE AREAS C-II-11

**PART III -- PERFORMANCE BASED STATEMENT OF WORK -- REDISTRIBUTED Part
III-1**

0\. INTRODUCTION C-III-1

1\. CORE COMPUTER SYSTEMS (CCS) (MHEPEVCVX) C-III-1

**Table of Contents**

**Detail**

**INTRODUCTION** 1

**STATEMENT OF WORK COMPLIANCE MATRIX** 7

**PART I - AREAS OF SUPPORT** **Part I - 1**

**SECTION A: ENGINEERING Section A-1**

> 1\. SYSTEMS ENGINEERING 1-1
>
> 1.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 1-1
>
> 1.1.1 Program Management Support 1-1
>
> 1.1.2 Research and Development Support 1-4
>
> 1.1.3 Engineering, Scientific, and Analytical Tools 1-6
>
> 1.2 LABORATORY/FACILITY SUPPORT SERVICES - N/A 1-6
>
> 1.3 MAINTENANCE AND OPERATIONS SUPPORT 1-6
>
> 1.4 LOGISTICS SUPPORT 1-7
>
> 2\. BIOMEDICAL HARDWARE DEVELOPMENT AND ENGINEERING 2-1
>
> 2.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 2-1
>
> 2.1.1 Program Management Support 2-1
>
> 2.1.2 Research and Development 2-5
>
> 2.1.3 Engineering, Scientific, and Analytical Tools 2-12
>
> 2.1.4 Studies and Assessments 2-15
>
> 2.2 LABORATORY/FACILITY SUPPORT SERVICES 2-19
>
> 2.2.1 General Support Services 2-19
>
> 2.2.2 Laboratories 2-19
>
> 2.2.3 Facility/Ground, Systems Engineering, and Operations 2-19
>
> 2.3 MAINTENANCE AND OPERATIONS SUPPORT 2-22
>
> 2.4 LOGISTICS SUPPORT 2-23
>
> 3\. CREW AND THERMAL SYSTEMS 3-1
>
> 3.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 3-1
>
> 3.1.1 Program Management Support 3-1
>
> 3.1.2 Research and Development Support 3-3
>
> 3.1.3 Engineering, Scientific, and Analytical Tools 3-4
>
> 3.1.4 Studies and Assessments 3-5
>
> 3.2 LABORATORY/FACILITY SUPPORT SERVICES 3-6
>
> 3.2.1 General Support Services 3-6
>
> 3.2.2 Federal Information Processing Resources (FIPR) Support 3-10
>
> 3.2.3 Special Purpose Laboratories 3-11
>
> 3.2.4 Technology/Discipline Laboratories 3-12
>
> 3.2.5 Chemistry Laboratories 3-14
>
> 3.2.6 Bond Room Facility 3-15
>
> 3.3 MAINTENANCE AND OPERATIONS SUPPORT 3-15
>
> 3.4 LOGISTICS SUPPORT 3-16
>
> 4\. AEROSCIENCE AND FLIGHT MECHANICS 4-1
>
> 4.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 4-1
>
> 4.1.1 Program Management Support 4-1
>
> 4.1.2 Research and Development Support 4-4
>
> 4.1.3 Engineering, Scientific, and Analytical Tools 4-4
>
> 4.1.4 Studies and Assessments 4-6
>
> 4.2 LABORATORY/FACILITY SUPPORT SERVICES 4-9
>
> 4.2.1 General Support Services 4-9
>
> 4.2.2 Federal Information Processing Resources (FIPR) Support 4-9
>
> 4.3 MAINTENANCE AND OPERATIONS SUPPORT 4-10
>
> 4.4 LOGISTICS SUPPORT 4-11
>
> 5\. MANUFACTURING, MATERIALS, AND PROCESS TECHNOLOGY 5-1
>
> 5.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 5-1
>
> 5.1.1 Program Management Support 5-1
>
> 5.1.2 Research and Development Support 5-1
>
> 5.1.3 Engineering, Scientific, and Analytical Tools 5-1
>
> 5.1.4 Engineering Studies and Assessments 5-3
>
> 5.2 ENGINEERING STANDARDS AND PROCESSES 5-5
>
> 5.3 LABORATORY/FACILITY SUPPORT SERVICES 5-6
>
> 5.3.1 General Support Services 5-6
>
> 5.3.2 Federal Information Processing Resources (FIPR) Support 5-7
>
> 5.3.3 Materials Technology Laboratory 5-8
>
> 5.3.4 Mechanical Systems Laboratory 5-8
>
> 5.4 MAINTENANCE AND OPERATIONS SUPPORT 5-9
>
> 5.5 LOGISTICS SUPPORT 5-9
>
> 6\. ENERGY SYSTEMS 6-1
>
> 6.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 6-1
>
> 6.1.1 Program Management Support 6-1
>
> 6.2 LABORATORY/FACILITY SUPPORT SERVICES 6-2
>
> 6.2.1 General Support Services 6-2
>
> 6.2.2 Electrical Power Systems Laboratory (EPSL) 6-2
>
> 6.2.3 Energy Systems Test Area (ESTA) 6-3
>
> 6.2.4 Energy Systems Technical Discipline Facilities 6-4
>
> 6.2.5 Federal Information Processing Resources (FIPR) Support 6-5
>
> 6.3 MAINTENANCE AND OPERATIONS SUPPORT 6-5
>
> 6.4 LOGISTICS SUPPORT 6-6
>
> 7\. AUTOMATION, ROBOTICS, AND SIMULATION 7-1
>
> 7.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 7-1
>
> 7.1.1 Program Management Support 7-1
>
> 7.1.2 Research and Development Support 7-4
>
> 7.1.3 Engineering, scientific, and Analytical Tools 7-6
>
> 7.2 LABORATORY/FACILITY SUPPORT SERVICES 7-8
>
> 7.2.1 General Support Services 7-8
>
> 7.2.2 SES General Support Services 7-9
>
> 7.2.3 Building Support Services 7-9
>
> 7.2.4 Federal information Processing Resources /FIPR Support 7-10
>
> 7.2.5 The Automation, Robotics, and Simulation Laboratories 7-11
>
> 7.2.6 Bond Room Facility 7-12
>
> 7.2.7 Facility Development and/or Upgrade 7-12
>
> 7.3 MAINTENANCE AND OPERATIONS SUPPORT 7-13
>
> 7.4 LOGISTICS SUPPORT 7-14
>
> 8\. STRUCTURES AND MECHANICS 8-1
>
> 8.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 8-1
>
> 8.1.1 Program Management Support 8-1
>
> 8.1.2 Research and Development Support 8-2
>
> 8.1.3 Engineering, Scientific, and Analytical Tools 8-2
>
> 8.1.4 Engineering Studies and Assessments 8-3
>
> 8.2 LABORATORY/FACILITY SUPPORT SERVICES 8-5
>
> 8.2.1 General Support Services 8-5
>
> 8.2.2 Federal Information Processing Resources (FIPR) Support 8-6
>
> 8.2.3 Atmospheric Re-entry Materials and Structures Evaluation
> (ARMSEF)\
> and Radiant Heating Test Facility (RHTF) 8-7
>
> 8.2.4 Structures Test Laboratory (STL) 8-8
>
> 8.2.5 Vibration and Acoustic Test Facility (VATF) 8-8
>
> 8.3 MAINTENANCE AND OPERATIONS SUPPORT 8-8
>
> 8.4 LOGISTICS SUPPORT 8-9
>
> 9\. AVIONICS SYSTEMS 9-1
>
> 9.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 9-1
>
> 9.1.1 Program Management Support 9-1
>
> 9.1.2 Research and Development Support 9-10
>
> 9.1.3 Engineering. Scientific. and Analytical Tools 9-11
>
> 9.1.4 Studies and Assessments 9-12
>
> 9.2 LABORATORY/FACILITY SUPPORT SERVICES 9-13
>
> 9.2.1 General Support Services 9-13
>
> 9.2.2 Federal Information Processing Resources (FIPR) Support 9-14
>
> 9.2.3 Communications Processing Laboratories 9-17
>
> 9.2.4 Tracking Techniques Laboratories 9-18
>
> 9.2.5 Electronic Systems Test Laboratory (ESTL) 9-19
>
> 9.2.6 Antenna Range and Anechoic Chamber 9-20
>
> 9.2.7 Microwave Design and Integrated Circuit Laboratories 9-21
>
> 9.2.8 High Temperature Superconductivity (HTSC) Laboratory 9-21
>
> 9.2.9 Electromagnetic Compatibility (EMC) and\
> Electromagnetic Interference (EMI) Test Laboratory 9-21
>
> 9.2.10 Communications System Development Laboratory 9-21
>
> 9.2.11 Communications Software Development Laboratory 9-22
>
> 9.2.12 Communication Systems Simulation Laboratory 9-22
>
> 9.2.13 Government Furnished Equipment (GFE) Flight Hardware
> Maintenance Facility 9-22
>
> 9.2.14 Bond Room Facility 9-23
>
> 9.2.15 Inertial Systems and Inertial Components Laboratories 9-23
>
> 9.2.16 Electro-Optics Laboratory (EOL)/Tracking Laboratory (TL) 9-24
>
> 9.2.17 Interactive Analysis Laboratory 9-24
>
> 9.2.18 Technology Insertion Laboratory (TIL) 9-25
>
> 9.2.19 JSC Avionics Engineering Laboratory (JAEL) 9-25
>
> 9.2.20 Flight Data Recorder Laboratory 9-26
>
> 9.2.21 Instrumentation Laboratory 9-26
>
> 9.2.22 Portable Computer Laboratory 9-27
>
> 9.2.23 Display and Control Laboratory 9-27
>
> 9.2.24 Real-time Systems Engineering Laboratory (RSEL) 9-27
>
> 9.2.25 Software Development Facility 9-28
>
> 9.2.26 Avionics Development Facility (ADF) 9-28
>
> 9.2.27 Central Software Facility/Central Avionics Facility 9-28
>
> 9.2.28 Technical Library 9-30
>
> 9.2.29 Building Facilities Design and Integration 9-30
>
> 9.3 MAINTENANCE AND OPERATIONS SUPPORT 9-31
>
> 9.4 LOGISTICS SUPPORT 9-31
>
> 10\. ADVANCED DEVELOPMENT 10-1
>
> 10.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 10-1
>
> 10.1.1 Program Management Support 10-1
>
> 10.1.2 Research and Development Support 10-3
>
> 10.1.3 Other R&D Support 10-6
>
> 10.2 LABORATORY/FACILITY SUPPORT SERVICES - N/A 10-6
>
> 10.3 MAINTENANCE AND OPERATIONS SUPPORT 10-6
>
> 10.4 LOGISTICS SUPPORT 10-7

**SECTION B: SPACE AND LIFE SCIENCES Section B-1**

> 11\. MEDICAL AND MISSION SCIENCE 11-1
>
> 11.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 11-1
>
> 11.1.1 Program Management Support 11-1
>
> 11.1.2 Studies and Assessments 11-1
>
> 11.2 LABORATORY/FACILITY SUPPORT SERVICES 11-2
>
> 11.2.1 General Support Services 11-2
>
> 11.3 MAINTENANCE AND OPERATION SUPPORT 11-2
>
> 11.4 LOGISTICS SUPPORT 11-3
>
> 12\. SCIENCE PAYLOADS MANAGEMENT 12-1
>
> 12.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 12-1
>
> 12.1.1 Program Management Support 12-1
>
> 12.1.2 Engineering, Scientific, and Analytical Tools 12-10
>
> 12.1.3 Studies and Assessments 12-19
>
> 12.1.4 Research and Development Support 12-40
>
> 12.2 LABORATORY/FACILITY SUPPORT SERVICES 12-48
>
> 12.2.1 General Support Services 12-48
>
> 12.2.2 Federal Information Processing Resources Support 12-49
>
> 12.2.3 Special Purpose Laboratories 12-49
>
> 12.2.4 Facility/Ground, Systems Engineering, and Operations 12-50
>
> 12.3 MAINTENANCE AND OPERATIONS SUPPORT 12-53
>
> 12.4 LOGISTICS SUPPORT 12-54
>
> 13\. EARTH SCIENCE AND SOLAR SYSTEM EXPLORATION 13-1
>
> 13.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 13-1
>
> 13.1.1 Program Management Support 13-1
>
> 13.1.2 Research and Development Summary 13-1
>
> 13.1.3 Engineering, Scientific, and Analytical Tools 13-3
>
> 13.1.4 Studies and Assessments 13-3
>
> 13.2 LABORATORY/FAClLlTIES SUPPORT SERVICES 13-3
>
> 13.2.1 General Support Services 13-3
>
> 13.2.2 Federal Information Processing Resources (FIPR) Support 13-4
>
> 13.2.3 Planetary Materials Curatorial Laboratories 13-4
>
> 13.2.4 Geoscience and Space Science Instrumental Analysis Laboratories
> 13-5
>
> 13.2.5 Specialized Experimental Laboratories 13-6
>
> 13.3 MAINTENANCE AND OPERATIONS SUPPORT 13-8
>
> 13.4 LOGISTICS SUPPORT 13-9

**SECTION C: SPACE SHUTTLE PROGRAM Section C-1**

> 14\. SPACE SHUTTLE VEHICLE ENGINEERING 14-1
>
> 14.1 REPRESENTATIVE TASKS 14-1
>
> 14.1.1 Computer Systems Support 14-1
>
> 14.1.2 Software and Database Maintenance 14-1
>
> 14.1.3 Photographic and Program Requirements 14-2
>
> 14.1.4 Information Management 14-2
>
> 14.1.5 MER Hardware/Software Operations 14-2
>
> 14.1.6 ODRC Rehost Development 14-2
>
> 14.1.7 MER Engineering Data Display System Upgrade 14-2
>
> 14.1.8 Video Digital Analysis Laboratory (VDAS) 14-3
>
> 14.2 MAINTENANCE AND OPERATIONS SUPPORT 14-3
>
> 14.3 LOGISTICS SUPPORT 14-4

**SECTION D: OTHER ENGINEERING & SCIENCE AREAS Section D-1**

> 15\. OTHER ENGINEERING & SCIENCE AREAS 15-1
>
> 15.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES 15-1
>
> 15.1.1 Engineering, Scientific, and Analytical Tools 15-1
>
> 15.1.2 Research and Development Support 15-1
>
> 15.1.3 Subsystem Management Support System (SMSS) and Orbiter Data
> Reduction Complex (ODRC) Interface System 15-3
>
> 15.1.4 Visual Communication Lab Support 15-3
>
> 15.1.5 Maintenance of Computer Equipment and Related Ground Support
> Equipment 15-3
>
> 15.2 LABORATORY/FACILITY SUPPORT SERVICES 15-4
>
> 15.2.1 Federal Information Processing Resources Support 15-4
>
> 15.2.2 Materials Technology Laboratory C-I-15-4
>
> 15.3 MAINTENANCE AND OPERATIONS SUPPORT C-I-15-5
>
> 15.4 LOGISTICS SUPPORT C-I-15-6
>
> 15.5 SAFETY, RELIABILITY, MAINTAINABILITY, AND QUALITY ASSURANCE\
> (ARM&QA) C-I-15-6
>
> 15.5.1 SRM&QA Management C-I-15-6
>
> 15.1.2 Safety and Mission Assurance (S&MA) C-I-15-6
>
> 15.1.3 S&MA Certification C-I-15-6
>
> 15.5.4 Safety C-I-15-6
>
> 15.5.5 Safety Requirements C-I-15-7
>
> 15.5.6 Safety Reviews C-I-15-7
>
> 15.5.7 Evaluation of Test Activity C-I-15-7
>
> 15.5.8 Review of Flight Hardware Failures C-I-15-8
>
> 15.5.9 Reliability and Maintainability C-I-15-8
>
> 15.5.10 Reliability Design Criteria C-I-15-8
>
> 15.5.11 Flight Hardware Failure Modes and Effects Analyses/Critical
> Items List (FMEA/CIL) C-I-15-8
>
> 15.5.12 Reliability and Analysis C-I-15-8
>
> 15.5.13 Electronic, Electrical, and Electromechanical (EEE) Parts
> Control Plan C-I-15-8
>
> 15.5.14 Alert System C-I-15-9
>
> 15.5.15 Limited-Life Items C-I-15-9
>
> 15.5.16 Maintainability C-I-15-9
>
> 15.5.17 Maintainability Allocations and Predictions C-I-15-9
>
> 15.5.18 Maintainability Qualitative Assessments C-I-15-9
>
> 15.5.19 Failure Detection, Isolation, and Recovery Assessment C-I-15-9
>
> 15.5.20 Problem Reporting and Corrective Action C-I-15-10
>
> 15.5.21 Training and Certification (T&C) C-I-15-10
>
> 15.5.22 Quality/Product Assurance C-I-15-10
>
> 15.5.23 Applicable Documents List for SR&QA C-I-15-13

PART II -- PERFORMCE BASED STATEMENT OF WORK (Detail on C-II-i and
C-II-I) C-II-1

0\. INTRODUCTION C-II-1

1\. TEST, FACILITY, MAINTENANCE, AND OPERATIONS C-II-1

2\. ENGINEERING AND SCIENCE ANALYSIS C-II-9

3\. OTHER ENGINEERING & SCIENCE AREAS C-II-11

**PART III -- PERFORMANCE BASED STATEMENT OF WORK -- REDISTRIBUTED
C-III-1**

0\. INTRODUCTION C-III-1

1\. CORE COMPUTER SYSTEMS (CCS) (MHEPEVCVX) C-III-1

INTRODUCTION

\*\*\*From Schedule A, 13.0, Engineering and Scientific Support

This SOW is structured to reflect engineering and science work in
support of the Johnson Space Center organization as of the effective
date of this contract. Any subsequent changes in the JSC organizations
being supported by this contract, such as the assignment of work to new
divisions or offices, merger of divisions or offices, or elimination of
divisions or offices, shall not affect the scope of work as described
herein nor the contractor's obligation hereunder.

The introduction of this statement of work covers the contract-wide
management and administration (M&A) requirements.

The contractor shall provide M&A for all work that is described:

-   under level of effort and indefinite delivery, indefinite quantity
    (IDIQ) task orders and/or subtask orders that are issued at either a
    contract, directorate, and/or at a division/office level identified
    in the technical functional areas within Part I, or

-   under a performance based work breakdown structure (WBS) under the
    SOW in Part II

    M&A includes the technical and program management/allocation of
    program resources, program controls, planning, management reporting,
    and coordination with NASA.

    \*\*\*NEW NEW NEW

    Part I of the statement of work describes those services under the
    contract that may be directed through task orders under the task
    order clauses of the contract (Contract Section H.4 and H.5). Part
    II of the statement of work is reserved for performance based
    statements of work.

    \*\*\*From Schedule A, 13.1, General Support Requirements, edited;
    Schedule B, Introduction

    The Contractor shall provide support to the Science, Engineering,
    Analysis, and Test (SEAT) functional areas identified in this SOW
    and specific outside requesting organizations in all of the
    technical disciplines covered under this contract. Representative
    tasks include technical management studies, analytical studies,
    technical analysis, scientific research and analysis, engineering,
    investigations, systems engineering/integration activities,
    technical fact finding, and systems development and implementation,
    and science activities necessary to support current and future space
    missions, e.g., Space Shuttle, Spacelab, space station, and Space
    Exploration Initiative. Typical science projects include dedicated
    life sciences missions, space station mission increments, the
    biomedical monitoring and counter-measures project, small and rapid
    response payloads, crew health care system, and cosmic dust
    collection facility.

    Typical tasks for which the contractor shall be responsible include
    managing, developing, and implementing scientific and operational
    experiments to support research into the physiological responses and
    adaptation of humans to the environment of space; on-orbit medical,
    exercise, and environmental monitoring necessary to assure crew
    health; and other assigned payloads for both human and human-tended
    missions. In support of these activities, the contractor shall
    develop and provide ground support equipment, data systems and
    facilities; support payload design, test, and integration, and
    support all operational aspects of NASA-approved programs for flight
    missions.

    Also the contractor shall perform program management,
    payload/mission planning, systems analysis, physical and analytical
    integration, data management, flight operations planning and
    implementation, and advanced planning for all JSC-managed Spacelab
    life sciences missions or other experiment payloads assigned to
    human or human-tended pressurized module missions.

    **\*\*\*From Schedule A, edited to encompass entire SOW as
    applicable.**

    In all work areas of this SOW which encompass hardware design and
    development, including computer-aided design and drafting, the
    contractor shall, where described within authorized work elements,
    provide final detailed drawings suitable for fabrication and
    assembly of hardware. Drawing format, practices, and configuration
    management shall be performed in accordance with JPG 8500.4,
    "Engineering Drawing System Manual, as revised." All final drawings
    and subsequent drawing revisions will require approval by the
    Authorized Government Representative (AGR) before hardware
    fabrication begins.

    1\. Program Management and Administration

    \*\*\*From Schedule A, 13.2.1, Management Processes, edited

    The contractor shall provide program management and administration
    for all work performed under this contract. The contractor shall
    establish and maintain management processes for:

-   project/planning control,

-   performance management,

-   resources management,

-   safety, reliability and maintainability, and quality assurance ,

-   software quality assurance,

-   training coordination,

-   Information Technology (I/T) planning, and offsite I/T maintenance
    and operations.

    The management responsibility shall include procedures, tools, and
    metrics used to assure efficiency and cost savings. The contractor
    shall provide the clerical and administrative support incidental to
    performing the management function described herein.

    \*\*\*NEW NEW NEW

    The contractor shall establish an infrastructure consistent with
    effective execution of assigned work. This infrastructure will
    include:

-   Offsite Facilities

-   Offsite Communications systems

-   Offsite Building Management

-   Offsite Security

-   Contractor-required Information Technology

-   Payroll and Accounting

-   Finance and Administration Program Support

-   Human Resources, including relocation

-   Procurement, including Material Handling

-   Logistics

    The contractor shall provide the appropriate interfaces with NASA on
    procurement, business, and technical matters to ensure effective
    communication. The contractor shall retain enough flexibility in its
    management structure to handle informal inquiries. Examples may
    include inquiries to clarify procurement, business, and/or technical
    issues and problems.

    \*\*\*From Schedule B, Part 1, 2.2.4 and 2.2.5; Schedule B, Part 2,
    2.1.1

    The contractor shall provide the necessary program and technical
    management oversight, planning, scheduling, monitoring, project
    control, administration, and coordination of all effort under the
    contract. The contractor shall assign qualified personnel, institute
    cost control, and establish effective communication to accomplish
    the work. M&A shall provide the infrastructure for management of all
    the activities under the contract. This infrastructure shall include
    establishing efficient project and functional organizations
    regularly assessing the performance of such organization to ensure
    proper job assignment and accomplishment.

    The contractor shall provide total contract-level reporting for
    technical, cost, and schedule performance as specified in the
    following Data Requirements Lists (DRLs):

-   DRL 3 Organization Report

-   DRL 17 Security Reporting Requirements

-   DRL 18 DM-397T Quarterly Printing Report

-   DRL 19 Monthly Small Disadvantages Business Subcontract Report

-   DRL 20 Logistics Information

-   DRL 21 Financial Management Report

    The contractor shall provide a training coordination function to
    serve as the focal point for all SEAT training.

    The contractor shall prepare Basis-of-Estimates (BOE) for all
    performance based statement of work elements and task orders planned
    to be issued under this Contract. The BOE shall define the
    contractor's approach to performing the task (statement of work
    element), the skill mix and direct labor hours required, material
    and travel costs, and the target cost. BOE preparation for task
    order (statement of work) amendments shall be charged directly to
    the task order (statement of work).

    The contractor shall conduct a Monthly Management Review with the
    SEAT Contract Management Team. This review shall include a
    cost/resource and technical variance analysis for the prior month
    and for the Government fiscal year to date. The cost/resource
    analysis shall include a comparison of actual costs with contract
    baseline plans. The variance analysis will include total hours and
    equivalent persons, total direct labor dollars, subcontract costs,
    service center costs, other direct cost (ODC), overhead rate, G&A
    rate, material costs, travel costs, a wrap-rate analysis on
    level-of-effort (LOE) tasks and a bottom line actual vs. negotiated
    analysis on performance based efforts, and contract total cost and
    fee. The technical variance analysis shall include significant
    results of the variance analysis reported in DRL 21, Financial
    Management Report. The contractor shall identify resolution to cost
    and technical problems and review its internal cost and technical
    recovery plans. The contractor shall review their technical recovery
    plans for those major technical deficiencies found and formally
    documented in the contractor's performance. The contractor shall
    provide rationale for performance against contract negotiated
    values. The contractor shall provide a highlight of cost and
    technical efficiencies that have been identified for work being
    performed under SEAT Contract. The contractor is encouraged to also
    include a showcase of the technical work, a significant project, or
    tour of the area being performed by the contractor. The contractor
    is encouraged to showcase where new and improved techniques have
    been implemented for managing the work more efficiently. This
    Monthly Management Review shall be used as a forum for discussing
    significant technical, contractual, and cost issues on the SEAT
    Contract.

    The contractor shall plan, coordinate, track, monitor, and status
    level of effort and performance based efforts under this SOW. The
    contractor shall communicate progress to NASA according to the
    deliverables outlined in DRL 21.

    The contractor shall maintain and present to NASA when requested
    appropriate records, reports supporting data necessary to understand
    the contractor's plans for procurements, cost control schedule
    adherence, and technical work performance. Also, the contractor
    shall establish and present to NASA new and improved techniques for
    managing the work in an efficient manner.

    The contractor shall assess the results of NASA's overall contract
    performance evaluations in technical and cost categories and develop
    plans for correcting major weaknesses or deficiencies. These plans
    shall include corrective actions which shall be presented to NASA at
    the Monthly Management review until all corrective actions are
    completed.

    The contractor shall at least annually in concert with the beginning
    of the government fiscal year, review and assess overall and
    specific contract objectives. The contractor shall make changes to
    plans and recommendations to increase overall productivity and
    performance in meeting level-of-effort or performance based
    requirements. These opportunities for efficiencies and improved
    performance shall be presented to NASA. The contractor shall provide
    contribution to the annual fiscal year transition, training, and
    "kick-off" activities.

    2\. Environmental Safety and Health (ESH)

    The contractor shall ensure the protection of personnel, property,
    equipment, and the environment for contractor products and
    activities generated in support of institutional and space flight
    program objectives. To ensure compliance with pertinent NASA
    policies and requirements as well as Federal, State, and local
    regulations for safety, health, environmental protection, and fire
    protection, the contractor shall develop and implement a safety and
    health program in accordance with a safety and health plan as
    approved by the NASA. The contractor shall submit and comply with
    the following data requirements document:

-   DRL 1 Safety & Health Plan (SA-1-1)

    3\. Quality Management System

    \*\*\*NEW NEW NEW

    The contractor shall establish and maintain a Quality Management
    System (QMS) for design, development, and manufacturing of flight
    hardware, Ground Support Equipment (GSE), and associated flight
    software in the contractor's off-site facilities that complies with
    ANSI/ASQC Q9001-1994, American National Standard, Quality
    Systems---Model for Quality Assurance in Design/Development,
    Production, Installation, and Servicing. The contractor's QMS shall
    be registered by an RAB/ANSI accredited third party registration
    body by October 1, 1997. The QMS procedures, planning, and all other
    documentation and data that comprise the QMS shall be made available
    to NASA for review upon request. NASA may perform any necessary
    inspections, verifications, and evaluations, to ascertain
    conformance to requirements and the adequacy of the implementing
    procedures. The contractor shall require their subtier suppliers to
    have a QMS capable of achieving control of the quality of the
    services and supplies provided. NASA may exercise its right to
    disapprove the quality program or portions thereof when it fails to
    meet its intended objectives. Also, the contractor's quality manual
    as developed per the ANSI/ASQC Q9001-1994 requirements, shall be
    submitted in accordance with DRL #22, Quality Manual. The
    contractor's quality manual shall make provisions for the following
    supplements to the ANSI/ASQC Q9001-1994 elements:

    a\. Customer Verification of Subcontracted Product

    The contractor shall submit specified categories (ref: NASA/JSC
    Letter ND6-94-012 dated April 28, 1994) of procurement documents to
    the designated NASA quality representative for determination of the
    need for Government Source Inspection (GSI) prior to release of the
    procurement.

```{=html}
<!-- -->
```
-   Procurements which require GSI shall include the following
    statements:

    "All work on this order is subject to inspection and test by the
    Government at any time and place. The Government quality
    representative who has been delegated quality assurance functions on
    this procurement shall be notified immediately upon receipt of this
    order. The Government representative shall also be notified 48 hours
    in advance of the time articles or materials are ready for
    inspection or test."

```{=html}
<!-- -->
```
-   Procurements which do not require GSI shall include the following
    statement:

    "The Government has the right to inspect any or all of the work
    included in this order at the supplier's plant."

    b\. Review and Disposition of Nonconforming Product

    Disposition of non-conforming product, other than rework to
    specification, shall be approved by the designated NASA Quality
    Assurance Representative.

    c\. Traceability

    Traceability shall be as defined in the project requirements
    document and/or task order for each subsystem, unless otherwise
    specified, as a minimum for flight or GSE projects, a system shall
    be in place to ensure identification of all materials/products,
    whether separately produced discrete items, or material produced in
    lot/batches, to ensure traceability to the original
    source/manufacturer and to determine verification status. This
    system shall be maintained throughout the life of this contract,
    including material/product receipt; all stages of production;
    delivery; installation, etc.

    4\. Information Technology

    \*\*\*From Schedule A, 13.2,3, Planning edited: FIPR

    The contractor shall provide information technology (I/T) planning
    to NASA, along with an annual I/T plan that details the required I/T
    hardware, software, and services to meet the requirements of the
    organizations, laboratories, and facilities, delineated in the SOW
    for the next year and projections for 4 years following that year.
    The plan shall be submitted in accordance with the schedule
    delineated in DRL 2. The plan shall include an analysis to support
    what steps can be taken toward moving the SEAT Contract supported
    systems toward an open systems architecture and increasing the
    amount of competitive acquisitions.

    The contractor shall provide contract-wide planning support and
    development of management and operations approaches which are
    consistent with the I/T practices that NASA must employ. These
    approaches shall extend to all the I/T areas (equipment, software,
    networks, information, and personnel) and consider uniform
    approaches to similar services, commonality, standards, and other
    cost saving methods.

    The contractor shall provide information required to support the JSC
    Information Technology Systems Plan. The contractor shall report I/T
    data per the JSC Information Technology Systems Plan instructions
    published by the JSC Chief Information Officer.

    The contractor shall provide maintenance for the SEAT Information
    Technology (I/T) Government Furnished Equipment (GFE) located in the
    contractor's off-site facilities that it has in its possession.

    \*\*\*NEW NEW NEW

    The contractor, in performing this function, shall be disciplined in
    computer systems engineering, software engineering, and network
    engineering.

    **\*\*\*From MOU dated October 1, 1996**

    The contractor will continue to receive SPDEO heritage existing
    engineering analysis and office automation software onsite, as
    negotiated.

    \*\*\*NEW NEW NEW

    5\. Year 2000 Compliance -- Existing NASA Contracts (May 21, 1998)

    "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 provide documentation describing how
    the IT items or services delivered after October 1, 1998 demonstrate
    Year 2000 compliance. Effective October 1, 1998, this shall be
    accomplished by submittal of a certification to the Contracting
    Officer with each applicable deliverable under task orders or
    delivery orders. The certification will verify that the deliverable
    meets the specific requirements for Y2K compliance. Requirements for
    Y2K compliance shall be flowed down to any affected subcontracts or
    purchase orders.

<table style="width:100%;">
<colgroup>
<col style="width: 3%" />
<col style="width: 46%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
</colgroup>
<thead>
<tr class="header">
<th></th>
<th></th>
<th colspan="30">NEW Statement Of Work</th>
</tr>
<tr class="odd">
<th></th>
<th></th>
<th colspan="16">Part I</th>
<th colspan="14">Part II</th>
</tr>
<tr class="header">
<th><strong>Schd</strong></th>
<th><strong>Old SOW Element</strong></th>
<th>Intro</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4</th>
<th>5</th>
<th>6</th>
<th>7</th>
<th>8</th>
<th>9</th>
<th>10</th>
<th>11</th>
<th>12</th>
<th>13</th>
<th>14</th>
<th>15</th>
<th>A</th>
<th>B</th>
<th>C</th>
<th>D</th>
<th>E</th>
<th>F</th>
<th>G</th>
<th>H</th>
<th>I</th>
<th>J</th>
<th>K</th>
<th>L</th>
<th><p>M</p>
<p>N</p></th>
<th></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>A.</td>
<td>1.0 Crew And Thermal Systems Division (CTSD)</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.1.1.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.1.1.2 Payload-To-Orbiter ATCS, ECLSS, And EVA Integration</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.1.2 Shuttle-Unique</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.1.2.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.1.2.2 Other Shuttle Support</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.1.3 Space Station-Unique</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.1.3.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.1.3.2 Other Space Station Support</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.2 Research And Development Support</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.2.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.3 Engineering, Scientific, And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.3.1 Computer Programs Development And Maintenance</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.4 Studies And Assessments</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.4.1 General</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.1.4.2 EVA Systems Definition</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.1.4.3 Mechanical Systems Design</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1. 2 .1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.1.1 Division Processes And Controls</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.1.2 Common Facility Services</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.2 Federal Information Processing Resources (FIPR) Support</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.3 Special Purpose Laboratories</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.3.1 Soft Goods On-Site Development Laboratory</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.3.2 Soft Goods Off-Site Fabrication Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.3.3 Advanced Materials Laboratory</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.4 Technology/Discipline Laboratories</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.4.1 Thermal Control System (TCS) Laboratory</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.4.2 Environmental Control Life Support Systems (ECLSS)
Laboratory</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.4.2.1 Regenerative Life Support Systems (RLSS) Test
Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.4.2.2 Human-Rated Regenerative Life Support Systems Test
Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.4.2.3 Exploration Test Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.4.2.4 Hybrid Regenerative Water Recovery And Wastes Processing
Test Bed Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.4.3 Extravehicular Activity (Eva) Systems Laboratory</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.4.3.1 Advanced EMU Development Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.4.3.2 Space Station Airlock Test Article (SSATA) Test
Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.4.3.3 Crew Equipment Translation Assembly (CETA) Test
Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>1.2.5 Chemistry Laboratories</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>1.2.6 Bond Room Facility</td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.0 Tracking And Communications Division (TCD)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.1.1.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.1.1.2 Systems Engineering Technical Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.1.1.2.1 C&amp;T RF Coverage And Performance Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.1.1.2.2 C&amp;T System Performance Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.1.1.2.3 C&amp;T System Compatibility Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.1.1.2.4 Communications Systems Test</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.1.1.2.5 Electromagnetic Effects Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.2 Research And Development Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.2.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.2.2 Advanced Program Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.3 Engineering. Scientific. And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.3.1 Computer Program Development And Maintenance Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.4 Studies And Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.1.4.1 C&amp;T Conceptual Design Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.1.4.2 C&amp;T Special Studies</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.2 Federal Information Processing Resources (FIPR) Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.3 Communications Processing Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.4 Tracking Techniques Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.5 Electronic Systems Test Laboratory (ESTL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.6 Antenna Range And Anechoic Chamber</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.7 Microwave Design And Integrated Circuit Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.8 High Temperature Superconductivity (HTSC) Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.9 Electromagnetic Compatibility (EMC) And Electromagnetic
Interference(EMI) Test Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.10 Communications System Development Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.11 Communications Software Development Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.12 Communication Systems Simulation Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>2.2.13 Government Furnished Equipment (GFE) Flight Hardware
Maintenance Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>2.2.14 Bond Room Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.0 Navigation. Control. And Aeronautics Division (NCAD]</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.1.1 Shuttle - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.1.2 Space Station - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.1.2.1 Orbital Parameters</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.1.2.2 Rendezvous</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.1.2.3 Proximity Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.1.2.4 Payload Handling</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.1.2.5 Recontact Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.1.2.6 Mission Requirements Synthesis And Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.1.2.7 Systems Requirements Synthesis And Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.1.2.8 GN&amp;C</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.1.2.9 GN&amp;C Verification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.2 Research And Development Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.2.1 Avionics Systems Engineering And Integration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.3 Engineering. Scientific. And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.3.1 Flight Control System Stability</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.3.2 Computational Fluid Dynamics (CFD)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3 1.3.3 Other Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.4 Studies And Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.4.1 GN&amp;C Systems Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.4.2 Plume Flow Field And Impingement Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.4.3 Ascent Performance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.4.4 Aerodynamics</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.4.5 Entry Flight Testing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.1.4.6 Aerothermodynamics</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.1.4.7 Parachute Landing Systems</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.2.2 Federal Information Processing Resources (FIPR) Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.2.3 NCAD Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.2.3.1 Inertial Systems And Inertial Components Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.2.3.2 Electro-Optics Laboratory (EOL)/Tracking Laboratory
(TL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>3.2.3.3 Interactive Analysis Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>3.2.3.4 Technology Insertion Laboratory (TIL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.0 Flight Data Systems Division (FDSD)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.1 Engineering And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.1.1.1 Shuttle - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.1.1.1.1 Data Systems Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.1.1.1.2 Cargo Integration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.1.1.1.3 Change Request Coordination</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.1.1.2 Space Station - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.1.1.2.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.1.1.2.2 Software Support Environment</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.1.2 Engineering, Scientific, And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.1.3 Studies &amp; Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2 Laboratory/Facility Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.1 Laboratory/Facility General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.2 Federal Information Processing Resources (FIPR) Related
Activities</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.2.1 Computing/Networking Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.2.1.2 Network Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.2.1.3 Systems Software Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.3 Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.3.1 JSC Avionics Engineering Laboratory (JAEL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.3.2 Flight Data Recorder Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.3.3 Instrumentation Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.3.4 Portable Computer Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.3.5 Display And Control Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.3.6 Real-Time Systems Engineering Laboratory (RSEL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.4 Facilities</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.4.1 Software Development Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.4.2 Avionics Development Facility (ADF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.4.3 Central Software Facility/Central Avionics Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>4.2.4.4 Technical Library</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>4.2.4.5 Building Facilities Design And Integration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.0 Propulsion And Power Division (PPD)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.1.1.1.1 Payload Safety Analyses</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.1.1.1.2 Pyrotechnic Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.1.1.1.3 Battery Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.1.1.1.4 Government Furnished Equipment (GFE) Wiring</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.1.1.2 Shuttle - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.1.1.2.1 Modeling And Analysis Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.1.1.2.2 Programming And Documentation Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.2.2 Federal Information Processing Resources (FIPR) Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.2.3 PPD Technical Discipline Facilities</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.2.3.1 Propulsion Test Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.2.3.2 Power Systems Test Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.2.3.3 Fluid Systems Test Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.2.3.4 Thermal Vacuum Test Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.2.3.5 Pyrotechnics Test Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>5.2.3.6 Control/Actuation And Power System Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>5.2.3.7 Electrical Power Systems Laboratory (EPSL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.0 Automation And Robotics Division (A&amp;RD)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.1.1.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.1.1.2 Other Multiprogram Support Functions</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.1.2 Shuttle - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.1.2.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.1.2.2 Other Shuttle Support Functions</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.1.3 Space Station- Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.1.3.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.1.3.2 Other Station Support Functions</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.2 Research And Development Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.2.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.2.1.1 Systems Engineering And Integration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.2.1.2 Intelligent Systems Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.2.1.3 Robotic Systems Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.1.3 Engineering, Scientific, And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.1.3.1 Computer Program Development And Maintenance Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.2.2 Federal Information Processing Resources /FIPR Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>6.2.3 The Automation And Robotics Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>6.2.4 Bond Room Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.0 Structures And Mechanics Division (SMD)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.1.1.1.1 Subsystem Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7 1.1.2 Shuttle – Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.1.1.2.1 General Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.1.2 Research And Development Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.1.2.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.1.3 Engineering, Scientific, And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.1.3.1 Computer Program Development And Maintenance Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7 1.3.2 Analysis Methods Development And Data Base Maintenance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.1.4 Engineering Studies And Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.2.2 Federal Information Processing Resources (FIPR) Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.2.3 Atmospheric Re-Entry Materials And Structures Evaluation
(ARMSEF) And Radiant Heating Test Facility (RHTF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.2.4 Structures Test Laboratory (STL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.2.5 Vibration and Acoustics Test Facility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>7.2.6 Materials Technology Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>7.2.7 Mechanical Systems Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.0 Systems Engineering Division (SED)</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1 Program Management Support</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.1 Multiprogram</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1 1.1.1 Systems Engineering And Integration</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.1.2 Systems Engineering Analysis, And Trade Studies</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1.1.3 Engineering Design And Development Products</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.1.4 Simulation Development</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1.1.5 Analysis</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.1.6 Analytical Development</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1.1.7 Requirements Development</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.1.8 Test Analysis</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1.1.9 Advanced Planning And Implementation</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.1.10 Systems Engineering (SE) Process Development</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1.2 Shuttle Unique</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.2.1 Space Shuttle Cargo Integration</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.1.3 Space Station - Unique</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.1.3.1 Systems Engineering Analysis</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.2 Research And Development Support</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.2.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.2.1.1 Systems Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.2.1.2 Systems Design and Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.2.1.3 Trajectory, Mission/Performance Analysis, And
Integration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.2.1.4 System Performance And Resource Utilization</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.2.2 Other R&amp;D Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.2.2.1 Workshops</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.3 Engineering, Scientific. And Analytical Tools</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.3.1 Data Base Management Systems (DBMS)</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.3.2 Data Base Support</td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.1.3.3 Simulator Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.1.3.4 Simulator Update</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.2.2 Federal Information Processing Resources</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.2.2.1 Analyst Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>8.2.3 Facility Development and/or Upgrade</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>8.2.4 Systems Engineering Simulation Laboratory (SES)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.0 New Initiatives Office (NIO)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.1.1.1 Payload Mission Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.1.1.2 Experiment/Payload Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.1.1.3 Experiment Project Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.1.2 Shuttle - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.1.2.1 Commercial Middeck Augmentation Module (CMAM) Engineering
Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.1.3 Space Station - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.2 Engineering, Scientific, And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.2.1 Computer Program Development And Maintenance Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.3 Studies And Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.3.1 Future Mission Studies</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.4 Research And Development Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.4.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.4.1.1 Human Space Transportation And Human Planet Surface
Systems</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.4.1.1.4 Systems Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.4.1.2 Space Servicing Systems</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.4.1.2.1 Program Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.4.1.2.2 Space Assembly And Servicing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.4.2 Technology Utilization And Commercial Transfer</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.4.2.1 Technology Advancement</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.1.4.2.2 Technology Utilization</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.1.4.2.3 Research And Technology Programs Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.2.2 Federal Information Processing Resources Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.2.2.1 Computer Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.2.3 Special Purpose Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.2.3.1 Experiment Development Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>9.2.3.2 Model Development Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>9.2.3.3 Payload Integration Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>10.0 Human Life Sciences Division (HLS)</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>10.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>10.1.1 Program Management Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>10.1.1.1 Multiprogram</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>10.1.1.1.1 Science Operations Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>10.1.1.1.2 Science Missions Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>10.1.1.1.3 Project Engineering Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>10.1.1.2 Studies And Assessments</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>10.1.1.2.1 Programs Office Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>10.2 Laboratory/Facility Support Services</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>10.2.1 General Support Services</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>10.2.1.1 Advanced Concepts</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.0 Solar System Exploration Division (SSED)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1 Engineering, Scientific, And Analytical Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.1 Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.1.1 Shuttle - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.1.1.1 Flight Science</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.1 1.1.1 Space Shuttle Earth Observations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.1.1.1.2 Space Shuttle Photo/TV Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.1.2 Space Station - Unique</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.1.2.1 Space Station Earth Observations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.1.2.2 Space Station Photo/TV Analysis Project</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.2 Research And Development Summary</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.2.1 Advanced Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.2.1.1 Experiment Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.2.1.2 Lunar And Mars Exploration Concept Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.2.2 Scientific Research</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.3 Engineering, Scientific, And Analytical Tools</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.1.4 Studies And Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.1.4.1 Engineering, Science, Technical, And Management
Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2 Laboratory/Facilities Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.2.1 General Support Services</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2.2 Federal Information Processing Resources (FlPR) Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.2.3 Planetary Materials Curatorial Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2.4 Geoscience And Space Science Instrumental Analysis
Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.2.5 Specialized Experimental Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2.5.1 Experimental Planetary Science Laboratories</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.2.5.2 Experimental Impact Laboratory (EIL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2.5.3 Hypervelocity Impact Test Facility (Hit-F</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.2.5.4 Radar Data Analysis Facility (RDAF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2.5.5 Radiation Dosimetry Laboratory</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>11.2.6 Video Digital Analysis Laboratory (VDAS)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>11.2.6.2 Earth Observations Laboratory (EOL)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>12.0 Flight Engineering Office</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>12.1 Computer Systems Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>12.2 Software And Data Base Maintenance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>12.3 Photographic And Program Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>12.4 Information Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>12.5 MER Hardware/Software Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>12.6 ODRC Rehost Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>12.7 MER Engineering Data Display System Upgrade</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.0 Engineering And Scientific Support</td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.1 General Support Requirements</td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.1.1 Office Automation Applications</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.1.2 Financial Data Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.1.3 Subsystem Management Support System (SMSS) And Orbiter Data
Reduction Complex (ODRC) Interface System</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.1.4 Engineering Standards And Processes</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.1.5 Visual Communication Lab Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2 Contract-Wide Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.1 Management Processes</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.2 Maintenance And Operations Support</td>
<td></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.3 FIPR Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.4 Logistics Support</td>
<td></td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5 Safety. Reliability And Maintainability. And Quality
Assurance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.1 Safety And Health</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.2 Reliability And Maintainability(R&amp;M) Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.3 Quality Assurance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.1.5.3.1 Instrument Calibration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.3.2 Materials Analysis And Testing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.3.3 Record Center Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.3.4 Ground Based Pressure Systems Certification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.4 Software Quality Assurance (SQA)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.4.1 SQA Organization And Authority</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.4.2 SQA Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.4.3 SQA Implementation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.4.4 Software Quality Audits</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.4.5 Software Quality Records And Reports</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.4.6 Software Nonconformance And Corrective Action
Procedures</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.4.7 Software Delivery/Acceptance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>A.</td>
<td>13.2.5.4.8 Subcontract SQA Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>A.</td>
<td>13.2.5.4.9 Personnel Training And Certification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td><strong>SCHEDULE B SOW</strong></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td><strong>PART 1</strong></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.0 Introduction</td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.1 Task Work Breakdown Structure (WBS)</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.0 Project Management And Control</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.1 Project Planning And Requirements</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.2 Project Control</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.2.1 Performance Management And Administration</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.2.2 Cost Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.2.3 Schedule Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.2.4 Project Control System Development And Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.2.5 Resources Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.2.6 Advanced Planning</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.3 Management Operations</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.3.1 Configuration Management And Control</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.3.2 Information Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.3.3 Logistics Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.3.4 Procurement Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.3.5 Safety, Reliability, And Quality Assurance (SR&amp;QA)
Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.3.6 Project Documentation, Management Information, And
Presentations</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.3.7 Scientific And Technical Information (STI) Center</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.3.7.1 Technical Information</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.3.7.2 Special Projects</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.3.8 Requirements Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.0 Payload Planning And Experiment Management/Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.1 Payload Planning And Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.1.1 Flight/Payload Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.1.2 Principal Investigator Support For Payload Planning And
Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.1.3 Science Requirements Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.1.4 Experiment Systems Definition Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.1.5 Performance Analysis</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2 Experiment Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.1 Experiment Support Teams (ESTs)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.1.1 Experiment Requirements Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.1.2 Statement Of Work Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.1.3 Experiment Systems Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.1.4 Experiment Systems Documentation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.2 Roles Of Experiment Managers</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.2.1 Experiment Systems Testing -</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.2.2 Experiment Safety Compliance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.2.3 Experiment Systems Interface Compatibility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.2.4 Experiment Verification And Certification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.2.5 Experiment Hardware Configuration Control</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.2.6 Experiment Coordination</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.2.7 New Experiment Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.2.8 Documentation Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.2.9 Experiment Hardware Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.2.10 Experiment Requirements Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.3 Roles Of Experiment Engineers</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.3.1 Experiment Systems Testing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.3.2 Experiment Hardware Safety Compliance/Verification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.3.3 Experiment Systems Interface Compatibility</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.3.4 Experiment System Interface Documentation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.3.5 Experiment Verification And Certification Tests And
Reports</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.3.6 Experiment Systems Hardware Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.3.7 Experiment Hardware Configuration Control</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.3.8 Experiment Hardware/Software Integration And
Maintenance</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.3.9 Experiment Support For Crew Training</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.2.3.10 Experiment Baseline Data Collection (BDC)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2.3.11 Documentation Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.0 Flight Hardware/Software Engineering And Provisioning</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.1 Systems Engineering</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.1.1 Experiment System Engineering Studies</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.1.2 Experiment System Interface Compatibility</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.1.3 Experiment System Interface Documentation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.1.4 NASA Safety Accurate Launch Emergency Reliability Tips
(Alerts) Coordination</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.2 Project Engineering Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.2.1 Hardware Requirements Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.2.2 Hardware Development Plans</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.2.3 Hardware Specification Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.3 Hardware Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.3.1 HLS Refrigerator/Freezer (R/F) Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.3.1.1 HLS Refrigerator/Freezer Improvements</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.3.1.2 Development Of Second Generation Life Sciences
Refrigerator/Freezers</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.3.2 In-house Flight Equipment Design</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.4 Sustaining Engineering Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.4.1 Flight Data Systems</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.4.2 Microcomputer Laboratory</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.4.3 Flight Data Systems Interface</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.5 Flight- Equipment Inventory/Maintenance</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.5.1 Preventive Maintenance</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.5.2 Logistics</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.5.3 LSLE Usage Schedule/Mission-Commitment Data</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.6 LSLE Modernization</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.6.1 Trade-Off Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.6.2 LSLE Modernization Implementation Plan</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.6.3 LSLE Modernization' Cost Estimate</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.7 Payload Project Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.7.1 Payload Feasibility</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.7.2 Support For Payload Project Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.7.2.1 Inter-Organizational Liaison</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.7.2.2 Resource Allocation</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.7.2.3 Payload Status</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.7.3 Project Payload Definition</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.7.4 Mission Reviews And Presentations</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.7.5 Mission Support To The Payload Project Manager</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.7.6 Flight Hardware Safety</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.7.7 Documentation Reviews</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.8 Systems Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.8.1 Structural And Mechanical Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.8.2 Thermal And Environmental Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.8.3 Electrical Systems Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.9 Integration Hardware Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.9.1 Integration Hardware Requirements Definition</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.9.2 Hardware Design Engineering And Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.9.3 Hardware Inventory Control</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.10 Stowage Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.11 Engineering Design And Drafting</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.0 Data Systems Development And Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.1 Experiments Data Requirements Definition And Determination Of
Methods Meeting Experiment Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2 Ground Data Systems Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.1 Data Systems Hardware</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.1.1 Real-Time Data Systems Hardware</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.1.2 Non-Real-Time Data Systems Hardware</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.1.3 Computer Network Hardware</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.2 Management Computational Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.2.1 Management Computational Support Requirements
Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.2.2 Management Computational Support Data Systems Hardware</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.3 Ground Data Systems Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.3.1 Real-Time Experiment Systems Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.3.2 Non-Real-Time Experiment Systems Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.3.3 Management Systems Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.3.4 Computer Network Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.3.5 Computer Network Management And Security</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.3.6 Data Bases</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.3.7 Data Storage And Retrieval</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.4 Data System And Ground Support Equipment Operation, Security,
Maintenance, And Configuration Control</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.4.1 Computer System Operation And Security</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.4.2 Computer Operating System Generation And Maintenance And
System Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.4.3 Maintenance Of Computer Equipment And Related Ground Support
Equipment</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.4.4 Configuration Control</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.4.4.1 Hardware Configuration Control</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.4.4.2 Software Configuration Control</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.2.4.4.3 Software Configuration Control Library</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2.5 Maintenance And Operation Of Specialized Computer Systems And
Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.3 Experiment And Payload Testing, Simulation, Mission Support, And
Training</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.3.1 Mission Support Preparation</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.3.2 Training</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.4 Attendance At Technical And Professional Conferences</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.5 Technical Documentation</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.6 Compliance With Federal Information Processing (FIP) Regulations
And Policies</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.7 Computer System Upgrading</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.8 Production Of Postmission Data Products For Principal
Investigators</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.0 Project Science Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1 Experiment-Support Scientist Program</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.1 Science Documentation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.2 Data Sharing Plan</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.3 Investigator Working Group (IWG)/Science Working Team (SWT)
Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.4 Life Sciences Laboratory Equipment Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.5 Payload Science Objectives/Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.6 Experiment Solicitation/Selection</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.7 Experiment Procedures Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.8 Payload Flight Data File (PFDF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.9 Light Crew Training Scheduling</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.10 Human Research Policy And Procedures Committee (HRPPC)
Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.11 Crew Activity Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.11.1 Experiment Timeline Requirements Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.11.2 HLS Payload Project Timeline Requirements Document
Preparation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.11.3 Preflight/Postflight Data Collection Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.12 Medical Experiments Data Collection Facility (MEDCF)</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.0 Project Payload Integration And Verification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.1 Project Payload Assembly And Installation And Payload
Integration Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.2 Experiment Checkout</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.3 Experiment Verification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.4 Science Verification Test</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.5 Total Project Payload Verification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>8.0 Operational Training</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>8.1 Flight Crew Training</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>8.2 Ground Crews And Support Personnel Training And Mission
Integrated Training/Simulations (MIT/Ss), Joint Integrated
Training/Simulations (JITSS), and Other Simulations Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>8.3 Training Certification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>9.0 Mission Operations Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>9.1 Science Monitoring Area And Payload Operations Control Center
Operations Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>9.2 Project Payload Performance Analysis And Reports</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>9.3 Principal Investigator Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>10.0 Facility/Ground Systems Engineering And Operations</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>10.1 Operations Support Facility Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>10.1.1 Planning And Analysis</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>10.1.2 Design, Monitoring And Certification Of Facilities</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>10.1.3 Buildings 36, 56, And 266 Facility Buildup</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>10.2 Ground Support Equipment, Test Equipment, And Spares</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>10.3 Vehicle Mockup And Test Bed Development</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>10.4 Laboratory Management</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>10.5 Test-And Fabrication Support</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>11.0 Advanced Technology Development (ATD)</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>11.1 Advanced Technology Development Project Review Board
Activities</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>11.2 Advanced Technology Development Project Teams</td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td><strong>PART 2</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.0 Introduction</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.0 Payload/Program Management Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.1 Program Control</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.1.1 Resource And Cost Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.1.2 Configuration Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.1.3 Schedule Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.1.4 Information Management System</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.1.5 Procurement Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.2 Programmatic Documentation Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.3 Major Program Review Support/Coordination</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.4 Safety, Reliability, And Quality Assurance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.4.1 Safety</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.4.2 Reliability</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.4.3 Quality Assurance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>2.4.4 Surveys</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>2.5 Special Studies</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.0 Mission Feasibility And Design</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.1 Mission Feasibility And Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.2 Detailed Mission Design</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.3 Resource Allocation Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.4 System Engineering</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.4.1 Structural/Mechanical</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.4.2 Thermal/Environmental</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.4.3 Electrical</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>3.4.4 Mass Properties</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>3.4.5 Stowage Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.0 Mission Peculiar Equipment/Other Support Hardware
Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>4.1 Hardware Requirements Definition</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>4.2 Hardware Design/Fabrication</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.0 Data Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.1 Flight Data System</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.2 Ground Data System</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.3 Data System Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.3.1 Flight Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>5.3.2 Ground Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>5.3.3 Simulation Software</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.0 Flight Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1 Flight Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.1.1 Operations Support Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.1.2 Operations Guidelines And Constraints</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.2 Flight Design</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.3 Payload Crew Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.3.1 Payload Crew Training</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.3.2 Baseline Data Collection</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.3.3 Launch And Landing Site Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.4 Payload Flight Data File Development Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.5 Payload Operations Control Center/Payload Operation Integration
Center Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.5.1 Real-Time Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.5.2 Payload Operations Support Team (Post)/Payload Operation
Integration Center Training</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>6.6 Simulations Management</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>6.7 Mission Integrated Training Facility Maintenance</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.0 Payload Integration</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.1 Ground Processing Of The Integrated Payload</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.2 Mission Peculiar Equipment And Experiment Developer Hardware
Verification</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.3 Ground Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.3.1 Ground Operations Management Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.3.2 KSC Documentation Logging And Tracking</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.4 Logistics</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>7.4.1 Stowage Provisions</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>7.4.2 Flight Hardware Logistics</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>8.0 Advanced Programs/Planing</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>X</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td><strong>PART 3</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.0 Introduction</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.1 Science Program Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.1.1 Science Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.1.2 Mission Science Requirements</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.2 Science Applications</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.2.1 Science Operations</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.2.1.1 Timeline Development</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.2.1.2 Contingency Planning</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.2.1.3 Mission Science Console Support</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.2.1.4 Mission Science Readiness Assessments</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>B.</td>
<td>1.2.2 Science Reporting And Documentation</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>B.</td>
<td>1.2.3 Science Coordination</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

# PART I - AREAS OF SUPPORT {#part-i---areas-of-support .unnumbered}

**SECTION A: ENGINEERING**

**1. SYSTEMS ENGINEERING**

\*\*\*From Schedule A, 8.0, SYS. ENG. DIV:

1.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

1.1.1 Program Management Support

**1.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and space station Program. The following are
representative tasks the contractor shall perform:

**1.1.1.1.1 Systems Engineering and Integration** - Support
multidiscipline projects involving multiple functions. This includes
project management and multi-discipline technical support for projects
requiring definition, design, research, development, fabrication,
integration, and testing of complex facilities, systems, flight and
flight-like hardware.

**1.1.1.1.2 Systems Engineering Analysis, and Trade Studies**

1.1.1.1.2.1 Provide analysis support for mission definition, design and
development, system requirements, and system design evaluations for
current and future NASA programs and projects; provide analytical
studies to assess alternate mission and system design options; provide
technical integration across program elements; assist in providing
technical direction to other contractors; and perform independent
analysis.

1.1.1.1.2.2 Provide engineering and analysis to support performance
scans and trade studies leading to the selection of optimum systems and
operations performance profiles and trajectory parameters for current
and future NASA programs and projects. Study areas include the
functional areas of system performance and resource utilization for
electrical power, thermal, Environmental control and Life Support
Systems (ECLSS), and propulsion; orbit strategy and maintenance;
resupply missions and return from human-staffed bases; integrated stem
design verification; design cycle planning and implementation; ascent,
descent, rendezvous, proximity operation, and navigation; attitude and
pointing; separation analysis; and tethered satellite dynamics analysis.

**1.1.1.1.3 Engineering Design and Development Products**

1.1.1.1.3.1 Perform product design, development, and delivery, for those
products associated with the systems performance, resource utilization,
trajectory control, and logistics (resupply and return) of current and
future NASA program vehicles and elements from the conceptual design
phase through the development and operations readiness phases of these
programs.

**1.1.1.1.4 Simulation Development** - Define requirements for a
simulation; formulate requirements to the equation level; and size the
simulation in terms of manpower, cost, schedule, and verification-plan.
Convert simulation requirements into math models and integrate them with
the simulation executive; execute and analyze test cases in accordance
with the verification plan. Support the software simulations and math
models including flight mechanics, dynamics, and hardware math models;
stand alone guidance, navigation, and control math models; and
integrated Monte-Carlo and linear covariance simulations employing the
above math models.

**1.1.1.1.5 Analysis** - Define analysis plans and products as well as
size the task in terms of labor, cost, and schedule perform analysis
studies including: flight phase performance envelopes affected
(thrust-to-weight ratio, lift-to-drag ratio, ballistic coefficient,
delta-V, stage mass split, throttle range, maximum angular accelerations
for control, and navigation measurement types); flight phase and systems
compatibility assessments; and navigation performance envelopes
supporting the flight phases.

**1.1.1.1.6 Analytical Development** - Define analytical development
plans and products as well as size the task in terms of labor, cost, and
schedule. Derive the supporting flight phase analytics, for the
following models: Monte- Carlo; linear covariance; guidance and
targeting; navigation; control; flight mechanics; dynamics; and control
and navigation hardware.

**1.1.1.1.7 Requirements Development** - Define flight phase performance
parameter requirements such as thrust-to-weight ratio, lift-to-drag
ratio, and ballistic coefficient. These requirements are derived from
flight phase performance envelopes and/or are compatible with
programmatic requirements and guidelines.

**1.1.1.1.8 Test Analysis** - This function provides the analytical
effort required to implement test programs in compliance with official
test requirements documentation. This includes early participation in
requirements definition and analysis, preparation of test implementation
requirements sheets, generation and/or modification of math model
formulations and expert systems specifications, evaluation and
generation of proposed hardware and/or software changes required to
implement tests, analysis of system problems for the purpose of
recommending solutions and other system analysis in support of test
operations. The following are representative tasks the contractor shall
perform:

1.1.1.1.8.1 Analyze official requirements documents with respect to
satisfying the requirements through facility tests.

1.1.1.1.8.2 Prepare implementation plans for each task to be performed.
These plans shall include laboratory element implementation requirements
and initial conditions if they are lacking in other documents.

1.1.1.1.8.3 Generate and/or modify simulator math models and expert
systems in compliance with new requirements to be satisfied by the
Systems Engineering facility.

1.1.1.1.8.4 Perform system analysis studies in support of test design
and configuration definition in response to test requirements.

1.1.1.1.8.5 Optimize/prioritize tests for maximum support.

1.1.1.1.8.6 Perform test status reviews to determine omissions, schedule
problems, and adequacy of test and checkout procedures.

**1.1.1.1.9 Advanced planning and implementation** - This function
provides the planning, engineering, and implementation of systems in
support of long-range requirements. Included are analysis of system
design requirements, planning of facility and equipment and
modifications, development of test requirements, development of
supporting software, development of math models and expert systems
specifications for advanced systems, and the conduct of test support
operations. The following are representative tasks the contractor shall
perform:

1.1.1.1.9.1 Participate in Systems Engineering advanced planning
functions to determine requirements for an effective simulation;
establish coordination with outside groups which will use the simulator
or obtain data from test runs; estimate labor, costs, and schedules for
the project; prepare work packages to give specific task assignments,
detailed schedules, and formal review points; and define facility
requirements such as power, space, and cooling.

1.1.1.1.9.2 Contractor tasks to implement advanced planning simulation
requirements are identical to those listed under functions 7.1.3.2,
Simulator Development.

**1.1.1.1.10 Systems Engineering (SE) Process Development**

1.1.1.1.10.1 Provide systems engineering services to projects, including
the Common Lunar Lander (CLL) and Personnel Launch System (PLS)
projects. This effort shall include continuous refinement of systems
engineering environment, conduct of rigorous pre- Phase A and Phase A
systems studies, incubation of new process teams, cost/schedule plan
proposals, requirements analysis, risk analysis (cost, schedule,
quality, and performance), evaluation of SE tools, and communication of
results to all cognizant program and functional organizations. Report
variance with requirements to NASA technical personnel.

1.1.1.1.10.1 Provide systems engineering support to the Systems
Engineering Process Improvement Team (SEPIT) and SEPIT Project
Management Team. This effort shall include to document tree, data
dictionary, detailed definition of life cycle charts, generic project
life cycle update plan, definition phase project review, project
implementation plan, and detailed project plans for development of later
phase products; and report variance with requirements to NASA technical
personnel.

\*\*\*From Schedule A, SED, 8.1.1.2 Shuttle-Unique:

**1.1.1.2 Shuttle Unique**

**1.1.1.2.1 Space Shuttle Cargo Integration** - This function provides
support for the safety and programmatic related activities to be
performed for Space Shuttle Program (SSP) safety panels and change
boards. The following are representative tasks the contractor shall
perform:

1.1.1.2.1.1 Support payload safety reviews which include the review of
payload safety documentation to show compliance with NASA standards; and
identify areas of non- compliance found in the proposed design and
report to the payload sponsor, NASA Safety representative and the safety
panel for each safety review phase.

1.1.1.2.1.2 Evaluate programmatic changes to ensure compatibility with
existing accommodations/requirements documents, identify issues, and
recommend solutions.

1.1.1.2.1.3 Provide technical support to the SSP Berthing Panel. This
panel is responsible for providing the integrated technical solutions
which optimizes the berthing process between the Shuttle Orbiter and
space station. Perform studies and assessments associated with mating
these two vehicles; identify issues; and recommend solutions to NASA
technical personnel.

**1.1.1.3 Space Station - Unique**

**1.1.1.3.1 Systems Engineering Analysis** - This function is
responsible for evaluating space station designs and preliminary
revisions of new space station design options such as post-permanent
human capability (PHC) and evolution. Geometric computer modeling of the
space station in the IDEAS\*\*2 environment is required. The IDEAS\*\*2
environment is also used to perform studies, simulations, and
assessments. Other tools, such as BUMPER for meteoroid and debris and
FEAT for fault tolerance, are used for studies and assessments. Some
studies are also performed in the Systems Engineering Simulator aft
cockpit simulator. The following are representative tasks the contractor
shall perform:

1.1.1.3.1.1 Collect, focus, and develop integrated geometric models
across space station work packages using the IDEAS\*\*2 computer
modeling environment. Subsystems include power generation and
distribution; structures; guidance, navigation and control;
communications and tracking; thermal control; data management;
environmental control and life support; EVA; berthing; and Shuttle
Orbiter. Vehicle properties such as dimensional data, mass properties,
coordinate systems, and aerodynamics shall be in bed either in the
models, or be computed as a result of the models. Natural environments
such as atmosphere, orbital debris, radiation, and earth\'s gravity
shall be used in the model development or assessment process.
Methodologies must account for types, fidelity of data and documentation
required by users. Implement selected methodologies and provide
continuing support; document and recommend methodologies for providing
integrated geometric models; and document chosen methodologies.

1.1.1.3.1.2 Perform analyses and trade studies of space station
configuration and systems options including optimization and evaluation
of configurations, requirements and constraints levied by space station
users (e.g., micro-gravity environment) and designers; analysis of rigid
and flexible control systems, structural interference, constraints on
proximity operations (e.g., viewing) and astronaut EVA. Perform weight
and mass properties assessments; provide analysis products (e.g.,
moments of inertia for WP-2 hardware) to support the appropriate space
station organization; manage the software tools and-hardware platforms
utilized for assessments and the geometric modeling; provide
recommendations to maintain the required hardware/software capability;
and report variances with requirements to the NASA technical personnel.

1.1.1.3.1.3 Perform analyses and assessments of the meteoroid and debris
environment and how this impacts the hardware designs and how well the
designs meet space station requirements. The BUMPER tool is typically
utilized for these assessments. Report variances with requirements to
the NASA technical personnel.

1.1.1.3.1.4 Perform analyses and assessments of the failure tolerance
capability of the hardware and software designs to indicate how well the
designs meet the space station requirements; and report variances with
requirements to the NASA technical personnel.

1.1.1.3.1.5 Perform maintainability assessments; identify issues and
recommendations to resolve them; and report issues and recommendations
to the NASA technical personnel as they are raised.

1.1.1.3.1.6 Operate and maintain the Configuration Management
Engineering System (CMES). This Oracle data base is used in the
Engineering Directorate to track and status the Level II Change Requests
(CR's) and provide the Project Office with a coordinated Engineering
Directorate technical position on the proposed change.

1.1.2 Research and Development Support

\*\*\*From Schedule A, SED, 8.1.2.1.4, System Performances and Resource
Utilization:

**1.1.2.1 System Performance and Resource Utilization** - The following
are representative tasks the contractor shall perform:

1.1.2.1.1 Perform system performance and resource utilization analysis,
develop and maintain the associated software tools and working data
bases to support the space station and advanced program vehicle design,
design assessment and operations concept development for electrical
systems and certain mechanical systems.

1.1.2.1.2 Provide detailed analysis of spacecraft electrical power
systems (EPS) with focus on system performance as well as the
operational aspects of the power system; perform trade studies to
develop and evaluate EPS systems requirements and support development of
operations scenarios for various configurations; perform analyses to
evaluate the EPS under nominal and off-nominal scenarios; and utilize
and maintain an electrical equipment data base. Adapt application
software from existing tools, obtained from commercial sources, or
developed by this task to meet analysis needs for modeling spacecraft
power generation, storage, distribution, and usage.

1.1.2.1.3 Perform detailed systems and resource (consumables) analysis
with emphasis on the systems performance as well as the operational
aspects of spacecraft thermal control systems (TCS), ECLSS and
propulsion systems; perform trade studies to evaluate system
requirements and support development of operations scenarios for various
spacecraft assembly configurations; perform analyses to evaluate the
integrated TCS and ECLSS systems under nominal and off-nominal
scenarios; and adapt application programs from existing tools, obtained
from commercial software packages, or developed by this task for
modeling these systems.

1.1.2.1.4 Develop fully time-phased electrical power, thermal, nitrogen,
oxygen, water, and other systems resource profiles of selected
operational mission segments for evaluation of specified system design
cases. For example, schedule electrical components that support the
various spacecraft systems in such a way as to ensure that both mission
and spacecraft requirements are met.

1.1.2.1.5 Perform EPS, TCS, ECLSS, and propulsion systems analyses that
support the definition, development, and assessment of design reference
missions and assembly sequences. The scenarios and associated
evaluations and assessments are for the purpose of developing and then
refining system design requirements.

1.1.2.1.6 Provide analysis support for trade studies, evaluate proposed
operational constraints against system requirements, and evaluate
resource usage against allocations.

1.1.2.1.7 Develop the analytical algorithms to analyze spacecraft
electrical power generation, storage, and distribution systems; stand
alone and integrated spacecraft TCS and ECLSS ; and propulsion system
performance.

1.1.2.1.8 Support panels and working groups.

1.1.2.1.9 Collect, review, critique, and store systems data obtained
from SE&I, Level II, subsystem managers, and various other sources.

1.1.2.1.10 Extract the data required for system and mission analyses
from the various data sources and supplement these data.

1.1.2.1.11 Support the development of data exchange and interfaces
between systems analysis tasks, including definition of interface
specifications and interface conversion programs/data bases.

1.1.2.1.12 Support the development of requirements and design of
engineering data bases such as those required-for Electrical, Mass
Properties, Thermal, Propulsion, ECLSS, and any additional data bases
required to accomplish systems analysis tasks.

1.1.2.1.13 Maintain test, development, and production environments for
all in 1.1.2.1.4 and other data bases and software tools.

\*\*\*From Schedule A, SED, 8.1.3, Eng. Sci. & Analytical Tools:

1.1.3 Engineering, Scientific, and Analytical Tools

\*\*\*From Schedule A, SED, 8.1.3.1, DBMS:

**1.1.3.1 Data Base Management Systems (DBMS) -** The following are
representative task the contractor shall perform:

1.1.3.1.1 Maintain applications; collect, analyze, and screen selected
DBMS data; and support trade studies regarding the application of data
base management systems to support the above engineering analyses and
produce development.

1.1.3.1.2 Analyze data arrangement and data requirements with respect to
data format and DBMS capabilities; design and implement data file
structures and relations to meet requirements for data base expansion
and efficient report generation; support any movement to an alternate
DBMS or computer system; and develop and implement configuration control
procedures for data base file usage.

1.1.3.1.3 Provide data collection, screening, and analysis for all areas
of the DBMS; work with various groups to coordinate and resolve all data
discrepancies, evaluate the quality of the data with respect to
operational constraints; and provide points-of-contact for customers and
users of all DBMS.

\*\*\*From Schedule A, SED, 8.1.3.2, Data Base Support:

**1.1.3.2 Data Base Support** - The following are representative tasks
the contractor shall perform:

1.1.3.2.1 Provide Data Base Management Systems support for both the
Trajectory. Mission/Performance Analysis, and Integration task and the
Systems Performance and Resource Utilization task. Representative
technical support subtasks include the following: provide installation,
maintenance, testing, and control of the Adabas/natural and Oracle DBMS.
Develop and document procedures for maintaining and controlling access
to the DBMS; provide user training for the DBMS and host computers;
assist developers in analyzing system-related problems on host
computers; assist in the design and implementation of data base schema
and architectures; evaluate and support the movement to alternate
DBMS's; and develop external electronics connectivity with other data
bases for analysis support.

1.2 LABORATORY/FACILITY SUPPORT SERVICES - N/A

\*\*\*FOR every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

1.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements.

Provide preventive maintenance through periodic testing, adjusting,
cleaning, lubricating, and replacing of parts for all equipment to
insure proper and continued operation. Perform remedial maintenance to
restore failed equipment to its proper operating condition. Remedial
maintenance includes the requirement to perform, upon request from the
government, capital type rehabilitation on or the replacement of
equipment or systems which cannot be physically repaired or for which
continued routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

1.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

2\. BIOMEDICAL HARDWARE DEVELOPMENT AND ENGINEERING

\*\*\*From Schedule A, 10.0, LSPD:

2.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

2.1.1 Program Management Support

**2.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program. The following are
representative tasks the contractor shall perform:

**2.1.1.1.1 Science Operations Support** - Provide mission support to
operations personnel in terms of payload mission management, flight and
ground protocol development, on-orbit and pre- and post-flight
operations support, and post-flight data reduction support.

**2.1.1.1.2 Science Missions Support** - Provide engineering support to
ensure that mission objectives are carried out consistent with vehicle
capabilities and applicable NASA policies.

**2.1.1.1.3 Project Engineering Support** - Support engineering
hardware/software development. Prepare concept drawings; detailed
engineering and fabrication drawings; engineering studies including
trades-off; evaluations, layouts, cost and schedule analyses;
coordination and interface definition for proper integration into the
space program; structural analysis; dynamic analysis; weight and
center-of-gravity analysis; thermal analysis; consider applicable
elements of Safety, Reliability and Quality Assurance; and manual and
computer aided generation of engineering drawings.

**2.1.1.2 Studies and Assessments** - The following are representative
tasks the contractor shall perform:

**2.1.1.2.1 Programs Office Support** - Conduct advanced concepts
studies; determine technical cost and schedule feasibility; conduct risk
assessments; produce project plans; and plan operations and operations
support scenarios for Space Shuttle Program, space station, and other
HLS specified experiment programs.

2.1.1.3 Project Support

\*\*\*From Schedule B, Part 1, 2.2.3 Schedule Mgt; to be condensed to
schedule & Tracking tasks and combined with (old) Schedule B 2.1, para.
3:

**2.1.1.3.1 Schedule Management** - The contractor shall develop and
maintain a project status tracking and forecasting system which shall
include but not necessarily be limited to:

-   Review, analysis, and preparation of project-level interactive
    master schedules to assure timeliness of support to the project,
    identifying interface requirements, milestones, man-hour
    limitations, potential problem areas, resource conflicts, etc.

-   Review overall impact of schedule changes

-   Provide planning coordination with other organizations

-   Standardization and rapid dissemination of schedule information

-   Routine review and assessment of individual task schedules for
    compliance with master schedule milestones and to assess the impact
    of problems with specific recommendations to correct or minimize
    these problems

-   Rapid update capabilities

-   Accurate visibility to appropriate subtask element

    \*\*\*From Schedule B, Part 1, 2.1 Projects Planning & Requirements,
    Paragraph 3, edited to include Scheduling and Tracking only:

    **2.1.1.3.1.1 Human Life Sciences Project Management Plan -** The
    contractor shall write and maintain a Human Life Sciences Project
    Management Plan (HLSPMP). This document shall describe the
    contractors organization and management approach for support of HLS
    in the scheduling and tracking of life sciences payloads.

    2.1.1.3.2 Performance Management

    \*\*\*From Schedule B, Part 1, 2.2 Project Control, paragraph 3:

    **2.1.1.3.2.1 Project Reviews** - In contract progress reviews, the
    contractor shall report on progress since the last review, program
    status, ongoing and planned activities, milestone schedules, and
    technical cost status relative to plan. The contractor shall
    identify problems and suggest resolutions. Scientific, engineering,
    technical, and management activities shall be presented in the
    format defined in task orders or other implementing.

    \*\*\*From Schedule B, Part 1, 2.2.4 Project Control System
    Development & Analysis; last 2 sentences \[combine with (old)
    Sch. B, P1, 2.3.1\]:

    The contractor shall recommend system improvements based on
    experience gained, improvements in technology, or other factors.

    The contractor shall develop, publish, and distribute monthly
    Project Management Report.

    \*\*\*From Schedule B, Part 1 2.2.1 Performance Mgt & Admin;
    sentences 3,4,5 to NEW SOW Part I, Section 2:

    **2.1.1.3.2.2 Task Order Reviews** - The contractor shall provide a
    monthly report for individual task orders to each NASA task order
    manager. This report shall identify all problems and recommend
    solutions. Effective management is required to assure that all
    program requirements are met on time and within budget.

    \*\*\*From Schedule B, Part 1, 2.2.6

    **2.1.1.3.2.3 Advanced Planning** - The contractor shall perform
    advanced planning, including the optimization of multi-project
    scheduling and the assessment of the feasibility of future projects.
    Advanced planning shall include the evaluation of schedules of HLS
    activities at other locations, such as at the Kennedy Space Center
    (KSC) or Marshall Space Flight Center (MSFC), to optimize HLS
    capabilities. Advanced planning shall also investigate methods for
    improvement in and/or automation of such functions as documentation,
    configuration control, inventory management, technologies to allow
    investigators to access test and flight experiment data from remote
    sites, and project operations. Advanced planning shall propose and
    make recommendations for future projects and methods of
    implementation.

    \*\*\*From Schedule B, Part 1, 2.3.1 Config. Mgt & Control:

    **2.1.1.3.3 Configuration Management and Control** - Configuration
    management shall be directed by the HLS Configuration Control Board
    (CCB). The contractor shall maintain the HLS configuration
    management system and shall maintain all configuration control data.

    a\. The contractor shall prepare, coordinate, and maintain the HLS
    configuration management plan. The contractor shall develop and
    modify operating procedures to improve the configuration management
    system as required.

    b\. The contractor shall maintain HLS baseline documentation
    including, but not limited to, the Johnson Space Center (JSC)
    payload project mission specific manifest.

    c\. The contractor shall prepare agendas for the CCB. The contractor
    shall record configuration control board directives (CCBDs) and
    shall collect approval signatures for CCB actions.

    d\. The contractor shall be responsible for the coordination of
    change requests (CR's) from HLS project management and technical
    monitors (TMs), other NASA Centers, and inter-Center panels. The
    contractor shall be responsible for the preparation of requests for
    engineering change proposals as required. The contractor shall
    review change proposals for completeness, requested approval dates,
    and internal Center effect. The contractor shall distribute change
    proposals to affected offices and establish schedule dates for
    review inputs. The contractor shall be responsible for maintaining
    the status of change proposals after distribution and prepare CCBD
    transmittal letters for signatures.

    e\. The contractor shall be responsible for maintaining a change
    file to include copies of CCB changes, together with revisions,
    CCBDs, review comments, and synopses. The contractor shall be
    responsible for the preparation and maintenance of change proposal
    logs that indicate the status and history of changes from receipt
    through disposition and contractor notification.

    f\. The contractor shall be responsible for furnishing configuration
    information to HLS in support of design and program reviews. The
    contractor shall be responsible for managerially and technically
    participating in the configuration management aspect of these design
    and program reviews.

    \*\*\*From Schedule B, Part 1, 2.3.2 Information Management:

    **2.1.1.3.4 Information Management -** The contractor shall develop
    an information management plan (IMP) which will identify the
    documentation requirements that define, manage, and support life
    sciences payloads. The IMP shall include a summary which identifies
    HLS documentation requirements and their relationship to each other
    and to the program.

    The contractor shall review existing and new JSC and NASA management
    instructions as well as flight and ground support equipment (GSE)
    hardware design requirements. The contractor shall advise HLS and
    contractor engineering and management personnel on these
    requirements.

    The contractor shall establish, operate, and maintain a
    documentation control system which identifies, controls, prepares,
    reproduces, stores, and distributes HLS documents. The contractor
    shall be responsible for preparing, reproducing, storing,
    cataloging, and distributing all HLS experiment related scientific,
    engineering; technical, management, program administration, and
    other documentation which may be assigned to the contractor.
    Documentation responsibilities shall include providing technical
    writing and editing capability.

    The contractor shall prepare, maintain, and submit
    management/project review materials; identify, track, and control
    action items; and establish, operate, and maintain a program
    information file.

    \*\*\*From Schedule B, Part 1, 2.3.3 Logistics Management:

    **2.1.1.3.5 Logistics Management** - As part of its HLSPMP, the
    contractor shall prepare a logistics plan that indicates how it will
    develop and use a logistics system in support of HLS activities.

    The contractor shall implement the logistics plan in accordance with
    NASA standards and other applicable documentation.

    The contractor shall develop, operate, and maintain the HLS
    logistics system. The contractor's logistics plan shall describe Its
    logistics support to all on-site/off-site and remote locations,
    e.g., launch/landing sites and crew training sites. The plan shall
    define logistics procedures for HLS furnished equipment and shall
    provide guidelines for preparing and shipping hardware to and from
    the launch site or other locations as required.

    The contractor shall maintain records for equipment items shipped to
    other geographic locations.

    The contractor shall be responsible for operating and maintaining a
    logistics system including a material control station, a receiving
    and shipping area, and methods for control of all capital and
    sensitive equipment.

    The contractor shall record all receipts and issuances of stock and
    shall operate and maintain a material control station that maintains
    the predetermined minimum/maximum stores as defined in sec­\
    tion 2.1.3.1.2, Logistics.

    The contractor shall maintain all equipment/instrumentation
    calibration records and shall coordinate calibration maintenance
    with the JSC metrology laboratory

    The contractor shall develop, manage, and operate an inventory
    control system for HLS equipment in accordance with approved
    standards for Government property. The contractor shall be
    responsible for serving as property custodian of Government property
    assigned to the contractor for use in support of the SPDEO contract
    and shall follow established procedures for controlling, managing,
    and accounting for Government property.

    **2.1.1.3.6 Documentation**

    \*\*\*From Schedule B, Part 1, 2.3.6

    **2.1.1.3.6.1 Project Documentation, Management Information, and
    Presentations** - The data requirements list and data requirements
    description of this contract include only a small part of the total
    documentation requirements. A more complete description of
    documentation and contents will be found in documentation as defined
    by implementing task orders or other enabling documentation and in
    other sections of this SOW.

    The contractor shall make timely responses to requests for
    briefings, presentations, and status reviews.

    The contractor shall prepare presentation material and shall
    maintain a simple and accessible system of filing this material.

    \*\*\*From Schedule B, Part 1, 2.3.7.2 Special Projects:

    **2.1.1.3.6.2 Special Projects** - The contractor shall develop and
    maintain all documents related to the HLS mission and the LSFEP as
    defined in section 2.1.1.3.4 and shall prepare, publish, and
    distribute information booklets on HLS missions, experiments,
    hardware, and facilities; shall prepare graphics displays as
    required; shall coordinate the preparation, review, approval,
    revision, and distribution of the HLS Standard Operating Procedures
    (SOPs) Manual (HLS-1 0003).

    \*\*\*From Schedule B, Part 1, 2.3.8 Reqt. Mgt; para. 1:

    **2.1.1.3.6.3 Requirements Management** - The contractor shall
    develop and implement a plan for assuring the compliance of HLS
    flight equipment to level 1 through level 3 requirements including
    safety requirements and design standards. This shall include the
    necessary expertise to assess these requirements against flight
    equipment design requirements and design reviews for HLS flight
    equipment, whether being delivered by the contractor, experiment
    principal investigator (PI), or other NASA contractor.

    2.1.2 Research and Development

    2.1.2.1 Experiment Systems Hardware

    \*\*\*From Schedule B, Part 1, 3.2.3.6:

    **2.1.2.1.1 Experiment Systems Hardware Development -** EEs shall
    support the development of experiment systems/hardware including but
    not limited to:

    a\. Developing hardware designs and review for performance,
    scientific/mission compatibility, and adherence to safety and
    reliability requirements of HLS flight hardware/software

    b\. Preparing for and conducting experiment/hardware design reviews

    c\. Proposing and evaluating design changes to meet experiment
    objectives and maintain vehicle compatibility

    d\. Participating in acceptance testing of delivered flight
    hardware/software and experiment systems

    e\. Performing system studies and analyses to determine experiment
    compliance with performance and compatibility objectives

    f\. Developing data display requirements for preflight testing and
    mission support

    \*\*\*From Schedule B, Part 1, 3.2.3.7:

    **2.1.2.1.2 Experiment Hardware Configuration Control** - EEs shall
    perform tasks associated with configuration control of flight
    experiments hardware/soft ware, including but not limited to:

    a\. Updating experiment hardware drawings to reflect all CCB
    approved changes and to agree with the "as built" hardware

    b\. Preparing documentation required to support CCB CR's and
    documenting approved CCB changes to experiment hardware

    c\. Assuring that no changes-are made to expert hardware without
    proper CCB action and approval

    d\. Making recommendations to the EST concerning changes to
    experiment hardware and the advantages and/or disadvantages of
    proposed changes

    e\. Providing estimates of the time and materials costs involved in
    implementing proposed changes to experiment hardware

    \*\*\*From Schedule B, Part 1, 3.2.3.8:

    **2.1.2.1.3 Experiment Hardware/Software Integration and
    Maintenance** - EEs shall perform and support:

    a\. Integrated systems bench tests

    b\. Integrated systems mockup tests

    c\. Science verification tests

    d\. Mission integrated tests

    e\. Joint integrated tests

    f\. Mission sequence tests

    g\. Special required hardware/software tests

    h\. Review of mission level documentation

    \*\*\*From Schedule B, Part 1, 3.2.2.6 Experiment Coordination:

    **2.1.2.1.4 Experiment Coordination** - EMs shall be responsible for
    managing, performing, and coordinating all experiment activities,
    including, but not limited to:

    a\. PI interfaces

    b\. Hardware shipment to vendors, KSC, or other required locations

    c\. Product development and/or modification

    d\. Surveys of state-of-the-art biomedical measurement concepts and
    make recommendations thereon

    e\. Recent developments through publications, meetings, symposia,
    and by contacting technical experts in the field

    f\. Periodic status to NASA HLS on all experiment activities

    \*\*\*From Schedule B, Part 1, 4.0:

    **2.1.2.2 Flight Hardware/Software Engineering and Provisioning** -
    The contractor shall define, design, fabricate, test, integrate, and
    maintain HLS flight and GSE systems. These systems include
    experiment systems (e.g., LSLE, EUE, and GSE) and integration
    hardware, including mounting slides and stowage containers. In the
    content of this SOW, reference to "hardware" implies the inclusion
    of related software.

    \*\*\*From Schedule B, Part 1, 4.1 Systems Engineering:

    **2.1.2.2.1 Systems Engineering** - The contractor shall provide
    systems engineering for life sciences flight experiments. For HLS
    experiments, the contractor shall design experiment systems that
    integrate certified components from various-sources (e.g., cables,
    brackets, switch panels, flight instruments, etc.) to form a
    flight-certified system.

    \*\*\*From Schedule B, Part 1, 4.2 Project Engineering Support:

    **2.1.2.3 Project Engineering Support** - The contractor shall
    provide project engineering and management for all HLS flight and
    ground hardware, including hardware definition, hardware development
    and modification (where required), and maintenance.

    Project engineers (PEs) shall provide design assistance HLS and
    furnish technical information to other contractors or PIs. The PEs
    shall assure that all experiment requirements are met and that all
    hardware meets program guidelines.

    PEs shall monitor the development and fabrication of flight hardware
    for technical compliance and shall make recommendations thereon.
    Specifically, the contractor shall:

    a\. Review documentation prepared by hardware/experiment developers
    and make recommendations.

    b\. Review EISs and other documents for compatibility with program
    requirements.

    c\. Perform or provide technical assistance to all experiment
    reviews; review and analyze contractor documents, schedules, and
    hardware.

    d\. Perform reviews of experiment interface documentation and
    provide recommendations.

    e\. Troubleshoot and resolve experiment hardware problems, failures,
    etc.

    PEs shall prepare and support the preparation of all necessary
    documents including the following:

    a\. Technical reports, as required

    b\. Activity reports

    c\. Project activity and milestone schedules

    d\. Hardware development plans (HDPs)

    e\. Statements of work for hardware development or modification

    During hardware development, contractor PEs assigned to HLS flight
    hardware shall:

-   Review proposed designs for ability to meet performance, scientific,
    compatibility, safety, reliability, quality, and other requirements
    of HLS flight hardware.

-   Provide technical data and information to hardware

-   developers and potential users.

-   Assess technical progress; assure that the delivered hardware works;
    is on time and within budget; take corrective actions required.

-   Propose/evaluate design changes and review delivered documents, make
    recommendations and assure that all program requirements are met.

-   Prepare and perform hardware design reviews and assure that review
    preparation is adequate.

-   Assure that instrument interfaces are correct and clearly defined.

-   Present proposed changes to the baseline configuration to the HLS
    CCB.

-   Participate in acceptance/functional testing of flight hardware and
    experiment systems.

-   Perform analyses and tests to assure that hardware meets
    design/interface requirements and all performance objectives.

    Following delivery, contractor PEs assigned to HLS flight hardware
    shall :

-   Provide technical data and engineering support to any experiment
    that will use the instrument, support EMs in system design and in
    preparing ICDs.

-   Assure timely close-out of all open paperwork.

-   Plan, write procedures for, conduct, and document frequent
    functional tests to assure that the hardware continues to perform.

-   Support crew training and hardware refurbishment.

    \*\*\*From Schedule B, Part 1, 4.2.2:

    **2.1.2.3.1 Hardware Development Plans -** The contractor shall
    prepare HOPs for all new flight hardware. The HOP is used to assess
    the advisability of proceeding with development and to determine the
    method of acquisition. The plans shall include, but are not limited
    to:

-   Item description/general specifications

-   Justification for the item

-   Results of evaluation tests/analyses

-   Development approach recommendations

```{=html}
<!-- -->
```
-   Modify or new build

-   Method of acquisition

-   Quantities and uses

```{=html}
<!-- -->
```
-   Interfaces and mission resource requirements

-   Budget estimate

-   Proposed schedule

    \*\*\*From Schedule B, Part 1, 4.2.3:

    **2.1.2.3.2 Hardware Specification Development -** The contractor
    shall develop specifications (e.g., EISs; Specification/Assembly
    Drawings \[S/ADs\]) for flight hardware. A specification typically
    includes, but is not limited to:

-   Introduction

-   Applicable documents

-   Hardware requirements

```{=html}
<!-- -->
```
-   Performance requirements

-   Technical requirements

-   Safety requirements

-   Reliability requirements

-   Quality assurance requirements

-   Materials requirements

-   Configuration management requirements

```{=html}
<!-- -->
```
-   Documentation requirements

    \*\*\*From Schedule B, Part 1, 4.3.1:

    **2.1.2.3.3 HLS Refrigerator/Freezer (R/F) Development** - A new
    LSLE R/F and an improved R/F based on the current system are major
    hardware developments that the contractor shall perform.
    Additionally, consistent with its LSLE support and maintenance role,
    the contractor shall provide Orbiter refrigerator/freezers (OR/Fs),
    LSLE R/Fs, and spare parts to HLS for all missions and shall perform
    pre- and postflight analyses, tests, and refurbishment on each
    flight unit.

    \*\*\*From Schedule B, Part 1, 4.3.1.1:

    **2.1.2.3.3.1 HLS Refrigerator/Freezer Improvements** - The
    contractor shall make a continuing effort to improve the reliability
    and performance of the current LSLE Spacelab R/F and OR/F. The
    contractor shall perform all necessary design, analyses,
    modifications, and testing to meet the technical, reliability,
    quality, safety, and operational requirements in the R/F S/AD
    (LS-30063) and in the OR/F S/AD (LS-30065).

    The contractor shall implement improvements to the OR/Fs and LSLE
    R/F identified in the aforementioned documents and shall perform
    reliability and failure analyses to verify performance and identify
    additional weaknesses. Where possible, the contractor shall
    suggest/implement other improvements.

    \*\*\*From Schedule B, Part 1, 4.3.1.2:

    **2.1.2.3.3.2 Development of Second Generation Life Sciences
    Refrigerator/Freezers** - The contractor shall assess requirements,
    formulate specifications, and investigate approaches for a second
    generation of R/Fs to alleviate the weaknesses in the present units.

    Areas to be investigated include, but are not limited to the
    evaluation of new compressor, condenser, and evaporator designs and
    the evaluation of work on R/Fs for space station. The contractors
    activities should address potential uses in the Spacelab; Orbiter,
    and space station.

    The contractor shall provide an engineering prototype (including
    test beds for compressors and other subassemblies) with a means of
    efficiently collecting and quickly analyzing data collected from the
    engineering prototype.

    \*\*\*From Schedule B, Part 1, 4.3.2:

    **2.1.2.3.4 In-House Flight Equipment Design** - As required,
    whether as a result of modifications to the existing flight
    equipment inventory, "in-house" modifications to off-the-shelf
    commercial equipment, or development of items of electrical or
    mechanical flight equipment, the contractor shall have the resources
    for implementing the design requirements to accomplish necessary
    tasks. These resources as a minimum shall include mechanical and
    electrical design analyses, human engineering as reflected in the
    requirements for manned space flight, thermal analyses, and other
    design standards imposed on the development of HLS flight hardware.
    The contractor may implement designs utilizing both contractor and
    NASA facilities for design and testing efforts. The JSC engineering
    drawing control and tracking system will, where practical, be
    utilized in the implementation of these designs. Requirements for
    delivery of this redesigned or new flight equipment to HLS are the
    same as imposed on other flight equipment development, including
    design and ARs, acceptance/certification testing, and flight
    verification and certification.

    \*\*\*From Schedule B, Part 1, 4.4:

    **2.1.2.3.5 Sustaining Engineering Support** - The contractor shall
    provide sustaining engineering support to HLS flight and ground
    hardware, including troubleshooting and repair during preflight and
    postflight integration and testing

    \*\*\*From Schedule B, Part 1, 4.4.1:

    **2.1.2.3.5.1 Flight Data Systems** - The contractor shall program
    flight data systems for HLS experiments and shall perform hardware
    and software testing, maintenance, and operation of flight data
    systems. The contractor shall document and verify the interfaces
    between flight data systems and the vehicle.

    \*\*\*From Schedule B, Part 1, 4.4.3:

    **2.1.2.3.5.1.1 Flight Data Systems Interface** - The contractor
    shall document the interface between experiment and vehicle data
    systems and shall verify that all electrical, mechanical, and data
    format requirements are met.

    \*\*\*From Schedule B, Part 1, 4.9 Integration HW Dev:

    **2.1.2.4 Integration Hardware Development** - Integration hardware
    development for life sciences flight experiments shall include
    mechanical hardware, data cables, power cables, video signal
    interfaces, flight vehicle cooling system to experiment interface
    hardware, interfaces to the flight vehicle vacuum system, and any
    other hardware that is required to meet the experiment operational
    requirements through the use of vehicle subsystems.

    The contractor shall be responsible for reviewing the experiments
    selected by NASA for each payload and developing an installation
    design for each item that identifies all the flight vehicle
    interfaces. Those interfaces that are the responsibility of HLS will
    be identified in agreements with the PMM. It will then be the
    responsibility of the contractor to provide experienced mechanical
    and electrical engineering personnel to develop detailed fabrication
    drawings for the necessary integration hardware identified in the
    installation designs. Existing inventories of integration hardware
    will be used where practical. The contractor shall also be
    responsible for the procurement and fabrication of new or additional
    hardware items.

    **2.1.2.4.1 Integration Hardware Requirements Definition** - Once
    the contractor has evaluated the experiment to vehicle interfaces,
    they shall develop mechanical installation drawings for each
    experiment hardware installation into the flight vehicle. This
    requirements definition will include the evaluation of the method of
    experiment installation, such as deciding to mount an experiment
    item to the rack by front panel support only or to utilize equipment
    slides for additional support. Development of the mechanical
    installation drawings should result in the identification of any
    interference problems between the experiment and the flight vehicle
    structures and the subsequent resolution of those interference
    problems. The mechanical installation drawings shall become the
    basis for an Integration Hardware List (IHL) for each payload. This
    IHL shall identify all mechanical hardware required to install the
    experiment into the flight vehicle. This includes all adapter
    plates, fittings, shims, slides, ECS connections, nuts, bolts,
    washers, and any other fabricated or provided hardware necessary to
    make complete installation into the flight vehicle. The IHL shall be
    maintained current as the installation designs evolve. This list
    will be maintained in an easily accessible automated format.

    The contractor shall be responsible for evaluating the experiment
    data, power, and video interfaces and shall develop a block diagram
    of the HLS payload cabling requirements to use as a basis for
    harness design. The block diagram will be reviewed with HLS for
    initial approval. The contractor will subsequently proceed with the
    generation of cable fabrication drawings.

    Special integration hardware requirements that are identified during
    the RR will become the responsibility of the contractor. The types
    of special hardware are items such as interfaces to the flight
    vehicle vacuum system, special air ducting for cabin air usage
    instead of ECS cooling air, or special clamps to support experiment
    hardware during the mission.

    **2.1.2.4.2 Hardware Design Engineering and Development** - As a
    result of the integration hardware requirements definition, the
    contractor shall be responsible for generating mechanical drawings
    for the fabrication of any integration hardware required to support
    a payload. Where appropriate, these parts will be analyzed for their
    structural integrity in their specific applications. Stress analyses
    will be formally documented as appropriate. Hardware design work
    will be performed. The contractor shall be responsible for the
    fabrication of the new integration hardware through either JSC
    Technical Services or a commercial fabricator that is experienced in
    the manufacturing of flight hardware. Depending upon the complexity
    of the mechanical system, the contractor will be required to defend
    his design in various design reviews.

    The contractor will be responsible for the completion of cable
    fabrication drawings for all the data, power, and video interfaces
    that are the responsibility of HLS. The cable design and the
    fabrication drawings will be based on the "Life Sciences Flight
    Cable Fabrication Practices and Specifications", LS-60035. The cable
    designs will also utilize the "Standard Connector Inventory" that
    has been established within HLS to the maximum degree practical. The
    contractor will be responsible for determining the length and
    routing of all cables. The contractor will subsequently be
    responsible for the material-procurement and the fabrication of the
    flight cables.

    **2.1.2.4.3 Hardware Inventory Control** - The contractor shall be
    responsible for the assignment of existing integration hardware to
    support new payloads. As the IHL for each new payload is developed,
    the contractor will review the available uncommitted integration
    hardware and the new integration hardware requirements. From this
    review, a listing of new or additional quantities of integration
    hardware will be generated. All items that are either not presently
    available or not available in sufficient quantities will be procured
    by the contractor to, through commercial suppliers or fabricated.
    The contractor will maintain a system which tracks the available
    reusable and expendable integration hardware. This system shall be
    maintained current and will indicate the allocations of reusable
    hardware for each payload and shall be adequate to assure that the
    expendable hardware is available in sufficient quantities to support
    all the active payloads.

    The contractor shall be responsible for the maintenance of a
    standard set of flight and non-flight data and power connectors as
    required. This standard connector list will be the basis for
    connector selection for the fabrication of the flight cables as well
    as providing a source of data and power receptacles for use by the
    experiment hardware developers to assure standardization and
    compatibility. A supply of acceptable single conductor wire and
    impedance controlled cable will be maintained by the contractor to
    support HLS and experiment cable and experiment fabrication. The
    listing/inventory of connector, wire, and cable item will be kept
    current own automated system.

    Automated systems are already in use within HLS to track the
    integration hardware and electrical components mentioned above. The
    contractor shall use these existing automated systems to the maximum
    extent possible for cost effectiveness.

    \*\*\*From Schedule B, Part 1, 4.10 Stowage Management:

    **2.1.2.5 Stowage Management** - The contractor shall be responsible
    for managing the stowage requirements of all experiments. The
    contractor shall review the loose equipment that is identified by
    the experimenter which will require stowage for launch and, while
    considering the order of usage and the crew accessibility needs,
    will develop a stowage configuration that proposes the specific
    locations of all loose equipment. This configuration will be
    documented with layout drawings and a stowage list. This stowage
    document will require many updates and revisions as the experiments
    mature. The stowage requirements must be satisfied within the
    constraints of the available space allocation that has been provided
    to HLS on each payload. The contractor personnel responsible for
    stowage requirements must coordinate with the HLS and contractor
    personnel to assure that the optimum stowage container or stowage
    drawer configuration is utilized.

    As the stowage layout is finalized, the contractor will be
    responsible for the coordination of the development of drawings that
    show the positioning of the hardware in the stowage foam. The
    contractor will also be responsible for the coordination and
    scheduling of the cutting of the flight and training foam cushions.
    If required, the contractor will be responsible for developing a
    mechanism for having the cutting of the foam cushions accomplished
    by other NASA/contractor organizations.

    \*\*\*From Schedule B, Part 1, 11.0 Advanced Technology Development,
    edited to include Human Research Facility:

    **2.1.2.6 Human Research Facility (HRF) and Advanced Technology
    Development (ATD)** - The contractor shall be responsible for the
    HRF and ATD activity, which is an advanced planning and development
    process that identifies and evaluates new technology tray be used in
    future flight or ground systems. This process is directed by the ATD
    project review board (PRB), which is composed of the HLS chief and
    the branch chiefs. Project proposals are submitted to the PRB for
    review and allocation of resources. ATD project teams shall perform
    the following type of activities:

-   Technology surveys

-   Trade studies

-   Procurement

-   Prototype design

-   Rapid prototyping

-   Prototype evaluation

-   Prototype documentation package development

    **2.1.2.6.1 Advanced Technology Development Project Review Board
    Activities** - The ATD PRB meets monthly to review project proposals
    and status. The contractor shall be responsible for supporting these
    reviews as follows:

    Administrative

-   Receive and organize project proposals

-   Publish and circulate PRB agenda

-   Provide secretary and record minutes of the PRB

-   Circulate minutes of the PRB and track action items, project
    budgets, and schedules

    Technical

-   Status reviews and project proposal presentations

    **2.1.2.6.2 Advanced Technology Development Project Teams** -
    Engineering, technician, and administrative support for ATD projects
    will be determined by the ATD PRB. The contractor shall have the
    following responsibilities:

-   Technology Survey

```{=html}
<!-- -->
```
-   Review technical literature and commercial manufacturers to
    determine the current state of the art for the technology being
    evaluated.

-   Contact the technical experts and get status updates on the
    technology.

```{=html}
<!-- -->
```
-   Trade Survey

```{=html}
<!-- -->
```
-   Establish evaluation criteria for the technology based on HLS
    requirements.

-   Evaluate technology options against these criteria.

```{=html}
<!-- -->
```
-   Hardware/Software (System) Procurement

```{=html}
<!-- -->
```
-   Procure commercial off-the-shelf (COTS) equipment (if available) or
    developmental prototypes, including software (if required), to use
    in characterization of the technology.

```{=html}
<!-- -->
```
-   System Modification Rapid Prototyping

```{=html}
<!-- -->
```
-   Modify COTS system to meet HLS requirements and prototype a HLS
    configured system for evaluation and characterization testing.

```{=html}
<!-- -->
```
-   Prototype Evaluation

```{=html}
<!-- -->
```
-   Test the prototype to determine the performance characteristics of
    the chosen technology.

```{=html}
<!-- -->
```
-   Document Prototype

```{=html}
<!-- -->
```
-   Produce design documentation (schematics, mechanical drawings,
    assembly drawings, software listings, flow charts, operators
    manuals, technical manuals, etc.) for the prototype system.

-   Itemize hardware and labor costs required for development of the
    prototype system.

-   Document the schedule used to develop the prototype.

-   Publish the performance specifications for the prototype.

### 2.1.3 Engineering, Scientific, and Analytical Tools {#engineering-scientific-and-analytical-tools .unnumbered}

\*\*\*From Schedule B, Part 1, 4.5:

**2.1.3.1 Flight Equipment Inventory/Maintenance** - The contractor
shall maintain all HLS flight equipment, including associated GSE. The
contractor shall refurbish, replenish, repair, and rectify the inventory
for flight. A representative list of current LSLE is contained in the
LSLE catalog (LS‑3001 3‑J).

The contractor shall provide :

-   Controlled storage and handling

-   Shipping and receiving

-   Cleanliness control

-   Retesting, including environmental retesting

-   Materials control

-   Quality assurance

-   Ground and flight safety

-   Planning, scheduling, and tracking of end items

-   Consumables management

-   Spares

-   Providing and maintaining documentation, including:

```{=html}
<!-- -->
```
-   Hardware data packs

-   Operating, maintenance, and handling procedures

-   Engineering drawings

-   User handbooks

-   Periodic updates of the LSLE catalog

-   Acceptance and functional test procedures

    **2.1.3.1.1 Preventive Maintenance** - The contractor shall
    establish and maintain a schedule-based preventive maintenance
    program. Before and after each mission, the contractor shall
    refurbish and perform complete functional tests on appropriate HLS
    hardware to assure mission performance and determine causes of
    failures.

    Where appropriate, the contractor shall place and manage vendor
    subcontracts (with the original equipment developer or with other
    qualified vendors) for the repair/modification/maintenance of flight
    equipment.

    The contractor shall maintain all batteries for HLS hardware. The
    contractor shall assemble battery packs, dispose of used batteries,
    and write battery preparation/test/use procedures.

    **2.1.3.1.2 Logistics** - The contractor shall establish and
    maintain a logistics activity that reorders expendable items/spares
    when established minimums are reached. For example, the contractor
    shall maintain and resupply the inflight blood collection system
    (IBCS), assuring that all items are within shelf-life and meet
    mission requirements. The contractor shall also maintain vendor
    listings for all IBCS components.

    **2.1.3.1.3 LSLE Usage Schedule/Mission-Commitment Data** - The
    contractor shall maintain LSLE usage schedule/mission-commitment
    data. As each new experiment/payload is defined, the contractor
    shall review the hardware list against the current mission
    commitment schedule and shall identify unavailable items. The
    contractor shall continually update the data and shall track the
    usage, availability, and location of each inventory item by part
    number, serial number, and mission. This data shall be accessible to
    HLS through the current computer network.

    \*\*\*From Schedule B, Part 1, 4.6:

    **2.1.3.2 LSLE Modernization** - The contractor shall review all
    LSLE and EUE items and identify those whose supporting technology
    has sufficiently improved to warrant upgrade or modernization. The
    contractor shall recommend science and technology improvements to
    LSLE for future missions and programs.

    **2.1.3.2.1 Trade-Off Analysis** - This contractor shall implement a
    LSLE hardware modernization program. This program will support
    future POP exercises. The contractor shall report on all areas
    required to begin developments in a detailed LSLE modernization
    plan. The contractor shall:

    a\. Review existing waivers and material usage agreements.

    b\. Review EUE hardware specifications and determine modernization
    strategies and when to upgrade LSLE.

    c\. Perform technology assessments to identify project technologies.

    d\. Analyze available technology and assess applicability to the
    LSLE cadre of flight hardware.

    e\. Recommend candidate LSLE hardware prototypes for modernization.

    **2.1.3.2.2 LSLE Modernization Implementation Plan** - The
    contractor shall develop an implementation plan for LSLE
    modernization. The plan shall include:

    a\. Schedule and major milestones for prototype development and LSLE
    upgrade.

    b\. Resource requirements, labor, materials, and facilities.

    c\. Recommendation on prototype development approaches, i.e.,
    outside vendors, subcontracts, or contractor build.

    **2.1.3.2.3 LSLE Modernization Cost Estimate** - This contractor
    shall provide detailed cost estimates which will include:

    a\. Identification of future LSLE modernization activities

    b\. Resource requirement or these activities

    c\. Specific hardware modifications

    \*\*\*From Schedule B, Part 1, 4.11 Eng. Design & Drafting:

    **2.1.3.3 Engineering Design and Drafting** - The contractor shall
    provide experienced management and technical personnel to perform
    the function of engineering design and drafting that is required for
    the development of flight hardware and ground support systems within
    HLS. The design and drafting shall include, but not limited to
    mechanical components, printed circuit boards, experiment
    installation drawings, electrical cable drawings, soft component
    drawings, electrical interface control drawings, and mechanical
    interface control drawings. The contractor shall be capable of
    performing all of the new hardware design and drafting utilizing
    automated drafting systems. Current HLS drawings exist as hand drawn
    drawings, vendor drawings, and CAD generated drawings and the
    contractor must be proficient in the handling of all these drawings.
    The existing CAD drawings and models for HLS hardware exist in CALMA
    design drafting manufactory, International Business Machines
    Computer Aided Engineering Design System, and AutoCad formats. The
    contractor must be able to continue the development of drawings and
    models that have been started under these formats as well as provide
    modifications to drawings produced under these formats. The
    contractor shall be required to produce all drawings in accordance
    with JSCM 8500, Engineering Drawing System Manual. The contractor
    shall provide the administrative structure for the efficient and
    effective management of the required design and drawing tasks,
    including utilization of experienced designers and support
    draftsmen, support by stress analysis personnel, and coordination of
    priority conflicts.

    \*\*\*From Schedule B, Part 1, 5.3:

    2.1.3.4 Experiment and Payload Testing, Simulation, Mission Support,
    and Training

    **2.1.3.4.1 Mission Support Preparation** - The contractor shall be
    responsible for configuration and/or reconfiguring HLS data systems
    hardware, software, and GSE and for developing, acquiring,
    implementing, testing, and validating all hardware, software, and
    GSE required to support experiment and payload testing of any type
    at JSC or remote locations, for supporting mission simulation and
    training exercises, and for providing mission support during
    missions on which life sciences experiments are flown. This activity
    shall include, but not be limited to, experiment and mission
    software development, modification, testing, validation, and
    computer and GSE hardware and software testing and validation.

    **2.1.3.4.2 Training** - The contractor shall be responsible for
    providing appropriate training for data systems and other personnel
    on the use of the hardware and/or software with which they will be
    working. This includes, but is not limited to, computer operating
    systems and network hardware and software training, and training of
    users in the operation of the real-time data acquisitions system,
    non-real-time software, and management software used to support
    LSFEP missions and activities.

    \*\*\*From Schedule B, Part 1, 5.4:

    **2.1.3.4.3 Attendance At Technical and Professional Conferences** -
    The contractor shall encourage personnel to publish the results of
    their work in appropriate professional journals and/or conferences
    except where the work may be proprietary or otherwise restricted.
    Such presentations, talks, and publications shall not include any
    data or information which is sensitive, has privacy act
    implications, or may involve national security.

    \*\*\*From Schedule B, Part 1, 5.5:

    **2.1.3.4.4 Technical Documentation** - The contractor shall be
    responsible for producing documentation which describes how
    software, hardware, technical procedures, and other processes and
    methods used in support of the LSFEP are designed, how they
    function, and how personnel may use these products and items. Such
    documentation shall consist of but not be limited to, RDs, design
    documents, implementation plans, user's guides, general
    documentation for public release, and proposals for new and upgraded
    equipment, methods, and procedures.

    All baselined software used to support a mission or other major
    activity shall be fully documented so that technical details of how
    a mission is to, be or was supported can be understood and used for
    future modification or other purposes such as supporting future
    related missions or analyzing data from previous missions.

    \*\*\*NOTE: Schedule B, Part 1, 5.6 and 5.7 went to NEW SOW Part II,
    Core Computer Support.

### 2.1.4 Studies and Assessments {#studies-and-assessments .unnumbered}

\*\*\*From Schedule B, Part 1, 4.1.1:

**2.1.4.1 Experiment System Engineering Studies** - The contractor shall
perform-experiment system engineering studies and analyses including:

a\. Performing analyses on systems, subsystems, and associated equipment
to identify and evaluate alternative configuration approaches.

b\. Performing feasibility and trade-off studies for new and/or revised
technical approaches to assure total system compatibility.

c\. Assessing technical impacts of proposed changes to experiment
systems, subsystems, and associated equipment.

d\. Providing recommendations for improvements in experiment hardware
and software.

e\. Supporting system level testing to identify problems and assist in
troubleshooting and correction of identified problems.

The results of these studies shall be presented to NASA in written
reports, oral presentations, and in the contractor's monthly progress
reports.

\*\*\*From Schedule B, Part 1, 4.1.2:

**2.1.4.2 Experiment System Interface Compatibility** - The contractor
shall assess and assure the compatibility of HLS experiment systems with
the vehicle and with mission resources.

\*\*\*From Schedule B, Part 1, 4.7:

**2.1.4.3 Payload Project Management** - For each set of experiments
assigned to a mission there will be a Payload Project Manager (PPM)
assigned to provide representation of HLS to the Payload Mission Manager
(PMM) during negotiations for vehicle requirements and documentation
submittal. The PPM is responsible for meeting the mission milestones and
developing the implementation plans for support of each mission. The PPM
is also responsible for resource allocations to each experiment and the
payload complement. The contractor will support the PPM as defined in
the following paragraphs.

\*\*\*From Schedule B, Part 1, 4.7.1:

**2.1.4.3.1 Payload Feasibility** - The contractor shall be responsible
for determining the feasibility of various project payload
configurations during the experiment selection process by NASA.
Contractor engineers shall be familiar with the experiment to vehicle
interface requirements and restrictions. This includes mechanical,
electrical, data, video, and thermal limitations of the vehicle. The
contractor will be provided a selection of potential experiments and
hardware for a payload under consideration. The contractor will
subsequently evaluate the reasonable configurations of the experiments
in the racks and report this information, together with the evaluation
of thermal and power resource distribution, to HLS with specific
recommendations.

In order to perform accurate feasibility payload studies with quick
response changes, the contractor shall be capable of performing these
studies using an existing three-dimensional computer-aided design
(CAD)/computer-aided engineering system.

\*\*\*From Schedule B, Part 1, 4.7.2:

**2.1.4.3.2 Support for Payload Project Management -** The contractor
will provide support to, and represent as requested, the JSC PPMs
assigned to payloads containing experiments developed and managed by the
HLS. The contractor will work with the PPMs to identify task required to
support mission milestones and distribute tasks and need dates to
contractor personnel supporting the mission. The contractor will track
the progress of the activities and provide the PPM with a current status
information. The contractor should also identify problem areas
associated with task completion and assist in the resolution of these
problems where appropriate.

\*\*\*From Schedule B, Part 1, 4.7.2.1:

**2.1.4.3.2.1 Inter-Organizational Liaison** - The contractor will
perform the necessary coordination to provide the PPMs with an
inter-organizational liaison to the contractor organization. The
contractor will collect and collate data required to support mission
milestones and requirements, identify and analyze the tasks needed to
obtain these data, and distribute this information to the
inter-organizational elements. This support will also include the
generation of schedules to support mission milestones and tasks and the
development and maintenance of status reports and task lists.

\*\*\*From Schedule B, Part 1, 4.7.2.2:

**2.1.4.3.2.2 Resource Allocation** - The contractor shall provide
engineering personnel to the PPM who will be responsible for the
accumulation of the payload project resource requirements from all HLS
experiment hardware that will be flown on each mission. The payload
resources that are to be documented, updated, and analyzed include
experiment power consumption, power profile de-experiment cooling
requirements, vacuum venting requirements, mass and center-of-gravity
data, stowage space needs, and crew timeline requirements. Maintenance
of these data in an automated format accessible to HLS and contractor
personnel is required.

\*\*\*From Schedule B, Part 1, 4.7.2.3:

**2.1.4.3.2.3 Payload Status** - Since the PPM is the interface for HLS
to the PMM, the status for all activities supporting a mission is
required by the PPM. The contractor will track the status of action
items and identified tasks, including the areas of verification
submittals, verification testing, safety hazard reports and closures,
certification testing, certification review sheet completion, materials
certification, waiver/deviation status, hardware shipments, and KSC
testing. This shall include a detailed status for all requirements
levied on each item of hardware to be flown on a mission.

\*\*\*From Schedule B, Part 1, 4.7.3:

**2.1.4.3.3 Project Payload Definition** - Once a set of experiments has
been selected by NASA as a result of the feasibility studies, the
contractor will start the process of defining the project payload in
terms of specific locations within the flight vehicle rack structures.
The contractor will also compile the best available set of resource
requirements from the experiment development teams. This will include
estimated power requirements, maximum weights and center-of-gravity
information, and unique interface needs. The information derived from
this payload definition effort will be provided to the HLS PPM as a
basis for development of payload configuration agreements between the
HLS PPM and the PMM. The contractor will be responsible for assisting
the HLS PPM in the negotiations of these agreements with the PMM.

\*\*\*From Schedule B, Part 1, 4.7.4:

**2.1.4.3.4 Mission Reviews and Presentations** - The contractor will
support PPM presentations and meetings by preparing presentation
material, presenting the material when required, and developing an
action item list/minutes for each review/meeting as appropriate. The
contractor will assure that the appropriate contractor personnel are
notified to support the necessary presentations and meetings. The
contractor will distribute information received at meetings and the
minutes of the meetings to contractor and HLS personnel.

\*\*\*From Schedule B, Part 1, 4.7.5:

**2.1.4.3.5 Mission Support to the Payload Project Manager** - The
contractor will man console positions in support of the PPMs during
mission level simulations and during flight. This includes obtaining the
appropriate training courses as required by the payload or mission
organizations.

\*\*\*NOTE : Schedule B, 4.1.4 NASA ALERTS - DELETED. See New SOW,
Section 15.5.

\*\*\*From Schedule B, Part 1, 4.7.7:

**2.1.4.3.6 Documentation Reviews** - During the development of a
payload complement to be flown, there are various organizations that
prepare documentation which includes experiment resources and
requirements applicable to the experiments developed by HLS. The
contractor will review these documents to assure that the experiment
requirements have been interpreted correctly by outside organizations.
Included are the following representative documents prepared by external
organizations: PIP Annexes, Ground Integration Requirements Document,
Operations and Maintenance Requirements and Specifications Document
(OMRSD), Test and Checkout Procedures and Operations and Maintenance
Instructions (OMI).

Preparation for experiments to be flown on space station will also
require contractor review of the implementation documentation prepared
by outside organizations.

The contractor will review this documentation and prepare
comments/recommendations to appropriate personnel.

\*\*\*From Schedule B, Part 1, 4.8 Systems Analysis:

**2.1.4.4 Systems Analysis** - The contractor shall be responsible for
the total systems analysis of the HLS portion of each experiment
payload. This analysis shall include structural and stress analysis of
all mechanical installations, the heat load distribution and rejection
through the carrier cooling systems, and shall develop the power
distribution logic that will assure a balanced power usage from the
carrier. Data interface requirements will be identified, electrical
interface documents created, and cable harness definition established.
Video interfaces will be evaluated for compatibility with the carrier
systems.

The contractor shall be responsible for all experiment, integration
hardware, and payload design reviews. A prime goal of HLS is to identify
design, operations, and integration problems during the design stages of
all systems and payloads rather than after start of fabrication. To
accomplish this goal, the contractor engineering personnel that support
the PDRs and CDRs should be highly skilled in the various technical
areas such as structures, thermal, electrical, data, and integration:

**2.1.4.4.1 Structural and Mechanical Analysis** - The contractor shall
be responsible for the evaluation of all mechanical installations in the
flight vehicle. Structural engineering personnel shall be provided that
are experienced in performing stress analysis of flight hardware. The
structural engineering personnel will review all experiment installation
drawings for adequate safety factors and proper design techniques.
Formal stress analyses will be performed on the installations. The
designs will be specifically reviewed for "Safety Critical Structures."
Any safety critical structures will be separately analyzed and
documented. The contractor will be responsible for reviewing the
experiment hardware developer's design and assisting them in completion
of adequate stress analysis documentation. In some cases, the contractor
will be expected to perform the stress analysis for the hardware
developer. The contractor engineering personnel shall be familiar with
and be proficient in the use of NASA Structural Analyses programs, in
particular COSMIC NASTRAN. Contractor responsibility includes qualifying
for final structures "sign-of" on engineering drawings and stress
reports.

**2.1.4.4.2 Thermal and Environmental Analysis** - The contractor shall
be responsible for evaluating the HLS experiment and experiment support
hardware thermal loads and their affect on the flight vehicle equipment
and crew environmental control items (ECS). This will include the
determination air flow levels required to maintain the experiment
hardware within a safe operating temperature age assure reliable
operation during flight. The air flow requirements must be evaluated
against the air flow and delta pressure limitations of the flight
vehicle and any violations of these limitations must be analyzed for
options and these options presented to HLS for either waiver processing
or payload configuration modifications.

The contractor shall be responsible for the determination of the impact
on the flight vehicle ECSs that may result from all aspects of the
experiments such as cabin heat and moisture loads generated by various
protocols that require strenuous crew exercise.

**2.1.4.4.3 Electrical Systems Analysis** - The contractor shall be
responsible for reviewing electrical systems design including data,
power, and video requirements of the experiments on each flight payload.
The contractor engineering personnel will compare the experiment
requirements with the carrier capabilities to assure that all experiment
needs are satisfied. The development and maintenance of ICDs will be the
responsibility of the contractor. The contractor shall be responsible
for standardizing the experiment electrical interfaces. Once the
electrical interface agreements have been signed, the contractor will be
responsible for determining the optimum interconnect cable layouts
within the flight racks or in the crew area as required. Development and
maintenance of the cable fabrication drawings will be the contractor's
responsibility. The contractor shall be responsible for assuring that
proper components are selected and that acceptable flight assembly
techniques are utilized. The contractor will also be responsible for the
fabrication of flight cables.

## 2.2 LABORATORY/FACILITY SUPPORT SERVICES {#laboratoryfacility-support-services .unnumbered}

\*\*\*From Schedule A, LSPD, 10.2.1, [EDITED]{.underline} to delete the
first sentence from the original:

### 2.2.1 General Support Services {#general-support-services .unnumbered}

The following are representative tasks the contractor shall perform:

\*\*\*From Schedule A, LSPD, 10.2.1.1:

**2.2.1.1 Advanced Concepts** - Evaluate existing and planned programs;
formulate plans for life sciences laboratory facilities which meet the
stated experiment operational support requirements; and formulate
experiment support plans which optimize utilization of existing JSC
Human Life Sciences Laboratories.

### 2.2.2 Laboratories {#laboratories .unnumbered}

\*\*\*From Schedule B, Part 1, 4.4.2, Microcomputer Laboratory, edited
to change microcomputer lab to microcomputer HW development:

**2.2.2.1 Microcomputer Hardware Development** - The contractor shall
furnish the necessary skilled personnel and materials to maintain a
microcomputer hardware development capability which shall:

-   Write utility programs and routines for the LSLE microcomputer and
    the LSLE microcomputer-2, a new development that will eventually
    replace the old microcomputer.

-   Write programs to test LSLE microcomputers.

-   Write experiment software as required.

-   Act as a consultant to experiment developers who use the LSLE
    microcomputers.

-   Configure flight LSLE microcomputers to experiment requirements,
    prepare configuration documentation, and install software. The
    contractor shall test' and certify that the experiment
    microcomputers are flight ready.

-   Maintain LSLE microcomputers and ground-use software development
    systems. The contractor shall troubleshoot and repair LSLE
    microcomputers as required.

\*\*\*From Schedule B, Part 1, 10.0:

### 2.2.3 Facility/Ground, Systems Engineering, and Operations

**2.2.3.1 Operations Support Facility Development** - The contractor
shall be responsible for the development and operational support of the
HLS facilities. These facilities shall support all activities as defined
in Part 1 of the SOW. The contractor shall be responsible for developing
an overall facility development and implementation plan which will
describe the total process of developing, implementing, and dining the
basic support facility. The plan shall address existing and future
requirements, proposed proud new facility concepts and designs, and
shall describe each functional area within the facility.

**2.2.3.1.1 Planning and Analysis** - It shall be the contractor's
responsibility to accumulate detailed requirements, conduct analyses,
and develop the rationale necessary to support HLS in the design and
implementation of special test and checkout facilities at JSC and other
specialized facilities as required to support the HLS contract elements.
These requirements shall be based upon existing project support as well
as plans for future projects; e.g., space station.

**2.2.3.1.2 Design, Monitoring and Certification of Facilities** - The
contractor shall be responsible for the design and implementation of
special facilities as required to support the HLS project as defined in
Part 1 of the SOW. This shall include test laboratories, computer areas,
SMAs, logistics support areas, etc.

The contractor shall be responsible for monitoring the construction,
alteration, and development of these facilities to assure timely
completion and that the facility is built in accordance with established
project requirements.

The contractor shall be responsible for the development of criteria
necessary to accommodate a proper certification of facility readiness
and shall participate in the demonstration of this readiness.

\*\*\*From Schedule B, Part 1, 10.1.3, [EDITED]{.underline} to include
the EA5 buildings (37, 241), was 36,56,266 (to SM):

**2.2.3.1.3 Buildings 37 and 241 Facility Buildup** - The contractor
shall be responsible for the reconfiguration of the building 37, and 241
facilities and provide working laboratories in support of future
projects, experiment development, fabrication and assembly work, test
and verification, science monitoring, and computer systems. The
contractor shall be responsible for maintaining and operating these
areas and shall be responsible for their configuration control.
Specifically, the contractor shall be responsible for performing the
following activities:

a\. Review for accuracy, provide update for, and maintain a complete set
of as-built facility structure and utility drawings. (Drawings will be
provided by the JSC Center Operations Directorate).

b\. Develop/document detailed room layouts for configuring each of the
rooms. This effort requires coordination between several different
elements within HLS which have responsibility over different areas.

c\. Identify, label, and maintain correct identification of all
utilities available within each room.

d\. Identify, establish, document, and implement interfaces with other
NASA center elements as to respective maintenance and operations (M&O)
responsibilities and implement a method to assure that any required M&O
is regularly scheduled and performed to maintain uninterrupted
operations.

e\. Implement and maintain an adequate documentation control system for
the total test facility to assure configuration control and establish a
method of change request documentation and implementation.

f\. In conjunction with the STI Center, maintain documentation relative
to facility lab area activities, i.e., procedures, equipment manuals,
vendor supply catalogs, etc.

\*\*\*From Schedule B, Part 1, 10.2:

**2.2.3.2 Ground Support Equipment, Test Equipment, and Spares** - The
contractor shall be responsible for the development, implementation and
operation of new GSE and test equipment, provide spares, and provide for
M&O of existing GSE and test equipment. This task shall include the
following:

a\. Providing new GSE, test equipment, and spares provisioning which may
be developed by/through the contractor, procured and modified through
the contractor, procured through the contractor without modification or
provided to the contractor as GFE.

b\. Define/compile and document specific GSE and test equipment
requirements to support facility operations, existing and future test
and check-out operations, and existing and future operational support.

c\. Perform activities such as design (preliminary and detailed),
structural, mechanical, thermal, environmental, electrical/electronics
systems analyses, procurement, fabrication, installation, check out,
acceptance test, documentation (drawings and procedures), and M&O.

d\. Establish and implement a routine maintenance and periodic checkout
plan for all GSE and test equipment to assure that it remains in a ready
state, within repair and calibration where required, and ready to
support any activities when needed.

e\. The contractor shall be responsible for maintenance of GSE,
including but not limited to, the simulated remote acquisition unit, the
simulated high rate demultiplexer, the high rate demultiplexer
interface; the simulated user time clock, and the cassette data tape
recorder playback unit. This shall include a method of documenting
problems as a check for design weakness, a system to track maintenance
problems to assure their prompt correction, the maintenance of a spare
parts inventory, the maintenance of configuration control, calibration
and proof test status, and physical location of operational equipment.

f\. Provide trained operators for all GSE and test equipment.

g\. Prepare and maintain an updated inventory of existing and required
test equipment and instrumentation essential to the proper function of
all laboratories.

h\. Provide procurement documentation and procure additional test
equipment and support hardware as required.

i\. In conjunction with the STI Center, maintain adequate documentation,
i.e., procedures, drawings, manuals, etc., to maintain configuration
control, and provide for operations and maintenance of all GSE and test
equipment.

\*\*\*From Schedule B, Part 1, 10.3:

**2.2.3.3 Vehicle Mockup and Test Bed Development** - The contractor
shall be responsible for defining/compiling and documenting requirements
for flight vehicle mockups and test bed modules and their related
subsystems required by HLS to support present and future flight
programs. The contractor shall be responsible for the development of new
vehicle mockups and test bed modules and the modification of existing
vehicle mockups and shall provide for their M&O. This shall include the
following:

a\. Perform activities such as design (preliminary and detailed),
structural, mechanical, thermal, environmental, electrical/electronic
systems analysis, procurement, fabrication, installation and buildup,
check out, acceptance test, documentation (drawings and procedures), and
M&O.

b\. Establish and implement a routine maintenance and periodic checkout
plan for all vehicle mockups, test beds, and ancillary support systems
to assure they remain in a ready state, within repair and calibration
where required, and ready to support any activities when needed. This
shall include a method of documenting problems as a check for design
weakness, a system to track maintenance problems to assure their prompt
correction, the maintenance of a spare parts inventory, and the
maintenance of configuration control on operational equipment.

c\. Provide trained personnel, equipment, documentation, and spare parts
to maintain and operate the mockups and test beds.

d\. Provide experienced personnel to interface with other Center
elements as related to space station and/or other future projects, to
assure concepts and configurations are factored into test bed module
design and implementation and to serve as technical representatives for
life sciences to space station.

\*\*\*From Schedule B, Part 1, 10.4:

**2.2.3.4 Laboratory Management** - The contractor shall be responsible
for laboratory management to assure efficient, well planned and
supervised laboratory activities. This shall include the following:

a\. Interface with other division elements to identify proposed work and
establish near-term and long-range planning, including establishment of
specific priority ratings.

b\. Implement a work control system to assign work, clearly identify the
task to be supported, and status the progress of work being performed.
The work control system shall comply with the established plans,
priorities, and schedules previously established, schedule resources to
comply with the work identified, implement a mechanism to identify the
impact when problems affect scheduled completion.

c\. Provide adequate technician support along with adequate technical
and managerial supervision to assure efficient utilization of personnel.

d\. Provide basic laboratory management of all laboratories to assure
proper utilization, operation, and maintenance and to assure compliance
with well organized, clean, and sale laboratory practices.

\*\*\*From Schedule B, Part 1, 10.5:

**2.2.3.5 Test and Fabrication Support** - The contractor shall be
responsible for the development and implementation of test requirements
definition, planning, schedules, procedures, test setups, test
evaluations, test reports and the planning for future payload systems
verification.

The contractor will be responsible for the design and development of
hardware for special experiment and instrumentation requirements. The
contractor technical personnel shall be NASA-certified for specific
skills such as soldering, crimping, wire wrap, etc. The type of work
experience required is in areas such as (1) flight cable fabrication and
testing, (2) flight printed circuit board assembly and repair, and (3)
flight circuit design and environmental testing and broad experience
with laboratory test equipment.

The contractor shall be responsible for light-to-moderate fabrication
activities in support of test operations, facility and equipment
maintenance, and repair/refurbishment of flight and nonflight hardware.

The contractor must interface with many supporting center elements to
establish test requirements, schedules, and priorities and support
resources.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

## 2.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\* From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

2.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

3\. CREW AND THERMAL SYSTEMS

\*\*\* From Schedule A, 1.0 CTSD:

3.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

3.1.1 Program Management Support

**3.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program.

**3.1.1.1.1 Subsystem Management** - This function provides system
engineering and technical support for subsystem, system and element
technical management activities assigned to CTS including Thermal
Control Systems, Environmental Control and Life Support Systems (ECLSS),
EVA Systems, and Airlocks. The following are representative tasks the
contractor shall perform:

3.1.1.1.1.1 Provide architecture definition, requirements definition,
trade and design studies, integrated system assessments, hardware and
software integration assessments, critical technology assessments,
verification assessments, test planning, real-time test support, flight
support, anomaly resolution support, crew procedures review, hardware
changes review, conduct certification testing, provide project
coordination and perform sustaining engineering and system engineering
for subsystem and systems on spacecraft and habitats assigned to CTS.

3.1.1.1.1.2 Provide assessments, designs, testing, certification, and
evaluations for anomaly resolutions, enhancements, replacements, and
modifications of ECLSS for current and future programs including space
station assembly, man-tended station, and longer duration missions.

3.1.1.1.1.3 Provide assessments, designs, testing, certification,
evaluations, and documentation for anomaly resolutions, enhancements,
replacements and modifications of launch entry suits and related crew
escape equipment including biomedical sensors, emergency oxygen system,
Personal Parachute Assembly, and Advanced Crew Rescue system and for the
Space Shuttle EMU including portable life support system electrical and
mechanical systems.

3.1.1.1.1.4 Provide assessments, designs, development, fabrication,
test, evaluation, and documentation for design concepts,
proof-of-concept mockups, breadboards, prototypes, certification,
training, and flight hardware for anomaly resolutions, enhancements,
replacements, and modifications of EVA support equipment and tools.

3.1.1.1.1.5 Provide and maintain configuration and inventory control of
EVA systems flight and test hardware (including ground test and support
equipment) through a hardware control data center.

**3.1.1.1.2 Payload-to-Orbiter ATCS, ECLSS, and EVA Integration** - This
function provides integration and compatibility assessments for payloads
having fluid and thermal interfaces with the Orbiter ECLSS; EVA Annex II
preparation and assessment for payloads having planned, unscheduled, and
contingency EVAs; and EVA crew equipment and tools definition, design,
development, test, and delivery for payloads. The following are
representative tasks the contractor shall perform:

3.1.1.1.2.1 Identify and assess potential planned, unplanned and
contingency ATCS, ECLSS, and EVA requirements in support of Shuttle
payload and vehicle planning and integration activities. Define specific
task requirements and specify hardware performance requirements. Assess
existing hardware against these requirements and identify new hardware
requirements. Support user and operations personnel during the early
planning phases by providing ATCS, ECLSS, and EVA capability and
productivity data. Provide analytical support for the development and
review of each Payload Integration Plan (PIP). Document results of these
assessments in appropriate annexes to the PIP. Provide analytical and
engineering support to the Cargo Integration Review for each Shuttle
mission. Develop and review each Interface Control Document (ICD).

3.1.1.1.2.2 Provide analytical, design, fabrication, test, and
certification support for the buildup of prototype, training and flight
hardware for payload EVA crew equipment and tools, in-house non-flight
and flight projects, and flight experiments. Prepare volumetric mockups
1-G and neutral buoyancy evaluations and fabricate and engineering
models at contractor's facilities, NASA facilities, or a combination of
both.

3.1.1.1.2.3 Provide project management support for flight experiments
and in-house projects including task planning, scheduling, resource
definition and status, coordinating, and reporting. Develop project
plans quickly for potential major projects and put in place a project
management capability for initiating new projects.

3.1.1.1.2.4 Prepare, assess, and coordinate EVA Annex II content for
each Orbiter payload. Support Annex II activities during Program and
Project Reviews.

**3.1.1.2 Shuttle-Unique** - The program management functions described
below are unique to the SSP. The following are representative tasks the
contractor shall perform:

**3.1.1.2.1 Subsystem Management** - The subsystem management technical
support responsibilities are delineated in Sections 3.1.1.1.1.1 through
3.1.1.1.1.5.

3.1.1.2.2 Other Shuttle Support

3.1.1.2.2.1 Provide CEE technician support for Shuttle training
including aircraft and crew rescue, Terminal Countdown Demonstration
Tests (TCDT), Shuttle launch, Shuttle landing, and Personal Parachute
Assembly processing documentation activities including crew suit up and
insertion; buildup, servicing, checkout, testing, operation, repair, and
maintenance of CEE equipment and GSE.

3.1.1.2.2.2 Provide engineering and technical support for the
certification, flight readiness, real-time flight and postflight
activities of the Space Shuttle EMU, EVA support equipment and tools,
and airlock outfitting hardware.

**3.1.1.3 Space Station-Unique** - The program management functions
described below are unique to the Space Station Program. The following
are representative tasks the contractor shall perform:

**3.1.1.3.1 Subsystem Management** - The space station subsystem
management responsibilities assigned to CTS include ATCS System
Development Manager (SDM), Architectural Control Document (ACD) agent,
Mode Team Leader, and Subsystem Managers (SSMs); ECLSS SDM; and EVA
system SDM, ACD Agent, Mode Team Leader, and SSMs.

3.1.1.3.1.1 The subsystem management technical support responsibilities
are delineated in Sec­tion 3.1.1.1.1.

3.1.1.3.2 Other Space Station Support

3.1.1.3.2.1 Provide design assessments, requirements definition,
integrated Airlock trade studies, test planning, real-time test support,
verification support, flight support, anomaly resolution support, and
system engineering support for airlock activities assigned by space
station.

3.1.1.3.2.2 Support the space station Level II and Level III inline
development, certification, training, and verification activities for
the systems and elements assigned to CTS.

3.1.2 Research and Development Support

**3.1.2.1 Advanced Development** - This function includes the
responsibility to further the technology needed for spacecraft and
surface habitat active thermal control, environmental control and life
support, and extravehicular and airlock activity. The following are
representative tasks the contractor shall perform:

3.1.2.1.1 Provide resources to conduct Phase A and Phase B studies
within the technical responsibilities of CTS in support of Technology
and Project Implementation development activities and other advanced
endeavors and to those projects for which NASA elects to conduct the
Phase C-D activities in-house. Examples of advanced projects include
robotic lunar lander missions, human-tended lunar missions, human-tended
lunar habitat with EVAs, and human Mars missions. Provide technical
support in the areas of mechanical, chemical, and electrical engineering
for the contracted development and in-house evaluation of regenerative
life support technologies. Assist in review of the overall design,
definition of test facilities requirements, design of interface
equipment, definition of detailed test requirements and preparation of
documentation including test plans, procedures, and reports.

3.1.2.1.2 Provide technical support for the development and evaluation
of subsystems and systems related hardware of advanced thermal control
systems. The subsystems perform the functions of heat acquisition, heat
transport, heat storage, and heat rejection. The development effort
includes single phase and two phase heat exchangers, evaporators,
two-phase pumps, heats pumps of various types, condensers and advanced
heat rejection devices. These subsystems, when combined together form
the overall active thermal control system. Conduct analytical studies,
support test bed development and operations, and support component,
subsystem and systems level testing. Assist in the evaluation of
candidate technologies, support design reviews, assist in the
development of test requirements, test procedures, test evaluations, and
post test documentation such as test reports.

3.1.2.1.3 Provide technical support for advanced regenerative life
support systems consisting of biological and physical/chemical
components and subsystems. These subsystems perform the functions of
atmosphere revitalization, water recovery, and wastes processing with
minimum launch resupply penalties. Conduct analytical studies; prepare
designs; support component, subsystem, and system-level testing; and
support test bed development and operations. Provide chemical,
microbiological, agricultural, horticultural, electrical, mechanical,
control systems, and other technical support for the contracted
development and in-house evaluation of regenerative life support
technologies that include the biological/physicochemical areas of food
production, waste processing/resource recovery, water recovery, O2
recovery, CO2 conversion processes, and atmospheric and water trace
contaminant control (gaseous, particulate, and microbiological). Assist
in review of the overall design, definition of test facilities
requirements, design of interface equipment, definition of detailed test
requirements, and preparation of documentation including test plans,
procedures, and reports.

3.1.2.1.4 Provide technical support for the development and evaluation
of subsystems and related hardware/software in support of advanced EVAs.
The development effort includes advanced thermal systems, portable life
support systems, helmet mounted displays, high density energy sources,
carbon dioxide sensors, high pressure suits and gloves, thermal/optical
protective visors, liquid cooled ventilation garments, and automated
servicing and checkout systems. Assist in technology assessment,
coordinate design reviews, define development test requirements and
procedures, conduct test evaluations of system performance, and prepare
supporting documentation including test plans, procedures, and reports.

3.1.3 Engineering, Scientific, and Analytical Tools

**3.1.3.1 Computer Programs Development and Maintenance** - This
function provides specialized computer modeling support for development,
enhancement, and maintenance of ECLSS, ATCS, and EVA analysis computer
programs for Shuttle, space station, and advanced applications. The
following are representative tasks the contractor shall perform:

3.1.3.1.1 Develop, enhance, and maintain generalized and application
specific computer models and programs for thermal environment and
performance calculation; system and component level design and
optimization; fluid dynamics, heat transfer, chemical and
electrochemical systems analysis; and crewmember thermoregulatory system
simulation. The models and analytical tools include SINDA/FLUENT, G189A,
TRASYS, TSS, SlMTOOL CASE/A, ASPEN/PLUS, SINDA/EUM, LSOP, ASDA, and
41-node man.

3.1.3.1.2 Provide computer models to predict ECLSS and EVAS performance,
assess hardware changes, and support ground testing, mission activities,
and anomaly investigation for the SSP ECLSS and EVAS system engineering,
enhancements and assessments for space station, Mir, and longer duration
mission activities.

3.1.3.1.3 Provide computer models for space station ATCS/EVA test beds
and flight experiments to support definition, integration, test, and
mission planning activities. Develop and upgrade computer to evaluate
system support pretest/experiment planning and integration activities,
provide real-time test and mission support, and conduct post-test/flight
data and anomaly analysis.

3.1.3.1.4 Provide computer models for space station development, system
engineering, system integration and sustaining engineering activities
involving the ATCS, node/airlock ECLSS, EVAS, and Airlock element to
conduct independent ATCS, ECLSS, and EVA capability assessment and
selected trade studies; generate ATCS, ECLSS, and EVA subsystem database
inputs; support integrated ATCS, ECLSS, EVAS, Airlock development,
verification, and training tests; provide real-time mission support; and
conduct flight data and anomaly analysis.

3.1.3.1.5 Provide computer models for space exploration activities in
the ATCS, ECLSS, EVA, and Airlock areas. Develop computer models for
advanced ATCS/ECLSS/EVA systems and subsystems to perform engineering
analysis and trade studies that support development of advanced
ATCS/ECLSS/EVA conceptual designs, develop critical technologies, and
support test and flight experiment planning, integration, and evaluation
activities. Provide state-of-the-art software packages for the analysis
support.

3.1.3.1.6 Provide computer models for advanced regenerative life support
systems to support CTS's research, technology development, test bed, and
flight experiments activities.

3.1.4 Studies and Assessments

**3.1.4.1 General** - This function provides engineering analysis
support for Crew and Thermal Systems' responsibilities including
research, development, assessments, tests, missions, and anomaly
resolutions activities for technologies including ECLSS, ATCS, and EVA
and their applications for NASA-sponsored programs and activities
including Shuttle, space station, space exploration, and international
projects. The following are representative tasks the contractor shall
perform:

3.1.4.1.1 Provide engineering analysis ranging from characterization of
physical phenomena of data from laboratory research to transient
performance of integrated systems for applications that include
definition of thermal environment and performance, design and
optimization of components and systems involving fluid dynamics, heat
transfer, chemical and electrochemical processes and simulation of
crewmember thermoregulatory system.

3.1.4.1.2 Provide engineering analysis and studies of the Shuttle,
ECLSS, and EVAS enhancement activities including assessments of duration
missions and assessments of Shuttle, ECLSS, and EVA operations with
Space Station and international spacecraft including Mir and Soyuz.

3.1.4.1.3 Provide engineering analysis for SSP, ATCS/EVA test beds and
flight experiments activities including definition, integration, test,
and mission support activities.

3.1.4.1.4 Provide engineering analysis for Space Station development,
system engineering, system integration, and sustaining engineering and
Shuttle/space station integration and operations activities involving
the ATCS including two-phase flows and condensing radiators,
node/airlock ECLSS, EVAS, and Airlock element.

3.1.4.1.5 Provide engineering analysis for space exploration activities
in the ATCS, ECLSS, EVAS, and Airlock areas.

3.1.3.1.6 Provide engineering analysis and statistical analysis for
CTS's advanced regenerative life support systems activities.

**3.1.4.2 EVA Systems Definition** - This function includes the
responsibility for defining EVA requirements and establishing compatible
hardware Interface designs and test protocol procedures for EVA Systems
development programs across all NASA centers. This effort includes
establishing hardware integration requirements, defining test
requirements, providing real-time participation and support of test
activities, and assessing hardware performance. The following are
representative tasks the contractor shall perform:

3.1.4.2.1 Review individual EVA subsystems/components development
requirements and design approaches, and develop integrated system design
schematics and test requirements documentation necessary to conduct
tests to establish hardware performance capabilities and limitations.

3.1.4.2.2 Evaluate and assess individual subsystems/components and
system test results and prepare test reports detailing findings and
recommendations.

3.1.4.2.3 Review and assess EVA system and hardware contractor(s) inputs
such as trade studies, interface requirements, and design standards to
assure compatibility and adequacy.

3.1.4.2.4 Review change requests to identify and evaluate EVA system and
hardware impacts, and provide recommendations for change disposition.

3.1.4.2.5 Attend and support reviews conducted at other NASA Centers and
Space Shuttle and space station contractor facilities having EVA system
interface responsibilities.

3.1.4.2.6 Provide real-time chamber test engineering support.

**3.1.4.3 Mechanical Systems Design** - This function includes the
responsibility for mechanical systems designs for specified test and
flight experiment hardware and equipment required for implementing CTS
in-house projects. The following are representative tasks the contractor
shall perform and shall be accomplished to NASA JSC documentation
formats rather than any contractor corporate format:

3.1.4.3.1 Prepare schematics and layouts, conduct detailed mechanical
systems design and drafting with traditional and CAD tools, and provide
the supporting analyses and documentation required for fabrication of
the specified hardware and equipment in JSC facilities.

3.1.4.3.2 Provide stress analysis of mechanical system designs before
and during the preliminary design phase. Provide fully computerized
finite element structural math models and related stress calculations
for the detailed design and final stress report phase. Provide all
structural analyses in NASA JSC formats (i.e., NASTRAN).

3.1.4.3.3 Provide expert consultation support for design projects in the
electrical, structural, and material (metallic, non-metallic,
composites, or ceramics) disciplines.

3.1.4.3.4 Provide tracking and coordination support for CTS hardware
being fabricated or modified in other JSC facilities.

3.2 LABORATORY/FACILITY SUPPORT SERVICES

3.2.1 General Support Services

**3.2.1.1 Processes and Controls** - This function provides the
processes and controls that are used by more than one organization
within CTS to accomplish CTS projects and tasks. The following are
representative tasks the contractor shall perform:

3.2.1.1.1 Establish and operate program unique and integrated programs
tracking and status information reporting systems for CTS resources.

3.2.1.1.2 Maintain and operate a detailed, accurate, and complete
configuration control system in accordance with JSCM 8500, and a
contract documentation logging, status and tracking system for Firm
Contract Change Proposals (FCCPs), Engineering Change Proposals (ECPs),
and contract modifications.

3.2.1.1.3 Prepare test data for presentation and identify, scale,
combine, graph, and perform systematic checks to verify the accuracy of
directly acquired and processed data. Provide real-time and post-event
graphic and numerical calculations and display, and comparison and
coordination of data with results from computer programs associated with
laboratory operations.

**3.2.1.2 Common Facility Services** - This function covers those
facility operations which are common to the laboratories including
buildings 7, 7A, 7B,29, 32, 32Q, 33, 34, and 241. A variety of shops,
laboratories and test chambers, test beds and flight hardware systems
are located in these buildings and utilized for engineering development
testing, system analysis, and flight certification testing of crew
equipment, crew support equipment, life support equipment, and active
thermal control systems for human space flight programs. In addition,
the laboratories provide for reduced pressure EVA training; real-time
mission support; anomaly investigation and resolution; and flight
procedure development verification for CTS hardware. Frequently, test
buildup and test conduct require three shift operations support. The
following are common representative tasks the contractor shall perform
in each laboratory:

3.2.1.2.1 Provide control of materials used in human and
non-human-tended test setups including non-metallic materials and other
materials that might be a hazard in such testing or cause damage to
equipment. Prepare material control reports and submit to the CTS
Material Utilization Control Board for approval and present results to
the Test Readiness Review Boards. Provide support to the CTS Material
Utilization Board.

3.2.1.2.2 Operate JSC Satellite Calibration Laboratory including
preparation of procedures, providing calibrating services, and
maintaining records. Provide continuity verification, and checkout of
the overall test setup, referred to as end-to-end verification. The
calibration and instrument verification service shall include instrument
and transducer troubleshooting and repair.

3.2.1.2.3 Operate and maintain cleaning facilities for CTS. Clean test
buildups and portable life support systems or components, suits, or
other Environmental Control System (ECS) components; maintain and
operate dry cleaning equipment; maintain and operate checkout benches in
a clean condition; and maintain the clean facility itself along with its
support equipment.

3.2.1.2.4 Provide design, construction, and operational verification of
special hardware and software systems when specified by the Government;
provide recommendations and evaluations of equipment, both facility and
test-related to be purchased by NASA for the laboratories; provide
technology assessment of support system designs and/or testing in the
technical disciplines such as thermodynamics, chemical, mechanical,
electrical, and computer sciences.

3.2.1.2.5 Provide the engineering and technician support for test
facility projects to plan, design, schedule, buildup, modify, and
checkout test facilities and test support systems. This effort includes
providing project engineering to lead projects and support all or part
of the project elements including requirement reviews, design reviews,
status reviews, configuration change boards, and readiness reviews;
conducting project meetings; coordination of outside support efforts;
maintaining schedules; monitoring resources; and assuring compliance
with the project objectives and the applicable regulations.

3.2.1.2.6 Design ground test support equipment; install and integrate
test articles.

3.2.1.2.7 Provide engineering and technical support to design, install,
operate, and maintain chamber support systems, both manual and
automated, such as the water cooling system, hazardous gas detection,
oxygen monitoring, refrigeration systems, vacuum system, waste
management system, cryogenic systems, solar simulation system,
electrical system, and chamber automated controls.

3.2.1.2.8 Provide and install connections to the designated computers
and/or data acquisition systems for reduction of control data for
non-human-tended and human-tended test activities, automation, CAD
and/or engineering analysis.

3.2.1.2.9 Install thermocouples and transducers on test articles;
cabling to signal conditioning, recording and display equipment; and
system adjustment, calibration, and verification.

3.2.1.2.10 Provide property calibrated/certified transducers, signal
conditioning, display and recording equipment, test facility and test
support system control instrumentation, for measurement of test
parameters, control of test support systems, and the recording of test
data by data acquisition systems which include the operation and
maintenance of the CTS JSC Satellite Calibration Laboratory. Insure that
calibration/certifications are achieved in compliance with JSC
instructions and in cooperation with the JSC Calibration Laboratory,
develop schedules for calibration/certification of transducers and
instrumentation against primary standards traceable to the National
Institute of Standards and Technology. Maintain calibration and
certification procedures, calibration/certification records, and provide
for the storage of test instrumentation. Provide a systematic program to
insure accomplishment of the above.

3.2.1.2.11 Assemble, test, clean, use, and maintain crew equipment
necessary to operate long-duration tests. This shall include, but not be
limited to space suits, lock observer/test subject helmet assembly with
oxygen mask, waste management systems, and protective clothing. Provide
food and utensils required by the test subject/lock observers during
test condition.

3.2.1.2.12 Provide engineering and technician support to select and
install necessary instrumentation for measuring test parameters (i.e.,
temperature, pressure, flow, partial pressures) in test buildups on test
articles, and for flight systems.

3.2.1.2.13 Provide instrumentation and physiological data collecting and
processing in support of test activities which include preparing and
installing on the test subjects the necessary instrumentation devices to
provide physiological measurements such as blood pressure, respiration
rate, electro-encephalograms, electro-cardiograms, body temperatures,
galvanic skin response.

3.2.1.2.14 Produce documentation suitable for status determination of
test article and test support systems for Test Readiness Review Boards.
Have and maintain a current work control system which shall control the
assignment and flow of work within the contractors organization,
determine work status, produce reports and current schedules of work
status, and develop coordination with other facility work such as Test
Preparation Sheets (TPS's), Discrepancy Reports (DR's), procedures,
checklists, engineering work orders, and major facility rework.

3.2.1.2.15 Prepare and implement test preparation sheets, detailed test
procedures, drawings, configuration change orders, checklists,
procedures, DR (Discrepancy Report) disposition.

3.2.1.2.16 Document test setups and operation with wiring diagrams,
patch sheets, and system configuration control drawings and recording
logs.

3.2.1.2.17 Maintain operating logs on facilities, test items, and an
up-to-date status on consumables and equipment. This includes the proper
identification and filing of tapes, recorder paper rolls, and similar
basic raw data obtained from test and equipment verification runs.

3.2.1.2.18 Maintain the test readiness of test face and test support
systems including cryogenic systems. Coordinate outside support
maintenance activities; coordinate consumables supplies including liquid
nitrogen, helium, ammonia, oxygen, breathing air, and special
gases/fluids.

3.2.1.2.19 Provide development test support in CTS's test complexes.
Perform design, buildup, maintenance, operation, and conduct of
development tests and evaluations on breadboard, prototype, and flight
experimental equipment and materials. Fabricate breadboards, test
setups, and special instrument and environmental simulation systems in
accordance with engineering drawings, sketches, and specifications for
the test set-ups.

3.2.1.2.20 Provide, operate, and maintain laboratory and test support
systems including communication systems, television system (video and
IR).

3.2.1.2.21 Direct and/or conduct all or parts of test functions
including coordination of events and scheduling of activities.

3.2.1.2.22 Provide comprehensive test direction, conduct, and
coordination of vacuum and thermal/vacuum testing of highly specialized
and complex space equipment and/or spacecraft including the special
requirements for human-tended operations. This includes the preparation
of detailed test procedures for conducting test operations.

3.2.1.2.23 Design, fabricate, check out, and operate laboratory pressure
systems in compliance with all applicable National Codes and NASA
directives.

3.2.1.2.24 Operate the chambers and associated equipment for
non-human-tended and human-tended tests in the various laboratories of
CTS during checkout verification and operational periods. This involves
starting and stopping of the equipment and the necessary observation of
automated systems.

3.2.1.2.25 Modify, operate, and maintain personal equipment and
oxygen/air breathing systems used to support pre-test and test activity
such as equipment used for pre-breathing with oxygen, portable
ventilators for transfer of crews to chambers, lock observers and test
crew equipment, and portable breathing systems for crew rescue. Maintain
equipment at a sufficient level to support the activity of human-tended
tests for CTS laboratories. Maintain laboratory rescue breathing systems
in working order.

3.2.1.2.26 Provide inside vacuum chamber airlock observers and rescue
technicians (sea level, hypo/hyperbaric conditions) to support test
runs. Technicians will be required to work inside the chamber during
reduced pressure operations and in other hazardous environments created
within the CTS test programs.

3.2.1.2.27 Provide, on a voluntary basis only, employees to be utilized
as crew in test activities such as man-rated chambers, zero-g aircraft
flights and other test activities. This specifically includes
participation in tests at less than ambient atmospheric pressure.

3.2.1.2.28 Provide personnel training/certification and safety services
specifically related to activities in the CTS laboratories with
particular emphasis on the hazardous/human-tended test complexes.
Provide certified support in the areas of: (a) high pressure fluid
systems; (b) vacuum systems; (c) cryogenic systems; d) human-tended test
support for operations in hazardous environments including flight
physical and physiological qualification; (e) high and low energy
electrical/hydraulic systems; (f) gas analysis systems; (g) test
directors for conduct of human-tended and non-human-tended testing; (h)
solar simulation systems; (i) space suit support systems; (j) data
acquisition systems; and (k) electrical and mechanical buildup,
verification, and operation of man-rated systems. Develop and maintain
near real-time safety procedures to facilitate egress from potentially
hazardous operations. Provide support to the CTS Training Review Board
for maintenance of all CTS training plans and records. Safety services
include the use of life support systems such as oxygen and/or breathing
air for test subject/astronauts in a hostile environment, use of
hazardous and toxic chemicals such as ammonia, freon, hydrogen,
cryogenic, high pressure systems and electric/electronic systems.

3.2.1.2.29 Prepare and maintain current the configuration control
documentation including drawings, operational procedures/checklists,
maintenance/checkout procedures, calibration procedures, system and
integrated systems FMEA/hazard analysis, and materials utilization
control in accordance with the CTS Standard Operating Procedures Manual
STB-F-001 for CTSL test facilities and test support systems.

3.2.1.2.30 Provide a CTS schedule showing all critical milestones
associated with laboratory operations. Maintain the schedule daily and
major modifications weekly. Included shall be at least a 6-year
schedule, with the annual schedule reviewed quarterly, identifying
accomplishments, and projecting the CTS remaining test load. The CTS
schedule shall be capable of assisting in the complex scheduling chores
of facilities, total work force and critical skills while bookkeeping
rule violation. Make recommendations of new rules leading to a total
Artificial Intelligence (AI) scheduling system.

3.2.2 Federal Information Processing Resources (FIPR) Support

This function includes the definition, acquisition, installation,
operation, maintenance, upgrade, and modification of data acquisition
computer hardware and software systems (including AI systems and
networks) within CTS. The following are representative tasks the
contractor shall perform:

3.2.2.1 Operate the computer facility including the computer-based data
acquisition systems, in support of automation, data base operations,
engineering analysis, and test facility support for laboratory testing.
Develop software to support real-time data acquisition and display,
automated control and data processing, automation, Computer Aided Design
(CAD), engineering analysis, and laboratory operations. Upgrade and
maintain the software on all computer systems.

3.2.2.2 Specify and integrate computer software systems in computers
and/or data acquisition system(s), as required for control, data
reduction and/or analysis.

3.2.2.3 Assemble CTS computer complex requirements. Prepare necessary
system design, design specifications and documentation for procurement,
installation, verification, and implementation to insure the
requirements shall be satisfied.

3.2.2.4 Procure, schedule, install, verify, operate, maintain, modify,
and upgrade the computer complex in a timely manner with minimal
perturbation to the CTS's scheduled operations.

3.2.2.5 Procure, schedule, install, maintain, manage, and upgrade the
CAD computer network in a timely manner with minimal perturbations to
the CAD operations and the CTS computer scheduled operations.

3.2.2.6 Design, implement, and insure the continued operation of
computer systems networks including Ethernet and their interfaces with
other networks. Expand and modify these systems using computer
automation techniques and computer tuning techniques as applied to an
automation environment.

3.2.2.7 Design and develop programs to automate and improve operations
and management information systems.

3.2.2.8 Provide user assistance during checkout and implementation of
computers and data acquisition systems.

3.2.2.9 Support computing applications with assistance in configuration
planning, capability reporting, schedule development, user help,
training, equipment/systems procurement, network design, documentation,
data base formation, laboratory modifications, and computer language and
graphics software capabilities.

3.2.2.10 Provide for security in the acquisition of FIPR systems. These
security requirements shall cover the total system to be acquired,
including all aspects of hardware, software, facilities, personnel,
data, and operations.

3.2.2.11 Operate and maintain the various data and computer systems
associated with data collection, reduction, computation and chamber
system automation.

3.2.2.12 Operate and maintain computer-based data acquisition, display,
and control equipment and systems in support of all test operations.

3.2.2.13 Modify data acquisition and processing systems, and develop
automatic control systems that increase test capabilities, improve
facility efficiency, and support unique test requirements. The effort
includes the provision of special purpose recording and display systems,
the modification of existing hardware to meet new requirements, and the
assembly of electronic devices and systems. Verify the specified
performance of such systems, develop operating and maintenance
procedures, and prepare detailed drawings and other documentation.

3.2.2.14 Develop software to support utilization of computer systems for
test data acquisition, automated test control, real-time information
display, and post-test data processing. This effort includes planning of
software configuration, scheduling of software development, and
preparing detailed documentation of the software. Plan and conduct tests
to demonstrate and verify software performance, develop operating
procedures, and train system operators on software utilization. Operate
PC, Macintosh, and DEC VAX computers using protocols including DECNET
and TCP/IP on VAX computers and APPLETALK, ETHERTALK, NOVELL.

3.2.3 Special Purpose Laboratories

**3.2.3.1 Soft Goods On-Site Development Laboratory** - This function
includes on-site design, development, fabrication, assembly, and test of
unique soft good products for male and female crewmembers and equipment
to be used for ground and flight applications including crew training,
chamber testing, medical research, and space flight. The following are
representative tasks the contractor shall perform:

3.2.3.1.1 Develop soft goods designs and fabrication patterns; sewing,
heat sealing, and adhesive bonding procedures; assembly instructions;
and acceptance test procedures.

3.2.3.1.2 Manufacture, test, and support fit checks and crew evaluations
of prototype, test, training, and flight soft goods products including
fabric pressure containers, multilayer thermal insulation blankets, and
other specialized articles.

3.2.3.1.3 Operate and service soft goods fabrication equipment,
including sewing machines, heat sealing equipment, curing ovens and
related instrumentation.

**3.2.3.2 Soft Goods Off-Site Fabrication Facility** - This function
provides off-site capability for the design, development, fabrication,
assembly and acceptance, and certification testing of unique prototype,
test, training, and flight soft goods end-items including tethers,
containers, stowage bags and cushions, multi-layer thermal insulation
blankets and other specialized articles required to support male and
female crew training, chamber testing and flight equipment. The
following are representative tasks the contractor shall perform:

3.2.3.2.1 Develop soft goods designs and fabrication patterns and
drawings, fabrication, assembly and acceptance/certification test
procedures.

3.2.3.2.2 Manufacture and test the soft goods equipment and support fit
checks and crew evaluations.

**3.2.3.3 Advanced Materials Laboratory** - This function provides
testing of fabric materials in the Advanced Materials Laboratory. The
fabric materials characteristics to be evaluated include abrasion and
puncture resistance, cycle life, permeability, optical properties,
tensile strength, and comparative testing of representative fabric
structures. The following are representative tasks the contractor shall
perform:

3.2.3.3.1 Prepare test procedures and samples; set up, operate, and
maintain test equipment; conduct tests; and analyze test data.

3.2.3.3.2 Provide properly calibrated/certified equipment for evaluation
of the materials characteristics in the laboratory.

3.2.4 Technology/Discipline Laboratories

This function includes laboratory buildup (including test stand
customizing), procurement of candidate advanced test articles,
assistance in test operations, and assurance of test readiness in
"hands-on" testing laboratories. The test stands/buildups, located at
JSC buildings 7, 7B, 32Q, 34, and 241, are used to verify technology
concepts, component performance, and parametric testing while providing
hands-on experience to engineers and scientists. The laboratory
complexes are grouped by discipline (i.e., thermal, life support, and
EVA/PLSS). The following are representative tasks the contractor shall
perform:

**3.2.4.1 Thermal Control System (TCS) Laboratory** - Provide the
design, facility and test buildup, procurement and integration of test
articles, testing and documentation required in the TCS laboratory for
development and evaluation of state-of-the-art advanced thermal control
components and systems including capillary controlled two-phase flows
and phase change phenomena in two-phase flows; technologies for heat
acquisition, transport, storage, rejection and transport fluids; and
techniques for real-time data acquisition and control software and
hardware systems and their application to integrated thermal control
systems having multiple parallel heat sources and heat sinks.

**3.2.4.2 Environmental Control Life Support Systems (ECLSS) Laboratory
-** Provide engineering, scientific, technical, and procurement support
to the following ECLSS test facilities:

**3.2.4.2.1 Regenerative Life Support Systems (RLSS) Test Facility** -
Provide the design, facility and test buildup, procurement and
integration of test articles, testing, and documentation required in the
RLSS test bed for development and evaluation of RLSS biological and
physical/chemical components and systems.

**3.2.4.2.2 Human-Rated Regenerative Life Support Systems Test
Facility** - Provide the design, facility and test buildup, procurement
and integration of test articles, testing, and documentation required in
the human-rated test facility to demonstrate planetary surface habitat
life support systems; provide laboratory analysis support for both
human-tended and non-human-tended test bed activities; and develop and
operate an integrated control system for operating test articles
independently and as an integrated system.

**3.2.4.2.3 Exploration Test Facility** - Provide the design, facility
and test buildup, procurement and integration of test articles, testing,
and documentation required in the Exploration Test Facility to provide
data for process characterization and modeling and to investigate new
evolving technologies for future applications.

**3.2.4.2.4 Hybrid Regenerative Water Recovery and Wastes Processing
Test Bed Facility** - Provide the design, facility and test buildup,
procurement and integration of test articles, testing, and documentation
required in the Hybrid Regenerative Water Recovery and Wastes Processing
test bed facility to evaluate specific processes and advance the
technology for water recovery and wastes processing.

3.2.4.3 Extravehicular Activity (EVA) Systems Laboratory

3.2.4.3.1 Advanced EMU Development Facility

3.2.4.3.1.1 Provide the design, facility and test buildup, procurement
and integration of test articles, testing, and documentation required in
the Advanced EMU Development facility for development and evaluation of
advanced EMU components and systems.

3.2.4.3.1.2 Provide technician support for development, fabrication, and
testing of proof-of-concept and new technology EMU PLSS subsystems and
space suit components, mobility systems, and ancillary hardware items.

3.2.4.3.1.2.1 Fabricate soft goods, mockups, and modifications for
advanced space suit concepts.

3.2.4.3.1.2.2 Provide technicians certified for setup and conduct of
human-suited testing of advanced space suit and life support assemblies
and components in ground-based (sea-level conditions) facilities
including the 1-g trainer, Portable Air Bearing Floor (PABF), vacuum
chambers, and thermal vacuum chamber; zero-g aircraft reduced gravity
flight simulations, and Weightless Environment Training Facility (WETF)
activities. These evaluations include fit checks and measurements of CO2
removal, thermal control, reach envelope, torque, and force.

3.2.4.3.1.2.3 Set up and conduct non-human-tended performance and bench
cycle evaluations of space suit, life support system, and related
equipment.

3.2.4.3.1.2.4 Develop and fabricate specialized test fixtures, mockups
including foam-core, and prototypes of ancillary hardware items required
to support evaluation of EMU hardware development and test activities.

**3.2.4.3.2 Space Station Airlock Test Article (SSATA) Test Facility** -
Provide the design, facility outfitting and test buildup; procurement
and integration of test articles; testing and documentation required to
evaluate the airlock and EVA support systems activities supporting the
space station development, operations, and training responsibilities of
CTS.

**3.2.4.3.3 Crew Equipment Translation Assembly (CETA) Test Facility** -
Provide the design, facility outfitting and test buildup; procurement
and integration of test articles; testing and documentation required to
evaluate EVA support equipment and tools including CETA.

3.2.5 Chemistry Laboratories

This function supports the CTS Dry and Wet Chemistry laboratories whose
responsibilities include performing chemical analyses and evaluations,
performing spacecraft atmosphere evaluations and Life Support Systems
(LSS) liquid evaluations (which include chemical analyses and
evaluations), performing spacecraft atmosphere evaluations and LSS
liquid evaluations (which include chemical analyses), and providing
chemistry lab experiments to support portable life support systems
activities. The following are representative tasks the contractor shall
perform:

3.2.5.1 Provide procurement of lithium hydroxide (LiOH) and other
chemicals for potential flight use; conduct chemical analysis of unused
and expended LiOH; service LiOH cartridges for in-house test programs;
and conduct LiOH certification testing.

3.2.5.2 Prepare special solutions and mixtures requiring a knowledge of
chemistry for support of in-house development testing.

3.2.5.3 Provide the chemical analysis expertise to measure the
compositions of atmospheres, water, and heat transport fluids involved
in ECLSS functions provided on current and future spacecraft and in
advanced regenerative life support systems, both physical/chemical and
biological. This includes atmosphere revitalization, water reclamation,
waste processing, and plant growth processes, as well as investigating
the cause of corrosion, materials incompatibility, contamination, fluid,
or material degradation or other phenomena that lead to test or flight
anomalies.

3.2.5.4 Identify and quantify unknown organic/inorganic materials which
include solid, liquid and gaseous materials from CTS development ECS
hardware. Develop any new procedures as required to support development
of ECS hardware.

3.2.5.5 Evaluate current and advanced LSS concepts including trace
contaminant control subsystems and carbon dioxide control subsystem.
Include in-house laboratory bench-type studies with the required
sampling and analysis as well as gas analysis of feed and product gases
from advanced subsystems.

3.2.5.6 Build up, operate, and maintain sample acquisition equipment for
real-time atmosphere (trace contaminant and permanent gas) analysis of
samples taken in non-human-tended and human-tended chamber tests. During
the tests, analyze samples taken and continuously monitor the
atmosphere. Prepare procedures to do this work per NASA JSC requirements
and test reports.

3.2.5.7 Support the development of post-treatment methods and techniques
for purification of waste water distillates and spacecraft Atmosphere
Revitalization System (ARS) humidity-condensate water.

3.2.5.8 Develop new procedures for improved trace gas analysis as
required or anticipated. Where analysis cannot be performed by
instrumental means, utilize wet chemical methods until the instrumental
method is developed or the necessary equipment is obtained.

3.2.5.9 Evaluate spacecraft materials with respect to outgassing,
decomposition, compatibility; and chemical reactivity. This work shall
require the design and buildup of special equipment and apparatus.

3.2.5.10 Identity, operate, and maintain current state-of-the-art
analytical instrumentation for evaluation of environmental atmospheres
and water for both organic and inorganic impurities including infrared
adsorption spectrophotometry, mass spectrometry, gas chromatography, gas
chromatography-mass spectrometry combinations, UV/visible and atomic
absorption spectrophotometry, and ion chromatography. Classical wet
chemical techniques will be observed in the performance of these tasks.

3.2.6 Bond Room Facility

This function supports the bond room facility which houses flight
hardware and flight-related equipment under secure and controlled
conditions. The following are representative tasks the contractor shall
perform:

3.2.6.1 Provide for the shipment and receipt of flight and
flight-related properties into storage; maintain the hardware and
equipment while in storage; and issue to authorized users.

3.2.6.2 Operate and maintain a program stock inventory-control system
that identifies and records all transactions necessary for compliance
with regulations contained in NHB 4100.1 B.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

3.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

3.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

4\. AEROSCIENCE AND FLIGHT MECHANICS

\*\*\*From Schedule A, 3.0 NCAD

4.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

4.1.1 Program Management Support

**4.1.1.1 Shuttle - Unique** - This function provides the Guidance,
Navigation, and Control (GN&C) system verification activity required for
the flight readiness assessment, monitors GN&C systems performance
during missions, and conduct of special tests required in the laboratory
or on the flight vehicle. It is responsible for flight readiness
verification for each shuttle mission in the following areas: the
integrated GN&C system hardware, software, and functional capabilities
for all mission phases from prelaunch through landing roll out including
the various abort modes; flight control system response and stability
for rigid and flex body for all mission phases; sensor and effector
hardware and software; redundancy management; systems management;
separation systems for the solid rocket boosters and external tank;
sequencing; hardware/software compatibility; mated element interfaces;
and remote manipulator system Interfaces. The following are
representative tasks the contractor shall perform:

4.1.1.1.1 Provide in-depth engineering support to each area of AFM
flight readiness verification responsibility. The technical capability
shall consist of the personnel and analytical tools to evaluate proposed
changes, audit I-loads, and define the test requirements for the SAIL to
verify the capability of the integrated systems to perform the planned
missions. Assist in the planning and coordination of the verification
requirements and participate in the test activity to evaluate results
and resolve discrepancies. Make recommendations concerning the flight
readiness, coordinate sign-off of the flight readiness statements, and
maintain files for each mission.

4.1.1.1.2 Provide mission support required by the Chief Engineer to
maintain a flight data file, log mission events and problems, and assist
in closing out problem reports.

4.1.1.1.3 Provide technical support for participation in various board
and panel meetings including the following: Shuttle-Avionics Software
Control Board; Shuttle Avionics Systems Review; Ascent Flight Systems
Integration Group, Launch System Evaluation Advisory Team, Joint Mission
Integration Control Board, and Orbiter Engineering Review Board.

4.1.1.1.4 Provide the analysis of redundancy management (RM) hardware
and software systems. This includes RM requirements definition, design,
and documentation for Flight Control System (FCS) sensors, controls, and
effectors (Rate Gyro Assembly, Body Flap, Reaction Control System) for
Inertial Measurement Units (IMUs) and navigational aids (NAVAIDs), and
other avionics system components. This shall include Functional
Subsystem Software Requirements and change request (CR) review, CR
preparation, and mode team participation.

4.1.1.1.5 Provide analysis support for continuing capability enhancement
and development in the areas of Space Shuttle guidance, navigation, and
control. This engineering analysis support shall include all effects of
design, development, implementation, and verification of guidance,
navigation, and control systems. Provide support for enhancements to
existing capability and development of new capability in guidance,
navigation, and control.

4.1.1.1.6 Provide support for the development of new guidance,
navigation and control I-loads, both for unique flights and design
dependent I-loads.

4.1.1.1.7 Provide support for design, development, and implementation of
software and procedural automation enhancements to facilitate the
verification of correct values and correct mission selections of the
GN&C I-loads.

4.1.1.1.8 Provide technical support to I-load owners and serve as GN&C
I-load owners. This function includes insuring that proper technical
studies and rationale are used to develop new I-loads values. The I-load
owner must also insure that the correct values are entered into the
I-load system. Finally, the I‑loads owner must insure that the correct
values are chosen for each Space Shuttle flight and that sufficient
checks and balances are in place throughout the I-load development
process.

4.1.1.1.9 Provide technical support to Principle Function Managers (PFM)
and serve as GN&C PFMs. This function includes responsibility for the
correctness of the Principle Function (PF) requirements in the
appropriate Software Requirements Documents. The PFM must work with the
Program Office and other subsystem managers, and PFMs to assess whether
hardware changes affect software and vice versa. The PFM must review
pending Software Change Requests (SCR) for changes that may affect the
PF. Also, the PFM shall assist the Flight Function Manager (FFM) and the
Program Office in resolving discrepancies pertaining to the PF.

4.1.1.1.10 Provide technical support to the GN&C Launch System
Evaluation Advisory Team (LSEAT), and serve as the GN&C representative
to the LSEAT. This position requires an understanding on the
Day-of-Launch-I-Load-Update system, and an understanding of the Space
Shuttle first stage trajectories and the ability to make a real-time
judgment of the adequacy of the GN&C system and the I-loads to support a
Space Shuttle launch.

4.1.1.1.11 Conduct engineering design activities, program design
reviews, and hardware/software system level design verification
activities, mission support, flight rule, Shuttle Operational Data Book
(SODB), launch commit criteria, testing, and maintenance requirements.

**4.1.1.2 Space Station - Unique** - This function provides the
engineering and analysis support for space station systems and
operations design evaluations. This effort includes activities such as:
analytical studies to assess alternate design options, provide technical
integration across space station systems and elements, assist in
developing technical direction to the prime space station work-package
contractor(s), perform independent analysis, and develop the experience
base to evolve from systems trades to operational trades to detail
flight techniques for space station operations. Assess performance of
manipulators to be used on the space station with regard to feasibility
and operational constraints. These studies, including performance scans
and trades, lead to the selection of optimum systems performance and
optimum operations performance profiles and trajectory parameters for
each specific event window. Study areas may include the functional areas
of proximity operations, attitude and pointing, consumable resources
rendezvous, payload handling, recontact analysis, space station Mobile
Remote Manipulator System (MRMS) analysis, berthing/docking analysis and
separation analysis. The following are representative tasks the
contractor shall perform:

**4.1.1.2.1 Orbital Parameters** - Conduct performance analysis
evaluating proposed orbits.

**4.1.1.2.2 Rendezvous** - Evaluate the space station in terms of
logistics, performance and tracking requirements.

**4.1.1.2.3 Proximity Operations** - Perform plume impingement and
dynamics analysis to design operationally acceptable profiles compatible
with vehicle constraints.

**4.1.1.2.4 Payload Handling** - Perform analyses which will evaluate
new capabilities for the Space Shuttle Remote Manipulator System (RMS)
and the Space station MRMS. Perform evaluations of the dynamic
interactions between the Orbiter, space station, manipulator, and
payloads to establish its operational constraints.

**4.1.1.2.5 Recontact Analysis** - Perform analyses to determine
envelopes from which various payloads (or portions thereof) may be
jettisoned without recontacting the space station, Orbiter, or other
elements of the system.

**4.1.1.2.6 Mission Requirements Synthesis and Analysis** - Support
definition, design, and development of space station Mission Integration
Plan (MIP) development, integrated mission scenarios, flight phase
analysis and systems requirements development, assembly sequence
definition, logistics and traffic management, orbit selection trade
studies, configuration definition analyses, and mission operations and
systems requirements assessments.

**4.1.1.2.7 Systems Requirements Synthesis and Analysis** - Support
Space station systems design and sizing requirements in the following
areas: electrical power system, thermal control systems, propulsion
systems, and fluids management systems.

**4.1.1.2.8 GN&C** - Provide support in the following areas:

4.1.1.2.8.1 Space station momentum management concepts including impacts
due to configuration changes, flight modes, MRMS, payload placement, and
tethers.

4.1.1.2.8.2 Space Station propulsive control concepts, systems, and
designs, including impacts due to configuration changes, flight modes,
and operational restrictions.

4.1.1.2.8.3 Provide support to Technical Interchange Meetings between
ISS Program Office, Primt GN&C, and system designers, including U.S.
Operating Segment and Russian Segment.

4.1.1.2.8.4 Space station mass distribution guidelines to support the
space station user environment including microgravity.

4.1.1.2.8.5 Space station attitude and pointing guidelines to support
Space station user requirements.

4.1.1.2.8.6 Space station onboard techniques for maintaining velocity,
position, and attitude knowledge and related interfaces with ground, and
global positioning satellite (GPS).

4.1.1.2.8.7 Sensors and hardware evaluation, mean time between failure
(MTBF) analysis, redundancy requirements, and management.

4.1.1.2.8.8 Space station onboard software requirements and design
integration across systems and elements.

**4.1.1.2.9 GN&C Verification** - Provide support to the integrated
software and avionics verification in the following areas:

4.1.1.2.9.1 Develop verification requirements.

4.1.1.2.9.2 Review Program Office and Program Group 1 proposed test
plan.

4.1.1.2.9.3 Provide assessment of analytical and software verification
testing results produced by the system designers.

4.1.2 Research and Development Support

**4.1.2.1 Avionics Systems Engineering and Integration** - This function
provides for the design, test and/or analysis of avionics system
requirements to define the optimum systems configuration to meet program
requirements and provide an acceptable balance between development risk
and application of new technology; and defines avionics system/subsystem
integration requirements and assesses their implementation impact on
system-level hardware/software design requirements, development risk and
growth potential. The following are representative tasks the contractor
shall perform:

4.1.2.1.1 Perform studies and analyses to define the requirements for
implementation of new avionics systems concepts and evaluate the impact
on hardware and software systems design and development risk.

4.1.2.1.2 Support the design, development, and implementation of
simulation math models and provide support for integration with other
laboratories when required for advanced projects like the Personnel
Launch System (PLS). Tasks include conducting simulation tests,
implementing modifications and delivering resultant simulation data.

\*\*\* From Schedule A, NCAD, 3.1.2.1.3, [EDITED]{.underline} to remove
inertial/optical subsystems/components (which went to NEW SOW, Part I,
Section 9):

4.1.2.1.3 Provide the engineering design, development, implementation,
and evaluation of candidate Aerosurface/sensors, and Flight Control
techniques; and define the data interface requirements and engineering
assessment criteria for integrating these subsystems with other avionics
subsystems.

\*\*\*From Schedule A, NCAD, 3.1.3, Eng, Scientific, & Analytical Tools:

### 4.1.3 Engineering, Scientific, and Analytical Tools

1.  **Flight Control System Stability** - The function of this area is
    to:

\(1\) define Flight Control System (FCS) stability and controllability
requirements of rigid and flexible spacecraft configuration in terms of
phase and gain margins, time domain analyses; (2) evaluate guidance and
navigation subsystems of spacecraft that interact in a multibody orbital
environment (a multi-body proximity operations environment includes
rendezvous, docking, satellite retrieval, formation flying, and
planetary orbit); (3) define system level requirements for and perform
analysis of spacecraft integrated GN&C systems for ascent, on-orbit, and
entry mission phases (high fidelity time domain analysis tools such as
the Shuttle Engineering Simulator (SES) and Shuttle Trajectory and
Mission Planning Simulation (STAMPS) are utilized as well as simplified
part-task programs operated on individual workstations to insure that
all elements of GN&C hardware and software work together satisfactorily
with interfacing elements such as propulsion, communications and
tracking, flight crew, and ground support); and (4) insure that flight
worthiness criteria are met during all stages of vehicle development
from early conceptual design through flight testing and for all
appropriate flight phases. Spacecraft configurations include all vehicle
for which the AFM has responsibility for design, and/or development,
and/or flight test such as STS integrated vehicle, Orbiter with attached
(direct and remote manipulator system) payloads, space station with and
without appendages during coast and reboost. The following are
representative tasks the contractor shall perform:

4.1.3.1.1 Design, develop, and maintain engineering analysis tools with
high fidelity models for all subsystems elements/components that drive
or interact with vehicle stability and control and proximity operations.
Elements include control system sensors and effectors, rigid and
flexible structural components, flight control application software
modules, guidance and navigation software algorithms, navigation sensor
math models, and natural environment models such as gravity, atmosphere,
plume impingement.

4.1.3.1.2 Integrate software models developed for GN&C systems analysis
and proximity operation analysis into end-to-end simulators and/or test
beds. The GN&C application software modules for advanced vehicles such
as space station shall be of sufficiently high fidelity and programmed
in the appropriate software languages such that they may be utilized as
prototype flight code and/or run in other test beds at the integrated
avionics level.

4.1.3.1.3 Provide analytical tool maintenance, improvement, and
development for the digital computer programs of FAR, CSAP, MatrixX,
Matlab, NASTRAN, STOCS, and SES batch version required for ascent and
entry FCS linear flex analysis capability.

4.1.3.1.4 Expand FCS and payload integration capability by continuing to
implement, develop, and verify the batch version ascent/entry non-linear
flex time domain simulation. The flex SES batch version should include
the vehicle/payload structural flexibility, payload damping assistant
mechanism, and high fidelity flex actuator models.

4.1.3.1.5 Maintain the JAEL Shuttle trajectory simulation math models to
reflect current Shuttle Avionics Integration Laboratory simulator
configurations. Other support tasks include validation of math model
modifications, conduct OI to OI simulation validation, post test
analysis and design evaluation.

**4.1.3.2 Computational Fluid Dynamics (CFD)** - This function covers
the application of existing codes and development of new codes for
analyzing the flow field associated with present space transportation
systems, the Assured Crew Return Vehicle (ACRV), and future concepts. A
spectrum of analysis capabilities shall be required to support various
phases of the conceptual design, detailed design and flight
verification. The following are representative tasks the contractor
shall perform:

4.1.3.2.1 Maintain and upgrade the computer codes for predicting in
viscid flow, boundary layer flow and viscous flow in both external and
internal environments.

4.1.3.2.2 Provide support in the areas of aerodynamics, thermodynamics,
heat transfer, propulsion, and microgravity flow, including working with
off-site super computers, in adapting existing codes to
vector-processing modes.

4.1.3.2.3 Use and modify existing codes to estimate aerodynamic 6-DOF
force and moment coefficients of various ascent, entry and orbital
spacecraft.

4.1.3.2.4 Develop and modify Computational Fluid Dynamics (CFD) codes
for unique applications to advanced projects.

4.1.3.2.5 Maintain "method of characteristics" type computer codes for
generation of plume flow fields for spacecraft engines at atmospheric
conditions.

4.1.3.2.6 Develop plume impingement and flow field tools for analysis of
engineering problems unique to advanced mission designs (for example:
clustered engine plume radiative heating analysis).

4.1.3.2.7 Create, modify, and document heating computer codes.

**4.1.3.3 Other Tools** - The following are representative tasks the
contractor shall perform:

4.1.3.3.1 Support development and operation of software programs for the
layout and preparation of schematics, printed circuit and wire-wrap
boards, and photoplotting.

4.1.3.3.2 Provide programming support for the following software
programs: DAP, ADAP, GEMAS, Modified Maximum Likelihood Estimator
(MMLE), Parameter Estimator (PEst), GRAM, OADB, and POST.

4.1.4 Studies and Assessments

**4.1.4.1 GN&C Systems Analysis** - This function provides the planning,
coordination, requirements definition/documentation, validation of
implemented requirements, and simulation test conduct for real-time
man-in-the-loop (MIL) engineering simulations and non-real-time
simulations required to evaluate GN&C systems and related subsystems,
flight procedures, and mission requirements and performance as required
for operational activities on existing programs or for evaluation of new
advanced avionics systems requirements and capabilities. The following
are representative tasks the contractor shall perform:

4.1.4.1.1 Assist in the planning and coordination of requirements and
development of test plans and simulation requirements. A test plan
should consist of a run schedule, test objectives, test parameters,
initial conditions, test procedures, and data output requirements. The
planning shall also include analysis of the capabilities and limitations
of the specific simulation facility to evaluate the given problem and to
define tests to evaluate the simulator itself.

4.1.4.1.2 Prepare math models, numerical data, and evaluation criteria
required for the implementation and validation of the real-time MIL
engineering simulations.

4.1.4.1.3 Participate in simulation operations by providing engineering
pilot evaluation personnel for daily checkout and test evaluation and
for data collection and reporting.

4.1.4.1.4 Perform engineering simulation analyses to support the
evaluation of Shuttle Orbiter/payload avionics systems interface design
and performance requirements; proposed hardware/software design
improvements of the ascent, entry, and on-orbit integrated GN&C systems;
new display and payload system control requirements/procedures; and
Orbiter/payload dynamic interaction, including Tether Satellite System
experiments, to ascertain system design boundaries.

**4.1.4.2 Plume Flow Field and Impingement Analysis** - This function
covers the responsibility for the definition and maintenance of plume
flow fields and their associated aerodynamic/aerothermal induced
environments. Plume flow fields and impingement effects are to be
predicted for both atmospheric and vacuum conditions. Products from the
function include the definition of plume impingement pressure
distributions and convective and radiative heating environments for
vehicle/mission design and analysis, lunar landing soil erosion
analysis, and plume/plume interference characterization. The following
are representative tasks the contractor shall perform:

4.1.4.2.1 Support plume ground and flight test definition, data
analysis, and model development to improve plume effects prediction
capabilities.

4.1.4.2.2 Support the development and application of coupled continuum
and Direct Simulation Monte-Carlo plume simulation tools for the
characterization of vacuum plumes.

4.1.4.2.3 Provide analysis support for the definition of plume flow
field interactions with spacecraft, including the characterization of
plume induced loads and heating.

**4.1.4.3 Ascent Performance** - This function provides spacecraft
launch vehicle trajectory design and systems performance analyses to
maximize ascent performance capability while minimizing the potential
for exceeding systems constraints. This includes 3 and 6-DOF (degrees of
freedom) rigid body ascent trajectory simulation programs to analyze the
dynamics, performance, and trajectory profile of multi-engine launch
vehicles during any flight regime from launch to orbit insertion. The
following are representative tasks the contractor shall perform:

4.1.4.3.1 Provide support for the analyses to determine the best flight
attitude profile for a launch vehicle design with specified mass
distribution and aerodynamic characteristics considering vehicle
performance losses, control system requirements, and structural loads.
The effects of inflight winds and systems anomalies, or failures, must
also be considered from the standpoint of vehicle design criteria,
mission planning, and day of launch "go/no go" decisions.

4.1.4.3.2 Provide support in data base maintenance and ascent flight
systems math modeling for such areas as solid and liquid propulsive
systems; flight control systems gains, filters, and error signal mixing;
environment both winds and atmosphere; vehicle mass properties;
aerodynamic data bases mated vehicle and element; thrust vector and aero
control effectors; and structural and thermal load indicators.

**4.1.4.4 Aerodynamics** - This function provides the required support
towards the development, modification, and maintenance of the
aerodynamic models in support of the many simulator and trajectory
studies. The following are representative tasks the contractor shall
perform:

4.1.4.4.1 Provide support in the aerodynamic wind tunnel testing, flight
data analysis, and aerodynamic estimation areas.

4.1.4.4.2 Provide support in data base maintenance and math modeling for
such areas as aerodynamic force and moment coefficients; airloads
pressure coefficients; and flight test results for Orbiter, integrated
vehicle and element.

**4.1.4.5 Entry Flight Testing** - This function provides the entry
flight testing required to support the planning of flight test
maneuvers, analysis of the flight test results, and incorporation of the
results into the data base. Such tasks involve the Forward Reaction
Control System (RCS) Test Program and the Center of Gravity Expansion
Study. Numerous software programs must be obtained and updated. The
following are representative tasks the contractor shall perform:

4.1.4.5.1 Perform aerodynamic identification extraction analysis using
the MMLE, PEst, and other analysis programs of flight test maneuvers on
the Space Shuttle ascent and entry vehicles.

4.1.4.5.2 Make comparisons with preflight predictions and difference
analysis conducted to isolate modeling problems, coordinate and document
updates to the data base. Perform analytical, wind tunnel and CFD
estimations of aerodynamic characteristics.

4.1.4.5.3 Coordinate all activities required to establish flight test
requirements and develop them into experiments.

4.1.4.5.4 Identify flight test requirements, instrumentation, analysis
software and planning activities that would be applicable to future
advanced programs and to second generation Shuttle.

**4.1.4.6 Aerothermodynamics** - This function covers the responsibility
for the aerodynamic heating environments for current and advanced space
vehicles. Analytical capabilities are required in fluid mechanics,
aerothermodynamics, including radiation and convective heating, and
associated phenomena such as boundary layer transition, interference
effects, shock/shock interaction, catalytic effects, real gas and
chemistry models from wind tunnel and flight data and in using industry
accepted heating computer codes, such as MINIVER and BLIMP for
aerodynamic heating. These include codes in a UNIX computer environment
on standard mainframe and super computers. The following are
representative tasks the contractor shall perform:

4.1.4.6.1 Apply the methodologies and design data bases for the SSP
External Tank, Orbiter, Solid Rocket Boosters, Advanced Solid Rocket
Boosters and SSME nozzles.

4.1.4.6.2 Support SSP, ACRV, and advanced project panels and boards.

4.1.4.6.3 Support NASA in analyses and disposition of flight anomalies.

4.1.4.6.4 Establish, maintaining and creating of flight, wind tunnel and
predicted data bases.

4.1.4.6.5 Investigate TPS long term heating performance, such as
emittance and catalytic changes, in the flight environment.

4.1.4.6.6 Perform flow field calculations using computational fluid
dynamic codes such as IEC3D. Typical aerothermodynamic codes include
AA3DBL, ARCJET, BLIMP88, BLAB, GASPROP, GASRAD, HALIS, LANMIN, MASCC80,
MASCC88, MINIVER, NEBL, QRAD, RIFSIP, STREAMLINE, SUTRAD and VSL.
Reports shall utilize standard industry plotting codes, such as DISPLA
and PLOT3D.

4.1.4.6.7 Support aeroheating ground and flight test definition, data
analysis, and model development to improve aeroheating prediction
capabilities.

4.1.4.6.8 Use existing simulation codes to estimate ascent and entry
vehicle aerothermo characteristics. The effort shall be aimed at
estimating temperature limits so as to establish thermal boundaries.

**4.1.4.7 Parachute Landing Systems** - This function covers the
analysis and development of parachute landing systems for advanced
spacecraft such as the ACRV and the Lunar Transportation System. A wide
range of analysis capabilities shall be required to support various
phases of these programs from concept analysis to detailed design and
flight qualification testing. The following are representative tasks the
contractor shall perform:

4.1.4.7.1 Design and analyze conventional and gliding parachute systems
using empirical methods and wind tunnel/flight test data.

4.1.4.7.2 Perform analyses of parachute/payload trajectories, flow field
analysis, inflation analysis, and terminal area guidance analysis.

4.1.4.7.3 Plan and perform wind tunnel and flight tests on a range of
candidate parachute concepts. Coordinate all activities required to
establish flight test requirements, coordinate test readiness reviews,
and analyze test data.

4.2 LABORATORY/FACILITY SUPPORT SERVICES

4.2.1 General Support Services

This function provides the design, development, test, and evaluation for
avionics systems and related computing systems, data distribution,
subsystem interface processing, data operations functions for integrated
avionics systems services cover a spectrum from state-of-the-art concept
development, for both ground-based and flight systems, to laboratory
operations. Open system interconnect processing techniques, computing
systems, and data distribution/operations functions require a wide range
of integrated services. This support shall encompass a spectrum of
activity from state-of-the-art subsystem concept development for both
ground-base and flight systems to laboratory operations. The following
are representative tasks the contractor shall perform:

4.2.1.1 Provide test setups, develop test procedures, conduct Test
Readiness Reviews, perform test operations, provide data reduction,
evaluate test data, operate and maintain laboratory simulators, support
test bed activities, and issue test and evaluation reports for avionics
systems and components.

4.2.1.2 Perform the research, documentation review, design definitions,
engineering tradeoff studies, system optimizations definitions, and
other analyses in support of avionics systems integration, development,
and performing evaluation activities.

4.2.1.3 Perform design, fabrication, test, and analysis. This includes
the procurement, operation, and maintenance of data systems, display and
controls, and guidance, navigation, and control system hardware,
engineering breadboards and test beds, and test facilities to support
advanced space vehicle sensor and effector development.

4.2.1.4 Provide the day-to-day maintenance and operations support
required for advanced avionics systems data networks and "automation"
related data networks for which Aerospace and Flight Mechanics is
responsible.

4.2.1.5 Support the installation and checkout of additional
hardware/software and/or upgrades to present lab facilities; development
and maintenance of computer software for cathode ray tube (CRT) display;
video and film recording of dynamics graphics data; and documentation of
all appropriate lab hardware and software.

4.2.2 Federal Information Processing Resources (FIPR) Support

The following are representative tasks the contractor shall perform:

4.2.2.1 Provide general computer systems support in the areas of
software development and maintenance of existing and planned engineering
software and hardware systems. Support activities such as applications
and operating systems software development, vendor software installation
and operational support, consultation, user training, and the
maintenance and operational support of the AFM data bases and analysis
software systems.

4.2.2.2 Support the migrating of engineering software from one AFM
computer to another and for the maintenance of existing software systems
on any of the AFM computers. Provide training and consultation to users
of the AFM computers, operating systems, or any purchased or developed
software. Gain information for installation and maintenance of purchased
systems and for the training of AFM users. Design and develop software
and data flow interfaces between existing and planned AFM systems.

4.2.2.3 Provide system analyst support for day-to-day operating system
problems, system tuning, system operational upkeep and system hardware
upgrade consultation. This also includes installation and maintenance of
operating systems.

4.2.2.4 Provide support in the assessment of existing, enhanced and new
commercially available computer programs which may enhance the design
and analysis capabilities of the AFM. The assessment may include
trade-off studies of potential improvements in capabilities,
compatibility with existing programs, data bases, and procurement
recommendations.

4.2.2.5 Provide support to the AFM Functional Area Coordinator (FAC) in
the coordination of requirements and funding for material purchases and
the preparation of the associated paperwork, review of service requests
(SR) for completeness, proper signatures, timely assessment of the SR
status in the process flow, pickup/delivery of software and
documentation to users, maintenance of a data base of AFM equipment and
associated software.

4.2.2.6 Provide support to the AFM Information Resource Management (IRM)
Coordinator through supporting IRM Coordinators Meetings, scheduling
personnel for training classes, providing support in preparation of
paperwork involving purchase requests and supply requisitions and
tracking their status, and other IRM assignments.

4.2.2.7 Provide support to the AFM Computer Security Officer in the
preparation of computer system risk analyses, sensitive application
surveys/requirements, installation and maintenance of security related
software, and other security related assignments.

\*\*\*NOTE: Schedule A, NCAD, 3.2.3, NCAD Laboratories went to NEW SOW,
Section 9.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

4.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\* From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

4.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

5\. MANUFACTURING, MATERIALS, AND PROCESS TECHNOLOGY

\*\*\*From Schedule A, 7.0, STRUCTURES AND MECHANICS:

5.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

5.1.1 Program Management Support

**5.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program.

**5.1.1.1.1 Subsystem Management** - The following are representative
tasks the contractor shall perform:

5.1.1.1.1.1 Provide engineering support for analysis and resolution of
subsystem anomalies, and for evaluation of candidate hardware
modifications. Perform analyses of critical components and correlate
analytical predictions with laboratory and flight measurements.

5.1.1.1.1.2 Assist in the certification review of the thermal,
mechanics, material, and structural aspects of the various spacecraft
systems using flight data and contractor analyses and/or tests.

\*\*\*NOTE: Schedule A, SMD, 7.1.1.1.1.3 went to NEW SOW, Part I,
Section 8.

\*\*\*From Schedule A, SMD, 7.1.1.2:

5.1.1.2 Shuttle - Unique

5.1.1.2.1 General Engineering - This function defines design guidelines
and evaluates analytical techniques which may be used in the design
process. Also required is the development and maintenance of design and
operational data bases to support analytical studies and design
assessments. The following are representative tasks the contractor shall
perform:

\*\*\*NOTE: Schedule A, SMD, 7.1.1.2.1.1 and 7.1.1.2.1.2 went to NEW SOW
Part I, Section 8.

\*\*\*NOTE: Schedule A, SMD, 7.1.1.2.1.3 went to NEW SOW Part II,
Fracture Mechanics and Fracture Analysis.

5.1.2 Research and Development Support

**5.1.2.1 Advanced Development** - Provide engineering support for
technology assessment and development in the areas of automation,
docking and berthing, and remote situation systems.

5.1.3 Engineering, Scientific, and Analytical Tools

**5.1.3.1 Computer Program Development and Maintenance Support** - This
function includes the responsibility of programming support of all
analysis programs used, being evaluated, and being developed by
manufacturing, materials, and process technology. Programming support
shall encompass maintenance, consultation, documentation, evaluation,
and enhancements to existing programs, as well as evaluation and
development of new programs to support analysis and presentation of data
on computer systems utilized by JSC. The following are representative
tasks the contractor shall perform:

\*\*\*NOTE: Schedule A, SMD 7.1.3.1.1 went to NEW SOW Part I, Section 8.

\*\*\*NOTE: Schedule A, SMD, 7.1.3.1.2 went to NEW SOW Part II, Fracture
Mechanics and Fracture Analysis.

\*\*\*NOTE: Schedule A, SMD 7.1.3.1.3 went to NEW SOW Part I, Section 8.

\*\*\*From Schedule A, SMD, 7.1.3.1.4:

5.1.3.1.1 Provide program upgrades and enhancements to existing
programs, and develop new programs to support engineering analysis and
presentation of data. Provide capability evaluations and programming
support upon delivery of new program segments; develop test math models
and run check-out problems to evaluate new analytical software, new
computer facilities and new systems; and document all engineering
studies.

\*\*\*From Schedule A, SMD, 7.1.3.1.5:

5.1.3.1.2 Provide program development and software maintenance for
advanced interactive CAD/CAE graphics systems to support pre- and
post-processing of math models and data results, and advanced graphics
software.

\*\*\*From Schedule A, SMD, 7.1.3.1.6:

5.1.3.1.3 Provide expertise for interfacing between system software,
policies and procedures, and the application programs used by
manufacturing, materials, and process technology.

\*\*\*From Schedule A, SMD, 7.1.3.1.7:

5.1.3.1.4 Provide programmer consultation and user support for thermal
analysis programs used in integrated thermal analyses and include
thermal program modification and enhancements to satisfy unique
requirements dictated by program analytical needs.

\*\*\*From Schedule A, SMD, 7.1.3.1.8:

5.1.3.1.5 Provide engineering, computer program modifications, program
software consultation and user support for integrated payloads/advanced
space exploration programs/space station, Integrated Thermal Control
System (TCS) and Thermal Protection System (TPS) analysis using for
example, Thermal Synthesizer System (TSS), System Improved Numerical
Differencing Analyzer (SlNDA); Thermal Radiation Analysis System
(TRASYS) and other thermal programs and include definition and analysis
of requirements for these unique thermal analysis programs as well as
enhancements and maintenance associated with these programs.

\*\*\*NOTE: Schedule A, SMD 7.1.3.1.9, 7.1.3.1.10, and 7.1.3.1.11 went
to NEW SOW Part II, Fracture Mechanics and Fracture Analysis

\*\*\*From Schedule A, SMD, 7.1.3.1.12:

5.1.3.1.6 Provide engineering and programming support for modification
and maintenance of flight data analysis software, and for use of
computer programs to provide post-flight data analysis and data
correlation products, including correlation of flight measurement data
with other data sources such as wind tunnel pressure data and design
limits on strain data. The programs normally used for data reduction are
STRESS/STRAIN, COPP, and IGNITION OVERPRESSURE for use with operational
instrumentation measurements. Maintain these packages in operational
form as the host operating systems are updated.

\*\*\*From Schedule A, SMD, 7.1.3.1.13:

5.1.3.1.7 Provide programming support for developing and maintaining
computer interfaces required for transfer of graphic models between the
various CAD/CAM systems such as Calma, McAuto, and Anvil.

\*\*\*From Schedule A, SMD, 7.1.3.1.14:

5.1.3.1.8 Provide programming support to incorporate improvements,
improve correlation, and extend capability of the soft docking/berthing
computer programs and maintain and improve berthing analysis through
inclusion of Remote Manipulator System (RMS) characteristics, Orbiter
modal and RCS characteristics, modifications for "Smart" actuators, and
actuator test data; provide engineering and programming support to
conduct parametric berthing (or docking) analyses; to maintain and
improve the soft docking program; and to maintain and update a user's
guide for the program.

\*\*\*From Schedule A, SMD, 7.1.3.2:

**5.1.3.2 Analysis Methods Development and Data Base Maintenance -**
This function defines design guidelines and evaluates analytical
techniques which may be used in the design process. Also required is the
development and maintenance of design and operational data bases to
support analytical studies and design assessments. The following are
representative tasks the contractor shall perform:

5.1.3.2.1 Provide development and maintenance of data and math models in
support of structural system analyses. The large volume of data, which
includes Shuttle math models, payload models, forcing functions, and
other related structural data, requires the establishment of a well
managed and controlled data base with a catalogue accessible via demand
terminal. Maintain data and update as new data becomes available.

5.1.3.2.2 Develop maintain, and operate an integrated thermal data base
consisting of thermal properties data, integrated geometric math models,
integrated thermal math models, external thermal environment/data
results. The data base shall be used to access and control the
integrated thermal models and analysis results generated by NASA JSC and
contractors.

5.1.3.2.3 Provide analytical support for correlation of math models with
ground test and flight data, the refinement of these models, and the
incorporation of revisions into the data bases and the assessment of
correlation by payload developers including space station components.

\*\*\*From Schedule A, SED, 7.1.4:

5.1.4 Engineering Studies and Assessments

This function is to perform engineering trade studies, analyses, data
evaluations and assessments with regard to spacecraft hardware design,
development, certification, flight test and operation of the structural,
thermal, materials, and mechanical integrity of spacecraft systems and
subsystems to assure safety of flight. The following are representative
tasks the contractor shall perform:

5.1.4.1 Provide engineering support for the evaluation and correlation
of flight measured data with data from other sources (such as wind
tunnel pressure data) and design limits.

5.1.4.2 Provide analytical support for data processing, review,
evaluation, and correlation of flight data for integrated payloads
performance evaluation.

5.1.4.3 Provide analytical support for the assessment of loads and
structural response analyses of selected hardware including forcing
function development and response analyses; develop selected coupled
Shuttle/payload and Shuttle/space station system modal characteristics
from data base files; perform transient and quasi-static analysis for
selected configurations and conditions with NASTRAN or other codes using
the coupled modal characteristics; and investigate methods of loads
analysis which include the effects of interface sliding friction and
system nonlinearities.

5.1.4.4 Provide analytical engineering support for STS and advanced
programs TPS ground and flight testing, including the development of new
models and/or the integration of existing mathematical models and
boundary conditions of Shuttle and advanced programs hardware in the
test environment. Include test data formatting, data reduction, and
correlation of analytical results with thermal test data.

5.1.4.5 Conduct materials failure analysis for all JSC programs,
aircraft operations, and Center support. Failure analysis shall include
metallurgical analysis, chemical analysis of materials,
scanning-electron microscopy of fracture surfaces, mechanical and
physical properties evaluation, and laboratory testing.

5.1.4.6 Provide engineering support of evaluation, review, prediction
and verification of the adequacy of the molecular, particulate and light
environment of space station and other spacecraft; and develop
guidelines for allowable contamination levels and methods to predict and
assess the levels and effects of the contamination environment on
spacecraft operations. This information shall be provided to the
engineering and science community to assure that adequate contamination
related data are available prior to hardware fabrication and flight
operations.

5.1.4.7 Provide Nondestructive Evaluation (NDE) support for all JSC
programs, aircraft operations, and center support. This effort shall
include development and maintenance of NDE reliability data; production
of NDE calibration standards; generation of NDE procedures;
investigation of new NDE techniques; and resolution of program NDE
issues.

5.1.4.8 Provide analytical data and documentation to support
spacecraft/experiment meetings and activities related to contamination
environment issues.

5.1.4.9 Develop and operate analytical models for predicting ambient
density in the low earth Orbital environment and generate fluency levels
for varying conditions.

5.1.4.10 Provide engineering support in planning, scheduling, and
accomplishing tasks required in the requirements definition, design, and
evaluation of new mechanical systems. This effort shall include
development of instrumentation requirements, review of specifications,
performing analysis, test support, data reduction, correlation of
analytical predictions with ground test and flight data.

5.1.4.11 Provide engineering support for the performance and evaluation
of stress analyses of mechanical system hardware; and provide assistance
in the review of structural certification documentation and in
performing required supplementary certification analysis and
documentation.

5.1.4.12 Provide analysis and design effort to evaluate manipulator,
docking/berthing, and automation systems designs.

5.1.4.13 Provide engineering support for spacecraft missions including:
processing of flight data, determining flight performance, resolving
anomalies, maintaining flight performance history files to identify
performance trends, designing new GFE flight hardware for unique mission
requirements; and redesign, modifications and refurbishment of existing
GFE hardware.

5.1.4.14 Provide support for design reviews, evaluation of changes to
documentation (e.g., Interface Control Documents (ICD's) and Payload
Integration Plans (PIPs)), assessment of certification plans, and the
evaluation of design criteria and environments. Provide analyses to
assess the documentation and/or develop revisions.

5.1.4.15 Participate in program meetings and activities to monitor and
effect resolution of various issues; apprise personnel of significant
issues and action items discussed at the meetings and any
other-potential issues identified; maintain an up-to-date status of
integration activities and review changes to specific documentation such
as Interface Control Documents for potential impact; and perform
analyses to help resolve problems.

5.1.4.16 Provide engineering support to evaluate the need for and to
implement any refinements to design criteria and environments; develop
analytical predictions for the actual flight conditions, comparison
between analytical and flight data shall be a basis for evaluating
current design criteria and environments.

5.1.4.17 Provide engineering support in the area of materials and
processes for all spacecraft and payload activities:

5.1.4.17.1 Review and implement programmatic specifications,
requirements, ground rules and memoranda of understanding (MOU's).

5.1.4.17.2 Review and assess Material and Processes (M&P) related
program documentation.

5.1.4.17.3 Review and assess material usage in spacecraft hardware
design.

5.1.4.17.4 Review, assess, and resolve M&P related problems involving
stress corrosion, flammability, contamination, vacuum stability, fluid
compatibility, and age life.

5.1.4.18 Provide support by the review and evaluation of loads, loads
criteria, and load conditions as they relate to structural integrity and
operational capability. Include assessments of mathematical models and
stress analyses.

5.1.4.19 Provide analytical support and develop software (contamination
math models) for the prediction of contamination levels and effects in
the external space station/spacecraft flight experiment environment;
review contamination issues and apply the models for engineering
analyses as well as trade studies of contamination levels and possible
contamination effects.

5.1.4.20 Perform thermal analysis for definition of the overall thermal
environment, thermal performance, thermal boundary conditions for
detailed subsystem design and mission analysis, and thermal trade
studies.

5.1.4.21 Provide analytic support for the review, evaluation, and
certification of the structural integrity of spacecraft hardware to
assure safety of flight. Review documentation and perform analyses of
selected critical elements for static and dynamic, mechanical, and
thermal induced loads.

\*\*\*From Schedule A, 13.1.4

5.2 ENGINEERING STANDARDS AND PROCESSES

Provide planning, coordination, and documentation support for the
review, revision, rewrite, and creation of new and existing Engineering
standards, processes, and procedures. Research existing standards,
processes, and procedures. More specifically, this effort will involve
the evaluation, formulation, corrections, and updates of standards and
procedures for which the Engineering Directorate is the Office of
Primary Responsibility including (1) JSCM 8080, "JSC Design and
Procedures Standards Manual," (2) JPG 8500.4, "Engineering Drawing
System Manual," (3) JSC 23540, "Program Requirements Document
Guideline," and (4) JSC 25290, "JSC Metrication Plan," organize and
coordinate review meetings and management-boards, and coordinate inputs.

Provide support to identify requirements for placing specifications and
other documentation on a host computer system, to provide real-time
access to Engineering standards and procedures.

\*\*\*From Schedule A, SMD, 7.2:

5.3 LABORATORY/FACILITY SUPPORT SERVICES

5.3.1 General Support Services

This function covers those facility operations which are common to all
laboratories, facilities, and work areas encompassed within the
manufacturing, materials, and process technology laboratories (MMPTL).
The following are representative tasks the contractor shall perform:

5.3.1.1 Provide operational and maintenance support in technological
areas associated with testing in the MMPTL test facilities as directed
by NASA. This support shall include conducting tests; planning test
operations; operating the test facilities and ancillary equipment; minor
repair and maintenance of these facilities and support equipment;
generation of procurement specifications and initiation of procurement
for test support equipment and systems; maintenance of necessary
laboratory records; maintaining configuration control of laboratory
equipment; training and cross-training of contractor personnel;
laboratory safety; provisioning of equipment spares, tools, and
expendable materials necessary to perform tests and operate in MMPTL;
and preparing operational procedures and test reports.

Perform an annual chemical inventory in the laboratory facilities.

5.3.1.2 Maintain current schedules (including shift arrangements and
responsibilities) for each major facility, test program status, facility
resources, and other items which affect the management and efficiency of
major test activities.

5.3.1.3 Establish a records center library in each facility area for
indexing, filing, and storing of operational procedures, engineering and
configuration control drawings, test preparation sheets, photographs,
motion picture film, data records, test reports, and any other documents
pertinent to the operation of facility systems; and establish procedures
for the efficient maintenance and control of all such records.

5.3.1.4 Prepare test articles and specimens for testing, including
installation of transducers, sensing of data, signal conditioning and
recording, and processing and preparing data; document in laboratory
logs, operating and maintenance activities for major equipment; prepare
test procedures; and support test setup, test operations, test
evaluation, reporting of test operations, and reporting of test results.

5.3.1.5 Perform proof pressure tests on pressurized hydraulic and
pneumatic equipment in accordance with NASA safety regulations (see Part
II, Section A).

5.3.1.6 Install transducers on test articles; install cabling to signal
conditioning, recording, and display equipment; support system
adjustment, calibration, and verification; and document test setups and
operation with wiring diagrams, patch sheets, and system configuration
drawings and recording logs. Maintenance shall consist of preventive
measures plus minor equipment repairs and modifications. Equipment
within the scope of this task shall include analog transducers; strain
gage signal-conditioning; voltage and charge amplifiers; magnetic
tape-recorders; oscillographic recorders; digital data acquisition
systems; data conversion and display equipment; automatic control system
verification, monitoring, and trouble-shooting instruments; and timing,
control, and other associated equipment and systems.

5.3.1.7 Develop sensors and sensor installation techniques, modify data
acquisition and processing systems, and develop automatic control
systems that shall increase test capabilities, improve laboratory
efficiency, and support unique test requirements. This effort shall
include provisioning of special purpose recording and display systems;
modification of existing hardware to meet new requirements; assembly of
electronic devices and systems; verification of the specified
performance of such systems; developing operating and maintenance
procedures; and preparing detailed drawings and other documentation.

5.3.1.8 Provide technical support in areas of mechanical and electrical
engineering, structural dynamics and acoustics, chemical analysis,
non-destructive testing, failure analyses, entry environment simulation
using convective (arc jet) and radioactive heating techniques, laser
plasma diagnostic systems, computer based test data acquisition and
control systems, plasma, and property measurement systems, temperature
measurement systems, and pressure measurement systems. The support shall
consist of engineers, scientists, and technicians with the
responsibility-for engineering design, drafting using traditional and
CAD tools, fabrication, installation, checkout, integration, operating,
and technical documentation and configuration control.

\*\*\*From Schedule A, SMD, 7.2.2:

5.3.2 Federal Information Processing Resources (FIPR) Support

This function provides system and operations analysis and systems
management support to the manufacturing, materials, and process
technology FIPR system to insure its efficient and effective
utilization. The following are representative tasks the contractor shall
perform:

5.3.2.1 Provide system studies to aid in the determination of the
appropriate hardware to be acquired for the expansion and enhancement of
the data processing and analysis systems.

5.3.2.2 Provide general CAD/CAM support in the development and
maintenance of systems service type routines. Include development of
routines such as device drivers to support printers, tape drives, and
plotter that are unsupported by the CAD/CAM system supplier; researching
system problems and developing workarounds for the execution of special
tasks; provide support-for development of specialized graphic packages
to satisfy unique requirements such as drawing title blocks, view graph
templates, and other models required for system wide usage; and assist
in transfer of programs between computers, such as Harris 800 to the VAX
8600.

5.3.2.3 Provide development and maintenance of general purpose
programs/utilities in support of the manufacturing, materials, and
process technology FIPR user community placing special emphasis on the
development of CAD and DIGLAB graphics capabilities to assist the users
in its utilization and application; and support development of system
utilities, workload accounting and other system performance analysis
routines, and special purpose routines.

5.3.2.4 Perform systems and workload analyses to provide for efficient
and effective utilization of the manufacturing, materials, and process
technology computer systems. Areas to be addressed include hardware
configuration, SYSGEN parameters, operational procedures, and
programming practices. Provide documentation, recommendations, and
consultation. Provide the FIPR System Manager with the tools necessary
to manage the computer system.

5.3.2.5 Provide system analysis and procurement processing for
automation hardware and software. Activities include furnishing
technical assistance to system users and providing software to enhance
and extend automation capabilities.

5.3.2.6 Perform studies and participate in procurement decisions with
manufacturing, materials, and process technology personnel concerning
the appropriate hardware and/or software to be acquired for the
expansion and enhancement of the data processing and analysis systems
and related networks.

5.3.2.7 Modify data acquisition, and processing systems, and develop
automatic control systems that shall increase test capabilities, improve
facility efficiency, and support unique test requirements. This effort
shall include provision of special purpose recording and display
systems; modification of existing data acquisition and processing
hardware to meet new requirements; assembly of electronic devices and
systems; verification of the specified performance of such systems;
development of operating and maintenance procedures; and preparation of
detailed drawings and other documentation.

5.3.2.8 Develop software to support utilization of computer systems for
test data acquisition, automated test control, real-time information
display, and post-test data processing. This effort shall include
planning of software configuration, scheduling of software development,
preparing detailed documentation of the software, planning and
conducting tests to demonstrate and verify software performance,
developing operating procedures, and training system operators on
software utilization.

5.3.2.9 Operate and maintain data acquisition and display equipment and
computer systems.

\*\*\*From Schedule A, SMD, 7.2.6:

5.3.3. Materials Technology Laboratory

This function provides laboratory support for experimental
investigations and evaluation of materials programs. The following are
representative tasks the contractor shall perform:

5.3.3.1 Prepare TPS test articles; produce limited number of TPS tiles;
and conduct TPS environment compatibility tests.

5.3.3.2 Evaluate effects of atomic oxygen on spacecraft hardware;
evaluate fracture characteristics of various metallic components; manage
Shuttle flight experiments designed for the evaluation of reaction rates
of specific spacecraft materials; test materials; and prepare material
samples and portions of the flight hardware.

\*\*\*NOTE: Schedule A, SMD 7.2.6.3 went to NEW SOW Part II, Fracture
Mechanics and Fracture Analysis.

5.3.3.3 Evaluate chemical and physical properties of materials; conduct
chemical analysis as related to hardware and facility performance;
conduct failure analysis of both spacecraft and facility problems;
perform non-destructive evaluation of spacecraft/aircraft and facility
hardware; and conduct metallurgical analyses. Maintain laboratory
instruments including electron microscope, infrared spectrometer, gas
chromatograph-mass spectrometer, metallurgical sample preparation
equipment, thermal property evaluation equipment and mechanical property
testing equipment.

\*\*\*From Schedule A, SMD, 7.2.7:

5.3.4 Mechanical Systems Laboratory

This function provides laboratory support for advanced mechanism
research, development, test and operations, and experiment data analysis
for Shuttle, space station, and advanced programs. The following are
representative tasks the contractor shall perform.

5.3.4.1 Provide engineering analysis, mechanism design performance
evaluation, advanced mechanism demonstration, and software development.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

5.4 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

5.5 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

> Operate stockrooms for flight and flight related items including the
> preparation and maintenance of complete and adequate tool and
> equipment accountability records, and the submission of regular
> reports showing the use of items and the amounts available.
> Inventories shall be conducted in accordance with established JSC
> policy and procedures and equipment acquisition will be performed in
> compliance with the NEMS (NASA Equipment Management System).

6\. ENERGY SYSTEMS

\*\*\*From Schedule A, 5.0, PPD (EDITED to change references to Energy
Systems):

6.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

6.1.1 Program Management Support

**6.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program. For each function the following
are representative tasks the contractor shall perform:

**6.1.1.1.1 Payload Safety Analyses** - Provide support to analyze
safety review packages and other engineering data submitted by payload
providers to assure compliance with NASA safety requirements, including
NSTS 1700.7B-"Safety Policy and Requirements for Payloads using the
Space Transportation System;" provide detailed analyses and reviews for
batteries, solid rocket motors, pyrotechnic devices, and the Electrical
Power Distribution and Control (EPDC) system; and coordinate with
personnel in other technical disciplines such as materials, structures
and mechanics, cargo integration, and avionics.

**6.1.1.1.2 Pyrotechnic Engineering** - Provide engineering and
technical support for the review of pyrotechnic designs and performance
requirements; review firing systems, evaluate pyrotechnic hardware to
assure capability to satisfy the requirements, and assessment of safety,
reliability, and maintainability of candidate pyrotechnic systems; and
provide full-time drafting support using the Calma computer-aided
drafting system to generate and update drawings relative to the
pyrotechnic hardware and associated test fixtures.

**6.1.1.1.3 Battery Engineering** - Provide support for the review of
battery requirements and battery circuit designs including assessment of
performance safety, reliability, testing methods, and certification and
qualification criteria; prepare documentation summarizing the findings;
provide support for battery testing including the preparation of test
requirements, development of test plans, performance of tests,
evaluation of test results, and the preparation of all test
documentation; and provide battery safety consultation to the JSC
industrial safety organization relative to in-house battery
installations such as emergency lighting, emergency communications power
and battery backup systems.

**6.1.1.1.4 Government Furnished Equipment (GFE) Wiring** - Provide
engineering for completing the development of the JSC GFE Wiring
Handbook to document electrical wiring requirements for GFE hardware.

**6.1.1.1.5 Electronic Documentation and Tool Support** - The contractor
shall maintain and administer the electronic data systems and tools used
to support Energy Systems. Effort will include maintenance and
administration of Mars, maintenance of ISO 9000 documentation, Energy
Systems Web pages, and maintenance and administration of the UNIX-based
workstations. This includes system administration, network interfaces,
software upgrades, and user assistance and training.

**6.1.1.1.6 Dynamic Analysis Work** - The contractor shall conduct
steady-state, transient, and diagnostic/failure analyses of Orbiter
fluid systems and associated components, including, MPS, OMS, RCS, APU,
hydraulics, fuel cells, IN-Situ Propellant Resource Utilization (ISRU),
and Power Reactant Storage and Distribution. The contractor shall
conduct analysis to assess the effects of fluid/structural interaction
on fluid systems and associated components.

**6.1.1.1.7 Space Station Propulsion Support** - The contractor shall
provide propulsion system specialists concerning Russian propulsion
systems to enable technical understanding of their impact on the
International Space Station Program. The contractor shall support the
design reviews and Technical Interchange Meetings (TIMs) in both the
U.S. and abroad.

**6.1.1.1.8 Modeling and Analysis Support** - Develop and maintain
computational tools required for analysis of subsystem or component
performance and resolution of anomalies or concerns; perform
modifications and enhancements to the software to extend system modeling
capability, provide more flexible user interfaces, or integrate data
products from other analysis tools or data bases; and train the
Government and other contractor personnel on the utilization and
modification of the associated software.

**6.1.1.1.9 Programming and Documentation Support** - Provide
programming support to the modeling activities discussed above; provide
maintenance and enhancement of the software for the Engineering Diary
System, the principal data base used by Energy Systems subsystem
managers for documentation of subsystem configurations, performance, and
other historical data as well as for inventories of file cabinet
contents; and organize, document, and manage subsystem engineering
information as well as log, file, search, and retrieve documentation and
data from the document library maintained for the use of subsystem
management personnel.

6.2 LABORATORY/FACILITY SUPPORT SERVICES

6.2.1 General Support Services

The tasks in this function are unique to the Energy Systems
laboratories/facilities and are common to all the
laboratories/facilities listed below. The following are representative
tasks the contractor shall perform:

6.2.1.1 Provide mechanical shop functions such as welding, cutting,
machining, finishing, and assembling of various materials into test
fixture configurations.

6.2.1.2 Provide materials analysis services such as liquid and gas
sampling and analysis, preparation of special chemical mixes, materials
identification and test article chemical-related failure analysis.

6.2.2 Electrical Power Systems Laboratory (EPSL)

6.2.2.1 This function supports the Electrical Power Systems Laboratory
which includes the following: JSC Shuttle Electrical Power Distribution
and Control (EPDC) Breadboard; a Laboratory Data Management System
(LDMS); a High Voltage Test Bench (HVTB); electrical power source and
electrical load simulators; and computer based work stations to support
math modeling, software simulation, software program development and
data reduction. The EPDC breadboard supports hardware performance test
and evaluation, circuit analyses, interface compatibility evaluation and
anomalies investigation. The LDMS provides a fast accurate means of
gathering and recording data while performing various analytical
functions. The HVTB provides a means of testing and evaluating wiring
and distribution components up to 300 volts dc. The following are
representative tasks the contractor shall perform:

6.2.2.1.1 Perform specific EPDC tasks in the support of the Space
Shuttle and advanced space vehicle programs; evaluate EPDC systems and
components through a program of electrical and environmental testing and
perform analyses of the total spacecraft electrical power distribution
system; and maintain, modify, and operate equipment and systems of the
EPSL.

6.2.2.1.2 Operate and maintain the modified EPDC breadboard and prepare
test procedures, conduct tests, evaluate data, and provide documented
results.

6.2.2.1.3 Conduct environmental tests and electrical impedance tests on
subsystems or components of equipment within the scope of the specific
task.

6.2.2.1.4 Operate and maintain an electrical model of the fuel cell used
to supply dc power onboard the Shuttle.

6.2.2.1.5 Develop and operate simulated Shuttle loads; provide the
mechanism for driving and controlling the load simulators.

6.2.2.1.6 Develop, maintain, modify, and operate a High Voltage Test
Bench (HVTB) with electrical power source and load simulators,
distribution and control devices, and a data bus.

6.2.2.1.7 Develop software programs for the LDMS, the HVTB data bus,
operation/control of programmable EPDC devices and equipment, math
models and automated control programs such as the Advanced Electrical
Power Management Techniques for Space Systems (ADEPTS) development task.

6.2.2.1.8 Maintain files (software or hard copy) of reproducible copies
of breadboard configuration control drawings, test configuration
sketches, procedures, results, and reports.

6.2.2.1.9 Provide support for development of electrical power
distribution test systems in the Control/Actuation and Power System
Laboratory. Includes relocation of any test structures and capabilities
of the EPSL on an incremental, timely basis with no detrimental
interruption of existing program support.

6.2.3 Energy Systems Test Area (ESTA)

6.2.3.1 The contractor shall provide environmental exposure and flight
systems performance testing at ESTA. The contractor shall provide
support for the operation of the ESTA test facilities and test support
facilities (buildings 350, 351, 353, 354, 355, 356, 357, and 359),
including operations, maintenance, and procurement activities required
to perform tests of development and flight hardware in the ESTA complex.
The work will be performed per ESTA General Operating Procedures Manual
(GOPM).

6.2.3.2 Provide the Energy Systems Test Area (ESTA) metrology laboratory
functions such as the maintenance and calibration of various transducers
and measuring equipment and prepare the associated procedures and
records in accordance with JSC directives in the area of metrology.

6.2.3.3 Provide cleaning and pressure certification for fluid systems
and components which include procedural disassembly, cleaning,
reassembly, packaging, and record keeping in accordance with JSC
directives and ESTA General Operating Procedures. These activities are
accomplished in a preclean room and clean room rated at Level 10,000.

6.2.3.4 Provide electronic repair for maintenance of laboratory
equipment and provide a fabrication/design capability for special
digital and analog control packages.

6.2.3.5 Provide drafting services in support of test program and test
facility documentation.

6.2.3.6 Develop and maintain near real-time work schedules that
delineate test program status, facility resources, shift arrangements,
and other factors pertinent to test accomplishment. The normal mode of
operation is single shift; however, multishift coverage may be required
for test program support.

6.2.3.7 Provide operational test article interfacing, facility
engineering, facility procedure preparation, interface control
documentation and repair functions to maintain test response and test
continuity. Examples of systems to be maintained and operated in the
ESTA facilities are: signal conditioners, FM and digital recording
systems, digital and analog control systems, computers, cryogenic
systems, propellant systems, laboratory test equipment, steam systems,
high-pressure fluid systems and non-utility power generation systems.

6.2.3.8 Provide for personnel training/certification and safety services
specifically related to each ESTA activity. Safety concerns include the
use of propellant suits, breathing air systems, and special personnel
protective devices associated with propellants, cryogenics,
high-pressure fluid systems, laboratory chemicals and protection against
static electricity. Provide for certified support to the ESTA
laboratories in the areas of: high-pressure fluid systems,
earth-storable propellant handling, cryogenics operations,
instrumentation, high-energy density battery handling, and flight
qualification for zero "G" test operations. Develop and maintain near
real-time safety procedures to prevent safety incidents and facilitate
egress from potentially hazardous operations.

6.2.3.9 Provide procedures to handle routine and emergency propellant
situations that require personnel be physically fit for propellant
operations and properly certified in the use of personnel protective
equipment. Propellant handlers must successfully undergo a special
physical examination administered by the JSC Clinic.

6.2.3.10 Provide data management functions for acquiring, handling,
processing and storage of test data. All test setups and configurations
are considered test data and shall be documented by ESTA test number and
shall include wiring diagrams, patch sheets, system configuration
drawings, and recording logs.

6.2.3.11 Provide warehouse functions for controlled storage of materials
and specialized test equipment. Equipment will be stored and issued for
test as required. Data base of stored equipment, including salient
features and condition, will be maintained to aid in utilization.

6.2.4 Energy Systems Technical Discipline Facilities

The following are representative tasks the contractor shall perform:

**6.2.4.1 Propulsion Test Facility** - Research, develop, evaluate, and
qualify present and future Energy Systems hardware including the
reaction control system and auxiliary power units. Operate the facility
to handle earth-storable propellants and operate the altitude chamber,
steam system, and operate all digital, analog, and control
instrumentation.

**6.2.4.2 Power Systems Test Facility** - Support engineering and
developmental testing on flight power generation and cryogenic fluid
components. Investigate thermal, transient, life expectancy, system
optimization, and failure modes on hardware. A significant amount of the
activity in this facility involves the use of liquid and gaseous
hydrogen, oxygen, and nitrogen. Test articles subjected to test in this
facility include batteries, heat exchangers, fuel cells, high-pressure
vessels, pumps, and potentially hazardous materials used in evaluating
phase mange systems.

**6.2.4.3 Fluid Systems Test Facility** - Evaluated components, systems
and subsystems in terms of life cycles, proof and burst pressure
verifications, flow rates, materials compatibility, performance tests,
and leakage characterization. Provide test operations support to
high-energy battery testing and disposal, regenerative fuel cell
systems, high-pressure fluid systems, and compatibility tests involving
earth-storable propellants.

**6.2.4.4 Thermal Vacuum Test Facility** - Provide support for subsystem
and component testing requiring altitude and thermal environment to
assess leak rates, outgassing, and general performance assessments.
Additionally, this facility houses the central computing hardware for
the ESTA and the computing hardware that supports Energy Systems.

**6.2.4.5 Pyrotechnics Test Facility** - The contractor will not be
required to provide test support to this facility, although the
contractor shall provide general support services such as calibration,
machining, electronic support, as described for all facilities in
Section 6 of this statement of Work.

**6.2.4.6 Control/Actuation and Power System Laboratory** - Support
engineering and developmental testing of electromechanical/hydraulic
actuators for space flight applications and test and evaluate electrical
power, distribution, and control systems. It is planned that this
facility will eventually contain activities currently resident in the
Electrical Power Systems Laboratory and the Thermal Vacuum Test
Facility. Plans are being formulated to relocate equipment from these
facilities and support will be needed to affect this transition.

6.2.5 Federal Information Processing Resources (FIPR) Support

The following are representative tasks the contractor shall perform:

6.2.5.1 Provide programming and operational services for the Energy
Systems computing system and associated network peripherals.

6.2.5.2 Develop and maintain software in support of computer systems for
test acquisition, automated test control, real-time information
management, and post-test data processing. This effort includes planning
of software configuration, scheduling of software development and
preparing detailed documentation of the software. Plan and conduct tests
to demonstrate and verify software performance, develop operating
procedures, and train system operators on software utilization.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

6.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

6.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

7\. AUTOMATION, ROBOTICS, AND SIMULATION

\*\*\* From Schedule A, 6.0, AUTOMATION & ROBOTICS DIV

7.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

7.1.1 Program Management Support

This support includes responsibility for the engineering and technical
support to the Space Shuttle Program (SSP), space station, Advanced
Program Activities, and to those Project Managers responsible for
development, integration and Utilization of (1) manipulator and robotic
devices and (2) on-board systems management software.

**7.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program.

**7.1.1.1.1 Subsystem Management** - This function includes
responsibility for engineering and technical support for critical
technology development, trade studies, requirements definition, design,
analysis, development, integration, utilization and verification of (1)
onboard or in-situ systems management software applications, and (2)
manipulator and other robotic devices/end-effectors. This function also
includes real-time mission support, sustaining engineering functions,
and program documentation development. The following are representative
tasks the contractor shall perform:

7.1.1.1.1.1 Provide engineering and technical support for onboard, or
in-situ, systems management software. Functions performed by such
systems include systems level command and control
(automated/crew/ground) and systems level planning, scheduling,
procedures management, monitoring and controlling, and fault detection,
identification and recovery. These systems provide interactive,
intelligent human interfaces and provide adjustable levels of autonomy.
Assist in development of critical systems and in performing
human/automation/ground/onboard trade studies to define appropriate
functionally partitioned architectures and functional requirements for
such systems. Also supply assistance in establishing detailed system
architectures, design and design analysis, development, integration, and
validation and verification test planning and analysis, real-time
mission support and sustaining engineering functions.

7.1.1.1.1.2 Provide support in the sustaining engineering of space
manipulators and robots and vehicle onboard management software for the
following examples of activities: real-time mission support; performing
flight-to-flight flight software verification including developing test
requirements, reviewing test procedures and preparing test reports;
isolating and evaluating in-flight anomalies; supporting Flight
Readiness Reviews by reviewing and evaluating mission specific analyses
and reports, flight data files, mission rules and procedures; evaluating
mission specific flight software data sets; reviewing, evaluating and
updating operational maintenance requirements specifications documents
and operation maintenance instructions; and supporting operations
personnel and payload users in the development of planned operations
with flight manipulators and robots.

7.1.1.1.1.3 Provide assistance in the design and evaluation phases of
space manipulators and robot development. Examples include: evaluating
proposed designs for manipulators and robots; evaluating test
objectives, plans, procedures, and results from prime vendor
engineering, qualification and acceptance testing; developing test
objectives, plans and procedures and providing sponsor support to
engineering, qualification and acceptance testing of flight manipulators
and robots or their components performed in JSC facilities; developing
failure modes and effects analyses (FMEA's) and identifying critical
failures for inclusion into critical item lists; evaluating failure
analysis reports and problem closures; and developing detailed test
objectives for flight verification of manipulator and robots. The above
support is also required for engineering upgrades to existing flight
systems.

7.1.1.1.1.4 Provide support in the requirements development, design
evaluation and testing and sustaining engineering of manipulator and
robot handles (i.e., structure on a piece of hardware which the
manipulator or robot attaches to in order to maneuver the piece of
hardware). Logistics support shall also be required in some cases.
Provide support in the requirements development, design evaluation and
testing of hardware which is to be deployed, retrieved, maneuvered,
assembled, maintained or otherwise handed by space manipulators and
robots. This support will be with respect to the robotic compatibility
aspects of the system design.

**7.1.1.1.2 Other Multiprogram Support Functions** - The following are
representative tasks the contractor shall perform:

7.1.1.1.2.1 Provide support to intelligent software systems and robotic
technology development in the assessment, maturation and transfer of
technologies from laboratory to testbed to full-operational use in both
engineering and operations (ground and onboard or in-situ systems).
Applications of intelligent systems-technologies-include planning,
scheduling, design and design analysis, procedures generation and
management, systems monitoring and controlling, fault detection,
identification and recovery, and data analysis. Applications shall
provide interactive, intelligent human interfaces and shall provide
adjustable levels of autonomy.

7.1.1.1.2.2 Perform graphics/kinematic computer simulations analyses,
dynamic non-real-time computer simulation analyses, dynamic real-time
human-in-the-loop computer simulation analyses, and hardware testing in
ARS laboratories and other JSC facilities; develop analysis objectives
and plans, carry out simulations, and document results for the computer
simulation analyses; develop test objectives, plans, procedures, and
execute testing and document results for the hardware testing. These
analyses and tests will be used to develop requirements, validate design
against requirements and assess proposed operational uses of the
manipulators and robots.

7.1.1.1.3 Support the development and full deployment of intelligent
software system applications for real-time shuttle telemetry monitoring,
logging and analysis and for off-line Shuttle telemetry post flight
analysis. This responsibility includes requirements definition, design,
development, integration, verification, user training and operations in
facilities such as Mission Evaluation Room, the Mission Control Center,
the Combined Control Center, and future operations control and analysis
centers.

7.1.1.2 Shuttle - Unique

**7.1.1.2.1 Subsystem Management** - The subsystem management technical
support responsibilities are delineated in Section 7.

**7.1.1.2.2 Other Shuttle Support Functions** - The following are
representative tasks the contractor shall perform:

7.1.1.2.2.1 Provide assistance for real-time mission support for Shuttle
missions; perform flight-to-flight Shuttle Remote Manipulator System
(SRMS) flight software verification including developing Shuttle
Avionics and Integration Laboratory (SAIL) test requirements, reviewing
SAIL test procedures and preparing test reports; isolate and evaluate
in-flight anomalies of the SRMS and Shuttle grapple fixtures; support
Flight Readiness Reviews with respect to the SRMS and Shuttle grapple
fixtures by reviewing and evaluating mission specific analyses and
reports, flight data files, mission rules and procedures developed by
the Mission Operations Directorate; provide evaluation of mission
specific SRMS I-loads; review, evaluate, and update the Operational
Maintenance Requirements and Specification Document (OMRSD) and
Operation Maintenance Instructions (OMI) for SRMS and Shuttle grapple
fixtures.

7.1.1.2.2.2 Provide support for evaluating vendor designs for SRMS and
Shuttle grapple fixture hardware and software upgrades; assist in SAIL
testing of engineering and qualification units of SRMS components
including developing test requirements, providing support for reviewing
SAIL test procedures and preparing test reports; support and evaluate
engineering, qualification and flight unit testing of SRMS components
and Shuttle grapple fixtures at the vendor facility; develop failure
modes and effects analyses (FMEA) and identify critical failures for
inclusion in the critical items lists for SRMS and Shuttle grapple
fixtures; evaluate failure analysis reports and problem closures for
SRMS and Shuttle grapple fixtures; and develop detailed test objectives
(DTOs) for flight verification of SRMS and Shuttle grapple fixtures
upgrades.

7.1.1.2.2.3 Assist in providing Shuttle payload customer support to
users of the SRMS and Shuttle grapple fixtures by evaluating customer
requirements through the Cargo Compatibility Review and Cargo
Integration Review processes and by providing logistics support to the
payloads for Shuttle grapple fixtures.

7.1.1.2.2.4 Support the development and full deployment of intelligent
software system applications for real-time systems monitoring, data
logging and analysis and for off-line postflight analysis. This
responsibility includes requirements definition, design, development,
integration, verification, user training and operations in the Mission
Evaluation Room and the Mission Control Center.

7.1.1.3 Space Station - Unique

**7.1.1.3.1 Subsystem Management** - The subsystem management technical
support responsibilities are delineated in Section 7.

**7.1.1.3.2 Other Station Support Functions** - The following are
representative tasks the contractor shall perform:

7.1.1.3.2.1 Analyze with kinematic/graphics and real-time
person-in-the-loop computer simulations proposed space station assembly
sequences with respect to manipulator and robotic reach and clearance
capabilities, operator global viewing for collision avoidance and
operator local viewing of berthing interfaces; assist in defining and
assessing grapple fixture locations for space station elements, camera
locations for global viewing of assembly operations and camera locations
for local viewing-of assembly berthing interfaces; and provide support
for engineering evaluations of space station berthing interface designs
with respect to the capabilities of Shuttle Remote Manipulator System
(SRMS), space station Remote Manipulator System (SSRMS), and the Special
Purpose Dexterous Manipulator (SPDM).

7.1.1.3.2.2 Assist in establishing functional and performance
requirements for the SSRMS and SPDM; assist in establishing distributed
system architectures and structural/mechanical interfaces for the SRMS
and SPDM; provide support in developing requirements and plans for
end-to-end design verification of all integrated operating
configurations of the SSRMS and SPDM; perform graphics/kinematic
computer simulations analysis, dynamic non-real-time computer simulation
analyses, dynamic real-time person-in-the-loop computer simulation
analyses, and hardware testing in ARS laboratories; develop analysis
objectives and plans, carry out simulations, and document results for
the computer simulation analyses; develop test objectives, plans, and
procedures, execute testing and document results for the hardware
testing; and develop and update Space Station Program documentation such
as functional and performance requirements documents and verification
documents.

7.1.1.3.2.3 Provide engineering and technical support to the Mode Teams
for the space station, provide analyses, requirements definition,
integrated trade studies, and project coordination to provide support
for space station Level II and Level III requirements. Typical examples
include the ISE Mode Team and Command and Control Mode Team.

7.1.1.3.2.4 Provide engineering and technical support to the NASA JSC
Failure Environment Analysis Tool (FEAT) Project Manager, including
requirements definition, trade studies supporting FEAT design, FEAT
design, development and verification, FEAT integration with the
Technical Management Information System (TMIS) and the Space Station
Combined Control Center (SSCCC), critical technology development in
support of advanced capabilities for FEAT, user training, and project
management coordination.

7.1.1.3.2.5 Provide support in the evaluation of proposed space station
robotic interface standards.

7.1.2 Research and Development Support

7.1.2.1 Advanced Development

**7.1.2.1.1 Systems Engineering and Integration** - This function
includes responsibility for supporting NASA in the development of
requirements (from the system to the component level) in support of
assigned robotic and intelligent system development projects (including
project planning, Work Breakdown Structure (WBS) and task scheduling).
The following are representative tasks the contractor shall perform:

7.1.2.1.1.1 Provide configuration control and documentation on all
aspects of project development including drawings, test plans,
experiment plans, procedures, technical papers, summary reports, status
reports, and hardware and software documentation.

7.1.2.1.1.2 Conduct trade studies and perform system analysis to support
the robotic project development; provide input to the design process to
ensure that the overall robotic system will meet its design requirements
and objectives; and provide mechanical and electrical design support and
specification generation. Assist in the assembly, integration, and
checkout of assigned robotic systems including resolution of all system
problems encountered during the final assembly process.

**7.1.2.1.2 Intelligent Systems Engineering** - This function includes
responsibility for development and incorporation of advances in
intelligent systems in space systems, organizations, and programs for
the continual improvement of their effectiveness. The following are
representative tasks the contractor shall perform:

7.1.2.1.2.1 Provide in-depth knowledgeable support as participating
members of development teams that are not only developing and extending
technology, but also creating a state-of-the-art hardware and software
facility for such development. These technology areas include
monitoring, control and Failure
Detection/Isolation/Recovery/Reconfiguration (FDIR) knowledge based
systems, qualitative modeling, scheduling, computer vision, perception,
planning, spatial reasoning, and world modeling. Use supporting tools
including a network of engineering workstations with the X-Windows
System, Lisp based developmental platforms such as symbolics machines,
Lisp based tools such as Lucid Common Lisp with supporting graphics and
object oriented tools, KBVision for computer vision development,
simulation tools, and tools supporting various cognitive architectures
such as SOAR and REX/GAPPS in the R&D efforts. Also provide support of
multiple architectural approaches to robotic systems, such as functional
and behavioral architectures and variations of each.

7.1.2.1.2.2 Assist in technology development in intelligent software
systems for space systems design and analysis; operations procedures
design, analysis, and execution; space systems operations including
monitor and control, fault detection, identification, and
reconfiguration; planning and scheduling; and infrastructure support
(e.g., project management). Applicable intelligent software systems
technologies include knowledge-based systems; cognitive architectures;
qualitative systems modeling-for simulation, analysis, and operations
support; digraph modeling and analysis; planning and scheduling;
parallel processing, fuzzy logic; neural networks; and human interfaces
with intelligent systems.

7.1.2.1.2.3 Support the development of requirements for intelligent
software systems for current and advanced programs including operations
scenario development and analysis; trade studies supporting human,
automation, and robotics task allocations; critical technology
identification; and prototype software system design and development.

7.1.2.1.2.4 Conduct and support advanced development projects designed
to develop and demonstrate intelligent systems technologies in ground
and baseline/evolutionary space systems.

7.1.2.1.2.5 Support the development and full deployment of intelligent
software system applications including requirements definition, design,
development, integration, verification, user training, and operation of
fielded software intelligent system applications, both real-time and
non-real-time. Applications include ground-based systems such as those
used in the Operations Control and Analysis Centers, simulation
facilities, test and evaluation laboratories, and flight systems such as
flight experiments.

**7.1.2.1.3 Robotic Systems Engineering** - This function includes
responsibility for the planning and execution of advanced robotics and
autonomous robotic projects assigned by NASA. This support includes
project planning, design, analysis and reporting, and test. The
following are representative tasks the contractor shall perform:

7.1.2.1.3.1 Assist in technology development in intelligent software
systems for autonomous robotic systems design and analysis. Autonomous
robotic space systems operations include monitor and control, fault
detection, identification and reconfiguration; task and path planning;
and machine perception. Applicable intelligent software systems
technologies include knowledge-based systems, cognitive architectures,
qualitative systems modeling for simulation, analysis and operations
support, task and path planning, parallel processing, fuzzy logic,
neural networks, world modeling, machine vision, and human interfaces
with intelligent systems.

7.1.2.1.3.2 Support the development of requirements for robotic devices
and autonomous robotic systems for advanced programs including
operations scenario development and analysis, trade studies supporting
human, automation, and robotics task allocations, critical technology
identification, and prototype system design and development.

7.1.2.1.3.3 Support the development and full deployment of robotic
devices and autonomous robotic systems applications including
requirements definition, design, development, integration, verification,
user training, and operations of fielded robotic applications.
Applications include ground-based demonstration systems and flight
experiments.

7.1.3 Engineering, Scientific, and Analytical Tools

**7.1.3.1 Computer Program Development and Maintenance Support** - This
function provides the engineering to specify and integrate computer
hardware and software systems in computers and/on data acquisition
system(s), as required for control, data reduction and/or analysis. This
function also provides generic computer programming and engineering
analysis support for development, enhancement and maintenance of command
and control, advanced automation systems, manipulators, dexterous
robots, and robotic transportation analysis computer programs. The
following are representative tasks the contractor shall perform:

7.1.3.1.1 Develop, enhance, and maintain software, models, and tools
necessary to determine the functional, operational, and design
requirements for command and control, advanced automation systems, and
manipulator systems.

7.1.3.1.2 Evaluate software requirements, develop, test, and maintain
robotic software to assess manipulator systems performance. Development
of these tools shall be subject to approved software configuration
control and simulator validation plans.

7.1.3.1.3 Provide for software configuration control through a control
board under JSC authority and approval. Use software developed from this
effort to assess the ability of manipulator designs to meet operational
requirements by simulating performance on operational tasks.

7.1.3.1.4 Support engineering evaluations of robotic assembly and
maintenance tasks. These robotic capabilities include: development of
kinematic software to evaluate manipulator reach, clearance, operator
viewing requirements; maintenance and enhancement of software to perform
integrated robotic maintenance task verification involving multiple
manipulator systems; and development software to model mechanisms,
flight hardware and software, and environmental effects.

7.1.3.1.5 Provide for enhancement of user interfaces and engineering
tools for pre- and post-processing, and organizing and tracking
simulation data and results, including database systems development and
implementation of standards for software development, graphics
interfaces, interface definition, software modularity, and commonalty;
and administration of system hardware and software.

7.1.3.1.6 Develop, enhance, and maintain a real-time, non-real-time
simulation architecture capable of incorporating a variety of
manipulator and dexterous robot dynamic models. These capabilities
include rigid and flexible body dynamics algorithms, branched and closed
chain dynamics algorithms, as well as supporting servo control and
flight software models.

7.1.3.1.7 Maintain and operate a detailed, accurate, and complete
simulation data base and simulation configuration control system
including documentation logging, statusing and tracking system for all
simulation Change Requests (CRs).

7.1.3.1.8 Prepare test data for presentation and identify, scale,
combine, graph, and perform systematic checks to verify the accuracy of
all simulation models as implemented in simulations. The work shall
include graphic and numerical calculations, comparison and coordination
of data with results from independently developed computer programs.

7.1.3.1.9 Support the continuing evaluation and implementation of new
software development and maintenance techniques in the areas of
verification, validation, documentation, development standards, and
requirements management.

\*\*\* From Schedule A, 8.1.3.3, 8.1.3.4 SED:

**7.1.3.2 Simulator Development** - This function involves defining
hardware and software simulator requirements, committing these
requirements to software by way of math models, simulation executives,
and expert systems specifications, configuring the available hardware to
accommodate the software, integrating the computer models, expert
systems, and simulator hardware including human and/or spacecraft
systems hardware, and verifying the validity of the simulator. The
following are representative tasks the contractor shall perform:

7.1.3.2.1 Define all requirements for an effective simulation; establish
coordination with organizations which will use or obtain data from the
simulation; size the simulation in terms of labor, costs, and schedules;
develop work packages which will provide a detailed schedule, specific
task assignments, and formal review points for each task; define
facility requirements such as power, space, and cooling; and prepare a
verification plan which shall identify tests to establish the
operational validity of the simulation.

7.1.3.2.2 Convert simulation requirements into math models and expert
systems specifications and integrate them with a simulation executive
into a complete mathematical definition of the system to be simulated;
convert models and expert systems into source code to be compiled on the
computer and checked out as individual routines; check out total system
programs to determine and document system timing; identify and
accommodate data recording and reduction requirements; run test cases to
establish the validity of the integrated math model or expert system;
and provide a detailed technical requirements document.

7.1.3.2.3 Determine requirements for any human-tended stations involving
various controls and displays which must be provided and integrated into
the system; document and track mechanical and electronic design efforts;
provide procurement, checkout, and fabrication activities; and design
validation tests for equipment acceptance.

7.1.3.2.4 Interface and integrate all parts of the simulation into the
system including all human-tended work stations, scenes, recording
equipment, artificial intelligence systems, and flight hardware.

7.1.3.2.5 Perform validation tests on the simulator and supply recorded
data for analysis and determination of discrepancies submit as-built
documentation to establish configuration control; and identify and
document future changes.

\*\*\* From Schedule A, SED, 8.1.3.4, Simulator Update:

**7.1.3.3 Simulator Update** - This function involves keeping an
operational simulator current with both system design and requirements
changes. The following are representative tasks the contractor shall
perform:

7.1.3.3.1 Maintain two or more simulation configurations to accommodate
various support configurations. The following are representative tasks
the contractor shall perform:

7.1.3.3.2 Track approved systems and designs changes and determine
potential impact on the simulation; document changes determine schedule
and cost impacts; submit data through a review process for change
approval; and identify changes to verification tests.

7.1.3.3.3 Convert approved changes into math models, expert systems
specifications or other software and integrate them into the simulated
system; and modify, procure, install, and check out changes affect
hardware.

7.1.3.3.4 Convert math model and expert systems changes into source code
to be compiled and checked out; comply with overall timing constraints
when the changes are integrated into the total stem program; and revise
test cases to establish the validity of the altered math model and
expert systems.

7.1.3.3.5 Modify documentation to reflect the final change and submit to
the library for configuration control purposes.

7.1.3.4 Systems Engineering Simulation Laboratory

7.1.3.4.1 The following are representative tasks the contractor shall
perform:

7.1.3.4.1.1 Provide engineering and analytical support services and
general support to the SES Laboratory.

7.1.3.4.1.2 Provide customer interface support for each study that will
identify study requirements with simulation customers; determine which
requirements are routine and which require significant development;
implement routine requirements; coordinate development of non-routine
requirements; validate all requirements before sponsor use; ensure that
all simulation and data recording setup required by the customer is
available; support customer sessions to ensure reported problems are
promptly addressed; ensure the transfer of study data as requested; and
ensure required study documentation is published.

\*\*\* From Schedule A, A&R 6.2:

7.2 LABORATORY/FACILITY SUPPORT SERVICES

7.2.1 General Support Services

This general support area covers those functions which are common to the
laboratories of the ARS. The following are representative tasks the
contractor shall perform:

7.2.1.1 Provide design, construction, and operational verification of
special test systems including both hardware and software systems;
provide recommendations and evaluations of equipment, both facility and
test related; provide engineering specialists to ensure a technological
understanding is maintained for support system designs and/or testing;
provide special laboratory system-designs, procurements, installation,
implementation, verification, maintenance, and operational support.

7.2.1.2 Design, build up, operate, and conduct development tests and
evaluations on breadboard, prototype, and flight experimental equipment;
fabricate breadboards, test setups, and special engineering equipment in
accordance with engineering drawings, sketches, and specifications for
the test setups.

7.2.1.3 Train and certify all personnel with respect to the safe
operation of all laboratory and test equipment.

7.2.1.4 Provide calibrated/certified transducers, signal conditioning,
display and recording equipment, test facility, and test support systems
control instrumentation, for measurement of test parameters, control of
test support systems, and the recording of data by data acquisition
systems and ensure that calibration and certification are achieved in
compliance with JSC instructions (see Part II, Section A). In
cooperation with the JSC Calibration laboratory, develop schedules for
calibration/certification of transducers and instrumentation against
primary standards traceable to the National Bureau of Standards;
maintain calibration certification procedures, calibration and
certification records, and provide for the storage of test
instrumentation.

7.2.1.5 Provide a schedule showing all critical milestones associated
with laboratory operations; maintain the schedule with major
modifications incorporated on a routine basis; and there shall be an
annual schedule, reviewed quarterly, projecting the test load.

7.2.1.6 Produce documentation suitable for status determination of
systems for Test Readiness Review Boards; maintain a current work
control system which shall control the assignment and flow of work
within the contractor's organization, determine work status, produce
reports and current schedules of work status and develop coordination
with other facility work such as test preparation sheets (TPSs),
discrepancy reports (DRs), procedures, checklists engineering work
orders, and major facility rework.

7.2.2 SES General Support Services

This function provides capability of a sustaining nature with the
exception of providing or updating the equipment within the simulator
and test laboratories. The following are representative tasks the
contractor shall perform:

7.2.2.1 Maintain simulator operations daily logs and work in conjunction
with test sponsors to implement the sponsor test run matrix. An
operational period is 3.5 hours at a minimum schedule increment. Verify
that the simulator is functioning properly each morning by running a
series of test programs. Operators must have ready access to simulator
designers/programmers since changes are frequent in an engineering
simulation and operators are not often qualified to discuss these with
simulation sponsors. Maintenance engineering shall be provided to
troubleshoot a malfunctioning simulator. Preventative maintenance and
reparative maintenance support shall be required on first and second
shifts.

7.2.2.2 Provide and utilize an automated logistics inventory system to
account for all system spares, repair parts, and operational supplies.
The system shall also account for test equipment and its calibration
status and shall schedule calibration as required by quality standards.

7.2.2.3 Operate and maintain a library to control all documentation
associated with simulation facilities. This effort shall include both
vendor and in-house built equipment drawings, listings, manuals, system
software tapes and documentation, operational software tapes, disks,
change documentation, configuration control panel official minutes, and
simulation/testing data tapes. Maintain a complete master set of
documentation and provide for updating in accord with approved
modifications; make available updated copies to all users of record; and
use an automated system capable of retrieving documents or other stored
media.

7.2.2.4 Provide the capability to process recorded simulator and test
data, and accomplish in real-time or off-line using specially created
programs.

\*\*\* From Schedule A, SED, 8.2.1.5 Building Support Services:

7.2.3 Building Support Services

7.2.3.1 Define the building support services required by ARS technical
systems. This effort shall include the provision for electrical and
hydraulic power, air conditioning, facility modifications, special test
equipment, laboratory equipment, and personnel space. Based upon system
and subsystem designs, generate and maintain an equipment list which
contains equipment characteristics such as power requirements, cooling
requirements, and spatial dimensions; prepare laboratory layouts which
provide information on required power source size and location; and
prepare engineering specifications for the contracting and
implementation of the building support services, equipment and
modifications.

\*\*\* From Schedule A, A&R, 6.2.2 FIPR Support:

7.2.4 Federal Information Processing Resources /FIPR Support

This function includes the definition, acquisition, installation,
operation, maintenance, upgrade, and modification of data acquisition
computer hardware and software systems (including Artificial
Intelligence (AI) systems and networks) within Automation, Robotics, and
Simulation. The following are representative tasks the contractor shall
perform:

7.2.4.1 Operate the computer facility, including the computer-based
robotics systems, automation, Computer Aided Design (CAD), engineering
analysis, and laboratory operations. Upgrade and maintain the software
on all computer systems.

7.2.4.2 Specify and integrate computer software systems in computers as
required for control, data reduction, and/or analysis.

7.2.4.3 Assembly ARS computer complex requirements. Prepare necessary
system design, design specifications and documentation for procurement,
installation, verification, and implementation to insure the
requirements shall be satisfied.

7.2.4.4 Procure, schedule, install, verify, operate, maintain, and
upgrade the computer complex in a timely manner with minimal
perturbation to the ARS scheduled operations.

7.2.4.5 Procure, schedule, install, maintain, manage, and upgrade the
CAD computer network in a timely manner with minimal perturbations to
the CAD operations and the ARS computer scheduled operations.

7.2.4.6 Design, implement, and insure the continued operation of
computer systems networks and of the interfaces with other networks.
Expand and modify these systems.

7.2.4.7 Design and develop programs to automate and improve operations
and management information systems.

7.2.4.8 Provide user assistance during checkout and implementation of
computers.

7.2.4.9 Support computing applications with assistance in configuration
planning, capability reporting, schedule development, user help,
training, equipment/systems procurement, network design, documentation,
data base formation, laboratory modifications, and computer language
capabilities.

7.2.4.10 Provide for security in the acquisition of systems to insure
that all equipment purchased is consistent with JSC-computer security
policies.

7.2.4.11 Operate and maintain the various data and computer systems
associated with robotics laboratory operations.

7.2.4.12 Provide programming expertise in graphics, CAD, Xwindows,
simulation, robotics control, user interface design, and artificial
intelligence.

7.2.4.13 FIPR maintenance management shall not be required under the
first year of this contract.

7.2.5 The Automation, Robotics, and Simulation Laboratories

This function includes the responsibilities for establishing, operating,
and maintaining necessary test and laboratory facilities to evaluate,
verify, and validate robotic concepts and advanced intelligent systems,
as well as perform dynamic systems-level test training. The laboratories
and facilities of the ARS contain a variety of shops, laboratories, and
training facilities which are utilized for engineering development
testing and flight certification testing of automated and intelligent
systems, and robotics systems. In addition, the RD provides crew
training for manipulator and robotic operations; real-time mission
support; anomaly investigation and resolution; and flight procedure
development and verification. Also, ARS provides closed-loop dynamic
testing for automated assembly of large structures as well as
docking/berthing evaluations. The following are representative tasks the
contractor shall perform:

7.2.5.1 Support design of ground test support equipment and installation
and integration of test articles as specified in the test requirements.

7.2.5.2 Prepare plans and procedures for test conduct and operations and
prepare and implement test preparation sheets, detailed test procedures,
drawings, configuration change orders, checklists, procedures
Discrepancy Report (DR) disposition and other documentation pertinent to
laboratory operation.

7.2.5.3 Provide engineering and technician support to select and install
instrumentation for measuring test parameters (i.e., temperature,
pressure, flow, partial pressures, force, velocity, load, acceleration,
etc.) in test buildups, on test articles, and for flight systems.

7.2.5.4 Provide configuration control management for all laboratory FIPR
hardware and software and non-FIPR resources in order to ensure safety,
documentation of configuration changes, and to minimize spurious
electrical noise/Electromagnetic Interference (EMI) effects.

7.2.5.5 Operate and maintain computer-based data acquisition, display,
and control equipment and systems in support of all test operations,
including installation of transducers on test articles; cabling to
signal conditioning, recording and display equipment; and system
adjustment, calibration, and verification. Document test setups and
operation with wiring diagrams, patch sheets, and system configuration
control drawings and recording logs. Operate and maintain all laboratory
systems, including manipulator systems, data acquisition systems, robot
controllers, hand controllers, display terminals, and related laboratory
equipment in the performance of prescribed test objectives.

7.2.5.6 Modify data acquisition and processing systems, and develop
automatic control systems that shall increase test capabilities, improve
facility efficiency, and support unique test requirements. This effort
includes the provision of special purpose recording and display systems,
the modification of existing hardware to meet new requirements, and the
assembly of electronic devices and systems. Verify the specified
performance of such systems, develop operating and maintenance
procedures, and prepare detailed drawings and other documentation.

7.2.5.7 Develop and document software to control manipulators and
laboratory test support equipment to support utilization of computer
systems for test data acquisition, automated closed-loop test control,
real-time information display, and post-test data processing. This
effort includes planning of software configuration, scheduling of
software development, preparing detailed documentation of the software,
planning and conducting tests to demonstrate and verify software
performance, developing operating procedures, and training system
operators on software utilization.

7.2.5.8 Calibrate, provide continuity verification, and check-out of the
overall test setup, including end-to-end verification.

7.2.5.9 Provide and maintain laboratory and test communication systems
and closed circuit television systems.

7.2.5.10 Provide engineering and technician support in order to direct
and/or perform all test functions including coordination of events and
scheduling of activities.

7.2.5.11 Provide test direction, conduct, and operation of ARS
laboratories during checkout verification and operational periods which
involves starting and stopping of the equipment and observation of
automated systems.

7.2.5.12 Maintain operating logs on facilities, test items, and an
up-to-date status on the equipment and software which includes the
proper identification and filing of tapes, recorder paper rolls, and
similar basic raw data obtained from test and equipment verification
runs.

7.2.5.13 Identify candidate modifications and/or enhancements to the ARS
laboratories that shall facilitate both its operation and the ability to
accommodate state-of-the-art robotic technology development.

7.2.6 Bond Room Facility

This function supports the bond room facility which houses flight
hardware and flight related equipment under secure and controlled
conditions. The following are representative tasks the contractor shall
perform:

7.2.6.1 Provide for the receipt of flight and flight-related properties
into storage; maintain the hardware and equipment while in storage; and
issue to authorized users.

7.2.6.2 Operate and maintain a program stock inventory control system
that identifies and records all transactions necessary for compliance
with regulations contained in NHB 4100.1B.

\*\*\* From Schedule A, SED, 8.2.3 Facility Development/Upgrade:

7.2.7 Facility Development and/or Upgrade

This function involves the planning and development of test facility and
simulation systems capable of accomplishing the mission in support of
the various programs ongoing within the JSC. Inherent in this effort is
the procurement of required hardware and software, integrating this
equipment with in-house designed and built interfacing and special
purpose equipment into a facility as well as validating the system
performance for compliance with requirements. This task requires
detailed knowledge of real-time simulation, artificial intelligence
systems, computing equipment, systems and application software, high
speed electronics interfacing, space systems and systems analysis,
robotics systems, integration and checkout. The following are
representative tasks the contractor shall perform:

7.2.7.1 Support development of ongoing projects in order to determine
detailed facilities requirements including power, cooling, space,
lighting, storage, cable runs, and other mechanical and electrical
interfaces.

7.2.7.2 Coordinate and interface with other contractor and NASA groups
to implement facilities requirements related to new or changing
projects.

7.2.7.3 Determine requirements for special hardware and software to
support a development or modification effort; determine if a commercial
or in-line built approach is more cost and schedule effective; initiate
procurement or fabrication efforts; and maintain appropriate status
documentation during this cycle for reporting purposes.

7.2.7.4 Specify various stages of testing for equipment and software
validity including final integration tests with total simulation.

\*\*\* For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

7.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\* From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

7.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

8\. STRUCTURES AND MECHANICS

\*\*\*From Schedule A, 7.0 SMD:

8.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

8.1.1 Program Management Support

**8.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program.

**8.1.1.1.1 Subsystem Management** - The following are representative
tasks the contractor shall perform:

8.1.1.1.1.1 Provide engineering support for analysis and resolution of
subsystem anomalies, and for evaluation of candidate hardware
modifications. Perform analyses of critical components and correlate
analytical predictions with laboratory and flight measurements.

8.1.1.1.1.2 Assist in the certification review of the thermal,
mechanics, material, and structural aspects of the various spacecraft
systems using flight data and contractor analyses and/or tests.

8.1.1.1.1.3 Provide engineering support for subsystem/system
responsibilities regarding design, certification, update of placards,
and the determination of operational limits. Basic categories of work
under this task include ascent, descent, and abort loads and dynamic
assessments; on-orbit analyses of berthing (or docking), re-boost, crew
motion, and other load or dynamic events; flight data analysis and test
data reduction; and correlation of math models with ground test data.

8.1.1.2 Shuttle - Unique

**8.1.1.2.1 General Engineering** - This function defines design
guidelines and evaluates analytical techniques which may be used in the
design process. Also required is the development and maintenance of
design and operational data bases to support analytical studies and
design assessments. The following are representative tasks the
contractor shall perform:

8.1.1.2.1.1 Provide an assessment and refinement of design guidelines
for structural integration of payloads into the Shuttle vehicle to
evaluate analytical techniques which may be used to aid the payload
contractor in the design process. Maintain design criteria with
sufficient detail to allow a payload contractor to proceed with a
high-confidence preliminary design independent of Shuttle system
transient analyses. Preliminary load factors, coupled analyses, shock
(response) spectrum techniques, and base drive methods are identified as
the primary approaches. Use Shuttle flight data obtained to continually
evaluate design requirements and to redefine and implement the design
methods developed.

8.1.1.2.1.2 Provide the development, maintenance, data input, and
operation of an Orbiter Thermal Control System and Thermal Protection
System flight data base and graphics display capability for evaluation,
correlation, and archiving thermal flight data, including mission
anomaly data support during STS flights.

**8.1.1.3 GFE Project Support -** The contractor shall provide project
management support on the various GFE Projects undertaken by the
Division. Tasks for this type of support may include: development,
coordination, and maintenance of Project specifications, schedules, and
other documentation; coordination with Project customers; oversight of
project hardware subcontractors and/or other EA divisions.

\*\*\*NOTE: Schedule A, SMD 7.1.1.2.1.3 went to EM.

8.1.2 Research and Development Support

**8.1.2.1 Advanced Development** - Provide engineering support for
technology assessment and development in the areas of automation,
docking and berthing, and remote situation systems.

8.1.3 Engineering, Scientific, and Analytical Tools

**8.1.3.1 Computer Program Development and Maintenance Support -** This
function includes the responsibility of programming support of all
analysis programs used, being evaluated, and being developed.
Programming support shall encompass maintenance, consultation,
documentation, evaluation, and enhancements to existing programs, as
well as evaluation and development of new programs to support analysis
and presentation of data on computer systems utilized by JSC. The
following are representative tasks the contractor shall perform:

8.1.3.1.1 Provide support for development and modification of structural
dynamic models and response data bases and the development of analytical
software to support loads and dynamics analyses.

8.1.3.1.2 Develop a materials data base of fracture mechanics properties
and create software that can incorporate new materials data, and provide
access to the existing data base for plotting crack growth curves.

8.1.3.1.3 Provide maintenance, documentation, and consultation
programming support expertise for the existing Structures and Mechanics
analysis programs and their peripheral programs. Conversion of the
existing Structures and Mechanics analysis programs and their peripheral
programs for use on new or upgraded computer systems used by JSC shall
be developed, verified, and maintained within a configuration control
system.

8.1.3.1.4 Provide program upgrades and enhancements to existing
programs, and develop new programs to support engineering analysis and
presentation of data. Provide capability evaluations and programming
support upon delivery of new program segments; develop test math models
and run check-out problems to evaluate new analytical software, new
computer facilities and new systems; and document all engineering
studies.

8.1.3.1.5 Provide program development and software maintenance for
advanced interactive CAD/CAE graphics systems to support pre- and
post-processing of math models and data results, and advanced graphics
software.

8.1.3.1.6 Provide expertise for interfacing between system software,
policies and procedures, and the application programs used.

8.1.3.1.7 Provide programmer consultation and user support for thermal
analysis programs used in integrated thermal analyses and include
thermal program modification and enhancements to satisfy unique
requirements dictated by program analytical needs.

8.1.3.1.8 Provide engineering, computer program modifications, program
software consultation and user support for integrated payloads/advanced
space exploration programs/space station, Integrated Thermal Control
System (TCS) and Thermal Protection System (TPS) analysis using for
example, Thermal Synthesizer System (TSS), System Improved Numerical
Differencing Analyzer (SlNDA); Thermal Radiation Analysis System
(TRASYS) and other thermal programs and include definition and analysis
of requirements for these unique thermal analysis programs as well as
enhancements and maintenance associated with these programs.

8.1.3.1.9 Provide engineering and programming support for modification
and maintenance of flight data analysis software, and for use of
computer programs to provide post-flight data analysis and data
correlation products, including correlation of flight measurement data
with other data sources such as wind tunnel pressure data and design
limits on strain data. The programs normally used for data reduction are
STRESS/STRAIN, COPP, and IGNITION OVERPRESSURE for use with operational
instrumentation measurements. Maintain these packages in operational
form as the host operating systems are updated.

8.1.3.1.10 Provide programming support for developing and maintaining
computer interfaces required for transfer of graphic models between the
various CAD/CAM systems such as Calma, McAuto, and Anvil.

8.1.3.1.11 Provide programming support to incorporate improvements,
improve correlation, and extend capability of the soft docking/berthing
computer programs and maintain and improve berthing analysis through
inclusion of Remote Manipulator System (RMS) characteristics, Orbiter
modal and RCS characteristics, modifications for "Smart" actuators, and
actuator test data; provide engineering and programming support to
conduct parametric berthing (or docking) analyses; to maintain and
improve the soft docking program; and to maintain and update a user's
guide for the program.

**8.1.3.2 Analysis Methods Development and Data Base Maintenance -**
This function defines design guidelines and evaluates analytical
techniques which may be used in the design process. Also required is the
development and maintenance of design and operational data bases to
support analytical studies and design assessments. The following are
representative tasks the contractor shall perform:

8.1.3.2.1 Provide development and maintenance of data and math models in
support of structural system analyses. The large volume of data, which
includes Shuttle math models, payload models, forcing functions, and
other related structural data, requires the establishment of a well
managed and controlled data base with a catalogue accessible via demand
terminal. Maintain data and update as new data becomes available.

8.1.3.2.2 Develop, maintain, and operate an integrated thermal data base
consisting of thermal properties data, integrated geometric math models,
integrated thermal math models, external thermal environment/data
results. The data base shall be used to access and control the
integrated thermal models and analysis results generated by NASA JSC and
contractors.

8.1.3.2.3 Provide analytical support for correlation of math models with
ground test and flight data, the refinement of these models, and the
incorporation of revisions into the data bases and the assessment of
correlation by payload developers including space station components.

8.1.4 Engineering Studies and Assessments

This function is to perform engineering trade studies, analyses, data
evaluations and assessments with regard to spacecraft hardware design,
development, certification, flight test and operation of the structural,
thermal, materials, and mechanical integrity of spacecraft systems and
subsystems to assure safety of flight. The following are representative
tasks the contractor shall perform:

8.1.4.1 Provide engineering support for the evaluation and correlation
of flight measured data with data from other sources (such as wind
tunnel pressure data) and design limits.

8.1.4.2 Provide analytical support for data processing, review,
evaluation, and correlation of flight data for integrated payloads
performance evaluation.

8.1.4.3 Provide analytical support for the assessment of loads and
structural response analyses of selected hardware including forcing
function development and response analyses; develop selected coupled
Shuttle/payload and Shuttle/space station system modal characteristics
from data base files; perform transient and quasi-static analysis for
selected configurations and conditions with NASTRAN or other codes using
the coupled modal characteristics; and investigate methods of loads
analysis which include the effects of interface sliding friction and
system nonlinearities.

8.1.4.4 Provide analytical engineering support for STS and advanced
programs TPS ground and flight testing, including the development of new
models and/or the integration of existing mathematical models and
boundary conditions of Shuttle and advanced programs hardware in the
test environment. Include test data formatting, data reduction, and
correlation of analytical results with thermal test data.

8.1.4.5 Provide engineering support in planning, scheduling, and
accomplishing tasks required in the requirements definition, design, and
evaluation of new mechanical systems. This effort shall include
development of instrumentation requirements, review of specifications,
performing analysis, test support, data reduction, correlation of
analytical predictions with ground test and flight data.

8.1.4.6 Provide engineering support for the performance and evaluation
of stress analyses of mechanical system hardware; and provide assistance
in the review of structural certification documentation and in
performing required supplementary certification analysis and
documentation.

8.1.4.7 Provide analysis and design effort to evaluate manipulator,
docking/berthing, and automation systems designs.

8.1.4.8 Provide engineering support for spacecraft missions including:
processing of flight data, determining flight performance, resolving
anomalies, maintaining flight performance history files to identify
performance trends, designing new GFE flight hardware for unique mission
requirements; and redesign, modifications and refurbishment of existing
GFE hardware.

8.1.4.9 Provide support for design reviews, evaluation of changes to
documentation (e.g., Interface Control Documents (ICD's) and Payload
Integration Plans (PIPs)), assessment of certification plans, and the
evaluation of design criteria and environments. Provide analyses to
assess the documentation and/or develop revisions.

8.1.4.10 Participate in program meetings and activities to monitor and
effect resolution of various issues; apprise personnel of significant
issues and action items discussed at the meetings and any
other-potential issues identified; maintain an up-to-date status of
integration activities and review changes to specific documentation such
as Interface Control Documents for potential impact; and perform
analyses to help resolve problems.

8.1.4.11 Provide engineering support to evaluate the need for and to
implement any refinements to design criteria and environments; develop
analytical predictions for the actual flight conditions, comparison
between analytical and flight data shall be a basis for evaluating
current design criteria and environments.

8.1.4.12 Provide support by the review and evaluation of loads, loads
criteria, and load conditions as they relate to structural integrity and
operational capability. Include assessments of mathematical models and
stress analyses.

8.1.4.13 Perform thermal analysis for definition of the overall thermal
environment, thermal performance, thermal boundary conditions for
detailed subsystem design and mission analysis, and thermal trade
studies.

8.1.4.14 Provide analytic support for the review, evaluation, and
certification of the structural integrity of spacecraft hardware to
assure safety of flight. Review documentation and perform analyses of
selected critical elements for static and dynamic, mechanical, and
thermal induced loads.

8.1.4.15 Provide structural and mechanical design, analysis, and
certification services for selected GFE and advanced projects, such as
the X-38 Program, Transhab, and Orbiter extended nose landing gear.

8.2 LABORATORY/FACILITY SUPPORT SERVICES

8.2.1 General Support Services

This function covers those facility operations which are common to all
laboratories, facilities, and work areas encompassed within the
Structures and Mechanics Laboratories (SML). The following are
representative tasks the contractor shall perform:

8.2.1.1 Provide operational and maintenance support in technological
areas associated with testing in the SML test facilities as directed by
NASA. This support shall include conducting tests; planning test
operations; operating the test facilities and ancillary equipment; minor
repair and maintenance of these facilities and support equipment;
generation of procurement specifications and initiation of procurement
for test support equipment and systems; maintenance of necessary
laboratory records; maintaining configuration control of laboratory
equipment; training and cross-training of contractor personnel;
laboratory safety; provisioning of equipment spares, tools, and
expendable materials necessary to perform tests and operate in SML; and
preparing operational procedures and test reports.

8.2.1.2 Maintain current schedules (including shift arrangements and
responsibilities) for each major facility, test program status, facility
resources, and other items which affect the management and efficiency of
major test activities.

8.2.1.3 Establish a records center library in each facility area for
indexing, filing, and storing of operational procedures, engineering and
configuration control drawings, test preparation sheets, photographs,
motion picture film, data records, test reports, and any other documents
pertinent to the operation of facility systems; and establish procedures
for the efficient maintenance and control of all such records.

8.2.1.4 Prepare test articles and specimens for testing, including
installation of transducers, sensing of data, signal conditioning and
recording, and processing and preparing data; document in laboratory
logs, operating and maintenance activities for major equipment; prepare
test procedures; and support test setup, test operations, test
evaluation, reporting of test operations, and reporting of test results.

8.2.1.5 Perform proof pressure tests on pressurized hydraulic and
pneumatic equipment in accordance with NASA safety regulations (see Part
II, Section A).

8.2.1.6 Install transducers on test articles; install cabling to signal
conditioning, recording, and display equipment; support system
adjustment, calibration, and verification; and document test setups and
operation with wiring diagrams, patch sheets, and system configuration
drawings and recording logs. Maintenance shall consist of preventive
measures plus minor equipment repairs and modifications. Equipment
within the scope of this task shall include analog transducers; strain
gage signal-conditioning; voltage and charge amplifiers; magnetic
tape-recorders; oscillographic recorders; digital data acquisition
systems; data conversion and display equipment; automatic control system
verification, monitoring, and trouble-shooting instruments; and timing,
control, and other associated equipment and systems.

8.2.1.7 Develop sensors and sensor installation techniques, modify data
acquisition and processing systems, and develop automatic control
systems that shall increase test capabilities, improve laboratory
efficiency, and support unique test requirements. This effort shall
include provisioning of special purpose recording and display systems;
modification of existing hardware to meet new requirements; assembly of
electronic devices and systems; verification of the specified
performance of such systems; developing operating and maintenance
procedures; and preparing detailed drawings and other documentation.

8.2.1.8 Provide technical support in areas of mechanical and electrical
engineering, structural dynamics and acoustics, chemical analysis,
non-destructive testing, entry environment simulation using convective
(arc jet) and radioactive heating techniques, laser plasma diagnostic
systems, computer based test data acquisition and control systems,
plasma, and property measurement systems, temperature measurement
systems, and pressure measurement systems. The support shall consist of
engineers, scientists, and technicians with the responsibility-for
engineering design, drafting using traditional and CAD tools,
fabrication, installation, checkout, integration, operating, and
technical documentation and configuration control.

8.2.2 Federal Information Processing Resources (FIPR) Support

This function provides system and operations analysis and systems
management support to the Structures and Mechanics FIPR system to insure
its efficient and effective utilization. The following are
representative tasks the contractor shall perform:

8.2.2.1 Provide system studies to aid in the determination of the
appropriate hardware to be acquired for the expansion and enhancement of
the data processing and analysis systems.

8.2.2.2 Provide general CAD/CAM support in the development and
maintenance of systems service type routines. Include development of
routines such as device drivers to support printers, tape drives, and
plotter that are unsupported by the CAD/CAM system supplier; researching
system problems and developing workarounds for the execution of special
tasks; provide support-for development of specialized graphic packages
to satisfy unique requirements such as drawing title blocks, view graph
templates, and other models required for system wide usage; and assist
in transfer of programs between computers, such as Harris 800 to the VAX
8600.

8.2.2.3 Provide development and maintenance of general purpose
programs/utilities in support of the Structures and Mechanics FIPR user
community placing special emphasis on the development of CAD and DIGLAB
graphics capabilities to assist the users in its utilization and
application; and support development of system utilities, workload
accounting and other system performance analysis routines, and special
purpose routines.

8.2.2.4 Perform systems and workload analyses to provide for efficient
and effective utilization of the Structures and Mechanics computer
systems. Areas to be addressed include hardware configuration, SYSGEN
parameters, operational procedures, and programming practices. Provide
documentation, recommendations, and consultation. Provide the FIPR
System Manager with the tools necessary to manage the computer system.

8.2.2.5 Provide system analysis and procurement processing for
automation hardware and software. Activities include furnishing
technical assistance to system users and providing software to enhance
and extend automation capabilities.

8.2.2.6 Perform studies and participate in procurement decisions with
Structures and Mechanics personnel concerning the appropriate hardware
and/or software to be acquired for the expansion and enhancement of the
data processing and analysis systems and related networks.

8.2.2.7 Modify data acquisition, and processing systems, and develop
automatic control systems that shall increase test capabilities, improve
facility efficiency, and support unique test requirements. This effort
shall include provision of special purpose recording and display
systems; modification of existing data acquisition and processing
hardware to meet new requirements; assembly of electronic devices and
systems; verification of the specified performance of such systems;
development of operating and maintenance procedures; and preparation of
detailed drawings and other documentation.

8.2.2.8 Develop software to support utilization of computer systems for
test data acquisition, automated test control, real-time information
display, and post-test data processing. This effort shall include
planning of software configuration, scheduling of software development,
preparing detailed documentation of the software, planning and
conducting tests to demonstrate and verify software performance,
developing operating procedures, and training system operators on
software utilization.

8.2.2.9 Operate and maintain data acquisition and display equipment and
computer systems.

\*\*\*From Schedule A, 7.2.3 Structures and Mechanics Division Support

8.2.3 Atmospheric Re-entry Materials and Structures Evaluation (ARMSEF)
and Radiant Heating Test Facility (RHTF)

This function supports the ARMSEF and RHTF. The ARMSEF is used to
simulate the temperature and pressure environments experienced by
spacecraft thermal protection systems during ascent, on-orbit, and
re-entry. Tests are conducted under high temperature supersonic
convective flow environments in support of characterizing the thermal
performance and stability of TPS materials samples, developing TPS
system design concepts, and certifying TPS final design for flight. The
RHTF is used to simulate the temperature and pressure environments
experienced by spacecraft during ascent, on-orbit, and re-entry. Tests
are conducted on full scale components under high temperature radiant
heating environments in support of evaluating thermal protection system
(TPS) design concepts and certifying TPS designs for flight. The
following are representative tasks the contractor shall perform for both
facilities:

8.2.3.1 Provide engineering support for technology assessment and
development in the areas of ascent, on-orbit, and re-entry environment
simulation using arc jet and radiant heating facilities in support of
the development, evaluation, and certification of advanced thermal
protection systems for application on the Shuttle Orbiter vehicle,
transatmospheric vehicles, and advanced entry vehicles for Space
Exploration Initiative.

8.2.3.2 Provide for the maintenance and enhancement of computer programs
(NATA and BLIMP) used to predict free-stream and local model conditions
for correlation with experimental measurements and extrapolation to
flight.

8.2.3.3 Perform engineering tasks associated with major facility or test
system design and development projects. This effort shall include
design, analysis, fabrication, installation, and checkout in support of
improving operational efficiency through automation and control,
extending operational performance limits, accommodating new and unusual
test requirements, improving simulation techniques consistent with
state-of-the-art advancements, improving techniques for test parameter
measurement and control and test article response.

\*\*\*From Schedule A, 7.2.4 Structures and Mechanics Division Support

8.2.4 Structures Test Laboratory (STL)

This function supports the STL, which is located in the high bay of
building 13, which is utilized for engineering development tests and
flight certification structural tests. The following are representative
tasks the contractor shall perform:

8.2.4.1 Perform materials property testing of metals and non-metals at
ambient pressure and vacuum conditions, as well as at elevated and
cryogenic temperature. Conduct tests on structural assemblies including
proof loads tests on actual flight hardware and ultimate load tests on
prototype structures that are required for flight certification. Data
acquisition and post-test data reduction of up to 256 channels of data
are required for most of the tests.

8.2.5 Vibration and Acoustic Test Facility (VATF)

Spacecraft are subjected to intense acoustic environments which induce
high levels of vibration in the spacecraft structure and equipment. In
addition, elastic structural interactions with propulsion and flight
control systems can produce low-frequency, high deflection flight
instabilities. This function supports the laboratories of the VATF which
are capable of performing the wide range of tests needed to evaluate all
aspects of acoustic, vibration, structural dynamic, and shock problems.
This facility has the capability for development, qualification, and
acceptance testing not only of aerospace vehicles and equipment, but
also nonaerospace equipment which is to be subjected to high-intensity
acoustic noise, vibration, and shock environments. Closed-circuit
television and major rigging operations are specifically excluded from
this task. The following are representative tasks the contractor shall
perform:

8.2.5.1 Develop and provide a data base of properties of acoustical and
vibration control materials and components, which are applicable to the
SSF program and use the data base to predict vibration and acoustic
levels for habitable modules on the SSF. The data base shall be
supplemented as materials/components are developed and shall include
information on other important properties of the materials/components.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

8.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

8.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

9\. AVIONICS SYSTEMS

\*\*\*From Schedule A, 2.0 TRACKING AND COMMUNICATIONS DIVISION (TCD):

9.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

9.1.1 Program Management Support

**9.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and Space Station Program.

**9.1.1.1.1 Subsystem Management** - This function includes the design,
development, fabrication, data analyses, flight qualification of
electronic equipment and supporting software for communications,
tracking, telemetry, and related functions. Design activities include
establishing the operating parameters, reviewing and analyzing the
proposed designs, and resolving system compatibility and interface
problems, and ensuring certification of flight hardware and software.
The following are representative tasks the contractor shall perform:

9.1.1.1.1.1 Design, develop, specify, evaluate, fabricate, and test
audio components, subassemblies, assemblies, and systems, such as
earphones, headsets, microphones, speakers, recorders, processing
distribution/signaling systems, command/synthesis processing and
networks. Provide engineering analysis studies and evaluations for
current and proposed audio system hardware. Perform design, development,
fabrication, and testing of the Audio Test Bed. Develop detailed test
procedures and formal reports.

9.1.1.1.1.2 Provide engineering and analytical support for the
conceptual design and fabrication of video systems to assess the
availability of state-of-the-art devices for potential spaceflight use,
for the preparation of documentation to establish system component
requirements, and for the review of drawings and documentation. Provide
support for equipment design and integration reviews at JSC or at other
NASA or contractor facilities including the preparation of statements of
work, program requirements documents, and interface control
documentation. Video items include television systems, video tape
recorder, and related equipment.

9.1.1.1.1.3 Support design and development of modulation and
demodulation equipment, command encoding and decoding equipment,
software and firmware for these functions, and related equipment and
subsystems. This includes system design, design of components and
subassemblies, fabrication, preparation of specifications and
requirements documentation, and the resolution of design and interface
problems.

9.1.1.1.1.4 Provide engineering support to design and fabricate text and
graphics system, survey available equipment, establish system
requirements and specifications, prepare design and procurement
documentation, and assist in evaluating and certifying the equipment for
flight use.

9.1.1.1.1.5 Perform research, design, development, fabrication, and
analysis of antenna components and subsystems. Analyze, synthesize, and
compute the radiation characteristics of antenna elements and advanced
array antennas. Measurements are required to validate the theoretical
and specified performance of antennas. Measured parameters include
radiation pattern amplitude and phase, gain, directivity, and
polarization. Use both near field and far field techniques to measure
radiation patterns and computer-aided design and engineering techniques
for antenna design, fabrication, and the display of measured data.

9.1.1.1.1.6 Provide research, design, development, analysis, and
fabrication of voice, video, and data transceivers. Support all
technical phases of radio frequency (RF) transceiver development
including analytical, fabrication, and performance evaluation. Hardware
to be fabricated includes hybrid microwave integrated circuit components
such as low noise amplifiers, high power amplifiers, phase shifters,
switching networks.

9.1.1.1.1.7 Perform design analysis of Government-Furnished Equipment
(GFE) and Contractor-Furnished Equipment (CFE) schematics and drawings
to assure compatibility of the equipment/subsystem with the environment
in which it must operate. Provide results of the analysis along with
recommended design changes. Provide engineering support to the
Electromagnetic Compatibility (EMC) Laboratory which includes
preparation of test procedures, design of test setups, and preparation
of test reports. Perform this task in accordance with the
Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC)
specifications currently in use by NASA and the DOD, and with
consideration of the equipment to be tested and its proposed usage. The
task also includes review of vendor test documentation and monitoring of
tests at vendor plants. Perform electromagnetic surveys of JSC
facilities to determine the electromagnetic environment in which new
systems or equipment must operate.

9.1.1.1.1.8 Perform design, development, fabrication, and evaluation of
radar, microwave, and/or optical tracking systems for space rendezvous,
capture and landing activities. Implement studies to determine
feasibility, recommend approaches for implementation, with accuracy
predictions, and error analyses. Perform analysis for components and
systems, design comparison, and performance evaluation. Develop concepts
into prototype hardware, perform verification tests, implement test
instrumentation, analyze test data, and report results.

9.1.1.1.1.9 Provide performance analyses of navigation aids (navaids)
for both ground-based and spaceborne systems. Use, maintain, and update
analytical tools for evaluating navaid data, cinetheodolite, radar, and
IMU-based reference position data. Use, maintain, and update the
software required to provide computer generated plots of navaid
measurements, navaid link errors, and navaid and reference ground track
and altitude profiles.

9.1.1.1.1.10 Support the design and development of software subsystems
encompassing software, firmware and networks for mode control,
redundancy management, status-monitoring, dynamic data bases, antenna
management, Failure Detection, Isolation and Recovery (FDIR), and data
management system interaction functions for communication and tracking
(C&T) systems including system design; design and fabrication of network
components and subassemblies; preparation of software; preparation of
specifications; and investigation and resolution of design and interface
problems.

9.1.1.1.1.11 Support sustaining engineering efforts involving C&T
hardware and software investigation and resolution of problems which
arise during flight missions.

9.1.1.1.2 Systems Engineering Technical Support

**9.1.1.1.2.1 C&T RF Coverage and Performance Analysis** - This function
includes the responsibility for the development of RF coverage and
performance predictions for spacecraft C&T links. As part of this
responsibility, mission-specific documents are developed and provided to
the spacecraft technical community for use in design definition,
preflight planning, real-time mission support, and post-flight data
evaluation. The following are representative tasks the contractor shall
perform:

9.1.1.1.2.1.1 Provide C&T RF coverage analyses that accept as input the
mission trajectory and attitude timelines, antenna pattern data,
blockage, link characteristics and parameters, and RF interference.

9.1.1.1.2.1.2 Provide engineering evaluations of computer simulation
data and comparisons with measured mission data.

**9.1.1.1.2.2 C&T System Performance Analysis** - This function includes
the responsibility for the development of circuit margin (or equivalent)
performance predictions for spacecraft C&T links. The following are
representative tasks the contractor shall perform:

9.1.1.1.2.2.1 Determine the pertinent C&T system characteristics and
parameters from specifications, technical literature, and original
research test data to perform the circuit margin analyses.

9.1.1.1.2.2.2 Provide engineering evaluations of the circuit margin data
and comparisons with measured data.

**9.1.1.1.2.3 C&T System Compatibility Analysis** - This function
includes the responsibility for performing C&T system compatibility
analyses between spacecraft and interfacing terminals, such as NASA
Tracking and Data Relay Satellite System (TDRSS), Shuttle, United States
Air Force (USAF) ground network, Shuttle payloads, space station and its
elements, space station payloads and free flyers, foreign and commercial
space station terminals, and USAF Global Positioning System (GPS). The
following are representative tasks the contractor shall perform:

9.1.1.1.2.3.1 Provide C&T system performance requirements analysis;
conduct analysis to support generation of interface control
documentation; provide analysis of engineering change proposals; perform
problem area analysis; provide test requirements and analyses; and
conduct system feasibility analysis.

**9.1.1.1.2.4 Communications Systems Test** - The following are
representative tasks the contractor shall perform: Provide, in support
of the Electronic Systems Test Laboratory (ESTL), end-to-end RF
communications systems project planning and analytical engineering
support in the development of major test programs for early systems
development, system performance verification, and operation integration
activities including engineering evaluations and system assessments
based on measured test results and performance comparisons with systems
specifications, mission requirements, and math models. Develop system
performance assessment concepts/techniques, and requirements, and
identify and resolve performance discrepancies including math model/test
data disagreements.

**9.1.1.1.2.5 Electromagnetic Effects Analysis** - This function
promotes overall electromagnetic system compatibility with emphasis on
reducing the problems generated by the interference of overlapping
electromagnetic fields both internal and external to the spacecraft
system. Electromagnetic system compatibility includes the utilization
of: electromagnetic effects requirements and procedures; knowledge about
the amount and nature of energy in the aerospace region through which
the spacecraft travels; knowledge about the physical characteristics of
the operational environment, such as rain, snow, moisture, lightning,
terrestrial radiation, galactic radiation, plasma, and other
environmental factors to which the system is subjected; and knowledge
about terrestrial and spaceborne communications systems which
potentially serve as a source of propagation of interference and
interaction. The following are representative tasks the contractor shall
perform:

9.1.1.1.2.5.1 Provide engineering support for electromagnetic effects
analyses.

9.1.1.1.2.5.2 Assist in identifying specific verification or
reverification items in direct support flight readiness reviews. Issues
relating to specific elements and elements interfaces shall be
identified and analyzed, and corrective action shall be recommended.

9.1.1.1.2.5.3 Perform technical analysis of internal and External
Electromagnetic Effects (EME) to the spacecraft system. Electromagnetic
effects include electromagnetic compatibility, lightning, electrostatic
discharge, and EMI generation due to plasma and radiation effects.

9.1.1.1.2.5.4 Support the EME Team activities including assessment of
requirements status and technical analysis.

9.1.1.1.2.5.5 Assist in the periodic assessment of EME specifications
and control plans, and make recommendations for updates.

9.1.1.1.2.5.6 Assist in evaluating changes, deviations, and waivers for
electromagnetic effects and perform EME analyses for changes,
deviations, and waivers generated.

9.1.1.1.2.5.7 Assist in review of the launch, landing, and on-orbit RF
environment threat assessments for the spacecraft and establish and
maintain a data base to provide visibility into the spacecraft's and the
spacecraft elements' electromagnetic effects compliance status.

9.1.1.1.2.5.8 Assist in the review of proposed design or operational
solutions with respect to electromagnetic effects interactions between
the spacecraft and other space systems to which it interfaces.

\*\*\*From Schedule A, 3.0 NCAD, 3.1.1.1:

9.1.1.2 Shuttle-Unique

**9.1.1.2.1 Guidance, Navigation and Control (GN&C)** - This function
provides the Guidance, Navigation, and Control (GN&C) system
verification activity required for the flight readiness assessment,
monitors GN&C systems performance during missions, and conduct of
special tests required in the laboratory or on the flight vehicle. It is
responsible for flight readiness verification for each shuttle mission
in the following areas: the integrated GN&C system hardware, software,
and functional capabilities for all mission phases from prelaunch
through landing roll out including the various abort modes; flight
control system response and stability for rigid and flex body for all
mission phases; sensor and effector hardware and software; redundancy
management; systems management; separation systems for the solid rocket
boosters and external tank; sequencing; hardware/software compatibility;
mated element interfaces; and remote manipulator system Interfaces. The
following are representative tasks the contractor shall perform:

9.1.1.2.1.1 Provide in-depth engineering support to each area of ASD
flight readiness verification responsibility. The technical capability
shall consist of the personnel and analytical tools to evaluate proposed
changes, audit I-loads, and define the test requirements for the SAIL to
verify the capability of the integrated systems to perform the planned
missions. Assist in the planning and coordination of the verification
requirements and participate in the test activity to evaluate results
and resolve discrepancies. Make recommendations concerning the flight
readiness, coordinate sign-off of the flight readiness statements, and
maintain files for each mission.

9.1.1.2.1.2 Provide mission support required by the Analysis Manager to
maintain a flight data file, log mission events and problems, and assist
in closing out problem reports.

9.1.1.2.1.3 Provide technical support for participation in various board
and panel meetings including the following: Shuttle-Avionics Software
Control Board; Shuttle Avionics Systems Review; Orbiter Avionics Systems
Review; Shuttle Data Control Board; Orbiter Software Test and Operations
(T&O) Board; Space Shuttle Checkout Panel; and Avionics Integration
Panel.

9.1.1.2.1.4 Provide the analysis of redundancy management (RM) hardware
and software systems. This includes RM requirements definition, design,
and documentation for Flight Control System (FCS) sensors, controls, and
effectors (Rate Gyro Assembly, Body Flap, Reaction Control System) for
Inertial Measurement Units (IMUs) and navigational aids (NAVAIDs), and
other avionics system components. This shall include Functional
Subsystem Software Requirements and change request (CR) review, CR
preparation, and mode team participation.

9.1.1.2.1.5 Provide analysis support for continuing capability
enhancement and development in the areas of Space Shuttle guidance,
navigation, and control. This engineering analysis support shall include
all effects of design, development, implementation, and verification of
guidance, navigation, and control systems. Provide support for
enhancements to existing capability and development of new capability in
guidance, navigation, and control.

9.1.1.2.1.6 Provide support for the development of new guidance,
navigation and control I-loads, both for unique flights and design
dependent I-loads.

9.1.1.2.1.7 Provide support for design, development, and implementation
of software and procedural automation enhancements to facilitate the
verification of correct values and correct mission selections of the
GN&C I-loads.

9.1.1.2.1.8 Provide technical support to I-load owners.

9.1.1.2.1.9 Provide technical support to Principle Function Managers
(PFM) to assess whether hardware changes affect software and vice versa.
The PFM must review pending Software Change Requests (SCR) for changes
that may affect the PF. Also, the PFM shall assist the Flight Function
Manager (FFM) and the Program Office in resolving discrepancies
pertaining to the PF.

9.1.1.2.1.10 Provide technical support to the GN&C Launch System
Evaluation Advisory Team (LSEAT), and serve as the GN&C representative
to the LSEAT. This position requires an understanding on the
Day-of-Launch-I-Load-Update system, and an understanding of the Space
Shuttle first stage trajectories and the ability to make a real-time
judgment of the adequacy of the GN&C system and the I-loads to support a
Space Shuttle launch.

9.1.1.2.1.11 Conduct engineering design activities, program design
reviews, and hardware/software system level design verification
activities, mission support, flight rule, Shuttle Operational Data Book
(SODB), launch commit criteria, testing, and maintenance requirements.

\*\*\*From Schedule A, FDSD, 4.1.1.1, Shuttle Unique:

**9.1.1.2.2 Data Systems Support** - This function provides the
management of the avionics system verification activity required for the
flight readiness assessment, monitors avionics system performance during
missions, and conducts special tests required in the laboratory or on
the flight vehicle. Avionics Systems is responsible for flight readiness
verification for each Shuttle mission in the following areas: Primary
Avionics System data processing hardware and software; instrumentation;
tape recorders; payload support computers; displays and controls (D&C)
hardware; Systems Management Software; backup flight system hardware and
software; hardware/software compatibility; and mated element data system
interfaces. The following are representative tasks the contractor shall
perform:

9.1.1.2.2.1 Provide engineering support to each area of the Avionics
Systems flight readiness verification responsibility including
analytical tools to evaluate proposed changes. Define the test
requirements for the SAIL to verify the capability of the integrated
systems to perform the planned missions. Assist the avionics management
working group in the planning and coordination of the verification
requirements, and participate in the test activity to evaluate results
and resolve discrepancies. Make recommendations concerning the flight
readiness, coordinate the sign-off of the flight readiness elements, and
maintain files for each mission.

9.1.1.2.2.2 Provide technical support for participation in various board
and panel meetings including the following: Orbiter Avionics Software
Control Board; Shuttle Data Control Board; Orbiter Software Test and
Operations (T&O) Board; Space Shuttle Checkout Panel; and Avionics
Integration Panel.

9.1.1.2.2.3 Audit the test planning and test results of the Orbiter
flight software verification activity to assure adequate verification of
the software changes incorporated in the flight software. Audit
systems-level verification test plans to evaluate the impact of software
and hardware/software interface changes on the data processing system
performance; emphasize verification of the interfaces between the data
processing system and payloads and experiments in the Orbiter.

9.1.1.2.2.4 Provide support to developers of flight techniques, mission
and procedures planners, flight and ground crew training personnel, and
flight crews.

9.1.1.2.2.5 Support the evaluation of emerging technology developments
relative to future subsystem upgrades.

\*\*\*From Schedule A, FDSD, 4.1.1.1.2 Cargo Integration:

**9.1.1.2.3 Cargo Integration** - This function provides the safety and
avionics system integration engineering activities to be performed
commensurate with responsibilities for assuring cargo integration and
Orbiter/payload compatibility. The following are representative tasks
the contractor shall perform:

9.1.1.2.3.1 Conduct reviews of Payload Integration Plans (PIPs) and
associated PIP annexes to evaluate compatibility with the National Space
Transportation System (NSTS) systems operation documentation, and
provide the results for use at the PIP and PIP annex reviews.

9.1.1.2.3.2 Perform evaluations of Shuttle/Payload avionics interface
design requirements, based on PIPs, for the generation of payload-unique
interface Control Documents (ICDs). Conduct technical analyses and
evaluations of Preliminary Interface Revision Notices (PIRNs) to the
payload-unique ICDs shall also be conducted. Coordinate results of these
evaluations and analyses with the appropriate Avionics Working Group
(AWG) chairperson in support of the integration process.

9.1.1.2.3.3 Perform evaluations of the cargo element/Shuttle avionics
interface designs and integration to assure compatibility and compliance
with program design and mission requirements and assist in the
preparation of the results for use in the Cargo Compatibility Review
(CCR), Cargo Integration Review Dry Runs (CIRDs), and Cargo Integration
Reviews (CIRs).

9.1.1.2.3.4 Develop and maintain an automated method to store and
retrieve the Orbiter/payload avionics interface requirements for each
cargo element. This automated system shall provide a data base to
streamline the cargo integration process, especially cargo remanifest
activities.

9.1.1.2.3.5 Evaluate programmatic avionics changes to ensure
compatibility with existing accommodations/requirements documents
including identification of issues and solution recommendations.

9.1.1.2.3.6 Evaluate verification procedures for Payload Interfaces such
as Technical Operating Procedures (TOPs) to ensure proper implementation
of design center requirements.

9.1.1.2.3.7 Evaluate payload safety packages for compliance with JSC
electrical safety guidelines. This includes assessments of avionics
interfaces, such as power and data, as well as any computers used by the
load to control or monitor safety critical functions.

\*\*\*From Schedule A, FDSD 4.1.1.1.3, Change Request Coordination:

**9.1.1.2.4 Change Request Coordination** - This function is responsible
for the technical coordination of the directorates review of Shuttle
related change requests. To fulfill this responsibility, develop and
operate a relational data base that tracks SSP change requests
evaluations. The following are representative tasks the contractor shall
perform:

9.1.1.2.4.1 Support the design, implementation and operation of the
Engineering Shuttle Configuration Management System which includes
computer hardware/software requirements, test/check-out procedures,
training and operations.

9.1.1.2.4.2 Support the primary Shuttle Level II meetings (Change Review
Group (CRG) and Pre-Program Requirements Change Board (PRCB) on a weekly
basis.

9.1.1.2.4.3 Support Avionics Systems in coordinating Level II change
requests with the proper engineering disciplines.

\*\*\*From Schedule A, NCAD, 3.1.1.2, Space Station Unique:

**9.1.1.3 Space Station-Unique** - This function provides the
engineering and analysis support for space station systems and
operations design evaluations. This effort includes activities such as:
analytical studies to assess alternate design options, provide technical
integration across space station systems and elements, assist in
developing technical direction to the prime space station work-package
contractor(s), perform independent analysis, and develop the experience
base to evolve from systems trades to operational trades to detail
flight techniques for space station operations. Assess performance of
manipulators to be used on the space station with regard to feasibility
and operational constraints. These studies, including performance scans
and trades, lead to the selection of optimum systems performance and
optimum operations performance profiles and trajectory parameters for
each specific event window. Study areas may include the functional of
proximity operations, attitude and pointing, consumable resource
rendezvous, payload handling, recontact analysis, space station Mobile
Remote Manipulator System (MRMS) analysis, berthing/docking analysis and
separation analysis. The following are representative tasks the
contractor shall perform:

**9.1.1.3.1 Rendezvous** - Evaluate the space station in terms of
logistics, performance and tracking requirements.

**9.1.1.3.2 Mission Requirements Synthesis and Analysis** - Support
definition, design, and development of space station Mission Integration
Plan (MIP) development, integrated mission scenarios, flight phase
analysis and systems requirements development, assembly sequence
definition, logistics and traffic management, orbit selection trade
studies, configuration definition analyses, and mission operations and
systems requirements assessments.

**9.1.1.3.3 Systems Requirements Synthesis and Analysis** - Support
space station systems design and sizing requirements in the following
areas: electrical power system, thermal control systems, propulsion
systems, and fluids management systems.

**9.1.1.3.4 GN&C** - Provide support in the following areas:

9.1.1.3.4.1 Space station attitude and pointing guidelines to support
space station user requirements.

9.1.1.3.4.2 Space station onboard techniques for maintaining velocity,
position, and attitude knowledge and related interfaces with ground, and
global positioning satellite (GPS).

9.1.1.3.4.3 Sensors and hardware evaluation, mean time between failure
(MTBF) analysis, redundancy requirements, and management.

9.1.1.3.4.4 Space station onboard software requirements and design
integration across systems and elements.

**9.1.1.3.5 GN&C Verification** - Provide support to the integrated
software and avionics verification in the following areas:

9.1.1.3.5.1 Develop verification requirements.

9.1.1.3.5.2 Review Level II and Work Package 2 proposed test plan.

9.1.1.3.5.3 Analysis verification testing results.

\*\*\*From Schedule A, FDSD 4.1.1.2, Space Station Unique

**9.1.1.3.6 Subsystem Management** - This function provides Avionics
Systems with the capability for managing development of the space
station Data Management System (DMS) hardware and software, development
of avionics integration and verification tools, and the Work Package 2
flight software build process. Responsibilities include managing the
definition, design, development, integration, test, and evaluation of
DMS components, DMS system integration, and DMS system certification for
flight. The DMS provides the standard hardware resources and software
services that support the data processing and communications needs of
systems, elements, and payloads on board the space station. Other
responsibilities include managing definition, design, development,
integration, test, and evaluation of data management system software and
networks. The DMS system software provides the common operating
environment and human-machine interface for operation and control of the
various distributed systems and payloads. Avionics Systems is also
responsible for integrating data management system software with
application programs and for performing research and development in
support of data management system development. Avionics Systems has
responsibility for managing development and operation of the Avionics
Development Facility (ADF); development of the Integrated Test and
Verification Environment (ITVE); and the Work Package 2 flight software
build process. The ADF is the facility designated for integration,
verification, and certification of Work Package 2 flight software. The
ITVE is the integrated set of tools and procedures required to support
integration, verification, and validation for flight hardware and
software. Responsibilities include software configuration planning, test
planning, and performance of JSC flight software integration, build,
verification, and certification. Avionics Systems also conducts research
and development into software and hardware integration, testing
techniques, and technology appraisal. The following are representative
tasks the contractor shall perform:

9.1.1.3.6.1 Provide support to Avionics Systems for DMS hardware and
software subsystem management. DMS subsystems include the flight
hardware configuration Items, flight computer software configuration
items, and the DMS Kits used for simulation and testing. Flight hardware
and software items are identified in the Major Component Characteristic
section of the DMS Contract End Item (CEI) Specification, SP-M-001. The
DMS kits are described in the CEI specification for DMS kits, SP-M-015.
Subsystem management support includes participation in requirements,
design, documentation, and cost reviews; development, integration, and
documentation of functional, performance, and interface requirements;
analysis of DMS hardware and software to insure that end item
deliverables meet requirements; and technical monitoring of subsystem
integration and verification activities.

9.1.1.3.6.2 Provide support to Avionics Systems for DMS system
integration. This task supports the DMS system integration manager who
is responsible for architecture definition and system interfaces. Duties
include development of the DMS Architecture Control Document (ACD),
assuring end-to-end system functionality as defined in the ACD,
integration of DMS with other systems, and assuring that the DMS
complies with SSP 30000 requirements.

9.1.1.3.6.3 Provide support to Avionics Systems for DMS system
development. This task supports the DMS system development manager who
is responsible for overall technical management of DMS development.
Duties include supporting management of system development, analysis of
system functional and performance requirements as specified in Type I
documents, and providing integration support to other systems using DMS.

9.1.1.3.6.4 Provide support to Avionics Systems for DMS system level
verification. This task supports the DMS system verification manager who
is responsible for implementation and technical management of system
integration and verification. Duties include definition of testing
requirements, system analysis, system testing, and resource allocation.

9.1.1.3.6.5 Provide support to Avionics Systems for application of the
Ada computer programming language. This task supports the functional
area manager for the Ada programming language. Duties include
consultation in the use of Ada for the space station and technical
management of the acquisition and maintenance of the flight software
compiler and support tools.

9.1.1.3.6.6 Provide support to Avionics Systems in performing the Work
Package 2 flight software builds and post build testing. Duties include
producing build schedules, analyzing and tracking dependencies, and
analyzing test requirements and results.

9.1.1.3.6.7 Provide support to Avionics Systems for technical management
of ITVE development. This system is defined in the ITVE CEI
Specification, SP-M-144B. Duties include design analysis, performance
measurement and consultation with system users.

\*\*\*From Schedule A, FDSD 4.1.1.2.2 Software Support Environment:

**9.1.1.3.7 Software Support Environment** - This function provides
Avionics Systems with the capability for management of the
implementation of the space station Software Support Environment (SSE)
and the on-board Software Build system plus facility support to the
development and operation of the Master Object Data Base (MODB). The SSE
consists of the software tools and standards that are being used to
develop and maintain operational software for the Space Station Program.
The Build System is the set of software tools used to produce the
software builds for on-board space station software. These tools have
been built in part by the SSE Project and in part by Work Package 2. The
Space Station Project includes the operation and maintenance of the SSE
Development Facility (SSEDF). The SSEDF is used to build the SSE, to
evaluate commercial products for possible use as SSE tools, and also to
provide computational support to the MODB development effort by Work
Package 2. The overall SSE effort has three lines of emphasis:
operations and maintenance, system engineering, and software
development. This includes SSE requirements identification, design,
development, networking, integration, testing, verification, validation,
support, and long-term sustaining engineering. Because of the long
duration of the Space Station Program, the SSE is evolving in
incremental stages called Operational Increments (OIs). The Build System
is being developed in parallel and delivered with the appropriate SSE
OIs. The following are representative tasks the contractor shall
perform:

9.1.1.3.7.1 Develop and maintain Federal Information Processing
Resources (FIPR) plans in support of SSE Project procurements.

9.1.1.3.7.2 Provide detailed analyses, including cost/risk analyses on
the facilities and support software required to develop, verify, and
maintain Space Station Program operational software. Examples of areas
to be covered are: facility, system, and application security, software
requirements, network and communication issues, documentation quality,
software engineering adequacy, and software application design.

9.1.1.3.7.3 Provide analysis and detailed reports on delivered software,
documentation, and test results to assess product quality.

\*\*\*From Schedule A, TCD, 2.1.2, R&D Support:

9.1.2 Research and Development Support

The following are representative tasks the contractor shall perform:

**9.1.2.1 Advanced Development** - Perform research and development
associated with the design, implementation, and testing of advanced
space communications and tracking subsystems for the functional areas
described in Section 9.1.1.

**9.1.2.2 Advanced Program Definition** - Perform conceptual design
studies and engineering assessments, as defined in Section 9.1.4, in
support of advanced program activities such as Space Exploration
Initiative and Personnel Launch System.

\*\*\*From Schedule A, NCAD, 3.1.2, R&D Support:

**9.1.2.3 Avionics Systems Engineering and Integration** - This function
provides for the design, test and/or analysis of avionics system
requirements to define the optimum systems configuration to meet program
requirements and provide an acceptable balance between development risk
and application of new technology; and defines avionics system/subsystem
integration requirements and assesses their implementation impact on
system-level hardware/software design requirements, development risk and
growth potential. The following are representative tasks the contractor
shall perform:

9.1.2.3.1 Perform studies and analyses to define the requirements for
implementation of new avionics systems concepts and evaluate the impact
on hardware and software systems design and development risk.

\*\*\*NOTE: Schedule A, NCAD 3.1.2.1.2 went to NEW SOW Part I, Section
4.

\*\*\*From Schedule A, NCAD, 3.1.2.1.3, edited to include only inertial
and optical subsystem/components:

9.1.2.3.2 Provide the engineering design, development, implementation,
and evaluation of candidate Inertial and Optical subsystem/components;
and define the data interface requirements and engineering assessment
criteria for integrating these subsystems with other avionics
subsystems.

9.1.3 Engineering, Scientific, and Analytical Tools

\*\*\*From Schedule A, TCD, 2.1.3.1:

**9.1.3.1 Computer Program Development and Maintenance Support -** This
function includes the responsibility for the development and operation
of C&T simulation tools for use in performing C&T support services.
These tools shall allow the simulation and analysis of end-to-end C&T
links, including the effects of coding, modulation, antennas, signal
processing, multiplexing, spread spectrum, encryption, and the impacts
of multipath, interference, and nonlinearities. The following are
representative tasks the contractor shall perform:

9.1.3.1.1 Develop math models compatible with the simulation system
operating elements; develop software to integrate and upgrade the
simulation capability; and perform time domain and frequency domain
analyses, including Monte-Carlo simulations, and spectrum analyses.

9.1.3.1.2 Develop and maintain C&T RF coverage computer programs
(reference 9.1.1.1.2.1.1).

9.1.3.1.3 Develop and maintain math models for use in the calculation of
spacecraft C&T link circuit margins; develop and maintain computer tools
and data bases to aid in calculating and documenting the circuit margins
(reference 9.1.1.1.2.2).

\*\*\*From Schedule A, NCAD, 3.1.3.3, Other Tools:

**9.1.3.2 Other Tools** - The following are representative tasks the
contractor shall perform:

9.1.3.2.1 Support development and operation of software programs for the
layout and preparation of schematics, printed circuit and wire-wrap
boards, and photoplotting.

9.1.3.2.2 Provide programming support for the following software
programs: DAP, ADAP, GEMAS, Modified Maximum Likelihood Estimator
(MMLE), Parameter Estimator (PEst), GRAM, OADB, and POST.

\*\*\*From Schedule A, FDSD, 4.1.2 Engineering, Scientific, and
Analytical Tools:

9.1.3.3 Flight Data Systems Engineering, Scientific and Analytical
Tools - The following are representative tasks the contractor shall
perform:

9.1.3.3.1 Provide the engineering and technical support for the
evaluation of advanced flight data systems concepts including command
and control techniques. Activities include providing an environment for
proof of concept definition, preliminary designs, and design validation.
Provide the engineering and technical, support necessary to maintain
these laboratories. Be cognizant of the open system interconnect
processing techniques, computing systems, and data
distribution/operations functions requiring a wide range of integrated
services. This support shall encompass a spectrum of activity from
state-of-the-art systems concept development for both ground-based and
flight systems to laboratory operations.

9.1.3.3.2 Provide an automated capability to perform design, drafting,
engineering, simulation, analysis, scheduling, and graphics related to
avionics systems design and analysis activities for current and future
NASA human space programs. Provide support for the development and
operation of software programs for the layout and preparation of
schematics, printed circuit and wire-wrap boards, and photoplotting.

\*\*\*From Schedule A, 13.1.1

**9.1.3.4 Office Automation Applications** - Provide applications
development support for Engineering Directorate applications. The
support includes the definition of requirements, design, implementation,
testing and training for, and maintenance of the application. The
existing applications which require support are as follows: (1)
Equipment Lifecycle System and (2) Electronic LDR System.

The development and maintenance of the applications require the support
of the appropriate tools for representing the systems from a
directorate/enterprise point of view. The above applications require a
data base administration function for the Oracle DBMS on a VAX system.

\*\*\*From Schedule A, TCD, 2.1.4 Studies & Assessments

9.1.4 Studies and Assessments

**9.1.4.1 C&T Conceptual Design Analysis** - This function includes the
responsibility for the development of conceptual designs for spacecraft
C&T links. The following are representative tasks the contractor shall
perform:

9.1.4.1.1 Perform Phase A/B design/definition studies, assess systems
design requirements, and evaluate/maintain cognizance of current and
advanced C&T design techniques and equipment

**9.1.4.2 C&T Special Studies** - This function includes the
responsibility for performing special studies for specific C&T system
concerns/problems. Any or all of the preceding support services could be
required to achieve the desired output. The following are representative
tasks the contractor shall perform:

9.1.4.2.1 Provide C&T interface analysis; provide tradeoff analyses for
use in subsystem design selections (e.g., antenna type), operational
selectivity (non-standard mode selections); provide parametric
sensitivity analyses; and perform analysis in support of C&T performance
anomalies.

\*\*\*From Schedule A, FDSD, 4.1.3 Studies & Assessments:

**9.1.4.3 Flight Data Systems Design/Analysis** - The following are
representative tasks the contractor shall perform:

9.1.4.3.1 Provide design, test, and/or analysis of flight data systems
in support of Phases A and B of new programs and develop laboratory
based flight data system concepts and prototypes as precursor technology
development for future programs.

9.1.4.3.2 Perform systems engineering analysis and trades to develop
generic flight data system architectures. This activity includes
requirements analysis, conceptual design, standardization of interfaces,
and prototype development of flight data systems in a laboratory
environment for a variety of future, and as yet unspecified vehicles.

9.1.4.3.3 Perform specific vehicle systems designs and trades based on
general requirements for new vehicles ranging from small
non-human-tended scout vehicles to large human-tended complex
transportation vehicles. These activities shall support NASA Phase A and
B design activities for these vehicles.

9.1.4.3.4 Support NASA in its representation to various standards making
bodies that are directly related to NASA's roles and missions. Some of
the bodies would be the Ada Board, Institute of Electrical and
Electronics Engineers (IEEE) PI 003, American institute of Aeronautical
Engineers (AIAA), and Society of Automotive Engineers (SAE).

\*\*\*From Schedule A, TCD, 2.2:

9.2 LABORATORY/FACILITY SUPPORT SERVICES

9.2.1 General Support Services

**9.2.1.1 Communications -** Each of the laboratories is equipped with
modern test and analysis equipment necessary to design, assemble, and
evaluate communications components from initial conceptual designs to
prototype flight hardware. This function supports the development work
to be carried out in the facilities which includes all the components
and subsystems required to implement a space flight communications
system. The following are representative tasks the contractor shall
perform:

9.2.1.1.1 Maintain and operate the laboratories and facilities for
conceptual design, development, fabrication, testing, and evaluation of
various types of C&T equipment and software used for human space flight.

9.2.1.1.2 Provide troubleshooting and performance analysis of
flight-type equipment/hardware to identify potential problem areas and
methods of resolving them.

9.2.1.1.3 Support design, development, and fabrication/test of alternate
and new hardware to improve existing system performance or meet new
requirements.

9.2.1.1.4 Develop test plans, procedures, and associated schedules for
required tasks.

9.2.1.1.5 Fabricate and assemble test setups configured to operate as
spacecraft system consoles.

\*\*\*From Schedule A, NCAD 3.2.1, General Support Services:

**9.2.1.2 Avionics** - This function provides the design, development,
test, and evaluation for avionics systems and related computing systems,
data distribution, subsystem interface processing, data operations
functions for integrated avionics systems services cover a spectrum from
state-of-the-art concept development, for both ground-based and flight
systems, to laboratory operations. Open system interconnect processing
techniques, computing systems, and data distribution/operations
functions require a wide range of integrated services. This support
shall encompass a spectrum of activity from state-of-the-art subsystem
concept development for both ground-base and flight systems to
laboratory operations. The following are representative tasks the
contractor shall perform:

9.2.1.2.1 Provide test setups, develop test procedures, conduct Test
Readiness Reviews, perform test operations, provide data reduction,
evaluate test data, operate and maintain laboratory simulators, support
test bed activities, and issue test and evaluation reports for avionics
systems and components.

9.2.1.2.2 Perform the research, documentation review, design
definitions, engineering tradeoff studies, system optimizations
definitions, and other analyses in support of avionics systems
integration, development, and performing evaluation activities.

9.2.1.2.3 Perform design, fabrication, test, and analysis. This includes
the procurement, operation, and maintenance of data systems, display and
controls, and guidance, navigation, and control system hardware,
engineering breadboards and test beds, and test facilities to support
advanced space vehicle sensor and effector development, and the
definition, design, fabrication, development, and integration
requirements for optical and inertial GN&C components, math models, and
emulators.

9.2.1.2.4 Provide the day-to-day maintenance and operations support
required for advanced avionics systems data networks and "automation"
related data networks for which Avionics Systems is responsible.

9.2.1.2.5 Support the installation and checkout of additional
hardware/software and/or upgrades to present lab facilities; development
and maintenance of computer software for cathode ray tube (CRT) display;
video and film recording of dynamics graphics data; and documentation of
all appropriate lab hardware and software.

\*\*\*From Schedule A, FDSD, 4.2.1 Laboratory/Facility General Support
Services:

**9.2.1.3 Flight Data Systems -** Provide design, development, test, and
evaluation support for flight data systems and related computing
systems, data distribution, subsystem interface processing, data
operations functions for integrated flight data systems services that
include state-of-the-art concept development, for both ground-based and
flight systems, to laboratory operations.

9.2.1.3.1 Provide support relative to open system interconnect
processing techniques, computing systems, and data
distribution/operations functions. This support shall encompass a
spectrum of activity from state-of-the-art subsystem concept ranging
from development for both ground-base and flight systems to routine
laboratory operations.

9.2.1.3.2 Provide the required test setups, develop test procedures,
conduct Test Readiness Reviews, perform test operations, provide data
reduction, evaluate test data, operate and maintain laboratory
simulators, support test bed activities, and issue test and evaluation
reports for flight data systems and components.

9.2.1.3.3 Perform research, documentation review, design definitions,
engineering trade-off studies, system optimizations definitions, and
other analyses in support of flight data systems integration,
development, and evaluation activities.

9.2.1.3.4 Perform design, fabrication, test, and analysis. This includes
the procurement, operation, and maintenance of data systems, display and
controls, system hardware, engineering breadboards and test beds, and
test facilities to support advanced space data system development, and
the definition, design, fabrication, development, and integration
requirements for flight data systems components, math models, and
emulators.

9.2.1.3.5 Provide the day-to-day maintenance and operations support
required for advanced flight data systems data networks and operational
"automation" related data networks for which Avionics Systems is
responsible.

\*\*\*From Schedule A, TCD, 2.2.2 FIPR:

9.2.2 Federal Information Processing Resources (FIPR) Support

This function includes the FIPR support for Avionics Systems. The
avionics systems is served by an automation system based on DEC VAX
computers linked to directorate and site-wide computer networks. The
computers of Avionics Systems are used by both NASA and support
contractor personnel for scientific and engineering applications, for
real-time test control and laboratory automation (where practical), for
computer aided design, for operations and management, and for other
tasks necessary to support Avionics Systems' efforts. The following are
representative tasks the contractor shall perform:

9.2.2.1 Operate the computer systems and ensure the availability of a
computing capability.

9.2.2.2 Install system software, upgrade in accordance with the
manufacturers specifications and modify it as required to support tasks
and functions.

9.2.2.3 Coordinate maintenance of the computing systems and peripherals,
schedule and monitor preventive maintenance, make minor repairs and
coordinate major repairs provided by outside NASA JSC service contracts,
prepare exhibit lists for the maintenance contracts, and maintain a data
base containing an inventory of the computer equipment and software.

9.2.2.4 Ensure the continued operation of the ETHERNET local area
network and of the interfaces with the directorate and site networks and
expand and modify use as required for the interchange of engineering and
management data.

9.2.2.5 Operate the Computer-Aided Design (CAD) system and develop and
support engineering and automation applications on them.

9.2.2.6 Help design and develop programs to automate and improve
operations and management information systems, and provide user
assistance during checkout and implementation.

9.2.2.7 Design, develop, and implement special purpose electronic
equipment and software for unique interfaces and applications, such as
the real-time interfaces with computer-controlled communications
equipment, plotters, and CAD systems.

9.2.2.8 Develop application programs for real-time test control and
laboratory automation for current and advanced communications and
tracking systems testing, and for test bed development and for control
and monitoring functions.

9.2.2.9 Support the applications of computing systems by providing
configuration planning, capability reporting, schedule development, user
help, training, procurement, network design, documentation, data base
formation, laboratory modifications, and computer language capabilities.

\*\*\*From Schedule A, NCAD, 3.2.2, FIPR:

9.2.2.10 Provide general computer systems support in the areas of
software development and maintenance of existing and planned engineering
software and hardware systems. Support activities such as applications
and operating systems software development, vendor software installation
and operational support, consultation, user training, and the
maintenance and operational support of the Avionics Systems' data bases
and analysis software systems.

9.2.2.11 Support the migrating of engineering software from one Avionics
Systems computer to another and for the maintenance of existing software
systems on any of the Avionics Systems' computers. Provide training and
consultation to users of the Avionics Systems' computers, operating
systems, or any purchased or developed software. Gain information for
installation and maintenance of purchased systems and for the training
of Avionics Systems' users. Design and develop software and data flow
interfaces between existing and planned Avionics Systems' systems.

9.2.2.12 Provide system analyst support for day-to-day operating system
problems, system tuning, system operational upkeep and system hardware
upgrade consultation. This also includes installation and maintenance of
operating systems.

9.2.2.13 Provide support in the assessment of existing, enhanced and new
commercially available computer programs which may enhance the design
and analysis capabilities of the Avionics Systems. The assessment may
include trade-off studies of potential improvements in capabilities,
compatibility with existing programs, data bases, and procurement
recommendations.

9.2.2.14 Provide support to the Avionics Systems' Functional Area
Coordinator (FAC) in the coordination of requirements and funding for
material purchases and the preparation of the associated paperwork,
review of service requests (SR) for completeness, proper signatures,
timely assessment of the SR status in the process flow, pickup/delivery
of software and documentation to users, maintenance of a data base of
Avionics Systems' equipment and associated software.

9.2.2.15 Provide support to the Avionics Systems' Information Resource
Management (IRM) Coordinator through supporting IRM Coordinators
Meetings, scheduling personnel for training classes, providing support
in preparation of paperwork involving purchase requests and supply
requisitions and tracking their status, and other IRM assignments.

9.2.2.16 Provide support to the Avionics Systems' Computer Security
Officer in the preparation of computer system risk analyses, sensitive
application surveys/requirements, installation and maintenance of
security related software, and other security related assignments.

\*\*\*From Schedule A, FDSD, 4.2.2 Federal information Processing
Resources (FIPR) Related Activities:

**9.2.2.17 Computing/Networking Support** - The following are
representative tasks the contractor shall perform:

9.2.2.17.1 Support the design, development, and maintenance of a
multiple central processor unit networked computer facility that
produces the engineering and professional environment for space vehicle
avionics systems development. The facility shall also support data
retrieval efforts associated with archival or relational data base
storage systems.

**9.2.2.17.2 Network Engineering** - This function provides the systems
engineering design and evaluation methodology for computer
communications networking systems; provides the design effort that joins
together of the computational systems of a large group with widely
distributed equipment so that a common data base can be shared; defines
the current and future needs of the user community; and develops a
workstation network that is compatible with the needs of a diverse
installed user base. The following are representative tasks the
contractor shall perform:

9.2.2.17.2.1 Support the definition of a hardware and software
configuration which will provide an efficient and flexible engineering
computer communication network. Practical, affordable approaches, trade
studies, etc. are considered part of this activity.

9.2.2.17.2.2 Design, install, test, operate, and maintain a local and
remote area network which is based on the existing distribution of
automatic data processing equipment and data bus systems.

9.2.2.17.2.3 Assist with the development of advanced concepts which
permit the integration of computer communication systems with major
Program Office data bases at JSC and remote locations.

9.2.2.17.2.4 Support the development of innovative and cost effective
approaches to data base design and testing of distributed data base
information management.

**9.2.2.17.3 Systems Software Support** - This function provides
computer systems analysis using computer vendor software, such as
operating systems, enhancement packages, utilities and other user
support software. The following are representative tasks the contractor
shall perform:

9.2.2.17.3.1 Provide support for resolving system problems, evaluating
new software, testing performance and integrating system functions with
the developers and users of application software.

\*\*\*From Schedule A, TCD 2.2.3:

9.2.3 Communications Processing Laboratories

This function supports the Avionics Systems' Communications Processing
Laboratories including the Voice Processing Development Laboratory,
Audio Development Laboratory, Signal Processing Laboratory,
Electro-Acoustical Laboratory, Television (TV) Systems Laboratory, Text
and Graphic Systems Laboratory, Video Tape Recorder Laboratory, and
flight equipment assembly area. These laboratories support the
conceptual design, development, fabrication, testing, and evaluation of
various types of electronic telecommunications equipment used for human
space flight. The following are representative tasks the contractor
shall perform:

9.2.3.1 Perform tasks involving the design, fabrication, and evaluation
of digital uplink (combined audio-data-command signal)
modulation/demodulation equipment, and the interfaces of this equipment
with vehicle communication components.

9.2.3.2 Support design efforts which include the application and
evaluation of fail-safe, redundancy and self-checking techniques.
Specific efforts involve application of state-of-the-art circuit
technology and components to the design of communications components and
subsystems for space flight use. Throughout the development of such
hardware, computer aid design, simulation, and evaluation techniques
shall be employed requiring the contractor engineering personnel to be
cognizant of the mathematical basis for the subject tasks.

9.2.3.3 Support tasks which require measurement and evaluation and
determination of: (a) demodulator/synchronizer acquisition time for
signal lock, (b) performance relative to bit transition density,
signal/noise ratio, bit jitter, loop bandwidth, (c) error control
performance relative to erasure threshold error rates, message
acceptance and rejection rates, and (d) subjective quality evaluation of
digital television bandwidth compression algorithms.

9.2.3.4 Support activities which involve evaluation, measurement, and
determination of typical parameters such as resolution, lag, geometric
distortion, grey shades, motion rendition, spectral response, tilt,
aperture response, automatic light level and gain control response
characteristics, lights level sensitivity, and modulation transfer
function for systems and components.

9.2.3.5 Support design, development, fabrication and test of video
processors employing nonstandard formats for spacecraft television
systems. These processors include scan converters and color converters
utilizing disk recorders and other storage devices. Application of
state-of-the-art computer control, bandwidth compression, color
generation, and miniaturization techniques are required. Design tasks
shall accommodate requirements for high resolution color TV over narrow
communications bandwidths in support of remote control and inspection
applications involving the man-machine interface.

9.2.3.6 Perform sign tasks which involve the evaluation and definition
of television system to be used in advanced applications. This activity
includes multiple TV cameras/monitors, nonstandard color TV formats,
computer-controlled television control and distribution systems, and the
video proximity operations devices to implement functions such as
tracking end focusing/auto zoom. Prototype hardware for these systems
shall be designed, fabricated and assembled for testing in dedicated
subsystem test beds. Selected test beds for each system shall be
integrated into, and evaluated, in a system-level communications and
tracking test bed. The performance of this hardware shall be the basis
for hardware/engineering specifications to be provided for the build up
of advanced systems.

9.2.3.7 Support text and graphic system performance evaluation tasks
which include measurement of the modulation transfer function and
resolution of the system. Typical tasks specific to the scanner include
the optical and electrical alignment and functional testing. Tasks
associated with the copier are the development of the optimum video
alignment and developer heater temperature, evaluation of the paper
transport subsystem, and bench checkout of the equipment.

9.2.3.8 Support efforts to improve and modify the existing equipment by
performance deficiencies and requirement changes and in the engineering
work associated with the specification, design, development,
fabrication, and application of advanced scanning and hard copying
equipment.

9.2.3.9 Perform design tasks involving video tape recorders (VTRs), the
ground test equipment, and the spacecraft crew processing and recording
circuits, breadboard evaluation of candidate designs, and incorporation
of new or modified circuits or subassemblies in the VTRs or support
equipment.

9.2.3.10 Perform, analyze, and report on comprehensive measurements and
evaluation tests of recording devices to confirm parameters such as
bandwidth, luminance non-linearity, line time distortion, differential
gain and phase, chrominance to luminance gain and delay distortion, time
base stability, and various signal-to-noise ratios.

9.2.3.11 Support investigation and resolution of problems which occur
during missions and which involve improvements and modifications to the
existing equipment due to performance deficiencies and requirement
changes for the Shuttle and advanced systems applications.

9.2.3.12 Perform tasks supporting design, development, fabrication,
testing and evaluation of audio communication systems which include
headsets, microphones, earphones, speakers, recorders, analog and
digital processors, distribution/signaling system (LANs and PBXs), voice
command/synthesis processors, integrated services (voice/data), digital
networks, and associated data evaluation from test beds, flight
experiments, and actual flight systems.

9.2.3.13 Performs tasks supporting design, development, fabrication,
testing, and evaluation of communications data processors, frequency
division and time division multiplexers, packet data formatters, and
associated data evaluation from test beds, flight experiments, and
actual flight data systems.

9.2.4 Tracking Techniques Laboratories

This function supports Avionics Systems' Tracking Techniques
Laboratories including the Optical Tracking and Communications
Laboratory, Six-Degree-of-Freedom Positioner Test Facility, Image-Based
Tracking Laboratory, Radar Laboratory, Radar Boresight Facility, Global
Positioning System (GPS) Laboratory, and Hybrid Vision Laboratory. These
laboratories support the design, development, fabrication, test, and
evaluation of components and systems for optical communications and
tracking. The following are representative tasks the contractor shall
perform:

9.2.4.1 Support the design, development, fabrication, test, and
evaluation of laser and image-based tracking systems and optical
communications systems. Operate, maintain, and upgrade the Precision
Six-Degree-of-Freedom Positioning System.

9.2.4.2 Perform tests on tracking systems in the Radar Boresight
Facility. Support requirements for this facility entail determining and
measuring the effects of tilt errors, polarization errors, multipath, a
near-field effects tracking systems.

9.2.4.3 Support the design, development, fabrication, simulation, test,
and evaluation of microwave tracking systems including radars,
transponders, RF navigation aids, and GPS receivers/processors for
spacecraft orbital and landing operations. Operate and maintain the GPS
simulation and test facility.

9.2.5 Electronic Systems Test Laboratory (ESTL)

The functions of the ESTL are to conduct detailed
spacecraft-to-spacecraft, ground-to-spacecraft, and space craft to
ground RF communication system tests on an end-to-end system basis to
evaluate early system designs, to support communications system
development, and to verify that system performance is commensurate with
mission requirements prior to actual flights. Spacecraft communications
equipment including tandem link configurations, are interfaced through a
space simulation network to ground station equipment and integrated into
an overall test bed to accomplish test and evaluation objectives.
Testing consists of integrated and special system tests (including space
network operations integration testing) to assure that performance of
actual spacecraft and ground radio frequency systems meet program
requirements when subjected to electrical conditions similar to those
expected during operational missions. The following are representative
tasks the contractor shall perform:

9.2.5.1 Develop plans and schedule test programs, perform tests, and
analyze data. Prepare documentation to include data manuals, procedures,
reports, and graphic presentations.

9.2.5.2 Support the development of advanced communications system and/or
techniques including conceptual designs, and recommend test bed
evaluations of complex, unproved configurations and concepts, including
trade-offs between alternate or competing designs.

9.2.5.3 Provide engineering support for development of laboratory
configurations to test and evaluate space/ground systems. This effort
shall include the engineering design, build up, and integration of
special test systems (such as radio frequency space loss simulators
incorporating doppler, signal delay propagation effects, multipath, and
interference injection capabilities), consoles, devices, and fixtures
for control, operation, test of space/ground and space/space
communications systems, and the preparation of maintenance and operation
manuals for each test buildup.

9.2.5.4 Conduct test programs for evaluating the compatibility and
overall performance of spacecraft telecommunications electronic systems
and ground systems on an integrated basis.

9.2.5.5 Develop procedures and conduct tests and evaluations leading to
the resolution of special, identified communications system problems
and/or anomalies including pre-mission, real-time, and post-mission
periods of activity.

9.2.5.6 Develop diagnostic test concepts which will not only indicate
spacecraft-ground and spacecraft-spacecraft system incompatibilities,
but which will aid in recognizing the source of incompatibility.

9.2.5.7 Provide computer systems support (system analysts, programmers,
operators) for the development, maintenance, and operations of
computers, tools, data bases, as an aid in test operations, test
conducting, documenting, and test assessment as related to engineering
testing and evaluation of space/ground and space-space communications
systems. This effort shall include the development of test system
hardware/software capabilities to integrate, test, and evaluate on a
closed-loop basis. This activity also includes automation (where
practical) of overall laboratory test activities, CAD/CAE, and
automation functions.

9.2.5.8 Provide technical documentation consisting of test requirements,
test project plans, procedures, data packages, system performance
assessment reports, and summaries, including computer related and
general laboratory descriptive information.

9.2.5.9 Support the design, developments fabrication, test, and
evaluation of C&T control and status monitoring subsystem for the ESTL
and candidate/proposed subsystem for spaceflight applications.

9.2.5.10 Provide training in the form of operational instructions on
equipment procured, fabricated, or assembled by the contractor.

9.2.5.11 Review mission objectives and prepare communication systems
test plans; participate in preflight and flight communication tests and
evaluate the test results; determine and resolve communication system
problems; prepare flight and flight communications test reports; prepare
test requirements; maintain a file of communications system
engineering/flight verification support documents; and perform
engineering studies to establish advanced techniques.

9.2.6 Antenna Range and Anechoic Chamber

The functions of the Antenna Range and Anechoic Chamber are measurement
of antenna radiation patterns, antenna impedance measurement, and
electromagnetic interference testing. These facilities assist in the
design, development, fabrication, and test of antennas for Space
Shuttle, space station, space platforms, satellites, and other programs.
Functional activities encompass both the analytical and measurement
aspects of antenna design, development, fabrication, and testing. The
measurement techniques are required to validate the theoretical and
specified performance of antennas. Measured parameters typically include
radiation pattern (amplitude and phase), gain, directivity, efficiency,
impedance, current distribution, and polarization. The following are
representative tasks the contractor shall perform:

9.2.6.1 Support the test and evaluation of space-based antennas
including sophisticated antennas such as multibeam distributed array
antennas on doubly curved surfaces.

9.2.6.2 Perform design and fabrication of vehicle mockups and test
antennas (both full scale and scale models) along with providing any
required special test fixtures and antenna test apparatus.

9.2.6.3 Perform test and performance verification of candidate space
antennas.

9.2.6.4 Provide formulation of test plans and schedules and the
preparation of test procedures and test reports for antenna test
programs.

9.2.6.5 Provide computer graphics and simulation of antennas and antenna
systems and provide measured test data in reduced graphical forms.

9.2.6.6 Use the Geometrical Theory of Diffraction (GTD) mathematical
models to analyze the scattering, diffraction, and multipath
environments in proximity to space vehicles.

9.2.6.7 Provide maintenance, operation, calibration of the laboratory,
and minor repair of various test instrumentation.

9.2.6.8 Perform EMC evaluation and certification testing of flight
hardware and GSE. Support testing of other JSC laboratory shielding
effectiveness, formulate the test procedures, deliver a test report, and
provide an analysis of results.

9.2.7 Microwave Design and Integrated Circuit Laboratories

The function of these laboratories is to design, fabricate, and test
microwave components and systems for use in space based communication
and radar equipment. The laboratories are used to design, fabricate, and
test components such as circulators, RF limiters, filters, high power
amplifiers, low noise amplifiers, mixers, phase shifters, switching
networks, power dividers, and many other components. The following are
representative tasks the contractor shall perform:

9.2.7.1 Support the design, development, fabrication, and test of hybrid
microwave components for space communications and radar systems.

9.2.7.2 Support development of system designs and generation of
specifications for components for microwave systems and use the C system
to design various microwave components.

9.2.7.3 Generate layouts of microwave circuits, photoreduction to obtain
masks, exposure of masks on dielectric substrate boards, etching, and
assembly of discrete and patch components to the boards.

9.2.7.4 Perform testing of microwave circuits with specialized network
analyzers, noise figure meters, and other specialized laboratory
equipment.

9.2.7.5 Provide integration of various circuit components into working
microwave systems.

9.2.8 High Temperature Superconductivity (HTSC) Laboratory

The function of this laboratory is to test HTSC microwave components,
antennas, and RF systems for spaceborne systems applications. The
following are representative tasks the contractor shall perform:
Evaluate state-of-the-art HTSC communications and tracking devices for
application to advanced programs and support the design, development,
and testing of a HTSC flight experiment from the Orbiter payload bay
through the Advanced Communications Technology Satellite to a ground
terminal.

9.2.9 Electromagnetic Compatibility (EMC) and Electromagnetic
Interference (EMI) Test Laboratory

The function of this laboratory is to provide the equipment for
generating the electromagnetic environments necessary for EMC and EM
testing of a variety of flight and ground support hardware. The
following are representative tasks the contractor shall perform: Perform
EMI/EMC evaluation and certification testing of GFE to ensure compliance
with the Orbiter crew cabin, middeck, payload bay, and spacelab
specifications for EMI; provide engineering support to conduct EMI/EMC
testing; perform test data reduction and display; prepare reports
presenting the data from EM tests results; and evaluate prototype
hardware to assist in practical early solutions of EM problems prior to
delivery of flight hardware.

9.2.10 Communications System Development Laboratory

The function of this laboratory is the design, development, fabrication,
test, and evaluation of component and systems for RF communications. The
following are representative tasks the contractor shall perform:

9.2.10.1 Support the design, development, fabrication, test, and
evaluation of RF voice/data transceiver systems. This effort shall
include systems which bridge low VHF to high UHF frequencies
inclusively, and incorporate AM, FM, FSK, and PSK modulation techniques
and variations thereof for the transmission of voice, video, and data
signals.

9.2.10.2 Support the development of GFE which includes design,
breadboarding, preliminary and critical design reviews (PDRs and CDRs),
certification and acceptance testing of training and flight units.

9.2.10.3 Design and fabricate GSE for in-house built equipment.

9.2.11 Communications Software Development Laboratory

The function of this laboratory is to develop and evaluate candidate
communications software. Software functions such as antenna management
and fault isolation, detection, and recovery are supported. Hardware
simulators are also developed to support testing of prototype software.
The following are representative tasks the contractor shall perform:

9.2.11.1 Develop and maintain prototype software and hardware
simulators. Evaluate software techniques or performing communications
software functions.

9.2.12 Communication Systems Simulation Laboratory

The function of the Communication Systems Simulation Laboratory (CSSL)
is to use computer based simulations of space communications systems to
aid in their design and performance analysis. There are two basic
simulators which are used in CSSL: a communications signal analysis
simulator called the Block Oriented Systems Simulator (BOSS) and radio
frequency coverage simulator called the Dynamic Environment
Communication Analysis Testbed (DECAT). These simulators are used for
system design, design verification/optimization, derivation of system
level specifications, flight hardware test result predictions and
anomaly investigations, operational performance predictions, and
operational anomaly investigations. The following are representative
tasks the contractor shall perform:

9.2.12.1 Develop and maintain both the BOSS and DECAT simulators and
their hardware platforms

9.2.12.2 Develop communication system element models reflecting system
parameters to support simulations on both the BOSS and DECAT.

9.2.12.3 Develop and maintain structure models, trajectories, antenna
patterns, and planet dynamics to support the DECAT.

9.2.12.4 Develop and maintain graphical representation capabilities for
both the DECAT and BOSS.

9.2.12.5 Assist in the evaluation of simulator results to analyze
blockage due to vehicle structures and planets, communication link
performance, power flux density calculations, and radio frequency
interference.

9.2.13 Government Furnished Equipment (GFE) Flight Hardware Maintenance
Facility

The function of the GFE Flight Hardware Maintenance Facility is to
provide radio frequency communication transceiver field support, as well
as testing, evaluation, repair, and development of GFE. The following
are representative tasks the contractor shall perform:

9.2.13.1 Conduct preflight and postflight tests of GFE communications
systems.

9.2.13.2 Repair and disposition government furnished flight and training
communications equipment.

9.2.13.3 Operate and maintain ground support test equipment for GFE.

9.2.13.4 Provide real-time mission support and postflight anomaly
investigations for GFE flight items.

9.2.14 Bond Room Facility

This function supports the bond room facility which houses flight
hardware and flight-related equipment under secure and controlled
conditions. The following are representative tasks the contractor shall
perform:

9.2.14.1 Operate the facility for the receipt of flight and
flight-related properties into storage, their maintenance while in
storage, and issue to authorized users.

9.2.14.2 Operate and maintain a program stock inventory control system
that identifies and records ail transactions necessary for compliance
with regulations contained in NHB 4100.1B.

\*\*\*From Schedule A, NCAD, 3.2.3, NCAD Labs, 3.2.3.1 Inertial Systems
& Inertial Components Lab:

9.2.15 Inertial Systems and Inertial Components Laboratories

The function of the Inertial Systems Laboratory (ISL) is testing of
inertial guidance systems and inertial sensor systems. The principal
elements of the ISL are two-test tables and the computerized IMU data
base system. The ISL is a Certified Interim Repair Depot for the shuttle
IMUs. The ISL supports verification and calibration of the Shuttle
Orbiter IMUs; the High Accuracy Inertial Navigation System (HAINS); IMU
design, development, verification; calibration of other inertial sensor
systems; engineering development of software and hardware tests; and is
the residence for the IMU data base. The function of the Inertial
Components Laboratory (ICL) is testing of a wide variety of inertial
sensors (gyroscopes and accelerometers). The ICL also has the capability
to test gimbal angle resolvers and gyro spin motors. The principal
elements of the ICL are two precision position/rate tables, three
precision position tables, one resolver test stand, and one precision
torque motor test station. The ICL supports test evaluation of the
inertial components for the Shuttle IMU's, calibration of inertial
sensor instrumentation, and test evaluation of state-of-the-art
gyroscopes and accelerometers which are candidates for future NASA/JSC
programs. The following are representative tasks the contractor shall
perform:

9.2.15.1 Operate the ISL in accordance with the requirements as a
Certified Interim Repair Depot. Perform anomaly testing, repair, and
repair verification testing. Coordinate repair activities, the
acquisition, storage, transportation, and safe keeping of the SRU's
involved in an IMU repair. Update the repaired IMU configuration records
and data pack to reflect all repair actions and testing that occurred.

9.2.15.2 Calibrate orbiter IMUs to assure the flight-ready status of the
inertial measurement units delivered from the IMU manufacturer. Schedule
calibrations; perform calibration tests; perform engineering analysis of
all parameters with respect to the IMU specifications; perform retests;
pursue the analysis of anomalies or abnormalities discovered; maintain
test records and test article data files; and issue documentation that
substantiates the flight worthiness of the spare units.

9.2.15.3 Establish and maintain a computer based file for all IMU
calibration data generated by the Space Shuttle Program. Maintain this
computerized file in the ISL at NASA/JSC. Incorporate data as it becomes
available, correct erroneous data elements, and safeguard the contents
of the data base files. Distribute the data contained in the data base
through periodic reports, in response to valid special requests, and in
specialized forms to meet the needs of various users. Issue preflight
reports and support definitions/verifications of hardware unique
I-loads. Maintain integrity of the data base files, the test software,
and the computer operating systems, and all computing equipment to
perform these tasks.

9.2.15.4 Support SAIL test activities and perform the engineering
analysis of anomalies or fission-unique requirements that occur during
verifications.

9.2.15.5 Perform test evaluations, analyses, and verification. Provide
the technical expertise to review design documentation, support design
review meetings, assist in monitoring the technical aspects of the
program with special emphasis on analysis of system performance
characteristics and preparing test plans and test schedules.

9.2.15.6 Perform the test evaluation, and analysis of data for inertial
sensors or inertial sensor systems which are assigned to the ISL or ICL.
Perform the test preparation, design and fabricate interface and data
acquisition systems, prepare test plans, conduct tests, analyze data and
issue test reports.

\*\*\*From Schedule A, NCAD, 3.2.3.2 EOL/Tracking Lab:

9.2.16 Electro-Optics Laboratory (EOL)/Tracking Laboratory (TL)

The function of the EOL/TL is to perform experimental studies of
developmental and flight operational problems encountered with the star
tracker, horizon sensors, and image intensifier devices. The function of
the Tracking Laboratory is the testing of flight star tracker units with
real stars and in the development and evaluation of prototype star
trackers and sensor devices. Responsibilities include the study, design,
development, and evaluation of candidate guidance and navigation
systems, subsystems, and components. The following are representative
tasks the contractor shall perform:

9.2.16.1 Provide the definition, development, implementation, test, and
evaluation of hardware, engineering breadboards, and engineering test
beds for GN&C components and subsystems that will become part of
advanced space vehicle GN&C systems. The following are representative
tasks the contractor shall perform:

9.2.16.2 Perform tasks associated with the definition, development,
test, and evaluation of optical, guidance, and navigation hardware,
software, breadboards, and test beds. These tasks shall include the
design and development of hardware and software for the application of
current technology to optical navigation and pointing sensors. This
includes the development of mass storage systems for star catalogs,
interactive structural graphics, and related components to optimize
placement of advanced space vehicle optical sensors which will be
utilized in guidance and navigation systems. Support testing of sensor
hardware at remote sites (Sam Houston State University Campus
Observatory and others).

\*\*\*From Schedule A, NCAD, 3.2.3.3 Interactive Analysis Lab:

9.2.17 Interactive Analysis Laboratory

The function of the Interactive Analysis Laboratory is to host GN&C
analysis simulations which drive sophisticated graphics including
complex solid and wire-frame models, which run in real or non-real time,
and which can be adjusted mid-run by the interactive analyst. The
following are representative tasks the contractor shall perform:

9.2.17.1 Generate graphics system hardware and software dependent code
in the languages and operating systems as defined by the Government.
Software also includes networking of all systems, model and object
generation for all systems, simulation data generation, and
communications between a real-time simulator and the graphics system.

9.2.17.2 Generate post simulation documentation, training material in
graphics and video form, as well as documentaries in video form. Typical
tools include extended animation software packages.

9.2.17.3 Perform all interactive Analysis Laboratory software and system
maintenance.

9.2.17.4 Analyze graphics systems, presenting recommendations to NASA
with respect to applicability and future needs, and implement graphics
interface software to operate these devices.

\*\*\*From Schedule A, NCAD, 3.2.3.4 Technology Insertion Lab:

9.2.18 Technology Insertion Laboratory (TIL)

The function of the TIL is to provide a facility which can be used to
rapidly and efficiently design, and test avionics configurations for
multi-vehicle use. Sample capabilities include a central repository for
engineering data and information accessible by government and industry;
hardware and software assets to develop and evaluate avionics concepts
and technologies employed in the design of transportation systems; the
capability to conduct subsystem analysis and performance evaluations;
the capability to conduct high fidelity end-to-end simulations
containing prototype avionics systems for purposes of validating
performance and architectures; and the capability to conduct integrated
hardware-in-the-loop simulations for the purpose of demonstration,
evaluation, validation, and verification. The following are
representative tasks the contractor shall perform:

9.2.18.1 Support TIL activities such as the definition, development,
test, evaluation, and integration of hardware, software, breadboards,
and test beds. These tasks include the definition and development of
advanced space vehicle GN&C math models and their integration into a
flight control system test bed simulation; the definition and
development of advanced space vehicle emulators and their integration
into a GN&C test bed simulation.

9.2.18.2 Develop software math models, interface drivers, and graphic
displays for development and integration task.

\*\*\*From Schedule A, FDSD, 4.2.3 Laboratories:

\*\*\*From Schedule A, FDSD, 4.2.3.1 JAEL:

9.2.19 JSC Avionics Engineering Laboratory (JAEL)

The following are representative tasks the contractor shall perform:

9.2.19.1 Support the design, fabrication, installation, and checkout for
system cables, equipment racks, switch panels, and test equipment to
provide an operation and maintenance of the lab to enable to lab to
function as a GPC test station.

9.2.19.2 Utilize existing equipment such as a Shuttle/Orbiter cockpit
mockup, various computers and computer systems, special/unique interface
hardware, and standard test equipment to support the design and
development of Aft Station Command and Data System that separates the
payload and Orbiter data system functions.

9.2.19.3 Support the design, development, and fabrication of prototype
instrumentation systems. Services required include engineering design,
test, analysis, configuration changes, equipment modifications, and
documentation reports. Support short-term tasks which include infrequent
SAIL test data analysis support and bench tests performed on flight
components such as the Orbiter Multiplexer/Demultiplexer (MDM).

9.2.19.4 Support long-term advanced development projects performing
tasks such as interface studies, design, test, verification,
modifications, data analysis, and implementation of the latest
hardware/software technology. One area of application will be with the
interface between the Orbiter vehicle data processing system and the
space station data management system network.

\*\*\*From Schedule A, FDSD, 4.2.3.2:

9.2.20 Flight Data Recorder Laboratory

The following are representative tasks the contractor shall perform:

9.2.20.1 Perform the activities to keep flight data recorders
operational. These recorders include the Shuttle Tape Recorder (STR) and
the Modular Auxiliary Data System (MADS) Recorder. Typical support
activities include: maintenance and repair; functional and operational
testing; failure verification and analysis; and flight certification and
calibration. Other activities include evaluation of recorder
performance; providing specialized tape recorder data retrieval support;
developing methods and procedures for tape recorder post flight data
quality determination; and performance assessment utilizing post flight
data dumps.

9.2.20.2 Provide engineering and technical support for a new Payload
High Rate Recorder (PHRR) including integrating the recorder into the
Shuttle; providing design modifications; testing to insure that all
requirements are satisfied; designing and procuring equipment for an
automatic test station; flight certification; maintaining the equipment
when it is operational; providing command capabilities from the payload
general support computer; and providing an interface box to make the
system compatible with other payloads.

9.2.20.3 Provide the engineering and technical support for the
evaluation of new mass data storage techniques including the procurement
of off-the-shelf devices that could be used to replace the current tape
recorder systems; evaluation of devices for space flight; generation of
a set of requirements for an advanced recording system; and procuring
and certifying the new technology mass storage system.

\*\*\*From Schedule A, FDSD, 4.2.3.3:

9.2.21 Instrumentation Laboratory

This function provides Avionics Systems with the capability for
providing engineering support in five technical areas. They include: (1)
maintenance and operation of flight data recorders and evaluation of
advanced storage techniques; (2) design and development of miniaturized,
self-contained instrumentation devices; (3) design, development,
testing, evaluation, and qualification of flight portable computers; (4)
design, development, testing and certification of flight display and
control panels; and (5) evaluation of advanced flight data systems
concepts including command and control techniques. Avionics Systems
operates laboratories for each of these major work areas. The following
are representative tasks the contractor shall perform:

9.2.21.1 Provide the engineering and technical support design,
fabricate, test, and analyze flight instrumentation systems. Activity
shall include procurement, operational support, maintenance of
instrumentation, and building flight hardware, engineering breadboards
and test beds. Typical instrumentation systems include the Portable Data
Acquisition Package (PDAP) which is a portable data recorder suited for
use in the Space Shuttle and the Stand-Alone Measurement Device (SAMD)
which is a miniaturized, self-contained, measurement system. This device
can be used to measure pressure, strain, acceleration, temperature,
vibration, and other parameters.

9.2.21.2 Provide support for design improvements to reduce power, add
additional battery power, and additional memory, change the type of
memory being used, ruggedize the memory, and provide various types of
smart switches, and also provide support for test facilities to support
advanced space vehicle sensor developments.

\*\*\*From Schedule A, FDSD, 4.2.3.4:

9.2.22 Portable Computer Laboratory

The following are representative tasks the contractor shall perform:

9.2.22.1 Perform maintenance, operation, and engineering tasks for
flight portable computers, such as the current Payload and General
Support Computer (PGSC) including modification of existing designs to
flight configuration; maintenance and repair; functional and operational
testing; failure verification and analysis; flight certification and
calibration; provide operational user support, define payload software
interfaces, document a user software interface and configuration control
plan; perform engineering evaluations of off-the-shelf interfaces.
Evaluation of new portable computers, and associated software/hardware.
Current bans require flying other types of portable computers utilizing
software with advanced capabilities for evaluation by the Space Shuttle
crews. Support procurement of hardware and software, modifications to
meet flight requirements, flight certification and testing, and
operational and user support.

9.2.22.2 Maintain and operate a secure bond room for the temporary
storage of the PGSC computers. This facility would also be used to
accommodate SPDCI panels, and other flight hardware on an as needed
basis. The bond room would be operated in accordance with standard
procedures for shipping, receiving, and storing space flight hardware.

\*\*\*From Schedule A, FDSD, 4.2.3.5:

9.2.23 Display and Control Laboratory

The Displays and Control Laboratory has the capability of supporting the
development and testing of displays and control for various spacecraft
programs. The Standard Payload Display and Control interface (SPDCI) is
a group of panels that include the Standard Switch Panels (SSP), the
Deployment Pointing Panel, the Manual Pointing controller (MPC), the TV
Monitor Panel, and the Color TV Monitor Panel. These panels are located
in the payload station of the AFT flight deck of the Shuttle Orbiter on
an as required basis. They are provided for use by the payload community
to control their payload. The laboratory has the capability to perform
hardware, software, and implementation studies. The following are
representative tasks the contractor shall perform:

9.2.23.1 Maintain operational readiness of the SPDCI. Modify existing
designs to flight configuration; design and build new hardware; certify
for flight; and provide operational user support.

9.2.23.2 Provide support for research and development activities in the
area of displays and controls.

9.2.23.3 Support the development of simulation and test environments.

\*\*\*From Schedule A, FDSD, 4.2.3.6:

9.2.24 Real-time Systems Engineering Laboratory (RSEL)

RSEL contains a number of the personal and engineering workstations in a
reconfigurable environment that are used to develop space systems
network standards and interface technologies.

9.2.24.1 Provide support to Avionics Systems for research and
development activities in the RSEL. Support development of simulation
and test environments, test beds, prototypes including ultra reliable
computers, and data management and verification technology assessment.

\*\*\*From Schedule A, FDSD 4.2.4, Facilities:

9.2.25 Software Development Facility

The following are representative tasks the contractor shall perform:

9.2.25.1 Review and evaluate disaster recovery, risk analysis, data
management, print reduction, communications traffic, and automated
operations plans for the SDF.

9.2.25.2 Recommend modifications and/or additions to existing and
proposed facilities management plans in order to comply with JSC Safety,
Reliability, Maintainability, and Quality Assurance standards.

9.2.25.3 Analyze process flows of proposed facility modifications in
order to determine production impacts and optimum planning and
scheduling of critical activities.

9.2.25.4 Provide support in the development of oracle data bases and
control programs intended to support security objectives instituted in
the SDF.

9.2.25.5 Support of various NASA working groups to coordinate schedule
activities.

9.2.25.6 Review and evaluate system processes for engineering validity,
optimal process flow, and process cost effectiveness. Develop and submit
system process flow optimization techniques.

9.2.25.7 Provide support in implementing and maintaining AIS security
requirements and processes for the facility and applications.

\*\*\*From Schedule A, FDSD, 4.2.4.2:

9.2.26 Avionics Development Facility (ADF)

The ADF is defined in the ADF Product Specification, MDC H4693 and the
ADF Test Management System Product Specification, MDC H4694. The
following are representative tasks the contractor shall perform:

9.2.26.1 Provide support to Avionics Systems for technical management of
ADF development and operation. Support design analysis, analysis of Work
Package 2 test plans for software and selected avionics systems, and
requirements and design analysis for system and ORU simulations.

\*\*\*From Schedule A, FDSD, 4.2.4.3:

9.2.27 Central Software Facility/Central Avionics Facility

This function provides the Space Station Avionics Verification of the
Avionics Systems with the capability for management of the design,
development, implementation and operations of the Central Software
Facility/Central Avionics Facility (CSF/CAF) and the planning,
definition and execution of Space Station Program integrated software
and avionics verification performed at these facilities. The space
station Level II Integration Contractor has the responsibility for the
facilities design and verification requirements definition and
subsequent analysis of the verification prods. The Space Station Work
Package 2 contractor has the responsibility to design, develop,
implement and operate these facilities, in addition, Avionics
Verification is responsible for the management of the mode team
activities associated with the development of the integrated avionics
flight system software requirements and the development of the
integrated flight software builds. The following are representative
tasks the contractor shall perform:

9.2.27.1 Support the development and implementation of a verification
process network that tracks all integrated avionics and software systems
verification requirements from definition through test completion, data
analysis, and certification as ready for flight.

9.2.27.2 Support the identification, collection and integration of
integrated avionics and software test requirements for CSF/CAF testing.
Provide Space Station Program systems analysis to help ensure all
systems adequately identify requirements, logistics and technical
support for the collection of requirements from all Space Station
Program participants. Provide support to the Test Requirements
Integration Group (TRIG) in defining and integrating verification
requirements so that the minimum test set to meet all requirements is
defined and will support the development of the Test Requirements
Documents (TRDs), test matrices, and Test and Checkout Procedures (TCPs)
for CSF/CAF testing.

9.2.27.3 Support the development, definition, and integration of
requirements to define, develop, implement, certify and operate the
CSF/CAF. Provide support to interface and coordinate facility
requirements with NASA technical services in defining facility interface
control documents and the implementation of those interfaces. Support
analysis tasks to ensure requirements can be met within cost
constraints, that the design meets all requirements, that the design can
be implemented within budgets, and will support the definition of
acceptance plans and criteria. Support systems requirements definition
for power, temperature control, logistics, space, special test
equipment, and electrical systems including facility grounding
requirements.

9.2.27.4 Support the development of simulations of environments and
systems necessary to develop and operate the CSF/CAF as an integrated
avionics and software verification facility. Support math model working
group activities and include simulation math model requirements
definition, analysis of proposed models for adequacy to meet
requirements, model interface definitions, analysis of implementation
problems, and definition of acceptance criteria requirements.

9.2.27.5 Support the development of the CSF/CAF with systems engineering
analysis studies of development plans and approaches to ensure schedules
are met within budgets and the product will support requirements.
Provide studies of plans for integration of the program systems,
resident software, and ancillary equipment such as data systems.
Participate in requirements and design reviews, conduct analysis of
interfaces defined in Flight System Software Requirements (FSSR),
evaluate software integration and build plans and procedures, trade
studies of system models versus use of actual hardware, and conduct
analysis of test control systems and procedures.

9.2.27.6 Support the management and planning of the facilities
configuration to support the stage certification/verification as the
Space Station Program evolves through the assembly process to Man-Tended
Configuration and Permanent Human-tended Configuration. The available
verification time in the staged assembly schedules requires that the
facilities be in parallel configurations at any given time to be
verifying one stage configuration while upgrading/integrating the next
stage configuration. Define future hardware/software deliveries, define
necessary facility support modifications and provide the scheduling of
parallel verification/integration/checkout operations.

9.2.27.7 Support the selection/development, implementation and
validation of CSF/CAF environment and systems simulation math models.
Provide selection/development analysis support, interface test case
analysis and development, off-line test and certification data
development, and test and checkout support on the facilities.

9.2.27.8 Support the management of the integrated software and avionics
testing in the CSF/CAF. Provide test design, and development, test
execution, post-test acceptance decisions, retest decisions and
post-test data analysis.

9.2.27.9 Support the development, implementation and operation of a
configuration management system for the CSF/CAF avionics software and
facilities. Provide support to the selection/development of a system,
its implementation, and its maintenance and operation. Provide technical
and analytical audit support for evaluation of Level II/III program
changes for impact on the CSF/CAF.

9.2.27.10 Support the review, evaluation and analysis of CSF/CAF support
systems such as the ITVE and SSE.

9.2.27.11 Provide technical and logistical support to the Integrated
Avionics Mode Team, including collecting, organizing and distributing of
mode team associated data and information, overseeing the coordinated
development of the Flight System Software Requirements (FSSR) documents,
and analysis and recommendations for integrated avionics verification
testing.

9.2.27.12 Provide technical and logistical support to the integrated
Software Build Mode - Team process for the integrated software build
utilizing components provided by the Space Station Program participants.
Trace software schedules, review software build plans and requirements
from all participants, support definition of integrated software build
requirements and operations at the CSF, horizontal integration into a
mass storage build, and testing of the flight reconfigured software.
Provide analysis support for CSF/CAF required changes to support
software verification for each mission.

\*\*\*From Schedule A, FDSD, 4.2.4.4:

9.2.28 Technical Library

The following are representative tasks the contractor shall perform:

9.2.28.1 Operate and maintain a library to control all documentation
associated with Avionics Systems' facilities including both vendor and
in-house-built equipment drawings, listings, manuals, system software
tapes and documentation, operational software tapes, disks, decks and
associated descriptions, change documentation, configuration control
panel official minutes, and simulation/testing data tapes. Maintain a
complete master set of documentation and provide for updating in accord
with official modifications. Provide updated copies to all users of
record. Use an automated system capable of retrieving documents or other
stored media to accomplish the record maintenance.

\*\*\*From Schedule A, FDSD, 4.2.4.5:

9.2.29 Building Facilities Design and Integration

The following are representative tasks the contractor shall perform:

9.2.29.1 Assist in the definition of building support services required
by Avionics Systems technical systems including provisioning for
electrical and hydraulic power, air conditioning, facility
modifications, special test equipment, laboratory equipment, and
personnel space. Generate and maintain an equipment list based upon
system and subsystem designs which contain equipment characteristics
such as power requirements, cooling requirement, and spatial dimensions.
Prepare laboratory layouts which provide information on required power
source size and location.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

9.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

9.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

10\. ADVANCED DEVELOPMENT

\*\*\*From Schedule A, 8.1.1, SED

10.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

10.1.1 Program Management Support

**10.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP), Space Station Program, and Human Exploration and
Development of Space (HEDS) Program. The following are representative
tasks the contractor shall perform:

**10.1.1.1.1 Systems Engineering and Integration** - Support
multidiscipline projects involving multiple functions. This includes
project management and multi-discipline technical support for projects
requiring definition, design, research, development, fabrication,
integration, and testing of complex facilities, systems, flight and
flight-like hardware.

10.1.1.1.2 Systems Engineering Analysis, and Trade Studies

10.1.1.1.2.1 Provide analysis support for mission definition, design and
development, system requirements, and system design evaluations for
current and future NASA programs and projects; provide analytical
studies to assess alternate mission and system design options; provide
technical integration across program elements; assist in providing
technical direction to other contractors; and perform independent
analysis.

10.1.1.1.2.2 Provide engineering and analysis to support performance
scans and trade studies leading to the selection of optimum systems and
operations performance profiles and trajectory parameters for current
and future NASA programs and projects. Study areas include the
functional areas of system performance and resource utilization for
electrical power, thermal, Environmental control and Life Support
Systems (ECLSS), and propulsion; orbit strategy and maintenance;
resupply missions and return from human bases; integrated stem design
verification; design cycle planning and implementation; ascent, descent,
rendezvous, proximity operation, and navigation; attitude and pointing;
separation analysis; and tethered satellite dynamics analysis.

10.1.1.1.3 Engineering Design and Development Products

10.1.1.1.3.1 Perform product design, development, and delivery, for
those products associated with the systems performance, resource
utilization, trajectory control, and logistics (resupply and return) of
current and future NASA program vehicles and elements from the
conceptual design phase through the development and operations readiness
phases of these programs.

**10.1.1.1.4 Simulation Development** - Define requirements for
simulations, test beds, flight demonstrations, and X Vehicles; formulate
requirements to the equation level; and size the simulation in terms of
manpower, cost, schedule, and verification-plan. Convert simulation
requirements into math models and integrate them with the simulation
executive; execute and analyze test cases in accordance with the
verification plan. Support the software simulations and math models
including flight mechanics, dynamics, and hardware math models; stand
alone guidance, navigation, and control math models; and integrated
Monte-Carlo and linear covariance simulations employing the above math
models.

**10.1.1.1.5 Analysis** - Define analysis plans and products as well as
size the task in terms of labor, cost, and schedule Perform analysis
studies including: flight phase performance envelopes affected
(thrust-to-weight ratio, lift-to-drag ratio, ballistic coefficient,
delta-V, stage mass split, throttle range, maximum angular accelerations
for control, and navigation measurement types); flight phase and systems
compatibility assessments; and navigation performance envelopes
supporting the flight phases.

**10.1.1.1.6 Analytical Development** - Define analytical development
plans and products as well as size the task in terms of labor, cost, and
schedule. Derive the supporting flight phase analytics, for the
following models: Monte-Carlo; linear covariance; guidance and
targeting; navigation; control; flight mechanics; dynamics; and control
and navigation hardware.

**10.1.1.1.7 Requirements Development** - Define flight phase
performance parameter requirements such as thrust-to-weight ratio,
lift-to-drag ratio, and ballistic coefficient. These requirements are
derived from flight phase performance envelopes and/or are compatible
with programmatic requirements and guidelines.

**10.1.1.1.8 Test Analysis** - This function provides the analytical
effort required to implement test programs in compliance with official
test requirements documentation. This includes early participation in
requirements definition and analysis, preparation of test implementation
requirements sheets, generation and/or modification of math model
formulations and expert systems specifications, evaluation and
generation of proposed hardware and/or software changes required to
implement tests, analysis of system problems for the purpose of
recommending solutions and other system analysis in support of test
operations. The following are representative tasks the contractor shall
perform:

10.1.1.1.8.1 Analyze official requirements documents with respect to
satisfying the requirements through facility tests.

10.1.1.1.8.2 Prepare implementation plans for each task to be performed.
These plans shall include laboratory element implementation requirements
and initial conditions if they are lacking in other documents.

10.1.1.1.8.3 Generate and/or modify simulator math models and expert
systems in compliance with new requirements to be satisfied by the
Advanced Development facility.

10.1.1.1.8.4 Perform system analysis studies in support of test design
and configuration definition in response to test requirements.

10.1.1.1.8.5 Optimize/prioritize tests for maximum support.

10.1.1.1.8.6 Perform test status reviews to determine omissions,
schedule problems, and adequacy of test and checkout procedures.

**10.1.1.1.9 Advanced Planning and Implementation** - This function
provides the planning, engineering, and implementation of systems in
support of long-range requirements. Included are analysis of system
design requirements, planning of facility and equipment and
modifications, development of test requirements, development of
supporting software, development of math models and expert systems
specifications for advanced systems, and the conduct of test support
operations. The following are representative tasks the contractor shall
perform:

10.1.1.1.9.1 Participate in Systems Engineering advanced planning
functions to determine requirements for an effective simulation;
establish coordination with outside groups which will use the simulator
or obtain data from test runs; estimate labor, costs, and schedules for
the project; prepare work packages to give specific task assignments,
detailed schedules, and formal review points; and define facility
requirements such as power, space, and cooling.

\*\*\*NOTE: 10.1.1.1.9.2 has been edited from the ORIGINAL Schedule A,
8.1.1.1.9.2 to delete the reference:

10.1.1.1.9.2 Implement advanced planning simulation tasks.

10.1.1.1.10 Systems Engineering (SE) Process Development

10.1.1.1.10.1 Provide systems engineering services to projects,
including the Common Lunar Lander (CLL) and Personnel Launch System
(PLS) projects. This effort shall include continuous refinement of
systems engineering environment, conduct of rigorous pre- Phase A and
Phase A systems studies, incubation of new process teams, cost/schedule
plan proposals, requirements analysis, risk analysis (cost, schedule,
quality, and performance), evaluation of SE tools, and communication of
results to all cognizant program and functional organizations. Report
variance with requirements to NASA technical personnel.

10.1.1.1.10.2 Provide systems engineering support to the Systems
Engineering Process Improvement Team (SEPIT) and SEPIT Project
Management Team. This effort shall include to document tree, data
dictionary, detailed definition of life cycle charts, generic project
life cycle update plan, definition phase project review, project
implementation plan, and detailed project plans for development of later
phase products; and report variance with requirements to NASA technical
personnel.

\*\*\*From Schedule A, SED 8.1.2 R&D:

10.1.2 Research and Development Support

10.1.2.1 Advanced Development

\*\*\*From Schedule A, SED, 8.1.2.1:

**10.1.2.1.1 Systems Requirements** - This function involves the
integration of future mission plans into a consistent and rational
scenario. This will include analyzing the missions to define elements
and systems requirements. Missions include transportation to low Earth
orbit, interplanetary transportation, and planetary surface
inhabitation. The following are representative tasks the contractor
shall perform:

10.1.2.1.1.1 Analyze proposed future missions to identify elements and
systems including those which may result from utilization of
extraterrestrial resources; define requirements for elements and
systems; assemble recommended future mission sets; and determine the
impact of future missions and scenarios on currently approved spacecraft
such as the space station and next generation earth-to-orbit vehicles.

10.1.2.1.1.2 Determine the impacts of new technologies on proposed
future missions; compare costs of developing these technologies with the
benefits; and prepare technology development plans.

10.1.2.1.1.3 Provide development and implementation of systems sizing
and weight estimation algorithms.

10.1.2.1.1.4 Support the definition of missions operations (including
on-orbit) and servicing requirements to supply the logistics for the
surface activities and assist in the definition of systems which
minimize labor intensive operations.

10.1.2.1.1.5 Design and integrate subsystems, and determine the impacts
of the environment on the system during operations.

10.1.2.1.1.6 Systems Design and Analysis function involves the system
definition, design, development, test, and evaluation phases of current
and advanced spacecraft programs. The primary responsibility is to
determine the system level design requirements and specifications and to
develop and evaluate configuration concepts for advanced human-tended
and non-human-tended spacecraft. The spacecraft and systems to be
considered include new transportation systems (next generation human
transportation systems, launch systems, upper stages), orbiting systems
(platforms, transportation nodes, growth space station concepts), lunar
and Mars base systems to support permanent human presence. The following
are representative tasks the contractor shall perform:

\*\*\*From Schedule A, SED, 8.1.2.1.2:

**10.1.2.1.2 System Design and Analysis** - This function involves the
system definition, design, development, test, and evaluation phases of
current and advanced spacecraft programs. The primary responsibility is
to determine the system level design requirements and specifications and
to develop and evaluate configuration concepts for advanced human tended
and non-human-tended spacecraft. The spacecraft and systems to be
considered include new transportation systems (next generation
human-tended transportation systems, launch systems, upper stages),
orbiting systems (platforms, transportation nodes, growth SSF concepts),
lunar and Mars base systems, to support permanent human presence. The
following are representative tasks the contractor shall perform:

10.1.2.1.2.1 Provide programming, implementation, documentation, and
maintenance support to the development of an integrated analysis
capability including design and analysis computer programs, interfaces,
data bases, and their integration into an interactive, integrated design
and analysis system. The existing IDEAS\*\*2 program will be the basis
of this capability. Programs to be enhanced or added include: dynamic
simulations; vehicle/systems sizing algorithms; and weight/mass property
estimation routines, state of the art visualization and graphics tools,
and programs that enable a collaborative, distributed environment.
Industry standard protocols such as CORBA shall be used to link existing
engineering applications. Perform systems engineering functions for the
implementation and operation of the integrated design environment.

10.1.2.1.2.2 Perform vehicle/systems conceptual design studies and
configuration development analyses leading to the development of system
level specifications; perform investigation of vehicle performance
requirements and subsystem integration requirements to establish an
integrated space system concept.

10.1.2.1.2.3 Perform analyses of on-orbit systems (platforms
transportation nodes), including the dynamics, controllability, mass
properties of the systems, for the purposes of developing systems-level
requirements or assessing concept feasibility. The Space Systems
Integrated Simulation (SPASIS) tool is currently being used.

10.1.2.1.2.4 Perform test and verification planning for concepts in the
Pre-Phase A and Phase A stage.

10.1.2.1.2.5 Assist in assessing overall system, and subsystem risk for
concepts which they are analyzing. Include technical, cost, and
programmatic risks.

10.1.2.1.2.6 Develop costing algorithms appropriate to the concept
development phase of a project and perform costing analyses on current
and new projects.

10.1.2.1.2.7 Provide illustrations of vehicle or system concepts using
both hand-drawn renderings or computer-aided design (CAD) tools
available in Advanced Development. Create more detailed computer-aided
solid models of concepts, which could be used to perform systems
analyses. The IDEAS\*\*2 software and analysis packages are currently
used to perform this analysis.

\*\*\*From Schedule A, SED, 8.1.2.1.3:

**10.1.2.1.3 Trajectory, Mission/Performance Analysis, and
Integration** - The following are representative tasks the contractor
shall perform:

10.1.2.1.3.1 Perform trajectory, mission analysis, performance analysis,
and integration subtasks as well as associated software tool an-data
base development, maintenance, and modification to support planetary
orbital, lunar, and interplanetary mission definition and development
for current and advanced program vehicles. These tasks ultimately lead
to the definition and development of vehicle/system design
requirements/assessments.

10.1.2.1.3.2 Define and determine lunar and interplanetary mission
opportunities, trajectories, and specific Earth departure and return
windows; define and develop lunar and interplanetary one-way and round
trip nominal and abort trajectory strategies, lunar and planetary
orbital and surface stay-time strategies and relationships to outbound
and return trajectories, propulsive delta velocity requirements, and
end-to-end mission timelines.

10.1.2.1.3.3 Define and develop Design Reference Missions (DRM's) for
the assessment of spacecraft operations, configurations, and systems
design. The DRM's shall include event timelines, payload schedules,
mission manifests, resupply/return requirements, propellant
requirements, operational descriptions, and system operating concepts.

10.1.2.1.3.4 Provide detailed analysis of selected flight phases (e.g.,
reboost), as well as trajectory-related analysis for various space craft
elements. This activity shall include support for spacecraft orbital
design requirements/definition, operational trajectory scenario
development, and rendezvous profile analysis.

10.1.2.1.3.5 Compile, integrate, and develop spacecraft resupply/return
requirements, as well as strategic-level manifest planning analysis to
identify and evaluate primary driver sensitivities (e.g., flight rate,
logistics carrier sizing, altitude strategy, propellant system).

10.1.2.1.3.6 Provide integration of spacecraft design assessments
comparing current spacecraft design to the DRM's and including a broad
range of assessments such as resource utilization, resupply/return
analyses, and GN&C analyses.

10.1.2.1.3.7 Develop Assembly/Operations Engineering Assessments
(AOEA's) operations planning concepts, user accommodations assessments,
and mission manifesting concepts.

10.1.2.1.3.8 Generate payload schedules to support DRM development,
assessments and resupply/return analyses based on selected resources
required for the latest payload sets.

10.1.2.1.3.9 Navigation performance capability as a function of
alternative basing and hardware configuration including Earth based
(DSN, TDRSS) and local based (Radiometric, optical, and IMU/Spacecraft
based).

10.1.2.1.3.10 Flight phase spacecraft required performance
characteristics and optimal trajectory control strategies including
ascent (propulsive delta V, thrust-to-weight ratio, stage mass split,
throttle range, optimal trajectory control), descent (ballistic
coefficient, L/D, maximum angular accelerations for control, propulsive
delta V throttle range, number and location of landing sites) and
rendezvous (navigation and communication instrumentation capability,
thrust-to-weight ratio, propulsive delta V).

10.1.2.1.3.11 Develop, maintain, modify, and document software tools to
support trajectory, mission/performance analysis, and integration.

\*\*\*NOTE: Schedule A, SED 8.1.2.1.4 System Performance and Resource
Utilization went to NEW SOW Part I, Section 1.

\*\*\*From: Schedule A, SED 8.1.2.2

10.1.3 Other R&D Support

**10.1.3.1 Workshops** - The purpose of this function is to facilitate
large, multi-organizational, technical meetings or workshops. conducted
under the sponsorship of the Systems Engineering Division. The following
are representative tasks the contractor shall perform:

10.1.3.1.1 Provide the logistical support for technical workshops.

10.1.3.1.2 Provide support to SED supported workshops for the purposes
of recording significant findings and contributing to the intended
purposes of the meeting.

10.1.3.1.3 Provide drafting, data entry, plotting data, flow charting,
and technical writing.

10.2 LABORATORY/FACILITY SUPPORT SERVICES - N/A

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

10.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

10.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

# PART I - AREAS OF SUPPORT

######### SECTION B: SPACE AND LIFE SCIENCES

11\. MEDICAL AND MISSION SCIENCE

11.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

\*\*\*NOTE: Schedule B, Part 3, 1.0 went to NEW SOW Part II, Mission
Science Management.

11.1.1 Program Management Support

\*\*\*From Schedule A, LSPD, 10.1.1.1 Multiprogram, this is to cover the
CHeCS support:

**11.1.1.1 Multiprogram** - The program management functions described
below are applicable to multiprograms including the Space Shuttle
Program (SSP) and space station program. The following are tasks the
contractor shall perform:

**11.1.1.1.1 Science Operations Support** - Provide mission support to
operations personnel in terms of payload mission management, flight and
ground protocol development, on-orbit and pre- and post-flight
operations support, and post-flight data reduction support.

**11.1.1.1.2 Science Missions Support** - Provide engineering support to
ensure that mission objectives are carried out consistent with vehicle
capabilities and applicable NASA policies.

**11.1.1.1.3 Project Engineering Support** - Support engineering
hardware/software development. Prepare concept drawings; detailed
engineering and fabrication drawings; engineering studies including
trade-offs; evaluations, lay-outs, cost and schedule analysis;
coordination and interface definition for proper integration into the
space program; structural analysis; dynamic analysis; weight and
center-of-gravity analysis; thermal analysis; consider applicable
elements of Safety, Reliability, and Quality Assurance; and manual and
computer aided generation of engineering drawings.

\*\*\*NOTE: Schedule B, Part 3, 1.1 went to NEW SOW Part II, Mission
Science Management.

\*\*\*NOTE: Schedule B, Part 3, 1.2 went to NEW SOW Part II, Mission
Science Management.

11.1.2 Studies and Assessments

\*\*\*From Schedule A, LSPD, 10.1.1.2 Studies and Assessments, this is
to cover part of CHeCS support:

**11.1.2.1 Studies and Assessments** - The following are representative
tasks the contractor shall perform:

**11.1.2.1.1 Programs Office Support** - Conduct advanced concept
studies; determine technical cost and schedule feasibility; conduct risk
assessments; produce project plans; and plan operations and operations
support scenarios for Space Shuttle Program, space station, and other
life sciences specified experiment programs.

**11.1.2.2 Science Reporting and Documentation** - The contractor shall
help define and document the pre-, in-, and postflight science reporting
requirements for the mission. The contractor shall support NASA in
assembling, coordinating, and disseminating scientific information and
reports resulting from ground or flight experiment operations. The
contractor will aid in the rapid and thorough collation of the data and
documentation. The material shall be stored in an appropriate and
accessible manner. Periodic reports on the status of the payload will be
generated and distributed to NASA management and the PI teams.

**11.1.2.3 Science Coordination** - The participation of the PI's will
be solicited and encouraged during experiment and payload definition,
development, and implementation. The contractor shall provide support,
as required, in the separation and operation of SWT meetings, IWG
meetings, investigator committee meetings, and science status reviews.
Specific tasks include, but are not limited to, logistical support,
documentation, coordination of meetings, distribution of information,
and technical support.

11.2 LABORATORY/FACILITY SUPPORT SERVICES

\*\*\*From Schedule A, LSPD, 10.2.1 General Support Services - this is
to cover part of CHeCS support. EDITED, deleted 1st sentence of original
text:

11.2.1 General Support Services

The following are representative tasks the contractor shall perform:

**11.2.1.1 Advanced Concepts** - Evaluate existing and planned programs;
formulate plans for life sciences laboratory facilities which meet the
stated experiment operational support requirements; and formulate
experiment support plans which optimize utilization of existing JSC life
sciences laboratories.

\*\*\*For Every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

11.3 MAINTENANCE AND OPERATION SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

11.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

12\. SCIENCE PAYLOADS MANAGEMENT

\*\*\*From Schedule B, Part 1, 1.0 Introduction, edited:

The major functional areas for which support is required are as follows:

a\. Project management and control

b\. Project payload management and development

c\. Flight systems engineering

d\. Data systems development and operations

e\. Project science support

f\. Project payload integration and verification

g\. Operational training

h\. Mission operations support

i\. Facility/ground systems engineering and operations

The tasks identified in this SOW support all phases of approved
missions, programs, and projects assigned to science payload management,
including missions on current and all future human and human-tended
vehicles and missions, e.g., Space Shuttle (SS), Spacelab, Extended
Duration Orbiter Medical Project, Detailed-Supplemental Objective,
Spacelab, space station, Space Exploration Initiative (SEI), and Cosmic
Dust Collection Facility. Plans, schedules, analysis, and all other
documentation developed within the scope of this SOW shall be delivered
to the Government for unrestricted use and distribution.

\*\*\*From Schedule A, 9.0, NIO:

12.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

\*\*\*From Schedule B, Part 2, 1.0 INTRODUCTION, edited

The JSC Science Payloads Management and space station Payload Project
Offices plan, organize, manage, and control those activities required to
integrate experiments/facilities into a total payload complement for JSC
assigned pressurized module missions and/or flight increments.
Pressurized module payloads are generally comprised of experiments
and/or facilities from various scientific or technical disciplines
within the user community that can be packaged together to share common
orbiting vehicle capabilities. In support of this office, the contractor
is responsible for providing the manpower and other resources, as
required, to accomplish the tasks identified in this part of the SOW.
Applicable functional areas include:

-   Payload/program management

-   Mission feasibility and design

-   Data management

-   Flight operations

-   Payload integration management

-   Advanced program/planning

    \*\*\*From Schedule A, 9.1.1, NIO:

    12.1.1 Program Management Support

    **12.1.1.1 Multiprogram** - The functions described below support
    the mission management and/or project management of payload
    activities assigned to JSC by NASA Headquarters user code
    organizations. This includes dedicated Space Shuttle flights,
    partial cargo elements, middecks, space station mission build and
    utilization flights, and the JSC Project Office.

    **12.1.1.1.1 Payload Mission Management** - The following are
    representative tasks the contractor shall perform:

    12.1.1.1.1.1 Direct and manage all payload activities for a mission
    or flight increment. Develop mission requirements from
    science/experiment requirements; manage and develop payload
    hardware/software specifications and subsequent translation into
    mission planning, operations, and training; establish
    experiment/payload compatibilities with the flight vehicle; and
    establish certification and safety for flight missions and
    development of the space station documentation in support of flight
    assignments.

    12.1.1.1.1.2 Develop schedules and cost performance data; manage
    payload resource allocation; and provide configuration management.

    12.1.1.1.1.3 Provide mission/payload requirements definition and
    mission design and development.

    12.1.1.1.1.4 Provide research, development, assessment, and
    definition of payload/experiment configurations as potential
    candidates for flight on the Space Shuttle and space station.

    12.1.1.1.1.5 Support NASA payload operations activities preflight,
    inflight and postflight; define, coordinate, schedule, plan, and
    support the implementation of mission-level payload crew and ground
    sport personnel training activities; perform those activities
    required to prepare and support the Payload Operations Contractor
    for SS and the Integrated Space Operations Center for the space
    station; coordinate the development and/or provide the required
    payload flight data file elements for the mission; coordinate,
    schedule, and support preflight and postflight data acquisition and
    dissemination; and support real-time payload operations management
    during the mission or fight increment.

    12.1.1.1.1.6 Support development of information systems related to
    payload development, integration operations, and mission management.
    Plan the use of computer systems hardware, software, input/output
    forms, formats and procedures to enhance project planning, control
    and status visibility, and electronic communications; and develop
    program control tools.

    12.1.1.1.1.7 Provide carrier/vehicle-to-payload interface and
    compatibility analysis and analytical integration support for
    avionics, electrical, thermal/environmental, and structural
    analysis.

    12.1.1.1.1.8 Provide payload integration, ground and flight
    operations requirements definition, integration hardware
    development, and launch site integration support.

    12.1.1.1.1.9 Provide flight operations support which includes
    payload crew training, real-time payload operations support, and
    preflight and data acquisition and dissemination.

    12.1.1.1.1.10 Perform payload integration functions that include
    development of requirements, performance of acceptance/certification
    testing, and development of documentation required for payload
    verification/acceptance with SS/space station (Interface Control
    Documents, Payload Integration Plans (PIP), PIP Annex); provide
    technical expertise in the areas of command and measurements, crew
    compartment payload accommodations, training, mission operations,
    Orbiter testing, ground integration, payload bay electrical and
    mechanical interfaces, and flight planning; provide support at the
    STS requirements review associated with the PIP and PIP annexes
    process; provide representation during ground processing of the
    payload; provide logistic control of assigned flight hardware; and
    provide support during prelaunch and postlanding activities.

    12.1.1.1.1.11 Provide support to experiment developers and mission
    managers for both the payload safety process and the GFE safety
    process, including ground safety process. Prepare safety analysis
    reports and payload hazard reports, analyze safety hazards, safety
    controls, and verification methods. Support all safety reviews,
    track safety actions; and review analyses, reports, and test data
    generated by experiment and payload development.

    **12.1.1.1.2 Experiment/Payload Development** - This function
    supports concept development, program planning and management,
    design, manufacture, and qualification of flight experiments to
    support the SS/space station; space sciences, space technology, and
    commercial programs. Typical experiment developments are science
    experiments, space materials processing, camera systems, cryogenics
    systems, radar systems, deployable experiments, robotics, and
    satellite servicing. Typical payload development areas are payload
    carrier selection, cabling, mechanical design, experiment thermal
    control, payload power control and distribution, and payload
    analyses. The following are representative tasks the contractor
    shall perform:

    12.1.1.1.2.1 Provide electrical, electronic, mechanical, and
    software designs required to develop experiments and payloads and
    their support equipment; fabricate prototype systems; produce test
    articles; manufacture and/or procure flight equipment; and furnish
    bonded storage facilities.

    12.1.1.1.2.2 Automate design, documentation, and procurement with
    tools such as CAD and electronic design development systems.

    12.1.1.1.2.3 Conduct feasibility studies and engineering assessments
    concerning the specific experiment/payload development projects.
    This effort shall include the areas of Orbiter and space station
    accommodations capabilities, payload carrier capabilities,
    compatibility of proposed payload and related support components,
    ground integration and test requirements, and schedules and
    resources requirements.

    12.1.1.1.2.4 Support project reviews and meetings, including design
    and safety reviews; develop presentation materials and make special
    presentations to NASA management; develop the data requirements; and
    produce the project/experiment and payload supporting documentation,
    such as design review data packages operating procedures, ICDs,
    failure reports, and PRDs.

    12.1.1.1.2.5 Develop certification plans to demonstrate the
    experiment payloads meet project performance and environmental
    requirements. The certification plans shall include recommended
    environmental tests both at the system and subsystem levels,
    mathematical analyses, simulations and schedules. Develop any
    special test fixtures or equipment required for the qualification
    tests and supply with the equipment for test. Develop procedures for
    all certification testing. Conduct those analyses required to
    develop and certify the experiment or payload for flight including
    mechanical loads, both static and dynamic, fracture, stress,
    thermal, EMI/EMG, and any other special analysis to ensure flight
    safety.

    12.1.1.1.2.6 Support the development of program schedules, cost
    performance data, schedule performance, and project forecasts to
    evaluate the overall status of each project using automated tools to
    the maximum extent practical.

    12.1.1.1.2.7 Support each experiment/payload through its useful
    life; maintain hardware, software, and project documentation;
    support premission, mission, and postmission operations; investigate
    anomalies and resolve problems; conduct special studies and analyses
    to support the project requirements; and support these activities at
    other locations including any special training and clearance
    requirements.

    12.1.1.1.2.8 Provide support in the preparation and review of all
    levels of interface documents including experiment to payload,
    payload to payload carrier, and cargo element to Shuttle Orbiter
    interfaces. Provide technical review and analyses to support
    resource allocation and interface compatibility.

    **12.1.1.1.3 Experiment Project Management** - This function
    includes managing experiment as hardware such as IMAX, OEX, payload
    integration hardware and space station Small and Rapid Response
    (SRR), and other flight projects. The responsibilities include
    project support, system engineering and support of the various
    experiments, instrumentation configuration and SRR, along with data
    recording, processing, and analyses. The following are
    representative tasks the contractor shall perform:

    12.1.1.1.3.1 Provide project support including the preparation of
    reports; preparation of presentation documentation for project
    briefings; documentation and coordination of activities for change
    control panels, weekly conferences program reviews, configuration
    control board meetings, Preliminary Design Review (PDR), Critical
    Design Review (CDR), and integration reviews; preparation and
    maintenance of management plans, project procedures, and experiment
    integration plans and procedures; coordination of activities with
    other NASA Centers, maintenance of data files on all projects; and
    providing support to the Project Manager in development of
    documentation, engineering analyses, and project supporting
    activity.

    12.1.1.1.3.2 Provide systems engineering support to Space Shuttle
    experiment systems such as the IMAX, OEX, OASIS, SRR, space station
    attached payloads projects, and Space Shuttle including technical
    coordination, systems analysis, calibration, modifications and
    performance verification; failure analysis, anomaly investigation,
    and system certification; experiment technical documentation,
    proposal evaluation and assessments; design and development of
    integration hardware; maintenance, calibration and repair of
    hardware; project management controls, such as schedules, and cost
    and schedules performance; design, develop and manufacture unique
    experiment equipment; management and coordination of experiment
    integration and test activities; drafting and procurement support;
    preparation of software routines to support the GSE; and maintain,
    repair, calibrate, modify, troubleshoot, and analyze performance of
    the GSE.

    \*\*\*From Schedule A, 9.1.1.2, NIO:

    12.1.1.2 Shuttle - Unique

    **12.1.1.2.1 Commercial Middeck Augmentation Module (CMAM)
    Engineering Support Services** - The following are representative
    tasks the contractor shall perform:

    12.1.1.2.1.1 Analyze operations to safely and prudently reduce the
    cost and complexity of human space flight support technologies and
    opinions involving CMAM.

    12.1.1.2.1.2 Analyze and evaluate CMAM manifest and experiment
    proposals to afford CMAM users a fair and reasonable opportunity to
    achieve their experiment operations objectives.

    12.1.1.2.1.3 Establish and maintain schedules of CMAM project
    activities and plans.

    12.1.1.2.1.4 Review and assess Data Requirements Documentation
    provided by CMAM contractors.

    12.1.1.2.1.5 Coordinate utilization of resources for both CMAM users
    and the NASA.

    12.1.1.2.1.6 Provide support to formal reviews including CDRs,
    preparation of Shuttle Program Safety review packages, and
    post-mission technical performance assessments.

    **12.1.1.3 Space Station - Unique** - The following are
    representative tasks the contractor shall perform:

    12.1.1.3.1 Evaluate experiment design, payload integration, and
    operational requirements; assess experiment compatibility-with the
    space station accommodations, capabilities, and constraints; make
    trade studies and recommend alternatives and best combinations of
    payload experiments; and prepare initial mission accommodation
    assessment and space station increment assessment reports for
    presentation at design reviews.

    12.1.1.3.2 Support mission management and space station science
    utilization management activities for assigned payloads from project
    inception through payload design, development, and integration;
    mission planning implementation; and flight operations.

    2.1.1.4 Program/Project Control

    \*\*\*From Schedule B, Part 1, 2.2.3 Schedule Mgt. edited to include
    Schedule & Tracking tasks. Combined with (old) Schedule B 2.1, para.
    3:

    **12.1.1.4.1 Schedule Management** - The contractor shall develop
    and maintain a project status tracking and forecasting system which
    shall include but not necessarily be limited to:

-   Review, analysis, and preparation of project-level interactive
    master schedules to assure timeliness of support to the project,
    identifying interface requirements, milestones, man-hour
    limitations, potential problem areas, resource conflicts, etc.

-   Review overall impact of schedule changes

-   Standardization and rapid dissemination of schedule information

-   Routine review and assessment of individual task schedules for
    compliance with master schedule milestones and to assess the impact
    of problems with specific recommendations to correct or minimize
    these problems

-   Rapid update capabilities

-   Accurate visibility to appropriate subtask element

    \*\*\*From Schedule B, Part 2, 2.1.3, Schedule Mgt.:

    **12.1.1.4.1.1 Master Integrated Payload Schedule** - The contractor
    shall develop and maintain a Master Integrated Payload schedule that
    provides the mission manager insight into the progress of mission
    development activities. The schedule shall depict mission milestones
    and shall include, as a minimum: (1) NASA milestones requiring
    support inputs from mission management; (2) mission payload reviews
    required to support NASA reviews and; (3) other activities and
    documentation required to effectively manage a payload mission.

    \*\*\*From Schedule B, Part 1, 2.1 Projects Planning & Requirements,
    Paragraph 3, edited to include Scheduling and Tracking only:

    **12.1.1.4.1.2 Human Life Sciences Project Management Plan** - The
    contractor shall write and maintain a Human Life Sciences Project
    Management Plan (HLSPMP). This document shall describe the
    contractors approach for support of HLS in the scheduling and
    tracking of life sciences payloads listed in 3.1.

    \*\*\*From Schedule B, Part 1, 2.2.4 Project Control System
    Development & Analysis; last 2 sentences \[combine with (old)
    Sch. B, Part 1, 2.3.1\]:

    The contractor shall recommend system improvements based on
    experience gained, improvements in technology, or other factors.

    The contractor shall develop, publish, and distribute monthly
    Project Management Report.

    In contract progress reviews, the contractor shall report on
    progress since the last review, program status, ongoing and planned
    activities, milestone schedules, and technical cost status relative
    to plan. The contractor shall identify problems and suggest
    resolutions. Scientific, engineering, technical, and management
    activities shall be presented in the format defined in task orders
    or other implementing.

    \*\*\*From Schedule B, Part 1, 2.2.6

    The contractor shall perform advanced planning, including the
    optimization of multi-project scheduling and the assessment of the
    feasibility of future projects. Advanced planning shall include the
    evaluation of schedules of HLS activities at other locations, such
    as at the Kennedy Space Center (KSC) or Marshall Space Flight Center
    (MSFC), to optimize HLS capabilities. Advanced planning shall also
    investigate methods for improvement in and/or automation of such
    functions as documentation, configuration control, inventory
    management, technologies to allow investigators to access test and
    flight experiment data from remote sites, and project operations.
    Advanced planning shall propose and make recommendations for future
    projects and methods of implementation.

    12.1.1.4.2 Performance Management

    \*\*\*From Schedule B, Part 2, 2.3 Major Prog. Review Supt/Coord:

    **12.1.1.4.2.1 Major Program Review Support/Coordination** - The
    contractor shall be responsible for participating in the planning,
    organizing, and preparation of data packages for the major program
    reviews and milestones as required. Examples of the major program
    reviews include the Preliminary Requirements Review, PDR, FSR and
    GSRs, CDR, Spacelab Integration Review, Cargo Integration Review,
    Flight Operations Review, and Payload Flight Readiness Review. The
    contractor shall evaluate proposed changes to baselined mission
    requirements and recommend approval or disapproval. Additionally,
    the contractor shall establish and maintain a RID system, where
    applicable, to track inputs, responses, and disposition of
    discrepancies identified as a result of these reviews and/or
    evaluation activities.

    \*\*\*From Schedule B, Part 1, 2.2 Project Control, paragraph 3:

    **12.1.1.4.2.2 Project Reviews** - In contract progress reviews, the
    contractor shall report on progress since the last review, program
    status, ongoing and planned activities, milestone schedules, and
    technical cost status relative to plan. The contractor shall
    identify problems and suggest resolutions. Scientific, engineering,
    technical, and management activities shall be presented in the
    format defined in task orders or other implementing.

    \*\*\*From Schedule B, Part 1, 2.2.4 Project Control System
    Development & Analysis; last 2 sentences \[combined with (old) Sch.
    B, Part 1, 2.3.1\]:

    The contractor shall recommend system improvements based on
    experience gained, improvements in technology, or other factors.

    The contractor shall develop, publish, and distribute monthly
    Project Management Report.

    \*\*\*From Schedule B, Part 1, 2.2.1 Performance Mgt. & Admin.;
    sentences 3,4,5 to NEW SOW Part I, Section 2.

    **12.1.1.4.2.3 Task Order Reviews** - The contractor shall provide a
    monthly report for individual task orders to each NASA task order
    manager. This report shall identify all problems and recommend
    solutions. Effective management is required to assure that all
    program requirements are met on time and within budget.

    \*\*\*From Schedule B, Part 2, 2.1.2, Configuration Mgt.:

    12.1.1.4.3 Configuration Management

    \*\*\*From Schedule B, Part 1, 2.3.1 Config. Mgt. & Control:

    **12.1.1.4.3.1 HLSCCB Configuration Management and Control** -
    Configuration management shall be directed by the HLS Configuration
    Control Board (CCB). The contractor shall maintain the HLS
    configuration management system and shall maintain all configuration
    control data.

    a\. The contractor shall prepare, coordinate, and maintain the HLS
    configuration management plan. The contractor shall develop and
    modify operating procedures to improve the configuration management
    system as required.

    b\. The contractor shall maintain HLS baseline documentation
    including, but not limited to, the Johnson Space Center (JSC)
    payload project mission specific manifest.

    c\. The contractor shall prepare agendas for the CCB. The contractor
    shall record configuration control board directives (CCBDs) and
    shall collect approval signatures for CCB actions.

    d\. The contractor shall be responsible for the coordination of
    change requests (CRs) from HLS project management and technical
    monitors (TMs), other NASA Centers, and inter-Center panels. The
    contractor shall be responsible for the preparation of requests for
    engineering change proposals as required. The contractor shall
    review change proposals for completeness, requested approval dates,
    and internal Center effect. The contractor shall distribute change
    proposals to affected offices and establish schedule dates for
    review inputs. The contractor shall be responsible for maintaining
    the status of change proposals after distribution and prepare CCBD
    transmittal letters for signatures.

    e\. The contractor shall be responsible for maintaining a change
    file to include copies of CCB changes, together with revisions,
    CCBDs, review comments, and synopses. The contractor shall be
    responsible for the preparation and maintenance of change proposal
    logs that indicate the status and history of changes from receipt
    through disposition and contractor notification.

    f\. The contractor shall be responsible for furnishing configuration
    information to HLS in support of design and program reviews. The
    contractor shall be responsible for managerially and technically
    participating in the configuration management aspect of these design
    and program reviews.

    \*\*\*From Schedule B, Part 1, 2.2.6

    **12.1.1.4.3.2 Advanced Planning** - The contractor shall perform
    advanced planning, including the optimization of multi-project
    scheduling and the assessment of the feasibility of future projects.
    Advanced planning shall include the evaluation of schedules of HLS
    activities at other locations, such as at the Kennedy Space Center
    (KSC) or Marshall Space Flight Center (MSFC), to optimize HLS
    capabilities. Advanced planning shall also investigate methods for
    improvement in and/or automation of such functions as documentation,
    configuration control, inventory management, technologies to allow
    investigators to access test and flight experiment data from remote
    sites, and project operations. Advanced planning shall propose and
    make recommendations for future projects and methods of
    implementation.

    \*\*\*From Schedule B, Part 2, 2.1.2

    **12.1.1.4.3.3 Mission Management** - The contractor shall support
    the operations of the JSC MMO CCB and process in accordance with JSC
    07700, Volume IV, "Configuration Management Requirements," and JSC
    17844 (latest revision), "Mission Management Office Configuration
    Management Plan ." This configuration management process shall be
    applicable to engineering drawings, generic mission documents,
    schedules, mission design data, and software designated by NASA.
    Specific contractor duties shall include, but are not limited to:

-   Change request preparation

-   Engineer change proposal processing

-   Configuration Control Board secretary

-   Develop and publish minutes

-   Develop/maintain configuration management computerized tracking log

-   Maintain configuration control change files

-   Process drawings for release and distribution and maintain drawing
    files

    \*\*\*From Schedule B, Part 2, 2.2, Programmatic Documentation Dev.:

    12.1.1.4.4 Programmatic Documentation Development

    **12.1.1.4.4.1 Mission Management Documentation** - The contractor
    shall support the MMO in defining mission requirements and
    constraints to be included in interface agreements such as the PIP
    and its annexes, Payload Integration Agreements and its annexes,
    ICD's required by the SSP and space station. Additionally, the
    contractor shall coordinate and support the development of
    requirements and interface agreement documents between the MMO, SSP,
    and experiments developers as required.

    \*\*\*From Schedule B, Part 1, 2.3.6

    **12.1.1.4.4.2 Project Documentation, Management Information, and
    Presentations** - The data requirements list and data requirements
    description of this contract include only a small part of the total
    documentation requirements. A more complete description of
    documentation and contents will be found in documentation as defined
    by implementing task orders or other enabling documentation and in
    other sections of this SOW.

    The contractor shall make timely responses to requests for
    briefings, presentations, and status reviews.

    The contractor shall prepare presentation material and shall
    maintain a simple and accessible system of filing this material.

    \*\*\*From Schedule B, Part 1, 2.3.7 STI Center:

    **12.1.1.4.4.3 Scientific and Technical Information (STI) Center** -
    The existing STI Center is a repository of all official scientific,
    technical, graphics, and management information associated with the
    HLS and the Life sciences Flight Experiments Program (LSFEP).

    The scientific information consists of experiment proposals and
    evaluations, ground-based studies, experiment results, and
    investigator reports. Technical information consists of GSE, flight
    experiment, and other hardware documentation; software
    documentation; hardware and software RDs; acceptance and testing
    procedures and plans; design specifications, and related engineering
    drawings and information concerning experiments. Graphics
    information includes films, videotapes, photographs, slides, view
    graphs, and original artwork for presentations or document
    illustration. Management information includes management plans,
    configuration control documentation and records, project review
    materials, and other non-technical data.

    The contractor shall develop a plan for, maintain, and operate an
    STI Center.

    **12.1.1.4.4.3.1 Technical Information** - The STI Center shall
    maintain all program documentation, technical documents and
    information, drawings, specifications configuration management
    files, etc. The STI Center shall maintain an aperture card file of
    engineering drawings, current and historical, for HLS experiments
    and hardware, data systems, GSE, payload development, facilities,
    and other drawings relative to the LSFEP. The STI Center shall
    maintain official experiment, scientific, graphics, management, and
    other information as directed by HLS management.

    The STI Center shall maintain current applicable military and NASA
    specifications and standards on file or through subscription to a
    central data base. Vendor catalog information applicable to the HLS
    mission and the LSFEP shall also be maintained.

    The contractor shall maintain and manage a system for cataloging,
    maintaining, processing, integrating, controlling, and distributing
    information and materials related to the LSFEP and stored in the STI
    Center. The contractor shall maintain an automated index of
    information and materials stored in the STI Center and shall publish
    it as required.

    **12.1.1.4.4.4 Special Projects** - The contractor shall develop and
    maintain all documents related to the HLS mission and the LSFEP as
    defined in section 14.1.1.4.5 and shall prepare, publish, and
    distribute information booklets on HLS missions, experiments,
    hardware, and facilities; shall prepare graphics displays as
    required; shall coordinate the preparation, review, approval,
    revision, and distribution of the HLS Standard Operating Procedures
    (SOPs) Manual (HLS-1 0003).

    \*\*\*From Schedule B, Part 1, 2.3.8 Reqt. Mgt.; para. 1:

    **12.1.1.4.4.5 Requirements Management** - The contractor shall
    develop and implement a plan for assuring the compliance of HLS
    flight equipment to Level I through Level III requirements including
    safety requirements and design standards. This shall include the
    necessary expertise to assess these requirements against flight
    equipment design requirements and design reviews for HLS flight
    equipment, whether being delivered by the contractor, experiment
    principal investigator (PI), or other NASA contractor.

    \*\*\*From Schedule B, Part 1, 2.3.2 Information Management:

    **12.1.1.4.5 Information Management** - The contractor shall develop
    an information management plan (IMP) which will identify the
    documentation requirements that define, manage, and support life
    sciences payloads. The IMP shall include a summary which identifies
    HLS documentation requirements and their relationship to each other
    and to the program.

    The contractor shall review existing and new JSC and NASA management
    instructions as well as flight and ground support equipment (GSE)
    hardware design requirements. The contractor shall advise HLS and
    contractor engineering and management personnel on these
    requirements.

    The contractor shall establish, operate, and maintain a
    documentation control system which identifies, controls, prepares,
    reproduces, stores, and distributes HLS documents. The contractor
    shall be responsible for preparing, reproducing, storing,
    cataloging, and distributing all HLS experiment related scientific,
    engineering; technical, management, program administration, and
    other documentation which may be assigned to the contractor.
    Documentation responsibilities shall include providing technical
    writing and editing capability.

    The contractor shall prepare, maintain, and submit
    management/project review materials; identify, track, and control
    action items; and establish, operate, and maintain a program
    information file.

    \*\*\*From Schedule B, Part 1, 2.3.3 Logistics Management:

    **12.1.1.4.6 Logistics Management -** As part of its HLSPMP, the
    contractor shall prepare a logistics plan that indicates how it will
    develop and use a logistics system in support of HLS activities.

    The contractor shall implement the logistics plan in accordance with
    NASA standards and other applicable documentation.

    The contractor shall develop, operate, and maintain the HLS
    logistics system. The contractor's logistics plan shall describe its
    logistics support to all on-site/off-site and remote locations,
    (e.g., launch/landing sites and crew training sites). The plan shall
    define logistics procedures for HLS furnished equipment and shall
    provide guidelines for preparing and shipping hardware to and from
    the launch site or other locations as required.

    The contractor shall maintain records for equipment items shipped to
    other geographic locations.

    The contractor shall be responsible for operating and maintaining a
    logistics system including a material control station, a receiving
    and shipping area, and methods for control of all capital and
    sensitive equipment.

    The contractor shall record all receipts and issuances of stock and
    shall operate and maintain a material control station that maintains
    the predetermined minimum/maximum stores as defined by the
    government.

    The contractor shall maintain all equipment/instrumentation
    calibration records and shall coordinate calibration maintenance
    with the JSC metrology laboratory

    The contractor shall develop, manage, and operate an inventory
    control system for HLS equipment in accordance with approved
    standards for Government property. The contractor shall be
    responsible for serving as property custodian of Government property
    assigned to the contractor for use in support of the contract and
    shall follow established procedures for controlling, managing, and
    accounting for Government property.

    12.1.2 Engineering, Scientific, and Analytical Tools

    \*\*\*From Schedule B, Part 2, 3.0 Mission Feasibility & Design:

    **12.1.2.1 Mission Feasibility and Design -** The contractor is
    responsible for conducting the tasks and developing the necessary
    analytical tools required to assure the successful integration of
    life sciences and other assigned experiment payloads into a
    human-tended or non-human-tended, pressurized module. The
    contractor's activities shall support mission management in
    developing the final flight configuration of the payload.

    **12.1.2.2 Computer Program Development and Maintenance Support** -
    The following are representative tasks the contractor shall perform:

    12.1.2.2.1 Develop program control tools.

    12.1.2.2.2 Develop and/or install, maintain and document software
    applications for data processing and evaluation, simulation data
    reduction and analysis, automation support applications, and
    computer graphics. This effort shall include development and
    maintenance of a data base management system to support all data
    processing and dissemination requirements and implementing computer
    security applications.

    12.1.2.2.3 Provide support in the assessment of existing, enhanced
    and new commercially available computer programs which may enhance
    the design and analysis capabilities including trade-off studies of
    potential improvements in capabilities, compatibility with existing
    programs and data bases.

    \*\*\*From Schedule B, Part 2, 2.1.4, Info Mgt. System:

    **12.1.2.3 Information Management System** - The contractor is
    responsible for maintaining an information management system that
    assures the timely definition, preparation, maintenance and
    distribution of program documentation, reports, data, and material.

    The contractors shall establish and maintain the capability to
    provide letter-quality printed documents to support all program
    reviews, reports, presentations, documentation development, and
    other correspondence requirements.

    The contractor shall maintain a library for information archiving
    and retrieval. This library shall also contain video and
    photographic files and engineering drawings, schematics, and
    diagrams. This facility shall be used by the contractor for
    acquiring and controlling data from Government agencies,
    subcontractors, and vendors as appropriate.

    The contractor shall identify, track, log, status and control action
    items, incoming and outgoing correspondence and maintain a program
    information file for all program activities and operations.

    The contractor shall provide data, technical expertise, and support
    for development of brochures, videos for requested Public Affairs
    Office (PAO) activities, and NASA educational services. The
    contractor shall be responsible for the implementation of
    educational information products with the NASA PAO and identified
    education committees according to NASA publication and distribution
    standards as specified in the NASA Management Instructions. The
    contractor shall be responsible for the implementation of the
    educational and public information plan including, but not limited
    to, the production of photographic, TV, video, and written products.

    \*\*\*From Schedule B, Part 1, 5.0 Data Systems Development and
    Operation:

    **12.1.2.4 Data Systems Development and Operations** - The
    contractor shall be responsible for experiment data requirements
    definition and for the design, acquisition, archival, development,
    implementation, programming, maintenance, and operation of data
    systems used in support of the LSFEP.

    \*\*\*From Schedule B, Part 1, 5.1:

    **12.1.2.4.1 Experiments Data Requirements Definition and
    Determination of Methods Meeting Experiment Requirements** - The
    contractor shall be responsible for identifying and documenting as a
    part of the ED all requirements associated with data acquisition,
    automated experiment control, real-time data analysis, on-board data
    display, real-time and non-real-time ground-based data processing
    and display, off-line data processing, data storage, archival,
    retrieval, and data distribution to PIs. Such requirements
    identification and documentation shall include on-board data systems
    and interfaces, ground, Payload Operations Control Center (POCC),
    and flight data processing, non-real-time data support, and other
    data storage, archival, and retrieval functions as may be related to
    life sciences experiments on each mission.

    The contractor will be the functional contact with investigators
    with regard to experiment data requirements; such contact will
    necessitate extensive coordination with experiment TMs, support
    scientists, and the data groups within the HLS and the contractor
    organization.

    The contractor shall be responsible for exploring alternative
    methods of meeting flight, ground based, real-time, and
    non-real-time data requirements of all experiments. As a general
    guideline, the contractor shall use a total systems approach in
    meeting data requirements. This approach will address data
    requirements from a total program viewpoint so as to develop methods
    of meeting the total program data requirements as a whole and not as
    a large collection of isolated or unrelated requirements. The
    contractor shall consider, factors such as equipment costs, labor
    costs, schedule, availability of personnel and equipment, task
    complexity, and other factors appropriate or applicable for each
    situation in making recommendations for methods of meeting
    experiment requirements. The contractor shall document and justify
    these recommendations. The recommended or selected approach for
    meeting requirements shall be a part of the ED and shall be
    coordinated with the PE, EM, and PI, and ESS.

    \*\*\*From Schedule B, Part 1, 5.2:

    **12.1.2.4.2 Ground Data Systems Development** - Consistent with
    approved methods of meeting documented experiment data requirements,
    the contractor shall be responsible for designing, developing,
    acquiring, and implementing real-time data hardware systems and
    software to perform the following functions.

    \*\*\*From Schedule B, Part 1, 5.2.1:

    12.1.2.4.2.1 Data Systems Hardware

    **12.1.2.4.2.1.1 Real-Time Data Systems Hardware** - The contractor
    shall be responsible for designing, developing, implementing,
    acquiring, and documenting data system hardware to provide data
    support to life sciences activities during experiment development,
    check out, testing, mission simulations, and missions. Such hardware
    shall be capable of operating at JSC or at remote sites where pre-
    and/or postflight experiment operations may occur. Hardware shall be
    able to acquire, store, retrieve, analyze, and display real-time
    data in a manner and in locations (e.g., the Science Monitoring Area
    \[SMA\] and POCC) necessary to satisfy approved experiment data
    requirements. Hardware systems shall be designed with flexibility to
    minimize the problems/expense associated with supporting future
    requirements and missions. This hardware consists of computer
    systems, simulate remote acquisition units, high rate demultiplexer
    interface devices, simulated high rate demultiplexer devices,
    simulated user time clock devices, checkout boxes for simulating
    analog and/or digital signals, and other GSE which may or may not be
    emulations of on-board mission data equipment and systems.

    The contractor shall be responsible for configuring and/or
    reconfiguring HLS hardware systems as specified in Section 5.3.1.

    **12.1.2.4.2.1.2 Non-Real-Time Data Systems Hardware** - The
    contractor shall be responsible for designing, developing,
    implementing, acquiring, and documenting computer systems hardware
    necessary to satisfy approved non-real-time life sciences flight
    data requirements. Such systems shall possess the ability to
    retrieve, analyze, display, format or reformat, and manipulate the
    data required to produce PI data products, create and maintain
    experiment related data bases, and perform other data handling
    functions specified in approved requirements.

    **12.1.2.4.2.1.3 Computer Network Hardware** - The contractor shall
    design, acquire, develop, implement, and document computer network
    hardware necessary to meet approved requirements for supporting
    inter-computer exchange of data, software, and information for the
    HLS. All network hardware shall be compatible with other required
    HLS local and Center networks.

    \*\*\*From Schedule B, Part 1, 5.2.2 & 5.2.2.1:

    12.1.2.4.2.2 Management Computational Support

    **12.1.2.4.2.2.1 Management Computational Support Requirements
    Definition** - The contractor shall be responsible for identifying
    and documenting management computational support requirements for
    the HLS. Such requirements shall include, but not be limited to the
    MS, data base development and maintenance, word processing, document
    and report preparation, accounting, budget analysis and preparation,
    property, accounting, and other non-experiment related computational
    functions.

    \*\*\*From Schedule B, Part 1, 5.2.2.2:

    **12.1.2.4.2.2.2 Management Computational Support Data Systems
    Hardware** - The contractor shall be responsible for investigating
    alternative methods of meeting approved requirements considering
    such factors as, but not limited to, cost, training needs, future
    growth potential, schedule, and compatibility with existing systems
    and shall document the reasons for choosing or recommending
    a-particular alternative. The contractor shall be responsible for
    designing, developing, implementing, acquiring, and documenting data
    system hardware which will satisfy approved management computational
    requirements.

    \*\*\*From Schedule B, Part 1, 5.2.3:

    12.1.2.4.2.3 Ground Data Systems Software

    **12.1.2.4.2.3.1 Real-Time Experiment Systems Software** - The
    contractor shall be responsible for designing, developing,
    implementing, acquiring, and documenting data system' software to
    provide data support to life sciences experiments during experiment
    development, check out, testing, mission simulations, and missions.
    Such software shall operate at JSC or at remote sites where pre-
    and/or; postflight experiment operations occur. Such software shall
    acquire, store, retrieve, analyze, and display experiment data in a
    manner and in locations (e.g., the SMA and POCC) necessary to
    satisfy approved experiment data requirements. Software systems
    shall be designed with flexibility to minimize the problems and
    expense associated with supporting future requirements and missions.

    The contractor shall be responsible for configuring and/or
    reconfiguring HLS software systems as specified in Section
    12.2.3.15.1.

    **12.1.2.4.2.3.2 Non-Real-Time Experiment Systems Software** - The
    contractor shall be responsible for designing, developing,
    implementing, acquiring, and documenting computer systems software
    necessary to satisfy approved non-real-time life sciences flight
    experiments data requirements. These systems shall possess the
    ability to retrieve, analyze, display, format or reformat, and
    manipulate the data required to produce PI data products and perform
    other data handling functions as specified in EDs, job orders, or
    other documents and directives.

    **12.1.2.4.2.3.3 Management Systems Software** - The contractor
    shall be responsible for designing, developing, implementing,
    acquiring, and documenting management support software necessary to
    meet computational support requirements. These requirements shall
    include, but not be limited to, the MIS, non-real-time experiment
    data base development and maintenance, word processing, document and
    report preparation, accounting, budget analysis and preparation,
    property accounting, and other non-experiment related computational
    support.

    **12.1.2.4.2.3.4 Computer Network Software** - The contractor shall
    design, acquire, develop, implement, and document computer network
    software necessary to meet approved requirements for supporting
    inter-computer exchange of data, software, and information for the
    HLS. Network software shall be compatible with other required HLS
    local and Center networks.

    **12.1.2.4.2.3.5 Computer Network Management and Security** - The
    contractor shall be responsible for managing any networks for which
    HLS is responsible. They shall provide personnel who are qualified
    to maintain the network software and hardware. The contractor shall
    work closely with network CCBs, agencies, and working groups and
    shall comply with network security and other directives from these
    entities to assure that HLS networks will function properly with any
    networks to which they may be connected and that network security is
    maintained in accordance with the JSC Automated Information System
    Security Plan, JSC-23668.

    **12.1.2.4.2.3.6 Data Bases** - The contractor shall be responsible
    for designing, developing, implementing, acquiring, and documenting
    data bases required to support approved data requirements. The
    contractor shall be responsible for developing a long-range plan for
    the development and maintenance of data bases to assure that only
    the necessary data bases are developed and retained in accordance
    with approved requirements. These data bases include three major
    categories: real-time experiment data bases, non-real- time
    experiment data bases, and management data bases. Real-time data
    bases include functions such as supporting real-time data
    acquisition, archival, analysis, and display software. Non-real-time
    experiment data bases include functions such as experiment
    requirements, design criteria, flight parameters, hardware lists,
    experiment resources, and other data not directly related to the
    acquisition, archival, analysis, or display of experiment data.
    Management data bases include functions such as property records,
    logistics data bases, flight and GSE records, and maintenance data
    bases.

    **12.1.2.4.2.3.7 Data Storage and Retrieval** - The programs managed
    by HLS will result in the generation of large quantities of
    experiment and experiment-related data, both scientific and
    management. In order to assure adequate control over the retention
    of these data; the contractor shall be responsible for developing
    and documenting data storage, archival, and retrieval requirements
    for each experiment and each mission. The contractor shall be
    responsible for developing a long-range plan to support the overall
    scientific and management data storage, archival and retrieval
    requirements. The contractor shall design, develop, and implement
    techniques, methods, processes, and procedures for permanently
    storing data collected from life sciences experiments, including
    preflight, flight, and postflight. These techniques, methods,
    processes, and procedures will make use of any viable existing
    standards produced by NASA, other Government agencies, or industry
    which may be of use in or applicable to the HLS. The contractor
    shall consult with Government agencies, the National Institute for
    Standards and Technology, the National Space Science Data Center,
    other NASA Centers, industry, and standards organizations in
    formulating methods and techniques for permanently storing life
    sciences data.

    \*\*\*NOTE Schedule B, Part 1, 5.2.4 went to NEW SOW Part B, Core
    Computer Services

    \*\*\*From Schedule B, Part 1, 5.2.5:

    **12.1.2.4.2.4 Maintenance and Operation of Specialized Computer
    Systems and Software** - The contractor shall be responsible for the
    operation, modification, and maintenance of specialized computer
    software systems used in the HLS, such as the Facility Processor
    (FP) which supports the Spacelab mockup. The FP acquires, stores,
    and monitors environmental and electrical distribution parameters
    pertaining to the Spacelab mockup and experiment racks, but not to
    the experiments. Anticipated modifications to this system will
    include updating the active sensor list and updating sensor for each
    experiment on each mission. Operation of the FP will include
    computer system operation during experiment check-out and crew
    training exercises conducted in the Spacelab mockup.

    Other software systems which the contractor shall be required to
    operate, maintain, and update include, but are not limited to, GSE
    diagnostic software, specialized experiment data analysis software,
    specialized test software, experiment simulator software systems,
    the simulated experiment computer software, and other specialized
    GSE software which may be required to support future life sciences
    experiments and missions.

    \*\*\*From Schedule B, Part 1, 5.3:

    12.1.2.4.3 Experiment and Payload Testing, Simulation Mission
    Support, and Training

    **12.1.2.4.3.1 Mission Support Preparation** - The contractor shall
    be responsible for configuration and/or reconfiguring HLS data
    systems hardware, software, and GSE and for developing, acquiring,
    implementing, testing, and validating all hardware, software, and
    GSE required to support experiment and payload testing of any type
    at JSC or remote locations, for supporting mission simulation and
    training exercises, and for providing mission support during
    missions on which life sciences experiments are flown. This activity
    shall include, but not be limited to, experiment and mission
    software development, modification, testing, validation, and
    computer and GSE hardware and software testing and validation.

    **12.1.2.4.3.2 Training** - The contractor shall be responsible for
    providing appropriate training for data systems and other personnel
    on the use of the hardware and/or software with which they will be
    working. This includes, but is not limited to, computer operating
    systems and network hardware and software training, and training of
    users in the operation of the real-time data acquisitions system,
    non-real-time software, and management software used to support
    LSFEP missions and activities.

    \*\*\*From Schedule B, Part 1, 5.4:

    **12.1.2.4.4 Attendance at Technical and Professional
    Conferences** - The contractor shall encourage his personnel to
    publish the results of their work in appropriate professional
    journals and/or conferences except where the work may be proprietary
    or otherwise restricted. Such presentations, talks, and publications
    shall not include any data or information which is sensitive, has
    privacy act implications, or may involve national security.

    \*\*\*From Schedule B, Part 1, 5.5:

    **12.1.2.4.5 Technical Documentation** - The contractor shall be
    responsible for producing documentation which describes how
    software, hardware, technical procedures, and other processes and
    methods used in support of the LSFEP are designed, how they
    function, and how personnel may use these products and items. Such
    documentation shall consist of but not be limited to, RDs, design
    documents, implementation plans, user's guides, general
    documentation for public release, and proposals for new and upgraded
    equipment, methods, and procedures.

    All baselined software used to support a mission or other major
    activity shall be fully documented so that technical details of how
    a mission is to, be or was supported can be understood and used for
    future modification or other purposes such as supporting future
    related missions or analyzing data from previous missions.

    \*\*\*From Schedule B, Part 1, 5.6:

    **12.1.2.4.6 Compliance With Federal Information Processing (FIP)
    Regulations and Policies** - The contractor shall comply with all
    required FIP regulations and policies concerning the acquisition,
    modification, upgrading, and use of FIP resources. This includes,
    but is not limited to, development and maintenance of FIP Resource
    Decision Documents (FRDDs), formerly Automated Data Processing
    Equipment acquisition plans, comprehensive FRDD plans where
    required, performing and documenting computer risk analyses,
    computer risk response/reduction plans, contingency operating plans,
    computer security plans, other FIP documents as may be required by
    appropriate computer security directives, and updating such
    documents as may be required.

    \*\*\*From Schedule B, Part 1, 5.7:

    **12.1.2.4.7 Computer System Upgrading** - The contractor shall be
    responsible for evaluating the effectiveness and ability of all data
    systems hardware and software used in the LSFEP on a periodic basis
    and make any required recommendations for improving the use of such
    systems, possibly upgrading them to meet new or expanded
    requirements, and ways of more effectively and efficiently using
    them. Upon approval of any recommended upgrade, the contractor shall
    be responsible for implementing the approved upgrades.

    \*\*\*From Schedule B, Part 1, 5.8:

    **12.1.2.4.8 Production of Postmission Data Products for Principal
    Investigators** - The contractor shall be responsible for producing
    and supplying to LSFEP PIs the data products specified in their
    respective EDs. Production of PI data products involves retrieving
    the desired data, performing any required analysis, storing the data
    on the proper output medium in the required format, and delivery of
    the products to the PIs in accordance with the time frame specified
    in the mission data RD or contract.

    \*\*\*From Schedule B, Part 1, 6.0:

    **12.1.2.5 Project Science Support** - The contractor shall be
    responsible for the management and implementation of the science
    functions defined below. A NASA project scientist at JSC is
    responsible for the scientific aspects of experiment development.
    This JSC project scientist is responsible for coordinating all
    scientific tasks and activities related to the payload project. The
    contractor will support the project scientist in the areas described
    in the following paragraphs.

    \*\*\*From Schedule B, Part 1, 6.1:

    **12.1.2.5.1 Experiment-Support Scientist Program** - The contractor
    shall be responsible for managing and implementing the ESS program.
    They shall work with and coordinate efforts between the project
    scientist and PEs in order to maintain an orderly progress of
    experiment development and implementation. Each ESS shall be
    assigned specific experiments (depending upon experiment complexity)
    and the ESS must be proficient in the scientific aspects of the
    specific discipline being investigated. The contractor shall be
    responsible for the following areas listed below as they relate to
    each experiment/discipline or payload element.

    **12.1.2.5.1.1 Science Documentation** - The contractor shall be
    responsible for maintaining and assuring the correctness of required
    science documentation. Required documentation includes the (1)
    science portion of the ED and the Integrated Experiments
    Requirements Document (IERD) (or equivalent documentation for
    non-JSC managed missions) and (2) project input to the Mission
    Science Requirements Document (MSRD). The contractor shall, when
    required, assist with the development of appropriate sections of
    experiment SOWs.

    **12.1.2.5.1.2 Data Sharing Plan** - The HLS-managed experiments
    approved for development require considerable data/measurement
    sharing between investigators. It is important that the exchange of
    data between investigators be managed. The contractor shall be
    responsible for the definition of all data/measurements that will be
    shared using information contained in the EDs and through
    communication with experiment investigators. With this information,
    the contractor shall participate in the development and
    implementation of a data sharing plan for each payload.

    **12.1.2.5.1.3 Investigator Working Group (IWG)/Science Working Team
    (SWT) Support** - The contractor shall be responsible for supporting
    the SWT and the IWG meetings. Support for these meetings shall
    include: (1) preparation of required material for the dissemination
    of information to the investigators; (2) provide advice and
    assistance to the PIs; (3) provide personnel to maintain SWT meeting
    minutes and to distribute these meeting minutes according to an
    approved distribution list; (4) provide personnel to assist in
    arranging accommodations, meeting rooms, required equipment and
    transportation; (5) present, when required, appropriate material at
    these meetings; (6) support IWG committee meetings with advice,
    assistance and meeting minutes; and (7) review data packages for
    IWGs and provide comments.

    **12.1.2.5.1.4 Life Sciences Laboratory Equipment Support** - The
    contractor shall be responsible for scientific advice on LSLE items
    and the preparation of required material (e.g., science measurement
    specification). The contractor shall be responsible for providing
    advice and information to the project scientist concerning LSLE
    hardware. The contractor may also be required to plan and implement
    science verification tests of LSLE items.

    **12.1.2.5.1.5 Payload Science Objectives/Definition** - The
    contractor shall be responsible for studies and analyses which will
    support NASA management in establishing long-term payload science
    objectives and definition of payloads for specific missions. The
    approach shall take into account past space flight or ground-based
    research results as well as the pool of selected and available
    experiments.

    **12.1.2.5.1.6 Experiment Solicitation/Selection** - Experiment
    solicitation and selection is an ongoing process during the flight
    program. Although NASA Headquarters has the main responsibility for
    preparing and distributing announcements of opportunity, HLS
    provides engineering, management, and cost assessments of the
    proposals. The contractor shall be responsible for supporting the
    overall activity as required. Such support may include assessments
    of operational feasibility, estimates of experiment inflight
    resource requirements, and estimates of internal HLS experiment
    support requirements.

    **12.1.2.5.1.7 Experiment Procedures Development** - The contractor
    shall be responsible for supporting each experiment development team
    in the development of experiment operating procedures. These
    procedures will be updated and refined as crew training progresses
    and will be formatted as required. This responsibility will also
    include development of procedures for ancillary flight hardware
    required to achieve experiment objectives and, where appropriate,
    malfunction procedures for selected items of experiment hardware.

    **12.1.2.5.1.8 Payload Flight Data File (PFDF)** - As an integral
    part of life science experiment procedures development and
    maintenance, the contractor shall be responsible for preparing
    operating procedures for the mission manager's PFDF format on a
    schedule identified by that office. The PFDF will include procedural
    "cue" cards, check lists, and other documentation required to
    enhance inflight experiment operations and will be flown as an
    integral part of each life sciences payload. The contractor shall be
    responsible for integrating the inputs from each experiment and
    shall provide a system for updating, statusing, and controlling the
    information.

    **12.1.2.5.1.9 Flight Crew Training Scheduling** - The contractor
    shall be responsible for summarizing the requirements for the
    scheduling of all flight-dependent (HLS-managed experiment) training
    for the payload crew. This responsibility will cover both long-term
    and short-term requirements during the execution of a training tour
    and will include an intra-day schedule designed to, optimize crew
    utilization. The JSC payload project training will be implemented in
    accordance with the overall mission management training schedule.
    The contractor shall be responsible for preparing working schedules
    to support the overall training program. As a means of implementing
    and managing this activity, the contractor shall designate a
    training coordinator who will serve as the functional interface
    among HLS, PIs, payload crew, and mission management.

    The contractor shall be responsible for coordinating with the PIs
    the preparation and distribution to the crew of a training syllabus
    for each unique training tour. This syllabus shall address the HLS
    experiment tasks on which the crew will receive training and shall
    sequence the tasks in such a way that the crew time is optimally
    utilized during each session.

    **12.1.2.5.1.10 Human Research Policy and Procedures Committee
    (HRPPC) Requirements** - The contractor shall be responsible for
    coordinating with and collecting from the PIs the experiment
    procedures and background information required by the JSC HRPPC to
    approve the HLS experiment protocols. Coordinated by the contractor,
    these data will be provided by the PIs in the format and on the
    schedule required by the HRPPC for master HRPPC protocols and
    experiment training protocols. The contractor shall be responsible
    for participation in/and attendance at HRPPC meetings, as required,
    to coordinate/support PI requirements and shall document any
    protocol impacts resulting from changes required by the HRPPC.
    Associated with this activity, the contractor shall manage and
    distribute the HRPPC consent forms required. This task will entail
    the coordination of the forms among the crew, the PIs, and the JSC
    Project scientist. The contractor shall be responsible for obtaining
    signatures, distributing the consent forms before each training tour
    on the schedule required by HRPPC, and coordinating/documenting such
    activity with mission management.

    **12.1.2.5.1.11 Crew Activity Planning** - The contractor shall be
    responsible for determining the timeline requirements for the
    HLS-managed experiments and determining/implementing the mission
    specific crew activity planning relative to experiment
    preflight/postflight data collection requirements.

    **12.1.2.5.1.11.1 Experiment Timeline Requirements Definition** -
    The contractor shall be responsible for determining and documenting
    the timeline requirements for each HLS managed experiment. This
    information shall be defined in the EDs. As experiment development
    progresses, these requirements shall be refined by means of
    comprehensive discussions and coordination with the PIs and the
    Mission Management Office (MMO).

    **12.1.2.5.1.11.2 HLS Payload Project Timeline Requirements Document
    Preparation** - Based upon the requirements developed under Section
    6.1.11.1, the contractor shall be responsible for preparing and
    iterating the HLS payload project timeline requirements and document
    those requirements in the HLS payload project IERD. The data shall
    not only address HLS-managed experiment requirements, but also
    factor in the constraints imposed by other experiments, experiment
    task analyses, and medical operations constraints and requirements.
    In addition, this iterative process shall also address the
    constraints finalized by the MMO resulting from optimized work/rest
    cycles, shift operations, and concurrent mission operations.

    The contractor shall be responsible for preparation and presentation
    of materials summarizing HLS payload project timeline requirements
    for each major payload project review (RR, PDR, and CDR).

    **12.1.2.5.1.11.3 Preflight/Postflight Data Collection
    Requirements** - The contractor shall be responsible for
    implementing, scheduling, and coordinating the accomplishment of
    preflight/postflight HLS-managed experiment data collection. The
    requirements for this activity shall be documented in the EDs and
    summarized in the IERD. These requirements shall also be documented
    by the contractor and presented to the JSC HRPPC on the schedule
    established by that committee. Since there will be many conflicting
    demands made on the crew's time/availability immediately
    before/after preflight/postflight, this task will require
    interactive coordination and communication with all PIs to assure
    that their requirements are met. These data shall be documented in
    the HLS Payload Project IERD and summarized in presentation
    materials for each major HLS Payload Project Review.

    **12.1.2.5.1.12 Medical Experiments Data Collection Facility
    (MEDCF)** - The contractor shall be responsible for the operations
    of the MEDCF BDC activities and facilities (preflight and
    postflight) at JSC, KSC, Dryden Flight Research Facility (DFRF), and
    other sites as required by the individual and unique life sciences
    payload and mission requirements. The major portion of this activity
    will occur at JSC in the MEDCF (building 266). Remote site
    activities (e.g., at KSC and DFRF Baseline Data Collection
    Facilities \[BDCF\] Facilities) will vary from mission to mission
    and will consist of subsets of the JSC activities, depending on the
    mission requirements and the specific remote site involved. The JSC
    tasks to be accomplished by the contractor shall include, but not
    necessarily be limited to:

-   Identify and coordinate PI requirements for facilities, equipment,
    and support, including electrical power; requirements, unique
    equipment mounting or spatial considerations, and expendables
    provisioning.

-   Coordinate and schedule facility repair/maintenance/modification
    activities for the JSC MEDCF.

-   Evaluate BDC schedules to determine facility usage patterns and
    conflicts.

-   Identify facility support requirements for experiments/payloads at
    the KSC and DFRF BDCFs, as required.

-   Identify logistics requirements for shipping investigator and
    NASA-supplied equipment to/from the BDC facilities at the various
    centers. This activity will require coordination with both
    contractor and NASA logistics and transportation elements.

-   Coordinate and assist in ground safety and quality inspections and
    walkthroughs of the BDC facilities, laboratories, and equipment
    including the preparation of information (analyses, tests) to
    support these activities.

-   Maintain/operate the U.S. laboratory sled system, including sled
    operations, maintenance, calibration and certification, system
    upgrades, conduct man-rating procedures, provide assistance to
    investigators in interfacing investigator-unique equipment with the
    sled, and prepare procedures, manuals, and handbooks as required.

-   Provide facility support during the conduct of preflight and
    postflight tests for the experiments.

-   Maintain an automated log of instrument and pressure systems
    calibration and certification status.

    12.1.3 Studies and Assessments

    \*\*\*From Schedule B Part 2, 3.1:

    **12.1.3.1 Mission Feasibility and Definition** - The contractor
    shall perform analyses of candidate payload options to establish the
    basic compatibility of proposed payload requirements with the
    assigned pressurized module capability. Proposed locations of
    equipment shall be evaluated and layouts of acceptable
    configurations developed. Timelines shall be generated to assess
    availability and adequacy of resources such as power and energy,
    thermal control, crew work schedules, data/communications, systems
    utilizations, hardware usage conflicts, etc., to meet load needs.
    Assessments of inflight reference mission scenarios and human
    factors analyzes and ground operations requirements shall be
    performed in addition to carrier vehicle provisioning and interface
    requirements definition.

    Proposed payload configurations shall be refined to determine the
    optimum configuration for the payload equipment in the pressurized
    module of the Orbiter, Spacelab, or space station considering the
    capabilities and limitations of the carrier vehicle. The contractor
    shall determine the integrated payload requirements which must be
    accommodated. Areas to be evaluated include: power and energy,
    environmental/thermal, stowage, communications, structural
    compatibility, weight and volume, LSLE, Mission Dependent Equipment,
    and Mission Peculiar Equipment (MPE). The contractor shall conduct
    the overall payload analyses to assure a totally integrated and
    compatible payload. The results of this effort shall serve as a
    starting point for more extensive analysis and planning associated
    with detailed mission design.

    \*\*\*From Schedule B, Part 2, 3.2:

    **12.1.3.2 Detailed Mission Design** - The contractor will be
    responsible for the detailed design of the integrated payload and
    shall prepare layouts, engineering drawings, and parts lists showing
    the placement and interfaces of all payload equipment to be
    accommodated on the mission. The detailed design activity shall
    include requirements for the environmental/thermal configuration,
    the electrical system configuration, the stowage considerations,
    data systems configuration, and the structural/mechanical
    configuration. These configurations must satisfy the total payload
    requirements and be compatible with the pressurized module.
    Additionally, detailed design shall include considerations for
    stowage, interface design criteria, materials, human factors, and
    compliance with safety requirements. Drawings shall be prepared for
    use in payload assembly and installation and shall include sequence
    requirements and critical installation data. The contractor shall
    prepare and provide the pressurized module staging requirements
    using the appropriate documentation methods required by the carrier.
    These design data will constitute a part of the packages to be
    provided for PDR and CDR.

    \*\*\*From Schedule B, Part 2, 3.3:

    **12.1.3.3 Resource Allocation Management** - The contractor shall
    determine, manage, and control mission resource allocations to
    satisfy program requirements. These allocations will be consistent
    with the appropriate pressurized module capability as established by
    the cognizant carrier program office and defined in the appropriate
    payload accommodations documents. Incompatibilities will be
    analyzed, alternative means of ac accommodations developed, and
    proposed solutions negotiated with the carrier program office. The
    contractor shall prepare the necessary documentation to manage and
    control these allocations and effect changes as required. Resource
    management shall include power, energy, heat rejection, structural
    integrity, weight and volume, center-of-gravity, crew time, stowage,
    data/communication, and other consumables. Resources allocations
    will constitute a major input to interface agreements and
    documentation and mission design reviews.

    \*\*\*From Schedule B, Part 2, 3.4:

    **12.1.3.4 System Engineering** - The contractor is responsible for
    performing system engineering tasks required to assure payload
    feasibility/compatibility and the integration and operations of the
    experiment payloads in/with the pressurized module. Engineering
    tasks and analyses in avionics engineering, structural/mechanical,
    and thermal/environmental engineering will be performed. Results of
    these analyses shall be documented in systems analysis reports.
    These engineering tasks shall include intra-rack analyses well as
    payload level system analyses to assure the overall compatibility of
    the payload with the pressurized module.

    **12.1.3.4.1 Structural/Mechanical** - The contractor is responsible
    for developing mechanic interface requirements for the integrated
    payload based on the Spacelab/Orbiter constraints and requirements
    (NSTS 0700, Volume 14, "Shuttle/Orbiter Cargo Interface Document and
    the Spacelab Accommodation Handbook"). Additionally, the contractor
    shall provide design/development support to the experiment
    developers for experiment hardware development when required. The
    contractor shall analyze the structural/mechanical system to assure
    compatibility with the pressurized module structural system and
    perform stress and frequency analysis of the experiment/rack
    interfaces. This will include, but not be limited to, modal survey
    testing, developing Finite Element Models, and performing a
    structural integrity analysis and a rack-to-module interface
    analysis. The contractor shall per form a Design Coupled Loads
    Analysis utilizing the current SSP/Spacelab/space station/experiment
    models and forcing functions and develop loads for
    experiment-to-rack, or carrier stress analysis to support the CDR.
    The structural verification shall include stress analysis, interface
    analysis, fail-safe/safe-life/fracture mechanics analysis, and
    fatigue assessment. These analyses shall be accomplished to account
    for launch, on-orbit, normal and emergency landing phases, and rapid
    safing assessments with the results documented in systems analysis
    reports. The contractor shall support the SSP and space station
    pressurized module Coupled Loads Analyses by providing inputs and
    evaluations as required.

    **12.1.3.4.2 Thermal/Environmental** - The contractor shall define,
    document, and control all the thermal/fluid interfaces for the
    integrated payload at the experiment level. These interface
    requirements shall be consolidated to develop the total integrated
    mission requirements. The contractor shall perform the thermal
    design by developing Systems Improved Numerical Differencing
    Analyzer math models for payload components, integrated racks, and
    the integrated module, and shall analyze the thermal/environmental
    requirements of the integrated payload to assure compatibility with
    the SSP and SSP pressurized module. Typical analyses shall include
    consumables analysis, smoke detection and fire suppression system
    performance, avionics air loop flow versus pressure drop analysis,
    fluid loop design analysis, vacuum venting system design analysis,
    and the carrier environmental control and life sup port system
    performance evaluation using simulation parameters derived from the
    mission time lines covering prelaunch through postlanding
    conditions. The results shall be documented in systems analysis
    reports. The contractor shall also support the SSP and space station
    pressurized module thermal analyses by providing inputs and
    evaluations as required.

    **12.1.3.4.3 Electrical** - The contractor is responsible for
    developing the analytical tools necessary to determine the
    electrical power resource utilization by payload equipment to be
    located in the pressurized module during all phases of the mission
    or flight increment. The contractor shall analyze the electrical
    requirements of the integrated payload to assure compatibility with
    the carrier electrical power distribution system. The analysis shall
    include power utilization, total energy utilization, voltage drop of
    the electrical distribution system, and electromagnetic
    compatibility. Power and data interfaces between the payload and the
    carrier are to be defined to the lowest level of detail and verified
    through test/analysis procedures. The analyses shall be done for the
    pre-launch, launch, on orbit, re-entry, and postlanding phases. The
    results will be documented in a systems analysis report and
    submitted to the SSP in the appropriate PIP annexes and to the space
    station through applicable documentation.

    **12.1.3.4.4 Mass Properties** - The contractor shall analyze the
    payload requirements and develop the integrated payload mass
    properties report. This analysis shall also include the mass and
    center-of-gravity of the experiment elements at the rack level. The
    results shall be documented in a systems analysis report and updated
    quarterly.

    **12.1.3.4.5 Stowage Assessments** - The contractor shall develop
    and maintain a stowage list of all stowed items to be carried on a
    mission, defining their characteristics and usage requirements. The
    contractor shall perform an integrated stowage analysis of total
    mission stowage requirements against the carrier capabilities and
    identify problem areas. The contractor shall develop a stowage plan
    that locates the stowed items within available space taking into
    account mass and volume limitations of stowage containers/lockers
    provided by the carrier or other sources.

    \*\*\*From Schedule B, Part 2, 4.0:

    **12.1.3.5 Mission Peculiar Equipment/Other Support Hardware
    Development** - The contractor shall develop and/or procure MPE and
    other support hardware and components required to integrate
    experiment hardware to Spacelab components. Items shall include, but
    not be limited to:

    a\. Structural integration hardware, including fittings, payload
    mounting adapters, brackets, and all hardware necessary for
    attaching experiments/payloads to the Spacelab/Orbiter.

    b\. Electrical cables and wire harnesses, including electrical
    connectors, wire, and cables.

    c\. Plumbing and tubing for the circulation of coolant and fluids
    between the payload and Spacelab/Orbiter subsystem interface
    panels/components.

    d\. Training hardware to support MIT/S and/or Joint Integrated
    Simulation (JIS).

    **12.1.3.5.1 Hardware Requirements Definition** - The contractor
    shall be responsible for defining MPE and other mission support
    hardware/equipment required to facilitate payload integration with
    the Spacelab. The contractor shall use experiment requirements
    defined in the IERD and results from mission
    feasibility/compatibility and other engineering analysis to
    determine the MPE and other hardware needed to support the mission.
    The contractor shall assess the availability of these items from
    previous missions and recommend whether to utilize previously
    developed equipment, modify existing equipment, or procure new
    equipment. These items shall be identified and defined in
    appropriate mission documentation.

    **12.1.3.5.2 Hardware Design/Fabrication** - Using the requirements
    identified in the IERD, the contractor will initiate the design,
    development, hardware fabrication, and/or procurement for all MPE,
    training, and GSE hardware to support the integration of the
    payload. The contractor shall perform sufficient design engineering
    to prepare procurement specification and/or other requirements
    documentation such as schematics and drawings for each required new
    or modified hardware to support the mission, flight increment,
    training, or ground operations. Concurrent to these activities, the
    contractor will prepare and submit for approval all of the attendant
    program-level documentation and the required test plans and
    procedures which support the testing and flight certification of all
    hardware. The contractor will also provide test and certification
    reports to the appropriate organizations for approval and subsequent
    flight certification. All designs will be consistent with
    established JSC/NASA policies and specifications governing the
    design and certification of fight hardware (NSTS 7700, Volume 14,
    "Shuttle' Orbiter Cargo Interface Document," Spacelab Accommodation
    Handbook, SSP 30000, "Space Station Program Definition and
    Requirement," and other requirements defined in attachment J). The
    contractor shall all drawings, control documentation, and analytical
    reports necessary for the PDR band CDR prior to drawing release and
    hardware fabrication.

    \*\*\*From Schedule B, Part 2, 5.0 Data Mgt.:

    **12.1.3.6 Data Management** - The contractor shall be responsible
    for the development, coordination, and implementation of flight and
    ground telemetry and command data requirements to support the
    preflight training, inflight mission, and postflight data
    distribution activities. The data include, but are not limited to,
    digital, analog, as well as photographic, TV, and video.

    The contractor shall perform a detailed analysis of the mission
    payload complement to identify data system, TV, and communications
    requirements for flight and training of payload crew and ground
    controllers. The contractor shall support the development of PIP
    Annex 2 and 7 as related to data management activities, and be
    responsible for the development of PIP Annexes 4, 5, and 12 as well
    as other mission related documentation (i.e., Payload Data Flow
    Timeline, POCC Data Base Tape, Payload Data Base Tape, etc.). In
    addition, the contractor shall support the definition and
    development of payload simulation software, data and data interface
    requirements, and hardware for the Mission Integrated Training
    Facility (MITF), the Mission Control Center (MCC), POCC, remote
    Payload Experiment Developers facilities, Spacelab trainers and
    simulators and other applicable space station facilities as
    required.

    **12.1.3.6.1 Flight Data System** - The contractor shall performs an
    engineering evaluation of the data, TV, and communications
    interfaces in order to determine total payload data requirements.
    These inflight data requirements shall be compared with SSP,
    Spacelab, and space station capabilities and constraints to
    determine the adequacy of the onboard data, TV, and communications
    system standard configuration and determine the requirement for
    supplementary payload provided data system hardware. The contractor
    shall use the results of this analysis to develop and recommend a
    flight data system configuration and shall include specifications
    for any new equipment items, if needed. The contractor's proposed
    system de sign shall be included in the appropriate design review
    packages.

    **12.1.3.6.2 Ground Data System** - Using experiment developer
    inputs, the contractor shall define the ground data system, TV, and
    communications network which is needed to support preflight,
    mission, and postflight data, voice, and video transmission. Where
    appropriate, the contractor shall provide inputs to the PIP and the
    related annexes to detail ground data communication systems for
    flight, training support, and postflight products. The contractor
    shall subsequently develop a plan for data, TV, and communications
    network implementation and shall proceed to procure or otherwise
    establish the network. The contractor shall develop procedures for
    data communication verification to assure that the established
    configurations fulfill data, voice, video transmission, and user
    equipment requirements. In accordance with the approved procedure,
    the contractor shall verify the capabilities of the network to
    successfully support all phases of the mission.

    12.1.3.6.3 Data System Software

    **12.1.3.6.3.1 Flight Software** - Using experiment developer
    inputs, the contractor shall identify and define flight software
    required to acquire, process, format, display, and record experiment
    data. Experiment parameters will be downlinked via SSP module
    experiment computer, or the high rate multiplexer. The flight
    software shall provide for all interfaces with the onboard data
    system. The contractor shall develop design specifications which
    shall be used as the basis for the development and/or verification
    of the onboard experiment computer software. This software shall be
    modified and updated, as required, to a configuration that will
    fully support the mission. Software for experiment microprocessors
    shall be furnished by the hardware developer.

    **12.1.3.6.3.2 Ground Software** - Using experiment developer
    inputs, the contractor shall provide the ground software required to
    support payload integration and check out at the launch site and
    support of the mission during integrated training and flight
    operations. As a minimum, ground software systems will be provided
    to perform/support payload integration; to validate all data and
    functional interfaces, including physical connections; to validate
    data formats and data rates; and to verify capabilities for
    acquisition, processing, formatting, display, and analysis of
    payload flight data. To meet these requirements, the contractor
    shall evaluate and use, wherever possible, ground software systems
    furnished by the experiment developers for experiment check out,
    assembly, science verification, and training modified only as
    necessary to support payload integration at the launch site and
    flight operations in the POCC. The contractor shall analyze ground
    software verification procedures and testing to as certain their
    suitability to meet integrated mission requirements. The contractor
    shall support mission management in negotiating changes with the
    experiment developers to satisfy mission level considerations.

    **12.1.3.6.3.3 Simulation Software** - The contractor shall identify
    requirements for simulation software for training payload crew and
    payload ground controllers. Where necessary, the contractor shall
    provide simulation software or interfacing software to interact with
    existing experiment and subsystem simulation software.

    \*\*\*From Schedule B, Part 2, 6.0 Flight Operations:

    **12.1.3.7 Flight Operations** - The contractor is responsible for
    planning and implementing payload flight operations activities for
    the preflight, flight, and postflight phases of the mission. Payload
    operations activities include staffing the POCC, developing
    products, procedures, and contingency responses required to support
    nominal, and off-nominal mission requirements, as well as
    participating in training activities and simulations.

    **12.1.3.7.1 Flight Planning** - The contractor shall support
    mission management in conducting flight planning activities to
    develop operational support requirements, mission guidelines and
    constraints, payload timelines, PFDF inputs, POCC and/or Payload
    Operation Integration Center (POIC) requirements, training guides,
    plans, and schedules, and training facility and POCC cadre support
    requirements. The contractor shall also provide inputs to the major
    review packages, PIP and PIP annexes, payload interface control
    agreements, and other appropriate interface documents.

    **12.1.3.7.1.1 Operations Support Planning** - The contractor shall
    prepare a Mission Management Flight Operations Support Plan, which
    will describe the functional operations requirements for each flight
    phase and the interaction among functions, the major products for
    each function, organizational responsibility for the functions,
    management and technical' interfaces, correlation of applicable
    functions to the respective PIP annexes, and performance schedules
    keyed to major payload and NASA milestones. This includes preflight
    and postflight as well as real-time flight activities.

    The contractor's POCC cadre personnel shall support flight
    operations planning through the development of flight operations
    documentation such as console handbooks, POCC Operations Guidelines
    and Handbook, and Joint Operations Interface Procedures.

    **12.1.3.7.1.2 Operations Guidelines and Constraints** - The
    contractor shall develop and maintain mission or increment
    operations guidelines and constraints. These guidelines and
    constraints shall be developed for use by the mission manager in
    directing mission planning and development activities. As a minimum,
    the guidelines and constraints shall address crew and hardware
    on-orbit availability; POCC and remote user facilities planning and
    interfaces; payload operations responsibilities and support
    activities; payload and NASA crew availability; and command,
    communications, and data management activities. The guidelines and
    constraints shall be updated and published at periodic intervals in
    concert with mission planning milestones.

    **12.1.3.7.2 Flight Design** - In support of flight design, the
    contractor shall analyze the mission support requirements imposed by
    the experiments for individual and total impact on mission planning
    and implementation. This analysis shall include, but not be limited
    to, controls and displays, uplink and downlink requirements, vehicle
    stabilization, film and data management, and alternate operation
    techniques. Mission design criteria shall be developed defining
    trajectory inclination, use of consumables, mission ephemeris,
    air/ground communications coverage, data dumps, and attitude
    profiles. The results of these analyses shall be documented for each
    major review.

    The contractor shall develop composite mission timelines based on
    individual experiment timeline requirements. Each experiment
    activity shall be scheduled on the mission timeline to determine
    conflicts with crew availability, Tracking and Data Relay Satellite
    System acquisition, vehicle attitude, stability, hardware
    availability, onboard data management, or scheduled orbital vehicle
    events, or with other experiment requirements. Conflicts and
    incompatibilities shall be resolved through trade-off analyses
    coordinated with the appropriate personnel. The contractor shall
    define experiment operating schedules, crew activities assignments,
    mission timelines, power profiles, constraints, and alternate
    operating plans.

    The contractor shall prepare flight timelines that include available
    "windows" for the scheduling of experiment activities in compliance
    with the Crew Procedures Management Plan. Incompatibilities between
    the SSP and space station and payload scheduling requirements shall
    be coordinated with the appropriate organization. Resolutions to
    these conflicts shall be confirmed by review of integrated SSP and
    space station payload mission timelines subsequently issued by the
    responsible organization.

    The flight design results shall be documented in the PIP, PIP
    annexes, and other appropriate interface agreements, and these
    inputs shall be updated as payload requirements and operating
    constraints are refined.

    12.1.3.7.3 Payload Crew Support

    **12.1.3.7.3.1 Payload Crew Training** - The contractor is
    responsible for managing, scheduling, coordinating, and tracking the
    payload training of assigned crewmembers. The contractor shall
    coordinate and support the implementation of experiment orientation,
    task, and phase training activities conducted by the experiment
    developers. Additionally, the contractor shall plan and implement
    mission integrated payload training sessions conducted in the MITF.
    In support of all these training activities, the contractor shall
    assist the MMO in defining and documenting training requirements in
    applicable mission requirements documentation and plans (PIP Annex
    7, Training Plans etc.), in coordinating and submitting master and
    training protocols to the HRPPC, and in obtaining HRPPC approvals
    prior to the start of sessions. The contractor shall provide the
    technical expertise and support necessary to conduct nonhuman
    specimen handling and training either off, or onsite where
    applicable.

    **12.1.3.7.3.2 Baseline Data Collection** - The contractor shall
    coordinate, schedule, and manage the PI/experiment
    developer-requested BDC program as directed by the MMO. The
    contractor will support MMO in activities affected by the HRPPC in
    regards to crew safety during the conduct of any BDC operations.

    **12.1.3.7.3.3 Launch and Landing Site Support** - The contractor
    shall provide support at the launch and landing site to support
    payload crew activities. These tasks may include, but not be limited
    to, delivery of the PFDF to the launch site, incorporating pen and
    ink changes to the PFDF during the preflight crew review,
    transcribing crew flight voice tapes to word processor formats, and
    reproduction of the crew flight logs, data sheets, and notes for
    distribution to the science teams and experiment developers as
    defined in appropriate documentation by the MMO prior to flight.

    **12.1.3.7.4 Payload Flight Data File Development Management** - The
    contractor is responsible for identifying, developing, and
    coordinating the development, validation and verification of
    procedures, documentation and other items the payload crew will flip
    books, and data sheets shall be developed in accordance with
    requirements documented in the inflight to successfully accomplish
    experiment objectives. PFDF books and associated cue cards, PIP and
    other NASA-provided PFDF guidelines and requirements.

    The contractor is responsible for defining and in providing basic
    procedures, nomenclature, and schedules for PFDF production to the
    experiment developers as a guide for PFDF inputs to be provided by
    these organizations.

    The contractor shall be responsible for the production and
    distribution of all PFDF documents for integrated payload training,
    JIS and flight, with the exception of flight quality crew copies to
    be used during the mission. Functions associated with these tasks
    include coordination, review and revision, editing, data entry,
    information management, and publishing.

    12.1.3.7.5 Payload Operations Control Center/Payload Operation
    Integration Center Support

    **12.1.3.7.5.1 Real-Time Support** - The contractor shall provide a
    cadre of personnel to operate consoles at the MSPC POCC and
    equivalent space station facilities, and the JSC MCC Customer
    Support Room during the conduct of flight simulations and flight
    operations. The staffing requirements are determined by the MMO
    based on mission duration and console assignments. Staffing of
    console positions must be planned for around the. Dock operations
    with sufficiently trained and certified personnel to accommodate
    Spacelab and/or space station missions. The composite knowledge of
    the POCC cadre shall include intimate familiarization of the payload
    hardware, its operating characteristics and limitations, the mission
    science objectives, payload and vehicle safety concerns, mission
    rules, carrier vehicle system and subsystems operations and
    interfaces, POCC/MCC and POCC/SSCC operations protocols, and
    POCC/POIC data and communications systems operations.

    **12.1.3.7.5.2 Payload Operations Support Team (POST)/Payload
    Operation Integration Center Training** - The contractor shall
    define and document training requirements POST members in applicable
    mission requirements document and training plans. The contractor
    shall develop and provide basic mission overview and console
    familiarization training for POST assigned to the mission by the
    mission manager. The contractor shall develop and implement all
    training plans and materials associated with POST preparatory
    training. The SSP, Mission Operations Directorate, MSFC POCC and
    other NASA training material dealing with particular mission related
    subjects shall be used when possible. The contractor shall conduct
    all POST training activities including those in conjunction with
    payload flight crew training, and shall provide training guidance,
    including objectives, methods, schedules for accomplishment,
    facility and equipment requirements, and certification requirements.

    **12.1.3.7.6 Simulations Management** - The contractor shall plan,
    script, and conduct simulations for the payload flight crew and
    ground support team personnel. These simulations shall support
    MIT/S, stand-alone simulations for the POST or payload crew, and/or
    JIS. The contractor shall conduct a range of simulations for each
    team as necessary to assure training is accomplished as required by
    POST and payload crew training requirements for certification.
    Interfaces will be established with the appropriate NASA
    organizations in order to coordinate and support all simulation
    activities.

    **12.1.3.7.6.1 Mission Integrated Training Facility Maintenance** -
    The contractor shall provide oversight and management of the MITF,
    which supports flight and ground crew training, integrated payload
    training, and JIS. Following SOP's, the contractor shall coordinate
    and implement any relocation of the MITF hardware and software
    systems to meet mission training specific requirements. The
    contractor shall also implement or coordinate the maintenance of the
    data systems, communication systems, and video systems which support
    the training within the Spacelab trainer. The contractor shall
    provide modifications to the training payload and support facilities
    for mission specific requirements. The contractor shall conduct
    analysis of changes at the MSFC Huntsville Operations Support
    Center, JSC MCC, and within the Orbiter and Spacelab
    systems/subsystems; subsequently, the contractor shall then
    implement upgrades to the MITF to meet mission specific training
    objectives. The contractor shall develop documentation to establish
    a baseline configuration of the MITF which meets the mission
    specific training objectives.

    \*\*\*From Schedule B, Part 2, 7.0 Payload Integration:

    **12.1.3.8 Payload Integration** - The contractor shall be
    responsible for conducting payload integration activities that
    include but is not limited to, the development of requirements and
    the performance of acceptance/certification testing of the MPE; and
    development of all documentation required for the verification of
    the integrated payload to Spacelab/Orbiter interfaces. The
    contractor shall provide support during ground processing of the
    payload at KSC by providing logistics control of all flight
    hardware; engineering and technical support during the prelaunch
    activities, early access operations at the landing site, and
    postflight deintegration. Specifically, the contractor shall perform
    the following activities:

-   Develop/coordinate integrated ground processing activities with KSC

-   Verify MPE/experiment hardware

-   Support launch-site integration activities

-   Develop Logistics Management Plans/provisioning

    **12.1.3.8.1 Ground Processing of the Integrated Payload** - Based
    upon the ground processing requirements established by the
    experiment developers, the contractor will develop the required
    documentation to direct the integration efforts of the payload
    processing and carrier/launch vehicle processing organizations at
    the KSC. The contractor shall consolidate all ground operations and
    resource requirements established by the experiment developers and
    the MMO into the appropriate documentation for submission to the KSC
    Launch Site Support Manager (LSSM). These requirements shall include
    all pre- and postflight activities, facility and resource
    requirements to be furnished by KSC, experiment and integrated
    payload test requirements, late access and early access
    requirements, deintegration requirements, and hardware disposition
    after the completion of the deintegration activities. The contractor
    shall define the specific integration and test requirements to be
    performed during the various phases of the ground operations flow
    and incorporate these requirements into the appropriate file and
    volume of the OMRSD.

    **12.1.3.8.2 Mission Peculiar Equipment and Experiments Developer
    Hardware Verification** - All MPE and experiment developer, hardware
    must fulfill established verification requirements prior to being
    approved for flight. The contractor shall establish an MPE
    Verification Plan and identify the test, inspection, and/or
    analytical requirements necessary to fulfill all verification
    requirements. In addition, the contractor shall review each
    experiment developer's Verification Plan for accuracy and
    completeness prior to recommending approval by the mission manager.
    The contractor shall establish a technical review and approval
    process prior to accepting the closure rationale of each
    verification requirement. The contractor shall develop a tracking
    and status reporting system by hardware item to assure that all
    verification requirements have been closed prior to flight and
    provide periodic reports to the mission manager on the closure
    progress of these requirements.

    **12.1.3.8.3 Ground Operations** - The contractor will provide KSC
    mission management representation during all phases of the payload
    integration, test, and check out, launch preparations, late access
    loading of the carrier/launch vehicle, launch, postlanding early
    access operations, and the subsequent deintegration of the payload
    after the return of the carrier to the KSC Operations and Checkout
    Building or other payload processing facility. In addition, the
    contractor shall establish and maintain a permanent Launch Site
    Support Office staffed with engineering, technical, and clerical
    personnel to provide a focal point for documentation and
    requirements transfers between the mission manager and the LSSM.

    **12.1.3.8.3.1 Ground Operations Management Planning** - The
    contractor shall develop management plans to effectively implement
    MMO objectives for all phases of payload integration and ground
    operations. These plans shall identify guidelines, policies, and
    procedures to be used by MMO and experiment developer personnel in
    accomplishing the MMO objectives and provide feedback to the MMO on
    the progress of payload related activities during the ground
    processing. These plans shall address such activities as, late and
    early access operations, the KSC-provided documentation flow
    control, engineering configuration requirements, and the Spacelab
    mission stowage.

    **12.1.3.8.3.2 KSC Documentation Logging and Tracking** - The
    contractor shall establish the mechanisms and data base tools
    necessary to track and control the flow of documentation generated
    by KSC integration personnel during the ground processing of the
    payload. The contractor shall be responsible for the coordination of
    this KSC-developed documentation with the experiment developers for
    completeness and accuracy relating to specific hardware processing
    requirements prior to recommending approval by the mission manager.
    This documentation may include such things as old Engineering
    Changes, Problem Reports, Test and Assembly Procedures, OMI, OMRSD
    inputs and other operation documents. The contractor shall provide
    periodic reports to the mission manager on the statue open
    documentation prepared by KSC integration personnel.

    12.1.3.8.4 Logistics

    **12.1.3.8.4.1 Stowage Provisions** - The contractor shall develop
    the mechanisms to support the activities associated with the
    provisioning of stowage. The contractor shall prepare and maintain
    the necessary documentation to define the stowage items, designate
    their locations, design, procure or otherwise provide for the
    packing material required to hold the stowed items in the various
    locker/container locations, support the payload crew training with
    the stowage items, initial and/or support the bench reviews which
    influence the final configuration of the stowage, and implement the
    delivery of all stowage to the launch site and its packing for
    flight. The contractor shall prepare the necessary documentation and
    support the activity necessary to remove time critical items from
    stowage at the landing site and turn it over to the appropriate
    organizations and then to process the remaining items to assure
    proper disposition and return during the postflight deintegration
    phases.

    **12.1.3.8.4.2 Flight Hardware Logistics** - The contractor shall
    establish the necessary logistics procedures and techniques to
    monitor the flow of all mission management-provided flight hardware,
    flight spares, and any GSE hardware used during the payload
    integration process throughout the entire provisioning process
    starting at the hardware procurement/fabrication phase and
    continuing until the final deintegration of the payload and the
    return of the hardware to the MMO. These logistic procedures and
    techniques must be capable of providing constant visibility to the
    mission manager on the status of all payload hardware delivery to
    the launch site from all the payload participants to support the KSC
    payload integration schedules and launch processing activities. The
    contractor shall initiate, conduct, and review all data presented at
    the IRR's held for each payload hardware supplier and identify and
    document the hardware delivery readiness and documentation status
    prior to transfer to KSC and the formal turnover to the MMO.

    \*\*\*From Schedule B, Part 2, 8.0 Advanced Programs/Planning:

    **12.1.3.9 Advanced Programs/Planning** - In support of mission
    management, the contractor shall provide definition studies and
    related mission planning oversight for advanced programs such as
    Spacelab, space station, and Lunar and Mars exploration. The
    contractor shall provide concept development to new start programs
    through white papers, draft presentations, and working groups. The
    contractor shall assist in programmatic definition by preparing
    presentations and program plans; defining processes, flows, and
    schedules; identifying requirements, roles, and responsibilities;
    reviewing documentation; and assessing compatibility between user
    requirements and program accommodations.

    The contractor shall perform special studies and develop
    payload/experiment programs for human-tended or non-human-tended,
    pressurized module missions based on requirements defined by mission
    management. This effort will include identification of
    payload/mission options, requirements evaluation, resources
    compatibility, and scheduling alternatives. Study activities would
    also include development of recommended design concepts for flight
    hardware required to meet the advanced programs requirements.

    The contractor shall perform special studies involving human-tended
    or non-human-tended, pressurized modules as required in response to
    task directives issued periodically by the contracting officer.
    These directives will also identify the labor-hours allocated for
    the study, the time and place of performance, labor skills, and
    other resources which are deemed necessary to complete the study.

    \*\*\*From Schedule A, 9.1.3.1, NIO:

    **12.1.3.9.1 Future Mission Studies** - This function involves the
    integration of future mission plans into a consistent and rational
    scenario. This shall include the sorting of the missions to find
    common elements and systems. It shall also include the assembly of a
    planning data base of the proposed missions and integrated
    scenarios. The following are representative tasks the contractor
    shall perform:

    12.1.3.9.2 Provide analysis of proposed future missions to find
    common elements and systems as well as other interactions which may
    result from utilization of extraterrestrial resources; and determine
    requirements for these common elements and systems, assemble
    recommended future mission sets based on alternative estimates of
    public support, and determine the impact of these future missions
    and scenarios on vehicle requirements.

    12.1.3.9.3 Support the development of exploration scenario reference
    missions and programmatic architectures including technical
    requirements and schedules in the areas of space transportation,
    planet surface systems, orbital nodes, ETO transportation, life
    science research, precursor missions, technology developments,
    communications and navigational infrastructure, and space station
    evolutionary growth; and development of requirement and synthesis of
    implementation results.

    12.1.3.9.4 Determine the impact of new technologies on proposed
    future missions; compare costs of developing these technologies with
    the benefits; and prepare yearly technology development plans.

    12.1.3.9.5 Develop candidate mission elements to provide a
    reasonable starting point for technical analyses. Provide estimates
    of power and labor support required by the compiled scenarios, as
    well as estimates of space transportation fleet requirements.

    12.1.3.9.6 Support the missions analysis and systems engineering to
    combine the study results into complete initiative scenarios;
    evaluate these results; and address synergy and compatibility
    issues.

    12.1.3.9.7 Perform trade studies to evaluate promising options to
    mission strategies which affect more than one area of interest; and
    support the knowledge base used to synthesize inputs on human
    planetary surface systems, space vehicles, transportation nodes, and
    technology development.

    12.1.3.9.8 Document the functional analyses which shall support the
    development of the requirements document which transmit initiative
    requirements to other NASA Headquarters' codes; and support
    development of the Annual Report that shall present the mission
    studies performed to satisfy initiative requirements and shall also
    report the systems engineering process used.

    \*\*\*From Schedule B, Part 2, 2.5 Special Studies:

    **12.1.3.10 Special Studies** - The contractor shall perform special
    studies, including engineering analyses, conception/feasibility
    analyses, and trade-off studies as required by mission management
    for long rang strategic and tactical program planning. These studies
    shall be undertaken and completed in response to specific task
    directives issued by mission management. These directives will also
    identify the labor hours allocated for the study, the time and place
    of performance, labor skills, and other resources which are deemed
    necessary to complete the study. Results will be documented formally
    or informally as defined by mission management.

    \*\*\*From Schedule B, Part 1, 3.0; 3.1:

    **12.1.3.11 Payload Planning and Analysis** - Payload planning and
    analysis is the development of payload schedules and profiles to
    optimize the use of mission resources to achieve program objectives.
    The contractor shall provide all resources needed to plan, schedule,
    prepare, and process concurrent payloads on multiple missions. The
    contractor shall identify and select payload components and shall
    perform long range planning that permits maximum flexibility in
    assigning HLS experiments/hardware to missions.

    The contractor shall continuously conduct payload planning
    activities to meet program objectives and to accommodate program
    changes. The contractor shall use existing HLS LSFEP data and
    resources to the maximum beneficial extent to make recommendations
    for payload planning and optimization. The contractor shall provide
    planning and analysis for the allocation of experiments and
    equipment to missions, for the selection and grouping of experiments
    on flights, and for the allocation and control of project resources.

    The contractor shall identify payload parameters for HLS experiments
    including the required flight hardware, experiment sessions, mission
    resources, and crew timelines. The contractor shall perform planning
    analysis and requirements definition for approved life sciences
    experiments and shall perform engineering analyses of candidate life
    sciences experiments. This activity includes the definition of new
    flight hardware and assessing the compatibility of proposed
    experiments with existing or planned hardware including life
    sciences laboratory equipment (LSLE), experiment unique equipment
    (EUE), and associated support hardware. The contractor shall analyze
    the relationships between experiments and baselined integration and
    operational requirements.

    **12.1.3.11.1 Flight/Payload Requirements** - The contractor shall
    develop and summarize all flight/payload resource requirements and
    parameters for HLS experiments. The contractor shall assure that
    experiment systems are consistent with scientific and
    vehicle/payload requirements.

    The contractor shall assist PI's in experiment definition including
    collection of engineering data, flight interface information, and in
    developing preflight experiment data requirements and validation
    criteria. The contractor shall define voice, data, and video
    requirements including content, format, time correlation, and
    processing. The contractor shall assure the compatibility of the
    PIs' requirements with the overall payload and with any vehicle
    and/or payload specifications, constraints, or limitations.

    **12.1.3.11.2 Principal Investigator Support for Payload Planning
    and Development** - In many cases, life sciences experiments are
    proposed and conducted by scientists who are unfamiliar with NASA
    requirements and management techniques. The contractor shall assist
    the PI's in bridging this gap; to reduce the burden on the science
    team; to reduce documentation costs; to assure proper use of flight
    hardware equipment; and to assure compatibility between science
    requirements, program requirements, mission resources, vehicle
    interfaces, and vehicle/crew resource limitations.

    **12.1.3.11.3 Science Requirements Definition** - The contractor
    shall obtain and document the science requirements for each
    experiment. The major source of information (besides the original
    proposal) will be meetings and discussions with the PI and/or the PI
    staff. The science requirements definition shall be documented in
    the experiment document (ED) (Section 3.2.1.1).

    **12.1.3.11.4 Experiment Systems Definition Development** - The
    contractor shall assist PI's in defining and developing a "flight
    experiment system" for each experiment. The contractor shall analyze
    alternate implementations and identify the limitations of each.

    **12.1.3.11.5 Performance Analysis** - The contractor shall gather
    and assess payload/mission performance data, shall evaluate each
    system and subsystem, and shall prepare performance/failure reports.
    In these reports the contractor shall recommend hardware and
    procedure changes to HLS when problems are identified.

    \*\*\*From Schedule B, Part 1, 3.2 Experiment Management:

    **12.1.3.12 Experiment Management** - The contractor shall manage
    all HLS flight experiments. The wide variety and scope of HLS
    experiments require the contractor to provide expertise in several
    scientific and engineering disciplines including but not limited to:

-   Project engineering for scientific research projects

-   Physics, general engineering, electrical and electronic engineering,
    and biomedical engineering

-   Equipment performance, human engineering, and safety of
    electrical/mechanical hardware for human research

-   Project and resource management, including but not limited to
    planning, scheduling, and resource requirements estimating

-   Software engineering

    \*\*\*From Schedule B, Part 1, 3.2.1:

    **12.1.3.12.1 Experiment Support Teams (ESTs)** - To accomplish the
    tasks and requirements of this section, the contractor shall provide
    an EST for each HLS experiment. The teams shall consist of an
    experiment manager (EM), experiment engineer (EE), experiment
    support scientist (ESS), and other support personnel. The teams
    shall support HLS in assuring experiment success, e.g., in assuring
    that the experiment satisfies science requirements, meets NASA
    safety and other requirements, and is delivered on time and within
    budget.

    **12.1.3.12.1.1 Experiment Requirements Definition** - The
    contractor EST(s) shall work with the PI team(s) to develop an ED
    for each experiment. The ED is the document used by NASA/HLS and the
    PI to establish and control experiment requirements to allocation
    resources, and to define interfaces for the experiment. Sections of
    the ED are incrementally baselined (approved and placed under
    configuration control). After baselining, all changes are processed
    under the NASA/HLS configuration control system. Each ED includes:

    a\. Experiment science requirements

    b\. Flight equipment required

    c\. Mission resources allocated

    d\. Physical and functional interfaces

    e\. Crew activities

    f\. Ground processing requirements at JSC, the launch site, and
    other locations (if required)

    g\. Operations and data management requirements

    h\. Hardware/software design and verification requirements

    The ED Structure and format are described further in LS-20079,
    Experiment Document Format and Instructions and the HLS SOP Manual.

    **12.1.3.12.1.2 Statement of Work Development** - The contractor EST
    shall assist HLS in writing experiment SOWs. Each SOW defines the
    tasks and requirements of an experiment contract. An experiment SOW
    typically includes but is not limited to:

    a\. Introduction

    b\. Applicable documents

    c\. PI support requirements

    d\. Hardware requirements

-   Technical

-   Safety

-   Reliability

-   Quality assurance

-   Materials

-   Configuration management

e\. Documentation requirements

**12.1.3.12.1.3 Experiment Systems Development** - The contractor EST
shall:

a\. Review proposed hardware designs against the scientific,
performance, compatibility, safety, quality and reliability requirements
for HLS flight software/hardware

b\. Perform experiment and hardware design and readiness reviews,
including but not limited to Preliminary Design Reviews (PDRs), Critical
Design Reviews (CDRs), and Integration Readiness Reviews (IRRs)

c\. Propose and evaluate design changes to meet experiment objectives
and maintain mission compatibility

d\. Perform acceptance testing of delivered flight hardware and
experiment systems

e\. Perform system studies and analyses to assure performance and
mission compatibility

**12.1.3.12.1.4 Experiment Systems Documentation** -The contractor EST
shall produce the following experiment documentation, including but not
limited to:

a.  Experiment documents

b.  Interface control documents (ICDs)

c.  Engineering study reports

d.  Verification reports

e.  Reliability reports

f.  Test preparation sheets

g.  Hazard reports

h.  Discrepancy reports (DRs)

i.  Change requests

j.  Action closure documents

k.  Procedures for assembly and test

l.  Payload integration plans (PIPs)

m.  Project activity reports

n.  Experiment and engineering drawings/drawing change notices

o.  Implementation plans

p.  Combined certification/acceptance test plans/procedures

q.  Certification reports

r.  Structural stress and thermal analysis reports

s.  End item specifications (EISs)

t.  Operation, maintenance, and handling manuals

\*\*\*From Schedule B, Part 1, 3.2.2:

**12.1.3.12.2 Roles of Experiment Managers** - The contractor shall
provide EMs for HLS experiments to be conducted on any/all space flight
missions. EMs shall be responsible for leading or co-leading and
managing the EST in the performance of the following tasks and
functions, and where appropriate or necessary, performing some or all of
these tasks and functions:

-   Experiment systems testing

-   Experiment safety compliance

-   Experiment systems interface compatibility

-   Experiment verification and certification

-   Experiment hardware/software configuration control

-   Experiment coordination

-   Experiment definition

-   Documentation support

-   Experiment hardware/software development

-   Experiment requirements development

    **12.1.3.12.2.1 Experiment Systems Testing** - EMs shall be
    responsible for performing, managing, and assuring that all required
    experiment systems are performed. The specific details and
    requirements concerning such tests are enumerated under the duties
    of the EE in Section 3.2.3.1.

    **12.1.3.12.2.2 Experiment Safety Compliance** - EMs shall be
    responsible for assuring that the experiment complies with safety
    requirements and that EEs perform the specific safety related tasks
    enumerated Section 3.2.3.2. Other duties of the EM shall include but
    not limited to:

    a\. Support for NASA/JSC payload flight safety reviews (FSRs) and
    KSC payload ground safety reviews (GSRs)

    b\. Developing safety controls, verification methods, and tests

    c\. Analysis of failure modes

    **12.1.3.12.2.3 Experiment Systems Interface Compatibility** - EMs
    shall be responsible for defining and controlling interfaces for HLS
    experiments.

    **12.1.2.12.2.4 Experiment Verification and Certification** - EMs
    shall be responsible for performing verification, and certification
    of all HLS experiment systems.

    **12.1.3.12.2.5 Experiment Hardware Configuration Control** - EMs
    shall be responsible for managing and performing configuration
    control of experiment hardware by:

    a\. Assuring the "as built" configuration of delivered
    hardware/software is reflected on the documentation

    b\. Preparing CRs and evaluating proposed modifications to assure
    that performance, compatibility, safety, quality assurance and
    reliability requirements are met

    c\. Developing plans for hardware modifications and verification
    testing

    d\. Presenting proposed changes to the HLS CCB

    e\. Providing closure documents for CCB actions

    **12.1.3.12.2.6 Experiment Coordination** - EMs shall be responsible
    for managing, performing, and coordinating all experiment
    activities, including, but not limited to:

    a\. PI interfaces

    b\. Hardware shipment to vendors, KSC, or other required locations

    c\. Product development and/or modification

    d\. Surveys of state-of-the-art biomedical measurement concepts and
    make recommendations thereon

    e\. Recent developments through publications, meetings, symposia,
    and by contacting technical experts in the field

    f\. Periodic status to NASA HLS on all experiment activities

    **12.1.3.12.2.7 New Experiment Definition** - The EM shall be
    responsible for supporting the definition of new experiments,
    including those on Spacelab Life sciences (SLS)-3 and SLS-4 as well
    as other future missions.

    **12.1.3.12.2.8 Documentation Support** - EMs shall develop and be
    responsible for the development of experiment documentation as
    specified in Section 3.2.1.4.

    **12.1.3.12.2.9 Experiment Hardware Development** - EMs shall direct
    experiment hardware development activities required to assure the
    success of the experiment as defined in Section 4.0 which describes
    specific requirements.

    **12.1.3.12.2.10 Experiment Requirements Development** - EMs shall
    direct the contractor EST in the development of experiment
    requirements by working with the PI team. Specific contents of the
    ED, which is used to document experiment requirements, are defined
    in Section 3.2.1.1.

    \*\*\*From Schedule B, Part 1, 3.2.3 Roles of Experiment Engineers:

    **12.1.3.12.3 Roles of Experiment Engineers** - The contractor shall
    provide EEs for, HLS experiments to be conducted on any/all space
    flight missions. Experiment engineers shall support designated EMs
    by performing the following tasks and functions:

-   Experiment systems testing

-   Experiment hardware/software safety compliance/verification

-   Experiment systems interface compatibility

-   Experiment systems interface documentation

-   Experiment verification and certification tests and reports

-   Experiment systems hardware/software development

-   Experiment hardware/software configuration control

-   Experiment hardware/software integration and maintenance

-   Experiment support for crew training

-   Baseline data collection (BDC)

-   Mission level documentation review

\*\*\*From Schedule B, Part 1, 3.2.3.1:

**12.1.3.12.3.1 Experiment Systems Testing** - EEs shall prepare and
conduct tests on experiment flight/prototype systems to verify, design,
functional performance, and interfaces. The effort shall include
planning, writing procedures, conducting tests, and documenting results.
Experiment testing shall include but not be limited to:

a.  Experiment systems verification

b.  Functional verification

c.  Certification and acceptance testing

d.  Science verification testing

e.  Mission sequence tests

f.  Procedure validation

g.  Crew training

h.  Baseline data collection

\*\*\*From Schedule B, Part 1, 3.2.3.2

**12.1.3.12.3.2 Experiment Hardware Safety Compliance/Verification** -
EEs shall:

a\. Participate in NASA/JSC safety reviews

b\. Verify safety controls, methods, and tests

c\. Prepare safety hazard reports

\*\*\*From Schedule B, Part 1, 3.2.3.3:

**12.1.3.12.3.3 Experiment Systems Interface Compatibility** - EEs shall
advise experiment teams on mission compatibility and accommodations to
assure that experiment systems will meet mission resource requirements.

\*\*\*From Schedule B, Part 1, 3.2.3.4:

**12.1.3.12.3.4 Experiment System Interface Documentation** - EEs shall
prepare and maintain ICDs that define and control the interfaces between
items of experiment equipment as defined in Section 3.2.1.4.

\*\*\*From Schedule B, Part 1, 3.2.3.5:

**12.1.3.12.3.5 Experiment Verification and Certification Tests and
Reports** - EEs shall provide support in the following areas to assure
compliance of experiment hardware verification:

a\. Review and write verification and certification plans

b\. Review, write, and perform verification and certification tests

c\. Review and compile verification reports

d\. Compile- certification reports for review by NASA/J56 Reliability

\*\*\*From Schedule B, Part 1, 3.2.3.8:

**12.1.3.12.3.6 Experiment Hardware/Software Integration and
Maintenance** - EEs shall perform and support:

a.  Integrated systems bench tests

b.  Integrated systems mockup tests

c.  Science verification tests,

d.  Mission integrated tests

e.  Joint integrated tests

f.  Mission sequence tests

g.  Special required hardware/software tests

h.  Review of mission level documentation

\*\*\*From Schedule B, Part 1, 3.2.3.9:

###### **12.1.3.12.3.7 Experiment Support for Crew Training** - EEs shall:

a.  Participate in hardware readiness reviews

b.  Participate in hardware readiness testing and check out

c.  Support training sessions

\*\*\*From Schedule B, Part 1, 3.2.3.10:

**12.1.3.12.3.8 Experiment Baseline Data Collection (BDC)** - EEs shall
support pre- and postflight BDC.

\*\*\*From Schedule B, Part 1, 3.2.3.11:

**12.1.3.12.3.9 Documentation Support** - EEs shall prepare and maintain
the documents necessary for experiment hardware development,
modification, and testing including but not limited to the documentation
enumerated in Section 3.2.1.4.

\*\*\*From Schedule B, Part 1, 4.1, except 4.1.4 which went to NEW SOW
Part II, Management and Administration:

**12.1.3.12.3.10 Experiment System Engineering Studies** - The
contractor shall perform-experiment system engineering studies and
analysis including:

a.  Performing analyses on systems, subsystems, and associated equipment
    to identify and evaluate alternative configuration approaches

b.  Performing feasibility and trade-off studies for new and/or revised
    technical approaches to assure total system compatibility

c.  Assessing technical impacts of proposed changes to experiment
    systems, subsystems, and associated equipment

d.  Providing recommendations for improvements in experiment hardware
    and software

e.  Supporting system level testing to identify problems and assist in
    troubleshooting and correction of identified problems

The results of these studies shall be presented to NASA in written
reports, oral presentations, and in the contractor's monthly progress
reports.

**12.1.3.12.3.10.1 Experiment System Interface Compatibility** - The
contractor shall assess and assure the compatibility of HLS experiment
systems with the vehicle and with mission resources.

**12.2.3.12.3.10.2 Experiment System Interface Documentation** - For
each HLS experiment, the contractor shall prepare and maintain the ICDs
that define and control the interfaces between each piece of HLS
equipment and between such equipment and the vehicle as defined in
Section 3.2.1.4.

\*\*\*From Schedule B, Part 1, 7.0:

**12.1.3.13 Project Payload Integration and Verification** - The
contractor shall be responsible for accomplishing the payload
integration and verification. The contractor shall have the
responsibility for performing, documenting, and tracking the status of
all experiment check-out and verification at JSC. Each mission manager
will identify a standard set of experiment interface functions that mist
be proven or verified to be within specific limitations. The
verification requirements include areas such as mechanical, electrical,
and thermal characteristics of the experiment operation. The contractor
will work with the installation design group to evaluate hardware
installations and assist in identifying interface and installation
problems. The contractor will be responsible for providing technical
assistance if the flight experiments are installed in the flight carrier
by a NASA Center other than JSC. The contractor may be required to
perform the installation in the flight carrier and shall be prepared to
do so.

**12.1.3.13.1 Project Payload Assembly and Installation and Payload
Integration Support** - The contractor shall be responsible for the
physical assembly and installation of the experiment prototype and
flight hardware systems into the HLS mockup structures. In the case of
Spacelab, HLS has at its disposal non-flight rack structures that have
dimensionally correct mechanical interfaces. It is planned to have
similar facilities to support space station activities and/or other
future programs. It shall be the contractor's responsibility to evaluate
the installation designs in these mockup racks as they are developed
within the contractor design group. When prototype and flight experiment
systems are delivered to HLS, the contractor will be responsible for the
assembly and installation of these systems into she mockup racks or
structures. All work will be performed with the appropriate controlling
documentation. The contractor must be prepared to work closely with the
installation design group to resolve interference problems that have not
been previously detected. A fast response problem solving/modification
capability is imperative at this stage.

During integration of the experiment/payload hardware into the launch
vehicle, the contractor will be required to support a repair and
refurbishment area at the launch site for planned and unplanned
activities. This includes the necessary equipment and personnel required
to perform troubleshooting and repairs, perform cleaning of hardware and
preparation of limited life items including the preparation of batteries
or other stored energy sources. This also includes the replacement of
consumables used during testing.

The contractor will be responsible for the logistics planning and
hardware preparation necessary to support all activities at the launch
site and landing site. This includes activities such as late loading of
items, early retrieval of items and the transport of items between the
development center and the launch and landing sites.

**12.1.3.13.2 Experiment Checkout** - The contractor shall be
responsible for working with the appropriate HLS PE and/or PI to perform
test and check-out of experiment systems. The primary responsibility for
the check-out of the experiment before turnover for integration and
verification will be with the contractor. The contractor responsible for
test setups, special GSE cable fabrication, troubleshooting, and
experiment operations.

**12.1.3.13.3 Experiment Verification** - The contractor will be
responsible for control of the flight experiment hardware during the
verification process at JSC. The contractor shall provide experienced
field test engineers, technicians, and documentation personnel to
support this verification process. The verification process will consist
primarily of performing tests and measurements that assure all the data,
power, video, mechanical, and thermal interfaces are in accord with the
requirements of the PMM. The tests and measurements which are made will
be documented and shall have independent quality inspection of all data.
Not later than the beginning of the verification process, the,
contractor shall have automated all data related to the verification
process in order to promptly provide the current status of all testing
to be performed, all testing that has been completed, and the reference
document that shows the test results.

**12.1.3.13.4 Science Verification Test** - The experiment science
verification test is designed to verify end-to-end experiment
operations. The test is performed as a part of the payload verification
test sequence and requires the use of the appropriate test specimen,
experiment hardware/data display, and data analysis methods. In essence,
the test consists of a nominal experiment operations sequence with
sufficient data acquired to allow both analysis and evaluation of the
performance of the experiment system. Thus, the specific test parameters
and requirements are unique to each experiment. The final judge of
system performance is the individual investigator or his/her designated
representative.

In order to exercise all aspects experiment operation and to assure
flight readiness, the investigator is required to process the
verification test data. This processing utilizes all nominal data
analytical procedures and results in a formal report containing the
analyzed data as well as a statement certifying the adequacy of that
data in fulfilling the scientific requirements of the experiment.

The contractor shall be responsible for the planning and conduct of this
test activity. Such support may include, but is not limited to, test
plans, schedules, procedures, facility support, data system support,
experiment hardware support, and the operation of the flight hardware
during the tests.

**12.1.3.13.5 Total Project Payload Verification** - The contractor
shall be responsible for the testing of all the experiment systems
together as a project payload. This testing will have as its goal the
verification that various experiments can operate concurrently with the
flight vehicle subsystems without interference. Also, a total project
payload electromagnetic interference susceptibility test may be
required. This testing will primarily be performed within the payload
mockups with the experiments interfacing with HLS-provided data, power
and video simulation systems, as well as interfacing with the HLS
LSLE-supplied hardware.

**12.1.3.14 Operational Training** - The contractor shall be responsible
for the training of flight and ground crews for payloads, flight
hardware equipment and experiment operations, and for (1) proper conduct
of all scheduled experiment-related operations from prelaunch through
post landing, (2) obtaining desired scientific data from the
experiments, (3) obtaining increased data return in the event of
advantageous unforeseen opportunities, and (4) work-around experiment
contingencies.

**12.1.3.14.1 Flight Crew Training** - The contractor shall be
responsible for developing plans for supporting the development and
maintenance of a crew training program for the conduct of the
HLS-managed experiments. This plan shall include the results of analysis
of payload and equipment requirements to determine the crew tasks and
level of proficiency required to perform each task, the type of
equipment required to provide the specific training, and the utilization
of this equipment to satisfy the training needs.

This life sciences crew training program will include tentative
schedules for preflight activity, taking into account crew training
workloads, the efficient use of available resources, and crew
integration requirements and will become part of the overall mission
crew training plan. The contractor shall be responsible for coordinating
and conducting flight crew training related to HLS-managed experiments
to achieve optimum operational proficiency in accordance with the
training plans as developed under this section.

**12.1.3.14.2 Ground Crews and Support Personnel Training and Mission
Integrated Training/Simulations (MIT/Ss), Joint Integrated
Training/Simulations (JITSs), and Other Simulations Support** - The
contractor shall be responsible for the implementation of the training
plan for each of the payloads to assure that personnel employed in the
inspection, handling, installing, testing, integration, operations,
maintenance, and launch activities of all related hardware and software
at JSC, KSC, and alternate/contingency landing sites have been trained
adequately and are qualified to perform their tasks competently. The
contractor shall also support other NASA organizations as required and
may be called upon to act as a team member with them in the conduct of
total crew training.

The contractor shall be responsible for providing the training and
documentation necessary for mission support personnel utilizing the SMA
and other HLS mission support facilities. The contractor shall identify
SMA tasks and positions and plan and conduct training for all console
operators including PI teams. Training will be initiated before the
start of MIT/S activities and continue through JITS with the POCC. The
contractor shall coordinate the planning, staffing, and operation of the
SMA for flight operations. During the flight, the contractor shall
provide daily activity summary reports.

**12.1.3.14.3 Training Certification** - The contractor shall be
responsible for training to achieve operational proficiency sufficient
for certification of operating personnel. The contractor shall be
responsible for the testing and/or certification of personnel in both
flight and ground activities.

\*\*\*From Schedule B, Part 1, 9.0 Mission Operations Support:

**12.1.3.15 Mission Operations Support** - The SMA and associated
operations support area function as a real-time monitoring area for
experiments during assembly, test, and training on life sciences
experiments and also supports the POCC during flight. The rooms contain
consoles for PIs, SMA support staff, and HLS management personnel. The
SMA contains television (TV) and intercom systems and devices for
display of data on strip charts, digital TV readouts, and graphics TV
presentation as well as work tables for flight planning and other
cities.

**12.1.3.15.1 Science Monitoring Area and Payload Operations Control
Center Operations\
Support** - The contractor shall be responsible for configuring the SMA
facility and SMA operations systems (data, flow chart recorder,
intercom, digital TV equipment, and video) to meet the mission-unique
ground support requirements and experiment/investigator data product
requirements. The contractor shall be responsible for verifying
configuration and function of the SMA and SMA systems and coordinating
maintenance.

The contractor shall be responsible for preparing an SMA configuration
document, an SMA verification plan, and an SMA operational support plan.
The contractor shall be responsible for operationally supporting the
POCC and SMA in accordance with the approved POCC and SMA operational
support plan. This plan will include, but not be limited to, the
following activities:

-   Contractor personnel certification (described under training)

-   Manpower assignments of qualified personnel for one to three shifts
    per day for a 1 to 30-day-period per mission

-   Procedures, checklists, and cue cards preparation

-   Communication and display information development

-   Mission monitoring (both science and engineering)

-   Anomaly identification, analysis, and resolution

-   Integrated check-out (simulations) monitoring

-   Preparation and distribution of data products

**12.1.3.15.2 Project Payload Performance Analysis and Reports** - The
contractor shall be responsible for monitoring the performance of
HLS-managed flight experiments, the related LSLE and other supporting
equipment. The contractor shall also gather any other information
available indicating hardware performance. From the accumulation of
these data, the contractor shall develop hardware performance and
experiment results analysis. The contractor will also perform the same
analysis and evaluation on groups of experiments, if appropriate, or on
the entire project payload as a system.

These evaluation results with appropriate recommendations will be
incorporated into a mission report. The contractor will be responsible
for this report and may be called upon to combine multiple mission
evaluations into a life sciences project evaluation report.

**12.1.3.15.3 Principal Investigator Support** - The contractor shall be
responsible for interfacing of visiting PIs with NASA and other agencies
including other contractors to NASA. This will require management
control of facilities, loan of equipment, assignment of priorities,
sharing of resources, and allocation of facilities.

12.1.4 Research and Development Support

12.1.4.1 Advanced Development

\*\*\*From Schedule A, NIO, 9.1.4.1.1:

**12.1.4.1.1 Human Space Transportation and Human Planet Surface Systems
-** This function is responsible for the definition and focus of new
projects which involve human access to and activities in space. The
following are representative tasks the contractor shall perform:

12.1.4.1.1.1 Support definition of human space transportation, including
advanced transportation requirements to low Earth orbit and for Moon and
Mars exploration. Synthesize data on the NASA requirements to transport
humans to and from Earth orbit. These efforts include management of a
Personnel Launch System, launch escape systems, human transfer vehicles,
lunar landers, and human ascent vehicles.

12.1.4.1.1.2 Support definition of human surface systems projects for
the Moon and Mars with a focus on requirements and suitable design-for
the integrated hardware needed to live and work productively on the
lunar or Martian surface. Areas of effort shall include Extravehicular
Activity (EVA) systems, habitation systems, surface transportation,
lander support, and resource utilization. Current work is termed the
First Lunar Outpost, the first human return to the Moon, with a crew of
four for 45 days.

12.1.4.1.1.3 Support definition of precursor missions to human
exploration of the Moon and Mars so that the future human job can be
made safer and easier. Support Project Artemis, a precursor mission to
the lunar surface in support of First Lunar Outpost. This includes
management and technical support to the design, development,
construction, and testing of the Common Lunar Lander (CLL) as well as
management support to an effort to offer JSC unique payloads for Project
Artemis. Assessments shall be provided to senior management to support
future mission planning.

**12.1.4.1.1.4 Systems Definition** - This area involves the definition
of systems required to support human transportation systems and human
bases off the Earth.

12.1.4.1.1.4.1 Provide support for requirements definition and design of
elements of human transportation systems and human lunar and planetary
bases; provide development and implementation of systems sizing and
weight estimation algorithms; assist in the performance assessment of
various concepts; provide recommended concepts to NASA; and update
models and algorithms to insure state-of-the-art capability.

12.1.4.1.1.4.2 Support the definition of mission operations and
servicing requirements for the human transportation and surface
activities; and assist in the definition of systems which minimize labor
intensive operations.

12.1.4.1.1.4.3 Identify, develop, refine, and maintain characteristics
and requirements for human transportation and surface systems and
associated elements; maintain descriptions of elements and systems in an
appropriate data base or catalog. The level of detail on each conceptual
definition of an element shall include estimates of physical dimensions,
mass, power, operational and support requirements, logistics and
resupply requirements, and other information pertinent to applying the
element to a scenario; and element descriptions with appropriate
parametrics as well as specific designs.

12.1.4.1.1.4.4 Support the definitions analysis, and maintenance of
requirements and approaches to human space operations; produce and
maintain the human transportation and surface systems requirements
document which will be the collector of these requirements and consider
aspects of operations with particular focus in the areas of exploration,
construction, transportation, and resource utilization; identify
appropriate techniques, required equipment, and crew support
requirements; investigate the potential role of automation and robotics,
human machine interfaces, and high leverage items for crew involvement;
document results including work breakdowns and equipment definitions in
sufficient detail for use in case study synthesis; and supported with
modeling and simulation.

**12.1.4.1.2 Space Servicing Systems** - This function provides the
focus for space servicing advanced development activities in the SPM
conducting studies, performing analysis, and performing technical and
programmatic "quick looks" which support the development of decision
packages for new program development. Also, development of a concept for
low- cost flight demonstration of autonomous rendezvous and capture and
automated fluid transfer between orbiting spacecraft. Also, development
of interface standards for space assembly and servicing. This involves
developing, proposing, and supporting spacecraft interface standards,
test procedures, guidelines, and recommended practices within the
sanctions of selected professional standards organizations. The goal is
to create American National Standard Institute (ANSI) standards for
spacecraft interfaces. The following are representative tasks the
contractor shall perform:

**12.1.4.1.2.1 Program Development** - This area consists of project
management and technical support in the definition, development and
integration of space-related projects.

12.1.4.1.2.1.1 Support planning, organizing, leading, and coordinating
JSC activities required to support specific advanced project
initiatives.

12.1.4.1.2.1.2 Support project reviews and meetings, including design
and technical interchange meetings, develop, and provide presentation
materials; provide special presentations; and develop data
documentation, such as status reports, hardware and software catalogs,
meeting minutes, and action items.

12.1.4.1.2.1.3 Support problem areas identification; evaluate alternate
solutions; and prepare recommendations and impact assessments as they
relate to designated study areas.

**12.1.4.1.2.2 Space Assembly and Servicing** - This area provides
specific engineering evaluations, technical critiques analysis,
management support, and reporting with respect to space assembly and
servicing.

12.1.4.1.2.2.1 Participate in and support NASA Space Assembly and
Servicing Working Group (SASWG) meetings, assist in preparation of
presentations; support liaison activities; execute planning functions
for coordination of designated participants or support elements; and
provide provisioning for logistical support.

12.1.4.1.2.2.2 Participate in and support SASWG Interface Standards
Committee (ISC); identify and document the key issues for
standardization at the ISC working sessions and teleconferences;
organize ISC standards panels, ISC meetings and telecons for the ISC
standards preparation panels; initiate documents prioritized by the
SASWG and draft the highest priority documents for submission to
professional standards organizations; and present and document the
status of ISC meetings telecons at each ISC meeting.

12.1.4.1.2.2.3 Research spacecraft interface hardware to determine the
ISC prioritized list of candidates hardware interfaces; and review the
development and revision of interface standards documents with the
appropriate interface standards review panels.

12.1.4.1.2.2.4 Present proposed standards documents at working sessions
of appropriate profession organizations (SAE, AIAA, and EIA); review
documents; support these organizations to ensure space performance
requirements are met; provide tutorial presentations; provide technical
presentations to spacecraft suppliers, and participate in one technical
conference per year; and actively participate in the American Institute
of Aeronautics and Astronautics Serviceable Spacecraft Committee on
Standards (SSCOS) and provide technical consultation at their regular
meetings.

12.1.4.1.2.2.5 Prepare and/or acquire supporting documentation and
source material; prepare and maintain a data base pertinent to support
requirements definition and planning task; and maintain cognizance of
the state-of-the-art of spacecraft interface hardware and robotics
components and systems in support of the data base.

12.1.4.1.2.2.6 Establish the value of existing tools and equipment used
on previous EVA and the suitability of these tools and equipment for
adaptation to robotic servicing; and refine designs of spacecraft
interface hardware, serviceable hardware, and servicing equipment as
required to achieve EVA/robotic compatibility.

12.1.4.1.2.2.7 Prepare and maintain computer aided design (CAD)
replications of spacecraft interface hardware, serviceable hardware, and
servicing equipment and apply the design information to standardization
activities of the ISC and SSCOS; and develop and maintain the SASWG
CAD/Computer Aided Visual (CAD/CAV) data base and a NASA data base for
proposed standards documents in preparation.

\*\*\*From Schedule B, Part 1, 4.0:

**12.1.4.2 Flight Hardware/Software Engineering and Provisioning** - The
contractor shall define, design, fabricate, test, integrate, and
maintain HLS flight and GSE systems. These systems include experiment
systems (e.g., LSLE, EUE, and GSE) and integration hardware, including
mounting slides and stowage containers. In the content of this SOW,
reference to "hardware" implies the inclusion of related software.

\*\*\*From Schedule B, Part 1, 4.2 Project Engineering Support:

**12.1.4.2.1 Project Engineering Support** - The contractor shall
provide project engineering and management for all HLS flight and ground
hardware, including hardware definition, hardware development and
modification (where required), and maintenance.

Project engineers (PEs) shall provide design assistance HLS and furnish
technical information to other contractors or PIs. The PEs shall assure
that all experiment requirements are met and that all hardware meets
program guidelines.

PEs shall monitor the development and fabrication of flight hardware for
technical compliance and shall make recommendations thereon.
Specifically, the contractor shall:

a.  Review documentation prepared by hardware/experiment developers and
    make recommendations

b.  Review EISs and other documents for compatibility with program
    requirements

c.  Perform or provide technical assistance to all experiment reviews;
    review and analyze contractor documents, schedules, and hardware

d\. Perform reviews of experiment interface documentation and provide
recommendations

e\. Troubleshoot and resolve experiment hardware problems, failures,
etc.

PEs shall prepare and support the preparation of all necessary documents
including but not limited to those specified in section 3.2.1.4 and the
following:

a.  Technical reports, as required

b.  Activity reports

c.  Project activity and milestone schedules

d.  Hardware development plans (HDPs)

e.  Statements of work for hardware development or modification

During hardware development, contractor PEs assigned to HLS flight
hardware shall :

-   Review proposed designs for ability to meet performance,
    scientific,\
    compatibility, safety, reliability, quality, and other requirements
    of HLS flight hardware

-   Provide technical data and information to hardware developers and
    potential users

-   Assess technical progress; assure that the delivered hardware works;
    is on time and within budget; take corrective actions required

-   Propose/evaluate design changes and review delivered documents, make
    recommendations and assure that all program requirements are met

-   Prepare and perform hardware design reviews and assure that review
    preparation is adequate

-   Assure that instrument interfaces are correct and clearly defined

-   Present proposed changes to the baseline configuration to the HLS
    CCB

-   Participate in acceptance/functional testing of flight hardware and
    experiment systems

-   Perform analyses and tests to assure that hardware meets
    design/interface requirements and all performance objectives

    Following delivery, contractor PEs assigned to HLS flight hardware
    shall :

-   Provide technical data and engineering support to any experiment
    that will use the instrument, support EMs in system design and in
    preparing ICDs.

-   Assure timely close-out of all open paperwork.

-   Plan, write procedures for, conduct, and document frequent
    functional tests to assure that the hardware continues to perform.

-   Support crew training and hardware refurbishment.

    \*\*\*From Schedule B, Part 1, 4.2.1:

    **12.1.4.2.1.1 Hardware Requirements Definition** - The contractor,
    shall support flight hardware requirements definition. During
    definition, the contractor shall review science requirements, survey
    the market, evaluate commercial candidates, and provide a
    recommendations on whether to flight qualify a commercial device or
    to begin a new development. Requirements definition shall consider
    but not be limited to:

-   Intended use

-   Performance

-   Weight

-   Volume

-   Power

-   Interface requirements

-   Reliability

-   Maintainability

-   Operational concerns

-   Safety

    \*\*\*From Schedule B, Part 1, 4.2.3:

    **12.1.4.2.1.2 Hardware Specification Development** - The contractor
    shall develop specifications (e.g., EISs; Specification/Assembly
    Drawings \[S/ADs\]) for flight hardware. A specification typically
    includes, but is not limited to:

-   Introduction

-   Applicable documents

-   Hardware requirements

```{=html}
<!-- -->
```
-   Performance requirements

-   Technical requirements

-   Safety requirements

-   Reliability requirements

-   Quality assurance requirements

-   Materials requirements

-   Configuration management requirements

```{=html}
<!-- -->
```
-   Documentation requirements

    \*\*\*From Schedule B, Part 1, 4.4.1:

    **12.1.4.2.1.3 Flight Data Systems** - The contractor shall program
    flight data systems for HLS experiments and shall perform hardware
    and software testing, maintenance, and operation of flight data
    systems. The contractor shall document and verify the interfaces
    between flight data systems and the vehicle.

    \*\*\*From Schedule B, Part 1, 4.4.3:

    **12.1.4.2.1.3.1 Flight Data Systems Interface** - The contractor
    shall document the interface between experiment and vehicle data
    systems and shall verify that all electrical, mechanical, and data
    format requirements are met.

    \*\*\*From Schedule B, Part 1, 4.7, except 4.7.6 which went to NEW
    SOW Part II, Management & Administration:

    **12.1.4.2.2 Payload Project Management** - For each set of
    experiments assigned to a mission there will be a Payload Project
    Manager (PPM) assigned to provide representation of HLS to the
    Payload Mission Manager (PMM) during negotiations for vehicle
    requirements and documentation submittal. The PPM is responsible for
    meeting the mission milestones and developing the implementation
    plans for support of each mission. The PPM is also responsible for
    resource allocations to each experiment and the payload complement.
    The contractor will support the PPM as defined in the following
    paragraphs.

    **12.1.4.2.2.1 Payload Feasibility** - The contractor shall be
    responsible for determining the feasibility of various project
    payload configurations during the experiment selection process by
    NASA. Contractor engineers shall be familiar with the experiment to
    vehicle interface requirements and restrictions. This includes
    mechanical, electrical, data, video, and thermal limitations of the
    vehicle. The contractor will be provided a selection of potential
    experiments and hardware for a payload under consideration. The
    contractor will subsequently evaluate the reasonable configurations
    of the experiments in the racks and report this information,
    together with the evaluation of thermal and power resource
    distribution, to HLS with specific recommendations.

    In order to perform accurate feasibility payload studies with quick
    response changes, the contractor shall be capable of performing
    these studies using an existing three-dimensional computer-aided
    design (CAD)/computer-aided engineering system.

    **12.1.4.2.2.2 Support for Payload Project Management** - The
    contractor will provide support to, and represent as requested, the
    JSC PPMs assigned to payloads containing experiments developed and
    managed by the HLS. The contractor will work with the PPMs to
    identify task required to support mission milestones and distribute
    tasks and need dates to contractor personnel supporting the mission.
    The contractor will track the progress of the activities and provide
    the PPM with a current status information. The contractor should
    also identify problem areas associated with task completion and
    assist in the resolution of these problems where appropriate.

    **12.1.4.2.2.2.1 Inter-Organizational Liaison** - The contractor
    will perform the necessary coordination to provide the PPMs with an
    inter-organizational liaison to the contractor organization. The
    contractor will collect and collate data required to support mission
    milestones and requirements, identify and analyze the tasks needed
    to obtain these data, and distribute this information to the
    inter-organizational elements. This support will also include the
    generation of schedules to support mission milestones and tasks and
    the development and maintenance of status reports and task lists.

    **12.1.4.2.2.2.2 Resource Allocation** - The contractor shall
    provide engineering personnel to the PPM who will be responsible for
    the accumulation of the payload project resource requirements from
    all HLS experiment hardware that will be flown on each mission. The
    payload resources that are to be documented, updated, and analyzed
    include experiment power consumption, power profile de-experiment
    cooling requirements, vacuum venting requirements, mass and
    center-of-gravity data, stowage space needs, and crew timeline
    requirements. Maintenance of these data in an automated format
    accessible to HLS and contractor personnel is required.

    **12.1.4.2.2.2.3 Payload Status** - Since the PPM is the interface
    for HLS to the PMM, the status for all activities supporting a
    mission is required by the PPM. The contractor will track the status
    of action items and identified tasks, including the areas of
    verification submittals, verification testing, safety hazard reports
    and closures, certification testing, certification review sheet
    completion, materials certification, waiver/deviation status,
    hardware shipments, and KSC testing. This shall include a detailed
    status for all requirements levied on each item of hardware to be
    flown on a mission.

    **12.1.4.2.2.3 Project Payload Definition** - Once a set of
    experiments has been selected by NASA as a result of the feasibility
    studies, the contractor will start the process of defining the
    project payload in terms of specific locations within the flight
    vehicle rack structures. The contractor will also compile the best
    available set of resource requirements from the experiment
    development teams. This will include estimated power requirements,
    maximum weights and center-of-gravity information, and unique
    interface needs. The information derived from this payload
    definition effort will be provided to the HLS PPM as a basis for
    development of payload configuration agreements between the HLS PPM
    and the PMM. The contractor will be responsible for assisting the
    HLS PPM in the negotiations of these agreements with the PMM.

    **12.1.4.2.2.4 Mission Reviews and Presentations** - The contractor
    will support PPM presentations and meetings by preparing
    presentation material, presenting the material when required, and
    developing an action item list/minutes for each review/meeting as
    appropriate. The contractor will assure that the appropriate
    contractor personnel are notified to support the necessary
    presentations and meetings. The contractor will distribute
    information received at meetings and the minutes of the meetings to
    contractor and HLS personnel.

    **12.1.4.2.2.5 Mission Support to the Payload Project Manager** -
    The contractor will man console positions in support of the PPMs
    during mission level simulations and during flight. This includes
    obtaining the appropriate training courses as required by the
    payload or mission organizations.

    **12.1.4.2.2.6 Documentation Reviews** - During the development of a
    payload complement to be flown, there are various organizations that
    prepare documentation which includes experiment resources and
    requirements applicable to the experiments developed by HLS. The
    contractor will review these documents to assure that the experiment
    requirements have been interpreted correctly by outside
    organizations. Included are the following representative documents
    prepared by external organizations: PIP Annexes, Ground Integration
    Requirements Document, Operations and Maintenance Requirements and
    Specifications Document (OMRSD), Test and Checkout Procedures and
    Operations and Maintenance Instructions (OMI).

    Preparation for experiments to be flown on space station will also
    require contractor review of the implementation documentation
    prepared by outside organizations.

    The contractor will review this documentation and prepare
    comments/recommendations to appropriate personnel.

    \*\*\*From Schedule B, Part 1, 4.10 Stowage Management:

    **12.1.4.2.3 Stowage Management** - The contractor shall be
    responsible for managing the stowage requirements of all
    experiments. The contractor shall review the loose equipment that is
    identified by the experimenter which will require stowage for launch
    and, while considering the order of usage and the crew accessibility
    needs, will develop a stowage configuration that proposes the
    specific locations of all loose equipment. This configuration will
    be documented with layout drawings and a stowage list. This stowage
    document will require many updates and revisions as the experiments
    mature. The stowage requirements must be satisfied within the
    constraints of the available space allocation that has been provided
    to HLS on each payload. The contractor personnel responsible for
    stowage requirements must coordinate with the HLS and contractor
    personnel to assure that the optimum stowage container or stowage
    drawer configuration is utilized.

    As the stowage layout is finalized, the contractor will be
    responsible for the coordination of the development of drawings that
    show the positioning of the hardware in the stowage foam. The
    contractor will also be responsible for the coordination and
    scheduling of the cutting of the flight and training foam cushions.
    If required, the contractor will be responsible for developing a
    mechanism for having the cutting of the foam cushions accomplished
    by other NASA/contractor organizations.

    \*\*\*From Schedule B, Part 1, 11.0:

    **12.1.4.3 Advanced Technology Development (ATD)** - The contractor
    shall be responsible for the ATD activity which is an advanced
    planning and development process that identifies and evaluates new
    technology tray be used in future flight or ground systems. This
    process is directed by the ATD project review board (PRB), which is
    composed of the HLS chief and the branch chiefs. Project proposals
    are submitted to the PRB for review and allocation of resources. ATD
    project teams shall perform the following type of activities:

-   Technology surveys

-   Trade studies

-   Procurement

-   Prototype design

-   Rapid prototyping

-   Prototype evaluation

-   Prototype documentation package development

    **12.1.4.3.1 Advanced Technology Development Project Review Board
    Activities** - The ATD PRB meets monthly to review project proposals
    and status. The contractor shall be responsible for supporting these
    reviews as follows:

    Administrative

-   Receive and organize project proposals

-   Publish and circulate PRB agenda

-   Provide secretary and record minutes of the PRB

-   Circulate minutes of the PRB and track action items, project
    budgets, and schedules

    Technical

-   Status reviews and project proposal presentations

    **12.1.4.3.2 Advanced Technology Development Project Teams** -
    Engineering, technician, and administrative support for ATD projects
    will be determined by the ATD PRB. The contractor shall have the
    following responsibilities:

-   Technology Survey

```{=html}
<!-- -->
```
-   Review technical literature and commercial manufacturers to
    determine the current state of the art for the technology being
    evaluated.

-   Contact the technical experts and get status updates on the
    technology.

```{=html}
<!-- -->
```
-   Trade Survey

```{=html}
<!-- -->
```
-   Establish evaluation criteria for the technology based on HLS
    requirements.

-   Evaluate technology options against these criteria.

```{=html}
<!-- -->
```
-   Hardware/Software (System) Procurement

```{=html}
<!-- -->
```
-   Procure commercial off-the-shelf (COTS) equipment (if available) or
    developmental prototypes, including software (if required), to use
    in characterization of the technology.

```{=html}
<!-- -->
```
-   System Modification Rapid Prototyping

```{=html}
<!-- -->
```
-   Modify COTS system to meet HLS requirements and prototype a HLS
    configured system for evaluation and characterization testing.

```{=html}
<!-- -->
```
-   Prototype Evaluation

```{=html}
<!-- -->
```
-   Test the prototype to determine the performance characteristics of
    the chosen technology.

```{=html}
<!-- -->
```
-   Document Prototype

```{=html}
<!-- -->
```
-   Produce design documentation (schematics, mechanical drawings,
    assembly drawings, software listings, flow charts, operators
    manuals, technical manuals, etc.) for the prototype system.

-   Itemize hardware and labor costs required for development of the
    prototype system.

-   Document the schedule used to develop the prototype.

-   Publish the performance specifications for the prototype.

    12.2 LABORATORY/FACILITY SUPPORT SERVICES

    12.2.1 General Support Services

    This function supports the laboratories including the Experiment
    Development Laboratory, Model Development Laboratory, and Payload
    Integration Laboratory. The following are representative tasks the
    contractor shall perform:

    \*\*\*From Schedule B, Part 1, 10.1.1

    **12.2.1.1 Planning and Analysis** - It shall be the contractor's
    responsibility to accumulate detailed requirements, conduct
    analyses, and develop the rationale necessary to support HLS in the
    design and implementation of special test and checkout facilities at
    JSC and other specialized facilities as required to support the HLS
    contract elements. These requirements shall be based upon existing
    project support as well as plans for future projects; e.g., space
    station.

    12.2.1.2 Manage and maintain the laboratories to fulfill the mission
    of each facility. This effort shall include conducting
    investigations and studies to upgrade the laboratory's capabilities
    and the procurement of new equipment to replace worn/obsolete items;
    maintaining all tools, gages, and test equipment in clean and
    calibrated working order; and documentation of laboratory
    activities, including failure logs, inventory statuses operating
    procedures, and facility configuration.

    12.2.1.3 Use computer-aided techniques for design and computer data
    bases for inventory whenever practical.

    12.2.1.4 Maintain laboratory capability to support the activities
    related to flight hardware, cleanliness standards, procedures,
    security, and quality oversight.

    12.2.2 Federal Information Processing Resources Support

    **12.2.2.1 Computer Support** - This function supports the FlPR
    requirements of selected tasks of the SPM. The primary
    responsibilities of computer support include data processing and
    analysis, customized FIPR hardware interface design and development,
    customized software design and development, automation support, and
    the projection of future FlPR requirements. Support engineering
    development and analysis tasks including data base system design and
    support, advanced studies, data reduction, project management and
    automation applications design and development. The following are
    representative tasks the contractor shall perform:

    12.2.2.1.1 Provide systems and operations support for the computer
    systems and peripheral hardware. This effort shall include
    maintaining tape and hardware/software documentation libraries,
    developing documentation for computer systems and laboratory
    operating procedures, screening and installing operating system and
    application software, providing laboratory engineering evaluation
    studies, performing computer systems networking support, receiving
    and shipping user data products, and maintaining an equipment
    tracking system.

    12.2.2.1.2 Provide hardware support in the following areas:
    troubleshooting, inspection, and repair of all Computer Facility
    computer systems, peripheral hardware, and user workstations which
    include terminals, CAD workstations, graphics terminals and
    workstations, and personal computers; cable fabrication and routing
    for remote terminals and other peripherals; network design,
    development maintenance and management support; and design,
    development, installation, and maintenance of special purpose
    computer interfaces.

    12.2.2.1.3 Provide hardware and software maintenance for Computer
    Facility FlPR not under warranty or covered under vendor maintenance
    contracts. This effort shall include documenting all changes,
    upgrades, and enhancements to the hardware and software, maintain
    adequate parts and supplies to support routine operations and
    maintenance, both preventive and remedial, on all FlPR not covered
    under vendor maintenance.

    12.2.2.1.4 Provide general computer systems support in the areas of
    software development and maintenance of existing and planned
    engineering software and hardware systems and Computer Aided
    Engineering (CAE) hardware and software systems; and provide support
    for activities such as applications and operating systems software
    development, vendor software installation and maintenance and
    operational support, consultation, user training, and the
    maintenance and operational support of data bases and analysis
    software systems.

    \*\*\*From Schedule A, 9.2.3

    12.2.3 Special Purpose Laboratories

    The following are representative tasks the contractor shall perform:

    **12.2.3.1 Experiment Development Laboratory** - Provide a general
    purpose experiment integration laboratory including a dedicated area
    for the fabrication, assembly, and test of experiment projects that
    are to be flown on the Space Shuttle, space station, or other
    platforms.

    **12.2.3.2 Model Development Laboratory** - Provide a facility for
    the development of high fidelity, sub-scale models of experiments,
    payloads, and related space vehicles, containing special tools,
    devices, and an enclosed painting facility which are required to
    design and build these models. The models are used for presentations
    and analysis where complex devices must be accurately described to
    persons from a variety of disciplines.

    **12.2.3.3 Payload Integration Laboratory** - Provide a facility to
    perform standard test instrumentation for the assembly and testing
    of small and medium sized payloads that will be flown aboard the
    Space Shuttle, space station, or other platforms, containing
    equipment such as scaffolds and cranes required to service heavy
    and/or large structures as dictated by JSC/OSHA standards in the
    range greater than 50 pounds, including a class 100,000 clean work
    area with a special lighting system that meets the requirements of
    SNC-0005 for highly sensitive clean payloads.

    \*\*\*From Schedule B, Part 1, 4.4.2:

    **12.2.3.4 Microcomputer Laboratory** - The contractor shall furnish
    the necessary skilled personnel and materials to maintain a
    microcomputer laboratory which shall:

```{=html}
<!-- -->
```
-   Write utility programs and routines for the LSLE microcomputer and
    the LSLE microcomputer-2, a new development that will eventually
    replace the old microcomputer

-   Write programs to test LSLE microcomputers

-   Write experiment software as required

-   Act as a consultant to experiment developers who use the LSLE
    microcomputers

-   Configure flight LSLE microcomputers to experiment requirements,
    prepare configuration documentation, and install software. The
    contractor shall test' and certify that the experiment
    microcomputers are flight ready

-   Maintain LSLE microcomputers and ground-use software development
    systems. The contractor shall troubleshoot and repair LSLE
    microcomputers as required.

\*\*\*From Schedule B, Part 1, 10.0 & 10.1:

12.2.4 Facility/Ground, Systems Engineering, and Operations

**12.2.4.1 Operations Support Facility Development** - The contractor
shall be responsible for the development and operational support of the
HLS facilities. These facilities shall support all activities as defined
in Part 1 of the SOW. The contractor shall be responsible for developing
an overall facility development and implementation plan which will
describe the total process of developing, implementing, and dining the
basic support facility. The plan shall address existing and future
requirements, proposed proud new facility concepts and designs, and
shall describe each functional area within the facility.

\*\*\*From Schedule B, Part 1, 10.1.2:

**12.2.4.1.1 Design, Monitoring and Certification of Facilities** - The
contractor shall be responsible for the design and implementation of
special facilities as required to support the HLS project as defined in
Part 1 of the SOW. This shall include test laboratories, computer areas,
SMAs, logistics support areas, etc.

The contractor shall be responsible for monitoring the construction,
alteration, and development of these facilities to assure timely
completion and that the facility is built in accordance with established
project requirements.

The contractor shall be responsible for the development of criteria
necessary to accommodate a proper certification of facility readiness
and shall participate in the demonstration of this readiness.

\*\*\*From Schedule B, Part 1, 10.1.3

**12.2.4.1.2 Buildings 36, 56, and 266 Facility Buildup** - The
contractor shall be responsible for the reconfiguration of the building
36, 56, and 266 facilities and provide working laboratories in support
of future projects, experiment development, fabrication and assembly
work, test and verification, science monitoring, and computer systems.
The contractor shall be responsible for maintaining and operating these
areas and shall be responsible for their configuration control.
Specifically, the contractor shall be responsible for performing the
following activities:

a.  Review for accuracy, provide update for, and maintain a complete set
    of as-built facility structure and utility drawings. (Drawings will
    be provided by the JSC Center Operations Directorate).

b.  Develop/document detailed room layouts for configuring each of the
    rooms. This effort requires coordination between several different
    elements within HLS which have responsibility over different areas.

c.  Identify, label, and maintain correct identification of all
    utilities available within each room.

d.  Identify, establish, document, and implement interfaces with other
    NASA center elements as to respective maintenance and operations
    (M&O) responsibilities and implement a method to assure that any
    required M&O is regularly scheduled and performed to maintain
    uninterrupted operations.

e.  Implement and maintain an adequate documentation control system for
    the total test facility to assure configuration control and
    establish a method of change request documentation and
    implementation.

f.  In conjunction with the STI Center, maintain documentation relative
    to facility lab area activities, i.e., procedures, equipment
    manuals, vendor supply catalogs, etc.

\*\*\*From Schedule B, Part 1, 10.2:

**12.2.4.2 Ground Support Equipment, Test Equipment, and Spares** - The
contractor shall be responsible for the development, implementation and
operation of new GSE and test equipment, provide spares, and provide for
M&O of existing GSE and test equipment. This task shall include the
following:

a.  Providing new GSE, test equipment, and spares provisioning which may
    be developed by/through the contractor, procured and modified
    through the contractor, procured through the contractor without
    modification or provided to the contractor as GFE.

b.  Define/compile and document specific GSE and test equipment
    requirements to support facility operations, existing and future
    test and check-out operations, and existing and future operational
    support.

c.  Perform activities such as design (preliminary and detailed),
    structural, mechanical, thermal, environmental,
    electrical/electronics systems analyses, procurement, fabrication,
    installation, check out, acceptance test, documentation (drawings
    and procedures), and M&O.

d.  Establish and implement a routine maintenance and periodic checkout
    plan for all GSE and test equipment to assure that it remains in a
    ready state, within repair and calibration where required, and ready
    to support any activities when needed.

e.  The contractor shall be responsible for maintenance of GSE,
    including but not limited to, the simulated remote acquisition unit,
    the simulated high rate demultiplexer, the high rate demultiplexer
    interface; the simulated user time clock, and the cassette data tape
    recorder playback unit. This shall include a method of documenting
    problems as a check for design weakness, a system to track
    maintenance problems to assure their prompt correction, the
    maintenance of a spare parts inventory, the maintenance of
    configuration control, calibration and proof test status, and
    physical location of operational equipment.

f.  Provide trained operators for all GSE and test equipment.

g.  Prepare and maintain an updated inventory of existing and required
    test equipment and instrumentation essential to the proper function
    of all laboratories.

h.  Provide procurement documentation and procure additional test
    equipment and support hardware as required.

i.  In conjunction with the STI Center, maintain adequate documentation,
    i.e., procedures, drawings, manuals, etc., to maintain configuration
    control, and provide for operations and maintenance of all GSE and
    test equipment.

\*\*\*From Schedule B, Part 1, 10.3:

**12.2.4.3 Vehicle Mockup and Test Bed Development** - The contractor
shall be responsible for defining/compiling and documenting requirements
for flight vehicle mockups and test bed modules and their related
subsystems required by HLS to support present and future flight
programs. The contractor shall be responsible for the development of new
vehicle mockups and test bed modules and the modification of existing
vehicle mockups and shall provide for their M&O. This shall include the
following:

a.  Perform activities such as design (preliminary and detailed),
    structural, mechanical, thermal, environmental,
    electrical/electronic systems analysis, procurement, fabrication,
    installation and buildup, check out, acceptance test, documentation
    (drawings and procedures), and M&O.

b.  Establish and implement a routine maintenance and periodic checkout
    plan for all vehicle mockups, test beds, and ancillary support
    systems to assure they remain in a ready state, within repair and
    calibration where required, and ready to support any activities when
    needed. This shall include a method of documenting problems as a
    check for design weakness, a system to track maintenance problems to
    assure their prompt correction, the maintenance of a spare parts
    inventory, and the maintenance of configuration control on
    operational equipment.

c.  Provide trained personnel, equipment, documentation, and spare parts
    to maintain and operate the mockups and test beds.

d.  Provide experienced personnel to interface with other Center
    elements as related to space station and/or other future projects,
    to assure concepts and configurations are factored into test bed
    module design and implementation and to serve as technical
    representatives for life sciences to space station.

\*\*\*From Schedule B, Part 1, 10.4:

**12.2.4.4 Laboratory Management** - The contractor shall be responsible
for laboratory management to assure efficient, well planned and
supervised laboratory activities. This shall include the following:

a.  Interface with other division elements to identify proposed work and
    establish near-term and long-range planning, including establishment
    of specific priority ratings.

b.  Implement a work control system to assign work, clearly identify the
    task to be supported, and status the progress of work being
    performed. The work control system shall comply with the established
    plans, priorities, and schedules previously established, schedule
    resources to comply with the work identified, implement a mechanism
    to identify the impact when problems affect scheduled completion.

c.  Provide adequate technician support along with adequate technical
    and managerial supervision to assure efficient utilization of
    personnel.

d.  Provide basic laboratory management of all laboratories to assure
    proper utilization, operation, and maintenance and to assure
    compliance with well organized, clean, and sale laboratory practices

\*\*\*From Schedule B, Part 1, 10.5:

**12.2.4.5 Test and Fabrication Support** - The contractor shall be
responsible for the development and implementation of test requirements
definition, planning, schedules, procedures, test setups, test
evaluations, test reports and the planning for future payload systems
verification.

The contractor will be responsible for the design and development of
hardware for special experiment and instrumentation requirements. The
contractor technical personnel shall be NASA-certified for specific
skills such as soldering, crimping, wire wrap, etc. The type of work
experience required is in areas such as (1) flight cable fabrication and
testing, (2) flight printed circuit board assembly and repair, and (3)
flight circuit design and environmental testing and broad experience
with laboratory test equipment.

The contractor shall be responsible for light-to-moderate fabrication
activities in support of test operations, facility and equipment
maintenance, and repair/refurbishment of flight and nonflight hardware.

The contractor must interface with many supporting center elements to
establish test requirements, schedules, and priorities and support
resources.

\*\*\*For every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

12.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

12.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

13\. EARTH SCIENCE AND SOLAR SYSTEM EXPLORATION

\*\*\*From Schedule A, 11.0, SSED:

13.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

\*\*\*From Schedule A, 11.1.1, Solar System Exploration Division Support

13.1.1 Program Management Support

13.1.1.1 Shuttle - Unique

**13.1.1.1.1 Flight Science** - This function uses traditional manual
and visual techniques plus innovative, state-of-the-art electronic
image-analysis methods to evaluate images of Earth obtained by
astronauts, and images of Space Shuttle components obtained by
astronauts, on-board imaging systems, and by ground-based imaging
systems. The following are representative tasks the contractor shall
perform:

**13.1.1.1.1.1 Space Shuttle Earth Observations** - Provide Earth
science training to the Space Shuttle crews to enable them to better
observe and document the Earth from orbit; provide data bases, computer
software, and paper products to be carried on-board; and postflight
cataloging and archiving of the acquired photographs. Conduct postflight
analysis of selected data for technology development and Earth Science
research applications and provide assistance to educational and
scientific organizations in sorting through the 140,000-image Earth
observations data base. Provide focal point for Shuttle crews for Earth
observations real-time planning and remain in two-way communication
between orbiting observers and scientists/technicians on Earth.

**13.1.1.1.1.2 Space Shuttle Photo/TV Analysis** - Conduct digital and
photo-interpretative image analyses of photographs and television images
of launch, orbit, and landing phases for the purpose of identifying
flight safety issues; provide daily reports of the findings to the
Mission Evaluation Room and Level II during each mission; publish a
comprehensive summary of all findings within 30 days following each
landing; and support flight-safety reviews and Level II contingency
action plans.

13.1.1.2 Space Station - Unique

**13.1.1.2.1 Space Station Freedom (SSF) Earth observations** - Provide
support to SSF Earth observations and determine detailed requirements,
purchasing, and installing operational systems, and premission testing
of the subsystems.

**13.1.1.2.2 Space Station Photo/TV Analysis Project** - Provide rapid
and accurate analysis of photography, television, and other SSF on-board
imagery to support mission operations, engineering performance, and
anomaly assessment; develop requirements to extend present capabilities
to continuous operation during the construction and early operations
phases of SSF; acquisition of equipment; developing procedures, and
training personnel; and flight readiness reviews for early SSF
deployment.

13.1.2 Research and Development Summary

13.1.2.1 Advanced Development

**13.1.2.1.1 Experiment Development** - This function involves
developing new experimental techniques or modifying existing techniques.
It includes designing, fabricating, testing and utilizing new equipment
for analytical and laboratory investigations, field experiments, and
flight experiments. It also includes defining and documenting
requirements for integration of hardware onto balloon gondola, aircraft,
and space vehicles. Examples of instruments, and/or experiments are the
plasma motor generator experiment, aircraft cosmic dust collector,
Cosmic Dust Collection Facility for space station, Long Duration
Exposure Facility II, Thermal Analyzer for Planetary Surfaces, and
Backscatter Mossbauer Spectrometer. The following are representative
tasks the contractor shall perform:

13.1.2.1.1.1 Define requirements and specifications for hardware systems
of the experiment as well as test and ground support equipment.

13.1.2.1.1.2 Design both flight and test hardware; build breadboards;
prepare drawings; devise and write documentation for tests, operations,
and integration; and fabricate flight hardware.

13.1.2.1.1.3 Support operational phases of experiments, including the
acquisition and recording of data.

13.1.2.1.1.4 Support data reduction and analysis for experiments and
participate in preparation of results for publication.

13.1.2.1.1.5 Define and implement radar and optical experiments for both
laboratory and flight on such vehicles as Delta rockets and the Space
Shuttle Orbiter.

**13.1.2.1.2 Lunar and Mars Exploration Concept Development** - Tasks
are undertaken to help define future robotic and human missions to the
Moon and Mars and to help develop the technology in selected areas. The
following are representative tasks the contractor shall perform:

13.1.2.1.2.1 Support science mission planning, site evaluation, and site
selection for robotic lunar and Martian lander missions, as well as
early human missions to the Moon and Mars.

13.1.2.1.2.2 Survey requirements for science and technology for these
missions assemble data bases, prepare illustrations and reports, help
plan and manage works hops and other meetings, and provide logistic
support to science and resource utilization planning.

13.1.2.1.2.3 Design, fabricate, and operate experimental equipment and
test bed facilities needed to develop new technology for In Situ
Resource Utilization (ISRU) technology.

13.1.2.1.2.4 Perform data analysis of data from new robotic lunar and
Mars missions as they are flown, and provide reports, maps, and
illustrations to help with science and ISRU analysis and planning.

**13.1.2.2 Scientific Research** - This function requires support to
analytical and experimental research in disciplines of planetary and
space sciences. Programs to be supported include the following:
geological studies of early terrestrial crustal and atmosphere
evolution, lunar surface evolution, Mars weathering processes, origin of
meteorites and cosmic dust, elemental distribution coefficients, energy
expenditure studies of humans in space, space plasma physics, orbital
debris, digital image analysis, radar operations and data analysis, and
telescopic operations and data analysis. Some projects involve handling
radioactive samples and using instruments that produce ionizing
radiation. The following are representative tasks the contractor shall
perform:

13.1.2.2.1 Participate in all aspects of research from development of
the approach to publication of results; define research strategies;
develop experimental and analytical tools and procedures; execute
experiments; prepare samples for analysis; acquire and reduce data using
computer systems; analyze and interpret data; prepare oral and written
reports for internal and external publications; and contribute
scientific expertise to NASA educational programs. Some projects involve
handling radioactive samples and using instruments that produce ionizing
radiation.

13.1.2.2.2 Manage logistics for field operations; define data
requirements; collect and prepare samples for laboratory analysis,
collect data by chemical analysis, reduce and analyze data using
computer systems, interpret reduced data, develop mathematical models of
physical processes, prepare oral and written reports for internal as
well as external publication.

13.1.2.2.3 Contribute scientific expertise to NASA educational programs.

13.1.2.2.4 Perform analysis using experimental techniques including the
following: electron microscopy, electron microprobe analysis, neutron
activation analysis, X-ray diffraction, mass spectrometry, ultraviolet
absorption photometry, radar and optical data relative to orbital
debris, differential scanning calorirnetry, and infrared absorption
spectroscopy.

13.1.2.2.5 Conduct experiments using apparatus which includes
one-atmosphere gas mixing furnaces, internally heated pressure vessels,
externally heated pressure vessels, flat plate accelerators, light gas
guns, and vertical impact facility.

13.1.3 Engineering, Scientific, and Analytical Tools

The following are representative tasks the contractor shall perform:

13.1.3.1 Develop and use mathematical models to describe results of
measurements; identify key parameters and relationships; and develop and
maintain software models; develop and apply models of the orbital debris
environment; model radar and optical orbital debris sensors; and perform
mathematical analysis of the results from radar and optical measurements
of orbital debris.

13.1.4 Studies and Assessments

The following are representative tasks the contractor shall perform:

13.1.4.1 Engineering, Science, Technical, and Management Support

13.1.4.1.1 Support directorate levels, other internal directorate
elements, and specific approved outside requesting organizations.
Representative functions the contractor shall perform include technical
management studies, analytical studies, technical analysis, scientific
research and analysis, engineering investigations, systems
engineering/integration activities, technical fact finding, systems
development and implementation, and hardware/software systems
maintenance and operation.

13.1.4.1.2 Provide technical and administrative project management;
provide engineering, scientific, and technical support to prepare
documentation studies and briefing documentation; and coordinate,
assist, and participate in technical meetings related to technology and
projects to assure a continuous flow of technical information to the
professional and academic community.

13.2 LABORATORY/FAClLlTIES SUPPORT SERVICES

13.2.1 General Support Services

This function supports SSEDs laboratories/facilities including buildings
31, 31A, 261, 267, 268, and two labs in building 37. These laboratories
support research, engineering, and curatorial activities. The following
functions, common to all these laboratories and facilities, are
representative tasks the contractor shall perform:

13.2.1.1 Operate and maintain the liquid nitrogen tank farm which
provides liquid nitrogen for all laboratories, especially to the
curatorial laboratories for use in environmental cabinets; schedule
deliveries by the contracted vendor; and provide cryogenics support for
individual research laboratories.

13.2.2 Federal Information Processing Resources (FIPR) Support

The following are representative tasks the contractor shall perform:

13.2.2.1 Operate and support the computer facilities and associated
local area network including the general purpose and
laboratory-dedicated computers, file servers, network hardware,
individual workstations and all other computer-related data systems;
participate in the procurement, installation, and maintenance of new ADP
equipment and software, writing special purpose software, training
users, performing routine backups, maintaining tape libraries,
developing systems operation configurations, installing software and
upgrades of software, and diagnosing hardware and software problems; and
maintain all data bases relating to the configurations of the data
systems and associated hardware, including building wiring and
workstation hardware and software.

13.2.3 Planetary Materials Curatorial Laboratories

This function involves the curatorial responsibilities which are, in
most cases, extraordinary and unique tasks to maximize the safety and
purity of samples that represent national and international treasures.
This requires the adherence to established procedures and standards of
cleanliness and security. It also requires extensive record keeping and
reporting to outside advisory committees. The following is a list of
facilities now existing and requiring contractor support: Pristine Lunar
Sample Processing and Storage Laboratories, Returned Lunar Sample
Processing and Storage Laboratory, Sample Control and Data Center,
Curatorial Thin Section Laboratory, Meteorite Processing and Storage
Laboratory, Cosmic Dust Laboratory, and Facility for Optical Inspection
of Large Space-Exposed Surfaces (FOILS). Contractor support is also
required for the off-site Lunar Sample Remote Storage Facility at Brooks
Air Force Base (San Antonio, Texas) and the Curators Display located in
Space Center Houston (Houston, Texas - adjacent to NASA JSC). The
following are representative tasks the contractor shall perform:

13.2.3.1 Maintain inventories of ultra-clean controlled tools,
equipment, and containers; and perform maintenance on unique curatorial
tools and equipment and on stainless steel environmental cabinets used
for sample processing, and storage.

13.2.3.2 Operate and maintain all elements of the high purity nitrogen
system, including liquid nitrogen tank farm; and monitor systems for
analyzing oxygen and water content in environmental cabinets and vaults.

13.2.3.3 Develop and adhere to contamination control procedures; perform
maintenance and cleaning to comply with established standards of
cleanliness; and adhere to clean room protocol of ultra-clean Class-100
conditions in the Cosmic Dust Laboratory and Class-10,000 conditions in
other curatorial laboratories.

13.2.3.4 Maintain and operate an in-house precision cleaning capability
for curatorial tools, containers, equipment, and GN2 cabinets that
includes pre-cleaning, final cleaning, sampling, and certification.
Cleaning tasks include operations maintenance of a Freon still or its
equivalent upon later adoption of a Freon substitute.

13.2.3.5 Plan and carry out the processing of planetary samples
according to established procedures; understand scientific requirements
for specific samples; assimilate information on the sample collections
to derive specific preparation plans; work in a nitrogen environmental
cabinet, sawing, dissecting, chipping, weighing, photographing,
packaging samples, and updating data records on individual samples;
prepare written descriptions of samples which have been sawed, chipped,
or from which core samples are taken. Advanced analytical techniques
shall be required for complete documentation. Prepare samples for
shipment to investigators around the world; receive and return used
samples to the collections and all aspects of preparing and, maintaining
sample data bases, photographs, catalogs, and newsletters describing the
current state of samples and their fragments. For lunar samples, yearly
accountability through inventories and reports shall be required.
Inventories of other collections shall be required, but less often.

13.2.3.6 Prepare very high quality, specially documented thin sections
and polished thin sections of planetary samples for analysis by
petrographic microscopes, electron microprobes, and other microbeam
instruments; maintain a state-of-the-art competence in thin section
technology; and maintain a thin section library.

13.2.3.7 Provide support for the U.S. Antarctic Meteorite Program. This
includes logistic support for Antarctic field collection teams and
maintenance of records for field collection; description and
classification of new meteorites and announcement in newsletters and
catalogs; processing and allocation of samples to investigators; support
for Meteorite Working Group meetings; and support for Smithsonian
Institution catalogs and sample curation.

13.2.3.8 Provide support for designing, testing, and deploying systems
for collecting cosmic dust in space and in the stratosphere, and for
retrieval and scientific characterization of individual particles. This
includes all aspects of contamination control for cosmic dust
collectors. Operate microscopes and computer-aided optical scanning
equipment to detect and document particles from cosmic dust collectors
and materials and surfaces returned from space; and identify, document,
and prepare individual particles for analysis.

13.2.3.9 Provide support for examination, documentation, and
distribution of samples from space-exposed surfaces of satellites or
spacecraft. The nature and scope of such support shall be similar to
that pertaining to planetary samples.

13.2.3.10 Define requirements for new procedures or facilities needed to
maintain or enhance the effectiveness of sample preparation; control and
develop approved procedures and equipment; and define and develop the
capability to handle samples obtained by human-tended or
non-human-tended planetary missions

13.2.3.11 Provide support for computer-based data systems; assemble and
secure maintenance of data bases on minicomputers and microcomputers;
generate forms and reports; and control sample inventories.

13.2.4 Geoscience and Space Science Instrumental Analysis Laboratories

This function involves operation of the following state-of-the-art
laboratories: Electron Microscopy Laboratory, Electron Microprobe
Laboratory, Thermal Ionization Mass Spectroscopy Laboratory, Neutron
Activation Laboratory, Noble Gas and tight Element Analysis Laboratories
(which use gas chromatography, mass spectroscopy, and laser
microprobes), Spectroscopy and Magnetics Laboratory (which uses
Mossbauer, electron magnetic resonance and optical spectroscopy), Low
Level Radiation Counting Laboratory and Radiation Dosimetry Laboratory,
Thermal Analysis and Calorimetry Laboratory (which uses differential
scanning calorimetry and mass spectrometry), X-ray Diffraction
Laboratory, Atomic Absorption Spectroscopy Laboratory, and Stable
Isotope Mass Spectrometry Laboratory. The following are representative
tasks the contractor shall perform:

13.2.4.1 Prepare samples for analysis; perform analyses by operating
equipment in the laboratory according to established procedures and
specified levels of precision and accuracy; collect, reduce, and analyze
the data; maintain standards and controls for laboratory analyses; and
maintain data and photo archives.

13.2.4.2 Train and assist visiting scientists to operate equipment in
the laboratories and analyze the data.

13.2.4.3 Interpret data and prepare graphs, photographs, and manuscripts
for publication of analysis results and new operating techniques.

13.2.4.4 Define, develop, and implement new hardware and software
procedures to improve laboratory operation and analytical capability.

13.2.5 Specialized Experimental Laboratories

This function defines support to Unique non-routine experimental
laboratories. Technology in these laboratories require new or modified
equipment that must be designed and constructed before an experiment may
be initiated.

**13.2.5.1 Experimental Planetary Science Laboratories** - This function
supports the Experimental Petrology Laboratory, Planetary Surface
Process Simulation Laboratory, and the Indigenous Space Materials
Utilization (ISMU) Laboratory. The Petrology Laboratory studies the
stability of planetary materials as a function of temperature, pressure,
and oxygen partial pressure. The Planetary Surface Process Laboratory
involves simulation experiments and sample analyses to determine the
effects of weathering caused by ultraviolet and particulate radiation.
Current utilization is in support of Martian environmental hazards. The
ISMU Laboratory investigations include: (1) recovery of oxygen from
lunar soil, and (2) preparation of ceramic, structural materials by
radiant and microwave heating. The following are representative tasks
the contractor shall perform:

13.2.5.1.1 Design, construct, assemble, and test prototype experimental
arrangements from conceptual designs and determine materials performance
under test conditions, including obtaining or machining all specialized
parts for experimental apparatus.

13.2.5.1.2 Analyze effects of such tests using quantitative techniques;
assist in the preparation of reports; and maintain archival files of
test result documentation.

**13.2.5.2 Experimental Impact Laboratory (EIL)** - This laboratory uses
launchers (guns) of various design for their experimental tasks. The EIL
studies impact phenomena of scientific and technological interest,
including dynamic response of geological solids to planar shock waves,
and cratering in metallic and non-metallic materials. The following are
representative tasks the contractor shall perform:

13.2.5.2.1 Design, construct, assemble, and test prototype experimental
arrangements from conceptual designs; determine materials performance
under test conditions; and machine all specialized parts for
experimental apparatus.

13.2.5.2.2 Operate the light-gas guns, flash X-ray systems, photography,
and other diagnostic systems in support of the impact testing; adhere to
stringent safety requirements in the operation of the launchers (guns)
which operate with gun powder and hydrogen gas.

13.2.5.2.3 Analyze the results of impact testing using quantitative
techniques; assist in the preparation of reports; and maintain archival
files of test results and test documentation.

13.2.5.2.4 Define, develop, and implement new hardware and software
procedures to improve laboratory operation and analytical capability.

**13.2.5.3 Hypervelocity Impact Test Facility (HIT-F)** - The HIT-F
conducts impact tests using launchers (guns) of various designs, and
applies various analytical models to research and-develop effective
shielding systems and protection techniques for defending spacecraft
from meteoroid and orbital debris impacts. The following are
representative tasks the contractor shall perform:

13.2.5.3.1 Operate and maintain two-stage light-gas gun launchers, ultra
high-speed cameras, high-speed video cameras, flash X-ray systems, and
other diagnostic systems in support of the impact testing; adhere to
stringent safety requirements in the operation of the launchers (guns)
which operate with gun powder and hydrogen gas.

13.2.5.3.2 Design, construct, assemble, and test prototype experimental
arrangements from conceptual designs; determine materials performance
under test conditions; and machine all specialized parts for
experimental apparatus.

13.2.5.3.3 Analyze the results of impact testing using quantitative
techniques; assist in the preparation of reports; maintain archival
files of tests results and test documentation.

13.2.5.3.4 Utilize hydrocodes and other analytical models to predict the
effects and frequency of impacts on spacecraft structures.

13.2.5.3.5 Define, develop, and implement new hardware and software
procedures to improve laboratory operation and analytical capability.

**13.2.5.4 Radar Data Analysis Facility (RDAF)** - The RDAF processes
radar data from various Department of Defense (DOD) radars to
characterize the orbital debris environment. The following are
representative tasks the contractor shall perform:

13.2.5.4.1 Process data from the Haystack and Haystack Auxiliary (HAX)
radars collected in the staring mode of operation to determine the
distribution of orbital debris in size, altitude, inclination, and
eccentricity.

13.2.5.4.2 Define, develop, and implement software modifications to
accept data from different radars such as the Ground Based Radar (GBR).

13.2.5.4.3 Define, develop, and implement experiments to improve the
accuracy of the radar measurements. This includes calibration
experiments such as the Orbital Debris Radar Calibrations Spheres
(ODERACS) flight experiment and improving the Radar Cross Section
(RCS)/Physical Size Model.

**13.2.5.5 Radiation Dosimetry Laboratory** - This function provides the
ionizing radiation dosimetry hardware and processing services required
to meet the medical and legal requirements for Space Shuttle and space
station radiation exposure measurements, operation of the Dosimetry
Laboratory, and development of advanced instrumentation for experimental
measurements of the space radiation environment.

13.2.5.5.1 Provide flight qualified radiation dosimeter for each Space
Shuttle Flight. Provide laboratory analysis of the returned dosimeters,
and report summarizing the findings of that analysis.

13.2.5.5.2 Conceive advanced research or engineering approaches to new
developments and generate conceptual design for space radiation
measurements and experiments.

13.2.5.5.3 Perform space radiation experiments and measurements. Guide
the technical aspects of research, development or testing programs,
outlining procedures to be followed and suggesting modifications or new
approaches as the work progresses. Analyze the results, using computer
programs developed for the experiment.

13.2.5.5.4 Implement analytical and laboratory methods to sustain the
highest quality product applicable to the laboratory requirements.

13.2.5.5.5 Prepare manuals and bulletins related to radiation dosimetry.
Prepare comprehensive technical reports or memorandums containing
analytical results, test results, and/or recommendations which may form
the basis of engineering decisions.

\*\*\*NOTE: Schedule A, 11.2.6 went to NEW SOW Part II, Earth and Image
Science Mission Operations.

\*\*\*For every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

13.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

13.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

# PART I - AREAS OF SUPPORT

**SECTION C: SPACE SHUTTLE PROGRAM**

14\. SPACE SHUTTLE VEHICLE ENGINEERING

\*\*\*From Schedule A, 12.0, FEO:

This function provides the engineering and technical support
requirements of the Flight Engineering. Shuttle systems performance is
verified through analysis of operational flight data and ground test
data. This activity will provide engineering and technical support to
the Shuttle subsystem managers by developing, coordinating, and
maintaining a series of postflight data requirements and specifications
used to verify subsystem performance and health. Included in this
activity are the requirements and software development for the Mission
Evaluation Room (MER) engineering analysis workstations which
encompasses interactive data analysis, networking and communications,
and access to Shuttle parametric subsystem data and operational data
bases. This will provide for consolidation of requirements through an
interactive process to support the needs of the Shuttle MER subsystem
support personnel. Also, included in this activity are the requirements
to study both Inter-Center and Center electronic transfer of Shuttle
flight data, to maintain the existing software needed to support data
product generation and requesting, and the Flight Engineering computer
hardware and software support.

14.1 REPRESENTATIVE TASKS

14.1.1 Computer Systems Support

14.1.1.1 Provide an ongoing comprehensive study of the type of hardware
recommended for the Flight Engineering. Also, manage the procurement of
the recommended hardware and system software and supervise the
installation and acceptance testing of the hardware and system software
to assure proper functionality of the installation.

14.1.1.2 Provide maintenance, troubleshooting, inspection, and repair
for Flight Engineering's computer systems, peripheral hardware,
stand-alone workstations, and other related hardware. Perform
preventative maintenance; provide support, schedule vendor maintenance,
and maintain facilities for equipment repair; operate test equipment for
troubleshooting and equipment testing; maintain technical documentation
for all hardware systems; and provide cable fabrication and cable
routing support for remote computer terminals and other peripherals.

14.1.1.3 Provide support of ongoing operations and upgrade of MER
hardware and software, to allow for the operational capability required
to support Shuttle programs.

14.1.2 Software and Database Maintenance

14.1.2.1 Coordinate with system/subsystem engineers to maintain and
enhance flight data analysis requirements to verify orbiter system
performance and health. Develop new workstation requirements based on
MER experience including the design of key system algorithms and output
products. These requirements shall include inflight, postflight, fault
isolation, and trend analysis algorithms and pass/fail limits.

14.1.2.2 Maintain and enhance software on workstations used by subsystem
personnel in their performance of flight analysis. Maintain and enhance
the data base for tracking system performance and health reports for
each mission and vehicle. Support system/subsystem personnel in
designing and requesting new data products for mission operations, both
flight and simulation.

14.1.3 Photographic and Program Requirements

14.1.3.1 Coordinate the inputs to the Program Requirements Document
between JSC and other NASA/contractor facilities including the
requesting and coordinating of photographic and flight/test data;
support the development of the inter-Center data communication network.

14.1.4 Information Management

14.1.4.1 Maintain data bases to support the generation, verification,
authentication, and distribution of several program level documents
including the Shuttle Operational Data Book (SODB), and several history
logs and tracking lists supporting JSC, Kennedy Space Center (KSC),
Marshall Space Flight Center (MSFC), and contractor elements; use
various computer systems to maintain data bases as required by entering
data, updating files, and producing reports; support real-time and
postflight Mission Evaluation Team activities utilizing the VAX and the
Xerox systems to produce required reports and records; and prepare
documentation in support of system reviews both at JSC and other
contractor facilities and supporting Flight Engineering personnel.

14.1.5 MER Hardware/Software Operations

14.1.5.1 Provide support of ongoing operations and upgrade of MER
hardware and software, to allow for the operational capability, required
to support Shuttle programs including dining data products from the
Orbiter Data Reduction Center (ODRC), MSFC, and KSC; maintaining
hardware and software configuration and certification of MER systems;
providing technical support to users during preflight and flight; and
managing and maintaining workstation security.

14.1.6 ODRC Rehost Development

14.1.6.1 Maintain the system for obtaining real-time telemetry
downlink/downlist data in the MER. This system is an integrated part of
the upgrade of the ODRC and includes the ability to display flight/test
data from other NASA centers.

14.1.7 MER Engineering Data Display System Upgrade

14.1.7.1 Design, develop, and maintain a system for obtaining real-time
Shuttle telemetry data in the MER. This system shall decommutate,
calibrate, and distribute real-time data to the MER workstations.

14.1.7.2 Establish MER workstation hardware requirements based on
combined real-time and non-real-time telemetry processing requirements.
Prepare necessary procurement related to hardware requirements.

14.1.7.3 Coordinate with system/subsystem engineers to develop flight
data analysis to verify system performance and health. These
requirements shall address both real-time and non-real-time monitoring
and processing of Shuttle telemetry data during the prelaunch, launch,
on-orbit, entry, and post landing phases.

14.1.7.4 Design, develop, and maintain workstation software to monitor
and process Shuttle telemetry data in the MER. This software shall
provide real-time data display, fault detection and isolation, event
detection and annunciation, and trend analysis capabilities.

14.1.7.5 Establish MER workstation configuration management and
Automated Information System (AIS) security requirements. Design,
develop, implement, and maintain procedures and software to meet these
requirements.

\*\*\*From schedule A, 11.2.6 Solar System Exploration Division Support

14.1.8 Video Digital Analysis Laboratory (VDAS)

The following are representative tasks the contractor shall perform:

14.1.8.1 Operate the VDAS as an open-shop image enhancement/analysis
laboratory which supports uses with innovative, state-of-the-art
image-analysis; and support the Space Shuttle Photo/TV Project, Orbital
Debris Project, and Space Shuttle Earth Observations Project.

14.1.8.1.1 Devise image analysis techniques involving real-time digital
disk systems and television systems, operate image analysis computer
systems, and provide ethernet and Internet digital communication to
other NASA and worldwide digital computer networks.

**14.1.8.2 Earth Observations Laboratory (EOL)** - The contractor shall
staff and operate the EOL in order to maintain instantaneous access and
proper interpretation (from the astronauts' perspective) of imagery from
geosynchronous environmental satellites (GOES, METEOSAT, GMS) and the
NOAA Polar Orbiter Series plus other meteorological and oceanographic
data sources and model outputs. EOL serves as the focal point for
continuous support to Shuttle crews for Earth observations real-time
planning, and remains in two-way communication between orbiting
observers, mission control, and scientists/technicians on Earth.

\*\*\*For every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

14.2 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

14.3 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

# PART 1 - AREAS OF SUPPORT

**SECTION D: OTHER ENGINEERING & SCIENCE AREAS**

15\. OTHER ENGINEERING & SCIENCE AREAS

15.1 ENGINEERING, SCIENTIFIC, AND ANALYTICAL SUPPORT SERVICES

15.1.1 Engineering, Scientific, and Analytical Tools

**15.1.1.1 Computer Program Development and Maintenance Support** - The
following are representative tasks the contractor shall perform:

15.1.1.1.1 Develop program control tools.

15.1.1.1.2 Develop and/or install, maintain and document software
applications for data processing and evaluation, simulation data
reduction and analysis, automation support applications, and computer
graphics. This effort shall include development and maintenance of a
data base management system to support all data processing and
dissemination requirements and implementing computer security
applications.

15.1.1.1.3 Provide support in the assessment of existing, enhanced and
new commercially available computer programs which may enhance the
design and analysis capabilities including trade-off studies of
potential improvements in capabilities, compatibility with existing
programs and data bases.

15.1.2 Research and Development Support

\*\*\*From Schedule A, 9.1.4.2, NIO

**15.1.2.1 Technology Utilization and Commercial Transfer** - The
Technology Utilization and Commercial Transfer function includes the
development of those new technologies that are required to advance
future space activity. It supports Technology Utilization and
Advancement, both government, small business and commercial. Technical
management studies, analytical studies, technical analyses, scientific
research and analyses, engineering and science investigations shall be
conducted. The following are representative tasks the contractor shall
perform:

**15.1.2.2 Technology Advancement** - The areas of study are expected to
include mission definition, preliminary assessment of payload/experiment
and/or cargo mixes and mission feasibility, and trade-offs of alternate
methods of payload preparation and experiment component development.
Provide interface with the Space Transportation System (STS); perform
mission feasibility planning and analytical design of payload; manage
the development, integration and implementation of flight and ground
operations requirements; perform the analytical integration of hardware
components and experiments into an effective payload; provide technical
support during payload ground and flight operations; and perform special
studies as identified and assigned.

15.1.2.2.1 Perform studies, trade-offs and analyses including
investigations of existing related study material; prepare documentation
and data bases containing the result of the studies; prepare and
maintain the documentation required to support all experiment
development/payload/STS reviews; and prepare and maintain engineering
drawings of contractor developed hardware.

15.1.2.2.2 Perform liaison functions and duties to assist in the
coordination of reviews and Technical Exchange Meetings; maintain
records, minutes of meetings, and action item logs; and assist in the
preparation of meeting summaries, technical documents and reports.

15.1.2.2.3 Perform special studies, assessments, evaluations and
analyses in designated project areas; prepare material to present study
results to other organizations; identify problem areas; evaluate
alternate solutions; and prepare recommendations and impact assessments
as they relate to the designated study areas.

15.1.2.2.4 Perform trade-offs of alternative methods of payload
preparation and experiment component development; investigate related
study material and other documentation in the development of these
studies, prepare documents and data bases to support the results of the
studies; assist in the preparation of plans, resources requirements and
schedules; coordinate the activities of support elements; and maintain
records, minutes of meetings, and action item lists.

15.1.2.2.5 Conduct special studies, assessments evaluations and analyses
in designated special study areas; and assist in the preparation of
material necessary to present study results to cognizant NASA agencies.

15.1.2.2.6 Support project reviews and meetings, including design and
safety reviews; develop presentation materials and make special
presentations to NASA management; and develop the data requirements and
produce the project/experiment and payload supporting documentation
including design review data packages, operating procedures, ICDs, and
failure reports.

15.1.2.2.7 Support the development of program schedules, cost
performance data, schedule performance, and project forecasts for NASA
to evaluate the overall status of each project.

**15.1.2.3 Technology Utilization** - This area implements the Space Act
directives requiring that advanced technologies in automation and
robotics, biomedical research, communications, materials processing, and
others be reported, developed, and utilized.

15.1.2.3.1 Provide liaison to the technical directives, divisions, and
branches for identification of new technology projects with high
transfer potential; identify new technology; plan and discuss
application projects; obtain management support for the projects; advise
management of benefits resulting from the program using appropriate
slide and view graph presentation material; and assist in writing
descriptions for submittal of Tech Briefs.

15.1.2.3.2 Support Program Operating Plan activities for existing as
well as new potential application projects including project
description, funding plan, and schedule; monitor application projects
with respect to schedule, operating plan milestones, and expenditures of
funds and manpower; and analyze this data to determine availability of
resources to make recommendations for rebudgeting, reallocation, or
transfer of funds to meet project goals; alert management to potential
problems for a timely resolution of project management issues/problems;
prepare and maintain detailed reports; and compile data for and prepare
a quarterly status report to the Technology Utilization Officer on the
financial and technical status of each project.

15.1.2.3.3 Process and coordinate each item of new technology for
submittal and processing with other NASA Headquarters contractors for
evaluation, draft preparation, and printing as a Tech Brief; prepare and
maintain reports, logs, files, and suspenses on each item of technology
on the Technology Utilization Network System (TUNS) computer network
system; assist innovators in the evaluation and processing of the new
item including preparation of the Tech Brief draft; and compile data for
and prepare a monthly status report on Tech Briefs to be used for the
monthly awards submittal to NASA Headquarters.

15.1.2.3.4 Provide technical support for the TUNS, including system
administration, configuration management, problem diagnosis and
resolution, maintenance and operation, coordination with the TUNS
contractor, and consultation with TUNS user personnel; and provide
technical support for the expansion and enhancement of the TUNS
including procurement of additional hardware and software.

15.1.2.3.5 Provide technical support to develop presentation material
for Project Outreach for use in presentations to members of the
petroleum industry, educational sector, and the medical professions; and
specify and procure video presentation equipment.

15.1.2.4 **Research and Technology Programs Support** - This area
provides support for the implementation and management of the Research
and Technology Programs.

15.1.2.4.1 Develop and maintain schedules; set up technology reviews;
and provide support budget management activities.

15.1.2.4.2 Prepare program briefing materials for presentation to NASA
management and technical forums.

\*\*\*From Schedule A, 13.1.3

15.1.3 Subsystem Management Support System (SMSS) and Orbiter Data
Reduction Complex (ODRC) Interface System

The SMSS and ODRC support provide applications which provide easy access
to programmatic data by Engineering Directorate subsystem managers. The
contractor shall develop and maintain data base capability to store
significant information about the subsystems. The contractor shall
develop and maintain tools to allow the subsystem managers to navigate
networks and systems in a transparent manner through a common desktop
graphical interface. The contractor shall also Interface with the
appropriate subsystem management and panel representatives to identify
programmatic data that is deemed important to be able to access locally.

\*\*\*From Schedule A, 13.1.5

15.1.4 Visual Communication Lab Support

Develop computer generated motion for product demonstration, educational
programs, and mission analysis. Coordinate with customer to understand
requirement, develop accurate story-boards for pre-production planning,
and develop project schedules. Develop new programming techniques for
the generation of models, textures, and motion specifications, as well
as provide support and direction in the development of more general
project management software related to the Wavefront Package. Prepare
and maintain software support and project management documentation.
Provide quality check for all animated sequences as well as maintain
direct interaction with the customer until final delivery of product.

\*\*\*From Schedule B, Part 1, 5.2.4.3 (EDITED to include other E&S
areas)

15.1.5 Maintenance of Computer Equipment and Related Ground Support
Equipment

The contractor shall be responsible for maintaining computer equipment
and computer related GSE associated with other engineering and sciences
areas. This GSE mainly applies to ground experiments, scientific
research equipment, flight experiment development, and mission support.
Where hardware maintenance contracts with outside maintenance vendors
are provided by NASA or other agencies, the contractor shall coordinate
maintenance scheduling with these outside vendors. The contractor shall
be responsible for maintaining current and accurate lists of other
engineering and science computer equipment and GSE, as covered under
this SOW, at JSC or remote sites for maintenance purposes and for
updating maintenance records associated with local or Center-wide
maintenance contracts where these are used. The contractor shall be
responsible for maintaining physical and automated records of all
maintenance formed on this computer equipment and GSE.

15.2 LABORATORY/FACILITY SUPPORT SERVICES

\*\*\*From Schedule A, 9.2.2, NIO (EDITED to cover all Other E&S Areas):

15.2.1 Federal Information Processing Resources Support

**15.2.1.1 Computer Support** - This function supports the FIPR
requirements of selected tasks related to other engineering and science
areas of the contract. The primary responsibilities of computer support
include data processing and analysis, customized FIPR hardware interface
design and development, customized software design and development,
automation support, and the projection of future FIPR requirements.
Support engineering development and analysis tasks including data base
system design and support, advanced studies, data reduction, project
management and automation applications design and development. The
following are representative tasks the contractor shall perform:

15.2.1.1.1 Provide systems and operations support for the computer
systems and peripheral hardware. This effort shall include maintaining
tape and hardware/software documentation libraries, developing
documentation for computer systems and laboratory operating procedures,
screening and installing operating system and application software,
providing laboratory engineering evaluation studies, performing computer
systems networking support, receiving and shipping user data products,
and maintaining an equipment tracking system.

15.2.1.1.2 Provide hardware support in the following areas:
troubleshooting, inspection, and repair of all Computer Facility
computer systems, peripheral hardware, and user workstations which
include terminals, CAD workstations, graphics terminals and
workstations, and personal computers; cable fabrication and routing for
remote terminals and other peripherals; network design, development
maintenance and management support; and design, development,
installation, and maintenance of special purpose computer interfaces.

15.2.1.1.3 Provide hardware and software maintenance for Computer
Facility FIPR not under warranty or covered under vendor maintenance
contracts. This effort shall include documenting all changes, upgrades,
and enhancements to the hardware and software, maintain adequate parts
and supplies to support routine operations and maintenance, both
preventive and remedial, on all FIPR not covered under vendor
maintenance.

15.2.1.1.4 Provide general computer systems support in the areas of
software development and maintenance of existing and planned engineering
software and hardware systems and Computer Aided Engineering (CAE)
hardware and software systems; and provide support for activities such
as applications and operating systems software development, vendor
software installation and maintenance and operational support,
consultation, user training, and the maintenance and operational support
of data bases and analysis software systems.

\*\*\*For every NASA Div/Ofc: From Schedule A, 13.2.2 M&O Support,
edited to include only Lab-unique FIPR:

\*\*\*From Schedule A, 7.2.6 Structures & Mechanics Division.

15.2.2 Materials Technology Laboratory

This function provides laboratory support for experimental
investigations and evaluation of materials programs. The following are
representative tasks the contractor shall perform:

15.2.2.1 Prepare TPS test articles, produce limited number of TPS tiles,
and conduct TPS-environment compatibility tests.

15.2.2.2 Evaluate effects of atomic oxygen on spacecraft hardware,
evaluate fracture characteristics of various metallic components, manage
Shuttle flight experiments designed for the evaluation of reaction rates
of specific spacecraft materials, test materials, and prepare material
samples and portions of the flight hardware.

15.2.2.3 Perform detailed experimental evaluation of materials fracture
characteristics under various stress and environmental conditions,
operate mechanical loading equipment, and operate special data reduction
instrumentation.

15.2.2.4 Evaluate chemical and physical properties of materials, conduct
chemical analysis as related to hardware and facility performance,
conduct failure analysis of both spacecraft and facility problems,
perform nondestructive evaluation of spacecraft/aircraft and facility
hardware, and conduct metallurgical analyses. Maintain laboratory
instruments including electron microscope, infrared spectrometers, gas
chromatograph-mass spectrometer, metallurgical sample preparation
equipment, thermal property evaluation equipment, and mechanical
property testing equipment.

15.3 MAINTENANCE AND OPERATIONS SUPPORT

Provide maintenance and operation support to all laboratories,
facilities, and related hardware/software systems and equipment for
laboratory unique FIPR, including FIPR and related peripherals,
communications, and networks. Develop and Implement maintenance and
operations plans and procedures.

Ensure the operational availability of laboratory unique FIPR equipment,
including laboratory-unique FIPR logging/inspection for flight, through
continued development and execution of maintenance plans and procedures,
by providing properly trained personnel and by ensuring that adequate
maintenance tools are available. Contractor maintenance personnel shall
be proficient in the equipment and systems under their individual areas
of responsibility and shall be sufficiently familiar with interfacing
systems so as to trouble-shoot interface anomalies. Where it is not
beneficial to the Government for the contractor to maintain local
expertise on specific equipment, the contractor shall provide for
preventive maintenance agreements and/or call-in of specialists in a
manner consistent with equipment availability requirements. Provide
preventive maintenance through periodic testing, adjusting, cleaning,
lubricating, and replacing of parts for all equipment to insure proper
and continued operation. Perform remedial maintenance to restore failed
equipment to its proper operating condition. Remedial maintenance
includes the requirement to perform, upon request from the government,
capital type rehabilitation on or the replacement of equipment or
systems which cannot be physically repaired or for which continued
routine maintenance is not economically feasible.

The contractor shall be responsible for the maintenance of
laboratory-unique FIPR equipment and software in the laboratory
facilities. Laboratory-unique equipment and software are equipment and
software which do not commonly exist at JSC outside a particular
laboratory and are integral to the function of the laboratory and the
tasks which the laboratory performs. Equipment and software which are
laboratory-unique at the inception of this contract may lose their
status as such because of increases in the amounts of particular types
of equipment and software put in use at JSC. The Government will monitor
the incidence of laboratory-unique equipment and software during the
period of the contract. If the Government determines, at their own
discretion, that any equipment or software are not or cease to be
laboratory-unique, the contractor will be so notified. The maintenance
requirements for such equipment will thereafter be undertaken by a JSC
contractor having Center-wide responsibility for the maintenance of
general, non-mission FIP equipment and software (currently the
Information Systems Contract, or ISC). The transfer of maintenance
responsibility as contemplated herein will be at a time determined by
the Government to be the most efficient and effective. The
responsibility for maintenance shall include problem "screening" prior
to a maintenance call, the ability to reconfigure the hardware,
software, or systems, and the implementation of hardware or software
upgrades.

\*\*\*From Schedule A, 13.2.4 Logistics support, edited to include only
flight related items receiving/inspection:

15.4 LOGISTICS SUPPORT

Provide receiving and inspection functions for flight and flight related
items. This shall include all acquisition implementation, inventory
control, receipt and inspection functions that are necessary to meet the
requirements of this contract.

Operate stockrooms for flight and flight related items including the
preparation and maintenance of complete and adequate tool and equipment
accountability records, and the submission of regular reports showing
the use of items and the amounts available. Inventories shall be
conducted in accordance with established JSC policy and procedures and
equipment acquisition will be performed in compliance with the NEMS
(NASA Equipment Management System).

15.5 SAFETY, RELIABILITY, MAINTAINABILITY, AND QUALITY ASSURANCE
(SRM&QA)

15.5.1 SRM&QA Management

The contractor shall provide necessary resources for the management,
supervision, planning and administration of safety, product assurance,
and training functions under the SEAT Contract. The SRM&QA Management
shall provide the infrastructure for managing safety, reliability,
maintainability, and quality assurance (SRM&QA), and software quality
assurance (SQA) activities under the contract.

15.5.2 Safety and Mission Assurance (S&MA)

The contractor shall be disciplined in system safety engineering to
manage the engineering and operations functions within the SEAT Contract
both at the contractor's facility and on-site at JSC. Failure modes
effects analyses, identification of component hazards, and other systems
safety functions shall be performed and charged directly to NASA
projects and tasks. These functions, performed in direct support of
projects and tasks, are not reflected in the M&A statement of work.

The contractor shall perform S&MA assessments and provide S&MA products
in accordance with the specified NASA program project S&MA requirements
for flight hardware and software.

15.5.3 S&MA Certification

The contractor shall use the Certification and Acceptance Requirements
Document (CARD) DRL #15 to provide cognizance of plans for hardware
certification and acceptance, and results thereof.

The contractor shall use the Safety and Mission Assurance Certification
Approval Request (SMACAR) DRL #13 in the preparation and delivery of GFE
flight hardware certification documentation.

15.5.4 Safety

The contractor shall develop, plan, and implement an independent safety
program to assure that hazards and their consequences are identified,
evaluated, and controlled throughout all phases of the program in
accordance with NHB 1700.1 (V1-B) "NASA Safety Policy and Requirements
Document" paragraphs 104, 108, and 310. As part of this program the
contractor shall develop a Safety Plan in accordance with the Safety
Plan DRL #7.

15.5.5 Safety Requirements

The contractor shall meet all applicable safety design and information
requirements as defined in the program or project requirements document
identified for each subsystem.

The contractor shall perform and maintain safety analyses for hardware,
software, and their interfaces. For Space Shuttle: The contractor shall
perform a safety analysis in accordance with NSTS 22254 "Methodology for
Conduct of Space Shuttle Program Hazard Analyses." The contractor shall
use the Space Shuttle GFE Safety Analysis Report (SAR) and Hazard Report
(HR) \[HR_1\] DRL #5 to document the safety analysis performed and any
identified hazards. For Space Station: The contractor shall perform a
safety analysis in accordance with SSP 30309 "Safety Analysis and Risk
Assessment Requirements Document" The contractor shall use the Space
Station GFE Safety Analysis Report (SAR) and Hazard Report (HR) \[HR_2\]
DRL #6 to document the safety analysis performed and any identified
hazards.

The following phases are to be included: ground processing, launch,
assembly, normal operations, contingency, and return. Working files of
hazard reports shall be delivered in accordance with the need dates as
specified by the NASA project safety review panel in support of program
schedule milestones.

The contractor shall evaluate proposed waivers and deviations for end
items, and provide a qualitative assessment for management concurrence.
When a waiver or deviation results in an increased risk, a hazard report
shall be initiated, or an existing hazard report shall be updated to
show the accepted risk status.

The contractor shall evaluate proposed changes and identify hazards that
may result from their incorporation. Upon approval of changes that
present new or modified hazards, the hazards shall be documented.

15.5.6 Safety Reviews

The contractor shall participate in in-process safety reviews including
the presentation of all hazards associated with their hardware and
software to the appropriate flight or ground safety panels.

Coordination of safety analysis with the NASA project safety panel shall
be completed prior to the formal safety review that will coincide with
the program schedule.

The contractor shall provide an overview and status of their analysis at
each of the formal reviews. The safety reviews shall be conducted in
accordance with the NASA project safety review process.

15.5.7 Evaluation of Test Activity

The contractor shall ensure that hardware and software test cases are
developed to verify safety requirements and hazard controls at the
component, integration, acceptance, and system test levels.

For Space Station, the contractor shall evaluate software or firmware,
identified through hazard analysis as safety critical for hazard
control, in accordance with SSP 30309.

15.5.8 Review of Flight Hardware Failures

The contractor shall evaluate flight end items failures, including
investigative results associated with catastrophic and critical hazards,
and participate in safety reviews to resolve issues.

15.5.9 Reliability & Maintainability

The contractor shall develop and implement a reliability and
maintainability program to assure implementation and verification of
reliability & maintainability requirements, and to evaluate
characteristics. As part of this program the contractor shall develop a
Reliability Plan in accordance with the Reliability & Maintainability
(R&M) Plan DRL #4.

15.5.10 Reliability Design Criteria

The contractor shall meet all applicable reliability design requirements
as defined in the program and project requirements document identified
for each subsystem.

The contractor shall review and evaluate design specifications,
procurement specifications, and design changes. This assures that all
design items reflect proper reliability design criteria and that all
specifications contains applicable reliability requirements.

15.5.11 Flight Hardware Failure Modes and Effects Analyses/Critical
Items List (FMEA/CIL)

The contractor shall prepare, maintain, and submit failure modes and
effects analysis (FMEA) and Critical Items List (CIL)and support program
reviews.

For Space Shuttle: The contractor shall conduct and prepare FMEAs and
CILs in accordance with NSTS 22206 "Instructions for Preparation of
Failure Modes and Effects Analysis (FMEA) and Critical items Lists
(CIL)." The contractor shall use the Space Shuttle GFE Failure Modes and
Effects Analysis (FMEA) and Critical Items List (CIL) \[FMEA_1\] DRL \#
8 to document FMEAs and CILs.

For Space Station: The contractor shall conduct and prepare FMEAs and
CILs in accordance with SSP 30234 "Instructions for Preparation of
Failure Modes and Effects Analysis and Critical items Lists for Space
Station." The contractor shall use the Space Station GFE Failure Modes
and Effects Analysis (FMEA) and Critical Items List (CIL) \[FMEA_1\] DRL
\# 9 to document FMEAs and CILs.

15.5.12 Reliability and Analysis

The contractor shall compile component failure rate data for end-items
in accordance with the Space Station Reliability & Maintainability
Predictions Report DRL #16. The contractor shall perform reliability
analyses and support program reviews for end-items using this failure
rate data and shall report these analyses in accordance with the Space
Station Reliability & Maintainability Predictions Report DRL.

The contractor shall make available upon request all component and part
data used to develop the Mean Time Between Failures (MTBFs). Ground
support equipment MTBFs shall be developed in contractor format and
available upon request.

15.5.13 Electronic Electrical and Electromechanical (EEE) and Mechanical
Parts Control Plan

Using DRL #10, the contractor shall provide a plan which describes the
process of how the contractor will interface with NASA management, EEE
and Mechanical Parts personnel, and design engineers to assure the
system, board level designs and selected parts meet performance
parameters, ensure long term reliability, and minimize program life
cycle cost.

15.5.14 Alert System

Using DRL #11 as a guide, the contractor shall provide a documented
response on each requested ALERT investigation and resolution to
NASA/JSC. Program/project initiated ALERT's are disseminated by the
NASA/JSC contractors, NASA centers, and Government and Industry Data
Exchange Program (GIDEP).

15.5.15 Limited-Life Items

The contractor shall provide estimated wearout life for orbit
maintainable items to support maintenance time predictions and
preventive maintenance analysis. The contractor shall identify the
life-limiting parts or materials and life limiting factor (i.e. cycles,
time, age) for the orbit-maintainable items and document this
information as part of the preventive maintenance analysis. The
contractor shall use the Limited-Life Item List DRL #12 to document
limited-life items.

15.5.16 Maintainability

The contractor shall meet all applicable maintainability design
requirements as defined in the project requirements document identified
for each subsystem.

The contractor shall develop and implement a maintainability program to
assure equipment meets the maintainability requirements identified in
the NASA project's requirements document. As part of this program the
contractor shall develop a Maintainability Plan in accordance with the
Reliability & Maintainability (R&M) Plan DRL #4. The contractor shall
coordinate and integrate to accomplish all the specified project
maintainability requirements. The contractor shall perform
maintainability analyses and trade studies to support verification that
the design complies with maintainability requirements.

15.5.17 Maintainability Allocations and Predictions

The contractor shall provide Mean Maintenance Crewhours per Year
(MMCH/Y) predictions for all on orbit maintainable equipment. If
necessary, design constraints shall be allocated down to the level of
equipment design where they can be most effectively managed and
controlled. A preventive maintenance program shall be performed.
Maintainability predictions shall be performed and submitted in
accordance with the Space Station Reliability & Maintainability
Predictions Report DRL #16.

15.5.18 Maintainability Qualitative Assessments

The contractor shall perform qualitative maintainability assessments.
Data resulting from qualitative assessments shall be used in the
concurrent engineering process for each aspect of the design. If
applicable, this includes performing assessments for accessibility and
equipment removal, replacement, and repair provisions. Methods of
failure detection and corrective action shall be identified to support
FMEA preparation. Qualitative assessment shall assure that appropriate
maintainability characteristics are incorporated in the designs and that
maintenance can be performed utilizing the specified resources.

For Space Station: The contractor shall use the Space Station
Reliability and Maintainability Predictions Report DRL #16 to status
quantitative R&M characteristics of Space Station functions,
capabilities, and equipment.

15.5.19 Failure Detection, Isolation, and Recovery Assessment

The contractor shall develop and implement a Failure Detection,
Isolation, and Recovery (FDIR) analysis process to ensure that each end
item design meets the FDIR requirements identified in the project
requirements document identified for each subsystem in the NASA
project's requirements document*.* The contractor shall document the
detectability and distinguishability of each end item failure mode as
identified in the FMEA document. The FDIR assessment data shall be
performed and submitted in accordance with the Space Station Reliability
and Maintainability Predictions Report DRL #16.

15.5.20 Problem Reporting and Corrective Action

The contractor shall participate in the NASA Problem Reporting and
Corrective Action (PRACA) system. The contractor shall use the Problem
Reporting and Corrective Action (PRACA) DRL #14 to report problems and
describe their resolution.

\*\*\*From CMS (Long version) 14.1.3.3.3 Training and Certification:

15.5.21 Training and Certification (T&C)

The contractor shall design and implement training and certification
processes to ensure that qualified personnel are available to perform
their assigned tasks in a safe and reliable manner. The contractor shall
develop training courses and certification criteria that satisfy skills
certification and technical operating requirements, including JPG 1700.1
Category I, II, and III hazardous operations. The contractor shall
develop and schedule classroom instruction, technical skills training,
and formal on-the-job training to meet T&C requirements. The contractor
shall develop and maintain a Training and Certification Records System
(TCRS) to document individual employee T&C qualifications, provide
periodic re-training, and provide an automated database of all T&C
activity.

15.5.22 Quality/Product Assurance

The contractor shall provide a Product Assurance process to maintain the
quality and reliability of all parts, materials, and processes. The
contractor shall provide quality assurance support for all
hardware/software designed, developed, and manufactured in off-site
facilities, through final acceptance and delivery to the Government.
Unless otherwise specified in Memorandum of Agreement, the contractor
shall adhere to the JSC Quality Management System for activities
performed on-site JSC.

The contractor shall submit specified categories (ref: NASA/JSC Ltr.
ND6-94-012 dated APR. 28, 1994) of procurement documents to the
designated NASA quality representative for determination of the need for
Government Source Inspection (GSI) prior to release of the procurement.
Procurements which require GSI shall include the following statements:

"All work on this order is subject to inspection and test by the
Government at any time and place. The Government quality representative
who has been delegated quality assurance functions on this procurement
shall be notified immediately upon receipt of this order. The Government
representative shall also be notified 48 hours in advance of the time
articles or materials are ready for inspection or test." Procurements
which do not require GSI shall include the following statement: "The
Government has the right to inspect any or all of the work included in
this order at the supplier's plant."

Disposition of non-conforming product, other than rework to
specification, shall be approved by the designated NASA Quality
Assurance Representative.

Traceability shall be as defined in the project requirements document
and/or task order for each subsystem, unless otherwise specified, as a
minimum for flight or GSE projects, a system shall be in place to ensure
identification of all materials/products, whether separately produced
discrete items, or material produced in lot/batches, to ensure
traceability to the original source/manufacturer and to determine
verification status. This system shall be maintained throughout the life
of this contract, including material/product receipt; all stages of
production; delivery; installation, etc.

In accordance with the project requirements document or task order
identified for each subsystem, NASA Assurance Standards shall be
employed throughout all phases of hardware manufacture to control the
quality of the operations. If the contractor opts to use other
standards, the contractor shall submit those standards for NASA approval
per DRL #23, Workmanship Specifications.

The contractor shall perform process audits upon request from the JSC
Contracting Officer. Process audits are performed to provide a candid
assessment of processes to identify generic system anomalies and areas
for improvement. The process audits shall be conducted in two phases.
Phase I consists of an in-depth audit of joint (JSC and contractor)
selected processes. Phase I is the investigative element of the audit,
involving knowledgeable personnel, preferably practitioners of the
process, to provide a set of data relative to variances and problems,
with the understanding that problems identified shall be corrected in a
timely manner. Phase II, conducted by an analysis team comprised of JSC
and contractor personnel, consists of a systematic review of the results
of the Phase I activities to identify symptoms of system problems. The
analysis team may identify further sampling or complete re-investigation
by the Phase I team(s) if there are concerns for the level of review
applied or significant system problems.

The contractor shall comply with JSC 23642C, JSC Fastener Integrity
Program. The contractor may utilize the JSC Receiving Inspection and
Test Facility (RITF) services for receiving inspection of externally
threaded fasteners procured for use on JSC programs. In addition, the
contractor may also use RITF receiving inspection services for metallic
and nonmetallic material properties analysis, destructive physical
analysis, failure analysis of electronic components, and screen burn-in
of electrical and electronic parts and components. Also, the contractor
may use RITF training services for nondestructive evaluation, hand
soldering, and electrostatic discharge, for personnel certification.

The contractor shall maintain a record center that is compatible with
the NASA JSC Operations and Quality Assurance Division policy (ref: JSC
Quality Management System). The record center operation shall have
electronic access which will permit interaction between the NASA JSC
SR&QA record centers and the contractor's data base for processing of
items such as historical records and authorization documents.
Effectiveness of the records system operations and procedures shall be
evaluated periodically to update and/or incorporate needed improvements.

The contractor shall assure the requirements of JSCM 1710, "Design,
Inspection, and Certification of Pressure Vessels and Pressurized
Systems," are met for all ground based Pressure Vessels/Systems (PV/S)
which are owned and/or operated by JSC and all PV/S which are used on
JSC property Specific services shall be provided the contractor by the
SR&QA Pressure Systems Manager's Office (PSMO) in accordance with the
provisions of JSCM 1710.

**15.5.22.1 Software Quality Assurance (SQA)** - The contractor shall
appoint an SQA manager who shall act as the prime interface between
QAED, the contractor, and subcontractor(s) on all matters pertaining to
software and firmware quality assurance. The contractor's SQA
organization shall be responsible for ensuring compliance with
contractual requirements, approved plans, control procedures, approved
processes, and standards for software and firmware. QAED shall conduct
periodic audits to verify compliance.

The SQA requirements are applicable to the following categories of
software and firmware: flight software and firmware; critical ground
support software and firmware, i.e., software and firmware that are an
integral part of the operational mission (i.e., support of flight
program); and software support tools used in (1) the development of
flight and critical ground support software and firmware;
(2) manufacturing processes of mission critical hardware; and (3) test
and integration of mission critical hardware, software, and firmware.

Personnel responsible for ensuring compliance with the software quality
program requirements shall have the responsibility, authority, and
organizational freedom to permit objective evaluation/audits and to
initiate and verify corrective actions.

SQA shall conduct a complete review of the technical work within this
contract to identify and make timely provisions for applying resources
and skills required to implement the SQA requirements. Prepare an SQA
plan in accordance with the requirements specified in DRD QA-009.

The contractor will implement the SQA requirements in accordance with
the approved SQA plan and adhere to the SQA requirements. Document the
SQA implementation in the form of SQA procedures. QAED may review the
contractor's SQA procedures and conduct audits as it deems necessary to
verify compliance to the SQA plan and procedures.

The contractor will conduct ongoing evaluations and compliance audits of
the standards, procedures, and processes used in development and control
of software. Verify contractual compliance of all deliverables.

The contractor will establish and maintain a record retention system to
provide an auditable record of all SQA activities and actions. The SQA
records shall be made available to QAED and their support contractor for
review and audit. The records retained shall include as a minimum:
quality assessment reports, nonconformance reports, quality assurance
activity reports, quality audit reports including completed checklists
and personnel training and certification records.

Prepare a software quality report for each quality evaluation and audit.
These reports shall be in the contractor's own format and shall contain
the following minimum information: date, SQA participants,
evaluations/audit criteria, findings, and recommended corrective
actions.

The contractor will establish nonconformance reporting and corrective
action procedures which provide for the following: (a) ensure that
action is initiated to correct the reported nonconformances; (b) monitor
the software corrective actions to ensure timely and positive corrective
actions; and (c) track and status all nonconformances and corrective
actions.

The contractor's SQA organization shall participate in the software
delivery/acceptance process, and shall certify that the
delivery/acceptance criteria have been satisfied. Identify authorized
deviations/waivers and attach copies to the certification records.

The contractor will flow down to the subcontractor(s) requirements
necessary to establish an effective SQA program within the
subcontractor's organization. The contractor's SQA organization shall
review and approve the subcontractor(s) SQA plan and procedures. The
contractor's SQA organization shall conduct periodic audits to verify
that the subcontractor is performing in accordance to the SQA plan and
procedures. The subcontractor's quality records shall be made available
for inspection by QAED.

The contractor will establish an SQA training program for all personnel
performing SQA activities on the contract. Upon completion of the
training program, all personnel shall be certified as being qualified to
perform the SQA function.

**15.5.22.2 Instrument Calibration** - Calibrate test and measurement
equipment for which the contractor is responsible in accordance with the
requirements of JSCMD 8070.1. The test equipment calibration, repair,
and recall program shall be provided to the contractor by the
Measurement Standards and Calibration Laboratory (MSCL) in accordance
with the requirements and procedures in JSCM 8070.1E. (See also clause
G.8.)

Staff and operate JSC Satellite Calibration Laboratories (SCLs) as
assigned. The authority and responsibility of each of these SCLs are
established in Section 3.3 of JSCM 8070.

15.5.23 Applicable Documents List for SR&QA

This list of documents form a part of the requirements, to the extent
specified, within the Management and Administration Statement of Work
and associated Data Requirements Description. Unless otherwise specified
the latest authorized version shall be used.

ANSI/ASQC Q9001-1994,\* American National Standard, Quality
Systems---Model for Quality Assurance in Design/Development, Production,
Installation, and Servicing

JPG 1700.1,\* JSC Safety Manual

JSC 17057, GFE Limited Cycle Time/Age Life Items Requirements

JSC 17481A, Safety Requirements Document for JSC Space Shuttle Flight
Equipment

JSC 17773, as revised, Instruction for Preparation of Hazard Analyses
for JSC Ground Operations

JSC 23642C, \* JSC Fastener Integrity Program

JSC 24636, JSC Orbiter and Government Furnished Equipment (GFE) Problem
Reporting and Corrective Action (PRACA) Requirements

JSCM 1710, \* Design, Inspection, and Certification of Pressure Vessels
and Pressurized Systems

MIL-STD-756, Reliability, Prediction, and Modeling

MIL-STD-882B, System Safety Program for Systems and Associated
Subsystems and Equipment, General Requirements for

NAS 5300.4(3G), Requirements for Interconnecting Cables, Harnesses, and
Wiring

NAS 5300.4(3H), Requirements for Crimping and wire Wrap

NAS 5300.4(3J-1), Workmanship Standard for Staking and Conformal Coating
of Printed Wiring Boards and Electronic Assemblies

ND6-94-012\* NASA/JSC letter, Subject "NAS919100 Test and Analysis
Services," April 28, 1994

NAS 5300.4(3M), Workmanship Standard for Surface Mount Technology

NHB 1700.1 (V1-B & V2)\* Guidelines for Mishap Investigation

NHB 5300.4 (1D-2), Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program

NHB 5300.4(3A-2), Requirements for Soldered Electrical Connections

NSTS 07700, Vol. V, Information Management

NSTS 08126 Space Shuttle Problem Reporting and Corrective Action (PRACA)
System Requirements

NSTS 22206, \* Instructions for Preparation of Failure Modes and Effects
Analysis and Critical Items List

NSTS 22254,\* Methodology for Conduct of Space Shuttle Program Hazard
Analyses

SN-D-0007, Space Shuttle Program Acceptance Data Package Requirements

SSP 30223, Problem Reporting and Corrective Action for the Space Station
Program

SSP 30234, Rev. D,\* Instructions for Preparation of Failure Modes
Effects and Analysis and Critical Items List for Space Station

SSP 30309, \* Safety Analysis and Risk Assessment Requirements Document

SSP 30312, EEE Parts Management and Implementation Plan

SSP 30524, Problem Reporting and Corrective Action (PRACA) Data System
(PDS) Requirements Definition Document (RDD)

SSP 30599, Revision A, Safety Review Process for Space Station

SSP 30695, Acceptance Data Package Requirements

SSP 41000, System Specification for the International Space Station,
paragraph 3.2.4

SSP 50021, Space Station Safety Requirements

SSP 50038, Computer Based Control System Safety Requirements

> \* Referenced in the M&A SOW, all other listings are referenced in the
> SRM&QA DRLs and DRDs.

**15.6 CORE COMPUTER SYSTEMS (CCS)**

This Statement of Work (SOW) element delineates the tasks of the Core
Computer Systems (CCS) effort for all NASA/JSC elements of the Lockheed
Martin Science, Engineering, Analysis, and Test (SEAT) Contract. This
SOW element replaces those references for the Engineering CCS originally
listed under Section 13.0 of the SEAT SOW. Specific work areas within
NASA/JSC Directorates under the SEAT Contract are associated with the
computer systems and services required by those Directorates and
indicated within the equipment tables of Attachments to this SOW as
contained in the CCS Master Computer Systems and Networks List
configuration control document.

Work performed under this SOW is directed toward providing Federal
Information Processing Resources (FIPR) management and maintenance for a
specified group of computer hardware and software systems and networks
within NASA/JSC Divisions, which has not specifically been set aside as
NASA or JSC center-wide work elements. The top-level objectives of the
tasks within this SOW are as follows:

• Requirements definition, analysis and service center for the CCS
sub-tasks.

• Systems management and administration of host engineering and
scientific processing computer systems (i.e. Digital Equipment
Corporation (DEC) VAX, DEC Alpha, etc.), and applicable major software
applications.

• Systems management and administration of UNIX based analytical,
engineering, and scientific computing systems, and applicable major
software applications.

• Systems management and administration of NT based analytical,
engineering, and scientific computing systems and applicable major
software applications.

• System management and administration of other operating-systems based
analytical, engineering, and scientific computer systems, including
relocation, setup, hardware and software installation and upgrades,
configuration, maintenance, and network connectivity, as applicable.

• Engineering and maintenance of network elements within laboratories of
selected Divisions (as listed

> in the SOW attachments), and network engineering customer service
> requests for Divisions as required.

• Database administration, software systems administration, and
configuration management for Division user organizations and major
software applications independent of Host, UNIX, and NT or Other
Operating Systems computer system platforms.

**15.6.1 CCS Service Center And Requirements And Analysis (WBS \#
MHEPEVCV2 and MHSPEVCV2)**

The contractor shall provide for handling of Customer Service Requests
(CSR) for new user capabilities, including appropriate requirements and
analysis, user assistance, and system trouble calls for host computer
systems, UNIX servers and workstations, NT servers and workstations,
other operating systems servers and workstations, networks, major
software applications, and applicable new technologies as described in
Attachments B through G and R of this SOW. Acquisition of hardware,
software, and maintenance for designated systems will be originated or
coordinated here.

On-line and phone access for users shall be provided. All service calls
shall be recorded in an on-line reporting system, which shall enable
generation of metrics for performance determination. Response to user
calls (either critical or non-critical) shall be performed in accordance
with the criticality described for that system in Attachments B through
G. Systems engineering and analysis, related to requirements and new
capabilities, shall be provided under this sub-task. The contractor
shall participate in meetings and discussions regarding network reviews,
risk analysis, ISO 9000 process, security, FIPR, Year 2000 Compliance,
and other topics that might affect the supported areas. Coordination
with NASA/JSC Division IRM representatives, and other NASA/JSC
contractors shall be required in support of new capabilities and problem
resolutions.

The contractor shall be an active participant in user groups associated
with major engineering and Scientific investments, such as DEC, HP,
Oracle, PDM/ProE, NT Security, and others as appropriate. This
participation includes, but is not limited to, representing NASA/CCS at
users group meetings, exchange technology updates between users and
NASA/CCS, sharing lessons learned and best practices with the user
community via NASA/CCS-to-other users and NASA/CCS-to-vendor
face-to-face interactions where available for maximum information
exchange, and discussing NASA/CCS major problems to identify problem
resolutions and formulating technology strategies for the future.

All non-critical customer service requests shall be responded to within
the designated number of working hours of the request being entered into
the CCS on-line reporting system. Working hours will be determined
exclusive of NASA/JSC and Contractor holidays and weekends. For critical
systems, response will be delivered within the designated time period
upon receipt of the service call at the CCS service center. Response
time designations are listed in Attachments B through G.

Where dedicated back-ups for critical systems are supported by this CCS
sub-task, these systems shall be provided as \"test and support ready,\"
according to an agreed upon test support and back-up plan. Examples of
critical systems are those such as FIPR used in an in-line manner in
critical tests or for mission support.

The preparation of a requirements and analysis document or a large
computer system acquisition package shall include, but not be limited
to, requirements fom1ulation, market survey, analysis, alternatives, and
recommendation. Upon approval of the recommendation, an acquisition
package shall include purchase requisition(s) and applicable sole source
justifications, specifications, and statements of work.

Each minor purchase requisition shall include a one page sole source
letter of justification as applicable.

Effective October 1, 1998, all items delivered under this task order are
required to be year 2000 compliant.

The contractor shall coordinate, conduct, and participate in the
preparation of JSC risk management plans (which include risk analysis,
sensitive applications, disaster recovery, and end-user contingency
plans), JSC Information Technology (IT) security plans, and annual
updates of the respective plans designated in Attachment R. The plans
shall include the general support systems (GSS) for respective
Engineering Directorate Division and the respective Space and Life
Sciences Directorate Division. The plans shall be prepared and certified
in accordance with the JSC IT security handbook (JPG 2810.1).

The contractor shall attend JSC computer security meetings and
disseminate relevant security information, define and coordinate
implementation of computer security controls and monitoring
requirements, provide coordination of incident response activities,
including determining the exploit remediation requirements, liaison
between system administration personnel and the NASA Center Computer
Security Manager and the NASA Office of the Inspector General, provide
input to organizational incident response reporting requirements, and
coordinate response to data call requirements as defined by the JSC
Center Computer Security Manager.

The contractor may be required to distribute software and documentation
either in hard copy form, or via electronic media such as magnetic tape,
floppy disk, and CD-ROM, or via telecommunication protocols such as FTP
and HTTP. This distribution is authorized under the Lockheed Martin
Science, Engineering, Analysis, and Test (SEAT) contracting officer\'s
letter of export authorization, \"Export Control guidance, NAS9-19100,\"
BE-035, dated December 23, 1996.

**15.6.2 Host Computer Systems (WBS \# MHEPEVCV3 and MSHEPEVCV3)**

The contractor shall provide resident systems management and
administration functions for host computer systems (i.e. DEC VAX, DEC
Alpha, etc.), including file and print services, systems and
applications software installation and administration, hardware and
software maintenance liaison, backups, and user accounts. The contractor
shall provide database administration and user application support; e.g.
Oracle database administration, configuration management or ISO 9000
software tool support, for those systems requiring Category L5 support
per Attachment B. Response to user calls (either critical or
non-critical) shall be performed in accordance with the criticality
described for that system in Attachment B.

Services for high speed printers will be limited to those served by the
systems listed in Attachment B, and will consist of host printer queue
management, which includes creating, stopping, resetting and restarting
queues. Service provided shall also include participation in the
planning and implementation of the consolidation of the DEC VAX host
computer systems. Limited applications software evaluation, analysis,
and problem resolution shall be provided under this CCS sub-task.
Problem resolution for host interactions with other institutional
computing elements will be coordinated with the current office
automation contractor.

The contractor shall attend and participate in local, national, and
international user group meetings related to current and future major
NASA/JSC technology investments as supported by this functional area,
such as Hewlett-Packard HP World, DEC User Group (DECUS), Oracle,
PDM/Pro-E, NT Security, etc.

The CCS system administrators shall participate in the identification of
year 2000 compliance issues, and shall coordinate with vendors for year
2000 hardware and operating system software upgrades and warrantees;
consultation only shall be provided for the testing and certification of
the computer systems.

System security monitoring, identification of security issues, and
reporting security issues to JSC Center

and Division personnel are required of the system administrators.
Consultation only shall be provided for the investigation of security
breaches and the implementation of corrective actions.

**15.6.3 UNIX Workstations (WBS \# MHEPEVCV4 and MHSPEVCV4)**

The contractor shall provide systems management and administration
functions for UNIX servers and workstations, including file and print
services, systems and applications software installation and
administration, hardware and software maintenance liaison, backups, and
user accounts. The contractor shall provide engineering and scientific
software application support; e.g. Pro-E, UNIGRAPHICS, I-DEAS,
configuration management or ISO 9000 software tool support, for those
systems requiring Category L5 support per Attachment C. Response to user
ca1ls (either critical or non-critical) shall be performed in accordance
with the criticality described for that system in Attachment C. Services
for printers will be limited to those served by the systems listed in
Attachment C and will consist of host printer queue management, which
includes creating, stopping, resetting and restarting queues. Co-located
systems administration services shall be provided to the supported area
when necessary. Limited applications software evaluation, analysis, and
problem resolution shall be provided under this CCS sub-task.
Client/server problem resolution will be coordinated with the current
office automation contractor, as applicable.

The contractor shall attend and participate in local, national, and
international user group meetings related to current and future major
NASA/JSC technology investments as supported by this functional area,
such as Hewlett-Packard HP World, DEC User Group (DECUS), Oracle,
PDM/Pro-E, NT Security, etc.

The CCS system administrators shall participate in the identification of
year 2000 compliance issues, and shall coordinate with vendors for year
2000 hardware and operating systems software upgrades and warrantees;
consultation only shall be provided for the testing and certification of
the computer systems.

System security monitoring, identification of security issues, and
reporting security issues to JSC Center and Division personnel are
required of the system administrators. Consultation only shall be
provided for the investigation of security breaches and the
implementation of corrective actions.

**15.6.4 NT Workstations (WBS \# MHEPEVCV6 and MHSPEVCV6)**

The contractor shall provide systems management and administration
functions for NT servers and workstations, including file and print
services, systems and applications software installation and
administration, hardware and software maintenance liaison, backups, and
user accounts. The contractor shall provide engineering and scientific
software application support; e.g. Pro-E, UNIGRAPHICS, I-DEAS,
configuration management or ISO 9000 software tool support, for those
systems requiring

Category L5 support per Attachment D. Response to user ca1ls (either
critical or non-critical) shall be performed in accordance with the
criticality described for that system in Attachments D. Services for
printers will be limited to those served by the systems listed in
Attachment D and will consist of host printer queue management, which
includes creating, stopping, resetting and restarting queues. Co-located
systems administration support will be provided to the supported area as
necessary. Limited applications software evaluation, analysis, and
problem resolution shall be provided under this CCS sub-task.
Client/server problem resolution will be coordinated with the current
office automation contractor, as applicable.

The contractor shall attend and participate in local, national, and
international user group meetings related to current and future major
NASA/JSC technology investments as supported by this functional area,
such as Hewlett-Packard HP World, DEC User Group (DECUS), Oracle,
PDM/Pro-E, NT Security, etc.

The CCS system administrators shall participate in the identification of
year 2000 compliance issues, and shall coordinate with vendors for year
2000 hardware and operating system software upgrades and warrantees;
consultation only shall be provided for the testing and certification of
the computer systems.

System security monitoring, identification of security issues, and
reporting security issues to JSC Center and Division personnel are
required of the system administrators. Consultation only shall be
provided for the investigation of security breaches and the
implementation of corrective actions.

**15.6.5 Other Operating Systems Workstations (WBS \# MHEPEVCV7 and
MHSPEVCV7)**

The contractor shall provide systems management and administration
functions for other operating systems servers and workstations,
including file and print services, systems and applications software
installation and administration, software licenses configuration
control, E-mail, IT security, hardware and software maintenance liaison,
backups, and user accounts as applicable, relocation, setup,
configuration, and network connectivity. The contractor shall provide
engineering and scientific software application support; e.g. E-mail,
Pro-E, UNIGRAPHICS, I-DEAS, configuration management or ISO 9000
software tool support, for those systems requiring Category L5 support
per Attachment E. Response to user calls (either critical or
non-critical) shall be performed in accordance with the criticality
described for that system in Attachment E. Co-located systems
administration support will be provided to the supported area as
necessary. Limited applications software evaluation, analysis, and
problem resolution shall be provided under this CCS sub-task.
Client/server problem resolution will be coordinated with the current
office automation contractor, as applicable.

The contractor shall attend and participate in local, national, and
international user group meetings related to current and future major
NASA/JSC technology investments as supported by this functional area,
such as Hewlett-Packard HP World, DEC User Group (DECUS), Oracle,
PDM/Pro-E, NT Security, etc.

The CCS system administrators shall participate in the identification of
year 2000 compliance issues, and shall coordinate with vendors for year
2000 hardware and operating system software upgrades and warrantees;
consultation only shall be provided for the testing and certification of
the computer systems.

System security monitoring, identification of security issues, and
reporting security issues to JSC Center and Division personnel are
required of the system administrators. Consultation only shall be
provided for the investigation of security breaches and the
implementation of corrective actions.

**15.6.6 Networks (WBS \# MHEPEVCV5 and MHSPEVCV5)**

The contractor shall provide systems management and administration
functions for networks designated as CCS service areas, including
hardware and performance maintenance. Response to user calls (either
critical or non-critical) shall be performed in accordance with the
criticality described for that system in Attachment F. Insta1lation and
upgrading of networks within laboratory and test facilities are provided
under this CCS sub-task. Installation and upgrading of office automation
networks are normally excluded from this SOW and should be coordinated
with the current office automation contractor. Service provided under
this SOW will also include participation in the planning and
implementation of any connections between the networks of the laboratory
and test areas supported and the NASA/JSC institutional network.
Inter-network problem resolution shall be coordinated with the current
office automation contractor, as applicable.

Each of the configuration documents for networks and network segments
maintained by The contractor (see Attachment F), shall be updated on a
quarterly basis.

Network consulting shall be provided to all NASA/JSC Divisions within
the SEAT Contract in response to their CSR. Twelve (12) one-man-month (1
mm) facility network designs, or twenty six (26) one-man-week (1 mw)
problem evaluations and resolutions, or a combination of these should be
expected in addition to those network elements listed in Attachment F.

The contractor shall attend and participate in local, national, and
international user group meetings related to current and future major
NASA/JSC technology investments as supported by this functional area,
such as Hewlett-Packard HP World, DEC User Group (DECUS), Oracle,
PDM/Pro-E, NT Security, etc.

The CCS system administrators shall participate in the identification of
year 2000 compliance issues, and shall coordinate with vendors for year
2000 hardware and operating system software upgrades and warrantees;
consultation only shall be provided for the testing and certification of
the computer systems.

System security monitoring, identification of security issues, and
reporting security issues to JSC Center and Division personnel are
required of the system administrators. Consultation only shall be
provided for the investigation of security breaches and the
implementation of corrective actions.

**15.6.7 Major Software Applications (WBS \# MHEPEVCV8 and MHSPEVCV8)**

The contractor shall provide database administration, systems
administration, WEB page support, and configuration management for major
software applications independent of hardware platforms. Per Attachment
G, Division Software Applications, such as Task Order Planning System,
ProE, Unigraphics, I-DEAS, and Oracle Database, shall be maintained.

The contractor shall maintain Software Configuration Control Centers
(SCCC) as specified in Attachment G to include the operation of a
software library and operation and maintenance of a keyed application
server. The library functions include signing out software to authorize
personnel and keeping all cabinets cards updated; installing keyed
software on the server, desktop machines, and laptops used for travel;
responding to user requests for assistance with programming problems or
other software related problems like unreadable files; downloading virus
update, and providing security oversight for the software center.

The contractor shall provide shared area support to include hardware and
system requirements to administer and maintain computer share areas as
specified in Attachment G. Support shall consist of requesting user
access/removal of access privileges, maintaining the access list of
users, receiving user request forms, verifying authorization, providing
tracking information for request, and confirming with users that
accounts have been set up and they received instructions for access to
the shared areas.

The contractor shall attend and participate in local, national, and
international user group meetings related to current and future major
NASA/JSC technology investments as supported by this functional area,
such as Hewlett-Packard HP World, DEC User Group (DECUS), Oracle,
PDM/Pro-E, NT Security, etc.

The CCS system administrators shall participate in the identification of
year 2000 compliance issues, and shall coordinate with vendors for year
2000 hardware and operating system software upgrades and warrantees;
consultation only shall be provided for the testing and certification of
the computer systems.

System security monitoring, identification of security issues, and
reporting security issues to JSC Center and Division personnel are
required of the system administrator. Consultation only shall be
provided for the investigation of security breaches and the
implementation of corrective actions.

**15.6.8 Integration**

This SOW and its sub-tasks provides services in support to major
computer related consolidation efforts, such as the DEC VAX
consolidation effort currently in progress at NASA/JSC. As part of this
VAX consolidation effort, all special application functions, e.g.,
FORTRAN, Ada, C, etc., shall be transitioned to contractor managed host
computer systems.

The contractor shall provide services that may cross Directorate,
Division and contractor boundaries. In accomplishing work elements,
interaction and coordination with other NASA/JSC Directorates,
contractors and organizations shall be required. The CCS service center
shall provide initial contact in these cases.

The contractor shall plan and implement all responsible redesign,
upgrade, and hardware and software replacement activities in a
coordinated manner. ISD standards and conventions will be utilized to
ensure consistency with integrated NASA/JSC computer systems, network
management, and systems operations.

**15.6.9 Testing, Verification, and Certification**

No special facilities, hardware, or software are required for testing,
verification, and certification of systems within this SOW. However, a
UNIX workstation node and/or a NT workstation node shall be identified
for on-site parallel testing and verification of hardware and software
upgrades, enhancements, and standard installations as necessary. The
designated equipment shall be made available or provided by the
Government.

A network analyzer system shall be provided for the test, verification,
and measurement of network connectivity and performance. This system
shall be utilized in selected laboratory areas. This equipment was
procured under the FY97 ECCS task order and shall be provided by the
Government.

**15.6.10 NASA Input Requirements**

The following facilities and equipment will be provided and made
available by the Government in the performance of this SOW:

• Division CCS host computer systems.

• Division CCS UNIX servers and workstations.

• Division CCS NT servers and workstations.

• Division CCS other operating systems servers and workstations.

• Division CCS laboratory networks.

• Division CCS major software applications, shared areas, and software
configuration control center (SCCC)

• Desk and telephone with voice mail on-site for each contractor person
supporting the SOW.

• GFE desktop systems, including hardware and software and network
connectivity, for each onsite contractor person supporting the SOW.
Software will include MS-Exchange, MS-office, a full function terminal
emulator, and other software provided as the Standard Load by ISD for
desktop workstations.

  ------------ ---------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------
  Functional   Division   System/Network   Operating   NEMS \#   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                    System                            Support                   System                

  UNIX         SN         SGI INDIGO 2     IRIX 6.2    1550363   EOL-DEV               1                          10/01/98   12/31/03
                          HIGH IMPACT                                                                                        

  UNIX         SN         SGI OCTANE       IRIX 6.4    1917672   ERSAF                 1               C          10/01/98   12/31/03

  UNIX         SN         SGI INDIGO 2     IRIX 5.3    1543071   ODASDEV               1               C          10/01/98   12/31/03

  UNIX         SN         SGI INDIGO       IRIX 5.3    1543072   ODASIND1              1                          10/01/98   12/31/03

  UNIX         SN         SGI INDIGO       IRIX 5.3    1543073   ODASIND2              1                          10/01/98   12/31/03

  UNIX         SN         SGI/CHALLENGE L  IRIX 5.3    1543070   ODASPRO               1               C          10/01/98   12/31/03

  UNIX         SN         SGI/O2           IRIX 5.3    1917937   POLARIS               1                          10/01/98   12/31/03

  UNIX         SN         HP 700           HP/UX 9.05  1118697   SHOCK1                1                          10/01/98   12/31/03

  UNIX         SN         SGI/INDIGO       IRIX 6.2    1240396   SSINDY                1                          10/01/98   12/31/03

  UNIX         SN         SGI/02           IRIX 6.3    1846970   VDAS-1                1                          10/01/98   12/31/03

  UNIX         SN         SGI/02           IRIX 6.3    1846969   VDAS-2                1                          10/01/98   12/31/03

  UNIX         SN         SGI/REALITY      IRIX 6.2    1544646   VDAS-DEV              1               C          10/01/98   12/31/03
                          STATION                                                                                            

  UNIX         SN         SGI/ONYX         IRIX 6.2    1544642   VDAS-OPS              1               C          10/01/98   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT WORKSTATION   WIN NT                AUTO CAD    1                                    10/01/97   12/31/03

  NT           EC         NT SERVER        WIN NT 4.0  1453145   BRAD 2      1                         C          10/01/97   12/31/03

  NT           EC         NT SERVER        WIN NT                CONFIG      1                         C          10/01/97   12/31/03
                                                                 CONTROL                                                     

  NT           EC         NT SERVER        WIN NT 4.0  1918003   CTSD-32BQ   1                         C          10/01/98   12/31/03
                                                                 FC1                                                         

  NT           EC         NT SERVER        WIN NT 4.0  1919349   CTSD_32TO   1                         C          10/01/98   12/31/03
                                                                 SHIBA1                                                      

  NT           EC         NT SERVER        WIN NT 4.0  1919167   CTSD_33BQ   1                         C          10/01/98   12/31/03
                                                                 FC1                                                         
  ------------ ---------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------

  ------------- ----------- ---------------- ----------- --------- ----------------- --------- --- --- --- ----- ---------- ---------- ----------
  Func-tional   Divi-sion   System/Network   Operating   NEMS \#   Node/Name         Level of                    Critical   Start Date End Date
  Areas                                      System                                  Support                     System                

  NT            EC          NT SERVER        WIN NT 4.0  1847520   CTSD_7BQF C1      1                           C          10/01/98   12/31/03

  NT            EC          PC               PC/NT                 CTSDPC1           1                           C          10/01/98   12/31/03

  NT            EC          PC               NT/WS                 CTSDPC3           1                           C          10/01/98   12/31/03

  NT            EC          NT WORKSTATION   WIN NT 4.0            EC_20FT_01        1                     1     C          8/01/98    12/31/03

  NT            EC          NT WORKSTATION   WIN NT4.0             EC_20FT_02        1                     1                8/01/98    12/31/03

  NT            EC          NT SERVER        WIN/NT4.0             EC_20FT_03        1                                      8/01/98    12/31/03

  NT            EC          NT WORKSTATION   WIN/NT4.0             EC_20FT_04        1                     1                8/01/98    12/31/03

  NT            EC          NT WORKSTATION   WIN/NT4.0             EC_20FT_05        1                     1                8/01/98    12/31/03

  NT            EC          NT SERVER        WIN/NT4.0             EC_20FT_06        1                                      8/01/98    12/31/03

  NT            EC          NT SERVER        WIN/NT4.0             EC_20FT_07        1                                      8/01/98    12/31/03

  NT            EC          NT SERVER        WIN/NT4.0             EC_20FT_08        1                                      8/01/98    12/31/03

  NT            EC          NT SERVER        WIN/NT4.0             EHT-TD            1                     1                3/01/98    12/31/03

  NT            EC          NT SQL SERVER    WIN NT                ENGR DB           1                     1     C          10/01/97   12/31/03

  NT            EC          NT SQL SERVER    WIN NT      1848074   FIX (TTA)         1                           C          10/01/97   12/31/03

  NT            EC          NT SERVER        WIN NT 4.0            HIPERGATE         1                     1     C          6/30/98    12/31/03

  NT            EC          NT SERVER        WIN NT 4.0  1917460   JSC_ENG_C TSD     1                           C          10/01/98   12/31/03

  NT            EC          NT SERVER        WIN NT 4.0  1874526   JSC-ENG_C CTSD1   1                           C          10/01/98   12/31/03

  NT            EC          NT SERVER        WIN NT 4.0  1543340   JSC-ENG- EC-BDC   1                     1     C          10/01/98   12/31/03

  NT            EC          NT SERVER        WIN NT 4.0  1543911   JSC-ENG-EC-PDC    1                     1     C          10/01/98   12/31/03

  NT            EC          NT SQL SERVER    WIN NT                OASIS             1                           C          10/01/97   12/31/03

  NT            EC          NT SQL SERVER    WIN NT                OASIS             1                           C          10/01/97   12/31/03

  NT            EC          NT SQL SERVER    WIN NT                OASIS             1                           C          10/01/97   12/31/03

  NT            EC          NT SQL SERVER    WIN NT                TTA               1                           C          10/01/97   12/31/03

  NT            ES          NT WORKSTATION   WIN NT4.0             ABBAS-SHEILA      1                     1     C          8/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            ANDERSON-THOMAS   1                     1     C          3/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            BACCUS- RON-K     1                     1     C          3/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            BOUCHER-MIKE-F    1                     1     C          6/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            BRANDT-MAVIS      1                     1     C          8/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            BRISCOE-TIMOTHY   1                     1     C          6/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            BROWN-BOBBIE      1                     1     C          8/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            BUFKIN- ANN-L     1                     1     C          8/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            CAO-TIMOTHY       1                     1     C          6/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            CEGIELSKI-D       1                     1     C          8/01/98    12/31/03

  NT            ES          NT WORKSTATION   WIN NT 4.0            CRUZ-SANTANA-F    1                     1     C          3/01/98    12/31/03
  ------------- ----------- ---------------- ----------- --------- ----------------- --------- --- --- --- ----- ---------- ---------- ----------

<table>
<colgroup>
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 9%" />
<col style="width: 6%" />
<col style="width: 11%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 9%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>DAO-ANTHONY-X</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>DAVIS-ROBERT-E1</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>DAVIS-WILLIAM-M</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>DELACRUZ-PAM</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>DELPAPA-STEVEN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>DINH-ADAM-D</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>EDEEN-GREGG-A</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>EDELSTEIN-KAREN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES2OPEN1</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP1</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP10</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP11</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP12</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP2</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP-222</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP3</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP5</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP6</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP7</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP8</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ES-COOP9</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>FANTASIA-PETE-M</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>FOGT-VINCENT-A</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>GAFKA-GEORGE-K</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>06/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>GALBREATH-GREG</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>GESSLER-</p>
<p>JOE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>GRACIA-JUNIOR</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>08/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>GRYGIER-MICHAEL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>03/01/98</td>
<td>12/31/03</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 9%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Criti-cal System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HAGEN-JEFF-D</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HANSEN-CHRIS-P</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HARRIS-WANISHA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HARTZ-LESLIE-S</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HEIM-</p>
<p>JASON-A</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HESS-</p>
<p>LINDA-F</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HONG-ANDREW-E</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HSU-SY-</p>
<p>YUEN</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JENSEN-SCOTT</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JERMSTAD-WAYNE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JOHNSON-CHRIS</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JOHNSON-PAMELA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>KENNEDY-JOHN-J</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>KING-GUY-L</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>KOWAL-</p>
<p>JOHN-T</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>KOWAL-MARIE-A</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>LANDECK-MARK-E</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>LESTER-JAMES-D</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>LEWIS-</p>
<p>JAMES-L</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>LONG-</p>
<p>TAMMY-L</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>LUPO-</p>
<p>CHRIS-P</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>MADDEN-CHRIS-B</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>NAKAYAMA-GLEN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>OHERREN-BILL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ORTIZ-CARLOS</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>OVERSTREET-GALE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>PADRON-JUAN-J</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 16%" />
<col style="width: 10%" />
<col style="width: 7%" />
<col style="width: 12%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 9%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HARRIS-WANISHA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HARTZ-</p>
<p>LESLIE-S</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HEIM-</p>
<p>JASON-A</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HESS-</p>
<p>LINDA-F</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>HONG-ANDREW-E</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>HSU-SY-</p>
<p>YUEN</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JENSEN-SCOTT</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JERMSTAD-WAYNE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JOHNSON-CHRIS</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JOHNSON-PAMELA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>KENNEDY-JOHN-J</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>KING-GUY-L</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>KOWAL-</p>
<p>JOHN-T</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>KOWAL-</p>
<p>MARIE-A</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>LANDECK-MARK-E</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>LESTER-JAMES-D</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>LEWIS-</p>
<p>JAMES-L</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>LONG-</p>
<p>TAMMY-L</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>LUPO-</p>
<p>CHRIS-P</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>MADDEN-CHRIS-B</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>NAKAYAMA-GLEN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>OHERREN-</p>
<p>BILL</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>ORTIZ-</p>
<p>CARLOS</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>OVERSTREET-GALE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>PADRON-JUAN-J</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>PATIN-RAYMOND-M</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>PREWITT-MARY-L</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 16%" />
<col style="width: 13%" />
<col style="width: 8%" />
<col style="width: 14%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td><p>Func-</p>
<p>tional</p>
<p>Areas</p></td>
<td><p>Divi-</p>
<p>sion</p></td>
<td><p>System/</p>
<p>Network</p></td>
<td><p>Operating</p>
<p>System</p></td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="6">Level of Support</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>RABOIN-</p>
<p>JASEN-L</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>REEVES-JENNIFER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>REYNA-</p>
<p>JEREMY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>RIED-SONIA-</p>
<p>L</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ROBERTSON-BRAND</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>SANDELL-BRITNEY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>6/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>SCHLIESING-JOHN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>SINGH-BHUMINDER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>SMD111-</p>
<p>B13-2002</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>SMD113</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>SMD114</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>STURM-JAMES-A</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>TAYLOR-</p>
<p>PETE-A</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>TSAI-TED-W</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>TYREE-WARREN-C</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>VALLE-GERARD-D</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>WHITCOMB-SHARON</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>WONG-KENNETH</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>3/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38-INTEGRATION</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38ST1</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38ST2</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38ST3</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38ST4</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38ST5</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38ST6</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38-STRU2</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>X38-STRU3</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>ES</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>ZAVALA-</p>
<p>ANGIE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 9%" />
<col style="width: 7%" />
<col style="width: 13%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 9%" />
<col style="width: 9%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EV</td>
<td>NT SERVER</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>CCS</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EV</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>CTNT1</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EV</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>CTNT2</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EV</td>
<td>NT SERVER</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ESTL_NT</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td></td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EV</td>
<td>NT SERVER</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>ESTL_NTS-1</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td></td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EV</td>
<td>NT SERVER</td>
<td>WIN NT 4.0</td>
<td>1919092</td>
<td><p>JSC-CCS-</p>
<p>KS1</p></td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1 </td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EV</td>
<td>NT SERVER</td>
<td>WIN NT 4.0</td>
<td>1918431</td>
<td><p>JSC-CCS-</p>
<p>WEB1</p></td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1 </td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EV</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>TCC1-1</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EV</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>TCC1-2</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EV</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>TCC2-1</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EV</td>
<td>NT WORKSTATION</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>TCC2-2</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EX</td>
<td>NT SERVER</td>
<td>WIN NT</td>
<td> </td>
<td>C3PO</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EX</td>
<td>NT SERVER</td>
<td>WIN NT</td>
<td> </td>
<td>JSCIDC7</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>EX</td>
<td>NT WORKSTATION</td>
<td>WIN NT</td>
<td> </td>
<td>UNKNOWN</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>HA</td>
<td>NT SERVER</td>
<td>WIN NT</td>
<td> </td>
<td>TECHTRACS</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>SM</td>
<td>NT SERVER</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>SCCC</td>
<td>1</td>
<td></td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>8/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>SN</td>
<td>SAG DUAL PENTIUM PRO SERVER</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>EOL-MAPS</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>SN</td>
<td>P5-166</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>JSCSNCHAR</p>
<p>ON</p></td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>SN</td>
<td>P5-233</td>
<td>WIN NT 4.0</td>
<td> </td>
<td>JSC-SN-IO</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>SN</td>
<td>HP NETSERVER 5/66 LC</td>
<td>WIN NT 4.0</td>
<td> </td>
<td><p>SN-</p>
<p>GANYMEDE</p></td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>SN</td>
<td>HP NETSERVER 5/66 LC</td>
<td>NOVELL NETWARE 3.12</td>
<td> </td>
<td>SN-TITAN</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>SN</td>
<td>HP NETSERVER 4/66 LC</td>
<td>NOVELL NETWARE 3.12</td>
<td> </td>
<td>SN-TRITON</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>NT</td>
<td>SN</td>
<td>DELL DIMENSION XPS 266 MHz</td>
<td>NT W/S</td>
<td> </td>
<td>SRAG_NT</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>NT</td>
<td>SN</td>
<td>PENTIUM II</td>
<td><p>WIN NT 4.0</p>
<p>(SERVER)</p></td>
<td></td>
<td>SX100PC</td>
<td></td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 13%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 11%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 10%" />
<col style="width: 9%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh</td>
<td> </td>
<td>30023 PARKER, WENDY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3010</td>
<td>Macintosh</td>
<td> </td>
<td><p>30219 MONEY,</p>
<p>ART</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td>30472 NGUYEN, HEATHER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3028</td>
<td>Macintosh</td>
<td> </td>
<td>30554 QE (Regina Senegal)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3017</td>
<td>PC</td>
<td> </td>
<td>30691 DIFARD, BECKY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>30964 BOUDREAX, TONY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td>31170 LOOS, ERIK</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3011</td>
<td>Macintosh</td>
<td> </td>
<td>31353 LANIER, RANDY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh</td>
<td> </td>
<td>31631 PALMITER, JANA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 115</td>
<td>Macintosh</td>
<td> </td>
<td><p>32441</p>
<p>COEN, GEOFFREY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 103</td>
<td>Macintosh</td>
<td> </td>
<td>32573 LI, LOUISE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 104</td>
<td>Macintosh</td>
<td> </td>
<td>32574 LEI, GRACE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 100</td>
<td>Macintosh</td>
<td> </td>
<td>32591 AMBERBOY, CLIF</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 102</td>
<td>Macintosh</td>
<td> </td>
<td>32607 MUECKE, DAVID</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 104</td>
<td>Macintosh</td>
<td> </td>
<td>32612 CHARLES, HUONG</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 103</td>
<td>Macintosh</td>
<td> </td>
<td>32621 CHENG, JEAN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 106</td>
<td>Macintosh</td>
<td> </td>
<td>32631 AL-HAJAS, AMJAD</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1006</td>
<td>Macintosh</td>
<td> </td>
<td>32632 BOND (MARY MCKEEN)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2008</td>
<td>Macintosh</td>
<td> </td>
<td><p>32687</p>
<p>WORK,</p>
<p>KELLY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3013</td>
<td>Macintosh</td>
<td> </td>
<td>32741 FOX, JAKE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3013</td>
<td>Macintosh</td>
<td> </td>
<td>32741 WALLACE, LARRY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Functional Areas</td>
<td>Division</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>104A</td>
<td>Macintosh</td>
<td> </td>
<td>32769 SORTO, SYLVIA (FLORES)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3015</td>
<td>Macintosh</td>
<td> </td>
<td>33013 PALACIOS, GEORGE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 104</td>
<td>Macintosh</td>
<td> </td>
<td>33027 JOSEPH, KENDRA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1005A</td>
<td>Macintosh</td>
<td> </td>
<td>33028 PEDRO, MAXINE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>33070 PATHAK, AMIT</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3027</td>
<td>Macintosh</td>
<td> </td>
<td>33234 KULHANJIA,N, ARA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 105</td>
<td>Macintosh</td>
<td> </td>
<td>33249 LEYMAN, AL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1002AA</td>
<td>Macintosh</td>
<td> </td>
<td>33353 HAWKINS, MARTIN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 104</td>
<td>Macintosh</td>
<td> </td>
<td>33504 BENNETT, RON</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>33596 CATHRINER, VALERIE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1006A</td>
<td>Macintosh</td>
<td> </td>
<td>34433 QAS (Dwayne Robinson)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1002AA</td>
<td>Macintosh</td>
<td> </td>
<td>34487 LACOUNT, BEN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh</td>
<td> </td>
<td>34573 EUSTAQUIO, ERNESTO</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1006</td>
<td>Macintosh</td>
<td> </td>
<td>34682 BOND (ALFREDO CAVALLO)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3011</td>
<td>Macintosh</td>
<td> </td>
<td>34898 RUIZ, BRANDON</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td><p>35397</p>
<p>SCOTT,</p>
<p>GENE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3024</td>
<td>Macintosh</td>
<td> </td>
<td>35398 HARTWICK, GEORGE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3015</td>
<td>Macintosh</td>
<td> </td>
<td>35399 HOLMAN, ROBERT</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 103</td>
<td>Macintosh</td>
<td> </td>
<td><p>35740</p>
<p>MILLS,</p>
<p>TRENT</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 11%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 13%" />
<col style="width: 7%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 9%" />
<col style="width: 14%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3030</td>
<td>Macintosh</td>
<td> </td>
<td><p>35825</p>
<p>GARZA,, MANUEL</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2008</td>
<td>Macintosh</td>
<td> </td>
<td><p>35955</p>
<p>DeLEON, ARMANDO</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3034</td>
<td>Macintosh</td>
<td> </td>
<td>36195 SILVAGNOLI, FELIX</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td>36292 COONER, MORGAN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td><p>36292</p>
<p>MUNEZ,</p>
<p>CHRIS</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td><p>36292 SCYPION,</p>
<p>DON</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>37058 BARNER,</p>
<p>DAVE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3024</td>
<td>Macintosh</td>
<td> </td>
<td>37199 CANGELOSI, SAL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1005A</td>
<td>Macintosh</td>
<td> </td>
<td>37215 GEORGE, JOANNE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3024</td>
<td>Macintosh</td>
<td> </td>
<td>37219 MALLERY, DAVIS</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1003</td>
<td>Macintosh</td>
<td> </td>
<td><p>37311</p>
<p>DAVIS, SIMONE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh</td>
<td> </td>
<td><p>37325</p>
<p>GUMM, SUE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td>37350 BENTON, MICHAEL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 105</td>
<td>Macintosh</td>
<td> </td>
<td>37351 BEJARANO, JOE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1005A</td>
<td>Macintosh</td>
<td> </td>
<td>37355 KREINHOP, KAY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>37358 COOPER, SALLY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>37358 DOBSON, SHELIA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>37358 DORRIAN, FRANCES</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>37358 MIDDLETON, KIM</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>37359 CRAWFORD, EVA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 14%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>37359</p>
<p>SHERER, ORVILLA</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>37359</p>
<p>SMITH,</p>
<p>CLIFTON</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>37359</p>
<p>STAHL,</p>
<p>JOHNNY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh </td>
<td> </td>
<td><p>37360</p>
<p>PERREN,</p>
<p>TERRY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 115</td>
<td>Macintosh </td>
<td> </td>
<td><p>37363</p>
<p>HALEY, TIM</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td>37366 LAJAUNIE, KELLY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3012</td>
<td>Macintosh </td>
<td> </td>
<td><p>37368</p>
<p>KELLER,</p>
<p>JOHN</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1006</td>
<td>Macintosh</td>
<td> </td>
<td>37369 BOND (SHARNETTE BASS)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1006</td>
<td>Macintosh</td>
<td> </td>
<td>37373 BOND (AMANDA PEARSON)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1006</td>
<td>Macintosh</td>
<td> </td>
<td><p>37373</p>
<p>BOND (MAE JOHNSON)</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3022A</td>
<td>Macintosh</td>
<td> </td>
<td>37387 SPRAYBERRY, CHUCK</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td><p>37389</p>
<p>DILLON,</p>
<p>CARL</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td><p>37416</p>
<p>POWELL,</p>
<p>CRAIG</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3024</td>
<td>Macintosh</td>
<td> </td>
<td>37418 KING, PAUL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3022</td>
<td>Macintosh</td>
<td> </td>
<td>37426 CROWHURST, NANCY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3015</td>
<td>Macintosh </td>
<td> </td>
<td><p>37432</p>
<p>REESE,</p>
<p>VICKI</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2018A</td>
<td>Macintosh</td>
<td> </td>
<td><p>37439</p>
<p>YELLE, WIL</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3035</td>
<td>Macintosh</td>
<td> </td>
<td>37440 KLEVELAND, KARA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3014</td>
<td>Macintosh</td>
<td> </td>
<td><p>37442</p>
<p>IVANHOE, WHITNEY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh</td>
<td> </td>
<td><p>37446</p>
<p>JEN,</p>
<p>DANNIS</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 9%" />
<col style="width: 6%" />
<col style="width: 14%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Division</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3017</td>
<td>Macintosh</td>
<td> </td>
<td><p>37549</p>
<p>MARKS,</p>
<p>DIANE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>37464</p>
<p>WINES, JIM</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1006A</td>
<td>Macintosh</td>
<td> </td>
<td>37473 QAS (Mike Justice)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td>37550 SHANNON, CAROLINE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td><p>37560</p>
<p>MEYER, THOMAS</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1005A</td>
<td>Macintosh</td>
<td> </td>
<td><p>38776 MORELLO,</p>
<p>TIM</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3034</td>
<td>Macintosh</td>
<td> </td>
<td>38780 FITZGERALD, HUGH</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3014A</td>
<td>Macintosh</td>
<td> </td>
<td>39065 TABIBIAN, HAMID</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>39686 COY, JAMES</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>39686</p>
<p>GEISSEN, GASCHEN</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>39686</p>
<p>WILSON, STEVEN</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>39687 CASTRILLON, OSCAR</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>39940</p>
<p>LOGAN,</p>
<p>LONNY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td><p>39940</p>
<p>LOONEY, DANNY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>39940 MERSINGER, KEN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>39984 STARKEY, GORDON</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3027</td>
<td>Macintosh</td>
<td> </td>
<td>40104 KHAN, FARZANA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 101</td>
<td>Macintosh</td>
<td> </td>
<td>45167 YALCINKAYA, METE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3016</td>
<td>Macintosh</td>
<td> </td>
<td><p>45272</p>
<p>TUCKER,</p>
<p>KEITH</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1006A</td>
<td>Macintosh</td>
<td> </td>
<td>45285 QAS (Mark Sobek)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 9%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1006A</td>
<td>Macintosh</td>
<td> </td>
<td>45286 QAS (Ron Coats)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/1/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3030</td>
<td>Macintosh</td>
<td> </td>
<td>45642 NYSTROM, PETER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3010</td>
<td>Macintosh</td>
<td> </td>
<td>45812 THREATT, GRANT</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td>45814 TRITTIPO, ROBERT</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45815 JIMINEZ, JAVIER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45816 RAMIREZ, OSCAR</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45817 FLANDERS, TOM</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45820 HERRING, MELVIN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45821 CURTNER, DOC</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45822 BALDWIN, LAURA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1014</td>
<td>Macintosh</td>
<td> </td>
<td>45823 OUTLAW, JEFF</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td>45906 ADAMS, TERENCE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3021</td>
<td>Macintosh</td>
<td> </td>
<td>45976 ISHMAEL, GEORGE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>45978 CHASTAIN, BILL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3028</td>
<td>Macintosh</td>
<td> </td>
<td>45984 QE (Masahru Iwasa)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh</td>
<td> </td>
<td>45986 DEFELICE, DANE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td>45988 LARA, SERGIO</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3027</td>
<td>Macintosh</td>
<td> </td>
<td>45991 DESAI, ASHOK</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2019</td>
<td>Macintosh</td>
<td> </td>
<td>45996 XIA, HONG</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1009</td>
<td>Macintosh</td>
<td> </td>
<td><p>46120 SCHNELL,</p>
<p>PAT</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.56, 100</td>
<td>Macintosh</td>
<td> </td>
<td>46263 COOPER, JAIME</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td>46358 THOMAS,</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>12/10/97</td>
</tr>
</tbody>
</table>

  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------
  Func-tional   Divi-sion   System/Network   Operating   NEMS \#   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                      System                            Support                   System                

                                                                   ALVIN                                                        

  OOS           SM4         Quadra 650 Mac   Macintosh   1346283               1                     1              10/01/97   12/10/97

  OOS           SM4         AS/2 PC          WIN95       1849698               1                                    10/01/97   12/10/97

  OOS           SM4         Quadra 650 Mac   Macintosh   1355723               1                     1              10/01/97   12/10/97

  OOS           SM4         Quadra 630 Mac   Macintosh   1346469               1                     1              10/01/97   12/10/97

  OOS           SM4         Quadra 650 Mac   Macintosh   1346274               1                     1              10/01/97   12/10/97

  OOS           SM4         Power Macintosh  Macintosh   1454511               1                     1              10/01/97   12/10/97

  OOS           SM4         Power Macintosh  Macintosh   1454507               1                     1              10/01/97   12/10/97

  OOS           SM4         Quadra 630 Mac   Macintosh   1449600               1                     1              10/01/97   12/10/97

  OOS           SM4         Quadra 630 Mac   Macintosh   1346356   Helix       1                     1              12/10/97   6/01/98
                                                                   Server #2                                                   

  OOS           SM4         Quadra 630 Mac   Macintosh   1346355   Helix       1                     1              12/10/97   6/01/98
                                                                   Server #4                                                   

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              10/01/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              12/10/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              12/10/97   9/30/98

  OOS           SM          B266             Macintosh             BDC         1                     1              12/10/97   9/30/98

  OOS           SM          2019             Macintosh             30654       1                     1              10/01/97   9/30/98
                                                                   REBTOY,                                                     
                                                                   SHAWN                                                       

  OOS           SM          1010             Macintosh             31021 SIM   1                     1              10/01/97   9/30/98
                                                                   POCC 38215                                                  
  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 9%" />
<col style="width: 6%" />
<col style="width: 13%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1010</td>
<td>Macintosh</td>
<td> </td>
<td><p>31021 SIM POCC</p>
<p>38215</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2018</td>
<td>Macintosh</td>
<td> </td>
<td><p>32544</p>
<p>CLARK, DANIEL</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2008A</td>
<td>Macintosh</td>
<td> </td>
<td>32776 SMA ANNEX</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2008A</td>
<td>Macintosh</td>
<td> </td>
<td>32776 SMA ANNEX</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2008A</td>
<td>Macintosh</td>
<td> </td>
<td>32776 SMA ANNEX</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2008A</td>
<td>Macintosh</td>
<td> </td>
<td>32776 SMA ANNEX</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3034</td>
<td>Macintosh</td>
<td> </td>
<td>34116 DAS, CHANDAN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2015</td>
<td>Macintosh</td>
<td> </td>
<td>34667 BRADFORD, KASIE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3012</td>
<td>Macintosh</td>
<td> </td>
<td><p>34809</p>
<p>BOURG, MARLENE</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>134</td>
<td>Macintosh</td>
<td> </td>
<td>34967 CONFERENCE ROOM</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3026</td>
<td>Macintosh</td>
<td> </td>
<td>35053 HUDSON, LACELIAN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3026</td>
<td>Macintosh</td>
<td> </td>
<td>35053 SRM (Lacelian Hudson)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>B.57, 104</td>
<td>Macintosh</td>
<td> </td>
<td>35454 DALRYMPLE, GARY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1005</td>
<td>Macintosh</td>
<td> </td>
<td><p>36048 ROSSER, STEVE</p>
<p>(casual)</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1002</td>
<td>Macintosh</td>
<td> </td>
<td><p>36137</p>
<p>FETZER, SHERMANN</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2018</td>
<td>Macintosh</td>
<td> </td>
<td>37315 FARUQUE, MONAZER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>1005</td>
<td>Macintosh</td>
<td> </td>
<td><p>37364</p>
<p>ALLEN,</p>
<p>MITSY</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1005</td>
<td>Macintosh</td>
<td> </td>
<td><p>37364</p>
<p>TODAI, KAMLESH (casual)</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2015</td>
<td>Macintosh</td>
<td> </td>
<td>37382 SOFTWARE LIBRARY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 13%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 12%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2015</td>
<td>Macintosh </td>
<td> </td>
<td>37382 SOFTWARE LIBRARY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2025</td>
<td>Macintosh</td>
<td> </td>
<td>37392 SMA (OUTSIDE)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2025C</td>
<td>Macintosh </td>
<td> </td>
<td>37412 CONF. RM 2ND FL.</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2025C</td>
<td>Macintosh </td>
<td> </td>
<td>37412 CONF. RM 2ND FL.</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2025C</td>
<td>Macintosh </td>
<td> </td>
<td>37412 CONF. RM 2ND FL.</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2025C</td>
<td>Macintosh </td>
<td> </td>
<td>37412 CONF. RM 2ND FL.</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2025C</td>
<td>Macintosh </td>
<td> </td>
<td>37412 CONF. RM 2ND FL.</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2015</td>
<td>Macintosh </td>
<td> </td>
<td>37430 BROWN, DONNA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>125</td>
<td>Macintosh </td>
<td> </td>
<td>37438 LUTZ, GEORGE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B. 266, 125</td>
<td>Macintosh </td>
<td> </td>
<td>37438 LUTZ, GEORGE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3014</td>
<td>Macintosh </td>
<td> </td>
<td><p>37442</p>
<p>NOLAN,</p>
<p>LORI</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3035</td>
<td>Macintosh </td>
<td> </td>
<td>37444 ZARECHNAK, ANDREW</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2030</td>
<td>Macintosh </td>
<td> </td>
<td><p>37446 NGUYEN, TONY</p>
<p>(casual)</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3026</td>
<td>Macintosh </td>
<td> </td>
<td>37450 DEBLANC, A.C.</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3026</td>
<td>Macintosh </td>
<td> </td>
<td><p>37450 SRM (A.C.</p>
<p>Deblanc)</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2018</td>
<td>Macintosh </td>
<td> </td>
<td>37455 SIDDIQUI, SAEED</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2019</td>
<td>Macintosh </td>
<td> </td>
<td>37456 GREEN, KINRA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2019</td>
<td>Macintosh </td>
<td> </td>
<td>37460 HODGES, JAMES (casual)</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2018B</td>
<td>Macintosh </td>
<td> </td>
<td>37460 RAHMAN, HASAN</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>B.57, 101</td>
<td>Macintosh </td>
<td> </td>
<td>37471 SEPAHBAN, AMIR</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 15%" />
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 11%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 9%" />
<col style="width: 7%" />
<col style="width: 8%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2018</td>
<td>Macintosh</td>
<td> </td>
<td>39684 SCHULTZ, RUSSELL</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3027</td>
<td>Macintosh</td>
<td> </td>
<td>40155 CARTER, SHERRY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>2018</td>
<td>Macintosh</td>
<td> </td>
<td>45826 AYUB, NASER</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>1004</td>
<td>Macintosh</td>
<td> </td>
<td>45907 NICHOLS, LAURA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3019B</td>
<td>Macintosh</td>
<td> </td>
<td>45980 NGUYEN, KIMBERLY</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>2019</td>
<td>Macintosh</td>
<td> </td>
<td>45987 PRODHAN, MIKE</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM</td>
<td>3012</td>
<td>Macintosh</td>
<td> </td>
<td><p>45990 TA,</p>
<p>M.T.</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM</td>
<td>3033</td>
<td>Macintosh</td>
<td> </td>
<td><p>46280 SCULLY,</p>
<p>BOB</p></td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM/DO</td>
<td>Power Macintosh</td>
<td>Macintosh</td>
<td>1712868</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM/NSL</td>
<td>Raynor PC</td>
<td>WIN95</td>
<td>1850290</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td><p>SM/R</p>
<p>R504</p></td>
<td>Power Macintosh</td>
<td>Macintosh</td>
<td>1350714</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM2</td>
<td>Laptop</td>
<td>Macintosh</td>
<td>1602716</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1449395</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1232937</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1449414</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1232938</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1449412</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1232921</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1232946</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM2</td>
<td>Macintosh</td>
<td>Macintosh</td>
<td>1232928</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM2</td>
<td>PC</td>
<td>WIN95</td>
<td>1347013</td>
<td>POSA</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
<td>FC</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 630 Mac</td>
<td>Macintosh</td>
<td>1454502</td>
<td>LSPD SERV</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 630 Mac</td>
<td>Macintosh</td>
<td>1454521</td>
<td>MMS SERV</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Macintosh II ci</td>
<td>Macintosh</td>
<td>1293371</td>
<td>PRI-ARNS</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 630 Mac</td>
<td>Macintosh</td>
<td>1346357</td>
<td>SEC_ARNS</td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>FC</td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 700 Mac</td>
<td>Macintosh</td>
<td>1232949</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Centris 650 Mac</td>
<td>Macintosh</td>
<td>1292051</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 650 Mac</td>
<td>Macintosh</td>
<td>1346276</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Macintosh II fx</td>
<td>Macintosh</td>
<td>1238397</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Macintosh A950</td>
<td>Macintosh</td>
<td>1291288</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td>C</td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 610 Mac</td>
<td>Macintosh</td>
<td>1353011</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Macintosh II ci</td>
<td>Macintosh</td>
<td>1235096</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Macintosh II fx</td>
<td>Macintosh</td>
<td>1006539</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 630 Mac</td>
<td>Macintosh</td>
<td>1449957</td>
<td> </td>
<td>1</td>
<td></td>
<td></td>
<td></td>
<td>1</td>
<td> </td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 610 Mac</td>
<td>Macintosh</td>
<td>1169337</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>OOS</td>
<td>SM4</td>
<td>Quadra 700 Mac</td>
<td>Macintosh</td>
<td>1170383</td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>12/10/97</td>
<td>9/30/98</td>
</tr>
</tbody>
</table>

  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ---------
  Func-tional   Divi-sion   System/Network   Operating   NEMS \#   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                      System                            Support                   System                

  OOS           SM4         Quadra 630 Mac   Macintosh   1449956               1                     1              10/01/97   9/30/98

  OOS           SM4         Macintosh II     Macintosh   842547                1                     1              10/01/97   9/30/98

  OOS           SM4         Macintosh II fx  Macintosh   079149                1                     1              12/10/97   9/30/98

  OOS           SM4         Macintosh II ci  Macintosh   1008508               1                     1              12/10/97   9/30/98

  OOS           SM4         Macintosh II ci  Macintosh   1238444               1                     1              10/01/97   9/30/98

  OOS           SM4         Macintosh II ci  Macintosh   1118935               1                     1              10/01/97   9/30/98

  OOS           SM4         Quadra 610 Mac   Macintosh   1351925               1                     1              12/10/97   9/30/98

  OOS           SM4         Centris 650 Mac  Macintosh   1292050               1                     1              10/01/97   9/30/98

  OOS           SM4         Quadra 610 Mac   Macintosh   1353014               1                     1              10/01/97   9/30/98

  OOS           SM4         Macintosh II fx  Macintosh   1002187               1                     1              10/01/97   9/30/98

  OOS           SM4         Macintosh II si  Macintosh   1003381               1                     1              12/10/97   9/30/98

  OOS           SM4         Macintosh II ci  Macintosh   1170403               1                     1              12/10/97   9/30/98

  OOS           SM4         Quadra 630 Mac   Macintosh   1230629   Helix       1                     1              12/10/97   3/31/99
                                                                   Server #3                                                   

  OOS           SM4         Quadra 950 Mac   Macintosh   1233692   Helix       1                     1              12/10/97   3/31/99
                                                                   Server #6                                                   

  OOS           SM4         PPC 7100/66      Macintosh   1448331               1                     1              12/10/97   3/31/99

  OOS           SM4         Quadra 950 Mac   Macintosh   1449953               1                     1              12/10/97   3/31/99

  OOS           SM4         PC               WIN95       1552844               1                                    12/10/97   3/31/99

  OOS           SM4         Quadra 950 Mac   Macintosh   1291286               1                     1              10/01/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1454519               1                     1              10/01/97   3/31/99

  OOS           SM4         Quadra 630 Mac   Macintosh   1346351               1                     1              10/01/97   3/31/99

  OOS           SM4         604/180/Mac      Macintosh   1846664               1                     1              12/10/97   3/31/99
                            Clone                                                                                              

  OOS           SM4         Power Macintosh  Macintosh   1451884               1                     1              12/10/97   3/31/99

  OOS           SM4         Macintosh II fx  Macintosh   1002408               1                     1              12/10/97   3/31/99

  OOS           SM4         Quadra 630 Mac   Macintosh   1449597               1                     1              10/01/97   3/31/99

  OOS           SM4         M1350            Macintosh   1322112               1                     1              12/10/97   3/31/99

  OOS           SM4         486/66           PC          1453142               1                                    12/10/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1548215               1                     1              10/01/97   3/31/99

  OOS           SM4         Pentium 75       PC          1550058               1                     1              12/10/97   3/31/99

  OOS           SM4         586 PII/266      PC          1913516               1                     1              12/10/97   3/31/99

  OOS           SM4         PPC 7100/66      Macintosh   1347981               1                     1              12/10/97   3/31/99

  OOS           SM4         PPC 6100/66      Macintosh   1454588               1                     1              12/10/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1454512               1                     1              12/10/97   3/31/99

  OOS           SM4         Macintosh II x   Macintosh   G18444                1                     1              10/01/97   3/31/99

  OOS           SM4         AS/2 PC          WIN95       1849636               1                                    12/10/97   3/31/99

  OOS           SM4         PPC 6100/66      Macintosh   1451885               1                     1              12/10/97   3/31/99

  OOS           SM4         PPC 6100/66      Macintosh   1451887               1                     1              10/01/97   3/31/99

  OOS           SM4         Vektron CPU 75   PC          1550059               1                     1              12/10/97   3/31/99
                            MHz                                                                                                

  OOS           SM4         Raynor PC        WIN95       1453163               1                                    10/01/97   3/31/99

  OOS           SM4         PPC 7100/66      Macintosh   1448365               1                     1              12/10/97   3/31/99

  OOS           SM4         PC               WIN95       1543118               1                                    10/01/97   3/31/99

  OOS           SM4         M5780            Macintosh   1008486               1                     1              12/10/97   3/31/99

  OOS           SM4         Raynor PC        WIN95       1550007               1                                    10/01/97   3/31/99

  OOS           SM4         Quadra 950 Mac   Macintosh   1233514               1                     1              10/01/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1448353               1                     1              12/10/97   3/31/99
  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ---------

  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------
  Func-tional   Divi-sion   System/Network   Operating   NEMS \#   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                      System                            Support                   System                

  OOS           SM4         Power Macintosh  Macintosh   1353528               1                     1              10/01/97   3/31/99

  OOS           SM4         Macintosh II x   Macintosh   G18426                1                     1              12/10/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1448333               1                     1              12/10/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1448251               1                     1              12/10/97   3/31/99

  OOS           SM4         Macintosh II CI  Macintosh   1238443               1                     1              12/10/97   3/31/99

  OOS           SM4         ISC 486 PC       WIN95       1451402               1                                    12/10/97   3/31/99

  OOS           SM4         PPC 7100/66      Macintosh   1448320               1                     1              12/10/97   3/31/99

  OOS           SM4         Macintosh II ci  Macintosh   1170352               1                     1              12/10/97   3/31/99

  OOS           SM4         486/66           PC          1346495               1                                    12/10/97   3/31/99

  OOS           SM4         486/66           PC          1347871               1                                    12/10/97   3/31/99

  OOS           SM4         Macintosh II ci  Macintosh   1119284               1                     1              12/10/97   3/31/99

  OOS           SM4         IBM Think Pad    PC          1848013               1                                    12/10/97   3/31/99

  OOS           SM4         IBM Think Pad    PC          1848014               1                                    12/10/97   3/31/99

  OOS           SM4         IBM Think Pad    PC          1848016               1                                    12/10/97   3/31/99

  OOS           SM4         IBM Think Pad    PC          1848017               1                                    12/10/97   3/31/99

  OOS           SM4         IBM Think Pad    PC          1919008               1                                    12/10/97   3/31/99

  OOS           SM4         IBM Think Pad    PC          1848015               1                                    12/10/97   3/31/99

  OOS           SM4         486DX/50         PC          1355792               1                                    12/10/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1550107               1                     1              10/01/97   3/31/99

  OOS           SM4         PPC 6100/66      Macintosh   1346359               1                     1              12/10/97   3/31/99

  OOS           SM4         586 PII/266      PC          1913517               1                                    12/10/97   3/31/99

  OOS           SM4         Macintosh II FX  Macintosh   0768701               1                     1              12/10/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1451744               1                     1              10/01/97   3/31/99

  OOS           SM4         Power Macintosh  Macintosh   1550108               1                     1              10/01/98   3/31/99

  OOS           SM4         Macintosh II ci  Macintosh   1008505               1                     1              12/10/97   3/31/99

  OOS           SM4         Raynor PC        WIN95       1452230               1                                    12/10/97   3/31/99

  OOS           SM4         SW KEYSERVER     Macintosh   1448351                         1           1              12/10/97   3/31/99
                            Power Macintosh                                                                                    
                            7100/66                                                                                            

  LAB           SM          J36                                                1                         C          10/01/97   6/02/98

  LAB           EC          J241                                                         1                          10/01/97   9/30/98

  LAB           EC          J29                                                1                                    10/01/97   9/30/98

  LAB           EC          J34                                                              1                      10/01/97   9/30/98

  LAB           EC          J34                                                1                                    10/01/97   9/30/98

  LAB           EG          J16                                                          1                          10/01/97   9/30/98

  LAB           EM          J15                                                1                         C          10/01/97   9/30/98

  LAB           EV          ECOMM J16A/ROOM                                              1               C          10/01/97   9/30/98
                            1032                                                                                               

  LAB           EV          OIU J16 / ROOM                                               1               C          10/01/97   9/30/98
                            290                                                                                                

  LAB           EA5         J36                                                              1                      6/03/98    12/31/03

  LAB           EC          FIREWALL                                           1                         C          6/30/98    12/31/03

  LAB           EC          J32                                                1                         C          10/01/97   12/31/03

  LAB           EC          J33                                                1                         C          10/01/97   12/31/03

  LAB           EC          J7                                                 1                         C          10/01/97   12/31/03

  LAB           EM          J10                                                1                         C          10/01/97   12/31/03
  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 16%" />
<col style="width: 8%" />
<col style="width: 7%" />
<col style="width: 12%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 6%" />
<col style="width: 8%" />
<col style="width: 8%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td>Critical System</td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>LAB</td>
<td>EM</td>
<td>J343</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>LAB</td>
<td>EM</td>
<td>J9S</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>LAB</td>
<td>EV</td>
<td><p>OIU/ECOMM J16A/ROOMS</p>
<p>1032 AND 1034</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>LAB</td>
<td>MV3</td>
<td>J4S</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>LAB</td>
<td>SA</td>
<td>J241</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>LAB</td>
<td>SM4</td>
<td>J266</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>6/03/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>LAB</td>
<td>SM4</td>
<td>J36</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>6/03/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>LAB</td>
<td>SM4</td>
<td>J56</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>6/03/98</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>LAB</td>
<td>SM4</td>
<td>J57</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>6/03/98</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EA5</td>
<td>ECL Mockup Helix DB</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>3/01/98</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EA5</td>
<td>Engineering Drawings Helix DB</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>3/01/98</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>ABUHANTES H-J-H</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>CAMPBELL-CARLIS</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>DONG-AINONG</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>E-D</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>ES-COOP4</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>GONAZLEZ-NORBER</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>GOODMARK-JEFF-A</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>HUSAIN-TASNEEM</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>KOTT-TREVOR-R</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>MCMANAMEN-JOHN</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>TILLIAN-DONALD</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td> </td>
<td>WESSELSKI-CLERAN</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>HA</td>
<td>TECHTRACS</td>
<td> </td>
<td> </td>
<td><p>CAMERON-</p>
<p>JIM</p></td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>HA</td>
<td>TECHTRACS</td>
<td> </td>
<td> </td>
<td>HEIL, TERRY (SPARE)</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>9/30/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>SM</td>
<td><p>STI Library Helix</p>
<p>DB</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>3/001/98</td>
<td>9/30/98</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>SA</td>
<td><p>Software Configuration</p>
<p>Control Center</p></td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/98</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EA5</td>
<td>J36 290 New Helix DB</td>
<td> </td>
<td>1233692</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td>C</td>
<td>3/01/98</td>
<td>3/31/99</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EA5</td>
<td>J36 Logistics Helix DB</td>
<td> </td>
<td>1233692</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td>C</td>
<td>3/01/98</td>
<td>3/31/99</td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 19%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 11%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 9%" />
<col style="width: 8%" />
</colgroup>
<tbody>
<tr class="odd">
<td>Func-tional Areas</td>
<td>Divi-sion</td>
<td>System/Network</td>
<td>Operating System</td>
<td>NEMS #</td>
<td>Node/Name</td>
<td colspan="5">Level of Support</td>
<td><p>Critical</p>
<p>System</p></td>
<td>Start Date</td>
<td>End Date</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>SM</td>
<td>AIL Helix DB</td>
<td> </td>
<td>1230629</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td>C</td>
<td>03/01/98</td>
<td>03/31/99</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>SM</td>
<td>CCB/Forms Action Helix DB</td>
<td> </td>
<td>1230629</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td>C</td>
<td>03/01/98</td>
<td>03/31/99</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>SM</td>
<td><p>Software BarCode</p>
<p>Helix DB</p></td>
<td> </td>
<td>1347981</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/97</td>
<td>03/31/99</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>SA</td>
<td>SCCC Phase Out</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>01/01/99</td>
<td>09/30/99</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EA</td>
<td>MS SQL Server</td>
<td> </td>
<td>1917460</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EA/BE</td>
<td><p>Automated PR</p>
<p>System</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EA/BE</td>
<td><p>Contractor Cost</p>
<p>Accrual System</p>
<p>(CCAS)</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EA/BE</td>
<td><p>Engineering</p>
<p>Business Office</p>
<p>(EBO) Menu</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EA/BE</td>
<td><p>ETAC Shared</p>
<p>Area</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EA/BE</td>
<td><p>Task Order</p>
<p>Planning System (TOPS)</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EC</td>
<td>Engineering DB</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EG4</td>
<td>WIN95/XCEED GATEWAY 2000</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>EG4</td>
<td>WIN95/XCEED GATEWAY PC</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>EG4</td>
<td><p>WIN95/XCEED</p>
<p>H/W TERMINAL</p></td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453477</td>
<td> ES20PEN1</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453465</td>
<td> ES-MEZZ95</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453519</td>
<td> PHAROAH</td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1347805</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453499</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453531</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1550016</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1450625</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1550017</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1552221</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1552243</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453455</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="even">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453522</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
<tr class="odd">
<td>MAJOR S/W</td>
<td>ES</td>
<td>XEED</td>
<td> </td>
<td>1453517</td>
<td> </td>
<td> </td>
<td> </td>
<td> </td>
<td>1</td>
<td> </td>
<td>C</td>
<td>10/01/97</td>
<td>12/31/03</td>
</tr>
</tbody>
</table>

  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------
  Func-tional   Divi-sion   System/Network   Operating   NEMS \#   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                      System                            Support                   System                

  MAJOR S/W     ES          XEED                         1744855                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1449664                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1450635                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1347810                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453496                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453513                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453513                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1552238                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453452                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1550012                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1549896                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1550011                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453276                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1450627                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453520                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1549891                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1453481                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1552237                                 1       C          10/01/97   12/31/03

  MAJOR S/W     ES          XEED                         1454330                                 1       C          10/01/97   12/31/03

  MAJOR S/W     EV          CCS On-Line                  1918431               1                                    10/01/97   12/31/03
                            System                                                                                             

  MAJOR S/W     EV          CCS WEB Page                 1918431               1                                    10/01/97   12/31/03

  MAJOR S/W     EV          CCSL Web Page                                      1                                    6/01/98    12/31/03

  MAJOR S/W     EV          CCS WEB PAGE                 1291430               1                                    10/01/97   12/31/03
                            (MAC)                                                                                              

  MAJOR S/W     EX          Revision Control                       LINDBERG              1               C          10/01/97   12/31/03
                            System (RCS)                                                                                       

  MAJOR S/W     HA          TECHTRACS                    1451384   AUTOAGENT                 1           C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1920794                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1929080                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACSS                   1920804                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1456456                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1456454                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1929064                                 1       C          10/01/97   12/31/03
  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------

  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------
  Func-tional   Divi-sion   System/Network   Operating   NEMS \#   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                      System                            Support                   System                

  MAJOR S/W     HA          TECHTRACS                    1920802                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1920800                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737447                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737443                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737487                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1920792                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1744992                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1456448                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1929076                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737433                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1929074                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1929078                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737455                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737435                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737449                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737445                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1920806                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1456418                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1744922                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1456460                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737437                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS                    1737439                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS -                  1913761                                 1       C          10/01/97   12/31/03
                            LAPTOP #1                                                                                          

  MAJOR S/W     HA          TECHTRACS -                  1913762                                 1       C          10/01/97   12/31/03
                            LAPTOP #2                                                                                          

  MAJOR S/W     HA          TECHTRACS                    1743467                                 1       C          10/01/97   12/31/03

  MAJOR S/W     HA          TECHTRACS SERVER             1914303                             1           C          10/01/97   12/31/03

  Security      EC          IT Security Plan                                             1                          10/01/98   3/31/98

  Security      EM          IT Security Plan                                             1                          10/01/98   3/31/98

  Security      EA4         IT Security Plan                                             1                          10/01/98   3/31/99

  Security      EA5         IT Security Plan                                             1                          10/01/98   3/31/99

  Security      EG          IT Security Plan                                             1                          04/01/98   3/31/99

  Security      EP          IT Security Plan                                             1                          10/01/98   3/31/99
  ------------- ----------- ---------------- ----------- --------- ----------- --------- --- --- --- --- ---------- ---------- ----------

  ------------- ----------- ---------------- ----------- ------ ----------- --------- --- --- --- --- ---------- ---------- ---------
  Func-tional   Divi-sion   System/Network   Operating   NEMS   Node/Name   Level of                  Critical   Start Date End Date
  Areas                                      System      \#                 Support                   System                

  Security      ER          IT Security Plan                                          1                          6/11/98    3/31/99

  Security      ES          IT Security Plan                                          1                          10/01/98   3/31/99

  Security      EV          IT Security Plan                                          1                          8/01/98    3/31/99

  Security      EX12        IT Security Plan                                          1                          10/01/98   3/31/99

  Security      SM4         IT Security Plan                                          1                          10/01/98   9/30/99
  ------------- ----------- ---------------- ----------- ------ ----------- --------- --- --- --- --- ---------- ---------- ---------