SECTION A

SOLICITATION/CONTRACT FORM

A.1 [RESERVED]{.underline}

A.2 [TABLE OF CONTRACT CONTENTS]{.underline}

A.  RESERVED

    1.  RESERVED

    2.  TABLE OF CONTRACT CONTENTS

B.  SUPPLIES OR SERVICES AND PRICE/COSTS

    1.  SUPPLIES AND/OR SERVICES TO BE FURNISHED

    2.  ESTIMATED COST AND FEE

    3.  FEE STRUCTURE

    4.  CONTRACT FUNDING

    5.  OPTION(S) TO EXTEND COMPLETION OF WORK

    6.  CONTRACT ADJUSTMENT FOR LANDINGS AT SITES OTHER THAN KSC

    7.  TOTAL ANNUAL FUNDING PROFILE

C.  DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

    1.  SCOPE OF WORK

D.  PACKAGING AND MARKING

    1.  PACKAGING AND MARKING

E.  INSPECTION AND ACCEPTANCE

    1.  LISTING OF CLAUSES INCORPORATED BY REFERENCE

    2.  SHIPPING INSTRUCTIONS

    3.  HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT (GOVERNMENT
        SPECIFICATION)

    4.  HUMAN SPACE FLIGHT ITEM

    5.  RESERVED

    6.  RESERVED

F.  DELIVERIES OR PERFORMANCE

    1.  LISTING OF CLAUSES INCORPORATED BY REFERENCE

    2.  COMPLETION OF WORK

    3.  PLACE OF PERFORMANCE

    4.  BILLS OF LADING

    5.  FLIGHT ITEM

    6.  UNFINISHED WORK CONTENT TRANSFERRED FROM SFOC INTO SPOC

G.  CONTRACT ADMINISTRATION DATA

    1.  LISTING OF CLAUSES INCORPORATED BY REFERENCE

    2.  SUBMISSION OF VOUCHERS FOR PAYMENT

    3.  RESERVED

    4.  RESERVED

    5.  TECHNICAL DIRECTION

    6.  RESERVED

    7.  FINANCIAL REPORTING OF NASA PROPERTY IN THE CUSTODY OF
        CONTRACTORS

    8.  RESERVED

    9.  DESIGNATION OF CONTRACTING OFFICERS TECHNICAL MANAGEMENT
        REPRESENTATIVES

    10. SECURITY/BADGING REQUIREMENTS FOR FOREIGN NATIONAL VISITORS AND
        EMPLOYEES/REPRESENTATIVES OF FOREIGN CONTRACTORS

    11. GOVERNMENT-FURNISHED PROPERTY -- SPECIAL PROVISION

    12. INSTALLATION PROVIDED SERVICES (IPS)

    13. SPECIAL COST PROVISIONS

    14. RESERVED

    15. TECHNOLOGY TRANSFER

    16. MANAGEMENT OF POST DD 250 PROPERTY

    17. AWARD FEE FOR SERVICE CONTRACTS

    18. ADVANCE AGREEMENT ON IMPLEMENTATION OF THE SINGLE
        NON-CONFORMANCE SYSTEM (SNCS)

H.  SPECIAL CONTRACT REQUIREMENTS

    1.  LISTING OF CLAUSES INCORPORATED BY REFERENCE

    2.  REPRESENTATIONS, CERTIFICATIONS, AND OTHER STATEMENTS OF
        OFFERORS

    3.  SMALL BUSINESS SUBCONTRACTING GOALS

    4.  USE OF JSC CALIBRATION LABORATORY

    5.  RESERVED

    6.  MOTOR VEHICLE MANAGEMENT

    7.  INDEMNIFICATION

    8.  PRIVACY OR SECURITY SAFEGUARDS

    9.  ASSOCIATE CONTRACTOR AGREEMENTS FOR ISS OPERATIONS AND
        UTILIZATION ACTIVITIES

    10. CUSTODY AND DISPOSITION OF COMPUTER SOFTWARE

    11. INFORMATION TECHNOLOGY PURCHASES

    12. PROTECTION OF GOVERNMENT FIP ASSETS

    13. RESERVED

    14. EXPORT OF TECHNICAL DATA, DEFENSE SERVICES, COMPUTER SOFTWARE,
        OR HARDWARE

    15. RESERVED

    16. RESERVED

    17. RESERVED

    18. CONTINUOUS IMPROVEMENT/PARTNERING

    19. ACCESS TO CONTRACTOR DATA

    20. SPECIAL PROVISION FOR CONTRACT CHANGES

    21. COMPLIANCE WITH APPLICABLE CENTER POLICIES AND PROCEDURES

    22. SAFETY AND HEALTH PLAN

    23. RESERVED

    24. RESERVED

    25. GOVERNMENT INSIGHT

    26. RESERVED

    27. ENGINEERING CHANGE PROPOSALS

    28. SPACE FLIGHT AWARENESS PROGRAM

    29. RESERVED

    30. RESERVED

    31. REQUIREMENT FOR COST TRACKING

    32. PROCUREMENT DATA PACKAGE

    33. LAUNCH SCHEDULE VARIATIONS

    34. SELECTION OF FIRMS FOR ARCHITECT-ENGINEER (A-E) SERVICES

    35. PROVISIONING PROCEDURES

    36. RESERVED

    37. RESERVED

    38. RESERVED

    39. ACTIVITY BASED COSTING

    40. VALUE ENGINEERING

    41. MINIMUM INSURANCE COVERAGE FOR VESSEL LIABILITY

    42. RESERVED

    43. RESERVED

    44. RESERVED

    45. OBSERVANCE OF LEGAL HOLIDAYS

    46. ADMINISTRATIVE CONTRACT CLOSEOUT

    47. ADJUSTMENT FOR FINAL SPACE SHUTTLE FLIGHT LAUNCH DATE

I.  CONTRACT CLAUSES

    1.  CLAUSES INCORPORATED BY REFERENCE

    2.  CLAUSES INCORPORATED BY REFERENCE

    3.  RESERVED

    4.  APPROVAL OF CONTRACT

    5.  NOTIFICATION OF EMPLOYEE RIGHTS CONCERNING PAYMENT OF UNION DUES
        OR FEES

    6.  HAZARDOUS MATERIAL IDENTIFICATION AND MATERIAL SAFETY DATA

    7.  RIGHTS IN DATA - GENERAL

    8.  INDUSTRIAL RESOURCES DEVELOPED UNDER DEFENSE PRODUCTION ACT
        TITLE III

    9.  CONTINUITY OF SERVICES

    10. NOTIFICATION OF CHANGES

    11. RESERVED

    12. RESERVED

    13. AUTHORIZED DEVIATIONS IN CLAUSES

    14. SECURITY CLASSIFICATION REQUIREMENTS

    15. SECURITY REQUIREMENTS FOR UNCLASSIFIED INFORMATION TECHNOLOGY
        RESOURCES

    16. OMBUDSMAN

    17. STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES

    18. BUY AMERICAN ACT -- CONSTRUCTION MATERIALS

    19. BUY AMERICAN ACT -- CONSTRUCTION MATERIALS UNDER TRADE
        AGREEMENTS

    20. PRICE ADJUSTMENTS FOR "MAKE OR BUY" CHANGES

    21. RESERVED

    22. RESERVED

    23. RESERVED

J.  LIST OF ATTACHMENTS

    1.  STATEMENT OF WORK

        A.  STATEMENT OF WORK

        B.  PERFORMANCE REQUIREMENTS SUMMARIES

        C.  RESERVED

        D.  RESERVED

    2.  GLOSSARY, ACRONYMS, AND ABBREVIATIONS

    3.  RESERVED

    4.  RESERVED

    5.  DATA PROCUREMENT DOCUMENT

    6.  STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES

    7.  WAGE DETERMINATIONS

    8.  FEE PLAN

    9.  GOVERNMENT-FURNISHED PROPERTY

    10. INSTALLATION-PROVIDED SERVICES

    11. APPLICABLE NASA POLICIES AND PROCEDURES

    12. RESERVED

    13. MAKE OR BUY PLAN

    14. SMALL BUSINESS SUBCONTRACTING PLAN

    15. RESERVED

    16. CONTINUOUS IMPROVEMENT PLAN FOR THE SPACE PROGRAM OPERATIONS
        CONTRACT (SPOC)

    17. CONTRACT SECURITY CLASSIFICATION SPECIFICATION

    18. NASA CENTER SPECIFIC CLAUSES

    19. PROVISIONING MANAGEMENT PLAN

    20. RESERVED

    21. FACILITIES AND ENVIRONMENTAL PROJECTS

    22. RESERVED

    23. STANDARDS, FOOD, AND SPECIFICATION LIST

    24. RESERVED

    25. RESERVED

    26. RESERVED

    27. RESERVED

    28. IDIQ EFFORT

    29. PERSONAL IDENTITY VERIFICATION (PIV) CARD ISSUANCE PROCEDURES

(END OF SECTION)

SECTION B

SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 [SUPPLIES AND/OR SERVICES TO BE FURNISHED]{.underline}

The Contractor shall perform Space Flight Operations as described in
Section C and Attachments J-1 and J-5 during a 4-year base contract
period beginning October 1, 2006 plus, if exercised, option periods of a
single year (for a potential total period of performance of nine years).
The options shall consist of:

> Option 1: A single 1-year option period, extending performance from
> October 1, 2010, through September 30, 2011.
>
> Option 2: A single 1-year option period, extending performance from
> October 1, 2011, through September 30, 2012.
>
> Option 3: A single 1-year option period, extending performance from
> October 1, 2012, through September 30, 2013.
>
> Option 4: A single 1-year option period, extending performance from
> October 1, 2013 through September 30, 2014.
>
> Option 5: A single 1-year option period, extending performance from
> October 1, 2014, through September 30, 2015.

(End of clause)

B.2 [ESTIMATED COST AND FEE]{.underline}

Contract cost and fees are:

a.  Estimated Cost\*: \$ 5,711,200,000

b.  Estimated Program Provisioning Cost: \$ 9,284,431

c.  Estimated Transition Provisioning Cost: \$ 4,739,916

d.  Estimated Constellation Provisioning Cost: \$ 25,344,229

e.  Estimated Facilities Cost: [\$ 13,900,000]{.underline}

f.  Total Estimated Cost: \$ 5,764,468,576

g.  Maximum Available Award Fee: \$ 426,200,807

h.  Maximum Flight Performance Fee: \$ 119,000,000

> \(i\) Maximum End of Program Fee: [\$ 73,100,000]{.underline}
>
> \(j\) Maximum Total Fee: \$ 618,300,807
>
> \(k\) Total Contract Value: \$ 6,382,769,383

\*Does not include estimated provisioning cost or estimated facilities
costs.

(End of clause)

B.3 [FEE STRUCTURE]{.underline}

The fee structure of this contract is described in Attachment J-8.

(End of clause)

B.4 [CONTRACT FUNDING (1852.232-81) (JUN 1990)]{.underline}

(a) For purposes of payment of cost, exclusive of fee, in accordance
    with the *Limitation of Funds* clause, the total amount allotted by
    the Government to this contract is \$714,332,550. This allotment
    covers the estimated period of performance from the effective date
    of the contract through March 14, 2007.

(b) An additional amount of \$67,861,593 is obligated under this
    contract for payment of fee.

(End of clause)

B.5 [OPTION(S) TO EXTEND COMPLETION OF WORK]{.underline}

(a) The Government may require the Contractor to continue performing
    services under this contract. The Contracting Officer may exercise
    the option(s) by issuance of a unilateral contract modification 60
    days or more before the completion date set forth in Section F.
    Should the option(s) be exercised, the resultant contract will
    include all terms and conditions of the basic contract as it exists
    at the time the option is exercised, except for increases in
    estimated cost and fee and other changes indicated below:

+----------------+---------+---------+---------+---------+---------+
|                | OPTION  | OPTION  | OPTION  | OPTION  | OPTION  |
|                | 1       | 2       | 3       | 4       | 5       |
|                |         |         |         |         |         |
|                | 10/     | 10/     | 10/     | 10/     | 10/     |
|                | 01/2010 | 01/2011 | 01/2012 | 01/2013 | 01/2014 |
|                |         |         |         |         |         |
|                | \-      | \-      | \-      | \-      | \-      |
|                | 09/     | 09/     | 09/     | 09/     | 09/     |
|                | 30/2011 | 30/2012 | 30/2013 | 30/2014 | 30/2015 |
+----------------+---------+---------+---------+---------+---------+
| Clause         |         |         |         |         |         |
| B.2\--Cost and |         |         |         |         |         |
| Fee increased  |         |         |         |         |         |
| as follows:    |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+
| Estimated Cost | TBN     | TBN     | TBN     | TBN     | TBN     |
+----------------+---------+---------+---------+---------+---------+
| Total          | TBN     | TBN     | TBN     | TBN     | TBN     |
| Estimated Cost |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+
| Max. Available | TBN     | TBN     | TBN     | TBN     | TBN     |
| Fee            |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+
| Total Option   | TBN     | TBN     | TBN     | TBN     | TBN     |
| Value          |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+
| Clause F.2 -   | Sep 30, | Sep.    | Sep.    | Sep.    | Sep.    |
| Completion of  | 2011    | 30,     | 30,     | 30,     | 30,     |
| Work Extended  |         | 2012    | 2013    | 2014    | 2015    |
| to:            |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+
| Paragraph (a)  | Sep.    | Sep.    | Sep.    | Sep.    | Sep.    |
| of J-28.2      | 30,     | 30,     | 30,     | 30,     | 30,     |
| ORDERING (FAR  | 2011    | 2012    | 2013    | 2014    | 2015    |
| 52.216-18)     |         |         |         |         |         |
| (OCT 1995)     |         |         |         |         |         |
| Extended to:   |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+
| Paragraph (d)  | Sep.    | Sep.    | Sep.    | Sep.    | Sep.    |
| of J-28.4      | 30,     | 30,     | 30,     | 30,     | 30,     |
| INDEFINITE     | 2011    | 2012    | 2013    | 2014    | 2015    |
| QUANTITY (FAR  |         |         |         |         |         |
| 52.216-22)     |         |         |         |         |         |
| (OCT 1995)     |         |         |         |         |         |
| Extended to:   |         |         |         |         |         |
+----------------+---------+---------+---------+---------+---------+

> H.46, [Administrative Contract Closeout]{.underline}, and H.47,
> [Adjustment for Final Space Shuttle Flight Launch Date]{.underline},
> shall also be adjusted based upon the exercise of an option.

(b) \(1\) The parties recognize that given the dynamic nature of the
    Space Shuttle Program and the length of time before these options,
    if exercised, would become effective, it is impossible to negotiate
    option prices prior to contract award with any reasonable degree of
    reliability. Given these circumstances, the cost of each option will
    not be definitized at the time of award of this SPOC; rather, the
    parties agree to definitize the price of each option prior to
    exercise, in an amount not to exceed the NASA-approved budget for
    that option period.

    2.  In the event the Government decides to pursue the exercise of
        Option 1, 2, 3, 4, or 5, a Request for Proposal (RFP) will be
        issued to the contractor in sufficient time to negotiate a fair
        and reasonable price for the option that does not exceed the
        NASA-approved budget for the associated option period. It is
        understood that the Statement of Work requirements will be
        adjusted, if necessary, to reflect reductions in the program due
        to budgetary constraints. The option(s) will reflect the same
        fee structure (e.g., type and ratio of fee pools) extant under
        the SPOC at the time of RFP release unless otherwise authorized
        in the RFP.

    3.  In the event the parties cannot agree on a definitized price for
        the option(s), the Government may exercise the option, including
        the same fee structure as the basic contract, at a total price
        equaling the NASA-approved budget for that option(s). The work
        content for the option period will be commensurate with the
        budget for that period. Failure to agree to this adjustment
        shall be a dispute under the "Disputes" clause of this contract.
        However, nothing in this clause shall excuse the Contractor from
        proceeding with the contract as changed.

    4.  Release of an RFP for Option 1, 2, 3, 4, or 5 does not obligate
        the Government to exercise the option.

(End of clause)

B.6 [CONTRACT ADJUSTMENT FOR LANDINGS AT SITES OTHER THAN
KSC]{.underline}

The Government may require that the Space Shuttle land at sites other
than KSC such as Dryden, White Sands Space Harbor (WSSH), TAL sites, and
other emergency landing sites throughout the world. Should the Space
Shuttle Program decide a Dryden landing is necessary, and a landing
occurs at Dryden, then the Contracting Officer will execute a contract
adjustment by issuance of a unilateral contract modification. Should the
landing at Dryden be necessary due to the Contractor's failure to meet
performance criteria within the Statement of Work, the contractor shall
support the Dryden landing at no increase in contract value, and
execution of a contract adjustment shall not be necessary. Should a
contract adjustment be executed for a Dryden landing, the contract value
will be increased as follows:

  ---------------------- --------------------------- --------------------------- --------------------------- ---------------------------
                         [LANDINGS IN FY             [LANDINGS IN FY             [LANDINGS IN FY             [LANDINGS IN FY
                         2007]{.underline}           2008]{.underline}           2009]{.underline}           2010]{.underline}

  Estimated Cost         \$1,729,691                 \$1,781,224                 \$1,835,286                 \$1,934,459

  Max Available AF       169,813                     174,872                     180,179                     189,916

  End of Program Fee     [56,604]{.underline}        [58,291]{.underline}        [60,060]{.underline}        [63,305]{.underline}

  Total Available Fee    [\$ 226,417]{.underline}    [\$ 233,163]{.underline}    [\$ 240,239]{.underline}    [\$ 253,221]{.underline}

  Total Contract Value   [\$1,956,108]{.underline}   [\$2,014,386]{.underline}   [\$2,075,525]{.underline}   [\$2,187,680]{.underline}
  ---------------------- --------------------------- --------------------------- --------------------------- ---------------------------

Landing at other sites is a requirement that is not priced into the
contract. Should the landing at the other sites be necessary due to the
Contractor's failure to meet performance criteria within the Statement
of Work, the contractor shall support the landing at no increase in
contract value.

(End of clause)

B.7 [TOTAL ANNUAL FUNDING PROFILE]{.underline}

The total annual funding profile for this contract is:

  ----------------------- ----------------------- -----------------------
  [YEAR]{.underline}      [AMOUNT]{.underline}    [VECP
                                                  Savings]{.underline}

  GFY 2007                \$1,791,898,161         \$ 0

  GFY 2008                \$1,697,335,918         \$ 0

  GFY 2009                \$1,571,987,065         \$ 0

  GFY 2010                \$1,321,548,239         \$ 0

  GFY 2011                \$ TBN                  \$ 0

  GFY 2012                \$ TBN                  \$ 0

  TOTAL                   \$6,382,769,383         \$ 0
  ----------------------- ----------------------- -----------------------

The Contracting Officer will issue contract modifications from time to
time to increase the funding profile amounts: (1) for Program
Provisioning, Facilities work, IDIQ tasks, as the associated value
become known, and (2) for changes or any other Government direction or
action for which the contract provides for an equitable adjustment in
contract value. The Contracting Officer will specifically identify the
bases on which increases are being made in correspondence transmitting
such modifications to the Contractor.

(End of clause)

(END OF SECTION)

SECTION C

DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

C.1 [SCOPE OF WORK]{.underline}

> The work the Contractor shall perform under this contract is described
> in Attachments J-1, J-5, and J-28.

(End of clause)

(END OF SECTION)

SECTION D

PACKAGING AND MARKING

D.1 [PACKAGING AND MARKING]{.underline}

> \(a\) The Contractor shall pack and mark all hardware deliverables
> under this contract in accordance with the provisions of NASA
> Procedural Requirements (NPR) 6000.1, "Requirements for Packaging,
> Handling, and Transportation for Aeronautical and Space Systems,
> Equipment, and Associated Components," current version.
>
> \(b\) The Contractor shall pack potentially hazardous items in
> accordance with paragraph 2.5 of NPR 6000.1, current version.
>
> \(c\) The Contractor shall develop Packaging, Handling, and
> Transportation Records, NASA Form 1426 (or equivalent information) in
> accordance with paragraph 3.2 of NPR 6000.1, current version, and
> shall be submitted and approved as directed by the Data Requirements
> Descriptions (DRDs) in accordance with paragraph 3.3 of NPR 6000.1,
> current version. Approval will be obtained from the Center
> Transportation Officer of the procuring location and a designated
> representative of the procuring activity. Shipment shall not proceed
> without this approval.
>
> \(d\) The Contractor\'s packaging specifications or procedures may be
> utilized if they are (i) not in conflict with cited NASA
> specifications and (ii) approved in writing by the Contracting
> Officer. In any conflict between NASA and the Contractor
> specifications or procedures, the NASA documents cited in this clause
> shall take precedence.
>
> \(e\) The Contractor shall place identical requirements on all
> subcontracts.
>
> \(f\) The Contractor shall prominently display a NASA Critical Space
> Item Label, NASA Form 1368, on the exterior of all Class I, Class II,
> and Class III interior packages and exterior shipping containers to
> alert handling personnel to the criticality of the item in accordance
> with paragraph 3.4 of NPR 6000.1, current version and NPR 6200.1,
> "NASA Transportation and General Traffic Management," current version.
> All markings for space flight items shall be blue in color. All
> shipping documents and purchasing documents for these items shall be
> marked \"ITEMS FOR SPACE FLIGHT USE.\"

(End of clause)

(END OF SECTION)

SECTION E

INSPECTION AND ACCEPTANCE

E.1 [LISTING OF CLAUSES INCORPORATED BY REFERENCE]{.underline}

(a) The following clauses are incorporated by reference:

> 52.246-3 Inspection of Supplies \-- Cost-Reimbursement (May 2001)
>
> 52.246-5 Inspection of Services \-- Cost-Reimbursement (Apr 1984)

(b) The following clauses are incorporated by reference and apply to
    facilities-related effort in this contract:

> 52.246-10 Inspection of Facilities (Apr 1984)

E.2 [SHIPPING INSTRUCTIONS]{.underline}

Shipping instructions for NASA centers, if applicable, are listed in
Attachment J-18.

(End of clause)

E.3 [HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT (GOVERNMENT
SPECIFICATION) (FAR 52.246-11) (FEB 1999)]{.underline}

The contractor shall comply with the higher-level quality standard
selected below.

-   SAE AS 9100:2004, Quality Systems -- Aerospace -- Model for Quality
    Assurance in Design, Development, Manufacturing, Installation, and
    Servicing.

(End of clause)

E.4 [HUMAN SPACE FLIGHT ITEM (NFS 1852.246-73) (MAR 1997) (Applicable to
human space flight hardware and flight-related equipment)]{.underline}

> The Contractor shall include the following statement in all
> subcontracts and purchase orders placed by it in support of this
> contract, without exception as to amount or subcontract level:
>
> \"FOR USE IN HUMAN SPACE FLIGHT; MATERIALS, MANUFACTURING, AND
> WORKMANSHIP OF HIGHEST QUALITY STANDARDS ARE ESSENTIAL TO ASTRONAUT
> SAFETY.
>
> IF YOU ARE ABLE TO SUPPLY THE DESIRED ITEM WITH A HIGHER QUALITY THAN
> THAT OF THE ITEMS SPECIFIED OR PROPOSED, YOU ARE REQUESTED TO BRING
> THIS FACT TO THE IMMEDIATE ATTENTION OF THE PURCHASER.\"

(End of clause)

E.5 RESERVED

E.6 RESERVED

(END OF SECTION)

SECTION F

DELIVERIES OR PERFORMANCE

F.1 [LISTING OF CLAUSES INCORPORATED BY REFERENCE]{.underline}

(c) The following clauses are incorporated by reference:

> 52.242-15 Stop-Work Order (Aug 1989) -- Alternate I (Apr 1984)

(d) The following clauses are incorporated by reference and apply to
    facilities-related effort in this contract:

> 52.242-16 Stop-Work Order -- Facilities (Aug 1989)

F.2 [COMPLETION OF WORK (JSC 52.211-95) (OCT 2001)]{.underline}

All work required under this contract, including submission of all
reports, shall be completed on or before September 30, 2010.

(End of clause)

F.3 [PLACE OF PERFORMANCE]{.underline}

The principal places of contractor's performance of the various work
elements of the program are NASA's Johnson Space Center, Kennedy Space
Center, Marshall Space Flight Center, and other places covered by the
Statement of Work.

(End of clause)

F.4 [BILLS OF LADING (1852.247-73) (JUN 2002)]{.underline}

The purpose of this clause is to define when a commercial bill of lading
or a government bill of lading is to be used when shipments of
deliverable items under this contract are f.o.b. origin.

(a) **Commercial Bills of Lading.** All domestic shipments shall be made
    via commercial bills of lading (CBLs). The Contractor shall prepay
    domestic transportation charges. The Government shall reimburse the
    Contractor for these charges if they are added to the invoice as a
    separate line item supported by the paid freight receipts. If paid
    receipts in support of the invoice are not obtainable, a statement
    as described below must be completed, signed by an authorized
    company representative, and attached to the invoice.

> "I certify that the shipments identified below have been made,
> transportation charges have been paid by (company name), and paid
> freight or comparable receipts are not obtainable.
>
> Contract or Order Number:
>
> Destination: \".

(b) **Government Bills of Lading.**

```{=html}
<!-- -->
```
(1) International (export) and domestic overseas shipments of items
    deliverable under this contract shall be made by Government bills of
    lading (GBLs). As used in this clause, "domestic overseas" means
    non-continental United States, i.e. Hawaii, Commonwealth of Puerto
    Rico, and possessions of the United States.

(2) At least 15 days before shipment, the Contractor shall request in
    writing GBLs from: Silvia Hanagriff, Contract Transportation, 2101
    NASA Parkway, M/C JB7, Houston, TX 77058. If time is limited,
    requests may be by telephone: 281-483-6512. At KSC, the request will
    be made to: Leslie Carroll, NASA Transportation, Headquarters Bldg.,
    M6-399, Rm. 2649J, Kennedy Space Center, FL 32899. If time is
    limited, requests may be by telephone: (321) 867-2975. Requests for
    GBLs shall include the following information.

```{=html}
<!-- -->
```
(i) Item identification/ description.

(ii) Origin and destination.

(iii) Individual and total weights.

(iv) Dimensional Weight.

(v) Dimensions and total cubic footage.

(vi) Total number of pieces.

(vii) Total dollar value.

(viii) Other pertinent data.

(End of clause)

F.5 [FLIGHT ITEM (JSC 52.247-95) (AUG 2005)]{.underline}

Block 16 of each Department of Defense Form 250 prepared for flight
hardware or related equipment to be shipped under this contract must be
annotated as follows in 1/4-inch letters or larger by hand printing or
rubber stamp:

"THIS IS A FLIGHT ITEM," OR "THIS IS MISSION ESSENTIAL GROUND SUPPORT
EQUIPMENT," as applicable.

(End of clause)

F.6 [UNFINISHED WORK CONTENT TRANSFERRED FROM SFOC INTO
SPOC]{.underline}

(a) The tasks specified in paragraph (b) below were initiated under the
    Space Flight Operations Contract (SFOC) NAS9-20000, and were not
    anticipated to be completed by September 30, 2006. The remaining
    effort under these tasks was cancelled under SFOC effective
    September 30, 2006. These tasks are hereby authorized to be
    completed under this contract starting on October 1, 2006.

(b) The Contractor shall submit a plan for transfer of associated
    contract value for this effort by October 31, 2006.

  ------------------------------------------------ -------------------- ---------------------
  [Title]{.underline}                              Estimated\           Estimated\
                                                   Completion\          [Value]{.underline}
                                                   [Date]{.underline}   

  19908 Lightweight Seat Enhancement Study         Oct-06               TBD

  23411 Freon Aft Cold Plate Network Filter (FY06) Dec-06               TBD

  23451 Replacement of Obsolete BASF PDL 1034 Foam Sep-07               TBD
  (Two) (FY06)                                                          

  23440 Development and Implementation of          Feb-07               TBD
  Polycarbonate Window Protectors                                       

  19861 Material Static Age Life Extension         Oct-06               TBD

  19892 ECLSS Bulkhead Penetration Fluid Line Flex Feb-07               TBD
  Hoses Bench Test and Certification Update                             

  19893 ET Door Tile Ice Impact Testing            Nov-06               TBD

  23449 Stud Hang-Up (SHU) Loads Cycle Analysis    Apr-07               TBD

  23448 ECO Sensor System                          Feb-07               TBD

  23464 Ultrasonic Leak Detector                   Nov-07               TBD

  Waste Collector System Dash Number Change to -25 Dec-06               TBD

  23471 Booster Fan Bypass for Spacehab Missions   Nov-06               TBD

  19911 Streamlined NASA Safety System Process     Dec-06               TBD

  RCCR H/W Testing and Redesign                    Dec-06               TBD

  19910 Orbiter Cert Verification                  Jan-07               TBD

  19906 Phase II Delta Qaual Testing/Cert of       Dec-06               TBD
  Radiator Retract Assembly                                             

  23207 Convert PE Entry Aeroheating Data Book to  Nov-06               TBD
  Electronic Format                                                     

  23187 RCC Chin Panel 3D Thermal Math Model       May-07               TBD
  Analysis and Development                                              

  19702 PRCS/VRCS Orbiter Plume Environment Data   Aug-07               TBD
  Base                                                                  

  23056 Phase I Development Tests for Field Repair Feb-07               TBD
  of Exposed RCC Substrate                                              

  19800 APU Fuel Tank                              Jul-07               TBD

  19680 Structural Life Analysis Clean Up          Apr-07               TBD

  23029 Expanding Payload Latch Retention System   Sep-07               TBD

  234430Accoustic Measurement Implementation for   Nov-06               TBD
  OV-103                                                                

  21408 Convert 11EH Tooling to Certified GSE      Dec-06               TBD

  21424 RCS Thruster Trickle Purge System GSE      Jan-07               TBD
  Redesign & Certification                                              

  23452 Fiducial Markings on WLE RCC T-Seals       Feb-07               TBD

  19633 FY01 Abort Enhancements                    Nov-06               TBD

  23438 FRCS Down Firing Jets Rain Cover           Feb-07               TBD
  Improvements                                                          

  23442 ET Door Latch Actuator Mod Feasibility     Dec-06               TBD
  Study                                                                 

  19840 Space Crew Survival                        Feb-07               TBD

  23417 Remote Controlled Orbiter                  Dec-06               TBD

  23469 Wing Leading Edge Impact Detection System  Nov-06               TBD

  Supa Redesign Effort                             Dec-07               TBD

  17770 High Priority Environmental Analyses       Oct-06               TBD

  23054 Identification of a Supplier for Type II   Oct-06               TBD
  Beta Cloth                                                            

  23111 Update to RCC Step and Gap Analysis        Oct-06               TBD

  23365 Mass Proterties Database Re-Host           Oct-06               TBD

  234476 MLG Door Thermal Barrier Cavity           Noc-06               TBD
  Protection                                                            

  19904 Orbiter Wing Stringer Analysis             Nov-06               TBD

  19896 Emergency Egress Slide                     Feb-07               TBD

  23108 Structural Life (Fatigue/Fracture)         Oct-06               TBD
  Analysis Tools Upgrade                                                

  23470 WLE IDS GFE Box Installation Update        Jan-07               TBD

  19903 Sky Genie                                  Nov-06               TBD

  ATK Crack Repair                                 Dec-06               TBD

  17041 APU Qual Test Ext                          Dec-08               TBD

  23086 APU Fleet Leader                           Dec-08               TBD

  Station to Shuttle Power Transfer System (SSPTS) Jul-07               TBD

  19743 Main Landing Gear Door (MLGD) Thermal      Dec-06               TBD
  Barrier Redesign                                                      

  BRI-18 Qual & Cert Orbiter Hardening (OH) Phase  Dec-06               TBD
  3A (WBS 1.8.23.3)                                                     

  Thicker Side and Overhead Windows                Jan-09               TBD

  19582 Math Models ASKA to NASTRAN Conversion     Jul-07               TBD

  19732 Metal Bellows Flex Hose Qual & Cert        Feb-07               TBD

  19637 OMDP Interval Extension Evaluation         Nov-06               TBD

  19768 OBSS Phase II Additional Hardware          Dec-06               TBD

  Horse Collar                                     Oct-06               TBD

  18928 3-String GPS Implementation                Oct-06               TBD

  18985 N2/O2 Control Panel Upgrade                Jan-07               TBD

  23226 PGME Water for Water Spray Boiler          Feb-07               TBD
  Evaluation                                                            

  19711 Develop NDE Methods for RCC Panels         Dec-06               TBD

  23269 On-Orbit TPS Damage Assessment             Jun-07               TBD

  19826 Arc Jet Test Support at Boeing St. Louis   Jan-07               TBD
  Large Core Arc Tunnel (LCAT) Facility                                 

  19881 Emittance Primer Coating Testing and       Jun-07               TBD
  Analysis                                                              

  19719 On-Orbit TPS Damage Assessment Team 4      Apr-07               TBD

  19856 ON-Orbit TPS Repair R&D Support            Feb-07               TBD

  23269 RTF Tile Repair STA-54                     Mar-07               TBD

  19476 MLG Improved Tire & Wheel                  Dec-06               TBD

  19735 Front Spar Protection for Sneak Flow       May-07               TBD

  ATK Thiokol Plug Repair                          Feb-07               TBD

  19755 OBSS Phase I                               Oct-06               TBD

  AHMS Phase I Controller                          Jul-07               TBD

  ID/IQ 007, GFE Tile Overlay                      Dec-06               TBD

  ID/IQ 006, FY06 TPS Damage Assessment            Dec-06               TBD

  GFE Tile Overlay Repair/Additional Support       Dec-06               TBD
  Effort - IDIQ No. 016                                                 

  ID/IQ 018 23455 Mini Boom Phase I                Dec-06               TBD

  ID/IQ 015, Transition                            Dec-06               TBD

  Space Shuttle Crew Escape Equipment              Feb-07               TBD
  Communication Upgrade Project (SCCUP) (FY06)                          

  FCE Support for PTU Modifications to -510        Nov-06               TBD
  (Start-up)                                                            

  David Clark Subcontractor consumable items       Dec-06               TBD
  associated with Contract Extension core content                       
  to be moved from SFOC (FY06) to SPOC (FY07)                           

  CEE consumable items associated with Contract    Dec-06               TBD
  Extension core content to be moved from SFOC                          
  (FY06) to SPOC (FY07)                                                 

  Provisioning and Integration Freeze Dryer, Model Feb-07               TBD
  Quanta 36IB                                                           

  Hydraulic Actuator Refurbishment                 Sep-07               TBD

  Fleet Leader Phase II (WBS 1.8.20)               Sep-07               TBD

  12 and 17 Inch Orbiter Feed Lines                Jul-07               TBD

  SFOC Operations Roll Thru of Orbiter Material    Mar-07               TBD
  Hardware Dollars to be partnered with the Local                       
  NASA Customer                                                         

  Vacuum Jacketed (12 Inch) LH2 Feed Lines         May-07               TBD

  Mechanical Flight Control (MFC) STE Upgrade (WBS Dec-06               TBD
  1.8.22.4)                                                             

  Waste Collection Subsystem (WCS) Life Cycle      Jun-07               TBD
  Trade Study Implementation Plan                                       

  Rudder Speed Brake (RSB) Phase IV - Manufacture  Mar-07               TBD
  Eight New RSB Actuators and Two RSB Actuator                          
  Qualification Units                                                   

  Rudder Speed Brake (RSB) Actuators - Phase I     Jun-07               TBD
  (Boeing Task #47504)                                                  

  Rudder Speed Brake (RSB) Actuators               Nov-06               TBD
  Reinstallation Hardware and NESC Support - Phase                      
  5 (Boeing Task #47505)                                                

  Return to Flight (RTF) Lockheed Reinforced       Jan-07               TBD
  Carbon-Carbon (RCC) Panels (Replacement of 3 RCC                      
  Panels)                                                               

  Flex Hose Spares for Limited Life Program        Sep-07               TBD

  Fleet Leader Phase I (WBS 1.8.20)                Sep-07               TBD

  NSLD STE Repair Spares Provisioning - Phase 1    Jun-07               TBD

  79K Fluid Component Specification Update Project Jul-07               TBD
  (FY05)                                                                

  RPS Survivability Database Deployment (FY06)     May-07               TBD

  Hazardous Gas Detection Application Support      Sep-07               TBD

  Human System Integration (HSI) Gap Analysis      Jun-07               TBD
  Study                                                                 

  Nav-Aids Automated Flight Inspection System      Mar-07               TBD
  (AFIS) Data Downlink                                                  

  Pad A GSE Infrastructure Upgrades (Cryos & Other Nov-06               TBD
  GSE System) - MA Support                                              

  Pad A GSE Controls Subsystem Modifications       Nov-06               TBD

  Support for KSC Transition & Retirement          Oct-06               TBD

  FY\'05 - PPTL RPS Survivability                  Jul-06               TBD

  FY05 Hurricane Equitable Adjustment (Task 5) -   Mar-07               TBD
  CSR Trailers                                                          

  OSB II Activation                                Mar-08               TBD

  Upgrade Critical Lifting Devices Rescope         Sep-07               TBD

  FY \'05 Hurricane Equitable Adjustment (Task     Nov-06               TBD
  4) - OSB I Repairs                                                    

  FY \'05 Hurricane Equitable Adjustment           Oct-06               TBD
  (Task 1) - Facilities                                                 

  Crawler Transporter Upgrades SA 810              Dec-06               TBD

  Crawler Transporter Upgrades SA 914              Sep-07               TBD

  Crawler Transporter Upgrades SA1303              May-07               TBD

  Pad A GSE Infrastructure Upgrades (Cryos & Other Nov-06               TBD
  GSE Systems)                                                          

  FY \'00 PPTL - Upgrade Hypergolic Flowmeters     Nov-06               TBD

  FY \'06 PPTL - Replace C&T S-Band PM GSE         Oct-06               TBD

  Revitalization of Low Voltage Power Pad A        Dec-06               TBD
  Activation Ph 1, 2, & 3                                               

  MLP3 Cable Interconnect Replacement - Ph 2       Dec-06               TBD
  Design                                                                

  FY \'04 PPTL - KCCS Technology Update            Mar-07               TBD

  Pad A GSE Infrastructure Upgrades (ECS &         Oct-06               TBD
  Hypers) - Impl                                                        

  FY \'06 PPTL - Modify Davit Cranes for Class I   Oct-06               TBD
  Division II Explosion Proof Rqmt                                      

  FY \'06 PPTL - GSE Controls Integration          Nov-06               TBD

  VAB GSE Controls Revitalization                  Nov-06               TBD

  FY\' 05 PPTL - CUBIC II Upgraded Shuttle Bus     Oct-06               TBD
  Tester Cards for MEC OMRSD Testing                                    

  Pad A Infrastructure Revitalization (Tasks B, C, Nov-06               TBD
  D)                                                                    

  Refurbish VAB NTAD & HB3 Horizontal & Vertical   Dec-07               TBD
  Doors/Openings                                                        

  Refurbish Highbay 1 Doors/Openings - VAB Ph 2    Nov-06               TBD
  Implementation (FPN 7419)                                             

  Modify Critical Lifting Devices to Meet Safety   Nov-06               TBD
  Requirements, Ph I                                                    

  Pad A Infrastructure Revitalization (TaskE-1     Jan-07               TBD
  White Room Act/Deact)                                                 

  Pad A Infrastructure Revitalization (TaskE-2     Dec-06               TBD
  Activation/Deactivation)                                              

  Anntenna Access Platform Pad A - Construction    Oct-06               TBD

  Anntenna Access Platform Pad A - Activation      Dec-06               TBD

  Pad A Washdown System Enhancements -             Nov-06               TBD
  Construction                                                          

  Pad A Washdown System Enhancements - Activation  Dec-06               TBD

  Refurbish Inaccessible Areas of RSS Drive        Oct-06               TBD
  Trucks, Pad A                                                         

  Enhance Optical Tracker Hardware, Rev.2          Mar-06               TBD

  Technical Information Systems - Electronic       Jan-07               TBD
  Change Management System (ECMS)                                       

  Management Integration support to the            May-07               TBD
  Constellation Project                                                 

  Management Integration - ADPE Hardware           Nov-06               TBD

  STS-118 PACK (Payload Active Cooling Kit) Line   Dec-06               TBD
  and Washer Fabrication                                                

  Shuttle Power Distribution Unit (Option 1)       May-07               TBD

  Entry Computational Fluid Dynamics to support    Nov-06               TBD
  Debris Transport Analysis (CFD)                                       

  Mini Boom Cargo Integration Hardware             Jun-07               TBD

  SE&I Mini Boom                                   Nov-07               TBD

  EME Hazard Report Close Out                      Aug-07               TBD

  Debris Day of Launch Tools (RTF)                 Feb-07               TBD

  Roll Maneuver (RTF)                              Aug-07               TBD

  Rollout Fatigue Environment (RTF)                Feb-07               TBD

  OBSS Generic Certification (RTF)                 Nov-06               TBD

  IA700 Wind Tunnel Test Final Reports (RTF)       Nov-06               TBD

  ET Mold Line Revision (See subtasks below)       May-07               TBD

  -STS 115 IFR Envronments                                              TBD

  -IS22 Component Wind Tunnel Test                                      TBD

  -ET PAL                                                               TBD

  -Glenn Research WTT                                                   TBD

  IS-22 WTT Replan                                 May-07               TBD

  Replace HVAC Units, Building 153                 Nov-07               TBD

  Replace Switch Gear (Sub 7 & 8)                  Oct-07               TBD

  NESC                                             Mar-07               TBD

  Hypalon                                          Jan-07               TBD

  IEA Supportability                               Mar-07               TBD

  CRD Production                                   Nov-06               TBD

  CRD Reinstatement                                Nov-06               TBD

  ARF Fire Detection System                        Mar-07               TBD

  ET Pal Ramp Instrumentation BI 126 & 127         Dec-06               TBD

  AFT Skirt Instrumentation BI 128                 Dec-06               TBD

  Parachute Support for the CEV Project            Dec-06               TBD

  ASA Calibration Test Set                         Mar-07               TBD

  Process Control Video and Pamphlet (Fusion)      Mar-07               TBD

  Flight Hardware                                  Sep-07               TBD

  GSE Non-configured Hardware                      Sep-07               TBD

  IT Security Plan Assessment                      Jan-07               TBD

  S-405 Integrated Certification Hardware          Dec-06               TBD
  Preparation Phase                                                     
  ------------------------------------------------ -------------------- ---------------------

(End of clause)

(END OF SECTION)

SECTION G

CONTRACT ADMINISTRATION DATA

G.1 [LISTING OF CLAUSES INCORPORATED BY REFERENCE]{.underline}

> The following clauses are incorporated by reference:
>
> 1852.223-71 Frequency Authorization (Dec 1988)
>
> 1852.227-70 New Technology (May 2002)
>
> 1852.227-72 Designation of New Technology Representative and Patent
> Representative (Jul 1997); in paragraph (a) add:*\
> AL/Patent Representative\
> NASA Lyndon B. Johnson Space Center\
> Houston, TX 77058\
> and*
>
> *AT/Technology Transfer & Commercialization Office\
> NASA Lyndon B. Johnson Space Center\
> Houston, TX 77058*
>
> 1852.227-86 Commercial Computer Software-Licensing (Dec 1987)
>
> 1852.242-73 NASA Contractor Financial Management Reporting (Nov 2004)
>
> 1852.245-70 Contractor Requests For Government-Owned Equipment (Jul
> 1997)

G.2 [SUBMISSION OF VOUCHERS FOR PAYMENT (1852.216-87) (MAR
1998)]{.underline}

(a) The designated billing office for cost vouchers for purposes of the
    Prompt Payment clause of this contract is indicated below.

> NASA, Lyndon B. Johnson Space Center
>
> LF231/Financial Services Branch (Payables Group)
>
> Houston, TX 77058
>
> Public vouchers for payment of costs shall include a reference to the
> number of this contract.

(b) \(1\) If the contractor is authorized to submit interim cost
    vouchers directly to the NASA paying office, the original voucher
    should be submitted to:

> NASA, Lyndon B. Johnson Space Center
>
> LF231/Financial Services Branch (Payables Group)
>
> Houston, TX 77058

(2) For any period that the Defense Contract Audit Agency has authorized
    the Contractor to submit interim cost vouchers directly to the
    Government paying office, interim vouchers are not required to be
    sent to the Auditor, and are considered to be provisionally approved
    for payment, subject to final audit.

(3) Copies of vouchers should be submitted as directed by the
    Contracting Officer.

```{=html}
<!-- -->
```
(c) If the contractor is not authorized to submit interim cost vouchers
    directly to the paying office as described in paragraph (b), the
    contractor shall prepare and submit vouchers as follows:

```{=html}
<!-- -->
```
(1) One original Standard Form (SF) 1034, SF 1035, or equivalent
    Contractor's attachment to:

> N/A

(2) Five copies of SF 1034, SF 1035A, or equivalent Contractor's
    attachment to the following offices by insertion in the memorandum
    block of their names and addresses:

```{=html}
<!-- -->
```
(i) Copy 1 NASA Contracting Officer

(ii) Copy 2 Auditor

(iii) Copy 3 Contractor

(iv) Copy 4 Contract administration office; and

(v) Copy 5 Project management office.

```{=html}
<!-- -->
```
(3) The Contracting Officer may designate other recipients as required.

```{=html}
<!-- -->
```
(d) Public vouchers for payment of fee shall be prepared similarly to
    the procedures in paragraphs (b)or (c) of this clause, whichever is
    applicable, and be forwarded to:

> NASA, Lyndon B. Johnson Space Center
>
> BV/Space Shuttle Procurement Office
>
> Houston, TX 77058
>
> This is the designated billing office for fee vouchers for purposes of
> the Prompt Payment clause of this contract.

(e) In the event that amounts are withheld from payment in accordance
    with provisions of this contract, a separate voucher for the amount
    withheld will be required before payment for that amount may be
    made.

(End of clause)

G.3 [RESERVED]{.underline}

G.4 [RESERVED]{.underline}

G.5 [TECHNICAL DIRECTION (1852.242-70) (SEPT 1993)]{.underline}

(a) Performance of the work under this contract is subject to the
    written technical direction of a Contracting Officer\'s Technical
    Representative (COTR), who shall be specifically appointed by the
    Contracting Officer in writing in accordance with NFS 1842.270.
    \"Technical direction\" means a directive to the Contractor that
    approves approaches, solutions, designs, or refinements; fills in
    details or otherwise completes the general description of work or
    documentation items; shifts emphasis among work areas or tasks; or
    furnishes similar instruction to the Contractor. Technical direction
    includes requiring studies and pursuit of certain lines of inquiry
    regarding matters within the general tasks and requirements in
    Section C of this contract.

(b) The COTR does not have the authority to, and shall not, issue any
    instruction purporting to be technical direction that --

```{=html}
<!-- -->
```
(1) Constitutes an assignment of additional work outside the statement
    of work;

(2) Constitutes a change as defined in the Changes clause;

(3) Constitutes a basis for any increase or decrease in the total
    estimated contract cost, the fixed fee (if any), or the time
    required for contract performance;

(4) Changes any of the expressed terms, conditions, or specifications of
    the contract; or

(5) Interferes with the Contractor\'s rights to perform the terms and
    conditions of the contract.

```{=html}
<!-- -->
```
(c) All technical direction shall be issued in writing by the COTR.

(d) The Contractor shall proceed promptly with the performance of
    technical direction duly issued by the COTR in the manner prescribed
    by this clause and within the COTR\'s authority. If, in the
    Contractor\'s opinion, any instruction or direction by the COTR
    falls within any of the categories defined in paragraph (b) above,
    the Contractor shall not proceed but shall notify the Contracting
    Officer in writing within 5 working days after receiving it and
    shall request the Contracting Officer to take action as described in
    this clause. Upon receiving this notification, the Contracting
    Officer shall either issue an appropriate contract modification
    within a reasonable time or advise the Contractor in writing within
    30 days that the instruction or direction is --

```{=html}
<!-- -->
```
(1) Rescinded in its entirety; or

(2) Within the requirements of the contract and does not constitute a
    change under the Changes clause of the contract, and that the
    Contractor should proceed promptly with its performance.

```{=html}
<!-- -->
```
(e) A failure of the Contractor and Contracting Officer to agree that
    the instruction or direction is both within the requirements of the
    contract and does not constitute a change under the Changes clause,
    or a failure to agree upon the contract action to be taken with
    respect to the instruction or direction, shall be subject to the
    Disputes clause of this contract.

(f) Any action(s) taken by the Contractor in response to any direction
    given by any person other than the Contracting Officer or the COTR
    shall be at the Contractor\'s risk.

(End of clause)

G.6 [RESERVED]{.underline}

G.7 [FINANCIAL REPORTING OF NASA PROPERTY IN THE CUSTODY OF CONTRACTORS
(1852.245-73) (OCT 2003)]{.underline}

(a) The Contractor shall submit annually a NASA Form (NF) 1018, NASA
    Property in the Custody of Contractors, in accordance with the
    provisions of 1845.505-14, the instructions on the form, subpart
    1845.71 and any Supplemental Instructions for the current reporting
    period issued by NASA.

(b) \(1\) Subcontractor use of NF 1018 is not required by this clause;
    however, the Contractor shall include data on property in the
    possession of subcontractors in the annual NF 1018.

```{=html}
<!-- -->
```
(2) The Contractor shall mail the original signed NF 1018 directly to
    the cognizant NASA Center Deputy Chief Financial Officer, Finance,
    unless the Contractor uses the NF 1018 Electronic Submission System
    (NESS) for report preparation and submission.

(3) One copy shall be submitted (through the Department of Defense (DOD)
    Property Administrator if contract administration has been delegated
    to DOD) to the following address: Johnson Space Center, Mail Code
    JB3, Houston, Texas 77058 unless the Contractor uses the NF 1018
    Electronic Submission System (NESS) for report preparation and
    submission.

```{=html}
<!-- -->
```
(c) \(1\) The annual reporting period shall be from October 1 of each
    year through September 30 of the following year. The report shall be
    submitted in time to be received by November 30. The information
    contained in these reports is entered into the NASA accounting
    system to reflect current asset values for agency financial
    statement purposes. Therefore, it is essential that required reports
    be received no later than November 30. Some activity may be
    estimated for the month of September, if necessary, to ensure the NF
    1018 is received when due. However, contractors procedures must
    document the process for developing these estimates based on planned
    activity such as planned purchases or NASA Form 533 (NF 533
    Contractor Financial Management Report) cost estimates. It should be
    supported and documented by historical experience or other
    corroborating evidence, and be retained in accordance with FAR
    Subpart 4.7, Contractor Records Retention. Contractors shall
    validate the reasonableness of the estimates and associated
    methodology by comparing them to the actual activity once that data
    is available, and adjust them accordingly. In addition, differences
    between the estimated cost and actual cost must be adjusted during
    the next reporting period. Contractors shall have formal policies
    and procedures, which address the validation of NF 1018 data,
    including data from subcontractors, and the identification and
    timely reporting of errors. The objective of this validation is to
    ensure that information reported is accurate and in compliance with
    the NASA FAR Supplement. If errors are discovered on NF 1018 after
    submission, the contractor shall contact the cognizant NASA Center
    Industrial Property Officer (IPO) within 30 days after discovery of
    the error to discuss corrective action.

```{=html}
<!-- -->
```
(2) The Contracting Officer may, in NASA's interest, withhold payment
    until a reserve not exceeding \$25,000 or 5 percent of the amount of
    the contract, whichever is less, has been set aside, if the
    Contractor fails to submit annual NF 1018 reports in accordance with
    1845.505-14 and any Supplemental Instructions for the current
    reporting period issued by NASA. Such reserve shall be withheld
    until the Contracting Officer has determined that NASA has received
    the required reports. The withholding of any amount or the
    subsequent payment thereof shall not be construed as a waiver of any
    Government right.

```{=html}
<!-- -->
```
(d) A final report shall be submitted within 30 days after disposition
    of all property subject to reporting when the contract performance
    period is complete in accordance with (b)(1) through (3) of this
    clause.

(End of clause)

G.8 [RESERVED]{.underline}

G.9 [DESIGNATION OF CONTRACTING OFFICER'S TECHNICAL MANAGEMENT
REPRESENTATIVES]{.underline}

The COTR may elect to have one or more Technical Management
Representatives (TMRs) for the purposes of monitoring of and insight
into specified work areas. The TMRs will be appointed in writing by the
Contracting Officer. The TMR's authority will be limited to that
specified in the Contracting Officer's Letter of Appointment. Contractor
change notification requirements are identical to those reflected in
Clause G.5.

(End of clause)

G.10 [SECURITY/BADGING REQUIREMENTS FOR FOREIGN NATIONAL VISITORS AND
EMPLOYEES/REPRESENTATIVES OF FOREIGN CONTRACTORS]{.underline}

(a) An employee of a domestic Johnson Space Center (JSC) contractor or
    its subcontractor who is not a U.S. citizen (foreign national) may
    not be admitted to any NASA Installation site for purposes of
    performing work without special arrangements. In addition, all
    employees or representatives of a foreign JSC
    contractor/subcontractor may not be admitted to any NASA
    Installation site without special arrangements. For employees as
    described above, advance notice must be given to the Security Office
    of the host NASA Installation at least 3 weeks prior to the
    scheduled need for access to the site so that instructions on
    obtaining access may be provided. In addition to these requirements,
    foreign nationals/representatives from designated countries that
    request physical/logical access to any NASA installation or
    information resource must be approved by both the local NASA center
    and NASA HQ. All designated foreign national/representative requests
    must be submitted at least 4 weeks before the start date of access.
    Contractors should be aware that approval for access to the site and
    issuance of a badge may take much longer than three weeks and
    sufficient lead time must be allowed to accommodate the approval
    process.

(b) All visit/badge requests for persons described in (a) above must be
    entered in the NASA Foreign National Management System (NFNMS) for
    acceptance, review, concurrence and approval purposes. When an
    authorized company official requests a NASA Installation badge for
    site access, he/she is certifying that steps have been taken to
    ensure that its contractor or subcontractor employees, visitors, or
    representatives will not be given access to export-controlled or
    classified information for which they are not authorized. The
    authorized company officials shall serve as the contractor's
    representative(s) in certifying that all visit/badge request forms
    are processed in accordance with the cognizant NASA Installation
    security and export control procedures. No foreign national,
    representative, or resident alien contractor/subcontractor employee
    shall be granted access into any NASA Installation until approved
    and processed through the NFNMS. Unescorted access will not be
    granted unless a favorable National Agency Check (NAC) has been
    completed by the cognizant NASA Installation Security Office, and an
    approved NASA Foreign National Visitor Security/Technology Control
    Plan (STTCP), (previously called the Access Control Plan) has been
    submitted and approved..

(c) The contractor agrees that it will not employ for the performance of
    work onsite at any NASA Installation any individuals who are not
    legally authorized to work in the United States. If the cognizant
    NASA Installation Industrial Security Specialist or the contracting
    officer has reason to believe that any employee of the contractor
    may not be legally authorized to work in the United States and/or on
    the contract, the contractor may be required to furnish copies of
    Form I-9 (Employment Eligibility Verification), U.S. Department of
    Labor Application for Alien Employment Certification, and any other
    type of employment authorization document.\
    \
    The contractor agrees to provide the information requested by the
    cognizant NASA Installation Security Office in order to comply with
    NASA policy directives and guidelines related to foreign visits to
    NASA facilities so that (1) the visitor/employee/ representative may
    be allowed access to JSC or any other NASA Centers for performance
    of this contract, (2) required investigations can be conducted,
    and (3) required annual or revalidation reports can be submitted to
    NASA Headquarters. All requested information must be submitted in a
    timely manner in accordance with instructions provided by JSC or any
    other Center to be visited.

(End of clause)

G.11 [GOVERNMENT-FURNISHED PROPERTY - SPECIAL PROVISION]{.underline}

(a) For performance of work under this contract, the Government will
    make available Government Furnished Property (GFP) identified in
    Attachment J-9 on a no-charge-for-use basis. In accordance with the
    Government Property clause of this contract, the Contractor is
    accountable for that property, except where identified for
    contractor "use only".

(b) The Government shall have the option to purchase any property (as
    defined in FAR 45.101) acquired, manufactured, or constructed in
    support of this contract if title does not already vest with the
    Government by other provisions of this contract. The acquisition
    price to the Government shall be the contractor's net book value, if
    any, of that property at the time of the Government's purchase.

(c) The contractor shall plan, manage, and implement all restoration,
    modernization, maintenance, and repair projects that are associated
    with the property identified in Attachment J-9 (excluding that
    property in Attachment J-9 identified for contractor "use only"),
    and that have an estimated cost for implementation of less than
    \$500,000. The contractor shall also plan, manage, and implement new
    construction projects associated with the above mentioned property,
    that have an estimated cost for implementation of less than
    \$500,000 and are required to effectively perform other work
    required under this contract. These projects will be authorized in
    accordance with the provisions of clause H.20 (b).

(d) The Contractor shall incorporate paragraph (b) of this clause in all
    subcontracts with companies having an ownership interest in the
    Contractor performing this contract.

(e) The Contractor within their Government Property Accountability
    System maintains a current listing of GFP.

(End of clause)

G.12 [INSTALLATION PROVIDED SERVICES (IPS)]{.underline}

For performance of work under this contract, the Government will make
available the IPS identified in Attachment J-10 on a no-charge-for-use
basis. The IPS will be provided to the extent that it is available and
approved for use by the Contracting Officer. Attachment J-10 delineates
any special provisions associated with the IPS at different locations.
IPS may be provided in support of contract work which is performed both
on-site and off-site. "On site" means within the physical boundaries of
the Centers identified in Attachment J-10 and any other local area they
occupy and use for the conduct of Center activities (e.g., part of
Ellington Field near to and used by Johnson Space Center). "Off-site"
refers to contractor facilities (leased or owned) in reasonably close
proximity to their related NASA centers. To the extent that the IPS
described in Attachment J-10 are designated as furnished to "off-site"
facilities, they will in many cases be physically performed on-site at
the related Center (e.g., photography services, calibration service). If
the Government fails to provide the IPS specified in Attachment J-10 and
that failure adversely affects the Contractor's ability to perform the
contract, the Contracting Officer shall, upon timely written request
from the Contractor, (1) make a determination of the effect on the
Contractor and (2) equitably adjust the contract in accordance with the
procedures provided in the Changes clause of the contract. Such
equitable adjustments, however, shall not include adjustments to fee.

(End of clause)

G.13 [SPECIAL COST PROVISIONS]{.underline}

Without otherwise affecting the applicability of the cost principles set
forth in FAR Part 31 and pursuant to the terms of FAR 52.216-7,
Allowable Cost and Payment, the Contractor shall be reimbursed for such
actual and allowable expenditures incurred in the performance of work
required by this contract as may be approved by the Contracting Officer
subject to the following limitations and provisions:

(a) RESERVED.

(b) [Provisional Billing Rates.]{.underline} Provisional Billing rates
    for indirect cost pools shall be established by the Contracting
    Officer based on proposals from the Contractor, and after review of
    Government auditors. These provisional rates shall be specified in
    writing and may be revised, either retroactively or prospectively,
    by the Contracting Officer.

(c) *RESERVED*.

(d) *Relocation Costs*.

```{=html}
<!-- -->
```
(1) Reimbursement for relocation costs shall be in accordance with the
    provisions of FAR 31.205-35 or the most economical rates
    commercially available. No relocation costs will be reimbursable
    under this contract for employees whose residence at time of hiring
    or assignment to this contract was within a 50 mile radius of the
    applicable place of contract performance.

(2) It is mutually agreed that upon expiration or termination of this
    contract, the Contractor shall not be entitled to reimbursement for
    cost of employee relocation.

```{=html}
<!-- -->
```
(e) *Household Goods Shipments*.

```{=html}
<!-- -->
```
(1) Movement of household goods and personal effects of Contractor
    employees, when the total transportation costs are to be reimbursed
    by the Government, shall be made by carriers furnishing reduced
    rates under Section 10721 (formerly Section 22) quotations of the
    Interstate Commerce Act or commercial rates if more economically
    advantageous. The Contractor will inform the Chief, Transportation
    Branch, Mail Code JB, Lyndon B. Johnson Space Center, Houston, Texas
    77058, of each planned movement; and that office will provide the
    Contractor with applicable instructions for household goods movement
    if Section 10721 rates have been utilized and such other support or
    guidance that is requested.

(2) The Contractor shall furnish the Chief, Transportation Branch/JSC
    with advance information of any planned mass movement of personnel
    (25 or more families) 30 or more days prior to the start of any
    major relocations.

(3) Carrier's bill of lading and related shipping documents will be
    annotated with the following statement:

> "TRANSPORTATION HEREUNDER IS FOR THE GOVERNMENT, AND THE ACTUAL TOTAL
> TRANSPORTATION CHARGES PAID TO THE CARRIER OR CARRIERS ARE TO BE
> REIMBURSED BY THE GOVERNMENT"

(4) One copy of all carrier's bills of lading will be furnished to the
    Chief, Transportation Branch/JSC on movements of household goods and
    personal effects which are the results of the relocation of
    Contractor employees when the total transportation costs are to be
    reimbursed by the Government. Requests for deviations from the
    procedures established by this clause shall be in writing and
    addressed to the Contracting Officer.

(5) Such requests must be made prior to the proposed move and in
    sufficient time for the Contracting Officer to make a decision.
    Failure to comply with the provisions of this clause may result in
    the disallowance of costs, which are in excess of those which would
    have resulted from utilization of reduced rate obtainable under the
    provisions of the clause.

```{=html}
<!-- -->
```
(f) [Travel.]{.underline} Travel required in the performance of work
    under this contract must be in accordance with the Contractor's
    Government-approved written travel policy.

(g) [Severance Pay]{.underline}. Reimbursement of severance pay shall be
    in accordance with FAR 31.205-6(g). However, in no event shall the
    Government reimburse the Contractor for severance pay for any
    Contractor employee who voluntarily elects to stay in place and work
    for a succeeding contractor, subcontractor, or member subcontractor.
    The Government shall cease reimbursement of severance pay under mass
    severance, beyond the initial lump sum, or subsequent installments,
    as identified in the contractor's Layoff and Reinstatement policy,
    upon reinstatement of an employee with the company, employment by a
    succeeding contractor or subcontractor, employment by a NASA
    contractor, NASA subcontractor or NASA within a 50 mile radius of
    the employee's last location of employment with the company.

(h) [Fringe Benefits.]{.underline} The Contractor shall inform the
    Contracting Officer of all proposed changes in fringe benefits prior
    to such changes being implemented. Fringe benefits include, but are
    not limited to, such items as health insurance, life insurance,
    pension plans, retiree health care, savings plans, education
    assistance and leave policies. Notwithstanding FAR 31.205-6(m),
    failure to comply with the terms of this clause may result in the
    disallowance of costs.

(i) RESERVED

(j) RESERVED.

(k) RESERVED.

(End of clause)

(a) 
(b) 
(c) 
(d) 

```{=html}
<!-- -->
```
(1) 
(2) 

```{=html}
<!-- -->
```
(e) 

```{=html}
<!-- -->
```
(1) 
(2) 
(3) 
(4) 
(5) 

```{=html}
<!-- -->
```
(f) 
(g) 
(h) 
(i) 
(j) 
(k) 

G.14 [RESERVED]{.underline}

G.15 [TECHNOLOGY TRANSFER]{.underline}

(a) The Contractor shall support, and participate in, the Government's
    Technology Transfer Program by assisting in the transfer of
    technology developed under government contracts to the private
    sector. The contractor's participation may include a number of
    different activities including the following:

```{=html}
<!-- -->
```
(1) Dual-use technology development of cutting edge technology having
    applications both within and outside the aerospace community.

(2) Collaborative efforts with third parties for the purpose of
    transferring technology.

(3) Government sponsored technology outreach and industry assistance
    programs that further the transfer of technology.

(4) Applications engineering work for the purpose of adapting the
    developed technology to a specific commercial use.

> All projects and associated agreements will be coordinated with the
> COTR and the Contracting Officer, or their appointed designees.
> Agreements will state funding requirements, project description, scope
> of project, reporting requirements, and responsible NASA and
> contractor personnel. Ownership of rights to the technology developed
> under these collaborative and partnership activities shall be
> addressed in the individual agreements.

(b) The Contractor shall establish a written plan to further the
    transfer of technology developed under Government contracts which is
    consistent with NASA's "Agenda for Change" dated June 1994. This
    policy shall include:

```{=html}
<!-- -->
```
(1) Education and training: The Contractors' commitment to educating and
    training its work force in technology transfer activities.

(2) Subcontractors: The Contractors' commitment to assist subcontractors
    with technology transfer activities.

(3) Commercialization: The Contractor's commitment to outreach
    activities aimed at marketing and commercializing technology being
    used under this contract.

```{=html}
<!-- -->
```
(c) The Contractor shall submit interim reports every 12 months from the
    effective date of this contract which explains their progress in
    meeting the objectives of their Technology Transfer Plan to the
    Technology Transfer and Commercialization Office (see 1852.227-72 in
    clause G.1).

(End of clause)

G.16 [MANAGEMENT OF POST DD 250 PROPERTY]{.underline}

The parties agree that the International Space Station (ISS) Contract
(Boeing NAS 15-10000) will retain accountability of ISS Government
Property to be delivered to the International Space Station. This
accountability will occur when assets have been transitioned from the
Design, Development, Test, and Evaluation phase to Integration &
Operations (I&O) of the NAS 15-10000 contract.

The parties agree that Integration Prime Contractors' must report any
loss, damage, or destruction of such ISS property in their possession,
or in the possession of their subcontractors, to the Boeing Property
Manager, as well as the delegated NASA or DOD Government Property
Administrator cognizant of the Integration Prime Contractors' when the
property is accountable to the NAS 15-10000 Contract. The parties agree
to cooperatively communicate any such incidents or related issues to the
Boeing Property Manager.

This clause does not add to or diminish the Integration Prime
Contractors' rights, responsibilities, or obligations with respect to
ISS property accountable to the ISS Contract (NAS 15-10000) in their
possession. In addition, this clause does not relieve the Integration
Prime Contractors' from any other property provisions set forth in their
respective contracts.

(End of clause)

G.17 [AWARD FEE FOR SERVICE CONTRACTS (1852.216-76) (JUN
2000)]{.underline}

(a) The contractor can earn award fee from a minimum of zero dollars to
    the maximum stated in NASA FAR Supplement clause 1852.216-85,
    \"Estimated Cost and Award Fee\" in this contract.

(b) Beginning 6 months after the effective date of this contract, the
    Government shall evaluate the Contractor\'s performance every 6
    months to determine the amount of award fee earned by the contractor
    during the period. The Contractor may submit a self-evaluation of
    performance for each evaluation period under consideration. These
    self-evaluations will be considered by the Government in its
    evaluation. The Government\'s Fee Determination Official (FDO) will
    determine the award fee amounts based on the Contractor\'s
    performance in accordance with the Award Fee Plan (Attachment J-8).
    The plan may be revised unilaterally by the Government prior to the
    beginning of any rating period to redirect emphasis.

(c) The Government will advise the Contractor in writing of the
    evaluation results. The payment office will make payment based on
    issuance of a unilateral modification by the contracting officer\].

(d) After 85 percent of the potential award fee has been paid, the
    Contracting Officer may direct the withholding of further payment of
    award fee until a reserve is set aside in an amount that the
    Contracting Officer considers necessary to protect the Government\'s
    interest. This reserve shall not exceed 15 percent of the total
    potential award fee.

(e) The amount of award fee which can be awarded in each evaluation
    period is limited to the amounts set forth at the table in
    Attachment J-8. Award fee which is not earned in an evaluation
    period cannot be reallocated to future evaluation periods.

(f) \(1\) Provisional award fee payments will, as applicable, be made
    under this contract pending the determination of the amount of fee
    earned for an evaluation period. If applicable, provisional award
    fee payments will be made to the Contractor on a monthly basis. The
    total amount of award fee available in an evaluation period that
    will be provisionally paid is the lesser of 80 or the prior
    period\'s evaluation score.

```{=html}
<!-- -->
```
(2) Provisional award fee payments will be superseded by the final award
    fee evaluation for that period. If provisional payments exceed the
    final evaluation score, the Contractor will either credit the next
    payment voucher for the amount of such overpayment or refund the
    difference to the Government, as directed by the Contracting
    Officer.

(3) If the Contracting Officer determines that the Contractor will not
    achieve a level of performance commensurate with the provisional
    rate, payment of provisional award fee will be discontinued or
    reduced in such amounts as the Contracting Officer deems
    appropriate. The Contracting Officer will notify the Contractor in
    writing if it is determined that such discontinuance or reduction is
    appropriate.

(4) Provisional award fee payments will be made prior to the first award
    fee determination by the Government.

```{=html}
<!-- -->
```
(g) Award fee determinations are unilateral decisions made solely at the
    discretion of the Government.

(End of clause)

G.18  [ADVANCE AGREEMENT ON IMPLEMENTATION OF THE SINGLE]{.underline}
[NON-CONFORMANCE SYSTEM (SNCS)]{.underline}

> (a)  [Agreement]{.underline}. The Government has elected to complete
> development of the integrated database known as the Single
> Non-Conformance System (SNCS) under the SPOC contract, and the
> development of this system and any remaining implementation costs will
> transition into any successor Space Shuttle operations contract. 

(b)  [Handling of Costs]{.underline}.

> (1)  The Government has determined that completion of this initiative
> is in the best interests of the Government.
>
> (2)  The Government and Contractor agree that cost for development of
> this effort will be billed as part of SPOC. USA will reflect the cost
> recovery on USA's Public Voucher continuation sheet, Form 1035.
> Further, these costs shall be charged to the contract based on savings
> generated for the implementation of this project per the following
> schedule:
>
> YEAR                               AMOUNT
>
> FY05                                   \$       0\
> FY06                                   \$ 0\
> FY07                                   \$ 405,200 \*\
> FY08                                   \$ 2,670,500 \*\
> FY09                                   \$ 3,060,800 \*\
> FY10                                   [\$    0]{.underline}
>
> **TOTAL                              \$** 6,136,500 \*
>
> **\*** These numbers are subject to change, once the total
> non-recurring development and implementation costs and the savings for
> the project are determined.
>
> \(3\) The direct cost for this project (January 2005 through
> completion) will be accounted for as a deferred charge/deferred
> billing and be fully burdened through G&A cost. Applicable indirect
> and service center cost will be applied to the labor and non-labor
> costs in the respective years as the cost are incurred. The cost will
> be liquidated and charged direct to the final cost objective(s) as
> scheduled above (b)(2). USA has established specific PIDs (WBS 1.3
> "Safety and Quality") for the recovery of the project cost by Program
> Element's final cost objective.
>
> \(4\) Though USA's Disclosure Statement (Part II 2.3.0) specifies that
> the timing of charging direct cost to Federal contracts is when the
> matching process is complete and the labor is performed, the parties
> agree that the specified method of this Advance Agreement better
> represents the direct contract cost as the anticipated savings of this
> project are recognized.
>
> \(5\) The Contractor agrees that all other costs to develop this
> integrated system shall not be reimbursed under any Government
> contract other than those identified in paragraph (a) above.

(End of clause)

(END OF SECTION)

SECTION H

SPECIAL CONTRACT REQUIREMENTS

H.1 [LISTING OF CLAUSES INCORPORATED BY REFERENCE]{.underline}

(f) The following clauses are incorporated by reference:

> 1852.208-81 Restrictions on Printing and Duplicating (Nov 2004)
>
> 1852.223-70 Safety and Health (Apr 2002)
>
> 1852.223-75 Major Breach of Safety or Security (Feb 2002)
>
> 1852.223-76 Federal Automotive Statistical Tool Reporting (Jul 2003)
>
> 1852.225-70 Export Licenses (Feb 2000); in paragraph (b) insert: *all
> NASA installations where work is performed*
>
> 1852.228-72 Cross-Waiver of Liability for Space Shuttle Services (Sept
> 1993)
>
> 1852.228-76 Cross-Waiver of Liability for Space Station Activities
> (Dec 1994)
>
> 1852.246-70 Mission Critical Space System Personnel Reliability
> Program (Mar 1997)
>
> 1852.247-71 Protection of the Florida Manatee (Mar 1989)

(g) The following clause is incorporated by reference and applies only
    to facilities-related effort in this contract:

> 1852.236-73 Hurricane Plan (Dec 1988)

H.2 [REPRESENTATIONS, CERTIFICATIONS, AND OTHER STATEMENTS OF OFFERORS
(JSC 52.209-90) (SEPT 1988)]{.underline}

This contract incorporates Section K, Representations, Certifications,
and Other Statements of Offerors, as set forth in the contractor\'s
proposal 06USA0109, dated June 30, 2006, by reference, with the same
force and effect as if it were given in full text.

(End of clause)

H.3 [SMALL BUSINESS SUBCONTRACTING GOALS]{.underline}

For the purposes of this clause, the terms: "HUBZone Small Business
Concern," "Small Disadvantaged Business Concern", "Service-Disabled,
Veteran-Owned Small Business Concern", "Veteran-Owned Small Business
Concern, "Woman-Owned Small Business Concern', and "Historically Black
College or University (HBCU)" are defined in paragraph 2.101 of the
Federal Acquisition Regulation.

Performance by the contractor in exerting its best effort to operate in
accordance with this plan shall be a factor in determining award fee
under this contract.

The total small business goal, expressed as a percent of total contract
value including options, is [18]{.underline} percent. The small business
percentage goal includes the following goals expressed as a percent of
total contract value:

> Small Disadvantaged Business Concern [6.0]{.underline} percent
>
> Woman-Owned Small Business Concern [3.5]{.underline} percent
>
> HUBZone Small Business Concern [0.5]{.underline} percent
>
> Service-Disabled Veteran-Owned Small\
> Business Concern [1.0]{.underline} percent
>
> Veteran-Owned Small Business Concern [1.0]{.underline} percent
>
> Historically Black Colleges or Universities/\
> Minority Institutions [1.0]{.underline} percent

(End of clause)

H.4 [USE OF JSC CALIBRATION LABORATORY]{.underline}

> The contractor shall utilize the services of the JSC Calibration
> Laboratory to the maximum extent practicable for calibration of all
> instruments (Government property or contractor property) utilized
> under this contract, the total cost for maintenance of which would
> otherwise be a direct charge to the Government. The procedures for
> obtaining calibration of instrument are described in JSC Procedures
> and Guidelines 5151.2 -- "JSC Support Contractor Procedures and
> Guidelines."

(End of clause)

H.5 RESERVED

H.6 [MOTOR VEHICLE MANAGEMENT]{.underline}

(a) The contractor shall acquire and manage motor vehicles necessary to
    support the performance of the contract. Such needed vehicles are to
    be acquired and managed in the manner most efficient and economic to
    the Government. Vehicles may be obtained from the GSA Interagency
    Motor Pool, commercial sources, or other sources. Costs related to
    motor vehicles shall be borne by the Contractor and reimbursed by
    the Government to the extent allowable in accordance with Part 31 of
    the FAR relating to the reimbursement of costs.

(b) The contractor will use the appropriate NASA form (Vehicle Use
    Record) to record vehicle utilization for all GSA and commercial
    rental vehicles. These records will be maintained and made available
    at the request of the Government for a period of 3 years. Two copies
    of the monthly billings, both GSA and commercial, for motor vehicle
    services will be forwarded to the Contracting Officer each month.
    The contractor shall assure that all vehicle operators are
    appropriately licensed in the state. The contractor will furnish GSA
    a copy of their third party automobile insurance policy if acquiring
    GSA motor vehicles.

(c) The contractor shall prepare and submit a Vehicle Utilization Plan
    semiannually. This plan shall, as a minimum, demonstrate the
    economic and efficient management of vehicles and fuel. It shall
    forecast the vehicle requirements for 2 years allowing at least 6
    months advance notice for additional requirements. It shall
    demonstrate the techniques utilized by the contractor to assure that
    vehicles are used for official purposes only.

(End of clause)

H.7 [INDEMNIFICATION]{.underline}

For purposes of FAR Clause 52.250-1, Alternate 1, (APR 84) the following
is the definition of unusually hazardous risks:

The unusually hazardous risks associated with this contract for which
indemnification is authorized are risks arising from or in connection
with:

\(1\) The burning, explosion, or detonation of Space Transportation
System (STS) flight elements or components, or ground support equipment.

\(2\) Uncontrolled or accidental releases or spills of hazardous
chemicals or gases.

\(3\) The landfall of STS, Shuttle Carrier Aircraft (SCA), or elements,
components or fragments thereof.

Any or all of the risks identified above may result in liability for
personal injury or death, loss of or damage to property, or loss of use
of property during the Flight Risk Period, SCA operations with the
orbiter attached, or ground operations at Kennedy Space Center (KSC) or
Cape Canaveral Air Force Station (CCAFS). The Flight Risk Period begins
upon commencement of movement of STS at rollout to the launch pad and
ends prior to launch upon completion of movement after STS rollback, or
after launch when the orbiter or the SCA with the orbiter attached
completes its landing at KSC, exclusive of marine operations.

These risks are considered unusually hazardous in the sense that the
potential occurrence of such risks during the Flight Risk Period, SCA
Operations with the orbiter attached, or ground operations at KSC or
CCAFS may result in a catastrophic accident with potential liability
that could be substantially in excess of the insurance coverage NASA
contractors could reasonably be expected to purchase and maintain,
considering the availability, cost, and terms and conditions of such
insurance.

(End of clause)

H.8 [PRIVACY OR SECURITY SAFEGUARDS]{.underline}

(a) The details of any safeguards the Contractor may design or develop
    under this contract are the property of the Government and shall not
    be published or disclosed in any manner without the Contracting
    Officer\'s express written consent.

(b) The details of any safeguards that may be disclosed to the
    Contractor by the Government in the course of performance under this
    contract shall not be published or disclosed in any manner without
    the Contracting Officer\'s express written consent.

(c) The Government shall be afforded full, free, and uninhibited access
    to all facilities, installations, technical capabilities,
    operations, documentation, records, and data bases for the purpose
    of carrying out a program of inspection to ensure continued efficacy
    and efficiency of safeguards against threats and hazards.

(d) If new or unanticipated threats or hazards are discovered by either
    the Government or the Contractor, or if existing safeguards have
    ceased to function, the discoverer shall immediately bring the
    situation to the attention of the other party. Mutual agreement
    shall then be reached on changes or corrections to existing
    safeguards or institution of new safeguards, with final
    determination of appropriateness being made by the Government. The
    Government\'s liability is limited to an equitable adjustment of
    cost for such changes or corrections, and the Government shall not
    be liable for claims of loss of business, damage to reputation, or
    damages of any other kind arising from, or related to, discovery of
    new or unanticipated threats or hazards, or any public or private
    disclosure thereof.

(End of clause)

H.9 [ASSOCIATE CONTRACTOR AGREEMENT FOR ISS OPERATIONS AND UTILIZATION
ACTIVITIES]{.underline}

(a) The success of the International Space Station (ISS) Program is
    dependent on the efforts of multiple contractors. The SPOC
    contractor is a key participant. The other contracts of the key
    participating contractors are:

> NNJ04AA01C Program Integration and Control Contract (PI&C)
>
> NNJ04AA03C Cargo Mission Contract
>
> NAS15-10000 USOS Acceptance and ISS Vehicle Sustaining Contract
>
> NNJ04AA02C Mission Integration Contract
>
> NAS10-02007 Checkout, Assembly, and Payload Processing Services
> (CAPPS)
>
> Under the aforementioned contracts and their successors, the
> contractors will provide the necessary technical, engineering and
> processing products and services required to develop, operate,
> maintain and utilize the International Space Station.

(b) In order to achieve efficient and effective implementation of the
    operation and utilization phase of the ISS, the contractor shall
    establish the means for coordination and exchange of information
    with associate contractors. The information to be exchanged shall be
    that required by the contractors in the execution of their
    respective contract requirements. The contractors are strongly
    encouraged to seek out and foster cooperative efforts that will
    benefit the ISS Program with increased safety, efficiency, and
    productivity.

(c) Given the unique role of this contract in developing, operating,
    maintaining and utilizing the ISS, the contractor will engage in
    cooperative relationships that facilitate effective management of
    the overall ISS effort. This joint cooperation will be evaluated as
    part of the contract award fee process, as defined in the Award Fee
    Plan for the contract. Successful performance will be determined by
    the Government's assessment of the overall and combined performance
    of the operation and utilization requirements in the contracts, as
    modified.

(d) To ensure successful implementation and utilization of the ISS, the
    contractors shall establish formal guidelines to address
    coordination, cooperation and communication. All program elements
    shall work in a coordinated fashion. Each contractor shall establish
    the means for the exchange of such data as needed to keep other
    project elements fully informed.

(End of clause)

H.10 [CUSTODY AND DISPOSITION OF COMPUTER SOFTWARE]{.underline}

(a) The computer software packages acquired, developed or used during
    the performance of this contract may remain in the custody of the
    Contractor until the Contracting Officer calls for the transfer or
    delivery thereof, or until transfer or delivery is made pursuant to
    any requirements specified elsewhere in this contract, whichever is
    earlier. Whenever such software packages are commercially available,
    the contractor shall either grant or obtain from the appropriate
    third party vendors sufficient rights to transfer or deliver,
    without additional fee or approval, the software packages and their
    licenses to the Government or any authorized follow-on Government
    contractor.

(b) To comply with subparagraph (h) of the *Rights-In-Data\--General*
    clause (FAR 52.227-14), the contractor shall include the *Commercial
    Computer Software\--Licensing* clause (1852.227-86) in all
    subcontracts and purchase orders when acquiring commercially
    available software in accordance with paragraph (a) above. If a
    subcontractor or other vendor refuses to accept this *Commercial
    Computer Software\--Licensing* clause, the Contractor shall promptly
    notify the Contracting Officer and not proceed with the contract
    award without further authorization.

(End of clause)

H.11 [INFORMATION TECHNOLOGY PURCHASES]{.underline}

(a) Information Technology purchases may be made only after the
    applicable NASA Center Chief Information Officer review and approval
    of the proposed purchases. "Information Technology" applies to all
    resources as defined in the Information Technology Management Reform
    Act (ITMRA).

(b) To satisfy the review and approval requirement, the Contractor shall
    prepare, submit and present Information Technology Plans in
    accordance with SOW 1.1.4.1, Information Management, and DRD
    1.1.4.1-b, Information Technology Plan and DRD 1.1.4.1-g, Enterprise
    Architecture Reviews.

(End of clause)

H.12 [PROTECTION OF GOVERNMENT FIP ASSETS]{.underline}

(a) For the purpose of this clause, "Federal Information Processing
    (FIP) assets" mean computer software such as programs, data files,
    data bases, and other automatic data processing (ADP) material in
    whatever form such as magnetic tapes, disks, cassettes, card decks,
    printed listing, or other recorded media.

(b) The Contractor shall establish procedures to protect Government FIP
    assets whether furnished by the Government or first produced by the
    Contractor under the work of the contract, from misuse, destruction,
    loss, sale, publication or release to others, except as otherwise
    provided by the *Rights in Data* clause included in the general
    provisions of this contract. Such procedures will provide for the
    accountability of FIP assets by the Contractor and the return to the
    Government of any FIP assets in the possession of employees upon
    termination or transfer of such employees.

(c) On completion of the contract work, Government FIP assets will be
    delivered as authorized by the Contracting Officer.

(d) The Contractor shall flow this clause substantially as written to
    any subcontract which will receive or first produce significant
    Government FIP assets (i.e., valued at \$100,000 or more).

(End of clause)

H.13 [RESERVED]{.underline}

H.14 [EXPORT OF TECHNICAL DATA, DEFENSE SERVICES, COMPUTER SOFTWARE, OR
HARDWARE]{.underline}

(a) During the conduct of this contract, NASA may have a need to
    deliver, disclose, or transfer to a foreign entity or person
    ("export") technical data, computer software, or hardware developed,
    used or required to be delivered by the Contractor in the
    performance of this contract. When such a need arises NASA may
    exercise the applicable exemptions, general licenses, existing NASA
    export licenses, available exceptions or other approvals available
    to a Federal agency under the US export control laws, and may effect
    the export of such technical data, computer software, or hardware
    for NASA by direction to the Contractor.

(b) When directed in writing by the Contracting Officer or his/her
    designated representative, the Contractor, for purposes of export
    control, shall export on behalf of NASA specifically identified
    technical data, computer software, or hardware to a named foreign
    entity or person, in the manner and under the conditions provided
    for in the direction.

(c) The contractor will ensure that in the absence of NASA exemptions or
    exceptions, that appropriate licenses and Technical Assistance
    Agreements (TAAs) are in place to support exports.

(d) Any export made in accordance with this clause shall be limited to
    only that technical data, computer software, and hardware which NASA
    specifically identifies and authorizes the Contractor to export, in
    the manner and under the conditions provided in the authorization.
    All other exports of technical data, defense services, computer
    software and hardware by the Contractor, whether related to the
    performance of this contract or otherwise, are subject to the
    applicable requirements of the US export control laws and
    regulations.

(e) Nothing contained in this clause shall affect the protection or
    allocation of rights to technical data or computer software between
    NASA and the Contractor or any subcontractors as provided for in
    this contract or subcontract hereunder, nor shall this clause imply
    any license or affect the scope of any license otherwise granted to
    the Government or the recipient of the transferred or disclosed
    technical data or computer software.

(f) The Contractor shall include this clause in all subcontracts at any
    tier (suitably modified to reflect the relationship of the parties),
    the performance of which may require the development, delivery, or
    use of technical data, defense services, computer software, or
    hardware, and the Contractor may direct an export on behalf of NASA,
    subject to the limitations of paragraphs (c) and (d) above, by
    subcontractors. Alternately, any such direction may be given by the
    Contracting Officer or his/her designated representative directly to
    a subcontractor at any tier (with notice by NASA to the Contractor.)

(End of clause)

H.15 RESERVED

H.16 RESERVED

H.17 [RESERVED]{.underline}

H.18 [CONTINUOUS IMPROVEMENT/PARTNERING]{.underline}

(a) The Contractor shall implement and maintain vigorous continuous
    improvement (CI) activities for the full duration of this contract
    with the overarching goals of improving productivity, achieving cost
    savings, and achieving other economies and efficiencies across the
    full spectrum of its performance of this contract and the
    performance of its subcontractors each of whose subcontracts exceed
    a total of \$50 million over the base period of this contract. The
    Contractor's plan is incorporated herein as Attachment J-16.

(b) As part of its CI activities, the Contractor shall maintain data
    regarding its achievement of each of the Performance Requirements
    specified in Attachment J-1-B to this contract and its performance
    in relationship to those Performance Requirements. Although the
    Contractor may use any system and format to maintain this data, the
    data must be easily and continuously accessible to the Government
    pursuant to the Access to Contractor Data clause (H.19) and be
    complete enough to be meaningful.

(c) The parties recognize that the Government may need to change
    policies or requirements in this contract in order to enable the
    Contractor to achieve specific efficiencies under this contract. The
    Contractor, therefore, is encouraged to request these changes when
    they may result in additional improvements or cost savings. The
    Government will, in good faith, consider accepting these changes. In
    the event that the Government cannot accept a suggestion, it will
    provide rationale to the Contractor as to why the suggestion was
    unacceptable. When possible, the Government shall propose
    modifications to a suggestion in order to make it acceptable. The
    Government's rejection of a suggestion submitted pursuant to this
    clause shall not provide the basis for any equitable adjustment in
    accordance with the Changes clause, or an adjustment of fee that
    might otherwise have been earned.

(d) This clause is not an advance agreement on the part of NASA to
    accept any changes made pursuant to this clause. Moreover, the
    Contractor shall not request any changes that degrade either the
    safety of the program or the ability to meet the flight manifest.
    Additionally, the Government cannot accept any change which modifies
    or otherwise is contrary to a statute, an Executive Order, or a
    regulation issued by another Government agency.

(e) The Changes clause shall not apply to any suggestion accepted
    pursuant to this clause. Instead, this clause shall be cited as
    authority for any changes that are required to accept the
    Contractor's suggestion. Additionally, for a period of three years
    after implementation of a specific cost savings idea, an equitable
    adjustment shall not be required for changes resulting from this
    clause.

(f) The Contractor understands and agrees that, this clause
    notwithstanding, it is responsible for performance of all contract
    requirements.

(End of clause)

H.19 [ACCESS TO CONTRACTOR DATA]{.underline}

(i) "Data" for purposes of this clause, means recorded information,
    regardless of the form or media on which it may be recorded. The
    term includes technical data; computer software; and information
    incidental to contract administration, such as financial,
    administrative, cost or pricing, or management information. Types of
    data contained in the definition also include contractor internal
    audits of any discipline, system, or task which directly or
    indirectly supports Shuttle, payload, and ISS ground support,
    launch, flight, or landing operations as well as data from any audit
    of subcontractor(s) performing this contract. These examples are
    illustrative and are not to be construed as a limitation on the
    definition of data.

(ii) The Contracting Officer or designee shall, through closeout, have
     access to and the right to examine any of the data produced or used
     in the performance of this contract. The purpose of this access
     provision is to permit the Government to monitor the Contractor's
     performance under this contract and to permit sampling of
     contractor data to verify requirements compliance and continuous
     improvement without unduly increasing the number of data
     deliverables to this contract.

(iii) The Contractor shall make available at all reasonable times for
      Government inspection all existing Government data provided to the
      Contractor and any data first produced or used in the performance
      of this contract for examination through closeout. Moreover,
      information provided by the Contractor on any contractor system
      where NASA data resides shall contain all necessary technical and
      business application data to determine the degree to which
      contract requirements are met. At a minimum, the Contractor shall
      maintain the types of data required by DRD 1.1.4.1-c.

(iv) Except for software systems being provided as part of this
     contract, and existing Subcontractor systems, the Contractor shall
     maintain all data on a commercially available system for
     information management that is easily accessible by NASA. For the
     purposes of this clause, "commercially available system" is defined
     as a system comprised of a Commercial Off-the-Shelf (COTS) database
     management system with its associated reporting/query tools, and a
     COTS text and graphics viewer software package. The Contractor
     shall include its information Technology plans, reviews, and
     recommendations in the Information Technology (I/T) Plan and
     Reports, (DRD 1.1.4.1-b) and Enterprise Architecture Reviews (DRD
     1.1.4.1-g). The Contractor must obtain the approval of the
     Contracting Officer prior to using any new noncommercial system, or
     any major upgrading of any existing non-commercial systems for
     information management of data generated under this contract. As
     part of this request, the Contractor must justify why no commercial
     system to manage information is adequate for this contract. For
     existing contactor systems, or if use of a noncommercial system is
     approved, then, upon request, the Contractor shall demonstrate the
     system to the Government and provide thorough training to
     Government personnel to ensure they are able to access (i.e., read
     and copy) all data maintained on the system.

(v) The Contractor shall provide the Government unimpeded access to all
    physical and virtual Information Technology areas determined by
    Government representatives as necessary for surveillance, audit and
    independent evaluation purposes. In those instances that access is
    restricted due to hazards or other personnel access limitations, the
    Contractor shall accommodate Government personnel such that access
    is provided and operational safety is not compromised.

(vi) Notwithstanding the Additional Data Requirements clause, the
     Government shall have the right to reproduce any data found during
     the examination. The Government shall retain no greater rights in
     the reproduced data than it would have under the Rights in
     Data\--General clause.

(vii) The Contractor shall describe the areas of its internal systems
      where NASA access will be permitted, define access and interface
      requirements, and provide NASA the required training to be able to
      access and use these systems.

(viii) The Contractor shall flow this clause to all cost type
       subcontracts.

(End of clause)

H.20 [SPECIAL PROVISION FOR CONTRACT CHANGES]{.underline}

(a) Notwithstanding the provisions of the *Changes* clause and the
    *Government Property* clause, 52.245-5, the parties agree that no
    change made pursuant to the *Changes* clause shall give rise to an
    equitable adjustment in the estimated cost or fee, delivery
    schedule, or any other contract provision, when said change causes
    an increase or decrease in estimated cost of \$1 million or less in
    this contract. Each change shall be controlling in making this
    determination, and such change shall not, for purposes of
    determining the applicability of this clause, be added to any other
    change(s). The parties recognize that several changes may be grouped
    together in a bilateral contract modification for definitization;
    however, the dollar value of each individual change will be
    controlling in determining whether or not an equitable adjustment is
    in order.

(b) Facility Projects:

```{=html}
<!-- -->
```
(1) The Government intends to issue Change Orders (CO's) for facility
    projects over \$500,000. To the extent that CO's are issued for
    facility project work exceeding \$500,000, the facility cost and fee
    in Clause B.2 will be increased.

(2) All facility projects under \$500,000 which: (i) are submitted in
    the Contractor's 5-year plan which identifies facility projects
    required, in accordance with DRD 1.1.6.1-a or (ii) meet the
    definition of unforeseen programmatic projects as defined by NPG
    8820.2E, "Facility Project Implementation Guide" shall not be
    subject to the *"Changes"* clause. All costs associated with these
    projects are included in the baseline; therefore, no equitable
    adjustment shall be required.

(End of clause)

(a) 
(b) 

```{=html}
<!-- -->
```
(1) 
(2) 

H.21 [COMPLIANCE WITH APPLICABLE CENTER POLICIES AND
PROCEDURES]{.underline}

(a) Contractor and subcontractor personnel (regardless of tier) working
    on-site at NASA centers (or off-site as policies and procedures
    dictate) are required to comply with applicable agency and center
    policies and procedures. These are listed, by Center, at Attachment
    J-11. Unless specifically noted with version or date, the contractor
    and pertinent subcontractors shall comply with the latest revisions
    to these policies and procedures. Otherwise, requirements to comply
    with additions and deletions to this listing and/or latest document
    revisions will be made by contract modification. The Contractor
    shall promptly take corrective action upon receipt of notice from
    the Contracting Officer or representative of noncompliance with any
    applicable center policy or procedure.

(b) Additional contract clauses with applicability specific to each
    center are contained in Attachment J-18. The Contractor shall comply
    with these clauses when performing effort at the respective NASA
    center.

(End of clause)

H.22 [SAFETY AND HEALTH PLAN]{.underline}

(a) The Contractor shall implement and comply with the Safety and Health
    Plan specified in DRD 1.3.

(b) The Contractor shall provide for safety inspection and acceptance of
    work imposed by the SOW. Safety inspection and corrective action
    reports shall be made available to the Contracting Officer upon
    request.

(c) The Contractor shall immediately report to the cognizant center
    Director of Safety and Mission Assurance and the cognizant
    Contracting Officer (by telephone if possible) accidents and
    incidents which result in serious personal injuries or death; and
    incidents which result in substantial damage to resources, equipment
    or facilities used or occupied by the Contractor. Prepare and submit
    a NASA Mishap Report per local center requirements.

(End of clause)

H.23 [RESERVED]{.underline}

H.24 [RESERVED]{.underline}

H.25 [GOVERNMENT INSIGHT]{.underline}

(a) Definitions. For the purpose of this contract, the following
    definitions apply:

> "Insight," as used in this clause, means technical visibility into the
> Program, maintained through such means as audits, surveillance,
> assessment of trends and metrics, software independent verification
> and validation, the flight readiness review process, and review or
> independent assessment of any anomalies occurring in any phase of the
> program that are not within verified, validated, and certified design,
> operations, and processing requirements.
>
> "Surveillance," as used in this clause means continual monitoring and
> verification of the status of manufacturing, testing, and processing
> of Shuttle hardware, software and operations preparations to ensure
> that requirements are being fulfilled. Items to be monitored and
> verified are selected---this is not an all inclusive activity.
>
> "Audit," as used in this clause, means the implementation of
> procedures and requirements of the NASA Engineering Quality Audit
> (NEQA) or other equivalent audit techniques used to perform periodic
> audit of all aspects of processes and procedures required to
> manufacture, assemble, test, and process hardware for flight. Audits
> may include an examination of all disciplines and tasks which are
> involved with or support Shuttle launch and landing operations,
> hardware and software production and maintenance, safety and quality
> assurance, logistics, procurements and operations. These descriptions
> are illustrative only and shall not be construed as any limitation on
> the Government's right to conduct an audit of the Contractor and
> subcontractors to determine performance on this contract.

(b) The Government shall have the right to audit the Contractor and
    cost-reimbursement subcontractors (with values exceeding \$1
    million) to determine compliance with the requirements of this
    contract. One purpose of these audits is to afford the Government
    insight into and understanding of Contractor and selected
    subcontractor processes and procedures to determine whether the
    processes or procedures (1) adversely affect safety; (2) are not
    within control limits; or (3) adversely affect future launch
    schedules.

(c) The Government may schedule fact-finding meetings with the
    Contractor and subcontractors as necessary to discuss issues
    requiring Government insight. Scheduling and format of these
    meetings shall indicate whether exchange of information will be
    required, and the number and expertise of Contractor/subcontractor
    personnel who shall attend the meetings. When requested by the
    Contracting Officer or designee, the Contractor and subcontractors
    shall provide necessary support to the Government when it audits the
    Contractor or subcontractor and for the
    Government-Contractor/subcontractor meetings. The purpose of these
    meetings is to understand the findings of the Government audits. The
    parties understand and agree that no direction from the Government
    or constructive change to the contract shall result from any of
    these meetings.

(End of clause)

H.26 [RESERVED]{.underline}

H.27 [ENGINEERING CHANGE PROPOSALS]{.underline}

(a) Definitions.

> \"ECP\" means an Engineering Change Proposal (ECP) which is a proposed
> engineering change and the documentation by which the change is
> described, justified, and submitted to the Contracting Officer for
> approval or disapproval.
>
> \"NSTS 07700\" means the NASA publication entitled, Space Shuttle
> Flight and Ground Specifications.

(b) Either party to the contract may originate ECPs. The originator
    shall forward proposed ECPs to the Contracting Officer. Unless
    otherwise required by the Contracting Officer, the ECP formats,
    forms and controls specified in NSTS 07700, Volume IV, Book 1 shall
    be used for Shuttle operations and in ISS 41170 for Space Station
    operations. Implementation of an approved ECP may occur by either a
    supplemental agreement or, if appropriate, as a written change order
    to the contract.

(c) Any ECP submitted to the Contracting Officer over \$100,000, shall
    include a \"not-to-exceed\" estimated cost increase or decrease
    adjustment amount, if any, and the required time of delivery
    adjustment, if any, acceptable to the originator of the ECP. If the
    change is originated within the Government, the Contracting Officer
    shall obtain a written agreement with the contractor regarding the
    \"not-to-exceed\" estimated cost and delivery adjustments, if any,
    prior to issuing an order for implementation of the change. An ECP
    accepted in accordance with the *Changes* clause of this contract
    shall not be considered an authorization to the Contractor to exceed
    the estimated cost in the contract Schedule, unless the estimated
    cost is increased by the change order or other contract
    modification.

(d) After submission of a contractor initiated ECP, the Contracting
    Officer may require the contractor to submit the following
    information:

```{=html}
<!-- -->
```
(1) Cost or pricing data in accordance with FAR 15.403-5 if the proposed
    change meets the criteria for its submission under FAR 15.403-4; or

(2) Information other than cost or pricing data adequate for contracting
    officer determination of price reasonableness or cost realism. The
    contracting officer reserves the right to request additional
    information if that provided by the contractor is considered
    inadequate for that purpose. If the contractor claims applicability
    of one of the exceptions to submission of cost or pricing data, it
    shall cite the exception and provide rationale for its
    applicability.

```{=html}
<!-- -->
```
(e) If the ECP is initiated by NASA, the contracting officer shall
    specify the cost information requirements, if any.

(End of clause)

H.28 [SPACE FLIGHT AWARENESS PROGRAM]{.underline}

The Contractor shall maintain a product and performance-oriented
motivation (awareness) program in accordance with NASA Procedural
Requirements NPR 8715.3 and NPR 3451.1. The Program objective shall be
the prevention of human error by instilling in individuals performing on
the contract and on critical subcontracts an awareness of individual
responsibility for ISS, Shuttle, and any other ancillary
mission/payloads related to human space flight. As a minimum, goals
should be to assure mission success, flight crew safety, and recognition
of exemplary performance necessary to achieve success. The program shall
include as a minimum:

(a) Participation in NASA-Industry Space Flight Awareness Program.

(b) Reserved.

(c) Reserved.

(d) Methods to obtain and distribute motivational information and
    materials to concerned Contractor personnel, subcontractors, and
    vendors supplying critical flight and ground support hardware and
    software.

(e) Motivational (awareness) orientation for Contractor supervisory
    personnel and orientation of the work force in workmanship needs.

(f) Recognition of personnel who demonstrate their awareness through
    exceptional craftsmanship, error free workmanship, and attention to
    careful performance in their job responsibility. The Contractor
    shall flow down the provisions of this clause to all critical
    subcontractors.

(End of clause)

H.29 [RESERVED]{.underline}

H.30 [RESERVED]{.underline}

H.31 [REQUIREMENT FOR COST TRACKING]{.underline}

Costs for the Space Shuttle and ISS shall be tracked and reported
separately in order to comply with requirements that accurate and timely
reporting of ISS costs to the Congress can be accomplished by NASA.
These costs, to be reported in accordance with the requirements of
1852.242-73, *NASA Contractor Financial Management Reporting*, and
1852.242-74, *NASA Contractor Financial Management Reporting
(Performance Analysis Report)*, must be in suitable format and adequate
detail to fulfill obligations placed on NASA.

(End of clause)

H.32 [PROCUREMENT DATA PACKAGE]{.underline}

(a) In addition to the requirement to maintain certain data in the
    *Access to Contractor Data* clause (H.19), the Contractor shall
    maintain this data in its data management system in a form and
    format such that it is suitable for inclusion in a procurement data
    package. The procurement data package shall be in accordance with
    requirements of Data Requirements Document (DRD 1.1.4.1-d). The
    parties recognize that this contract does not require the delivery
    of the data necessary for a procurement package. Instead, the
    Government would order this package in accordance with FAR
    52.227-16, *Additional Data Requirements*. The Contractor shall be
    required to deliver this data to the Government within six months of
    it being ordered per FAR 52.227-16.

(b) Reserved

(c) The only costs the Government shall bear for the delivery of data
    necessary for a procurement package shall be those costs associated
    with reproduction and delivery. No costs shall be permitted for
    converting data to a prescribed format since the Contractor is
    required to maintain the data in a format suitable for a procurement
    package. The costs associated solely with the conversion of
    electronic data to a paper format, however, shall be deemed to be a
    reproduction cost.

(End of clause)

H.33 [LAUNCH SCHEDULE VARIATIONS]{.underline}

(a) The parties agree that the contract shall be equitably adjusted in
    accordance with the procedural provisions of the *Changes* clause if
    the number of flights during the term of the contract is more or
    less than the number anticipated for the contract. The anticipated
    number of flights is as follows:

  -------------- -------------- -------------- -------------- ------------
  Year 1         Year 2         Year 3         Year 4         Total

  4              5              5              3              17
  -------------- -------------- -------------- -------------- ------------

(b) It is expected that the actual number of flights in any given year
    may vary from the anticipated flights per year noted above, due to
    the spacing of the manifest. Variations of this type that cause the
    flight rate in any year to be 1 flight above or below the
    anticipated rate is considered normal and will not be subject to the
    *Changes* clause. This type of variation may also cause the
    anticipated number of flights for the entire contract period to vary
    by plus or minus 1 flight. This variation will not be subject to the
    *Changes* clause.

(c) The parties agree that the total number of flights for the contract
    will be adjusted (either upward or downward) to reflect changes in
    the actual number of flights only for those years in which an
    equitable adjustment is otherwise made. By way of example, and not
    limitation, in the event there are 5 flights in Year 1 (not subject
    to an equitable adjustment) and 3 flights in Year 2 (subject to an
    equitable adjustment), the total number of flights for purposes of
    final contract total would be reduced by 2. At the end of the
    contract period, a variance greater than plus or minus 1 flight will
    be subject to the *Changes* clause.

(End of clause)

H.34 [SELECTION OF FIRMS FOR ARCHITECT-ENGINEER (A-E)
SERVICES]{.underline}

When subcontracting for A-E services, the Contractor shall use
procedures generally consistent with FAR Subpart 36.6. A-E firms shall
be selected competitively based on qualifications, specialized
experience, and other critical considerations, instead of price alone.
The Contractor shall specifically comply with the requirements of FAR
36.602-1.

(End of clause)

H.35 [PROVISIONING PROCEDURES]{.underline}

(a) There are areas within the contract, Program, Transition, and
    Constellation Bridge Support related, where it is not possible to
    reasonably predict future requirements. These areas are subject to
    the Provisioning procedures set forth in Attachment J-19. Tasks
    subject to Program Provisioning requirements will be provisioned on
    an annual basis. Requirements subject to Program Provisioning
    include SOW paragraphs: 1.4.1.2, Orbiter Logistics \[High Value
    Spares (replacement parts with a unit cost of \$1M+)\], 1.4.1.5,
    Orbiter Hardware Production and Support Tasks; 1.4.9, Flight Crew
    Equipment; 1.6.5.4 Flight Operations Development; 1.7.1, Special
    Studies and Development Projects; 1.7.1.1, KSC Shuttle Development
    Activities; 1.7.1.2, KSC Construction of Facility Activities; 1.7.4,
    Program Reimbursables; and 1.7.5, Solid Rocket Booster Development
    Activities.

> Tasks subject to Transition Provisioning requirements will be
> provisioned on an annual basis. Requirements subject to Transition
> Provisioning are noted in SOW paragraph 1.9, Program Transition.
>
> Tasks subject to Constellation Provisioning requirements will be
> provisioned on an annual basis. Requirements subject to Constellation
> Provisioning are noted in SOW paragraph 1.10, Constellation Bridge
> Support.

(b) To provide for efficient and effective administration, the parties
    have structured a Provisioning Management Plan (PMP) (Attachment
    J-19). This plan provides additional background and defines
    administration requirements, specific tasks, schedules, and cost
    estimates.

(c) Procedures for updating task content within the PPMP are described
    below:

```{=html}
<!-- -->
```
(1) [First Year's Tasks]{.underline}: The estimated cost and fee for the
    tasks authorized to be performed in Provisioning are included in
    Clause B.2. The specific tasks to be performed are defined in the
    Program, Transition, and Constellation Provisioning Task Lists.

(2) [Subsequent Annual PPTL, TPTL, & CPTL]{.underline}: Each subsequent
    contract year, the Contractor and NASA shall partner the annual
    PPTL, TPTL, and CPTL attachment, by each individual program element,
    the contents of which are to be based on requirements identified by
    the Government. Each PPTL, TPTL, and CPTL shall only include tasks
    which are expected to be initiated in the forthcoming Government
    Fiscal Year (GFY), and will not include any amounts for the
    continuation or completion of tasks initiated in prior years.
    However, if a task is expected to be completed in a year subsequent
    to the one for which the proposal is being submitted, the time
    phased cost for each year in which work is to be performed on the
    task shall be included. The cost and fee for the instant year, as
    well as the "out-year" work will be included in the appropriate
    program element in the attachment and Clause B.2. Subsequent year
    PPTL's, TPTL's, and CPTL's shall not include this work for pricing
    purposes since it will have already been included in the contract
    baseline. The Contractor and NASA will negotiate and definitize said
    task lists, and adjust the cost and fee for Provisioning in Clause
    B.2, before September 30th of the forthcoming GFY.

(3) Should the Government add, delete or modify a task during the fiscal
    year which does not exceed the threshold(s) established in
    Attachment J-19, Technical Direction will be provided by the
    cognizant TMR. However, should such change exceed the threshold(s),
    the Contracting Officer will issue written direction in the form of
    a Provisioning Change Order (PCO) to the Contractor. A PCO is issued
    unilaterally by the Contracting Officer and will be used as the
    contractual document to update the PMP or task lists, by program
    elements.

(4) Recommendations for tasks not included in the task lists may be
    identified by both the Government and Contractor. At a minimum,
    recommendations shall be supported by information concerning: flight
    effectivity, or last need date; SOW or specification impacts; and
    time-phased cost estimates. Contractor-initiated recommendations
    shall be submitted to the cognizant TMR for consideration.
    Submission of a recommendation by the Contractor does not commit
    NASA to implementation.

(End of clause)

H.36 [RESERVED]{.underline}

H.37 [RESERVED]{.underline}

H.38 [RESERVED]{.underline}

H.39 [ACTIVITY BASED COSTING]{.underline}

(a) From time to time, the Contracting Officer may initiate the process
    leading to a price adjustment for a contract modification by
    utilizing Activity Based Costing (ABC). ABC may be used when both
    the work requirements and resources (Direct Labor, Subcontracts,
    ODC's, etc.) necessary for accomplishing the work can be predicted
    with a high degree of accuracy. For purposes of this special
    provision, ABC is a technique in which requirements definition and
    cost estimating baselines for a task to be proposed, are jointly
    developed and documented by representatives of the Government and
    Contractor prior to submittal of the Contractor\'s cost proposal.
    The Decision Package is the output of this process and, when
    approved by the Government, becomes the Basis of Estimate (BOE) to
    be proposed by the Contractor. Determination of the price for a
    contract modification requires the application of labor rates,
    indirect costs, and fee to the agreed upon BOE.

(b) Notwithstanding any other provision in this contract to the
    contrary, the parties agree that when the ABC technique is utilized
    as set forth in paragraph (a) of this provision, the Decision
    Package is \"Information other than cost or pricing data,\" as
    defined by FAR 15.403, and is not required to be certified. The
    applied labor rates, indirect costs and any other costs utilized to
    complete the Contractor\'s cost proposal are "cost or pricing data",
    as defined in 15.403. Such cost or pricing data is certifiable in
    accordance with 15.406-2.

(End of clause)

H.40 [VALUE ENGINEERING (52.248-1) (FEB 2000)]{.underline}

(a) General. The Contractor is encouraged to develop, prepare, and
    submit value engineering change proposals (VECP's) voluntarily. The
    Contractor shall share in any net acquisition savings realized from
    accepted VECP's, in accordance with the incentive sharing rates in
    paragraph (f) of this clause.

(b) Definitions.

> "Acquisition savings," as used in this clause, means savings resulting
> from the application of a VECP to contracts awarded by the same
> contracting office or its successor for essentially the same unit.
> Acquisition savings include---

(1) Instant contract savings, which are the net cost reductions on this,
    the instant contract, and which are equal to the instant unit cost
    reduction multiplied by the number of instant contract units
    affected by the VECP, less the Contractor's allowable development
    and implementation costs;

(2) Concurrent contract savings, which are net reductions in the prices
    of other contracts that are definitized and ongoing at the time the
    VECP is accepted; and

(3) Future contract savings, which are the product of the future unit
    cost reduction multiplied by the number of future contract units in
    the sharing base. On an instant contract, future contract savings
    include savings on increases in quantities after VECP acceptance
    that are due to contract modifications, exercise of options,
    additional orders, and funding of subsequent year requirements on a
    multiyear contract.

> "Collateral savings," as used in this clause, means those measurable
> net reductions resulting from a VECP in the agency's overall projected
> collateral costs, exclusive of acquisition savings, whether or not the
> acquisition cost changes.
>
> "Contracting office" includes any contracting office that the
> acquisition is transferred to, such as another branch of the agency or
> another agency's office that is performing a joint acquisition action.
>
> "Contractor's development and implementation costs," as used in this
> clause, means those costs the Contractor incurs on a VECP specifically
> in developing, testing, preparing, and submitting the VECP, as well as
> those costs the Contractor incurs to make the contractual changes
> required by Government acceptance of a VECP.
>
> "Future unit cost reduction," as used in this clause, means the
> instant unit cost reduction adjusted as the Contracting Officer
> considers necessary for projected learning or changes in quantity
> during the sharing period. It is calculated at the time the VECP is
> accepted and applies either---

(1) Throughout the sharing period, unless the Contracting Officer
    decides that recalculation is necessary because conditions are
    significantly different from those previously anticipated; or

(2) To the calculation of a lump-sum payment, which cannot later be
    revised.

> "Government costs," as used in this clause, means those agency costs
> that result directly from developing and implementing the VECP, such
> as any net increases in the cost of testing, operations, maintenance,
> and logistics support. The term does not include the normal
> administrative costs of processing the VECP or any increase in this
> contract's cost or price resulting from negative instant contract
> savings.
>
> "Instant contract," as used in this clause, means this contract, under
> which the VECP is submitted. It does not include increases in
> quantities after acceptance of the VECP that are due to contract
> modifications, exercise of options, or additional orders. If this is a
> multiyear contract, the term does not include quantities funded after
> VECP acceptance. If this contract is a fixed-price contract with
> prospective price redetermination, the term refers to the period for
> which firm prices have been established.
>
> "Instant unit cost reduction" means the amount of the decrease in unit
> cost of performance (without deducting any Contractor's development or
> implementation costs) resulting from using the VECP on this, the
> instant contract. If this is a service contract, the instant unit cost
> reduction is normally equal to the number of hours per line-item task
> saved by using the VECP on this contract, multiplied by the
> appropriate contract labor rate.
>
> "Negative instant contract savings" means the increase in the cost or
> price of this contract when the acceptance of a VECP results in an
> excess of the Contractor's allowable development and implementation
> costs over the product of the instant unit cost reduction multiplied
> by the number of instant contract units affected.
>
> "Net acquisition savings" means total acquisition savings, including
> instant, concurrent, and future contract savings, less Government
> costs.
>
> "Sharing base," as used in this clause, means the number of affected
> end items on contracts of the contracting office accepting the VECP.
>
> "Sharing period," as used in this clause, means the period beginning
> with acceptance of the first unit incorporating the VECP and ending at
> a calendar date or event determined by the contracting officer for
> each VECP.
>
> "Unit," as used in this clause, means the item or task to which the
> Contracting Officer and the Contractor agree the VECP applies.
>
> "Value engineering change proposal (VECP)" means a proposal that---

(1) Requires a change to this, the instant contract, to implement; and

(2) Results in reducing the overall projected cost to the agency without
    impairing essential functions or characteristics; provided, that it
    does not involve a change---

```{=html}
<!-- -->
```
(i) In deliverable end item quantities only;

(ii) In research and development (R&D) end items or R&D test quantities
     that is due solely to results of previous testing under this
     contract; or

(iii) To the contract type only.

```{=html}
<!-- -->
```
(c) VECP preparation. As a minimum, the Contractor shall include in each
    VECP the information described in paragraphs (c)(1) through (8) of
    this clause. If the proposed change is affected by contractually
    required configuration management or similar procedures, the
    instructions in those procedures relating to format, identification,
    and priority assignment shall govern VECP preparation. The VECP
    shall include the following:

```{=html}
<!-- -->
```
(1) A description of the difference between the existing contract
    requirement and the proposed requirement, the comparative advantages
    and disadvantages of each, a justification when an item's function
    or characteristics are being altered, the effect of the change on
    the end item's performance, and any pertinent objective test data.

(2) A list and analysis of the contract requirements that must be
    changed if the VECP is accepted, including any suggested
    specification revisions.

(3) Identification of the unit to which the VECP applies.

(4) A separate, detailed cost estimate for (i) the affected portions of
    the existing contract requirement and (ii) the VECP. The cost
    reduction associated with the VECP shall take into account the
    Contractor's allowable development and implementation costs,
    including any amount attributable to subcontracts under the
    Subcontracts paragraph of this clause.

(5) A description and estimate of costs the Government may incur in
    implementing the VECP, such as test and evaluation and operating and
    support costs.

(6) A prediction of any effects the proposed change would have on
    collateral costs to the agency.

(7) A statement of the time by which a contract modification accepting
    the VECP must be issued in order to achieve the maximum cost
    reduction, noting any effect on the contract completion time or
    delivery schedule.

(8) Identification of any previous submissions of the VECP, including
    the dates submitted, the agencies and contract numbers involved, and
    previous Government actions, if known.

```{=html}
<!-- -->
```
(d) Submission. The Contractor shall submit VECP's to the Contracting
    Officer, unless this contract states otherwise. If this contract is
    administered by other than the contracting office, the Contractor
    shall submit a copy of the VECP simultaneously to the Contracting
    Officer and to the Administrative Contracting Officer.

(e) Government action.

```{=html}
<!-- -->
```
(1) The Contracting Officer will notify the Contractor of the status of
    the VECP within 45 calendar days after the contracting office
    receives it. If additional time is required, the Contracting Officer
    will notify the Contractor within the 45-day period and provide the
    reason for the delay and the expected date of the decision. The
    Government will process VECP's expeditiously; however, it will not
    be liable for any delay in acting upon a VECP.

(2) If the VECP is not accepted, the Contracting Officer will notify the
    Contractor in writing, explaining the reasons for rejection. The
    Contractor may withdraw any VECP, in whole or in part, at any time
    before it is accepted by the Government. The Contracting Officer may
    require that the Contractor provide written notification before
    undertaking significant expenditures for VECP effort.

(3) Any VECP may be accepted, in whole or in part, by the Contracting
    Officer's award of a modification to this contract citing this
    clause and made either before or within a reasonable time after
    contract performance is completed. Until such a contract
    modification applies a VECP to this contract, the Contractor shall
    perform in accordance with the existing contract. The decision to
    accept or reject all or part of any VECP is a unilateral decision
    made solely at the discretion of the Contracting Officer.

```{=html}
<!-- -->
```
(f) Sharing rates. If a VECP is accepted, the Contractor shall share in
    net acquisition savings according to the percentages shown in the
    table below. The percentage paid the Contractor depends upon---

```{=html}
<!-- -->
```
(1) This contract's type (fixed-price, incentive, or
    cost-reimbursement);

(2) The sharing arrangement specified in paragraph (a) of this clause
    (incentive, program requirement, or a combination as delineated in
    the Schedule); and

(3) The source of the savings (the instant contract, or concurrent and
    future contracts), as follows:

+----------------------------+-------+-----------+-------+-----------+
| [Contractor's Share of Net |       |           |       |           |
| Acquisition Savings        |       |           |       |           |
| (Figure in                 |       |           |       |           |
| Percent)]{.smallcaps}      |       |           |       |           |
+----------------------------+-------+-----------+-------+-----------+
| [Contract                  | [Ince |           | [Pr   |           |
| Type]{.smallcaps}          | ntive |           | ogram |           |
|                            | (Vol  |           | R     |           |
|                            | untar |           | equir |           |
|                            | y)]{. |           | ement |           |
|                            | small |           | (Man  |           |
|                            | caps} |           | dator |           |
|                            |       |           | y)]{. |           |
|                            |       |           | small |           |
|                            |       |           | caps} |           |
+----------------------------+-------+-----------+-------+-----------+
|                            | In    | C         | In    | C         |
|                            | stant | oncurrent | stant | oncurrent |
|                            | Con   | and       | Con   | and       |
|                            | tract | Future    | tract | Future    |
|                            | Rate  | Contract  | Rate  | Contract  |
|                            |       | Rate      |       | Rate      |
+----------------------------+-------+-----------+-------+-----------+
| > Fixed-price (includes    | \*50  | \*50      | 25    | 25        |
| > fixed-price-award-fee;   |       |           |       |           |
| > excludes other           |       |           |       |           |
| > fixed-price incentive    |       |           |       |           |
| > contracts)               |       |           |       |           |
+----------------------------+-------+-----------+-------+-----------+
| > Incentive (fixed-price   | (     | \*50      | (     | 25        |
| > or cost) (other than     | \*\*) |           | \*\*) |           |
| > award fee)               |       |           |       |           |
+----------------------------+-------+-----------+-------+-----------+
| > Cost-reimbursement       | \*\   | \*\*\*25  | 15    | 15        |
| > (includes                | *\*25 |           |       |           |
| > cost-plus-award-fee;     |       |           |       |           |
| > excludes other cost-type |       |           |       |           |
| > incentive contracts)     |       |           |       |           |
+----------------------------+-------+-----------+-------+-----------+
| \* The Contracting Office  |       |           |       |           |
| may increase the           |       |           |       |           |
| Contractor's sharing rate  |       |           |       |           |
| to as high as 75 percent   |       |           |       |           |
| for each VECP.             |       |           |       |           |
|                            |       |           |       |           |
| \*\* Same sharing          |       |           |       |           |
| arrangement as the         |       |           |       |           |
| contract's profit or fee   |       |           |       |           |
| adjustment formula.        |       |           |       |           |
|                            |       |           |       |           |
| \*\*\* The Contracting     |       |           |       |           |
| Office may increase the    |       |           |       |           |
| Contractor's sharing rate  |       |           |       |           |
| to as high as 50 percent   |       |           |       |           |
| for each VECP.             |       |           |       |           |
+----------------------------+-------+-----------+-------+-----------+

(g) Calculating net acquisition savings.

```{=html}
<!-- -->
```
(1) Acquisition savings are realized when (i) the cost or price is
    reduced on the instant contract, (ii) reductions are negotiated in
    concurrent contracts, (iii) future contracts are awarded, or (iv)
    agreement is reached on a lump-sum payment for future contract
    savings (see paragraph (i)(4) of this clause). Net acquisition
    savings are first realized, and the Contractor shall be paid a
    share, when Government costs and any negative instant contract
    savings have been fully offset against acquisition savings.

(2) Except in incentive contracts, Government costs and any price or
    cost increases resulting from negative instant contract savings
    shall be offset against acquisition savings each time such savings
    are realized until they are fully offset. Then, the Contractor's
    share is calculated by multiplying net acquisition savings by the
    appropriate Contractor's percentage sharing rate (see paragraph (f)
    of this clause). Additional Contractor shares of net acquisition
    savings shall be paid to the Contractor at the time realized.

(3) If this is an incentive contract, recovery of Government costs on
    the instant contract shall be deferred and offset against concurrent
    and future contract savings. The Contractor shall share through the
    contract incentive structure in savings on the instant contract
    items affected. Any negative instant contract savings shall be added
    to the target cost or to the target price and ceiling price, and the
    amount shall be offset against concurrent and future contract
    savings.

(4) If the Government does not receive and accept all items on which it
    paid the Contractor's share, the Contractor shall reimburse the
    Government for the proportionate share of these payments.

```{=html}
<!-- -->
```
(h) Contract adjustment. The modification accepting the VECP (or a
    subsequent modification issued as soon as possible after any
    negotiations are completed) shall---

```{=html}
<!-- -->
```
(1) Reduce the contract price or estimated cost by the amount of instant
    contract savings, unless this is an incentive contract;

(2) When the amount of instant contract savings is negative, increase
    the contract price, target price and ceiling price, target cost, or
    estimated cost by that amount;

(3) Specify the Contractor's dollar share per unit on future contracts,
    or provide the lump-sum payment;

(4) Specify the amount of any Government costs or negative instant
    contract savings to be offset in determining net acquisition savings
    realized from concurrent or future contract savings; and

(5) Provide the Contractor's share of any net acquisition savings under
    the instant contract in accordance with the following:

```{=html}
<!-- -->
```
(i) Fixed-price contracts---add to contract price.

(ii) Cost-reimbursement contracts---add to contract fee.

```{=html}
<!-- -->
```
(i) Concurrent and future contract savings.

```{=html}
<!-- -->
```
(1) Payments of the Contractor's share of concurrent and future contract
    savings shall be made by a modification to the instant contract in
    accordance with paragraph (h)(5) of this clause. For incentive
    contracts, shares shall be added as a separate firm-fixed-price line
    item on the instant contract. The Contractor shall maintain records
    adequate to identify the first delivered unit for 3 years after
    final payment under this contract.

(2) The Contracting Officer shall calculate the Contractor's share of
    concurrent contract savings by---

```{=html}
<!-- -->
```
(i) Subtracting from the reduction in price negotiated on the concurrent
    contract any Government costs or negative instant contract savings
    not yet offset; and

(ii) Multiplying the result by the Contractor's sharing rate.

```{=html}
<!-- -->
```
(3) The Contracting Officer shall calculate the Contractor's share of
    future contract savings by---

```{=html}
<!-- -->
```
(i) Multiplying the future unit cost reduction by the number of future
    contract units scheduled for delivery during the sharing period;

(ii) Subtracting any Government costs or negative instant contract
     savings not yet offset; and

(iii) Multiplying the result by the Contractor's sharing rate.

```{=html}
<!-- -->
```
(4) When the Government wishes and the Contractor agrees, the
    Contractor's share of future contract savings may be paid in a
    single lump sum rather than in a series of payments over time as
    future contracts are awarded. Under this alternate procedure, the
    future contract savings may be calculated when the VECP is accepted,
    on the basis of the Contracting Officer's forecast of the number of
    units that will be delivered during the sharing period. The
    Contractor's share shall be included in a modification to this
    contract (see paragraph (h)(3) of this clause) and shall not be
    subject to subsequent adjustment.

(5) Alternate no-cost settlement method. When, in accordance with
    subsection 48.104-4 of the Federal Acquisition Regulation, the
    Government and the Contractor mutually agree to use the no-cost
    settlement method, the following applies:

```{=html}
<!-- -->
```
(i) The Contractor will keep all the savings on the instant contract and
    on its concurrent contracts only.

(ii) The Government will keep all the savings resulting from concurrent
     contracts placed on other sources, savings from all future
     contracts, and all collateral savings.

```{=html}
<!-- -->
```
(j) Collateral savings. If a VECP is accepted, the Contracting Officer
    will increase the instant contract amount, as specified in paragraph
    (h)(5) of this clause, by a rate from 20 to 100 percent, as
    determined by the Contracting Officer, of any projected collateral
    savings determined to be realized in a typical year of use after
    subtracting any Government costs not previously offset. However, the
    Contractor's share of collateral savings will not exceed the
    contract's firm-fixed-price, target price, target cost, or estimated
    cost, at the time the VECP is accepted, or \$100,000, whichever is
    greater. The Contracting Officer will be the sole determiner of the
    amount of collateral savings.

(k) Relationship to other incentives. Only those benefits of an accepted
    VECP not rewardable under performance, design-to-cost (production
    unit cost, operating and support costs, reliability and
    maintainability), or similar incentives shall be rewarded under this
    clause. However, the targets of such incentives affected by the VECP
    shall not be adjusted because of VECP acceptance. If this contract
    specifies targets but provides no incentive to surpass them, the
    value engineering sharing shall apply only to the amount of
    achievement better than target.

(l) Subcontracts. The Contractor shall include an appropriate value
    engineering clause in any subcontract of \$100,000 or more and may
    include one in subcontracts of lesser value. In calculating any
    adjustment in this contract's price for instant contract savings (or
    negative instant contract savings), the Contractor's allowable
    development and implementation costs shall include any
    subcontractor's allowable development and implementation costs, and
    any value engineering incentive payments to a subcontractor, clearly
    resulting from a VECP accepted by the Government under this
    contract. The Contractor may choose any arrangement for
    subcontractor value engineering incentive payments, provided, that
    the payments shall not reduce the Government's share of concurrent
    or future contract savings or collateral savings.

(m) Data. The Contractor may restrict the Government's right to use any
    part of a VECP or the supporting data by marking the following
    legend on the affected parts:

> These data, furnished under the Value Engineering clause of contract
> \_\_\_\_\_\_\_\_, shall not be disclosed outside the Government or
> duplicated, used, or disclosed, in whole or in part, for any purpose
> other than to evaluate a value engineering change proposal submitted
> under the clause. This restriction does not limit the Government's
> right to use information contained in these data if it has been
> obtained or is otherwise available from the Contractor or from another
> source without limitations.
>
> If a VECP is accepted, the Contractor hereby grants the Government
> unlimited rights in the VECP and supporting data, except that, with
> respect to data qualifying and submitted as limited rights technical
> data, the Government shall have the rights specified in the contract
> modification implementing the VECP and shall appropriately mark the
> data. (The terms "unlimited rights" and "limited rights" are defined
> in Part 27 of the Federal Acquisition Regulation.)

(End of clause)

H.41 [MINIMUM INSURANCE COVERAGE FOR VESSEL LIABILITY]{.underline}

(a) In accordance with clause 52.228-7, *Insurance---Liability to Third
    Persons*, and clause 1852.228-75, *Minimum Insurance Coverage*, the
    contractor agrees to obtain and maintain vessel liability coverage,
    in addition to the insurance coverage specified in the cited
    clauses.

(b) During performance of this contract, the Contractor shall secure
    Protection and Indemnity (P&I) marine insurance coverage similar to
    and with limits, customarily offered by the International Group of
    Protection and Indemnity Clubs, for all liabilities excluding those
    for which the Contractor has been relieved by the *Government
    Property* clause of this contract. Contractor may, at its option,
    exclude Workers' Compensation, Jones Act and Longshore and Harbor
    Workers Compensation Act liability coverage from its P&I coverage by
    covering such liabilities under a separate Workers' Compensation
    policy.

(c) The Government shall be listed on the insurance policy required by
    this clause as a "co-insured," and the policy shall contain the
    provision specified in 1852.228-75(d)."

(End of clause)

H.42 [RESERVED]{.underline}

H.43 [RESERVED]{.underline}

H.44 [RESERVED]{.underline}

H.45 [OBSERVANCE OF LEGAL HOLIDAYS (1852.242-72) (AUG 1992) -- Alternate
II (OCT 2000)]{.underline}

(c) The on-site Government personnel observe the following holidays:

> New Year\'s Day
>
> Labor Day
>
> Martin Luther King, Jr.\'s Birthday
>
> Columbus Day
>
> President\'s Day
>
> Veterans Day
>
> Memorial Day
>
> Thanksgiving Day
>
> Independence Day
>
> Christmas Day
>
> Any other day designated by Federal statute, Executive order, or the
> President\'s proclamation.

(d) When any holiday falls on a Saturday, the preceding Friday is
    observed. When any holiday falls on a Sunday, the following Monday
    is observed. Observance of such days by Government personnel shall
    not by itself be cause for an additional period of performance or
    entitlement of compensation except as set forth within the contract.

(e) When the NASA installation grants administrative leave to its
    Government employees (e.g., as a result of inclement weather,
    potentially hazardous conditions, or other special circumstances),
    Contractor personnel working on-site should also be dismissed.
    However, the contractor shall provide sufficient on-site personnel
    to perform round-the-clock requirements of critical work already in
    process, unless otherwise instructed by the Contracting Officer or
    authorized representative.

(f) Whenever administrative leave is granted to Contractor personnel
    pursuant to paragraph (e) of this clause, it shall be without loss
    to the Contractor. The cost of salaries and wages to the Contractor
    for the period of any such excused absence shall be a reimbursable
    item of cost under this contract for employees in accordance with
    the Contractor\'s established accounting policy.

(End of clause)

H.46 [ADMINISTRATIVE CONTRACT CLOSEOUT]{.underline}

Contract closeout activities, per FAR 4.804-5 and NFS 1804.804, and
their associated costs are within the scope and negotiated contract
value of the SPOC, with the following exceptions:

a.  Closeout of firm-fixed-price subcontracts which are physically
    completed after April 1, 2010, are within the scope of the contract,
    but not within the negotiated contract value of the SPOC;

b.  Closeout of other than firm-fixed-price subcontracts which are
    physically completed after October 1, 2008, are within the scope of
    the contract, but not within the negotiated contract value of the
    SPOC;

c.  Operational support to close-out tasks performed after June 30,
    2010, and all closeout tasks performed after September 30, 2010, are
    within the scope of the contract, but not within the negotiated
    contract value of the SPOC.

Not later than April 1, 2010, or other date as mutually agreed upon by
the parties, the contractor shall submit its proposal for equitable
adjustment for closeout activities noted under the above exceptions.
Failure to submit a proposal and pursue an equitable adjustment for the
activities noted under the above exceptions shall not relieve the
contractor of the requirement to perform the closeout activities noted
in the exceptions.

(End of clause)

H.47 [ADJUSTMENT FOR FINAL SPACE SHUTTLE FLIGHT LAUNCH DATE]{.underline}

April 8, 2010, has been established as the date of the last Space
Shuttle flight, with mission execution completion at the conclusion of
down mission processing, following that last flight, in June 2010.
Should the date of the last Space Shuttle flight vary by greater than ±
14 calendar days, the contract will be equitably adjusted (for Space
Shuttle content only, not ISS content) under this clause. This
adjustment is only to recognize variation to the date of the last
manifested flight; contract adjustments for changes to the total number
of flights to be flown are covered under H.33, Launch Schedule
Variations.

Should an adjustment to contract value be required pursuant to this
clause, the contractor shall submit a proposal to NASA not later than
April 2, 2010, or other date as mutually agreed upon by the parties.

(End of clause)

(END OF SECTION)

SECTION I

CONTRACT CLAUSES

I.1 [CLAUSES INCORPORATED BY REFERENCE (52.252-2) (FEB
1998)]{.underline}

This contract incorporates one or more clauses by reference, with the
same force and effect as if they were given in full text. Upon request,
the Contracting Officer will make their full text available. Also, the
full text of a clause may be accessed electronically at this/these
address(es):

Federal Acquisition Regulation (FAR) -- <http://www.acqnet.gov/far/>

NASA FAR Supplement --
<http://www.hq.nasa.gov/office/procurement/regs/nfstoc.htm>

I.2 [CLAUSES INCORPORATED BY REFERENCE]{.underline}

(a) The following clauses are hereby incorporated. The clauses marked
    with an asterisk do not apply to facilities-related effort in this
    contract.

```{=html}
<!-- -->
```
(1) FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) CLAUSES

+----------+-----------------------------------------------------------+
| [Clause  | [Title]{.underline}                                       |
| No.]{.un |                                                           |
| derline} |                                                           |
+==========+===========================================================+
| 52.202-1 | Definitions (Jul 2004)                                    |
+----------+-----------------------------------------------------------+
| 52.203-3 | Gratuities (Apr 1984)                                     |
+----------+-----------------------------------------------------------+
| 52.203-5 | Covenant Against Contingent Fees (Apr 1984)               |
+----------+-----------------------------------------------------------+
| 52.203-6 | Restrictions on Subcontractor Sales to the Government     |
|          | (Sept 2006)                                               |
+----------+-----------------------------------------------------------+
| 52.203-7 | Anti-Kickback Procedures (Jul 1995)                       |
+----------+-----------------------------------------------------------+
| 52.203-8 | Cancellation, Rescission, and Recovery of Funds for       |
|          | Illegal or Improper Activity (Jan 1997)                   |
+----------+-----------------------------------------------------------+
| 5        | Price or Fee Adjustment for Illegal or Improper Activity  |
| 2.203-10 | (Jan 1997)                                                |
+----------+-----------------------------------------------------------+
| 5        | Limitation on Payments to Influence Certain Federal       |
| 2.203-12 | Transactions (Sept 2005)                                  |
+----------+-----------------------------------------------------------+
| 52.204-2 | Security Requirements (Aug 1996)                          |
+----------+-----------------------------------------------------------+
| 52.204-4 | Printed or Copied Double-Sided on Recycled Paper (Aug     |
|          | 2000)                                                     |
+----------+-----------------------------------------------------------+
| 52.204-7 | Central Contractor Registration (Jul 2006)                |
+----------+-----------------------------------------------------------+
| 52.204-9 | Personal Identity Verification of Contractor Personnel    |
|          | (Nov 2006)                                                |
+----------+-----------------------------------------------------------+
| 52.208-8 | Required Sources for Helium and Helium Usage Data (Apr    |
|          | 2002)                                                     |
+----------+-----------------------------------------------------------+
| 52.209-6 | Protecting the Government\'s Interest when Subcontracting |
|          | with Contractors Debarred, Suspended, or Proposed for     |
|          | Debarment (Sept 2006)                                     |
+----------+-----------------------------------------------------------+
| 52.211-5 | Material Requirements (Aug 2000)                          |
+----------+-----------------------------------------------------------+
| 5        | Defense Priority and Allocation Requirements (Sept 1990)  |
| 2.211-15 |                                                           |
+----------+-----------------------------------------------------------+
| 52.215-2 | \*Audit and Records - Negotiations (June 1999)            |
+----------+-----------------------------------------------------------+
| 52.215-8 | Order of Precedence -- Uniform Contract Format (Oct 1997) |
+----------+-----------------------------------------------------------+
| 52.215-9 | Changes or Additions to Make-or-Buy Program (Oct 1997)    |
+----------+-----------------------------------------------------------+
| 5        | Price Reduction For Defective Cost or Pricing Data (Oct   |
| 2.215-10 | 1997)                                                     |
+----------+-----------------------------------------------------------+
| 5        | Subcontractor Cost or Pricing Data (Oct 1997)             |
| 2.215-12 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Integrity of Unit Prices (Oct 1997) -- Alternate I (Oct   |
| 2.215-14 | 1997)                                                     |
+----------+-----------------------------------------------------------+
| 5        | Pension Adjustments and Asset Reversions (Oct 2004)       |
| 2.215-15 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Reversion or Adjustment of Plans for Post Retirement      |
| 2.215-18 | Benefits (PRB) Other Than Pensions (Jul 2005)             |
+----------+-----------------------------------------------------------+
| 5        | Notification of Ownership Changes (Oct 1997)              |
| 2.215-19 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Requirements for Cost or Pricing Data or Information      |
| 2.215-21 | Other Than Cost or Pricing Data -- Modifications (Oct     |
|          | 1997)                                                     |
+----------+-----------------------------------------------------------+
| 52.216-7 | \*Allowable Cost and Payment (Dec 2002); insert "30^th^"  |
+----------+-----------------------------------------------------------+
| 52.217-8 | Option to Extend Services (Nov 1999); insert: 60          |
+----------+-----------------------------------------------------------+
| 52.219-8 | Utilization of Small Business Concerns (May 2004)         |
+----------+-----------------------------------------------------------+
| 52.219-9 | Small Business Subcontracting Plan (Sept 2006)            |
+----------+-----------------------------------------------------------+
| 5        | Liquidated Damages\--Subcontracting Plan (Jan 1999)       |
| 2.219-16 |                                                           |
+----------+-----------------------------------------------------------+
| 52.222-1 | Notice to the Government of Labor Disputes (Feb 1997)     |
+----------+-----------------------------------------------------------+
| 52.222-2 | Payment for Overtime Premiums (Jul 1990); in paragraph    |
|          | (a) insert: \$-0-                                         |
+----------+-----------------------------------------------------------+
| 52.222-4 | Contract Work Hours and Safety Standards Act\--Overtime   |
|          | Compensation (Jul 2005)                                   |
+----------+-----------------------------------------------------------+
| 5        | Walsh-Healey Public Contracts Act (Dec 1996)              |
| 2.222-20 |                                                           |
+----------+-----------------------------------------------------------+
| 52       | Prohibition of Segregated Facilities (Feb 1999)           |
| .222.-21 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Equal Opportunity (April 2002)                            |
| 2.222-26 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Notification of Visa Denial (Jun 2003)                    |
| 2.222-29 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Equal Opportunity For Special Disabled Veterans, Veterans |
| 2.222-35 | of the Vietnam Era, and other Eligible Veterans (Sept     |
|          | 2006)                                                     |
+----------+-----------------------------------------------------------+
| 5        | Affirmative Action for Workers with Disabilities (Jun     |
| 2.222-36 | 1998)                                                     |
+----------+-----------------------------------------------------------+
| 5        | Employment Reports on Special Disabled Veterans, Veterans |
| 2.222-37 | of the Vietnam Era and other Eligible Veterans (Sept      |
|          | 2006)                                                     |
+----------+-----------------------------------------------------------+
| 5        | Service Contract Act of 1965, As Amended (Jul 2005)       |
| 2.222-41 |                                                           |
+----------+-----------------------------------------------------------+
| 52.223-5 | Pollution Prevention and Right-to-Know Information (Aug   |
|          | 2003) -- Alternate I (Aug 2003) & Alternate II (Aug 2003) |
+----------+-----------------------------------------------------------+
| 52.223-6 | Drug-Free Workplace (May 2001)                            |
+----------+-----------------------------------------------------------+
| 52.223-9 | Estimate of Percentage of Recovered Material Content for  |
|          | EPA Designated Products (Aug 2000); insert "Center        |
|          | Environmental Manager"                                    |
+----------+-----------------------------------------------------------+
| 5        | Ozone-Depleting Substances (May 2001)                     |
| 2.223-11 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Refrigeration Equipment and Air Conditioners (May 1995)   |
| 2.223-12 |                                                           |
+----------+-----------------------------------------------------------+
| 52.225-8 | Duty-Free Entry (Feb 2000)                                |
+----------+-----------------------------------------------------------+
| 5        | Restrictions on Certain Foreign Purchases (Feb 2006)      |
| 2.225-13 |                                                           |
+----------+-----------------------------------------------------------+
| 52.226-1 | Utilization of Indian Organizations and Indian-Owned      |
|          | Economic Enterprises (Jun 2000)                           |
+----------+-----------------------------------------------------------+
| 52.227-1 | Authorization and Consent (Jul 1995)                      |
+----------+-----------------------------------------------------------+
| 52.227-2 | Notice and Assistance Regarding Patent and Copyright      |
|          | Infringement (Aug 1996)                                   |
+----------+-----------------------------------------------------------+
| 5        | Additional Data Requirements (Jun 1987)                   |
| 2.227-16 |                                                           |
+----------+-----------------------------------------------------------+
| 52.228-7 | Insurance \-- Liability to Third Persons (Mar 1996)       |
+----------+-----------------------------------------------------------+
| 5        | State of New Mexico Gross Receipts and Compensating Tax   |
| 2.229-10 | (Apr 2003), insert "NASA", "NASA", "NASA", "NASA"         |
+----------+-----------------------------------------------------------+
| 52.230-2 | Cost Accounting Standards (Apr 1998)                      |
+----------+-----------------------------------------------------------+
| 52.230-6 | Administration of Cost Accounting Standards (Apr 2005)    |
+----------+-----------------------------------------------------------+
| 52.232-9 | Limitation on Withholding of Payments (Apr 1984)          |
+----------+-----------------------------------------------------------+
| 5        | Interest (Jun 1996)                                       |
| 2.232-17 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | \*Limitation of Funds (Apr 1984)                          |
| 2.232-22 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Assignment of Claims (Jan 1986)                           |
| 2.232-23 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Prompt Payment (Oct 2003) -- Alternate I (Feb 2002); in   |
| 2.232-25 | paragraphs (a)(1)(i)(A), (a)(1)(i)(B), and (a)(1)(ii)     |
|          | change "30^th^" to "7^th^"                                |
+----------+-----------------------------------------------------------+
| 5        | Payment by Electronic Funds Transfer -- Central           |
| 2.232-33 | Contractor Registration (Oct 2003)                        |
+----------+-----------------------------------------------------------+
| 52.233-1 | Disputes (Jul 2002) \-- Alternate I (Dec 1991)            |
+----------+-----------------------------------------------------------+
| 52.233-3 | Protest After Award (Aug 1996) \-- Alternate I (Jun 1985) |
+----------+-----------------------------------------------------------+
| 52.233-4 | Applicable Law for Breach of Contract Claim (Oct 2004)    |
+----------+-----------------------------------------------------------+
| 52.237-2 | Protection of Government Buildings, Equipment, and        |
|          | Vegetation (Apr 1984)                                     |
+----------+-----------------------------------------------------------+
| 52.242-1 | Notice of Intent to Disallow Costs (Apr 1984)             |
+----------+-----------------------------------------------------------+
| 52.242-3 | Penalties for Unallowable Costs (May 2001)                |
+----------+-----------------------------------------------------------+
| 52.242-4 | Certification of Final Indirect Costs (Jan 1997)          |
+----------+-----------------------------------------------------------+
| 5        | Bankruptcy (Jul 1995)                                     |
| 2.242-13 |                                                           |
+----------+-----------------------------------------------------------+
| 52.243-2 | Changes \-- Cost-Reimbursement (Aug 1987) \-- Alternate   |
|          | II (Apr 1984)                                             |
+----------+-----------------------------------------------------------+
| 52.243-6 | Change Order Accounting (Apr 1984)                        |
+----------+-----------------------------------------------------------+
| 52.244-2 | Subcontracts (Aug 1998) \-- Alternate I (Jan 2006); in    |
|          | paragraph (e) add:                                        |
|          |                                                           |
|          | \(1\) For all Cost-Reimbursable, Time and Material, Labor |
|          | Hour, and Fixed Price subcontract type, advance           |
|          | notification is required for all modifications/changes \> |
|          | \$10M to be provided by monthly report, or may be         |
|          | provided on an individual case-by-case basis, and consent |
|          | is required for initial subcontracts \> \$10M which       |
|          | require cost or pricing data and those identified for     |
|          | "special surveillance".                                   |
|          |                                                           |
|          | \(2\) Special Surveillance:                               |
|          |                                                           |
|          | \(a\) Initial awards \> \$5M and changes \> \$1M to       |
|          | member-subcontractors;                                    |
|          |                                                           |
|          | \(b\) Experimental/Development or Research subcontract    |
|          | type, consent is required for all initial awards;         |
|          |                                                           |
|          | \(c\) Facility subcontract type, consent is required for  |
|          | subcontracts ≥ \$150K;                                    |
|          |                                                           |
|          | \(d\) Letter subcontracts, consent is required for all    |
|          | initial awards;                                           |
|          |                                                           |
|          | \(e\) Construction subcontract type, consent is required  |
|          | for initial awards ≥ \$50K;                               |
|          |                                                           |
|          | \(f\) Directed Subcontract type subcontracts, consent is  |
|          | required for all initial awards;                          |
|          |                                                           |
|          | \(g\) Ratifications (i.e. all orders issued prior to      |
|          | issuance of a contractual document or issued without all  |
|          | required approvals), regardless of dollar amount, consent |
|          | is required.                                              |
|          |                                                           |
|          | \(h\) Consultant Agreements, regardless of dollar amount, |
|          | consent is required for initial awards.                   |
+----------+-----------------------------------------------------------+
| 52.244-5 | Competition in Subcontracting (Dec 1996)                  |
+----------+-----------------------------------------------------------+
| 52.244-6 | Subcontracts for Commercial Items (Sept 2006)             |
+----------+-----------------------------------------------------------+
| 52.245-5 | \*Government Property (Cost-Reimbursement,                |
|          | Time-and-Material, or Labor-Hour Contracts) (May 2004)    |
+----------+-----------------------------------------------------------+
| 5        | Special Test Equipment (Feb 1993)                         |
| 2.245-18 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Government Property Furnished "As Is." (Apr 1984)         |
| 2.245-19 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | \*Limitation of Liability \-- Services (Feb 1997)         |
| 2.246-25 |                                                           |
+----------+-----------------------------------------------------------+
| 52.247-1 | Commercial Bill of Lading Notations (Feb 2006); insert    |
|          | "NASA", "NASA", "NNJ06VA01C", "JSC Procurement Office,    |
|          | 2101 NASA Parkway, Houston, TX 77058"                     |
+----------+-----------------------------------------------------------+
| 5        | Preference for U.S.-Flag Air Carriers (Jun 2003)          |
| 2.247-63 |                                                           |
+----------+-----------------------------------------------------------+
| 5        | Preference for Privately Owned U.S.-Flag Commercial       |
| 2.247-64 | Vessels (Feb 2006) \-- Alternate I (Apr 2003)             |
+----------+-----------------------------------------------------------+
| 52.249-6 | \*Termination (Cost-Reimbursement) (May 2004)             |
+----------+-----------------------------------------------------------+
| 5        | \*Excusable Delays (Apr 1984)                             |
| 2.249-14 |                                                           |
+----------+-----------------------------------------------------------+
| 52.250-1 | Indemnification Under Public Law 85-804 (Apr 1984) \--    |
|          | Alternate I (Apr 1984)                                    |
+----------+-----------------------------------------------------------+
| 52.251-1 | \*Government Supply Sources (Apr 1984)                    |
+----------+-----------------------------------------------------------+
| 52.251-2 | Interagency Fleet Management System (IFMS) Vehicles and   |
|          | Related Services (Jan 1991)                               |
+----------+-----------------------------------------------------------+
| 52.253-1 | Computer Generated Forms (Jan 1991)                       |
+----------+-----------------------------------------------------------+

(2) NASA FAR SUPPLEMENT (48 CFR CHAPTER 18) CLAUSES

  -----------------------------------------------------------------------------
  [Clause            [Title]{.underline}
  No.]{.underline}   
  ------------------ ----------------------------------------------------------
  1852.203-70        Display of Inspector General Hotline Posters (Jun 2001)

  1852.216-89        Assignment and Release Forms (Jul 1997)

  1852.219-74        Use of Rural Area Small Businesses (Sept 1990)

  1852.219-75        Small Business Subcontracting Reporting (May 1999)

  1852.219-76        NASA 8 Percent Goal (Jul 1997)

  1852.219-79        Mentor Requirements and Evaluation (Mar 1999)

  1852.223-74        Drug and Alcohol-Free Workplace (Mar 1996)

  1852.225-8         Duty-Free Entry of Space Articles (Feb 2000), insert
                     "none"

  1852.227-14        Rights in Data -- General (Oct 1995)

  1852.227-87        Transfer of Technical Data Under Space Station
                     International Agreements (Apr 1989)

  1852.228-75        Minimum Insurance Coverage (Oct 1988)

  1852.235-70        Center for Aerospace Information (Feb 2003)

  1852.237-70        Emergency Evacuation Procedures (Dec 1988)

  1852.237-72        Access to Sensitive Information (Jun 2005)

  1852.237-73        Release of Sensitive Information (Jun 2005)

  1852.242-78        Emergency Medical Services and Evacuation (Apr 2001)

  1852.243-71        Shared Savings (Mar 1997)

  1852.245-71        Installation-Accountable Government Property (Nov 2004) --
                     Alternate 1 (Nov 2004) The above clause is applicable to
                     "onsite", as defined in article G.12, equipment which does
                     not meet the criteria for installation "controlled
                     equipment."; insert "See Attachment J-10"
  -----------------------------------------------------------------------------

FACILITIES CLAUSES

(b) The following clauses are incorporated by reference and only apply
    to facilities-related effort in this contract:

```{=html}
<!-- -->
```
(1) FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) CLAUSES

  ------------------------------------------------------------------------------
  [Clause            [Title]{.underline}
  No.]{.underline}   
  ------------------ -----------------------------------------------------------
  52.215-2           Audit and Records \-- Negotiations (Jun 1999) \-- Alternate
                     I (Jan 1997)

  52.216-13          Allowable Cost and Payment -- Facilities (Feb 2002); insert
                     "30^th^"

  52.222-6           Davis-Bacon Act (Jul 2005)

  52.222-7           Withholding of Funds (Feb 1998)

  52.222-9           Apprentices and Trainees (Jul 2005)

  52.222-10          Compliance with Copeland Act Requirements (Feb 1988)

  52.222-11          Subcontracts (Labor Standards) (Jul 2005)

  52.222-12          Contract Termination -- Debarment (Feb 1988)

  52.222-13          Compliance with Davis-Bacon and Related Act Regulations
                     (Feb 1988)

  52.222-14          Disputes Concerning Labor Standards (Feb 1988)

  52.222-15          Certification of Eligibility (Feb 1988)

  52.222-16          Approval of Wage Rates (Feb 1988)

  52.223-10          Waste Reduction Program (Aug 2000)

  52.245-8           Liability for the Facilities (Jan 1997)

  52.245-9           Use and Charges (Aug 2005)

  52.249-11          Termination of Work (Consolidated Facilities or Facilities
                     Acquisition) (May 2004)

  52.249-13          Failure to Perform (Apr 1984)

  52.251-1           Government Supply Sources (Apr 1984) Alternate I (Apr 1984)
  ------------------------------------------------------------------------------

(c) 

```{=html}
<!-- -->
```
(3) 

  ----------- -----------------------------------------------------------
              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              
  ----------- -----------------------------------------------------------

(4) 

  ------------ ----------------------------------------------------------
               

               

               

               

               

               

               

               

               

               

               

               

               

               

               

               

               

               
  ------------ ----------------------------------------------------------

(d) 

```{=html}
<!-- -->
```
(2) 

  ----------- -----------------------------------------------------------
              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              

              
  ----------- -----------------------------------------------------------

I.3 [RESERVED]{.underline}

(End of clause)

I.4 [APPROVAL OF CONTRACT (52.204-1) (DEC 1989)]{.underline}

This contract is subject to the written approval of the NASA Johnson
Space Center Procurement Officer and shall not be binding until so
approved.

(End of clause)

I.5 [NOTIFICATION OF EMPLOYEE RIGHTS CONCERNING PAYMENT OF UNION DUES OR
FEES (52.222-39) (DEC 2004)]{.underline}

(a) Definition. As used in this clause --

> "United States" means the 50 States, the District of Columbia, Puerto
> Rico, the Northern Mariana Islands, American Samoa, Guam, the U.S.
> Virgin Islands, and Wake Island.

(b) Except as provided in paragraph (e) of this clause, during the term
    of this contract, the Contractor shall post a notice, in the form of
    a poster, informing employees of their rights concerning union
    membership and payment of union dues and fees, in conspicuous places
    in and about all its plants and offices, including all places where
    notices to employees are customarily posted. The notice shall
    include the following information (except that the information
    pertaining to National Labor Relations Board shall not be included
    in notices posted in the plants or offices of carriers subject to
    the Railway Labor Act, as amended (45 U.S.C. 151-188)).

Notice to Employees

> Under Federal law, employees cannot be required to join a union or
> maintain membership in a union in order to retain their jobs. Under
> certain conditions, the law permits a union and an employer to enter
> into a union-security agreement requiring employees to pay uniform
> periodic dues and initiation fees. However, employees who are not
> union members can object to the use of their payments for certain
> purposes and can only be required to pay their share of union costs
> relating to collective bargaining, contract administration, and
> grievance adjustment.
>
> If you do not want to pay that portion of dues or fees used to support
> activities not related to collective bargaining, contract
> administration, or grievance adjustment, you are entitled to an
> appropriate reduction in your payment. If you believe that you have
> been required to pay dues or fees used in part to support activities
> not related to collective bargaining, contract administration, or
> grievance adjustment, you may be entitled to a refund and to an
> appropriate reduction in future payments.
>
> For further information concerning your rights, you may wish to
> contact the National Labor Relations Board (NLRB) either at one of its
> Regional offices or at the following address or toll free number:
>
> National Labor Relations Board
>
> Division of Information
>
> 1099 14th Street, N.W.
>
> Washington, DC 20570
>
> 1-866-667-6572
>
> 1-866-316-6572 (TTY)
>
> To locate the nearest NLRB office, see NLRB\'s website at
> [http://www.nlrb.gov](http://www.nlrb.gov/).

(c) The Contractor shall comply with all provisions of Executive Order
    13201 of February 17, 2001, and related implementing regulations at
    29 CFR Part 470, and orders of the Secretary of Labor.

(d) In the event that the Contractor does not comply with any of the
    requirements set forth in paragraphs (b), (c), or (g), the Secretary
    may direct that this contract be cancelled, terminated, or suspended
    in whole or in part, and declare the Contractor ineligible for
    further Government contracts in accordance with procedures at 29 CFR
    Part 470, Subpart B -- Compliance Evaluations, Complaint
    Investigations and Enforcement Procedures. Such other sanctions or
    remedies may be imposed as are provided by 29 CFR Part 470, which
    implements Executive Order 13201, or as are otherwise provided by
    law.

(e) The requirement to post the employee notice in paragraph (b) does
    not apply to --

```{=html}
<!-- -->
```
(1) Contractors and subcontractors that employ fewer than 15 persons;

(2) Contractor establishments or construction work sites where no union
    has been formally recognized by the Contractor or certified as the
    exclusive bargaining representative of the Contractor's employees;

(3) Contractor establishments or construction work sites located in a
    jurisdiction named in the definition of the United States in which
    the law of that jurisdiction forbids enforcement of union-security
    agreements;

(4) Contractor facilities where upon the written request of the
    Contractor, the Department of Labor Deputy Assistant Secretary for
    Labor-Management Programs has waived the posting requirements with
    respect to any of the Contractor's facilities if the Deputy
    Assistant Secretary finds that the Contractor has demonstrated that
    --

```{=html}
<!-- -->
```
(i) The facility is in all respects separate and distinct from
    activities of the Contractor related to the performance of a
    contract; and

(ii) Such a waiver will not interfere with or impede the effectuation of
     the Executive order; or

```{=html}
<!-- -->
```
(5) Work outside the United States that does not involve the recruitment
    or employment of workers within the United States.

```{=html}
<!-- -->
```
(f) The Department of Labor publishes the official employee notice in
    two variations; one for contractors covered by the Railway Labor Act
    and a second for all other contractors. The Contractor shall --

```{=html}
<!-- -->
```
(1) Obtain the required employee notice poster from the Division of
    Interpretations and Standards, Office of Labor-Management Standards,
    U.S. Department of Labor, 200 Constitution Avenue, NW, Room N-5605,
    Washington, DC 20210, or from any field office of the Department's
    Office of Labor-Management Standards or Office of Federal Contract
    Compliance Programs;

(2) Download a copy of the poster from the Office of Labor-Management
    Standards website at
    [http://www.olms.dol.gov](http://www.olms.dol.gov/); or

(3) Reproduce and use exact duplicate copies of the Department of
    Labor's official poster.

```{=html}
<!-- -->
```
(g) The Contractor shall include the substance of this clause in every
    subcontract or purchase order that exceeds the simplified
    acquisition threshold, entered into in connection with this
    contract, unless exempted by the Department of Labor Deputy
    Assistant Secretary for Labor-Management Programs on account of
    special circumstances in the national interest under authority of 29
    CFR 470.3(c). For indefinite quantity subcontracts, the Contractor
    shall include the substance of this clause if the value of orders in
    any calendar year of the subcontract is expected to exceed the
    simplified acquisition threshold. Pursuant to 29 CFR Part 470,
    Subpart B -- Compliance Evaluations, Complaint Investigations and
    Enforcement Procedures, the Secretary of Labor may direct the
    Contractor to take such action in the enforcement of these
    regulations, including the imposition of sanctions for noncompliance
    with respect to any such subcontract or purchase order. If the
    Contractor becomes involved in litigation with a subcontractor or
    vendor, or is threatened with such involvement, as a result of such
    direction, the Contractor may request the United States, through the
    Secretary of Labor, to enter into such litigation to protect the
    interests of the United States.

(End of clause)

I.6 [HAZARDOUS MATERIAL IDENTIFICATION AND MATERIAL SAFETY DATA
(52.223-3) (JAN 1997) -- ALTERNATE I (JUL 1995)]{.underline}

(a) "Hazardous material," as used in this clause, includes any material
    defined as hazardous under the latest version of Federal Standard
    No. 313 (including revisions adopted during the term of the
    contract).

(b) The offeror must list any hazardous material, as defined in
    paragraph (a) of this clause, to be delivered under this contract.
    The hazardous material shall be properly identified and include any
    applicable identification number, such as National Stock Number or
    Special Item Number. This information shall also be included on the
    Material Safety Data Sheet submitted under this contract.

+----------------------------------+-----------------------------------+
| Material                         | Identification No.                |
|                                  |                                   |
| (If none, insert "None")         |                                   |
+----------------------------------+-----------------------------------+
|                                  |                                   |
+----------------------------------+-----------------------------------+
|                                  |                                   |
+----------------------------------+-----------------------------------+
|                                  |                                   |
+----------------------------------+-----------------------------------+

(c) This list must be updated during performance of the contract
    whenever the Contractor determines that any other material to be
    delivered under this contract is hazardous.

(d) The apparently successful offeror agrees to submit, for each item as
    required prior to award, a Material Safety Data Sheet, meeting the
    requirements of 29 CFR 1910.1200(g) and the latest version of
    Federal Standard No. 313, for all hazardous material identified in
    paragraph (b) of this clause. Data shall be submitted in accordance
    with Federal Standard No. 313, whether or not the apparently
    successful offeror is the actual manufacturer of these items.
    Failure to submit the Material Safety Data Sheet prior to award may
    result in the apparently successful offeror being considered
    nonresponsible and ineligible for award.

(e) If, after award, there is a change in the composition of the item(s)
    or a revision to Federal Standard No. 313, which renders incomplete
    or inaccurate the data submitted under paragraph (d) of this clause,
    the Contractor shall promptly notify the Contracting Officer and
    resubmit the data.

(f) Neither the requirements of this clause nor any act or failure to
    act by the Government shall relieve the Contractor of any
    responsibility or liability for the safety of Government,
    Contractor, or subcontractor personnel or property.

(g) Nothing contained in this clause shall relieve the Contractor from
    complying with applicable Federal, State, and local laws, codes,
    ordinances, and regulations (including the obtaining of licenses and
    permits) in connection with hazardous material.

(h) The Government's rights in data furnished under this contract with
    respect to hazardous material are as follows:

```{=html}
<!-- -->
```
(1) To use, duplicate and disclose any data to which this clause is
    applicable. The purposes of this right are to \--

```{=html}
<!-- -->
```
(i) Apprise personnel of the hazards to which they may be exposed in
    using, handling, packaging, transporting, or disposing of hazardous
    materials;

(ii) Obtain medical treatment for those affected by the material; and

(iii) Have others use, duplicate, and disclose the data for the
      Government for these purposes.

```{=html}
<!-- -->
```
(2) To use, duplicate, and disclose data furnished under this clause, in
    accordance with subparagraph (h)(1) of this clause, in precedence
    over any other clause of this contract providing for rights in data.

(3) The Government is not precluded from using similar or identical data
    acquired from other sources.

(End of Clause)

Alternate I (Jul 1995). Add the following paragraph (i) to the basic
clause:

(i) Except as provided in paragraph (i)(2), the Contractor shall prepare
    and submit a sufficient number of Material Safety Data Sheets
    (MSDS's), meeting the requirements of 29 CFR 1910.1200(g) and the
    latest version of Federal Standard No. 313, for all hazardous
    materials identified in paragraph (b) of this clause.

```{=html}
<!-- -->
```
(1) For items shipped to consignees, the Contractor shall include a copy
    of the MSDS's with the packing list or other suitable shipping
    document which accompanies each shipment. Alternatively, the
    Contractor is permitted to transmit MSDS's to consignees in advance
    of receipt of shipments by consignees, if authorized in writing by
    the Contracting Officer.

(2) For items shipped to consignees identified by mailing address as
    agency depots, distribution centers or customer supply centers, the
    Contractor shall provide one copy of the MSDS's in or on each
    shipping container. If affixed to the outside of each container, the
    MSDS's must be placed in a weather resistant envelope.

(End of clause)

I.7 [RIGHTS IN DATA -- GENERAL (JUN 1987) -- ALTERNATE II (JUN 1987) --
ALTERNATE III (JUN 1987) & ALTERNATE V (JUN 1987) AS MODIFIED BY NASA
FAR SUPPLEMENT 1852.227-14]{.underline}

(a) Definitions. "Computer software," as used in this clause, means
    computer programs, computer data bases, and documentation thereof.\
    \
    "Data," as used in this clause, means recorded information,
    regardless of form or the media on which it may be recorded. The
    term includes technical data and computer software. The term does
    not include information incidental to contract administration, such
    as financial, administrative, cost or pricing, or management
    information.\
    \
    "Form, fit, and function data," as used in this clause, means data
    relating to items, components, or processes that are sufficient to
    enable physical and functional interchangeability, as well as data
    identifying source, size, configuration, mating, and attachment
    characteristics, functional characteristics, and performance
    requirements; except that for computer software it means data
    identifying source, functional characteristics, and performance
    requirements but specifically excludes the source code, algorithm,
    process, formulae, and flow charts of the software.\
    \
    "Limited rights," as used in this clause, means the rights of the
    Government in limited rights data as set forth in the Limited Rights
    Notice of paragraph (g)(2) if included in this clause.\
    \
    "Limited rights data," as used in this clause, means data (other
    than computer software) that embody trade secrets or are commercial
    or financial and confidential or privileged, to the extent that such
    data pertain to items, components, or processes developed at private
    expense, including minor modifications thereof.\
    \
    "Restricted computer software," as used in this clause, means
    computer software developed at private expense and that is a trade
    secret; is commercial or financial and is confidential or
    privileged; or is published copyrighted computer software, including
    minor modifications of such computer software.\
    \
    "Restricted rights," as used in this clause, means the rights of the
    Government in restricted computer software, as set forth in a
    Restricted Rights Notice of paragraph (g)(3) if included in this
    clause, or as otherwise may be provided in a collateral agreement
    incorporated in and made part of this contract, including minor
    modifications of such computer software.\
    \
    "Technical data," as used in this clause, means data (other than
    computer software) which are of a scientific or technical nature.\
    \
    "Unlimited rights," as used in this clause, means the right of the
    Government to use, disclose, reproduce, prepare derivative works,
    distribute copies to the public, and perform publicly and display
    publicly, in any manner and for any purpose, and to have or permit
    others to do so.

(b) Allocation of rights.

```{=html}
<!-- -->
```
(1) Except as provided in paragraph (c) of this clause regarding
    copyright, the Government shall have unlimited rights in ---

    i.  Data first produced in the performance of this contract;

    ii. Form, fit, and function data delivered under this contract;

    iii. Data delivered under this contract (except for restricted
         computer software) that constitute manuals or instructional and
         training material for installation, operation, or routine
         maintenance and repair of items, components, or processes
         delivered or furnished for use under this contract; and

    iv. All other data delivered under this contract unless provided
        otherwise for limited rights data or restricted computer
        software in accordance with paragraph (g) of this clause.

(2) The Contractor shall have the right to ---

    i.  Use, release to others, reproduce, distribute, or publish any
        data first produced or specifically used by the Contractor in
        the performance of this contract, unless provided otherwise in
        paragraph (d) of this clause;

    ii. Protect from unauthorized disclosure and use those data which
        are limited rights data or restricted computer software to the
        extent provided in paragraph (g) of this clause;

    iii. Substantiate use of, add or correct limited rights, restricted
         rights, or copyright notices and to take other appropriate
         action, in accordance with paragraphs (e) and (f) of this
         clause; and

    iv. Establish claim to copyright subsisting in data first produced
        in the performance of this contract to the extent provided in
        paragraph (c)(1) of this clause.

```{=html}
<!-- -->
```
(c) Copyright ---

```{=html}
<!-- -->
```
(1) Data first produced in the performance of this contract. Unless
    provided otherwise in paragraph (d) of this clause, the Contractor
    may establish, without prior approval of the Contracting Officer,
    claim to copyright subsisting in scientific and technical articles
    based on or containing data first produced in the performance of
    this contract and published in academic, technical or professional
    journals, symposia proceedings or similar works. The prior, express
    written permission of the Contracting Officer is required to
    establish claim to copyright subsisting in all other data first
    produced in the performance of this contract. When claim to
    copyright is made, the Contractor shall affix the applicable
    copyright notices of 17 U.S.C. 401 or 402 and acknowledgment of
    Government sponsorship (including contract number) to the data when
    such data are delivered to the Government, as well as when the data
    are published or deposited for registration as a published work in
    the U.S. Copyright Office. For data other than computer software the
    Contractor grants to the Government, and others acting on its
    behalf, a paid-up, nonexclusive, irrevocable worldwide license in
    such copyrighted data to reproduce, prepare derivative works,
    distribute copies to the public, and perform publicly and display
    publicly, by or on behalf of the Government. For computer software,
    the Contractor grants to the Government and others acting in its
    behalf, a paid-up nonexclusive, irrevocable worldwide license in
    such copyrighted computer software to reproduce, prepare derivative
    works, and perform publicly and display publicly by or on behalf of
    the Government.

(2) Data not first produced in the performance of this contract. The
    Contractor shall not, without prior written permission of the
    Contracting Officer, incorporate in data delivered under this
    contract any data not first produced in the performance of this
    contract and which contains the copyright notice of 17 U.S.C. 401 or
    402, unless the Contractor identifies such data and grants to the
    Government, or acquires on its behalf, a license of the same scope
    as set forth in paragraph (c)(1) of this clause; provided, however,
    that if such data are computer software the Government shall acquire
    a copyright license as set forth in paragraph (g)(3) of this clause
    if included in this contract or as otherwise may be provided in a
    collateral agreement incorporated in or made part of this contract.

(3) Removal of copyright notices. The Government agrees not to remove
    any copyright notices placed on data pursuant to this paragraph (c),
    and to include such notices on all reproductions of the data.

```{=html}
<!-- -->
```
(d) Release, publication and use of data.

```{=html}
<!-- -->
```
(1) The Contractor shall have the right to use, release to others,
    reproduce, distribute, or publish any data first produced or
    specifically used by the Contractor in the performance of this
    contract, except to the extent such data may be subject to the
    Federal export control or national security laws or regulations, or
    unless otherwise provided in this paragraph of this clause or
    expressly set forth in this contract.

(2) The Contractor agrees that to the extent it receives or is given
    access to data necessary for the performance of this contract which
    contain restrictive markings, the Contractor shall treat the data in
    accordance with such markings unless otherwise specifically
    authorized in writing by the Contracting Officer.

(3) \(i\) The Contractor agrees not to establish claim to copyright,
    publish or release to others any computer software first produced in
    the performance of this contract without the Contracting Officer\'s
    prior written permission.

```{=html}
<!-- -->
```
(ii) If the Government desires to obtain copyright in computer software
     first produced in the performance of this contract and permission
     has not been granted as set forth in paragraph (d)(3)(i) of this
     clause, the Contracting Officer may direct the contractor to
     assert, or authorize the assertion of, claim to copyright in such
     data and to assign, or obtain the assignment of, such copyright to
     the Government or its designated assignee.

(iii) Whenever the word \"establish\" is used in this clause, with
      reference to a claim to copyright, it shall be construed to mean
      \"assert\".

```{=html}
<!-- -->
```
(e) Unauthorized marking of data.

```{=html}
<!-- -->
```
(1) Notwithstanding any other provisions of this contract concerning
    inspection or acceptance, if any data delivered under this contract
    are marked with the notices specified in paragraph (g)(2) or (g)(3)
    of this clause and use of such is not authorized by this clause, or
    if such data bears any other restrictive or limiting markings not
    authorized by this contract, the Contracting Officer may at any time
    either return the data to the Contractor, or cancel or ignore the
    markings. However, the following procedures shall apply prior to
    canceling or ignoring the markings.

```{=html}
<!-- -->
```
(i) The Contracting Officer shall make written inquiry to the Contractor
    affording the Contractor 30 days from receipt of the inquiry to
    provide written justification to substantiate the propriety of the
    markings;

(ii) If the Contractor fails to respond or fails to provide written
     justification to substantiate the propriety of the markings within
     the 30-day period (or a longer time not exceeding 90 days approved
     in writing by the Contracting Officer for good cause shown), the
     Government shall have the right to cancel or ignore the markings at
     any time after said period and the data will no longer be made
     subject to any disclosure prohibitions.

(iii) If the Contractor provides written justification to substantiate
      the propriety of the markings within the period set in subdivision
      (e)(1)(i) of this clause, the Contracting Officer shall consider
      such written justification and determine whether or not the
      markings are to be cancelled or ignored. If the Contracting
      Officer determines that the markings are authorized, the
      Contractor shall be so notified in writing. If the Contracting
      Officer determines, with concurrence of the head of the
      contracting activity, that the markings are not authorized, the
      Contracting Officer shall furnish the Contractor a written
      determination, which determination shall become the final agency
      decision regarding the appropriateness of the markings unless the
      Contractor files suit in a court of competent jurisdiction within
      90 days of receipt of the Contracting Officer's decision. The
      Government shall continue to abide by the markings under this
      subdivision (e)(1)(iii) until final resolution of the matter
      either by the Contracting Officer's determination becoming final
      (in which instance the Government shall thereafter have the right
      to cancel or ignore the markings at any time and the data will no
      longer be made subject to any disclosure prohibitions), or by
      final disposition of the matter by court decision if suit is
      filed.

```{=html}
<!-- -->
```
(2) The time limits in the procedures set forth in paragraph (e)(1) of
    this clause may be modified in accordance with agency regulations
    implementing the Freedom of Information Act (5 U.S.C. 552) if
    necessary to respond to a request thereunder.

(3) This paragraph (e) does not apply if this contract is for a major
    system or for support of a major system by a civilian agency other
    than NASA and the U.S. Coast Guard agency subject to the provisions
    of Title III of the Federal Property and Administrative Services Act
    of 1949.

(4) Except to the extent the Government's action occurs as the result of
    final disposition of the matter by a court of competent
    jurisdiction, the Contractor is not precluded by this paragraph (e)
    from bringing a claim under the Contract Disputes Act, including
    pursuant to the Disputes clause of this contract, as applicable,
    that may arise as the result of the Government removing or ignoring
    authorized markings on data delivered under this contract.

```{=html}
<!-- -->
```
(f) Omitted or incorrect markings.

```{=html}
<!-- -->
```
(1) Data delivered to the Government without either the limited rights
    or restricted rights notice as authorized by paragraph (g) of this
    clause, or the copyright notice required by paragraph (c) of this
    clause, shall be deemed to have been furnished with unlimited
    rights, and the Government assumes no liability for the disclosure,
    use, or reproduction of such data. However, to the extent the data
    has not been disclosed without restriction outside the Government,
    the Contractor may request, within 6 months (or a longer time
    approved by the Contracting Officer for good cause shown) after
    delivery of such data, permission to have notices placed on
    qualifying data at the Contractor's expense, and the Contracting
    Officer may agree to do so if the Contractor ---

```{=html}
<!-- -->
```
(i) Identifies the data to which the omitted notice is to be applied;

(ii) Demonstrates that the omission of the notice was inadvertent;

(iii) Establishes that the use of the proposed notice is authorized; and

(iv) Acknowledges that the Government has no liability with respect to
     the disclosure, use, or reproduction of any such data made prior to
     the addition of the notice or resulting from the omission of the
     notice.

```{=html}
<!-- -->
```
(2) The Contracting Officer may also (i) permit correction at the
    Contractor's expense of incorrect notices if the Contractor
    identifies the data on which correction of the notice is to be made,
    and demonstrates that the correct notice is authorized, or (ii)
    correct any incorrect notices.

```{=html}
<!-- -->
```
(g) Protection of limited rights data and restricted computer software.

```{=html}
<!-- -->
```
(1) When data other than that listed in subdivisions (b)(1)(i), (ii),
    and (iii) of this clause are specified to be delivered under this
    contract and qualify as either limited rights data or restricted
    computer software, if the Contractor desires to continue protection
    of such data, the Contractor shall withhold such data and not
    furnish them to the Government under this contract. As a condition
    to this withholding, the Contractor shall identify the data being
    withheld and furnish form, fit, and function data in lieu thereof.
    Limited rights data that are formatted as a computer data base for
    delivery to the Government are to be treated as limited rights data
    and not restricted computer software.

(2) Notwithstanding paragraph (g)(1) of this clause, the contract may
    identify and specify the delivery of limited rights data, or the
    Contracting Officer may require by written request the delivery of
    limited rights data that has been withheld or would otherwise be
    withholdable. If delivery of such data is so required, the
    Contractor may affix the following "Limited Rights Notice" to the
    data and the Government will thereafter treat the data, subject to
    the provisions of paragraphs (e) and (f) of this clause, in
    accordance with such Notice:

*Limited Rights Notice (June 1987)*

*(a) These data are submitted with limited rights under Government
Contract No. NNJ06VA01C (and subcontract \_\_\_\_\_\_, if appropriate).
These data may be reproduced and used by the Government with the express
limitation that they will not, without written permission of the
Contractor, be used for purposes of manufacture nor disclosed outside
the Government; except that the Government may disclose these data
outside the Government for the following purposes, if any; provided that
the Government makes such disclosure subject to prohibition against
further use and disclosure:\
*

(i) *Use (except for manufacture) by support service contractors.*

(ii) *Evaluation by nongovernment evaluators.*

(iii) *Use (except for manufacture) by other contractors participating
      in the Government's program of which the specific contract is a
      part, for information and use in connection with the work
      performed under each contract.*

(iv) *Emergency repair or overhaul work.*

(v) *Release to a foreign government, or instrumentality thereof, as the
    interests of the United States Government may require, for
    information or evaluation, or for emergency repair or overhaul work
    by such government.*

*(b) This Notice shall be marked on any reproduction of these data, in
whole or in part.*

*(End of notice)*

(3) \(i\) Notwithstanding paragraph (g)(1) of this clause, the contract
    may identify and specify the delivery of restricted computer
    software, or the Contracting Officer may require by written request
    the delivery of restricted computer software that has been withheld
    or would otherwise be withholdable. If delivery of such computer
    software is so required, the Contractor may affix the following
    "Restricted Rights Notice" to the computer software and the
    Government will thereafter treat the computer software, subject to
    paragraphs (e) and (f) of this clause, in accordance with the
    Notice:

*Restricted Rights Notice (June 1987)*

(a) *This computer software is submitted with restricted rights under
    Government Contract No. NNJ06VA01C (and subcontract
    \_\_\_\_\_\_\_\_, if appropriate). It may not be used, reproduced,
    or disclosed by the Government except as provided in paragraph (b)
    of this Notice or as otherwise expressly stated in the contract.*

(b) *This computer software may be ---*

```{=html}
<!-- -->
```
(1) *Used or copied for use in or with the computer or computers for
    which it was acquired, including use at any Government installation
    to which such computer or computers may be transferred;*

(2) *Used or copied for use in a backup computer if any computer for
    which it was acquired is inoperative;*

(3) *Reproduced for safekeeping (archives) or backup purposes;*

(4) *Modified, adapted, or combined with other computer software,
    provided that the modified, combined, or adapted portions of the
    derivative software incorporating restricted computer software are
    made subject to the same restricted rights;*

(5) *Disclosed to and reproduced for use by support service Contractors
    in accordance with paragraphs (b)(1) through (4) of this clause,
    provided the Government makes such disclosure or reproduction
    subject to these restricted rights; and*

(6) *Used or copied for use in or transferred to a replacement
    computer.*

```{=html}
<!-- -->
```
(c) *Notwithstanding the foregoing, if this computer software is
    published copyrighted computer software, it is licensed to the
    Government, without disclosure prohibitions, with the minimum rights
    set forth in paragraph (b) of this clause.*

(d) *Any other rights or limitations regarding the use, duplication, or
    disclosure of this computer software are to be expressly stated in,
    or incorporated in, the contract.*

(e) *This Notice shall be marked on any reproduction of this computer
    software, in whole or in part.*

*(End of notice)*

(ii) Where it is impractical to include the Restricted Rights Notice on
     restricted computer software, the following short-form Notice may
     be used in lieu thereof:

*Restricted Rights Notice Short Form (June 1987)*

*Use, reproduction, or disclosure is subject to restrictions set forth
in Contract No. NNJ06VA01C (and subcontract, if appropriate) with
\_\_\_\_\_\_\_\_ (name of Contractor and subcontractor).*

*(End of notice)*

(iii) If restricted computer software is delivered with the copyright
      notice of 17 U.S.C. 401, it will be presumed to be published
      copyrighted computer software licensed to the Government without
      disclosure prohibitions, with the minimum rights set forth in
      paragraph (b) of this clause, unless the Contractor includes the
      following statement with such copyright notice:
      "Unpublished---rights reserved under the Copyright Laws of the
      United States."

```{=html}
<!-- -->
```
(h) Subcontracting. The Contractor has the responsibility to obtain from
    its subcontractors all data and rights therein necessary to fulfill
    the Contractor's obligations to the Government under this contract.
    If a subcontractor refuses to accept terms affording the Government
    such rights, the Contractor shall promptly bring such refusal to the
    attention of the Contracting Officer and not proceed with
    subcontract award without further authorization.

(i) Relationship to patents. Nothing contained in this clause shall
    imply a license to the Government under any patent or be construed
    as affecting the scope of any license or other right otherwise
    granted to the Government.

(j) The Contractor agrees, except as may be otherwise specified in this
    contract for specific data items listed as not subject to this
    paragraph, that the Contracting Officer or an authorized
    representative may, up to three years after acceptance of all items
    to be delivered under this contract, inspect at the Contractor's
    facility any data withheld pursuant to paragraph (g)(1) of this
    clause, for purposes of verifying the Contractor's assertion
    pertaining to the limited rights or restricted rights status of the
    data or for evaluating work performance. Where the Contractor whose
    data are to be inspected demonstrates to the Contracting Officer
    that there would be a possible conflict of interest if the
    inspection were made by a particular representative, the Contracting
    Officer shall designate an alternate inspector.

(End of clause)

I.8 [INDUSTRIAL RESOURCES DEVELOPED UNDER DEFENSE PRODUCTION ACT TITLE
III (52.234-1) (DEC 1994)]{.underline}

(a) Definitions.

> Title III industrial resource means materials, services, processes, or
> manufacturing equipment (including the processes, technologies, and
> ancillary services for the use of such equipment) established or
> maintained under the authority of Title III, Defense Production Act
> (50 U.S.C. App. 2091 2093).
>
> Title III project contractor means a Contractor that has received
> assistance for the development or manufacture of an industrial
> resource under 50 U.S.C. App. 2091 2093, Defense Production Act.

(b) The Contractor shall refer any request from a Title III project
    contractor for testing and qualification of a Title III industrial
    resource to the Contracting Officer.

(c) Upon the direction of the Contracting Officer, the Contractor shall
    test Title III industrial resources for qualification. The
    Contractor shall provide the test results to the Defense Production
    Act Office, Title III Program, located at Wright Patterson Air Force
    Base, Ohio 45433 7739.

(d) When the Contracting Officer modifies the contract to direct testing
    pursuant to this clause, the Government will provide the Title III
    industrial resource to be tested and will make an equitable
    adjustment in the contract for the costs of testing and
    qualification of the Title III industrial resource.

(e) The Contractor agrees to insert the substance of this clause,
    including paragraph (e), in every subcontract issued in performance
    of this contract.

(End of clause)

I.9 [CONTINUITY OF SERVICES (52.237-3) (JAN 1991)]{.underline}

(a) The Contractor recognizes that the services under this contract are
    vital to the Government and must be continued without interruption
    and that, upon contract expiration, a successor, either the
    Government or another contractor, may continue them. The Contractor
    agrees to (1) furnish phase-in training and (2) exercise its best
    efforts and cooperation to effect an orderly and efficient
    transition to a successor.

(b) The Contractor shall, upon the Contracting Officer\'s written
    notice, (1) furnish phase-in, phase-out services for up to 90 days
    after this contract expires and (2) negotiate in good faith a plan
    with a successor to determine the nature and extent of phase- in,
    phase-out services required. The plan shall specify a training
    program and a date for transferring responsibilities for each
    division of work described in the plan, and shall be subject to the
    Contracting Officer\'s approval. The Contractor shall provide
    sufficient experienced personnel during the phase-in, phase-out
    period to ensure that the services called for by this contract are
    maintained at the required level of proficiency.

(c) The Contractor shall allow as many personnel as practicable to
    remain on the job to help the successor maintain the continuity and
    consistency of the services required by this contract. The
    Contractor also shall disclose necessary personnel records and allow
    the successor to conduct on-site interviews with these employees. If
    selected employees are agreeable to the change, the Contractor shall
    release them at a mutually agreeable date and negotiate transfer of
    their earned fringe benefits to the successor.

(d) The Contractor shall be reimbursed for all reasonable phase-in,
    phase-out costs (i.e., costs incurred within the agreed period after
    contract expiration that result from phase-in, phase-out operations)
    and a fee (profit) not to exceed a pro rata portion of the fee
    (profit) under this contract.

I.10 [NOTIFICATION OF CHANGES (52.243-7) (APR 1984)]{.underline}

(a) Definitions.

> \"Contracting Officer,\" as used in this clause, does not include any
> representative of the Contracting Officer.
>
> \"Specifically authorized representative (SAR),\" as used in this
> clause, means any person the Contracting Officer has so designated by
> written notice (a copy of which shall be provided to the Contractor)
> which shall refer to this subparagraph and shall be issued to the
> designated representative before the SAR exercises such authority.

(b) Notice. The primary purpose of this clause is to obtain prompt
    reporting of Government conduct that the Contractor considers to
    constitute a change to this contract. Except for changes identified
    as such in writing and signed by the Contracting Officer, the
    Contractor shall notify the Administrative Contracting Officer in
    writing promptly, within 7 calendar days from the date that the
    Contractor identifies any Government conduct (including actions,
    inactions, and written or oral communications) that the Contractor
    regards as a change to the contract terms and conditions. On the
    basis of the most accurate information available to the Contractor,
    the notice shall state

```{=html}
<!-- -->
```
(1) The date, nature, and circumstances of the conduct regarded as a
    change;

(2) The name, function, and activity of each Government individual and
    Contractor official or employee involved in or knowledgeable about
    such conduct;

(3) The identification of any documents and the substance of any oral
    communication involved in such conduct;

(4) In the instance of alleged acceleration of scheduled performance or
    delivery, the basis upon which it arose;

(5) The particular elements of contract performance for which the
    Contractor may seek an equitable adjustment under this clause,
    including

```{=html}
<!-- -->
```
(i) What contract line items have been or may be affected by the alleged
    change,

(ii) What labor or materials or both have been or may be added, deleted,
     or wasted by the alleged change;

(iii) To the extent practicable, what delay and disruption in the manner
      and sequence of performance and effect on continued performance
      have been or may be caused by the alleged change;

(iv) What adjustments to contract price, delivery schedule, and other
     provisions affected by the alleged change are estimated; and

```{=html}
<!-- -->
```
(6) The Contractor\'s estimate of the time by which the Government must
    respond to the Contractor\'s notice to minimize cost, delay or
    disruption of performance.

```{=html}
<!-- -->
```
(c) Continued performance. Following submission of the notice required
    by (b) above, the Contractor shall diligently continue performance
    of this contract to the maximum extent possible in accordance with
    its terms and conditions as construed by the Contractor, unless the
    notice reports a direction of the Contracting Officer or a
    communication from a SAR of the Contracting Officer, in either of
    which events the Contractor shall continue performance; provided,
    however, that if the Contractor regards the direction or
    communication as a change as described in (b) above, notice shall be
    given in the manner provided. All directions, communications,
    interpretations, orders and similar actions of the SAR shall be
    reduced to writing promptly and copies furnished to the Contractor
    and to the Contracting Officer. The Contracting Officer shall
    promptly countermand any action which exceeds the authority of the
    SAR.

(d) Government response. The Contracting Officer shall promptly, within
    TBN calendar days after receipt of notice, respond to the notice in
    writing. In responding, the Contracting Officer shall either

```{=html}
<!-- -->
```
(1) Confirm that the conduct of which the Contractor gave notice
    constitutes a change and when necessary direct the mode of further
    performance;

(2) Countermand any communication regarded as a change;

(3) Deny that the conduct of which the Contractor gave notice
    constitutes a change and when necessary direct the mode of further
    performance; or

(4) In the event the Contractor\'s notice information is inadequate to
    make a decision under (1), (2), or (3) above, advise the Contractor
    what additional information is required, and establish the date by
    which it should be furnished and the date thereafter by which the
    Government will respond.

```{=html}
<!-- -->
```
(e) Equitable adjustments.

```{=html}
<!-- -->
```
(1) If the Contracting Officer confirms that Government conduct effected
    a change as alleged by the Contractor, and the conduct causes an
    increase or decrease in the Contractor\'s cost of, or the time
    required for, performance of any part of the work under this
    contract, whether changed or not changed by such conduct, an
    equitable adjustment shall be made --

```{=html}
<!-- -->
```
(i) In the contract price or delivery schedule or both; and

(ii) In such other provisions of the contract as may be affected.

```{=html}
<!-- -->
```
(2) The contract shall be modified in writing accordingly. In the case
    of drawings, designs or specifications which are defective and for
    which the Government is responsible, the equitable adjustment shall
    include the cost and time extension for delay reasonably incurred by
    the Contractor in attempting to comply with the defective drawings,
    designs or specifications before the Contractor identified, or
    reasonably should have identified, such defect. When the cost of
    property made obsolete or excess as a result of a change confirmed
    by the Contracting Officer under this clause is included in the
    equitable adjustment, the Contracting Officer shall have the right
    to prescribe the manner of disposition of the property. The
    equitable adjustment shall not include increased costs or time
    extensions for delay resulting from the Contractor\'s failure to
    provide notice or to continue performance as provided, respectively,
    in (b) and (c) above.

(End of clause)

I.11 [RESERVED]{.underline}

I.12 [RESERVED]{.underline}

I.13 [AUTHORIZED DEVIATIONS IN CLAUSES (52.252-6) (APR
1984)]{.underline}

(a) The use in this solicitation or contract of any Federal Acquisition
    Regulation (48 CFR Chapter 1) clause with an authorized deviation is
    indicated by the addition of \"(DEVIATION)\" after the date of the
    clause.

(b) The use in this solicitation or contract of any NASA FAR Supplement
    Regulation (48 CFR Chapter 18) clause with an authorized deviation
    is indicated by the addition of \"(DEVIATION)\" after the name of
    the regulation.

(End of clause)

I.14 [SECURITY CLASSIFICATION REQUIREMENTS (1852.204-75) (SEPT
1989)]{.underline}

Performance under this contract will involve access to and/or generation
of classified information, work in a security area, or both, up to the
level of TOP SECRET. See Federal Acquisition Regulation clause 52.204 2
in this contract and DD Form 254, Contract Security Classification
Specification, Attachment J-17.

(End of clause)

I.15 [SECURITY REQUIREMENTS FOR UNCLASSIFIED INFORMATION TECHNOLOGY
RESOURCES (1852.204-76) (NOV 2004 \[DEVIATION\])]{.underline}

\(a\) The Contractor shall be responsible for information and
information technology (IT) security when the Contractor or its
subcontractors must obtain physical or electronic (i.e., authentication
level 2 and above as defined in National Institute of Standards and
Technology (NIST) Special Publication (SP) 800-63, Electronic
Authentication Guideline) access to NASA\'s computer systems, networks,
or IT infrastructure, or where information categorized as low, moderate,
or high by the Federal Information Processing Standards (FIPS) 199,
Standards for Security Categorization of Federal Information and
Information Systems, is stored, generated, or exchanged by NASA or on
behalf of NASA by a contractor or subcontractor, regardless of whether
the information resides on a NASA or a contractor/subcontractor's
information system.

\(b\) IT Security Requirements.

\(1\) Within 30 days after contract award, a Contractor shall submit to
the Contracting Officer for NASA approval an IT Security Plan, Risk
Assessment, and FIPS 199, Standards for Security Categorization of
Federal Information and Information Systems, Assessment. These plans and
assessments, including annual updates shall be incorporated into the
contract as compliance documents.

\(i\) The IT system security plan shall be prepared consistent, in form
and content, with NIST SP 800-18, Guide for Developing Security Plans
for Federal Information Systems, and any additions/augmentations
described in NASA Procedural Requirements (NPR) 2810.1A, Security of
Information Technology. The security plan shall identify and document
appropriate IT security controls consistent with the sensitivity of the
information and the requirements of Federal Information Processing
Standards (FIPS) 200, Recommended Security Controls for Federal
Information Systems. The plan shall be reviewed and updated in
accordance with NIST SP 800-26, Security Self-Assessment Guide for
Information Technology Systems, and FIPS 200, on a yearly basis.

\(ii\) The risk assessment shall be prepared consistent, in form and
content, with NIST SP 800-30, Risk Management Guide for Information
Technology Systems, and any additions/augmentations described in NPR
2810.1A. The risk assessment shall be updated on a yearly basis.

\(iii\) The FIPS 199 assessment shall identify all information types as
well as the "high water mark," as defined in FIPS 199, of the processed,
stored, or transmitted information necessary to fulfill the contractual
requirements.

\(2\) The Contractor shall produce contingency plans consistent, in form
and content, with NIST SP 800-34, Contingency Planning Guide for
Information Technology Systems, and any additions/augmentations
described in NPR 2810.1A. The Contractor shall perform yearly "Classroom
Exercises." "Functional Exercises," shall be coordinated with the Center
CIOs and be conducted once every three years, with the first conducted
within the first two years of contract award. These exercises are
defined and described in NIST SP 800-34.

\(3\) The Contractor shall ensure coordination of its incident response
team with the NASA Incident Response Center and the NASA Security
Operations Center.

\(4\) The Contractor shall ensure that its employees, in performance of
the contract, receive annual IT security training in NASA IT Security
policies, procedures, computer ethics, and best practices in accordance
with NPR 2810.1A requirements. The Contractor may use web-based training
available from NASA to meet this requirement.

\(5\) The Contractor shall provide NASA, including the NASA Office of
Inspector General, access to the Contractor's and subcontractors'
facilities, installations, operations, documentation, databases, and
personnel used in performance of the contract. Access shall be provided
to the extent required to carry out IT security inspection,
investigation, and/or audits to safeguard against threats and hazards to
the integrity, availability, and confidentiality of NASA information or
to the function of computer systems operated on behalf of NASA, and to
preserve evidence of computer crime. To facilitate mandatory reviews,
the Contractor shall ensure appropriate compartmentalization of NASA
information, stored and/or processed, either by information systems in
direct support of the contract or that are incidental to the contract.

\(6\) The Contractor shall ensure that all individuals who perform tasks
as a system administrator, or have authority to perform tasks normally
performed by a system administrator, demonstrate knowledge appropriate
to those tasks. Knowledge is demonstrated through the NASA System
Administrator Security Certification Program. A system administrator is
one who provides IT services, network services, files storage, and/or
web services, to someone else other than themselves and takes or assumes
the responsibility for the security and administrative controls of that
service. Within 30 days after contract award, the Contractor shall
provide to the Contracting Officer a list of all system administrator
positions and personnel filling those positions, along with a schedule
that ensures certification of all personnel within 90 days after
contract award. Additionally, the Contractor should report all personnel
changes which impact system administrator positions within 5 days of the
personnel change and ensure these individuals obtain System
Administrator certification within 90 days after the change.

\(7\) When the Contractor is located at a NASA Center or installation or
is using NASA IP address space, the Contractor shall \--

\(i\) Submit requests for non-NASA provided external Internet
connections to the Contracting Officer for approval by the Network
Security Configuration Control Board (NSCCB);

\(ii\) Comply with the NASA CIO metrics including patch management,
operating systems and application configuration guidelines,
vulnerability scanning, incident reporting, system administrator
certification, and security training; and

\(iii\) Utilize the NASA Public Key Infrastructure (PKI) for all
encrypted communication or non-repudiation requirements within NASA when
secure email capability is required.

\(c\) Physical and Logical Access Requirements.

\(1\) Contractor personnel requiring access to IT systems operated by
the Contractor for NASA or interconnected to a NASA network shall be
screened at an appropriate level in accordance with NPR 2810.1A and
Chapter 4, NPR 1600.1, NASA Security Program Procedural Requirements.
NASA shall provide screening, appropriate to the highest risk level, of
the IT systems and information accessed, using, as a minimum, National
Agency Check with Inquiries (NACI). The Contractor shall submit the
required forms to the NASA Center Chief of Security (CCS) within
fourteen (14) days after contract award or assignment of an individual
to a position requiring screening. The forms may be obtained from the
CCS. At the option of NASA, interim access may be granted pending
completion of the required investigation and final access determination.
For Contractors who will reside on a NASA Center or installation, the
security screening required for all required access (e.g., installation,
facility, IT, information, etc.) is consolidated to ensure only one
investigation is conducted based on the highest risk level. Contractors
not residing on a NASA installation will be screened based on their IT
access risk level determination only. See NPR 1600.1, Chapter 4.

\(2\) Guidance for selecting the appropriate level of screening is based
on the risk of adverse impact to NASA missions. NASA defines three
levels of risk for which screening is required (IT-1 has the highest
level of risk).

\(i\) IT-1 \-- Individuals having privileged access or limited
privileged access to systems whose misuse can cause very serious adverse
impact to NASA missions. These systems include, for example, those that
can transmit commands directly modifying the behavior of spacecraft,
satellites or aircraft.

\(ii\) IT-2 \-- Individuals having privileged access or limited
privileged access to systems whose misuse can cause serious adverse
impact to NASA missions. These systems include, for example, those that
can transmit commands directly modifying the behavior of payloads on
spacecraft, satellites or aircraft; and those that contain the primary
copy of "level 1" information whose cost to replace exceeds one million
dollars.

\(iii\) IT-3 \-- Individuals having privileged access or limited
privileged access to systems whose misuse can cause significant adverse
impact to NASA missions. These systems include, for example, those that
interconnect with a NASA network in a way that exceeds access by the
general public, such as bypassing firewalls; and systems operated by the
Contractor for NASA whose function or information has substantial cost
to replace, even if these systems are not interconnected with a NASA
network.

\(3\) Screening for individuals shall employ forms appropriate for the
level of risk as established in Chapter 4, NPR 1600.1.

\(4\) The Contractor may conduct its own screening of individuals
requiring privileged access or limited privileged access provided the
Contractor can demonstrate to the Contracting Officer that the
procedures used by the Contractor are equivalent to NASA\'s personnel
screening procedures for the risk level assigned for the IT position.

\(5\) Subject to approval of the Contracting Officer, the Contractor may
forgo screening of Contractor personnel for those individuals who have
proof of a \--

\(i\) Current or recent national security clearances (within last three
years);

\(ii\) Screening conducted by NASA within the last three years that
meets or exceeds the screening requirements of the IT position; or

\(iii\) Screening conducted by the Contractor, within the last three
years, that is equivalent to the NASA personnel screening procedures as
approved by the Contracting Officer and concurred on by the CCS.

\(d\) The Contracting Officer may waive the requirements of paragraphs
(b) and (c)(1) through (c)(3) upon request of the Contractor. The
Contractor shall provide all relevant information requested by the
Contracting Officer to support the waiver request.

\(e\) The Contractor shall contact the Contracting Officer for any
documents, information, or forms necessary to comply with the
requirements of this clause.

\(f\) The Contractor shall insert this clause, including this paragraph
(f), in all subcontracts when the subcontractor is required to --

\(1\) Have physical or electronic access to NASA\'s computer systems,
networks, or IT infrastructure; or

\(2\) Use information systems to generate, store, or exchange data with
NASA or on behalf of NASA, regardless of whether the data resides on a
NASA or a contractor's information system.

(End of clause)

I.16 [OMBUDSMAN (1852.215-84) (OCT 2003)]{.underline}

(a) An ombudsman has been appointed to hear and facilitate the
    resolution of concerns from offerors, potential offerors, and
    contractors during the preaward and postaward phases of this
    acquisition. When requested, the ombudsman will maintain strict
    confidentiality as to the source of the concern. The existence of
    the ombudsman is not to diminish the authority of the contracting
    officer, the Source Evaluation Board, or the source selection
    official. Further, the ombudsman does not participate in the
    evaluation of proposals, the source selection process, or the
    adjudication of formal contract disputes. Therefore, before
    consulting with an ombudsman, interested parties must first address
    their concerns, issues, disagreements, and/or recommendations to the
    contracting officer for resolution.

(b) If resolution cannot be made by the contracting officer, interested
    parties may contact the installation ombudsman, Lucy V. Kranz,
    Associate Director (Management), NASA, Lyndon B. Johnson Space
    Center, Mail code AC, 2101 NASA Parkway, Houston, TX 77058,
    281-244-7683 (phone), 281-483-2200 (fax), lucy.v.kranz@nasa.gov.
    Concerns, issues, disagreements, and recommendations which cannot be
    resolved at the installation may be referred to the NASA ombudsman,
    the Director of the Contract Management Division, at 202-358-0445,
    facsimile 202-358-3083, e-mail james.a.balinskas@nasa.gov. Please do
    not contact the ombudsman to request copies of the solicitation,
    verify offer due date, or clarify technical requirements. Such
    inquiries shall be directed to the Contracting Officer or as
    specified elsewhere in this document.

(End of clause)

(c) 
(d) 

I.17 [STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES (52.222-42) (MAY
1989)]{.underline}

In compliance with the Service Contract Act of 1965, as amended, and the
regulations of the Secretary of Labor (29 CFR Part 4), this clause
identifies the classes of service employees expected to be employed
under the contract and states the wages and fringe benefits payable to
each if they were employed by the contracting agency subject to the
provisions of 5 USC 5341 or 5332.

THIS STATEMENT IS FOR INFORMATION ONLY:

IT IS NOT A WAGE DETERMINATION

Employee Class Monetary Wage - Fringe Benefits

\-\-- See Attachment J-7 \-\--

(End of clause)

I.18 [BUY AMERICAN ACT -- CONSTRUCTION MATERIALS (52.225-9) (JAN
2005)]{.underline}

\[This clause applies only to facilities-related effort in this
contract.\]

(a) Definitions. As used in this clause --

> "Component" means an article, material, or supply incorporated
> directly into a construction material.
>
> "Construction material" means an article, material, or supply brought
> to the construction site by the Contractor or a subcontractor for
> incorporation into the building or work. The term also includes an
> item brought to the site preassembled from articles, materials, or
> supplies. However, emergency life safety systems, such as emergency
> lighting, fire alarm, and audio evacuation systems, that are discrete
> systems incorporated into a public building or work and that are
> produced as complete systems, are evaluated as a single and distinct
> construction material regardless of when or how the individual parts
> or components of those systems are delivered to the construction site.
> Materials purchased directly by the Government are supplies, not
> construction material.
>
> "Cost of components" means---

(1) For components purchased by the Contractor, the acquisition cost,
    including transportation costs to the place of incorporation into
    the construction material (whether or not such costs are paid to a
    domestic firm), and any applicable duty (whether or not a duty-free
    entry certificate is issued); or

(2) For components manufactured by the Contractor, all costs associated
    with the manufacture of the component, including transportation
    costs as described in paragraph (1) of this definition, plus
    allocable overhead costs, but excluding profit. Cost of components
    does not include any costs associated with the manufacture of the
    construction material.

> "Domestic construction material" means --

(1) An unmanufactured construction material mined or produced in the
    United States; or

(2) A construction material manufactured in the United States, if the
    cost of its components mined, produced, or manufactured in the
    United States exceeds 50 percent of the cost of all its components.
    Components of foreign origin of the same class or kind for which
    nonavailability determinations have been made are treated as
    domestic.

> "Foreign construction material" means a construction material other
> than a domestic construction material.
>
> "United States" means the 50 States, the District of Columbia, and
> outlying areas.

(b) Domestic preference.

```{=html}
<!-- -->
```
(1) This clause implements the Buy American Act (41 U.S.C. 10a - 10d) by
    providing a preference for domestic construction material. The
    Contractor shall use only domestic construction material in
    performing this contract, except as provided in paragraphs (b)(2)
    and (b)(3) of this clause.

(2) This requirement does not apply to the construction material or
    components listed by the Government as follows:\
    \_\_\_\_\_\_[N/A]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

(3) The Contracting Officer may add other foreign construction material
    to the list in paragraph (b)(2) of this clause if the Government
    determines that --

```{=html}
<!-- -->
```
(i) The cost of domestic construction material would be unreasonable.
    The cost of a particular domestic construction material subject to
    the requirements of the Buy American Act is unreasonable when the
    cost of such material exceeds the cost of foreign material by more
    than 6 percent;

(ii) The application of the restriction of the Buy American Act to a
     particular construction material would be impracticable or
     inconsistent with the public interest; or

(iii) The construction material is not mined, produced, or manufactured
      in the United States in sufficient and reasonably available
      commercial quantities of a satisfactory quality.

```{=html}
<!-- -->
```
(c) Request for determination of inapplicability of the Buy American
    Act.

```{=html}
<!-- -->
```
(1) \(i\) Any Contractor request to use foreign construction material in
    accordance with paragraph (b)(3) of this clause shall include
    adequate information for Government evaluation of the request,
    including --

```{=html}
<!-- -->
```
(A) A description of the foreign and domestic construction materials;

(B) Unit of measure;

(C) Quantity;

(D) Price;

(E) Time of delivery or availability;

(F) Location of the construction project;

(G) Name and address of the proposed supplier; and

(H) A detailed justification of the reason for use of foreign
    construction materials cited in accordance with paragraph (b)(3) of
    this clause.

```{=html}
<!-- -->
```
(ii) A request based on unreasonable cost shall include a reasonable
     survey of the market and a completed price comparison table in the
     format in paragraph (d) of this clause.

(iii) The price of construction material shall include all delivery
      costs to the construction site and any applicable duty (whether or
      not a duty-free certificate may be issued).

(iv) Any Contractor request for a determination submitted after contract
     award shall explain why the Contractor could not reasonably foresee
     the need for such determination and could not have requested the
     determination before contract award. If the Contractor does not
     submit a satisfactory explanation, the Contracting Officer need not
     make a determination.

```{=html}
<!-- -->
```
(2) If the Government determines after contract award that an exception
    to the Buy American Act applies and the Contracting Officer and the
    Contractor negotiate adequate consideration, the Contracting Officer
    will modify the contract to allow use of the foreign construction
    material. However, when the basis for the exception is the
    unreasonable price of a domestic construction material, adequate
    consideration is not less than the differential established in
    paragraph (b)(3)(i) of this clause.

(3) Unless the Government determines that an exception to the Buy
    American Act applies, use of foreign construction material is
    noncompliant with the Buy American Act.

```{=html}
<!-- -->
```
(d) Data. To permit evaluation of requests under paragraph (c) of this
    clause based on unreasonable cost, the Contractor shall include the
    following information and any applicable supporting data based on
    the survey of suppliers:

FOREIGN AND DOMESTIC CONSTRUCTION MATERIALS PRICE COMPARISON

  ---------------------------------------- ---------------------- ---------------------- ----------------------
  Construction Material Description        Unit of Measure        Quantity               Price (Dollars)\*

  *Item 1:*                                                                              

  Foreign construction material            \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_

  Domestic construction material           \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_

                                                                                         

  *Item 2:*                                                                              

  Foreign construction material            \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_

  Domestic construction material           \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_
  ---------------------------------------- ---------------------- ---------------------- ----------------------

\[List name, address, telephone number, and contact for suppliers
surveyed. Attach copy of response; if oral, attach summary.\]

\[Include other applicable supporting information.\]

\[\* Include all delivery costs to the construction site and any
applicable duty (whether or not a duty-free entry certificate is
issued).\]

(End of clause)

(a) 

```{=html}
<!-- -->
```
(1) 
(2) 

```{=html}
<!-- -->
```
(1) 
(2) 

```{=html}
<!-- -->
```
(b) 

```{=html}
<!-- -->
```
(1) 
(2) 
(3) 

```{=html}
<!-- -->
```
(i) 
(ii) 
(iii) 

```{=html}
<!-- -->
```
(c) 

```{=html}
<!-- -->
```
(1) 

```{=html}
<!-- -->
```
(A) 
(B) 
(C) 
(D) 
(E) 
(F) 
(G) 
(H) 

```{=html}
<!-- -->
```
(ii) 
(iii) 
(iv) 

```{=html}
<!-- -->
```
(2) 
(3) 

```{=html}
<!-- -->
```
(d) 

  ---------------------------------------- ---------- ---------- ----------
                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 
  ---------------------------------------- ---------- ---------- ----------

I.19 [BUY AMERICAN ACT\--CONSTRUCTION MATERIALS UNDER TRADE AGREEMENTS
(52.225-11) (NOV 2006)]{.underline}

\[This clause applies only to facilities-related effort in this
contract.\]

(a) Definitions. As used in this clause --

> "Caribbean Basin country construction material" means a construction
> material that---

(1) Is wholly the growth, product, or manufacture of a Caribbean Basin
    country; or

(2) In the case of a construction material that consists in whole or in
    part of materials from another country, has been substantially
    transformed in a Caribbean Basin country into a new and different
    construction material distinct from the materials from which it was
    transformed.

> "Component" means an article, material, or supply incorporated
> directly into a construction material.
>
> "Construction material" means an article, material, or supply brought
> to the construction site by the Contractor or subcontractor for
> incorporation into the building or work. The term also includes an
> item brought to the site preassembled from articles, materials, or
> supplies. However, emergency life safety systems, such as emergency
> lighting, fire alarm, and audio evacuation systems, that are discrete
> systems incorporated into a public building or work and that are
> produced as complete systems, are evaluated as a single and distinct
> construction material regardless of when or how the individual parts
> or components of those systems are delivered to the construction site.
> Materials purchased directly by the Government are supplies, not
> construction material.
>
> "Cost of components" means --

(1) For components purchased by the Contractor, the acquisition cost,
    including transportation costs to the place of incorporation into
    the construction material (whether or not such costs are paid to a
    domestic firm), and any applicable duty (whether or not a duty-free
    entry certificate is issued); or

(2) For components manufactured by the Contractor, all costs associated
    with the manufacture of the component, including transportation
    costs as described in paragraph (1) of this definition, plus
    allocable overhead costs, but excluding profit. Cost of components
    does not include any costs associated with the manufacture of the
    construction material.

> "Designated country" means any of the following countries:

(1) A World Trade Organization Government Procurement Agreement country
    (Aruba, Austria, Belgium, Canada, Cyprus, Czech Republic, Denmark,
    Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary,
    Iceland, Ireland, Israel, Italy, Japan, Korea (Republic of), Latvia,
    Liechtenstein, Lithuania, Luxembourg, Malta, Netherlands, Norway,
    Poland, Portugal, Singapore, Slovak Republic, Slovenia, Spain,
    Sweden, Switzerland, or United Kingdom);

(2) A Free Trade Agreement country (Australia, Bahrain, Canada, Chile,
    El Salvador, Guatemala, Honduras, Mexico, Morocco, Nicaragua, or
    Singapore);

(3) A least developed country (Afghanistan, Angola, Bangladesh, Benin,
    Bhutan, Burkina Faso, Burundi, Cambodia, Cape Verde, Central African
    Republic, Chad, Comoros, Democratic Republic of Congo, Djibouti,
    East Timor, Equatorial Guinea, Eritrea, Ethiopia, Gambia, Guinea,
    Guinea-Bissau, Haiti, Kiribati, Laos, Lesotho, Madagascar, Malawi,
    Maldives, Mali, Mauritania, Mozambique, Nepal, Niger, Rwanda, Samoa,
    Sao Tome and Principe, Senegal, Sierra Leone, Solomon Islands,
    Somalia, Tanzania, Togo, Tuvalu, Uganda, Vanuatu, Yemen, or Zambia);
    or

(4) A Caribbean Basin country (Antigua and Barbuda, Aruba, Bahamas,
    Barbados, Belize, British Virgin Islands, Costa Rica, Dominica,
    Dominican Republic, Grenada, Guyana, Haiti, Jamaica, Montserrat,
    Netherlands Antilles, St. Kitts and Nevis, St. Lucia, St. Vincent
    and the Grenadines, or Trinidad and Tobago).

> "Designated country construction material" means a construction
> material that is a WTO GPA country construction material, an FTA
> country construction material, a least developed country construction
> material, or a Caribbean Basin country construction material.
>
> "Domestic construction material" means---

(1) An unmanufactured construction material mined or produced in the
    United States; or

(2) A construction material manufactured in the United States, if the
    cost of its components mined, produced, or manufactured in the
    United States exceeds 50 percent of the cost of all its components.
    Components of foreign origin of the same class or kind for which
    nonavailability determinations have been made are treated as
    domestic.

> "Foreign construction material" means a construction material other
> than a domestic construction material.
>
> "Free Trade Agreement country construction material" means a
> construction material that --

(1) Is wholly the growth, product, or manufacture of a Free Trade
    Agreement (FTA) country; or

(2) In the case of a construction material that consists in whole or in
    part of materials from another country, has been substantially
    transformed in a FTA country into a new and different construction
    material distinct from the materials from which it was transformed.

> "Least developed country construction material" means a construction
> material that --

(1) Is wholly the growth, product, or manufacture of a least developed
    country; or

(2) In the case of a construction material that consists in whole or in
    part of materials from another country, has been substantially
    transformed in a least developed country into a new and different
    construction material distinct from the materials from which it was
    transformed.

> "United States" means the 50 States, the District of Columbia, and
> outlying areas.
>
> "WTO GPA country construction material" means a construction material
> that --

(1) Is wholly the growth, product, or manufacture of a WTO GPA country;
    or

(2) In the case of a construction material that consists in whole or in
    part of materials from another country, has been substantially
    transformed in a WTO GPA country into a new and different
    construction material distinct from the materials from which it was
    transformed.

```{=html}
<!-- -->
```
(b) Construction materials.

```{=html}
<!-- -->
```
(1) This clause implements the Buy American Act (41 U.S.C. 10a-10d) by
    providing a preference for domestic construction material. In
    addition, the Contracting Officer has determined that the WTO GPA
    and Free Trade Agreements (FTAs) apply to this acquisition.
    Therefore, the Buy American Act restrictions are waived for
    designated country construction materials.

(2) The Contractor shall use only domestic , or designated country
    construction material in performing this contract, except as
    provided in paragraphs (b)(3) and (b)(4) of this clause.

(3) The requirement in paragraph (b)(2) of this clause does not apply to
    the construction materials or components listed by the Government as
    follows:\
    \_\_\_\_[N/A]{.underline}\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

(4) The Contracting Officer may add other foreign construction material
    to the list in paragraph (b)(3) of this clause if the Government
    determines that --

```{=html}
<!-- -->
```
(i) The cost of domestic construction material would be unreasonable.
    The cost of a particular domestic construction material subject to
    the restrictions of the Buy American Act is unreasonable when the
    cost of such material exceeds the cost of foreign material by more
    than 6 percent;

(ii) The application of the restriction of the Buy American Act to a
     particular construction material would be impracticable or
     inconsistent with the public interest; or

(iii) The construction material is not mined, produced, or manufactured
      in the United States in sufficient and reasonably available
      commercial quantities of a satisfactory quality.

```{=html}
<!-- -->
```
(c) Request for determination of inapplicability of the Buy American
    Act.

```{=html}
<!-- -->
```
(1) \(i\) Any Contractor request to use foreign construction material in
    accordance with paragraph (b)(4) of this clause shall include
    adequate information for Government evaluation of the request,
    including --

```{=html}
<!-- -->
```
(A) A description of the foreign and domestic construction materials;

(B) Unit of measure;

(C) Quantity;

(D) Price;

(E) Time of delivery or availability;

(F) Location of the construction project;

(G) Name and address of the proposed supplier; and

(H) A detailed justification of the reason for use of foreign
    construction materials cited in accordance with paragraph (b)(3) of
    this clause.

```{=html}
<!-- -->
```
(ii) A request based on unreasonable cost shall include a reasonable
     survey of the market and a completed price comparison table in the
     format in paragraph (d) of this clause.

(iii) The price of construction material shall include all delivery
      costs to the construction site and any applicable duty (whether or
      not a duty-free certificate may be issued).

(iv) Any Contractor request for a determination submitted after contract
     award shall explain why the Contractor could not reasonably foresee
     the need for such determination and could not have requested the
     determination before contract award. If the Contractor does not
     submit a satisfactory explanation, the Contracting Officer need not
     make a determination.

```{=html}
<!-- -->
```
(2) If the Government determines after contract award that an exception
    to the Buy American Act applies and the Contracting Officer and the
    Contractor negotiate adequate consideration, the Contracting Officer
    will modify the contract to allow use of the foreign construction
    material. However, when the basis for the exception is the
    unreasonable price of a domestic construction material, adequate
    consideration is not less than the differential established in
    paragraph (b)(4)(i) of this clause.

(3) Unless the Government determines that an exception to the Buy
    American Act applies, use of foreign construction material is
    noncompliant with the Buy American Act.

```{=html}
<!-- -->
```
(d) Data. To permit evaluation of requests under paragraph (c) of this
    clause based on unreasonable cost, the Contractor shall include the
    following information and any applicable supporting data based on
    the survey of suppliers:

FOREIGN AND DOMESTIC CONSTRUCTION MATERIALS PRICE COMPARISON

  ---------------------------------------- ---------------------- ---------------------- ----------------------
  Construction Material Description        Unit of Measure        Quantity               Price (Dollars)\*

  *Item 1:*                                                                              

  Foreign construction material            \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_

  Domestic construction material           \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_

                                                                                         

  *Item 2:*                                                                              

  Foreign construction material            \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_

  Domestic construction material           \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_   \_\_\_\_\_\_\_\_\_\_
  ---------------------------------------- ---------------------- ---------------------- ----------------------

\[List name, address, telephone number, and contact for suppliers
surveyed. Attach copy of response; if oral, attach summary.\]

\[Include other applicable supporting information.\]

\[\* Include all delivery costs to the construction site and any
applicable duty (whether or not a duty-free entry certificate is
issued).\]

(End of clause)

  ---------------------------------------- ---------- ---------- ----------
                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 
  ---------------------------------------- ---------- ---------- ----------

I.20 [PRICE ADJUSTMENT FOR \"MAKE-OR-BUY\" CHANGES (1852.215-79) (DEC
1988)]{.underline}

The following make-or-buy items are subject to the provisions of
paragraph (d) of the *Changes* or *Additions to Make-or-Buy Program*
clause of this contract:

  ----------------------------------- -----------------------------------
  [ITEM DESCRIPTION]{.underline}      [MAKE-OR-BUY
                                      DETERMINATION]{.underline}

  None                                
  ----------------------------------- -----------------------------------

(End of clause)

I.21 [RESERVED]{.underline}

(a) 
(b) 

I.22 [RESERVED]{.underline}

(a) 
(b) 

-   
-   
-   

(c) 

```{=html}
<!-- -->
```
(1) 

```{=html}
<!-- -->
```
(i) 
(ii) 
(iii) 

```{=html}
<!-- -->
```
(2) 

I.23 [RESERVED]{.underline}

(a) 

```{=html}
<!-- -->
```
(1) 
(2) 
(3) 

```{=html}
<!-- -->
```
(b) 
(c) 
(d) 

```{=html}
<!-- -->
```
(1) 
(2) 

```{=html}
<!-- -->
```
(i) 

```{=html}
<!-- -->
```
(A) 
(B) 

```{=html}
<!-- -->
```
(ii) 
(iii) 
(iv) 
(v) 
(vi) 

```{=html}
<!-- -->
```
(3) 

```{=html}
<!-- -->
```
(e) 
(f) 

```{=html}
<!-- -->
```
(1) 
(2) 

(END OF SECTION)

SECTION J

LIST OF ATTACHMENTS

  ----------- -----------------------------------------------------------
  J-1-A       STATEMENT OF WORK

  J-1-B       PERFORMANCE REQUIREMENTS SUMMARIES

  J-1-C       RESERVED

  J-1-D       RESERVED

  J-2         GLOSSARY, ACRONYMS, AND ABBREVIATIONS

  J-3         RESERVED

  J-4         RESERVED

  J-5         DATA REQUIREMENTS LIST/DRDs

  J-6         STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES

  J-7         WAGE DETERMINATIONS

  J-8         FEE PLAN

  J-9         GOVERNMENT FURNISHED PROPERTY

  J-10        INSTALLATION PROVIDED SERVICES

  J-11        APPLICABLE NASA POLICIES AND PROCEDURES

  J-12        RESERVED

  J-13        MAKE OR BUY PLAN

  J-14        SMALL BUSINESS SUBCONTRACTING PLAN

  J-15        RESERVED

  J-16        CONTINUOUS IMPROVEMENT PLAN FOR THE SPACE PROGRAM
              OPERATIONS CONTRACT (SPOC)

  J-17        CONTRACT SECURITY CLASSIFICATION SPECIFICATION

  J-18        NASA CENTER SPECIFIC CLAUSES

  J-19        PROVISIONING MANAGEMENT PLAN

  J-20        RESERVED

  J-21        FACILITIES AND ENVIRONMENTAL PROJECTS

  J-22        RESERVED

  J-23        STANDARDS, FOOD, AND SPECIFICATIONS LIST

  J-24        RESERVED

  J-25        RESERVED

  J-26        RESERVED

  J-27        RESERVED

  J-28        IDIQ EFFORT

  J-29        PERSONAL IDENTITY VERIFICATION (PIV) CARD ISSUANCE
              PROCEDURES
  ----------- -----------------------------------------------------------

**ATTACHMENT J-1-A**

**SPACE PROGRAM OPERATIONS CONTRACT**

**STATEMENT OF WORK**

1.0 SPACE PROGRAM OPERATIONS CONTRACT
[26](#space-program-operations-contract)

1.1 PROGRAM AND BUSINESS MANAGEMENT
[26](#program-and-business-management)

1.1.1 PROGRAM MANAGEMENT [26](#program-management)

**1.1.1.1** **PLANNING** [26](#planning)

**1.1.1.2** **MANAGEMENT REVIEWS** [26](#management-reviews)

1.1.1.2.1 CONTRACT MANAGEMENT REVIEWS [26](#contract-management-reviews)

1.1.1.2.2 PROGRAM REVIEWS [26](#program-reviews)

1.1.1.2.3 FLIGHT READINESS [26](#flight-readiness)

**1.1.1.3** **RESERVED** [26](#reserved)

**1.1.1.4** **RISK MANAGEMENT** [26](#risk-management)

**1.1.1.5** **NEW TECHNOLOGY** [26](#new-technology)

1.1.2 FINANCIAL RESOURCES AND PERFORMANCE MANAGEMENT
[26](#financial-resources-and-performance-management)

**1.1.2.1** **FINANCIAL RESOURCES MANAGEMENT**
[26](#financial-resources-management)

**1.1.2.2** **PERFORMANCE MEASUREMENT** [26](#performance-measurement)

1.1.3 CONTRACT MANAGEMENT [26](#contract-management)

**1.1.3.1** **PRIME CONTRACT MANAGEMENT**
[26](#prime-contract-management)

**1.1.3.2** **SUBCONTRACT MANAGEMENT** [26](#subcontract-management)

1.1.4 INFORMATION AND DOCUMENT MANAGEMENT
[26](#information-and-document-management)

**1.1.4.1** **INFORMATION MANAGEMENT** [26](#information-management)

**1.1.4.2** **DOCUMENT MANAGEMENT** [26](#document-management)

**1.1.4.3** **RESERVED** [26](#reserved-1)

1.1.5 CONFIGURATION AND VERIFICATION MANAGEMENT
[26](#configuration-and-verification-management)

**1.1.5.1** **CONFIGURATION MANAGEMENT** [26](#configuration-management)

**1.1.5.2** **VERIFICATION MANAGEMENT** [26](#verification-management)

1.1.5.2.1 PROGRAM VERIFICATION MANAGEMENT
[26](#program-verification-management)

1.1.5.2.2 ORBITER AND COMBINED ELEMENT VERIFICATION MANAGEMENT
[26](#orbiter-and-combined-element-verification-management)

1.1.6 GOVERNMENT FACILITY, PROPERTY AND SECURITY MANAGEMENT
[26](#government-facility-property-and-security-management)

**1.1.6.1** **FACILITY MANAGEMENT** [26](#facility-management)

**1.1.6.2** **PROPERTY MANAGEMENT** [26](#property-management)

**1.1.6.3** **SECURITY AND TECHNOLOGY PROTECTION MANAGEMENT**
[26](#security-and-technology-protection-management)

1.1.7 FLIGHT INTEGRATION, MANIFEST AND SCHEDULES
[26](#flight-integration-manifest-and-schedules)

**1.1.7.1** **FLIGHT INTEGRATION** [26](#flight-integration)

**1.1.7.2** **MANIFESTS AND SCHEDULES** [26](#manifests-and-schedules)

1.1.8 TECHNICAL INFORMATION SYSTEMS MANAGEMENT
[26](#technical-information-systems-management)

1.2 SYSTEM AND CARGO ENGINEERING AND INTEGRATION
[26](#system-and-cargo-engineering-and-integration)

1.2.1 ENGINEERING INTEGRATION AND ANALYSIS
[26](#engineering-integration-and-analysis)

**1.2.1.1** **SSV POST FLIGHT ANALYSIS** [26](#ssv-post-flight-analysis)

**1.2.1.2** **ASCENT MARGINS AND FLIGHT READINESS ASSESSMENT**
[26](#ascent-margins-and-flight-readiness-assessment)

**1.2.1.3** **CARGO INTEGRATION ENGINEERING ANALYSIS**
[26](#cargo-integration-engineering-analysis)

1.2.1.3.1 COMPATIBILITY ASSESSMENTS [26](#compatibility-assessments)

1.2.1.3.2 MATH MODELS [26](#math-models)

1.2.1.3.3 STRUCTURAL VERIFICATION ANALYSIS
[26](#structural-verification-analysis)

1.2.1.3.4 THERMAL VERIFICATION ANALYSIS
[26](#thermal-verification-analysis)

1.2.1.3.5 AVIONICS ANALYSES [26](#avionics-analyses)

1.2.1.3.6 EME ANALYSES [26](#eme-analyses)

1.2.1.3.7 PAYLOAD/CARGO SAFETY ANALYSES
[26](#payloadcargo-safety-analyses)

**1.2.1.4** **CARGO INTEGRATION HARDWARE**
[26](#cargo-integration-hardware)

1.2.1.4.1 CARGO INTEGRATION HARDWARE LOGISTICS
[26](#cargo-integration-hardware-logistics)

1.2.1.4.2 CARGO INTEGRATION HARDWARE MISSION KITS
[26](#cargo-integration-hardware-mission-kits)

**1.2.1.5** **RECONFIGURATION ENGINEERING**
[26](#reconfiguration-engineering)

**1.2.1.6** **DOLILU OPERATIONS SUPPORT SYSTEM (DOSS) CONFIGURATION AND
DATABASE MAINTENANCE**
[26](#dolilu-operations-support-system-doss-configuration-and-database-maintenance)

**1.2.1.7** **SHUTTLE SYSTEMS ENGINEERING ANALYSIS**
[26](#shuttle-systems-engineering-analysis)

1.2.2 SYSTEM AND CARGO INTEGRATION [26](#system-and-cargo-integration)

**1.2.2.1** **INTEGRATED MASS PROPERTIES**
[26](#integrated-mass-properties)

**1.2.2.2** **TRAJECTORY DESIGN DATA PACKAGES (TDDP)**
[26](#trajectory-design-data-packages-tddp)

**1.2.2.3** **RESERVED** [26](#reserved-2)

**1.2.2.4** **INTEGRATION PLAN (IP) ANNEX 1**
[26](#integration-plan-ip-annex-1)

**1.2.2.5** **PROGRAM INTERFACE CONTROL DOCUMENT (ICD)/INTERFACE
DEFINITION DOCUMENTS (IDD)**
[26](#program-interface-control-document-icdinterface-definition-documents-idd)

1.2.2.5.1 SYSTEMS INTEGRATION ICDs [26](#systems-integration-icds)

1.2.2.5.2 CARGO INTEGRATION ICDs/IDDs [26](#cargo-integration-icdsidds)

**1.2.2.6** **PAYLOAD UNIQUE ICDs** [26](#payload-unique-icds)

**1.2.2.7** **PAYLOAD TEST AND HANDLING REQUIREMENTS**
[26](#payload-test-and-handling-requirements)

1.2.2.7.1 PAYLOAD OPERATIONS AND MAINTENANCE REQUIREMENTS AND
SPECIFICATIONS (OMRS)
[26](#payload-operations-and-maintenance-requirements-and-specifications-omrs)

1.2.2.7.2 PAYLOAD TIME CRITICAL GROUND HANDLING REQUIREMENTS (TGHR)
[26](#payload-time-critical-ground-handling-requirements-tghr)

**1.2.2.8** **TECHNICAL INTEGRATION ANALYSES**
[26](#technical-integration-analyses)

**1.2.2.9** **RESERVED** [26](#reserved-3)

**1.2.2.10** **INTEGRATED AVIONICS AND ELECTROMAGNETIC EFFECTS**
[26](#integrated-avionics-and-electromagnetic-effects)

1.2.2.10.1 INTEGRATED VEHICLE AVIONICS
[26](#integrated-vehicle-avionics)

1.2.2.10.2 ELECTROMAGNETIC EFFECTS (EME)
[26](#electromagnetic-effects-eme)

**1.2.2.11** **SSV DATABOOKS** [26](#ssv-databooks)

**1.2.2.12** **SYSTEMS INTEGRATION FLIGHT SUPPORT**
[26](#systems-integration-flight-support)

1.2.3 ELEMENT INTEGRATION [26](#element-integration)

1.2.4 SYSTEM ENGINEERING [26](#system-engineering)

**1.2.4.1** **ANOMALY INTEGRATION AND RESOLUTION**
[26](#anomaly-integration-and-resolution)

**1.2.4.2** **PROGRAM REQUIREMENTS MANAGEMENT**
[26](#program-requirements-management)

1.2.5 MSFC PROJECT INTEGRATION [26](#msfc-project-integration)

**1.2.5.1** **PROJECT SYSTEMS INTEGRATION**
[26](#project-systems-integration)

**1.2.5.2** **PROJECT ENGINEERING** [26](#project-engineering)

**1.2.5.3** **RESERVED** [26](#reserved-4)

**1.2.5.4** **PROJECT CONFIGURATION MANAGEMENT**
[26](#project-configuration-management)

**1.2.5.5** **PROJECT INFORMATION INTEGRATION**
[26](#project-information-integration)

1.3 SAFETY, RELIABILITY, QUALITY, MISSION ASSURANCE, AND ENVIRONMENTAL
MANAGEMENT
[26](#safety-reliability-quality-mission-assurance-and-environmental-management)

1.3.1 SAFETY [26](#safety)

**1.3.1.1** **SYSTEMS SAFETY** [26](#systems-safety)

**1.3.1.2** **OCCUPATIONAL SAFETY** [26](#occupational-safety)

1.3.2 RELIABILITY AND MAINTAINABILITY
[26](#reliability-and-maintainability)

**1.3.2.1** **FAILURE MODES AND EFFECTS ANALYSIS AND CRITICAL ITEMS LIST
(FMEA/CIL)**
[26](#failure-modes-and-effects-analysis-and-critical-items-list-fmeacil)

1.3.2.1.1 FMEA [26](#fmea)

1.3.2.1.2 CRITICAL ITEMS LIST [26](#critical-items-list)

**1.3.2.2** **MAINTAINABILITY** [26](#maintainability)

1.3.3 QUALITY ASSURANCE [26](#quality-assurance)

**1.3.3.1** **PRODUCT AND SERVICE QUALITY**
[26](#product-and-service-quality)

**1.3.3.2** **PROCESS QUALITY** [26](#process-quality)

1.3.4 ENVIRONMENTAL MANAGEMENT [26](#environmental-management)

**1.3.4.1** **GENERAL REQUIREMENTS** [26](#general-requirements)

**1.3.4.2** **RESERVED** [26](#reserved-5)

1.4 FLIGHT ELEMENTS [26](#flight-elements)

1.4.1 ORBITER [26](#orbiter)

**1.4.1.1** **MISSION AND TURNAROUND REQUIREMENTS**
[26](#mission-and-turnaround-requirements)

1.4.1.1.1 RESERVED [26](#reserved-6)

1.4.1.1.2 RESERVED [26](#reserved-7)

**1.4.1.2** **ORBITER LOGISTICS** [26](#orbiter-logistics)

**1.4.1.3** **ORBITER TURNAROUND PROCESSING**
[26](#orbiter-turnaround-processing)

**1.4.1.4** **ORBITER FERRY OPERATIONS** [26](#orbiter-ferry-operations)

**1.4.1.5** **ORBITER HARDWARE PRODUCTION AND SUPPORT TASKS**
[26](#orbiter-hardware-production-and-support-tasks)

1.4.1.5.1 RESERVED [26](#reserved-8)

1.4.1.5.2 HARDWARE, MODIFICATIONS, AND SUPPORT
[26](#hardware-modifications-and-support)

1.4.1.5.2.1 RESERVED [26](#reserved-9)

1.4.1.5.3 RESERVED [26](#reserved-10)

1.4.1.5.4 RESERVED [26](#reserved-11)

1.4.1.5.5 RESERVED [26](#reserved-12)

1.4.1.5.6 GROUND SUPPORT EQUIPMENT AND TOOLING SUPPORT
[26](#ground-support-equipment-and-tooling-support)

1.4.1.5.7 ORBITER STRUCTURES IMPROVEMENTS
[26](#orbiter-structures-improvements)

1.4.1.5.8 THERMAL PROTECTION SYSTEM (TPS) SUPPORT
[26](#thermal-protection-system-tps-support)

1.4.1.5.9 HARDWARE STUDIES [26](#hardware-studies)

1.4.1.5.10 ORBITER CREW SYSTEMS EQUIPMENT
[26](#orbiter-crew-systems-equipment)

**1.4.1.6** **ISS TECHNICAL INTEGRATION SUPPORT TO STATION APDS**
[26](#iss-technical-integration-support-to-station-apds)

1.4.2 SOLID ROCKET BOOSTER (SRB) [26](#solid-rocket-booster-srb)

**1.4.2.1** **SRB ELEMENT PROCESSING** [26](#srb-element-processing)

1.4.2.1.1 RESERVED [26](#reserved-13)

**1.4.2.2** **SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT**
[26](#srb-hardwaresystems-assembly-and-refurbishment)

1.4.2.2.1 RESERVED [26](#reserved-14)

**1.4.2.3** **SRB STAND ALONE LOGISTICS**
[26](#srb-stand-alone-logistics)

1.4.2.3.1 RESERVED [26](#reserved-15)

**1.4.2.4** **RESERVED** [26](#reserved-16)

**1.4.2.5** **SRB FLIGHT SYSTEMS DESIGN RESPONSIBILITY**
[26](#srb-flight-systems-design-responsibility)

1.4.2.5.1 RESERVED [26](#reserved-17)

1.4.2.5.2 RESERVED [26](#reserved-18)

1.4.2.5.3 RESERVED [26](#reserved-19)

1.4.2.5.4 RESERVED [26](#reserved-20)

**1.4.2.6** **SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT PROCESSING
FACILITIES AND GROUND SYSTEMS DESIGN RESPONSIBILITY**
[26](#srb-hardwaresystems-assembly-and-refurbishment-processing-facilities-and-ground-systems-design-responsibility)

**1.4.2.7** **RESERVED** [26](#reserved-21)

**1.4.2.8** **SRB RECOVERY OPERATIONS AND ET TRANSPORTATION**
[26](#srb-recovery-operations-and-et-transportation)

**1.4.2.9** **RSRM STATIC FIRING SUPPORT**
[26](#rsrm-static-firing-support)

**1.4.2.10** **SRB MODIFICATIONS** [26](#srb-modifications)

**1.4.2.11** **SRB FACILITY TOOLING, EQUIPMENT, AND MINOR CONSTRUCTION,
ALTERATION, AND REPAIR (MCAR)**
[26](#srb-facility-tooling-equipment-and-minor-construction-alteration-and-repair-mcar)

**1.4.2.12** **ACQUISITION SUPPORT** [26](#acquisition-support)

1.4.3 FLIGHT SOFTWARE [26](#flight-software)

**1.4.3.1** **ORBITER AND BFS FLIGHT SOFTWARE PROCESSING AND TOOLS**
[26](#orbiter-and-bfs-flight-software-processing-and-tools)

**1.4.3.2** **FLIGHT SOFTWARE TESTING** [26](#flight-software-testing)

**1.4.3.3** **AVIONICS AND SOFTWARE SYSTEM SUPPORT**
[26](#avionics-and-software-system-support)

**1.4.3.4** **BFS FLIGHT SOFTWARE RECONFIGURATION**
[26](#bfs-flight-software-reconfiguration)

**1.4.3.5** **BFS FLIGHT SOFTWARE MODIFICATIONS**
[26](#bfs-flight-software-modifications)

**1.4.3.6** **FLIGHT OPERATIONS SUPPORT**
[26](#flight-operations-support)

**1.4.3.7** **PASS FLIGHT SOFTWARE PROCESSING**
[26](#pass-flight-software-processing)

**1.4.3.8** **PASS FLIGHT SOFTWARE TOOLS**
[26](#pass-flight-software-tools)

**1.4.3.9** **PASS FLIGHT SOFTWARE IMPLEMENTATION**
[26](#pass-flight-software-implementation)

**1.4.3.10** **PASS FLIGHT SOFTWARE RECONFIGURATION AND MMU
INTEGRATION**
[26](#pass-flight-software-reconfiguration-and-mmu-integration)

**1.4.3.11** **GROUND FACILITY DATA PROCESSING SYSTEM**
[26](#ground-facility-data-processing-system)

**1.4.3.12** **PASS FLIGHT SOFTWARE MAINTENANCE**
[26](#pass-flight-software-maintenance)

**1.4.3.13** **MEDS MODIFICATION AND MAINTENANCE**
[26](#meds-modification-and-maintenance)

**1.4.3.14** **MEDS SOFTWARE TEST AND OPERATIONS SUPPORT**
[26](#meds-software-test-and-operations-support)

**1.4.3.15** **PORTABLE COMPUTER SOFTWARE SYSTEMS FOR SPACEFLIGHT**
[26](#portable-computer-software-systems-for-spaceflight)

**1.4.3.16** **VEHICLE AND PAYLOAD DATA COLLECTION/ RECONFIGURATION**
[26](#vehicle-and-payload-data-collection-reconfiguration)

**1.4.3.17** **SHUTTLE AVIONICS INTEGRATION LABORATORY (SAIL)**
[26](#shuttle-avionics-integration-laboratory-sail)

**1.4.3.18** **MINIATURE AIRBORNE GLOBAL POSITIONING SYSTEM (GPS)
RECEIVER SHUTTLE -- 3 STRING (MAGRS-3S)**
[26](#miniature-airborne-global-positioning-system-gps-receiver-shuttle-3-string-magrs-3s)

1.4.4 EXTERNAL TANK (ET) [26](#external-tank-et)

**1.4.4.1** **ET ELEMENT PROCESSING** [26](#et-element-processing)

**1.4.4.2** **ET LOGISTICS** [26](#et-logistics)

**1.4.4.3** **RESERVED** [26](#reserved-22)

**1.4.4.4** **RESERVED** [26](#reserved-23)

**1.4.4.5** **ET MODIFICATIONS** [26](#et-modifications)

**1.4.4.6** **RESERVED** [26](#reserved-24)

**1.4.4.7** **RESERVED** [26](#reserved-25)

1.4.5 REUSABLE SOLID ROCKET MOTOR (RSRM)
[26](#reusable-solid-rocket-motor-rsrm)

**1.4.5.1** **RSRM ELEMENT PROCESSING** [26](#rsrm-element-processing)

**1.4.5.2** **RSRM LOGISTICS** [26](#rsrm-logistics)

**1.4.5.3** **RSRM RECOVERY OPERATIONS** [26](#rsrm-recovery-operations)

**1.4.5.4** **RESERVED** [26](#reserved-26)

**1.4.5.5** **RSRM MODIFICATIONS** [26](#rsrm-modifications)

**1.4.5.6** **RESERVED** [26](#reserved-27)

**1.4.5.7** **RESERVED** [26](#reserved-28)

1.4.6 SPACE SHUTTLE MAIN ENGINE (SSME)
[26](#space-shuttle-main-engine-ssme)

**1.4.6.1** **SSME ELEMENT PROCESSING** [26](#ssme-element-processing)

**1.4.6.2** **SSME LOGISTICS** [26](#ssme-logistics)

**1.4.6.3** **SSME LANDING OPERATIONS** [26](#ssme-landing-operations)

**1.4.6.4** **RESERVED** [26](#reserved-29)

**1.4.6.5** **SSME MODIFICATIONS** [26](#ssme-modifications)

**1.4.6.6** **RESERVED** [26](#reserved-30)

**1.4.6.7** **RESERVED** [26](#reserved-31)

1.4.7 SHUTTLE REMOTE MANIPULATOR SYSTEM (SRMS) & ORBITER BOOM SENSOR
SYSTEM (OBSS) PROCESSING
[26](#shuttle-remote-manipulator-system-srms-orbiter-boom-sensor-system-obss-processing)

1.4.8 RESERVED [26](#reserved-32)

1.4.9 FLIGHT CREW EQUIPMENT [26](#__RefHeading___Toc147280486)

**1.4.9.1** **RESERVED** [26](#reserved-33)

**1.4.9.2** **RESERVED** [26](#reserved-34)

**1.4.9.3** **RESERVED** [26](#reserved-35)

1.4.9.3.1 RESERVED [26](#reserved-36)

**1.4.9.4** **RESERVED** [26](#reserved-37)

1.5 INTEGRATED LAUNCH & LANDING OPERATIONS
[26](#integrated-launch-landing-operations)

1.5.1 VEHICLE INTEGRATION [26](#vehicle-integration)

**1.5.1.1** **ELEMENT/CARGO PLANNING & INTEGRATION**
[26](#elementcargo-planning-integration)

**1.5.1.2** **PAYLOAD INSTALLATION AND TESTING**
[26](#payload-installation-and-testing)

**1.5.1.3** **INTEGRATED TEST EXECUTION**
[26](#integrated-test-execution)

1.5.2 LAUNCH PREPARATIONS [26](#launch-preparations)

**1.5.2.1** **LAUNCH REQUIREMENTS** [26](#launch-requirements)

**1.5.2.2** **LAUNCH PLANNING** [26](#launch-planning)

**1.5.2.3** **LAUNCH TEAM TRAINING** [26](#launch-team-training)

**1.5.2.4** **LAUNCH READINESS** [26](#launch-readiness)

1.5.3 LAUNCH EXECUTION [26](#launch-execution)

**1.5.3.1** **RESERVED** [26](#reserved-38)

**1.5.3.2** **LAUNCH OPERATIONS** [26](#launch-operations)

1.5.4 POST LAUNCH [26](#post-launch)

**1.5.4.1** **INTEGRATED LANDING OPERATIONS**
[26](#integrated-landing-operations)

**1.5.4.2** **MISSION SUPPORT** [26](#mission-support)

**1.5.4.3** **PAYLOAD ELEMENT REMOVAL** [26](#payload-element-removal)

**1.5.4.4** **RESERVED** [26](#reserved-39)

1.5.5 SYSTEMS, FACILITIES AND EQUIPMENT
[26](#systems-facilities-and-equipment)

**1.5.5.1** **OPERATIONS** [26](#operations)

**1.5.5.3** **SUSTAINING ENGINEERING** [26](#sustaining-engineering)

**1.5.5.4** **LOGISTICS** [26](#logistics)

1.5.5.4.1 ACQUISITION [26](#acquisition)

1.5.5.4.2 MATERIAL MANAGEMENT [26](#material-management)

1.5.5.4.3 SUPPORT [26](#support)

1.5.6 COLUMBIA DEBRIS RECOVERY AND LONG TERM PRESERVATION
[26](#columbia-debris-recovery-and-long-term-preservation)

1.5.7 INFRASTRUCTURE REVITALIZATION [26](#infrastructure-revitalization)

1.5.8 ENERGY MANAGEMENT [26](#energy-management)

1.6 FLIGHT OPERATIONS [26](#flight-operations)

1.6.1 TRAINING [26](#training)

**1.6.1.1** **TRAINING MANAGEMENT** [26](#training-management)

1.6.1.1.1 TRAINING RECORDS [26](#training-records)

1.6.1.1.2 CURRICULUM AND LESSON DEVELOPMENT
[26](#curriculum-and-lesson-development)

1.6.1.1.3 TRAINING SCHEDULING [26](#training-scheduling)

1.6.1.1.4 INSTRUCTORS [26](#instructors)

**1.6.1.2** **FLIGHT CONTROLLER TRAINING**
[26](#flight-controller-training)

**1.6.1.3** **FLIGHT CREW TRAINING** [26](#flight-crew-training)

**1.6.1.4** **FLIGHT TRAINING HARDWARE** [26](#flight-training-hardware)

1.6.2 FLIGHT PREPARATION [26](#flight-preparation)

**1.6.2.1** **OPERATIONS DOCUMENTATION/FLIGHT DATA FILE (FDF)**
[26](#operations-documentationflight-data-file-fdf)

1.6.2.1.1 RESERVED [26](#reserved-40)

1.6.2.1.2 OPERATIONS DOCUMENTATION [26](#operations-documentation)

1.6.2.1.3 FLIGHT DATA FILE AND OPERATIONS DATA FILE (ODF)
[26](#flight-data-file-and-operations-data-file-odf)

**1.6.2.2** **FLIGHT DESIGN** [26](#flight-design)

1.6.2.2.1 FLIGHT DESIGN REQUIREMENTS [26](#flight-design-requirements)

1.6.2.2.2 FLIGHT DESIGN PRODUCTS [26](#flight-design-products)

1.6.2.2.3 FLIGHT DESIGN SOFTWARE [26](#flight-design-software)

**1.6.2.3** **FLIGHT PLANNING** [26](#flight-planning)

**1.6.2.4** **CARGO INTEGRATION** [26](#cargo-integration)

**1.6.2.5** **FLIGHT CREW** [26](#flight-crew)

1.6.2.5.1 PROGRAM REQUIREMENTS DEVELOPMENT/CHANGE TECHNICAL ASSESSMENTS
[26](#program-requirements-developmentchange-technical-assessments)

1.6.2.5.2 SHUTTLE TRAINING AIRCRAFT SUPPORT
[26](#shuttle-training-aircraft-support)

1.6.2.5.3 EXPEDITION CREW SUPPORT [26](#expedition-crew-support)

1.6.2.5.4 FLIGHT CREW EQUIPMENT (FCE) INTEGRATION
[26](#flight-crew-equipment-fce-integration)

1.6.2.5.5 OPERATIONS DEVELOPMENT FOR ISS
[26](#operations-development-for-iss)

1.6.2.5.5.1 FLIGHT CREW TRAINING DEVELOPMENT
[26](#flight-crew-training-development)

1.6.2.5.5.2 RESERVED [26](#reserved-41)

1.6.2.5.5.3 ISS ASSEMBLY, SYSTEM AND UTILIZATION OPERATIONS ASSESSMENT
AND TESTING
[26](#iss-assembly-system-and-utilization-operations-assessment-and-testing)

1.6.2.5.5.4 RESERVED [26](#reserved-42)

1.6.2.5.5.5 COMMON DISPLAY DEVELOPMENT [26](#common-display-development)

1.6.2.5.5.6 RESERVED [26](#reserved-43)

1.6.2.5.5.7 RESERVED [26](#reserved-44)

1.6.2.5.6 SHUTTLE/ISS INTEGRATION [26](#shuttleiss-integration)

1.6.2.5.7 LIBRARY, DATABASE, AND DOCUMENTATION MAINTENANCE
[26](#library-database-and-documentation-maintenance)

**1.6.2.6** **CREW/VEHICLE INTEGRATION AND TESTING**
[26](#crewvehicle-integration-and-testing)

**1.6.2.7** **DATA COLLECTION/ RECONFIGURATION**
[26](#data-collection-reconfiguration)

**1.6.2.8** **LAPTOPS** [26](#laptops)

**1.6.2.9** **FLIGHT DIRECTOR OFFICE** [26](#flight-director-office)

1.6.2.9.1 FLIGHT RULES [26](#flight-rules)

1.6.2.9.2 ADMINISTRATIVE MEETINGS [26](#administrative-meetings)

1.6.2.9.3 PROGRAM INTEGRATION [26](#program-integration)

1.6.2.9.4 SAFETY INTEGRATION [26](#safety-integration)

1.6.3 RESERVED [26](#reserved-45)

1.6.4 FLIGHT OPERATIONS SYSTEMS AND EQUIPMENT
[26](#flight-operations-systems-and-equipment)

**1.6.4.1** **MISSION CONTROL CENTER (MCC)**
[26](#mission-control-center-mcc)

1.6.4.1.1 RESERVED [26](#reserved-46)

1.6.4.1.2 RESERVED [26](#reserved-47)

**1.6.4.2** **INTEGRATED TRAINING FACILITY (ITF)**
[26](#integrated-training-facility-itf)

**1.6.4.3** **INTEGRATED PLANNING SYSTEM (IPS)**
[26](#integrated-planning-system-ips)

**1.6.4.4** **SOFTWARE PRODUCTION FACILITY (SPF)**
[26](#software-production-facility-spf)

1.6.4.4.1 RESERVED [26](#reserved-48)

1.6.4.4.2 SPF-UNIQUE INSTALLATION SERVICES
[26](#spf-unique-installation-services)

**1.6.4.5** **RESERVED** [26](#reserved-49)

1.6.4.5.1 RESERVED [26](#reserved-50)

1.6.4.5.2 RESERVED [26](#reserved-51)

**1.6.4.6** **RESERVED** [26](#reserved-52)

**1.6.4.7** **RESERVED** [26](#reserved-53)

**1.6.4.8** **RESERVED** [26](#reserved-54)

**1.6.4.9** **OPERATIONS SUPPORT SYSTEMS**
[26](#operations-support-systems)

1.6.5 NASA MANAGED MISSION DESIGN, PREPARATION, AND EXECUTION SUPPORT
[26](#nasa-managed-mission-design-preparation-and-execution-support)

**1.6.5.1** **FLIGHT SYSTEMS** [26](#flight-systems)

**1.6.5.2** **FLIGHT PLANNING/CARGO/ASSEMBLY**
[26](#flight-planningcargoassembly)

**1.6.5.3** **FLIGHT DESIGN AND DYNAMICS**
[26](#flight-design-and-dynamics)

**1.6.5.4** **FLIGHT OPERATIONS DEVELOPMENT**
[26](#flight-operations-development)

**1.6.5.5** **FLIGHT DIRECTOR OFFICE** [26](#flight-director-office-1)

1.7 NASA MANAGED ACTIVITIES [26](#nasa-managed-activities)

1.7.1 SPECIAL STUDIES AND DEVELOPMENT PROJECTS
[26](#special-studies-and-development-projects)

**1.7.1.1** **KSC SHUTTLE DEVELOPMENT ACTIVITIES**
[26](#ksc-shuttle-development-activities)

**1.7.1.2** **KSC CONSTRUCTION OF FACILITIES (CofF) ACTIVITIES**
[26](#ksc-construction-of-facilities-coff-activities)

1.7.3 RESERVED [26](#reserved-55)

1.7.4 PROGRAM REIMBURSABLES [26](#program-reimbursables)

1.7.5 SRB DEVELOPMENT ACTIVITIES [26](#srb-development-activities)

1.8 RESERVED [26](#reserved-56)

1.9 PROGRAM TRANSITION [26](#program-transition)

1.9.1 RESERVED [26](#reserved-57)

1.9.2 RESERVED [26](#reserved-58)

1.10 CONSTELLATION BRIDGE SUPPORT [26](#constellation-bridge-support)

2.0 RESERVED [26](#reserved-59)

3.0 RESERVED [26](#reserved-60)

# 1.0 SPACE PROGRAM OPERATIONS CONTRACT

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

Table 1

SPACE TRANSPORTATION SYSTEM MANIFESTED FLIGHTS

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

o Overall flight definition and planning guidelines

o Near-term flight assignments, characteristics, and configuration

o Flight preparation configuration freeze point definitions

o Follow-on flight rate requirements by fiscal year

o Required capability enhancements in support of flight missions

o Orbiter Maintenance and Down Period (OMDP) Schedule

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

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

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

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

## 1.1 PROGRAM AND BUSINESS MANAGEMENT

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

### 1.1.1 PROGRAM MANAGEMENT

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

#### **1.1.1.1 PLANNING**

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

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

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

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

The contractor shall develop and maintain plans for contingency and
emergency situations. These plans shall include planning for natural
disasters, launch delay situations, off nominal landings, major hardware
failure safing/recovery situations, and crew evacuations. These plans
shall also include approaches to emergency preparedness, which
integrates preparedness, response, and recovery efforts into an
effective program that promotes a safe work environment to the employees
(DR 1.1.1.1-e and DR 1.1.1.1-l). A current list of NASA contingency and
emergency preparedness plans is included in Exhibit 1.1.1.1; the
contractor shall provide support to the customer to develop and maintain
these plans on an as needed basis. The contractor shall conduct
exercises and simulations that promote employees awareness and action to
contingency and emergency situations and participate in government
exercises and simulations upon request.

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

#### **1.1.1.2 MANAGEMENT REVIEWS**

##### 1.1.1.2.1 CONTRACT MANAGEMENT REVIEWS

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

##### 1.1.1.2.2 PROGRAM REVIEWS

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

The contractor shall establish a consistent method to manage the
preparation, technical review, and distribution of the Launch Site
Requirements Review (LSRR), Launch Site Flow Review (LSFR), Delta Launch
Site Flow Review (DLSFR), Modification Site Requirements Review (MSRR),
Modification Site Flow Review (MSFR), and Delta Modification Site Flow
Review (DMSFR), Change Requests (CRs) and presentation material for the
SSP Program. This includes the responsibility to evaluate the
presentation, to recommend items to be presented, and to prepare the
final presentation package for the Program Requirements Control Board
(PRCB).

##### 1.1.1.2.3 FLIGHT READINESS

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

#### **1.1.1.3 RESERVED**

#### **1.1.1.4 RISK MANAGEMENT**

The contractor shall implement risk management processes and standards
as defined in NASA and SSP policies and requirements (NASA Procedural
Requirements (NPR) 7120.5, 8000.4, and NSTS 07700). The contractor shall
provide a risk management plan (DR 1.1.1.4-a) which describes the
policies, standards and processes defined to implement these
requirements and the requirements defined in this SOW as well.

The contractor shall ensure that risks and hazards with potential
safety, mission success, supportability, cost, and schedule impacts
are: 1) identified and incorporated into the SSP Risk Management
process, 2) analyzed to characterize the potential risk, 3) communicated
to all affected stakeholders, and 4) effectively mitigated. The
contractor shall use established SSP reporting formats and information
systems to communicate risks to the government. Risk communication will
be accomplished formally through the Top Risk Reporting process defined
in NSTS 07700. However, risk communication shall occur as needed through
working level interfaces to ensure that element/project managers
routinely consider risks in the day-to-day planning and decision making
processes.

The contractor shall provide a risk assessment with the complete
relationship of the assurance issues (safety, reliability,
maintainability and quality) to program goals (cost, schedule and
mission success) with each topic and issue brought to program management
for resolution. The risk assessment shall include the contractor's
recommended means to mitigate the risk (DR 1.1.1.4-b).

The contractor shall participate in program risk management forums as
defined by NSTS 07700.

#### **1.1.1.5 NEW TECHNOLOGY**

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

### 1.1.2 FINANCIAL RESOURCES AND PERFORMANCE MANAGEMENT

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

#### **1.1.2.1 FINANCIAL RESOURCES MANAGEMENT**

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

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

The contractor shall conduct monthly Technical, Cost and Schedule
Reviews (TCSRs), providing NASA with insight into the contractor's,
subcontractors', and vendors' overall technical, schedule, and cost
performance. The presentations shall depict performance measurement,
accomplishments, issues, corrective actions, and enhanced variance
reporting which will provide more insight into the cause of the
variance. The contractor shall track and report energy utilization and
consumption (DR 1.1.2.1-d), on-site and off-site headcount (DR
1.1.2.1-e), and geographical economic impacts (DR 1.1.2.1-f).

The contractor shall provide Monthly Property Financial Reporting, (DR
1.1.2.1-l).

The contractor shall provide an Annual Property NASA Form (NF) 1018
Report, (DR 1.1.2.1-k).

#### **1.1.2.2 PERFORMANCE MEASUREMENT**

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

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

For development and production efforts which may be authorized in this
contract, the contractor shall provide PMS reporting (DR 1.1.2.2-a) in
accordance with NPD 9501.1G, NASA Contractor Financial Management
Reporting System, which correlates work accomplished and actual costs
against baseline cost plans and schedules.

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

### 1.1.3 CONTRACT MANAGEMENT

The contractor shall provide overall management of the contract
requirements.

#### **1.1.3.1 PRIME CONTRACT MANAGEMENT**

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

#### **1.1.3.2 SUBCONTRACT MANAGEMENT**

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

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

### 1.1.4 INFORMATION AND DOCUMENT MANAGEMENT

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

The contractor shall provide on-site software and data base development
and sustaining engineering services for the Mission Operations
Directorate (MOD) in support of the Management Services Office.

The contractor shall provide on-site administrative, operational, and
integration services for MOD Office and Mission Control Center PC based
Workstations and associated File Servers in support of the Management
Services Office.

#### **1.1.4.1 INFORMATION MANAGEMENT**

The contractor shall develop, maintain, operate and secure information
systems which provide for the management, preparation, publication,
control and dissemination of information and data required by this
contract. The government systems that are currently being used will be
made available to the contractor and are identified in Attachment J-9.

The contractor's information management activities shall include
operating and maintaining a data repository or repositories, as
required, for originals in any media including classified and
proprietary documents*.* The contractor shall produce and maintain a
data management plan (DR 1.1.4.1-e) which will document its process for
the management of its delivered products. The contractor shall maintain
files of the documentation required to perform all the tasks in this
SOW. The contractor shall establish a formal documentation release
system and a system for rapid retrieval of all records. The contractor
shall provide a records management plan (DR 1.1.4.1-f). This plan shall
document the contractor's processes for identifying, collecting,
maintaining, and archiving all records generated during the performance
of all tasks in this SOW. This shall include plans for disposition of
these records at the end of the contract.

The contractor shall establish and implement a program-wide (i.e.
contract-wide) information technology (I/T) planning and reporting
process (DR 1.1.4.1-b) to include IT POP and Capital Planning and
Investment Control (CPIC) processes. The contractor shall also implement
an enterprise architecture process (DR 1.1.4.1-g).

The contractor shall be responsible to ensure that their IT systems are
interoperable with NASA IT standards.

#### **1.1.4.2 DOCUMENT MANAGEMENT**

The contractor shall maintain accurate originals and shall prepare and
distribute NASA approved changes to SSP and operations baseline
documentation. These originals shall be made available to the NASA and
Shuttle community electronically. This includes the NSTS 07700
documentation series and other Program/Element/Project produced
documentation as described in Product Development Plan MS7-005.

#### **1.1.4.3 RESERVED**

### 1.1.5 CONFIGURATION AND VERIFICATION MANAGEMENT

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

#### **1.1.5.1 CONFIGURATION MANAGEMENT**

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

The contractor shall supply general meeting support for Program/Project
boards, panels, and other meetings to support Program Office operations
as described in Product Development Plan MS7-004.

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

#### **1.1.5.2 VERIFICATION MANAGEMENT**

##### 1.1.5.2.1 PROGRAM VERIFICATION MANAGEMENT

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

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

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

The contractor shall develop, deliver, and maintain the vehicle systems
drawings (DR 1.2.1.5-a).

##### 1.1.5.2.2 ORBITER AND COMBINED ELEMENT VERIFICATION MANAGEMENT

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

### 1.1.6 GOVERNMENT FACILITY, PROPERTY AND SECURITY MANAGEMENT

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

#### **1.1.6.1 FACILITY MANAGEMENT**

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

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

The contractor shall provide NASA a semi-annual review of all facility
projects giving insight into the contractor's and subcontractors'
progress throughout the projects' life, starting with requirements
documents and continuing throughout the study, Preliminary Engineering
Reports (PER), design, construction, and activation phases of the
projects. Particular emphasis shall be placed on identifying issues such
as environmental concerns, change orders and changes to schedules
(including completion milestones), scope of work and cost. Also,
particular emphasis shall be placed on other concerns on external issues
affecting the project such as access to work, other contractors, and
NASA support.

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

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

#### **1.1.6.2 PROPERTY MANAGEMENT**

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

The contractor shall maintain approved property management systems.
Approval is based on satisfactory ratings for each category covered
under the Property Management Plan, progress on any corrective action
plans or property initiatives (DR 1.1.6.2).

The contractor shall routinely disposition scrap, excess, engineering
obsolete, and unserviceable/non-repairable assets. The expected range
for such disposition is 15,000 to 20,000 line items per year at the
prime contract level, with an additional 2,500 line items per year at
the subcontractor level. Items requiring more than incidental
engineering analysis, for disposition in excess of routine ops, as well
as any residual assets requiring disposition at the end of FY10, will be
handled in accordance with DRD 1.1.6.2 and H.35 - Provisioning
Procedures.

#### **1.1.6.3 SECURITY AND TECHNOLOGY PROTECTION MANAGEMENT**

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

The contractor\'s security program shall encompass Industrial, Physical,
Administrative, Information, Communication, Personnel, threat analysis,
and IT security programs in accordance with the National Industrial
Security Program Operating Manual, SSP requirements, SPOC Security
Management Plan (DR 1.1.6.3-a), and DD Form 254. The contractor will
provide protection/safeguarding of personnel, facilities, assets,
equipment, classified information/materials, and unclassified
sensitive/technological data/information as required. In accordance with
NASA regulations governing National Security, National Resource
Protection, and Technology Protection the contractor shall provide
security engineering, maintenance, and operations for systems protecting
classified controlled and unclassified controlled information. The
contractor will act as the COMSEC controlling authority for certain
encrypted communications, and provide personnel certified to perform
limited cryptographic maintenance and operations.

The contractor shall report all allegations of espionage, terrorism
threats, or incidents providing counterintelligence indicators of the
loss or potential loss of administratively controlled, export
controlled, proprietary, or classified national security information to
the appropriate Center Counterintelligence Office and ensure that the
contractor shall fully cooperate in the conduct of inquiries,
investigations, and other NASA counterintelligence activities, to the
extent permitted by law.

The contractor\'s technology protection program shall encompass
classified controlled information/material and unclassified controlled
information, materials, and services (including Export Controlled, and
proprietary data/material as appropriate), and the SPOC Technology
Protection Control Plan (DR 1.1.6.3-b) In accordance with the Department
of Commerce (DOC) Export Administration Regulations (EAR), the
Department of State (DOS) International Traffic In Arms (ITAR), and the
NASA Export Control Program (ECP), the contractor shall provide export
control functions for hardware, services, software, and data requiring
export in the execution of specific contract responsibilities. The
contractor will ensure that in the absence of NASA exemptions or
exceptions, that appropriate licenses and Technical Assistance
Agreements (TAAs) are in place to support exports. The contractor shall
provide the methodology and processes for the application of risk
assessment to all security and technology protection activities, and the
integration of Security and Technology Protection Management across the
SPOC contract and its subcontractors.

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

### 1.1.7 FLIGHT INTEGRATION, MANIFEST AND SCHEDULES

#### **1.1.7.1 FLIGHT INTEGRATION**

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

The contractor shall support the Flight Integrated Product Teams (IPTs)
and interface with SSP and ISS organizations to resolve flight
preparation process implementation issues. The contractor shall direct
studies, assessment activities, and assign action items to resolve
flight preparation process issues. The contractor shall provide the SSP
with insight into flight preparation progress including issues and issue
resolution activities.

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

The contractor shall provide support to the NASA Mission Integration
Managers (MIMs) for integration documentation development and
maintenance. These documents include the Integration Plans (IPs) and
associated change requests (CRs).

The contractor shall provide integrated contractor evaluations of the
flight specific and generic Shuttle flight rules.

The contractor shall provide support to the NASA MIMs and payload
customers, supporting simulations and realtime flight operations at the
Customer Support Room (CSR), Payload Operations Control Center (POCC)
consoles and to the Mission Management Team (MMT). The contractor shall
maintain the In-Flight Anomaly (IFA) database.

The contractor shall maintain JSC 16768, Flight Crew Equipment Landing
Site Dispositioning Manual (LSDM), which includes the Landing Site
Dispositioning Report (LSDR).

The contractor shall chair the SSP Television Working Group (TVWG),
conduct meetings as defined in NSTS 08240, SSP Television Plan (section
4.2.1), and develop and maintain the Flight-Specific TV Plan (DR
1.1.7-d). The contractor shall represent the SSP on panels, boards and
working groups as appointed. The contractor shall be responsible for
oversight of the development, testing and operations of SSP TV and audio
requirements and assessment and evaluation of new TV technologies and
products.

#### **1.1.7.2 MANIFESTS AND SCHEDULES**

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

The contractor shall support the NASA working groups in the development,
definition, assessment, and modification of the Shuttle manifest and the
top-level program schedules and deliver products (DR 1.1.7-a). The
contractor shall maintain the Automated Manifest Planning System (AMPS).

The contractor shall perform early mission feasibility assessments
utilizing the Shuttle Payload Integration and Cargo Evaluation (SPICE)
process to include an evaluation of ascent performance margins, mission
mass properties, integrated cargo placement options and other key
mission parameters. These assessments shall be provided in support of
the baselining of missions in the Flight Definition and Requirements
Directive (FDRD), as well as manifest planning activities of the Joint
Consolidated Analysis Working Group (JCAWG) and other special requests.

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

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

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

The contractor shall provide timely analysis and data to support the
government managed manifest planning efforts by providing support to
Program Office manifest supportability assessments.

### 1.1.8 TECHNICAL INFORMATION SYSTEMS MANAGEMENT

The contractor shall provide software and hardware sustaining
engineering and development management for shuttle mainframe,
client-server based, and web-based technical information systems. The
contractor shall provide operational planning, requirements definition,
development, implementation, maintenance, and operations. Shuttle
technical information systems include configuration management,
verification management, requirements management, flight integration
manifests, schedules, and system/cargo engineering, integration, and
analysis toolsets (DR 1.1.8-a).

## 1.2 SYSTEM AND CARGO ENGINEERING AND INTEGRATION

The contractor shall plan, control, and perform SSV systems engineering
and integration activities. The contractor shall also plan, control, and
perform flight operations and cargo integration activities.

### 1.2.1 ENGINEERING INTEGRATION AND ANALYSIS

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

The contractor shall develop an additional set of reconfiguration flight
products and cargo integration engineering analyses for the manifest
contingencies, as defined by FRD or other program directive, for up to
three flights per fiscal year.

#### **1.2.1.1 SSV POST FLIGHT ANALYSIS**

The contractor shall plan, control, and perform post flight analyses of
the integrated SSV flight systems. The contractor shall provide the post
flight analyses of the SSV to validate engineering preflight prediction
tools and methodologies and to provide the SSP visibility on potential
in-flight anomalies and vehicle performance outside of flight
experience. The contractor shall participate in the resolution of
in-flight anomalies and evaluation of vehicle performance outside of
flight experience. Development of flight derived dispersions database
updates (DR 1.2.1.1-a), RSRM performance adjustments (DR 1.2.2.3-a), and
MPS budget updates (DR 1.2.2.3-b) will be required.

The contractor shall perform detailed trajectory reconstructions and
post-flight analysis for the following integrated functions:
aerodynamics; acoustics; aero heating; separation systems (Launch Pad,
SRB and ET); Guidance, Navigation, and Control (GN&C); Loads and
Dynamics; Ascent Performance; Integrated MPS (ET Pressurization;
propellant loading, consumption, and residuals at MECO). The contractor
shall perform assessments of integrated electrical, avionics, and
hydraulic systems. The contractor shall deliver quick-look and detailed
post-flight reconstructions (DR.1.2.1.1-b).

#### **1.2.1.2 ASCENT MARGINS AND FLIGHT READINESS ASSESSMENT**

The contractor shall support definition of ascent flight design criteria
and constraints based on vehicle performance. The contractor shall plan,
control, and perform a pre-flight evaluation of the integrated SSV
flight systems and induced environments. The contractor shall provide
the ascent flight verification assessment based on the latest available
Trajectory Design Data Package (TDDP) and the flight cycle I-loads.
Results of the evaluation shall be coordinated with NASA and presented
to the Program Integration Flight Readiness Program Milestone Reviews as
defined in NSTS 08117. The contractor shall maintain documentation of
the Flight Readiness Verification methodology and shall obtain NASA
approval prior to changing the methodology. Specific missions may
require unique contractor assessments. For these specific missions, NASA
will define requirements for those assessments. The contractor shall
maintain the ability to perform a complete Flight Margins Assessment for
mission unique designs.

#### **1.2.1.3 CARGO INTEGRATION ENGINEERING ANALYSIS**

The contractor shall provide all cargo integration assessments and
analyses necessary to verify compliance with SSP requirements,
compatibility between the Shuttle and manifested payload/cargo elements
and integration hardware, and readiness for all flight phases
(pre-launch, liftoff, ascent, on-orbit, entry, descent, landing,
post-landing, and ferry flight).

##### 1.2.1.3.1 COMPATIBILITY ASSESSMENTS

The contractor shall perform Orbiter and payload/cargo element
compatibility assessments, including the following technical areas as a
minimum: passive thermal, active thermal/Environmental Control and Life
Support (ECLS), contamination, structural/mechanical,
avionics/electrical, Electromagnetic Effects (EME), safety, and
environmental impacts. The contractor shall support the Cargo
Integration Review (CIR) for each Shuttle flight.

##### 1.2.1.3.2 MATH MODELS

The contractor shall provide support to Shuttle math model development
and maintenance. The contractor shall maintain the Shuttle cargo
integration Critical Math Models and Analysis Tools (CMMATs) database
content under configuration management/control and develop CMMAT changes
to improve flight predictions, with changes approved by NASA. The
contractor shall provide Shuttle math models (DR 1.2.1.3-a) to payload
customers. Payload math models will be furnished by the payload
customers and provided to the contractor.

##### 1.2.1.3.3 STRUCTURAL VERIFICATION ANALYSIS

The contractor shall perform structural flight verification analyses for
all Shuttle flights and provide engineering data (DR 1.2.1.3-b) to NASA
and payload customers. The contractor shall conduct the Pre-Verification
Loads Review (PVLR), Loads Verification Analysis Data Acceptability
Review (VADAR) and the Loads Verification Acceptance Review (VAR) for
all flights.

The contractor shall perform screening reviews of Shuttle/ISS proximity
operations and mated on-orbit loads results to ensure that analyses meet
SSP requirements in terms of process, methodology, and loads
combinations (including, but not limited to, Orbiter induced
environments such as RCS, EVA/IVA, and Orbiter/payload venting) and
report findings and recommendations of the screening reviews at the
PVLR. The contractor shall review on-orbit ICDs and flight rules for
compatibility with structural requirements and verification loads
analysis and report findings at the Joint On-Orbit Verification Review
(JOVR) Flight Readiness Review (DR 1.2.1.3-b).

The contractor shall perform structural loads and stress analysis for
secondary payloads to verify Orbiter and payload compatibility. The
contractor shall perform a middeck integrated acoustic assessment for
each flight to verify compatibility with SSP requirements (DR
1.2.1.3-b).

##### 1.2.1.3.4 THERMAL VERIFICATION ANALYSIS

The contractor shall perform thermal flight verification analyses for
all Shuttle flights and provide engineering data (DR 1.2.1.3-b) to NASA
and payload customers. The contractor shall conduct the Pre-Verification
Thermal Review (PVTR) and the Thermal VAR for all flights.

The contractor shall perform integrated passive thermal
analyses/assessments of the Shuttle/ISS docked phase attitude timeline
and thermal control system performance to verify Orbiter and
payload/cargo element compatibility (DR 1.2.1.3-b).

The contractor shall perform active thermal/ECLS analyses of the
Shuttle/ISS docked phase to verify habitability of the mixed air
environment and compatibility of the payload/cargo element with the
Orbiter capability (DR 1.2.1.3-b).

The contractor shall perform assessments for payload venting effects
into the cargo bay to verify Orbiter and payload/cargo element
compatibility (DR 1.2.1.3-b).

##### 1.2.1.3.5 AVIONICS ANALYSES

The contractor shall perform avionics analyses/assessments to verify
Orbiter and payload/cargo element compatibility. The contractor shall
perform voltage and power analysis and perform Orbiter payload/cargo
element flight and ground interface assessments (DR 1.2.1.5-b).

##### 1.2.1.3.6 EME ANALYSES

The contractor shall perform EME analyses/assessments to verify Orbiter
and payload/cargo element compatibility. The contractor shall perform
EME, lightning, non-ionizing radiation, beat frequency, RF threat
assessment, and electrostatic discharge analyses compatibility for all
payload/cargo related activities (DR 1.2.1.3-e).

##### 1.2.1.3.7 PAYLOAD/CARGO SAFETY ANALYSES

The contractor shall perform all analyses/assessments and issue
resolution necessary to verify that the integrated Orbiter and
payload/cargo element(s) meet Shuttle safety requirements. The
contractor shall support the Payload Safety Review Panel and ISS Safety
Review Panel (DR 1.2.1.3-c).

The contractor shall perform all assessments necessary to verify there
is no environmental impact threat from the manifested cargo. The
contractor shall provide a Payload Environmental Impact Statement (DR
1.2.1.3-d).

The contractor shall perform a mission specific Bent Pin Analysis and a
Hazard Analysis using the NSTS 21111, Generic Integrated Cargo Hazard
Assessment Report requirements.

The contractor shall evaluate program changes, and identify and process
required updates to the Safety and Reliability Requirements for the
Space Shuttle Cargo Integration Hardware (CIH), NSTS 60542. The
contractor shall develop, evaluate, and process hazard reports for
existing CIH in accordance with NSTS 60542.

#### **1.2.1.4 CARGO INTEGRATION HARDWARE**

The contractor shall provide management and technical support of all
cargo integration hardware tasks. The contractor shall provide
engineering design capability to accomplish any necessary changes
required to preserve original cargo integration hardware design
requirements compatibility with program requirements and certification
and to support assessment of new capability developments as might be
initiated by NASA. The contractor shall perform operational and
implementation impact assessments of all proposed or approved cargo
integration hardware designs and design changes.

##### 1.2.1.4.1 CARGO INTEGRATION HARDWARE LOGISTICS

The contractor shall provide logistics functions for cargo integration
hardware accountability and general logistics requirements. The
contractor shall store and maintain the inventory of government-and
contractor-furnished cargo integration hardware. The contractor shall
maintain an inventory management system. The contractor shall develop
and maintain a mission equipment allocation list of all cargo
integration hardware and Government Furnished Equipment (GFE) for each
flight and identify deficiencies in hardware availability to NASA. The
inventory of cargo integration hardware has been furnished by the
government and has become government-owned, contractor-maintained
hardware. The contractor shall perform repair and make-work changes to
accepted cargo integration hardware.

The contractor shall procure hardware items from certified suppliers and
repair failed hardware using a certified facility. Manufacturing,
procurement, and repair of hardware items shall be consistent with
Program requirements and directives. The contractor shall utilize
existing certification plans for all manufacturers, repair depots, and
support laboratories. The plans shall comply with Program requirements
and directives.

The contractor shall provide spares and consumables required to support
the hardware, support equipment, and processing activities. The
contractor shall provision these assets at the line replaceable unit
(LRU) and piece-part/consumable levels. The contractor shall monitor and
document hardware spares balances.

The contractor shall identify and resolve hardware and component
obsolescence issues; and loss of repair, failure analysis, or production
capabilities in compliance with Program management and control
requirements. Loss of capabilities includes, but is not limited to, loss
of skills or a supplier going out of business.

The contractor shall provide the engineering for hardware that includes,
but is not limited to, initial parts requirements, logistics support
analysis, and maintenance planning. The contractor shall report
supportability issues to the government.

The contractor shall provide transportation, shipping, receiving,
storage, warehousing, and distribution services. Transportation services
shall include hardware and equipment transportation for routine and
contingency operations. The contractor shall provide service with no
hardware damage due to transportation or storage. Minor damage judged to
be in the range of the acceptable wear and tear specification or able to
be repaired on-site by standard repair or Material Review action is
acceptable, but in no case shall minor damage impact safety, mission
success or major program schedule milestones. The contractor shall
report and investigate accidents resulting in damage to NASA property or
injuries to personnel, to include assessments of accident impacts to
cost, schedule and mission performance, and remedial and corrective
actions performed.

The contractor shall participate in the GIDEP ALERT System and provide
notice to the government of Cargo Integration GIDEP-related issues. The
contractor shall identify the affected hardware and start an analysis of
the problem with recommendations and corrective actions as part of their
response.

##### 1.2.1.4.2 CARGO INTEGRATION HARDWARE MISSION KITS

The contractor shall prepare program provisioning requests, draft
statements of work, budgetary and planning, cost estimates (including
rough-order-magnitudes) to initiate and implement cargo integration
hardware analytical/design studies and cargo integration hardware
projects in accordance with SOW section 1.7.1 (DRs 1.4.1.5.1-a,
1.4.1.5.1-b, 1.4.1.5.1-c, and 1.3.3.1).

The contractor shall maintain the Standard End Item Specification (SEIS)
for Orbiter/Payload Integration Hardware, MJO73-0001, and the Cargo
Integration Hardware Ground Support Equipment Standard End Item
Specification (GSE SEIS), MJO73-0010, under configuration management
control. The contractor shall maintain cognizance of SSP requirements
changes that may impact cargo integration SEISs and ensure that the
SEISs are kept current with identified changes. The contractor shall
prepare SEIS changes and provide the changes to the responsible
technical area for review of technical accuracy. The contractor shall
coordinate technical reviews necessary to resolve issues, update changes
to reflect technical area review, and submit changes to NASA for
approval.

The contractor shall accept cargo integration hardware certified by NASA
to SSP requirements and provided to the contractor as Government
Furnished Equipment (GFE) and integrate any such GFE into the Shuttle
system.

#### **1.2.1.5 RECONFIGURATION ENGINEERING**

The contractor shall develop, deliver, and maintain the set of mission
engineering products (DR 1.2.1.5-b) needed to configure the Orbiter
vehicle for payload accommodations and support flight operations for
each Shuttle flight.

The contractor shall develop reconfiguration flight products for the
manifest as defined in SSP requirements documentation (i.e., Flight
Requirement Document (FRD), FDRD, PRCB directives, etc.). These products
shall include hardware drawings, installation technical orders, Mission
Equipment Cargo Support Launch Site Integration (MECSLSI) drawings,
avionics diagrams/schematics, and cargo arrangement drawings. The
contractor shall conduct the engineering review portion of the Cargo
Integration Review (CIR) to ensure compatibility of payload/mission
requirements with Orbiter capabilities and to verify proper
implementation of these requirements. The contractor shall provide the
MECSLSI and reference drawings in support of CIR for each Shuttle
flight.

The contractor shall evaluate generic and mission specific flight rules,
flight data file, and change requests (CRs) for compliance with Cargo
Engineering flight products and analyses. The contractor shall provide
flight rule and flight data file CR coordination.

The contractor shall perform walkdown inspections during processing to
mitigate the SSP risk in the CoFR process for Cargo Elements.

The contractor shall maintain theIntegrated Configuration Engineering
Data (ICED) library (DR 1.4.1.6.1-e) consisting of Computer Aided Design
(CAD) models of non-ISS payloads and payload bay mission kit hardware
configuration.

The contractor shall provide advanced planning activities.

The contractor shall chair the Daily Mission Integration Control Board
(DMICB) and manage the processing of DMICB CRs.

The contractor shall provide design center support to Kennedy Space
Center to verify proper implementation of Design Center requirements,
assist with problem resolution, and provide processing status.

The contractor shall provide representation and status at flight
Integrated Product Teams (IPTs) and milestone reviews.

The contractor shall provide real-time mission support for on-orbit
operations for each mission.

The contractor shall be responsible for the build and maintenance of the
GFE database for the purpose of FRD GFE hardware integration into the
Orbiter for each mission.

#### **1.2.1.6 DOLILU OPERATIONS SUPPORT SYSTEM (DOSS) CONFIGURATION AND DATABASE MAINTENANCE**

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

The contractor shall maintain databases, computer hardware, and software
required to support DOSS activities in accordance with NSTS 08329 Volume
VIII DOLILU Operations Support Plan. The required DR's are as follows:
DR 1.2.1.6-a and DR 1.2.1.6-b.

#### **1.2.1.7 SHUTTLE SYSTEMS ENGINEERING ANALYSIS**

The contractor shall provide integrated Certificate of Flight Readiness
(CoFR) engineering support by compiling CoFR statements and supporting
data into the System Integration CoFR/Flight Readiness package. The
contractor shall also participate in Element CoFR/Flight Readiness
Review (FRR) briefings and status/ track Element open items to closure.

The contractor shall provide launch photo/TV analysis and debris
transport engineering analysis; provide launch pad ice/debris inspection
analysis to support day of launch and non-flight specific ice/debris
requirements development and analysis; and support Shuttle and ground
imagery system requirements development, maintenance and implementation.
The contractor shall arrange for, schedule, and manage necessary
satellite assets for the support of the external tank observation
camera.

The contractor shall manage and maintain the debris data for expected
and unexpected debris sources. Additionally the contractor shall provide
debris transport support for new debris sources identified preflight,
during orbit operations, and through post-flight analysis and
inspection. In this capacity, the contractor shall implement changes and
maintain transport models and methodologies, and execute transport
trajectories as requested. Furthermore, the contractor shall maintain
historical data of debris transport results which can be searched and
referenced for previous debris sources or transport trajectory impacts
(DR 1.2.1.7-d).

The contractor shall maintain and ensure data currency in the Shuttle
Systems Critical Math Model Database (CMMDB). The contractor shall
ensure that critical math models and tools utilized for integrated
system performance analyses are under configuration management and are
baselined in the CMMDB before utilization on mission products. The
contractor shall monitor and assess element/project changes for
potential impacts to critical math models and tools, and initiate
respective changes to the CMMDB (DR 1.2.1.7-b).

The contractor shall provide engineering support to the Engineering
Technical Panels in support of SE&I, the SICB and other Program Boards.
In this capacity, the contractor shall have engineering expertise
present to discuss technical content, communicate SE&I positions, and
respond to actions as assigned/approved by NASA SE&I.

### 1.2.2 SYSTEM AND CARGO INTEGRATION

The contractor shall provide integration engineering for mass
properties, trajectory, and flight design requirements; integration
analysis; and integration support during pre-launch and through the
flight. The contractor shall interface with payload customers to develop
cargo engineering requirements, and shall implement and verify that the
requirements have been accurately reflected in launch processing and
flight operations documentation.

#### **1.2.2.1 INTEGRATED MASS PROPERTIES**

The contractor shall plan, control, compile, and maintain data in an
integrated database system of current weights and centers of gravity for
all vehicle elements for all missions baselined in the Flight Definition
and Requirements Directive (FDRD), as well as reference missions and
special requests.

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

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

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

#### **1.2.2.3 RESERVED**

#### **1.2.2.4 INTEGRATION PLAN (IP) ANNEX 1**

The contractor shall interface with payload customers and develop,
baseline, and maintain unique IP Annex 1, Payload Data Packages, in
accordance with the IP schedule. The contractor shall maintain the
generic Annex 1 blank book with all blank book changes approved by NASA
(DR 1.2.2.4-a).

#### **1.2.2.5 PROGRAM INTERFACE CONTROL DOCUMENT (ICD)/INTERFACE DEFINITION DOCUMENTS (IDD)**

##### 1.2.2.5.1 SYSTEMS INTEGRATION ICDs

The contractor shall maintain all SSP systems ICDs (DR 1.2.2.5-a). The
contractor shall maintain cognizance of SSP and element/project changes
or issues that may impact systems ICDs and ensure that the ICDs are kept
current with identified element/project changes or issues. The
contractor shall coordinate with the SSP design elements/projects for
the preparation and coordination of proposed changes to SSP systems ICDs
and for obtaining the appropriate technical concurrence of the
interfacing element/project technical representatives. The contractor
shall perform reviews and assess all ICD changes for technical accuracy
before submittal to NASA for approval.

##### 1.2.2.5.2 CARGO INTEGRATION ICDs/IDDs

The contractor shall maintain all SSP cargo integration ICDs and IDDs
(DR 1.2.2.5-b). The contractor shall maintain cognizance of SSP and
payload/cargo element changes or issues that may impact cargo
integration ICDs/IDDs and ensure that the ICDs/IDDs are kept current
with identified changes. The contractor shall prepare ICD/IDD changes
and provide the changes to the responsible technical area for review of
technical accuracy. The contractor shall coordinate technical reviews
necessary to resolve issues, update changes to reflect technical area
review, and submit to NASA for disposition and approval.

#### **1.2.2.6 PAYLOAD UNIQUE ICDs**

The contractor shall interface with Shuttle users and develop, approve,
publish, and maintain payload unique ICDs, Installation Requirement
Documents (IRDs), and associated drawings (DR 1.2.2.6). Waivers,
deviations, or exceedances to the requirements of NSTS 07700, Volume
XIV, Attachment 1 (CORE ICD); NSTS 21000-IDD-ISS; NSTS 21000-IDD-MDK; or
NSTS 21000-IDD-SML for payload ICDs shall be prepared and submitted to
NASA for disposition per NSTS 07700, Volume IV.

The contractor shall provide configuration management support of the
On-Orbit ICDs and implement changes as directed by the NASA-chaired
Joint Technical Working Group (JTWG).

#### **1.2.2.7 PAYLOAD TEST AND HANDLING REQUIREMENTS**

##### 1.2.2.7.1 PAYLOAD OPERATIONS AND MAINTENANCE REQUIREMENTS AND SPECIFICATIONS (OMRS)

The contractor shall interface with the payload customer to develop,
baseline, and maintain all payload OMRS test requirements to verify the
payload utilized Orbiter services and the payload interfaces with the
Orbiter vehicle (DR 1.2.2.7). The contractor shall provide support to
and present the requirements to the payload OMRS Working Group (POG) for
review and problem resolution. The contractor shall provide support to
the FOICB as necessary for requirement approval. The contractor shall
maintain these requirements through the board change process.

##### 1.2.2.7.2 PAYLOAD TIME CRITICAL GROUND HANDLING REQUIREMENTS (TGHR)

The contractor shall interface with the payload customer to develop,
baseline, and maintain the mission unique middeck payloads Time-critical
Ground Handling Requirements Table (DR 1.2.2.7-a).

#### **1.2.2.8 TECHNICAL INTEGRATION ANALYSES**

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

#### **1.2.2.9 RESERVED**

#### **1.2.2.10 INTEGRATED AVIONICS AND ELECTROMAGNETIC EFFECTS**

##### 1.2.2.10.1 INTEGRATED VEHICLE AVIONICS

The contractor shall perform avionics system analyses for the integrated
Space Shuttle Vehicle. These analyses shall be comprised of end-to-end
analysis of electrical compatibility and requirements compliance across
ET, Orbiter, SRB/RSRM, SSME, and Ground Interfaces. The contractor shall
conduct system analyses and trade studies essential to the specification
and allocation of requirements for the integrated avionics system. The
contractor shall review and evaluate analytical and test data from
development and flight articles to assure compliance and compatibility
with the integrated Shuttle system requirements. The contractor shall
coordinate an ascent power analysis for each mission. The contractor
shall perform functional compatibility analyses of the systems software
and avionics interfaces to verify that proper fault tolerance
requirements are satisfied and that proper compatibilities exist.

##### 1.2.2.10.2 ELECTROMAGNETIC EFFECTS (EME)

The contractor shall perform EME, lightning, ionizing and non-ionizing
radiation, and electrostatic discharge compatibility analyses for the
integrated Space Shuttle Vehicle. These analyses shall be comprised of
unintended element-to-element, and externally induced electromagnetic
compatibility and requirements compliance across ET, Orbiter, SRB/RSRM,
SSME, and Ground Interfaces. The contract shall conduct EME system
analyses and synthesis essential to the specification and allocation of
requirements for the integrated system. The contractor shall review and
evaluate analytical and test data to assure compliance and compatibility
with the integrated Shuttle system requirements (DR 1.2.2.10-a).

#### **1.2.2.11 SSV DATABOOKS**

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

#### **1.2.2.12 SYSTEMS INTEGRATION FLIGHT SUPPORT**

The contractor shall provide pre-launch and real-time mission
engineering support for functions assigned to NASA Systems Engineering
and Integration. The engineering expertise that shall be provided during
the pre-launch activities includes, but shall not be limited to,
Integrated MPS, GN&C, Loads and Dynamics, Aero-thermal, Debris
Transport, Integrated Avionics, and Integrated Safety. During the
mission, the contractor shall provide support in the MER for the SE&I
Duty Officer and SE&I Imagery positions.

### 1.2.3 ELEMENT INTEGRATION

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

The contractor shall perform technical integration across all SSP
Elements. The contractor shall actively participate in Element Change
Control boards/processes; review and evaluate Element changes for
potential impacts to other Elements and the integrated vehicle; provide
membership and participate in all appropriate Element technical boards
and panels; review and evaluate proposed Element changes for SSP system
level impacts, issues, or conflicts; and provide risk assessments for
those changes (hardware, software, and interfaces).

The contractor shall evaluate Element engineering changes for Program
requirements compliance; provide Program level perspective, guidance and
expertise to SSP Elements to ensure appropriate implementation of
changes into the integrated vehicle; review SSP Element change
implementation evidence to ensure requirements compliance and verify as
designed/built engineering; and coordinate independent technical
evaluation of Element analyses, test plans, and test results that may
affect NSTS 07700 Volume X requirements.

The contractor shall provide Element support to System Requirements
Review (SRR), Preliminary Design Review (PDR), Critical Design Review
(CDR), Design Certification Review (DCR), Test Readiness Review (TRR),
and Operations Readiness Review (ORR) milestones for Element
Hardware/Software/System design modifications. The contractor shall
provide Project Engineering coordination of independent technical
assessments via Element and System level engineering review boards and
technical panels.

The contractor shall perform Multi-Element hardware commonality
assessments; develop and manage System Integration Plans (SIPs) for new
hardware, software, or interface design changes as directed by the SICB;
track Element progress against plan; participate in Design Reviews;
verify Element compliance with SIP requirements; modify SIPs based on
changes or modifications to the design; and summarize and publish
lessons learned for Element and Program reference.

### 1.2.4 SYSTEM ENGINEERING

The contractor shall provide programmatic level assessments of
Integrated Vehicle and Element requirements, hazards, risks assessments,
anomaly resolution and design changes. Contractor support for the
development and maintenance of the Integrated Hazard Analysis and
Reports including corresponding Fault Trees will be covered in section
1.3.1.1.

#### **1.2.4.1 ANOMALY INTEGRATION AND RESOLUTION**

The contractor shall facilitate the tracking, integration and resolution
of all in-flight anomalies. This shall include ensuring all integrated
in-flight anomalies are entered into the PRACA system, and that closures
and action plans are appropriately reviewed through the SICB and PRCB
prior to the next flight. Additionally as requested by NASA for selected
anomalies, the contractor shall perform data mining, reduction and
trending to identify potential issues at the Space Shuttle Program (SSP)
level; and interface with Element Chief Engineers and management to
understand problems and anomalies across the program.

The contractor shall participate on SSP level Tiger teams to perform
root cause analysis and recommend solutions to cross Element or
multi-Element issues and provide system engineering expertise in the
areas of hardware and system testing concepts, materials and processes
(M&P) and instrumentation.

#### **1.2.4.2 PROGRAM REQUIREMENTS MANAGEMENT**

The contractor shall assess Element level compliance with SSP
requirements for all Element changes (i.e. hardware, software,
interfaces); assure Program integration requirements issue
identification, documentation and resolution; provide SSP Level
requirements development, management and verification; and evaluate all
Element level requirements CRs, waivers, and exceptions for Program
level and multi-Element impacts, as well as common factors.

The contractor shall maintain cognizance of all NSTS 07700 requirements
and subordinate documents; update all SSP level requirements documents;
track and provide status of all waivers, deviations, and exceptions to
SSP level requirements; and suggest modifications to non-compliant
requirements to minimize or eliminate non-compliance conditions.

### 1.2.5 MSFC PROJECT INTEGRATION

The contractor shall provide project systems integration for the Shuttle
Propulsion Office (SPO), the MSFC Shuttle Propulsion Element Project
Offices and the Propulsion Systems Engineering & Integration (PSE&I)
office at Marshall Space Flight Center (MSFC).

#### **1.2.5.1 PROJECT SYSTEMS INTEGRATION**

This effort includes short term and long range strategic planning
efforts including development, preparation and integration of plans,
data and schedules, technical support for Huntsville Operations Support
Center (HOSC) launch/test activities including operation of data systems
and development of custom displays to monitor and process telemetry
data; MASTII data reconfiguration for the propulsion elements;
definition/coordination of data user requirements with the Data
Reduction Center; and preparation of flight evaluation reports.

#### **1.2.5.2 PROJECT ENGINEERING**

The contractor shall provide technical assessment of hardware design and
performance; resolution of hardware anomalies, flight performance issues
and processing discrepancies; technical support for hardware redesign
and upgrade efforts; integration of LCC, OMRSD and ICD requirements; and
preparation of project plans, schedules, metrics and databases for
management of technical initiatives.

#### **1.2.5.3 RESERVED**

#### **1.2.5.4 PROJECT CONFIGURATION MANAGEMENT**

The contractor shall provide the Configuration Control Board (CCB)
secretariat and shall perform functions including receipt, review,
coordination, tracking and filing of all SPO engineering changes and
associated requirements documentation. The contractor shall ensure
Quality records for the MSFC SPO PCIN master files are maintained. The
contractor shall provide configuration management for performance of
NEQA and CM audits in support of the SPO, PSE&I and the propulsion
element project offices.

#### **1.2.5.5 PROJECT INFORMATION INTEGRATION**

The contractor shall perform integration, generation, and distribution
of SPO related technical documentation and multi-media presentations;
development, maintenance and integration of SPO internal and external
web sites; and scheduling, media set up, real time support and
troubleshooting for video and audio conferencing. The contractor shall
integrate MSFC project resource and schedule information.

## 1.3 SAFETY, RELIABILITY, QUALITY, MISSION ASSURANCE, AND ENVIRONMENTAL MANAGEMENT

The contractor shall implement a management system which is certified by
third party audit to the requirements of SAE AS 9100:2004, Quality
Systems -- Aerospace -- Model for Quality Assurance in Design,
Development, Manufacturing, Installation, and Servicing and which meets
the requirements of NSTS 5300.4 (ID-2) for flight systems and systems
which interface with flight systems.

The contractor shall provide a Safety and Mission Assurance plan (DR
1.3-a) that documents auditable processes to achieve safe program
operations and assure flight safety, with emphasis on crew safety,
mission success, and prevention of loss of critical hardware. The plan
shall meet as a minimum, the requirements in the applicable volumes of
the NSTS 07770, and NSTS 5300.4 (1D-2) Safety, Reliability,
Maintainability and Quality Provisions for the Space Shuttle Program.

The contractor shall provide a Safety and Health plan (DR 1.3-b) that
describes management leadership and employee involvement in tasks and
activities related to the safety and health program at each site.

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

Performance of safety, reliability, quality, mission assurance, and
environmental management processes shall be managed through the
characterization of work and implementation of performance metrics (DR
1.1.1.1-f).

### 1.3.1 SAFETY

#### **1.3.1.1 SYSTEMS SAFETY**

The contractor shall implement an approach which ensures the
identification, elimination, control, and update of element hazards and
integrated hazards throughout the complete life cycle (design,
development, manufacture, test, operations, maintenance, and disposal)
of the program. The approach shall include but not be limited to,

-   analytical methods, both quantitative and qualitative as appropriate
    (e.g., hazard analyses and Critical Item risk assessments), to
    assess program flight and ground support hardware and software, and
    facilitate the decision process for risk identification and
    mitigation;

-   provisions for the program approval, by the appropriate government
    interface, of risk associated with hazards and critical items not
    eliminated by design;

-   project/program approval of exceptions, deviations or waivers from
    safety requirements or other requirements with safety or mission
    success impact. The approach and results shall be documented by the
    contractor and auditable by the government.

The contractor shall provide programmatic level assessments of
Integrated Vehicle, element and ground systems requirements changes,
hazards, risk assessments, anomalies, process changes, procedures
changes, and design changes.

As part of Systems Engineering the contractor shall maintain and ensure
technical adequacy and consistency of the Integrated Hazard Analysis and
Reports including the corresponding Fault Trees and Verification
Tracking Logs (DR 1.3.1.1-a, DR 1.3.1.1-b, and DR 1.3.1.1-c). This
includes adherence to guidelines specified in NSTS 22254, and providing
administrative support for the SE&IO system safety tasks. The contractor
shall review updates to element hazard reports and FMEA/CILs for impact
to the Integrated Hazard Reports.

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

The contractor shall implement an approach to flight safety in which the
operation of ground support equipment and flight hardware are assessed
for hazards. The approach shall include flight design and procedurally
controlled activities.

The contractor shall maintain and deliver Hazard Reports in accordance
with NSTS 07700, Vol. V, Information Management requirements.

#### **1.3.1.2 OCCUPATIONAL SAFETY**

The contractor shall implement an occupational safety and health (OS&H)
program that monitors activities to ensure compliance with NASA,
Occupational Safety and Health Administration (OSHA), and other local,
state, or federal regulatory agency requirements. The OS&H program will
be implemented according to a safety plan for each NASA installation
where the contractor performs work on this contract. The plan may be
unified or separate at the contractor's discretion but will follow as
needed the safety and health policies, requirements, and processes at
the specific NASA location.

The contractor shall implement an approach in which testing, ground
operations and maintenance activities in facilities or facility systems
are assessed for hazards. The approach shall indicate the process by
which personnel and property will be protected from injury or harm as a
result of exposure to these hazards. The assessment of operations or
task performed by persons and equipment shall consider (1) the planned
system configurations at each phase of activity; (2) the facility
interfaces; (3) the planned ground and space environment; (4) the
supporting equipment; (5) task sequence; (6) the regulatory safety and
health requirements; (7) the potential for human error, and (8) the
residual risk once hazards are mitigated (including any needed NASA
approvals).

The contractor shall establish processes for reporting and investigating
mishaps. These processes shall cover operations both by the contractor
and by other government and non-government organizations within
operational facilities controlled by the contractor. The approach shall
include provisions for project/program approval of risk associated with
occupational hazards not eliminated or controlled. The approach and
results shall be documented by the contractor and auditable by the
government. As a minimum, the contractor will submit reports on
individual mishaps to the NASA Incident Reporting Information System
(IRIS) including immediate (quick incident) reporting, 24-hour
reporting, and final (ten-day) report as well as selected statistics
such as monthly labor hours and headcount at each NASA installation and
at contractor facilities (lumped together as "off-site"). Reporting,
investigation, and corrective action will be in accordance with
guidelines found in NPR 8621.1, NASA Procedural Requirements for Mishap
Reporting, Investigating, and Recordkeeping.

The contractor shall report and investigate those mishaps resulting in
personnel injuries or damage to NASA property. The report shall include
assessments of accident impacts to cost, schedule and mission
performance, and remedial and corrective actions performed. The
contractor shall provide summary data on all mishaps that occur on NASA
property and contractor operated sites (DR 1.3.1.2-b).

The contractor will provide a safety and health program self evaluation
in accordance with DR 1.3.1.2-d. The contractor may use its most recent
VPP self evaluation report as updated by cover letter or revision of the
report.

### 1.3.2 RELIABILITY AND MAINTAINABILITY

#### **1.3.2.1 FAILURE MODES AND EFFECTS ANALYSIS AND CRITICAL ITEMS LIST (FMEA/CIL)**

The contractor shall maintain and deliver CILs in accordance with NSTS
07700, Volume V, Information Management Requirements.

##### 1.3.2.1.1 FMEA

Development, approval, and maintenance of FMEA shall be in accordance
with NSTS 22206, Space Shuttle Requirements for Preparation and Approval
of FMEA/CIL. The contractor shall develop FMEA for new hardware, and
update baselined FMEA for existing hardware based on needed changes.

##### 1.3.2.1.2 CRITICAL ITEMS LIST

The contractor shall develop and maintain the Critical Item List in
accordance with NSTS 22206, Space Shuttle Requirements for Preparation
and Approval of FMEA/CIL.

#### **1.3.2.2 MAINTAINABILITY**

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

### 1.3.3 QUALITY ASSURANCE

The contractor shall provide a Quality plan (DR 1.3.3) which describes
the establishment, maintenance, and improvement of its quality
management system.

The contractor shall participate in quality management forums as defined
by NSTS 07700.

The contractor shall provide processes for procurement quality defined
in NSTS 5300.4(1D-2).

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

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

The contractor shall provide and maintain, for those items that the
contractor has custody, an Acceptance Data Package (DR 1.3.3.1) for
HW/SW delivery or transfer to the government.

The contractor shall provide for the identification, reporting, and
elimination/disposition of technical issues and conditions, including
non-conformances/problems/anomalies, close calls, anomalous system
performance and material conditions, and failure analysis in accordance
with NSTS 07700 and NSTS 08126; JSC 28035, Program Problem Reporting and
Corrective Action Requirements for Johnson Space Center Government
Furnished Equipment; and SSP 30223, Problem Reporting and Corrective
Action (PRACA) for the Space Station Program, as appropriate.

As applicable, the contractor shall provide rationale for resolution,
the remedial action performed, the recurrence control and corrective
actions taken to preclude recurrence, and determining the effectiveness
of corrective actions. Of special interest are items that potentially
impact or constrain flight or key processing milestones and that
represent safety, mission success, major program schedule milestones, or
cost risks to the government. The contractor shall obtain government
approval of the technical issues and conditions that do not pass the
screening criteria established by the Elements/Projects.

The contractor shall provide access to PRACA documentation, data,
databases, analysis, and related information to the government. The
contractor shall have a data system that allows NASA real time access to
this problem data. The contractor shall initiate (including requesting
government approval) action to change or eliminate requirements that
non-conformance data analysis indicates are unreasonable or unnecessary,
and to improve or change processes which produce products or services
that fail to meet requirements.

#### **1.3.3.2 PROCESS QUALITY**

In order to ensure process quality, the contractor shall perform
required services for Flight Elements (SOW Section 1.4), Integrated
Launch and Landing (SOW Section 1.5), and Flight Operations (SOW Section
1.6) under controlled conditions. These controlled conditions shall
include:

-   Quality planning as described in the Quality Plan (DR 1.3.3).

-   Fabrication operations, article and material controls,
    cleanliness/contamination control, and flight hardware process
    controls described in NSTS 5300.4 (1D-2), section 1D504.

-   Quality records as identified and maintained per SOW paragraph
    1.1.4.1 and as described in DR 1.1.4.1-f.

-   Process metrics as specified in SOW 1.1.2.2 and DR 1.1.2.2-b.

-   Certification processes associated with certification of Contractor
    Furnished Equipment, including operating and maintaining a
    Certification Library.

The contractor shall, as requested, provide data or access to data, on
product and service production processes.

### 1.3.4 ENVIRONMENTAL MANAGEMENT

The contractor shall ensure that SPOC operations and facilities are in
compliance with applicable Federal, State, and local environmental laws,
regulations, and executive orders; NASA Headquarters directives per NPD
8500.1A and NPR 8570.1; and Center directives, requirements, plans, and
procedures per Attachment J-11.

#### **1.3.4.1 GENERAL REQUIREMENTS**

The contractor shall support NASA environmental program requirements
applicable to the SPOC. This support includes response to environmental
data calls, support inspections and audits, providing support to permit
applications and environmental permits, and providing technical support
to meet environmental permit and regulatory requirements.

Contractor responsibilities include, but are not limited to:

-   Preparation of environmental reports for permitted activities and
    regulatory requirements;

-   Promotion of environmental awareness;

-   Natural and cultural resource awareness and protection;

-   Waste minimization and pollution prevention opportunity assessments;

-   Affirmative procurement;

-   Environmental permit compliance;

-   Identification, interpretation, and applicability of new and
    existing environmental requirements as they pertain to SPOC
    operations;

-   Hazardous waste management support for all SPOC operations;

-   Environmental expertise in support of engineering design packages;

-   Development support for environmental requirements identification
    documents, integration of environmental requirements with design
    packages and monitoring of construction for proper implementation of
    environmental requirements;

-   Environmental permit development and implementation;

-   Support to NASA's environmental management system implementation per
    NPR 8553.1A, including environmental management plans, targets, and
    objectives;

-   Support to NASA's Energy and Water Conservation Plans per Attachment
    J-11.

#### **1.3.4.2 RESERVED**

## 1.4 FLIGHT ELEMENTS

**General Processing Requirements**

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

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

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

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

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

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

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

**General Logistics Requirements**

The contractor shall maintain a fully operational logistic system. The
contractor shall procure hardware items from certified suppliers,
manufacture hardware items if certified as a supplier, or repair failed
hardware using a certified facility. In addition, to maintaining flight
equipment assigned to flight element contractors, the contractor shall
maintain flight and flight-type equipment assigned to ground support
equipment, simulators, and off-line laboratories. Manufacturing,
procurement, and repair of hardware items shall be consistent with
Program requirements and directives. The contractor shall utilize
existing certification plans for all manufacturers, repair depots, and
support laboratories. The plans shall comply with Program requirements
and directives. Procurement, manufacture, and repair performance shall
be reported (DR 1.4-c).

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

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

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

The contractor shall provide transportation, shipping, receiving,
storage, warehousing, and distribution services. Transportation services
shall include hardware and equipment transportation for routine and
contingency operations. Transportation, shipping & receiving performance
shall be reported (DR 1.4-c). The contractor shall provide service with
no hardware damage due to transportation or storage. Minor damage judged
to be in the range of the acceptable wear and tear specification or able
to be repaired on-site by standard repair or Material Review action is
acceptable, but in no case shall minor damage impact safety, mission
success or major program schedule milestones. Damage shall be reported
in accordance with SOW Section 1.3.1.2.

The contractor shall maintain an inventory management system.

The contractor shall maintain sufficient inventory to meet the manifest
and report the levels (DR 1.4-c).

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

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

### 1.4.1 ORBITER

The contractor shall plan, control, and perform Orbiter engineering
processing activities. The contractor shall develop and maintain
performance metrics as partnered with the Orbiter Technical Management
Representative (TMR).

#### **1.4.1.1 MISSION AND TURNAROUND REQUIREMENTS**

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

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

The contractor shall provide systems engineering to sustain operational
performance validation, anomaly resolution, corrective action
disposition and mission analysis efforts as required to support the
certificate of flight readiness. The contractor shall provide problem
identification and resolution including failure analysis, hardware
teardown, test, and evaluation, root cause identification, and
corrective action (DR 1.4.1.1), as required, in accordance with SOW
section 1.4. The contractor shall proactively identify aging vehicle
problems and provide corrective action recommendations to maintain
Orbiter vehicle flight readiness and safety of flight. The contractor
shall evaluate vehicle operations and processing changes and notify NASA
of any changes that will violate the engineering basis of certification
of criticality 1/1 hardware during the remaining service life of the
program. Additionally, the contractor will notify NASA of any changes
that will violate the engineering basis of certification of lower
criticality hardware during the remaining service life of the program.

The contractor shall provide accurate Orbiter vehicle configuration
engineering and verification requirements for each flight as required to
support the mission manifest. The contractor shall establish and
document Orbiter turnaround maintenance requirements and specifications
(DR 1.4.1.1.3-a). The contractor shall submit changes to the JSC 08934
Shuttle Operational Data Book (DR 1.4.1.6.1-a). The contractor shall
analyze Orbiter vehicle configuration, mass properties, certification
status, and anomaly dispositions (DR 1.4.1.6.1-d) to determine whether
the requirements for each pending mission have been complied with. The
contractor shall prepare or evaluate launch commit criteria and flight
rule changes. The contractor shall prepare instrumentation configuration
information (DR 1.4.1.6.1-g) for launch and flight support. The
contractor shall provide Orbiter engineering and technical support for
the Orbiter processing operations identified in SOW paragraphs 1.4.1.2,
1.4.1.3, 1.4.1.4, and 1.5. These activities shall encompass vehicle
subsystems.

The contractor shall provide Pre-Launch/In-Flight/Post-Flight debris
assessments in support of each shuttle mission.

The contractor shall incorporate vehicle hardware Engineering Orders
(EOs) into production drawing releases on a priority basis as
coordinated with contractor Orbiter Element.

The contractor shall provide analysis support to the Wing Leading Edge
Impact Detection System (IDS). The contractor shall maintain critical
skills sufficient to support External Tank (ET) Disconnect Tip Load and
Angle, Problem Report (PR) Resolution, and Line Replaceable Unit (LRU)
Remove and Replace (R&R).

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

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

##### 1.4.1.1.1 RESERVED

##### 1.4.1.1.2 RESERVED

#### **1.4.1.2 ORBITER LOGISTICS**

The contractor shall provide Orbiter logistics functions in a manner
consistent with SOW section 1.4 for hardware element accountability and
general logistics requirements. The contractor shall obtain government
approval before cannibalizing Orbiter hardware to fill requests or
removing hardware prior to OMDP to support fill requests. Performance
shall be reported in accordance with DR 1.4-c. Hardware provisioning
shall include all spares and consumables for Orbiter processing and
flight. High Value Spares, replacement parts with a unit cost of \$1M or
more, shall be subject to the procedures of H.35, [Provisioning
Procedures]{.underline}. Hardware configuration management shall be in
compliance with the requirements specified in NSTS 07700, Volume IV with
implementation as defined in SOW section 1.4.1.1 and 1.4.1.5.

#### **1.4.1.3 ORBITER TURNAROUND PROCESSING**

The contractor shall plan, control and perform all turnaround processing
activities in a manner consistent with SOW section 1.4 for hardware
accountability and general processing requirements. The contractor shall
prepare the Orbiter for flight, including special action requirements
(DR 1.4.1.1.2-a) and support for integrated operations as specified in
SOW section 1.5. This shall include off-line turnaround processing of
LRUs. The contractor shall accomplish all documented Orbiter ground
turnaround configuration and verification requirements and report all
requirements not accomplished to NASA. The contractor shall identify,
document and provide NASA with access to all out-of-specification
turnaround verification results. The contractor shall assess, plan,
prepare, and execute modification and mission kit installation work
authorization documents and conduct subsystem and system verification
testing.

The contractor shall provide the capability to respond to multiple short
processing flows, work additional content in normal flows, accelerate
the completion of flight and ground hardware modifications, and perform
special in-flow inspections and maintenance to ensure the design
integrity and operational safety of the vehicle.

#### **1.4.1.4 ORBITER FERRY OPERATIONS**

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

#### **1.4.1.5 ORBITER HARDWARE PRODUCTION AND SUPPORT TASKS**

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

The contractor shall participate in and support program meetings and
reviews supporting the prioritization process, including presentations
covering the projected resource requirements computed by the process and
updates to the baseline work plan; and the coordination and resolution
of action items with NASA resulting from baseline work plan reviews
using the process.

A single effort in excess of \$3M shall be subject to workload
prioritization with NASA. All or portions of this single effort
authorized in excess of the \$3M threshold that cannot be accommodated
via workload prioritization shall be subject to Article H.35,
Provisioning Procedures. After initiation of separate approved efforts
aggregating \$7M over the basic period of performance, each of which
could not be accommodated via workload prioritization, all or portions
of any new effort that cannot be accomplished via workload
prioritization shall be subject to Article H.35, Provisioning
Procedures. Workload prioritization will be accomplished using a
partnered resource estimating process.

##### 1.4.1.5.1 RESERVED

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

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

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

The contractor shall incorporate vehicle hardware Engineering Orders
(EOs) into production drawing releases on a priority basis as
coordinated with contractor Orbiter Element.

###### 1.4.1.5.2.1 RESERVED

##### 1.4.1.5.3 RESERVED

##### 1.4.1.5.4 RESERVED

##### 1.4.1.5.5 RESERVED

##### 1.4.1.5.6 GROUND SUPPORT EQUIPMENT AND TOOLING SUPPORT

The contractor shall provide for ongoing recurring maintenance of active
GSE, STE, Tooling, and Facilities Equipment required to support ongoing
SPOC activities at Palmdale. Such ongoing activities include, but are
not limited to, Logistics (spares), Coldplate manufacture, Orbiter Mod
Kit Fabrication, TPS/TCS manufacturing, Machining and Assemble,
Electrical Fabrication and Assemble, and Payload Integration Nominal
Cost Hardware (PINCH).

##### 1.4.1.5.7 ORBITER STRUCTURES IMPROVEMENTS

The contractor shall perform evaluations of structural improvements as
directed by the Structures Problem Resolution Team (PRT). This task is
limited to: (1) evaluations limited to minor structural modifications to
the Orbiter (includes the development of cost and schedule); (2)
modification engineering for small structural changes (allows for
purchase of minor structural hardware, such as washers and brackets);
and (3) structures related tasks as defined by the Structures PRT.

##### 1.4.1.5.8 THERMAL PROTECTION SYSTEM (TPS) SUPPORT

The contractor shall perform evaluations of Thermal Protection System
(TPS) improvements as directed by the TPS Problem Resolution Team (PRT).
This task is limited to: (1) evaluations limited to minor TPS
modifications to the Orbiter (includes the development of cost and
schedule); (2) modification engineering for small TPS changes (allows
for purchase of minor TPS hardware); and (3) miscellaneous TPS related
tasks as defined by the TPS PRT.

##### 1.4.1.5.9 HARDWARE STUDIES

The contractor shall perform small studies associated with the Orbiter
element. This effort shall include development and evaluation of
options, technical coordination, development of Rough Order Magnitude
(ROM) and Budgetary & Planning (B&P) estimates, and preparation of
briefings for presentation to NASA.

##### 1.4.1.5.10 ORBITER CREW SYSTEMS EQUIPMENT

The contractor shall design, test, fabricate and sustain Orbiter Crew
Systems equipment and trainer hardware as defined in PDP
7.21-MV-CREWSYS. All related documentation and materials associated with
the design, test, fabrication and sustaining engineering of Orbiter Crew
Systems equipment and trainer hardware shall be provided to the
Government upon request. The contractor shall also include the design,
test, fabrication and sustaining engineering for the Port and Starboard
Lightweight Tool Stowage Assemblies (LWTSAs) in support of ISS and EVA
activities.

#### **1.4.1.6 ISS TECHNICAL INTEGRATION SUPPORT TO STATION APDS**

The contractor shall provide support to the NASA Docking System
Integrated Product Team (DSIPT) in the management and oversight of
International Space Station (ISS) installed Russian hardware that is
Space Station unique. Effort includes such activities as generation of
English-Russian documents for maintenance and repair activities or
Russian Formular updates, and Russian-American procedure generation
(translation activities only as needed to clarify/correct Government
provided translations); Orbiter Docking System (ODS) Russian hardware
logistics support, and the retest of Russian Line Replaceable Unit
(LRUs) on the Brassboard.

### 1.4.2 SOLID ROCKET BOOSTER (SRB)

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

#### **1.4.2.1 SRB ELEMENT PROCESSING**

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

##### 1.4.2.1.1 RESERVED

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

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

##### 1.4.2.2.1 RESERVED

#### **1.4.2.3 SRB STAND ALONE LOGISTICS**

The contractor shall provide the necessary level of stand alone, SRB
unique logistics to support all SRB tasks.

##### 1.4.2.3.1 RESERVED

#### **1.4.2.4 RESERVED**

#### **1.4.2.5 SRB FLIGHT SYSTEMS DESIGN RESPONSIBILITY**

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

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

The contractor shall be responsible for SRB Loads & Environments
criteria and requirements. Responsibility includes development,
analyses, update & control activities of the following products:

-   SRB Design Loads

-   SRB Integrated Thermal Environments

-   SRB Decent Trajectory Database

-   SRB Structural Math Models

-   SRB/RSRM Interface Loads

-   SRB Thermal Design Data

-   SRB Load Indicator Equations

-   and Vibration, Shock, & Acoustic Design/Test Criteria

-   SRB Ascent & Descent Venting Environments

-   Descent Thermal Environments

-   High-Frequency Component Loads

-   Ascent & Descent Aerodynamics

-   Descent Acoustic Environments

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

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

##### 1.4.2.5.1 RESERVED

##### 1.4.2.5.2 RESERVED

##### 1.4.2.5.3 RESERVED

##### 1.4.2.5.4 RESERVED

#### **1.4.2.6 SRB HARDWARE/SYSTEMS ASSEMBLY AND REFURBISHMENT PROCESSING FACILITIES AND GROUND SYSTEMS DESIGN RESPONSIBILITY**

The contractor shall perform sustaining engineering on all Ground
Support Equipment (GSE), Electrical Support Equipment (ESE) and
Production Support Equipment (PSE) which are used to support hardware
processing at the SRB facilities. The contractor shall perform
sustaining engineering on all SRB facilities and facility systems in
accordance with the requirements of SOW paragraph 1.5.5 and Attachment
J-9.

#### **1.4.2.7 RESERVED**

#### **1.4.2.8 SRB RECOVERY OPERATIONS AND ET TRANSPORTATION**

The contractor shall recover and retrieve the spent boosters,
parachutes, and frustums from the Atlantic Ocean and transport them to
the CCAS Hangar AF. The contractor shall safe and disassemble the
hardware, conduct post-flight inspections, document anomalies, prepare
the hardware for shipment off-site, and deliver parachute assemblies
on-site for processing.

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

The contractor will provide operational capability for the Marine Weibel
Radar Systems to track launch debris.

#### **1.4.2.9 RSRM STATIC FIRING SUPPORT**

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

#### **1.4.2.10 SRB MODIFICATIONS**

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

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

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

#### **1.4.2.12 ACQUISITION SUPPORT**

The contractor shall procure Aft Separation Bolts and NSI pressure
cartridges for the Tail Service Mast. In addition, the contractor shall
procure and ship System Tunnel Floor Plates to the RSRM contractor to
support each mission. The contractor shall provide the Orbiter Drag
Chute to support each mission and shall provide maintenance and repair,
as required, for the Integrated Receiver Decoders (IRDs) used by Launch
& Landing.

### 1.4.3 FLIGHT SOFTWARE

The contractor shall develop, verify, and implement Flight Software
(FSW) for the SSP. The Primary Avionics Software System (PASS), Back-up
Flight System (BFS), Multifunction Electronics Display Subsystem (MEDS),
Miniature Airborne Global Positioning System (GPS) Receiver Shuttle -- 3
String (MAGRS--3S) firmware, and avionics system support activities are
to be managed by the contractor with the direct involvement of the
government in accordance with the baselined Shuttle Avionics Software
Control Board (SASCB) software processes (Software Change Request (SCR)
89050-SASCB Process Documentation Overview). In accordance with NSTS
08271, FSW Verification and Validation Requirements, the contractor
shall perform requirements analysis, design, development, testing,
certification, and maintenance of the avionics software for the Data
Processing System (DPS) of the Space Shuttle Orbiter. The contractor
shall establish general and specific interfaces with other NASA-selected
contractors for coordination and data exchanges necessary in the
formulation, execution, and verification of Shuttle FSW and FSW
Application Tools (FSWAT) ground software. The contractor shall ensure
flight readiness by meeting FSW Software Readiness Review (SRR)
requirements in accordance with NSTS 08117, Requirements and Procedures
for Certification of Flight Readiness. The contractor shall provide FSW
quality metrics and reports to NASA (DR 1.4.3-a).

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

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

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

The contractor shall support computer access security, data integrity,
implementation, test, and maintenance of the Software Development
Facility (SDF) for all coding of BFS and FSW application tools. The
overall computer security and data integrity requirements shall be
consistent with NASA Procedures and Requirements (NPR) 2810.1A.

The contractor shall maintain the Measurement and Stimuli (MAST) II
database including definition and incorporation of hardware component
calibration coefficients and curves, measurement channelization, and
telemetry format requirements in accordance with current baseline
process SCR 89053-MAST II/STAR Reconfiguration. The contractor shall
resolve payload data interleaver compiler bandwidth and instruction
issues. The contractor shall provide a "help desk" capability to
facilitate user interaction (DR 1.4.3.1-k, DR 1.4.3.1-n, and DR
1.4.3.1-q).

The contractor shall perform MM pre-installation processing, install as
a total or partial load and perform memory dumps and compares to ensure
proper installation. Included is the assessment of the software delivery
to determine any Ground Operation Applications Language (GOAL)
application/procedure impacts and the provision of test support and
procedure execution.

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

#### **1.4.3.2 FLIGHT SOFTWARE TESTING**

The contractor shall verify that performance of the integrated Space
Shuttle Vehicle (SSV) avionics system hardware, software, and its
associated interfaces meets program requirements. Elements included in
the integrated avionics are the PASS, BFS, MEDS, MAGRS-3S, and all SSV
avionics hardware/software elements including the Space Shuttle Main
Engine (SSME) controller.

The contractor shall prepare avionics system verification test
requirements that utilize Shuttle Avionics Integration Laboratory
(SAIL), Software Reconfiguration Facility (SRF), audits, or other
appropriate methods to assess system compliance with requirements.
Verification requirements shall be provided for: Mission verification,
new Operational Increment (OI) testing, SAIL regression testing, Shuttle
hardware upgrade verification, SAIL site acceptance, and system
integration verification. Mission-unique testing shall include software
patches, Detailed Test Objectives (DTOs), and General Purpose Computer
(GPC) memory patches (GMEMS) (DR 1.4.3.2-a, DR 1.4.3.2-b, DR 1.4.3.2-c,
and DR 1.4.3.2-d).

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

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

#### **1.4.3.3 AVIONICS AND SOFTWARE SYSTEM SUPPORT**

The contractor shall be responsible for all aspects of the associated
Principal Function (PF) software design as defined in the STS Flight
Software Functional Subsystem Software Requirements (FSSRs), Space
Shuttle Computer Program Development Specifications (CPDSs), and Program
Requirements Documents (PRDs). This role is designated as Principal
Function Manager with the responsibility to serve as the primary expert
for all aspects of each FSW PF. The contractor shall be responsible for
all aspects of the design, definition, and mission selection of I-load
categories and occurrences for associated PF as defined in the FSSRs and
PRDs. This role is designated as Initialization Load (I-Load) Owner with
the responsibility for one or more I-Load categories. SASCB SCR 98350,
SASCB FSW Requirements Management Assignment Baseline, and SCR 98032,
FSW I-Load Owner Assignments govern the individual designations.

The contractor shall develop and establish flight software change
requirements for STS missions, Orbiter Major Modification (OMM)
processing, and pre- and post-launch ground checkout. The contractor
shall prepare FSW change proposals and change requests, and provide
recommendations for long-term definition of OI changes as defined in the
SASCB 3-year plan. The contractor shall provide impact assessments and
recommendations to the SASCB in response to FSW changes proposed by FSW
Change Proposals (FCPs), SCRs, I-Load Data Change Requests (DCRs),
Discrepancy Reports (DRs), Requirements Issue Tracking (RIT) forms, SSME
Software Authorization Notices (SANs), or Requirements Change Notices
(RCNs) in accordance with the current baselined software processes, SCR
89052 - Space Shuttle Flight Software Discrepancy Report Procedures, SCR
89054 - I-Load Data Change Request (DCR), and SCR 89056 - Space Shuttle
Main Engine Controller (SSMEC) FSW process (DR 1.4.3.3-c, DR 1.4.3.3-f,
and DR 1.4.3.3-y).

The contractor shall provide SASCB risk assessments in accordance with
the Risk Management Plan, SFOC-PG9604, for SCRs, DRs, and I-Load DCRs.
Risk assessments shall provide impacts to baselined Hazard Reports. A
mapping of Principal Functions and I-Load categories to baselined Hazard
Reports shall be maintained (DR 1.4.3.3.-ab).

The contractor shall review changes to the Flight Data File and Flight
Rules to ensure that the planned use of the flight software (PASS, BFS,
MEDS, and MAGRS-3S) is consistent with software functionality and
vehicle certification.

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

The contractor shall maintain FSW requirements documentation including
the CPDSs, FSSR, and PRD. The contractor shall update this documentation
and the PASS/BFS Interface Control Documents (ICD) for each approved OI.
The contractor shall maintain an I-Load Selection Criteria data book
with which to perform an independent selection of I-Loads for
mission-reconfigurable parameters. The contractor shall provide Software
Version Description Documents (VDDs) for BFS data set deliveries as
defined in JSC-22320 (Flight Software Class 1 Integration Plan (CIPP and
JSC-08338 (Shuttle Avionics Mass Memory Computer Program Integration
Plan (MIP)) (DR 1.4.3.3-o, DR 1.4.3.3-p, DR 1.4.3.3-q, DR 1.4.3.3-s, DR
1.4.3.3-t, DR 1.4.3.3-u, and DR 1.4.3.3-w).

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

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

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

#### **1.4.3.4 BFS FLIGHT SOFTWARE RECONFIGURATION**

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

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

#### **1.4.3.5 BFS FLIGHT SOFTWARE MODIFICATIONS**

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

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

#### **1.4.3.6 FLIGHT OPERATIONS SUPPORT**

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

#### **1.4.3.7 PASS FLIGHT SOFTWARE PROCESSING**

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

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

The contractor shall support computer security, data integrity,
implementation, test and maintenance of the Software Development
Facility (SDF) to be used for all coding of FSW and FSWAT. The
contractor shall provide Resources Access Control Facility (RACF)
profiles and administer user access for NASA and contract users. The
overall computer security and data integrity requirements shall be
consistent with NASA Procedural Requirements (NPR) 2810.1A. The overall
requirements, implementation, and maintenance shall be consistent with
all SDF policies and procedures approved by the SPF Configuration
Control Board (DR 1.4.3.7-a, DR 1.4.3.7-b, DR 1.4.3.7-c, DR 1.4.3.7-d,
DR 1.4.3.7-e, DR 1.4.3.7-f, DR 1.4.3.7-h, DR 1.4.3.7-i, and DR
1.4.3.7-j).

#### **1.4.3.8 PASS FLIGHT SOFTWARE TOOLS**

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

The contractor shall perform impact analyses of the proposed tool
changes relative to flight software OIs, considering compatibility with
other Support Software Change Requests (SSCRs) and Support Software
Discrepancy Reports (SSDRs). The contractor shall support the processes,
procedures, documentation, and databases for the Support Software
Configuration Control Board (SSCCB).

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

Facility management of the ASDEP shall be supported, including computer
security, system assurance, user support, and requirements,
implementation, verification, and configuration control of the system
tools.

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

The contractor shall be responsible for the NASA ADP (Automated Data
Processing) Consolidation Center (NACC) insight for the Space Shuttle
Program Office. This will include Shuttle Program Office NACC (SPON)
system integration (data base administration, system assurance,
change/risk management), Application Support (resource management), and
User Support (ID administration, Help Desk support) (DR 1.4.3.8-a, DR
1.4.3.8-b, DR 1.4.3.8-c, DR 1.4.3.8-d, DR 1.4.3.8-e, DR 1.4.3.8-f, DR
1.4.3.8-g, DR 1.4.3.8-h, and DR 1.4.3.8-i).

#### **1.4.3.9 PASS FLIGHT SOFTWARE IMPLEMENTATION**

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

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

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

Software delivery shall occur at CI of each FSW OI and as needed for
late changes as defined in the Flight Software Class 1 Integration Plan
(CIP) (JSC 22320) (DR 1.4.3.9-a, DR 1.4.3.9-b, DR 1.4.3.9-c, DR
1.4.3.9-d, DR 1.4.3.9-e, DR 1.4.3.9-f, DR 1.4.3.9-g, DR 1.4.3.9-h, DR
1.4.3.9-i, DR 1.4.3.9-j, DR 1.4.3.9-k, DR 1.4.3.9-l, DR 1.4.3.9-m, DR
1.4.3.9-n, DR 1.4.3.9-o, and DR 1.4.3.9-p).

#### **1.4.3.10 PASS FLIGHT SOFTWARE RECONFIGURATION AND MMU INTEGRATION**

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

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

#### **1.4.3.11 GROUND FACILITY DATA PROCESSING SYSTEM**

The contractor shall perform the maintenance, modification, and testing
of the DPS components used in the listed ground facilities including,
but not limited to, the General Purpose Computers, MCDS Keyboard,
Simulation Interface Device (SID), FEIDS, and Mass Memory Unit Simulator
(MMUS). The contractor shall also provide technical support for the
resolution of hardware and related software problems in the facilities
listed below (DR 1.4.3.11-a, DR 1.4.3.11-b, DR 1.4.3.11-c, and DR
1.4.3.11-d):

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

b.  JSC Avionics Engineering Laboratory (JAEL)

c.  Software Production Facility (SPF)

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

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

f.  Guidance and Navigation Simulator (GNS)

g.  Shuttle Training Aircraft (STA)

h.  KSC Avionics Test Station (KATS)

#### **1.4.3.12 PASS FLIGHT SOFTWARE MAINTENANCE**

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

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

#### **1.4.3.13 MEDS MODIFICATION AND MAINTENANCE**

The contractor shall perform the requirements analysis, design,
implementation, verification, certification, configuration control, and
maintenance of the MEDS software in accordance with the current
baselined software processes, SCR 89051, Space Shuttle Software Change
Request (SCR) Process, and SCR 89052, Space Shuttle Flight Software
Discrepancy Report Procedures. The contractor's responsibility includes
the Integrated Display Processor (IDP) software, the Multifunction
Display Unit Function (MDUF) software, the Analog-to-Digital Converter
Function (ADCF) firmware, the Integrated Display Procesor-Bootstrap
Loader (IDP-BSL) firmware, the Multifunction Electronic Display
Unit-User Development Interface (MDU-UDI) firmware, Multifunction
Electronic Display System Test Station (MTS) software, IDP support
software, Multifunction Display Unit Function Formal Verification Test
(MDUF FVT) software, Multifunction Display Unit Object Manipulator
(MOM), ADCF FVT Test Scripts, and the Portable Loader software.

The contractor shall prepare and present MEDS software change proposals,
change requests, and FSW DRs in accordance with the current baselined
software processes. The contractor shall provide recommendations for
long-term definition of MEDS Version Increments (VIs). The contractor
shall be responsible for configuration control of the MEDS
documentation, media, and tools required to maintain the MEDS software.

The contractor shall be responsible for the design, development,
verification, configuration control, and maintenance of the non-flight
software tools used for existing MEDS software product generation,
verification, delivery, maintenance, configuration control, performance
analysis, and problem investigation (DR 1.4.3.13-a, DR 1.4.3.13-d, DR
1.4.3.13-e, DR 1.4.3.13-f, DR 1.4.3.13-j, DR 1.4.3.13-k, DR 1.4.3.13-l,
DR 1.4.3.13-m, DR 1.4.3.13-n, DR 1.4.3.13-o, DR 1.4.3.13-p, DR
1.4.3.13-q, DR 1.4.3.13-r, DR 1.4.3.13-s, DR 1.4.3.13-t, DR 1.4.3.13-u,
DR 1.4.3.13-v, DR 1.4.3.13-w, DR 1.4.3.13-x, DR 1.4.3.13-y, and DR
1.4.3.13-z).

#### **1.4.3.14 MEDS SOFTWARE TEST AND OPERATIONS SUPPORT**

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

The contractor shall perform the design, implementation, and maintenance
of specific test software (interim releases) required by avionics system
facilities, such as the SAIL, Shuttle Mission Simulator (SMS), Shuttle
Training Aircraft (STA), and KSC facilities in support of checkout and
turnaround operations (DR 1.4.3.14-a and DR 1.4.3.14-b).

#### **1.4.3.15 PORTABLE COMPUTER SOFTWARE SYSTEMS FOR SPACEFLIGHT**

The contractor shall provide integration and coordination for the
Payload and General Support Computer (PGSC) processes and procedures.
The contractor shall create and maintain integrated PGSC development and
testing plans. Formal integrated testing plans shall be provided for
NASA approval. The contractor shall provide recommendation for improving
the PGSC processes and procedures. The contractor shall review new
PGSC-related hardware and software to determine its applicability to
PGSC-related activities and recommend appropriate responses.

The contractor shall provide hardware (including peripherals) systems
engineering, integration support and coordination to the POCCB. The
contractor shall provide software engineering, procedures, integration
support, and coordination to the POCCB. The contractor shall review
PGSC-related change paperwork and identify known issues with the
proposed changes to the POCCB chair (DR 1.4.3.15-b).

The contractor shall review all CoFR-related PGSC activities and verify
that the required activities have been properly completed and
signed-off. The contractor shall support all CoFR reviews related to the
PGSCs.The contractor shall deliver software that reads decommutated
downlist data generated by the Pulse Control Modulated Master Unit
(PCMMU) in a format and timetable specified in the Data Requirements
Description (DRD) document for the PGSCs. The contractor shall also be
responsible for system definition development for future PCMMU functions
that are compatible with present and future Space Shuttle portable
computer platforms (DR 1.4.3.15-a).

#### **1.4.3.16 VEHICLE AND PAYLOAD DATA COLLECTION/ RECONFIGURATION**

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

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

The contractor shall develop the payload requirements needed to
reconfigure the appropriate software for Shuttle vehicle and ground
facilities in support of SSP missions. The contractor shall work with
payload suppliers and the Shuttle community in order to develop,
baseline, and maintain unique Payload Integration Plan (PIP) Annex 4 in
accordance with the PIP schedule and develop the requirements necessary
to perform flight specific data reconfiguration. The contractor shall
maintain the generic blank book (NSTS 21000-A04) (DR 1.4.3.16-d and DR
1.4.3.16-g).

The contractor shall provide the reconfiguration products to users as
specified in the Data Integration Plan (DIP) and the Shuttle Avionics
Mass Memory Unit Computer Integration Plan in the correct format.
Products shall be delivered in support of mission specific schedules.
The contractor shall provide manifest assessments in support of the SSP.
Products shall be delivered as required for: Base, ADTL, Special Build
or Patch (DR 1.4.3.16-a, DR 1.4.3.16-e, DR 1.4.3.16-f, and DR
1.4.3.16-h).

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

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

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

#### **1.4.3.17 SHUTTLE AVIONICS INTEGRATION LABORATORY (SAIL)**

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

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

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

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

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

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

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

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

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

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

#### **1.4.3.18 MINIATURE AIRBORNE GLOBAL POSITIONING SYSTEM (GPS) RECEIVER SHUTTLE -- 3 STRING (MAGRS-3S)**

The contractor shall manage and perform the requirements definition,
analysis, design, implementation, verification, certification,
configuration control, test, and maintenance of the MAGRS-3S software
"link" for the Space Shuttle Orbiter in accordance to established SASCB
processes. Included in this responsibility is Orbiter installation and
verification of software updates. The contractor shall perform internal
software quality assurance of the processes and procedures used to
generate the MAGRS-3S products.

The contractor shall maintain configuration control of all MAGRS-3S
products delivered to NASA. Configuration control shall provide full
traceability from NASA approved requirements to the individual items
delivered and shall be applied to each software release.

The contractor shall process all MAGRS-3S discrepancies which cover all
analysis, recommendations, and corrective actions necessary to close
MAGRS-3S DRs at the SASCB as defined in SCR 89052, Space Shuttle Flight
Software Discrepancy Report (DR) Process.

The contractor shall provide anomaly resolution support for the MAGRS-3S
software. The contractor shall provide MAGRS-3S technical support to
program meetings as required (DR 1.4.3.18-a, DR 1.4.3.18-b, DR
1.4.3.18-c, DR 1.4.3.18-d, DR 1.4.3.18-e, DR 1.4.3.18-f, and DR
1.4.3.18-g).

### 1.4.4 EXTERNAL TANK (ET)

The contractor shall plan, control, and perform ET processing
activities. A Memorandum of Understanding shall be established between
the contractor and the ET element contractor that reflects the interface
relationships as defined in Memorandum of Understanding, USA/LMMSS-001,
current version, entitled "ET Launch Support Services Contractor/Space
Program Operations Contractor."

#### **1.4.4.1 ET ELEMENT PROCESSING**

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

#### **1.4.4.2 ET LOGISTICS**

Reference SOW section 1.4 for general logistics requirements.

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

#### **1.4.4.3 RESERVED**

#### **1.4.4.4 RESERVED**

#### **1.4.4.5 ET MODIFICATIONS**

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

#### **1.4.4.6 RESERVED**

#### **1.4.4.7 RESERVED**

### 1.4.5 REUSABLE SOLID ROCKET MOTOR (RSRM)

The contractor shall plan, control, and perform RSRM processing
activities. A Memorandum of Understanding shall be established between
the contractor and the RSRM element contractor that reflects the
interface relationships as defined in Memorandum of Understanding,
USA/THI-001, current version, entitled "RSRM Launch Support Services
Contractor/Space Program Operations Contractor.

#### **1.4.5.1 RSRM ELEMENT PROCESSING**

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

#### **1.4.5.2 RSRM LOGISTICS**

Reference SOW section 1.4 for general logistics requirements.

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

#### **1.4.5.3 RSRM RECOVERY OPERATIONS**

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

#### **1.4.5.4 RESERVED**

#### **1.4.5.5 RSRM MODIFICATIONS**

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

#### **1.4.5.6 RESERVED**

#### **1.4.5.7 RESERVED**

### 1.4.6 SPACE SHUTTLE MAIN ENGINE (SSME)

The contractor shall plan, control, and perform SSME processing
activities. A Memorandum of Understanding shall be established between
the contractor and the SSME element contractor that reflects the
interface relationships as defined in Memorandum of Understanding,
USA/ROC-001, current revision entitled "SSME Launch Support Services
Contractor/Space Program Operations Contractor."

#### **1.4.6.1 SSME ELEMENT PROCESSING**

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

#### **1.4.6.2 SSME LOGISTICS**

Reference SOW section 1.4 for general logistics requirements.

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

#### **1.4.6.3 SSME LANDING OPERATIONS**

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

#### **1.4.6.4 RESERVED**

#### **1.4.6.5 SSME MODIFICATIONS**

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

#### **1.4.6.6 RESERVED**

#### **1.4.6.7 RESERVED**

### 1.4.7 SHUTTLE REMOTE MANIPULATOR SYSTEM (SRMS) & ORBITER BOOM SENSOR SYSTEM (OBSS) PROCESSING

The contractor shall process the SRMS and OBSS in accordance with
established requirements. This includes off-line testing, installation,
and turnaround testing. Prior to rollout, the contractor shall verify
that the SRMS and OBSS, as applicable, are capable of supporting the
mission or identify issues and provide recommendations for resolution.

### 1.4.8 RESERVED

### 1.4.9 FLIGHT CREW EQUIPMENT

The contractor shall perform Flight Crew Equipment processing related
activities necessary to provide and maintain flight and training
hardware and services in support of the SSP and ISSP. All hardware shall
be provided on an as needed basis and meet design and operational
requirements. These requirements include, but are not limited to:
processing, maintenance, training and flight support, crew reviews, pre
and post flight shipset integration and packing operations, inventory
management, and logistics including Ground Support Equipment management.
For the ISSP, export compliant shipping documentation shall be prepared
as required. Major developmental efforts shall be authorized pursuant to
H.35, Provisioning Procedures.

Exhibit 1.4.9 describes the Flight Crew Equipment Groups supporting both
the SSP and ISSP flight and training requirements. This exhibit
represents the broad categories of SPOC accountable Flight Crew
Equipment and includes all approved processing items within these broad
categories.

For criticality 1 subsystems and hardware with program baselined hazards
and Critical Items Lists (CIL) requirements transferred to the
contractor for Maintenance and Operations, the contractor shall ensure
that subsystem processing procedure changes, engineering drawing
changes, and Material Review (MR) dispositions do not impact
certification. For lower criticality hardware transferred to the
contractor for Maintenance and Operations, the contractor will ensure
that subsystem processing procedure changes, engineering drawing
changes, and MR dispositions do not impact certification.

The contractor shall submit engineering drawings and associated lists
per DR 1.4.9-a.

The contractor shall submit a Food Contamination Control Plan describing
the overall approach for implementation of an effective contamination
control program for the food and the food production facility (DR
1.4.9-b). The contractor shall maintain Flight Food Acceptance
Documentation which shall show adherence of the food processes,
procedures, and analyses to required standards and specifications and
provide the basis for acceptance of the flight food assemblies for each
mission (DR 1.4.9-c).

The contractor shall submit Post Test Reports to fully document results
of testing and events of importance that involve support equipment, Crew
Escape Equipment (flight and training), or as requested by NASA (DR
1.4.9 -d).

The contractor shall submit to NASA PRACA Reportable Problems (PPRs) for
ISSP and SSP items which the contractor has maintenance and operation
responsibility (DR 1.4.9 -e). The contractor shall maintain a system for
the reviewing and statusing open problems. The contractor shall support
NASA in the dispositions of PPRs for ISSP and SSP items. Control numbers
for the contractor generated PPRs (i.e. FIARs) shall be provided by the
JSC PRACA Center. For items which the contractor has responsibility, the
contractor also shall support:

a\. Problem investigations and reviews

b\. Isolation of failures and determine probable cause, mode and
corrective/preventive action

The contractor shall submit to NASA an Equipment Inventory Report which
provides visibility of the inventory of material, parts, subassemblies,
and end items (DR 1.4.9-f).

The contractor shall generate a JF 1027, Pre-Shipment Readiness per
NT-CWI-004 or NASA approved equivalent prior to integration for flight.

### The contractor shall develop and maintain performance metrics as partnered with the Orbiter Technical Management Representative (TMR).

### 

### 

### 1.4.9.1 RESERVED

#### **1.4.9.2 RESERVED**

#### **1.4.9.3 RESERVED**

##### 1.4.9.3.1 RESERVED

#### **1.4.9.4 RESERVED**

## 1.5 INTEGRATED LAUNCH & LANDING OPERATIONS

For purposes of this SOW, integrated launch and landing (or post launch)
operations are defined as follows:

> Integrated Orbiter operations begin with the connection of the Orbiter
> sling assembly to the Orbiter for Orbiter to ET mate operations in the
> Vehicle Assembly Building (VAB) transfer aisle. Integrated Orbiter
> landing operations begin with preparations for End of Mission or
> Contingency landings and terminate with Orbiter spotting in the OPF at
> KSC or Mate-Demate Device at DFRC.
>
> Integrated booster operations begin with the SRB aft skirt and RSRM
> aft segment mate and buildup in the Rotation, Processing and Surge
> Facility (RPSF). RSRM and SRB integrated operations terminate at the
> completion of preparations for shipment.
>
> Integrated SSME operations begin with engine installation into the
> Orbiter. SSME post launch-integrated operations terminate after engine
> removal from the Orbiter in the OPF.
>
> Integrated ET operations begin with ET delivery to the VAB. However,
> stand‑alone ET operations in the checkout cell shall be accounted for
> under SOW section 1.4.4.1.
>
> Integrated payload operations begin with payload removal from the
> payload canister for installation into the Orbiter for horizontal or
> vertical payload installation and experiment arrival at the OPF/Pad
> for middeck experiments. Payload integrated operations terminate after
> removal from the Orbiter. The contractor shall support the Payload
> processing contractor in Payload operations at KSC.

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

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

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

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

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

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

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

### 1.5.1 VEHICLE INTEGRATION

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

#### **1.5.1.1 ELEMENT/CARGO PLANNING & INTEGRATION**

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

#### **1.5.1.2 PAYLOAD INSTALLATION AND TESTING**

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

#### **1.5.1.3 INTEGRATED TEST EXECUTION**

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

### 1.5.2 LAUNCH PREPARATIONS

The contractor shall plan and perform all tasks in preparation for SSV
launch.

#### **1.5.2.1 LAUNCH REQUIREMENTS**

The contractor shall develop and maintain integrated launch procedures
and work authorization documents that implement launch requirements. The
contractor shall implement Launch Commit Criteria documented in NSTS
16007. The contractor shall maintain and update the mission unique
Ground Launch Sequencer (GLS) Configurations document to support launch
operations (DR 1.5.2.1).

#### **1.5.2.2 LAUNCH PLANNING**

The contractor shall support the NASA Launch Countdown Working Group
(LCWG) efforts to integrate mission specific requirement into launch
countdown schedules and procedures. The contractor shall provide work
control functions in support of launch countdown including developing,
updating, and distributing launch countdown procedures, plans, and
schedules. Contingency plans and procedures shall be maintained current,
and personnel and resources made available to respond to Space Shuttle
contingencies. The contractor shall develop and implement methods to
improve launch support capabilities, including but not limited to, the
identification, mitigation, and control of risks; effective problem
resolution; optimization of resources; and adherence to schedules.

#### **1.5.2.3 LAUNCH TEAM TRAINING**

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

#### **1.5.2.4 LAUNCH READINESS**

The contractor shall develop and implement an auditable approach to
verify and certify contractor launch and landing readiness. The approach
shall include, as a minimum, the ability to satisfy the requirements of
NSTS 08117. This includes, but is not limited to, methods for closed
loop tracking of configuration and OMRS requirements satisfaction,
constraints management, anomaly dispositions verified acceptable for
flight, and certification of hardware and software for GSE and launch
and landing facilities and systems.

### 1.5.3 LAUNCH EXECUTION

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

#### **1.5.3.1 RESERVED**

#### **1.5.3.2 LAUNCH OPERATIONS**

The contractor shall assemble, qualify and certify its launch control
team to execute launch countdown activities, under the direction and
management of the NASA launch team. The contractor's organization and
personnel shall be fully responsive to the team's requirements and
direction. The final responsibility for launch commitment will continue
as a NASA function.

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

### 1.5.4 POST LAUNCH

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

#### **1.5.4.1 INTEGRATED LANDING OPERATIONS**

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

#### **1.5.4.2 MISSION SUPPORT**

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

#### **1.5.4.3 PAYLOAD ELEMENT REMOVAL**

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

#### **1.5.4.4 RESERVED**

### 1.5.5 SYSTEMS, FACILITIES AND EQUIPMENT

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

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

#### **1.5.5.1 OPERATIONS**

The contractor shall develop, plan, schedule and perform all systems,
facilities, and equipment operations required in the performance of this
contract. The contractor shall provide operational services to NASA and
other KSC users, for the contractor assigned systems, including the
Kennedy Complex Control Systems integration, and other assigned systems.
The contractor shall provide operators for all equipment maintained by
others and used by the contractor, such as life support. Training and
certification of contractor operators for life support will be provided
by the government. The contractor operators of critical cranes shall
comply with NASA-STD-8719.9.

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

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

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

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

The contractor shall provide all effort necessary to provide overall
process management for certification operations of Navigational Aids
Systems. The work encompasses:

-   Schedule development and coordination within the Space
    Transportation System (STS) community and the Federal Aviation
    Administration (FAA);

-   Technical and administrative support of certification operations;

-   Sustaining engineering and maintenance of specific certification
    hardware;

-   Acting as technical liaison for configuration changes of the FAA
    Automated Flight Inspection System (AFIS)

**1.5.5.2 MAINTENANCE**

The contractor shall implement a comprehensive proactive maintenance
program in accordance with NASA Directives NPD 8831.1D Maintenance of
Institutional and Program Facility, and Related Equipment, and NPR
8831.2D Facility Maintenance Management for assigned facilities,
facility systems. The contractor shall, as a minimum, assure assigned
systems, facilities, and equipment are maintained in a condition which
assures reliability and maximizes the service life while assuring the
safety, reliability, cost effectiveness, serviceability, and continuous
energy conservation of the assigned systems and equipment. The
contractor shall maintain all applicable software/firmware for the
assigned systems, facilities, and equipment. In addition to maintaining
the systems and equipment as delineated in Attachment J-9, the
contractor shall maintain and support flight and flight-type equipment
assigned to ground support equipment, simulators, and off-line
laboratories. The contractor shall budget, prioritize, and approve USA
generated Type 3C facility support requests affecting JBOSC-managed
facility systems or grounds that impact contractually obligated
facilities or facility projects. The contractor shall submit a
maintenance report (DR 1.5.5.2). The contractor shall provide support to
the systems managed by the KSC institutional communications contractor
as identified in Exhibit 1.5.5.2, entitled SPOC Support to KSC
Institutional Communications Contractor.

#### **1.5.5.3 SUSTAINING ENGINEERING**

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

The contractor shall maintain all drawings on the partnered maintained
drawing list. The contractor shall have existing EO's against critical
and process sensitive systems incorporated within one year of the
contract start date. Subsequent EO's will not exceed 10 EO's, or one
year of age. EO's for non-critical systems will be incorporated by the
end of the contract.

#### **1.5.5.4 LOGISTICS**

The contractor shall maintain a fully operational logistics system.
Performance shall be reported (DR 1.4-c).

##### 1.5.5.4.1 ACQUISITION

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

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

The contractor shall manufacture or repair hardware when cost effective.
The contractor shall use existing certification plans complying with
Program requirements and directives. Manufacture and repair performance
shall be reported (DR 1.4-c).

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

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

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

##### 1.5.5.4.2 MATERIAL MANAGEMENT

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

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

The contractor shall maintain an inventory management system.

The contractor shall maintain sufficient inventory to meet the manifest
and report the levels (DR 1.4-c).

##### 1.5.5.4.3 SUPPORT

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

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

### 1.5.6 COLUMBIA DEBRIS RECOVERY AND LONG TERM PRESERVATION

The contractor shall provide the support and equipment necessary to
perform the administrative functions associated with the Columbia Debris
Recovery Office and Long Term Preservation. Functions include receiving,
tracking, and dispositioning of potential debris findings, database
maintenance, long term storage/preservation, and shipping of debris.

### 1.5.7 INFRASTRUCTURE REVITALIZATION

The contractor shall conduct analyses of candidate Ground System
Sustainability Database tasks; support Ground System Steering Team
activities; define project requirements and project boundaries/scope;
perform system analyses and develop statements of requirements; combine
and integrate stakeholders' requirements; identify and evaluate
alternative concepts and associated testing and support requirements;
perform trade-off analyses and concept selection; define project
management and procurement approach; assess cost and schedule; and
submit candidate projects for Project Review Board review.

### 1.5.8 ENERGY MANAGEMENT

The contractor shall maintain a proactive energy management program in
accordance with NASA Procedural Requirement NPR 8570.1 (Energy
Efficiency and Water Conservation) for all assigned systems. Where the
SPOC contractor has facility O&M responsibility, the contractor's energy
management program will strive to meet the federally mandated energy
reduction goals (as referenced in NPR 8570.1 and for KSC at a minimum
shall be a reduction of 2200 BTUs per square foot per year) through use
of energy efficient modifications to operations, maintenance, and design
procedures. The effort should emphasize facility system recommissioning
and target the efficient operation of building HVAC and lighting
controls. In addition, the contractor's program shall include provisions
for facility audits, workforce awareness, support for related
initiatives/working groups, seek to expand the use of renewable energy
sources, and apply life cycle costs analysis when making decisions that
significantly affect energy usage, so that mission requirements will be
satisfied at the lowest life-cycle-cost.

The contractor shall submit energy consumption data to serve as a
performance metric and an energy management program plan (DR 1.1.2.1-d).

## 1.6 FLIGHT OPERATIONS

The contractor shall prepare for and execute SSP flight operations and
ISS mission operations. The contractor shall develop alternatives that
are more efficient and effective by taking advantage of synergies across
the Program(s), utilization of new technology and tools, consolidation
of functions, or by other means. For the purposes of SOW section 1.6
flight operations are equivalent to SSP flight operations and ISS
mission operations.

The government will lead and is responsible for mission execution and
requisite mission preparation tasks, new capability development,
non-mission specific Programmatic support tasks, and disposition of
anomalies that are not within verified, validated, and certified design,
operations, and processing requirements. As mission execution and
preparation tasks become more stable and standardized, they will, at the
discretion of the government, transition from Civil Service to
contractor responsibility. The contractor shall perform flight
controller tasks for SSP and ISS flight control responsibilities as
documented in the Fiscal Year (FY) Government Accountable Functions
Directive (GAFD). Contractor participation shall be specified via
Technical Direction and reported consistent with Flight Operations
Metrics requirements. The skill mix and size of the
government/contractor participation will be established through
concurrence with the annual operating plan.

The contractor shall utilize the standard metric (SI) system and U.S.
Customary System of measurement for all ISS displays, crew interfaces
(decal, placards, etc.), and operations/training documentation
developed. The contractor shall develop individual crew/flight
controller displays using a mixture of both the SI and U.S. Customary
System of measurement. Current versions of documentation, hardware, or
software will not be affected.

Flight Operations Integration, Manifest, and Schedules

The contractor shall provide integration of the Flight Operations/MOD
flight production process, including planning, development and
integration of flight product delivery schedules for all flights in the
manifest. The contractor shall provide flight-specific production
integration leadership via assignment of Flight Production Manager's
(FPM's), and will also lead a weekly Shuttle Schedule Tracking and
Technical Summary (STATS) forum for the purpose of reviewing
multi-flight strategies for each Shuttle flight in the manifest. The
STATS forum will review production schedules, identify/resolve
production issues, and will ensure requirements implementation
consistency. The FPM integration role will include development of
production build load strategies/plans to ensure that the
flight-specific implementation is in agreement with the overall Program
schedule and the overall Programmatic requirements. This will include
membership and support to the Program Flight Production Schedules Board
(FPSB) to ensure that a consistent and coordinated production schedule
is developed and maintained between the Flight Ops/MOD community and the
overall Program schedule.

The contractor shall provide support to the Program Flight Integrated
Product Teams (IPT's), and the various Flight Ops/MOD-internal forums
for the purpose of issue resolution and coordination for matters
pertaining to the Flight Ops/MOD product content and schedule, and will
also include integration of Program requirements impacting the
production process. This will include the prerequisite MOD-internal
coordination, as well as coordination with various Flight
Operations/MOD-external elements, such as the Flight Software element
and the Program flight production Schedules team. The FPM function will
include tracking and monitoring of multi-flight/multi-discipline impacts
and resource issues to ensure the overall resource loading is kept
within established capabilities.

The contractor shall manage the administration and integration of the
Programmatic requirements relative to the overall MOD integrated
production plan. This will be executed via the Flight Implementation
Data Pack (FIDP) instrument, which will serve as a build specification
for Flight Operations/MOD-internal products. A flight-specific and a
generic FIDP document shall be developed, managed and maintained by the
contractor. The FIDP shall be established at the baselining of each
flight in the FDRD, and shall be managed and utilized up to mission
launch. The contractor shall utilize the FIDP as the mechanism for
implementation of the Certification of Flight Readiness (CoFR) process
for MOD requirements compliance in support of the Flight Readiness
Review (FRR) for each mission.

The contractor shall provide timely analysis and data to support the
government-managed manifest planning efforts by providing support to
Program Office manifest supportability assessments. This includes risk
mitigation (cost and schedule), assessing potential impact to mission
performance, conducting internal studies to reduce turnaround times, and
requirements analysis. The contractor shall support the NASA working
groups in the development, definition, assessment, and modification of
the Shuttle manifest.

The contractor shall demonstrate schedule performance by accomplishment
of the manifest and established Program milestones. The contractor shall
provide MOD production schedules utilizing the Program-level flight
production generic template. The contractor shall serve as the OPR in
the development of the Flight Ops/MOD Management Level Network (MLN)
generic template, and ensure that it is in agreement with the Program
generic template.

The contractor shall provide development and sustaining engineering of a
math model representation and software model/tool to be used for the
purposes of developing a MLN-based production schedule to be used in
initializing a production schedule for each flight.

### 1.6.1 TRAINING

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

The government will lead and is responsible for overall ISS training and
training processes and the Crew On-Orbit Support System (COSS) which
will be developed and implemented by government and contractor
personnel. The government will transition ISS training to the contractor
when stable and standardized ISS training processes have been
established. During the development period, the contractor participation
shall be specified via Technical Direction and reported consistent with
Flight Operations Metrics requirements, as related to performance
metrics. The size and skill mix of the contractor participation will be
established through concurrence of the annual operating plan. The
contractor shall provide for the development and implementation of
identified ISS training responsibilities. The contractor will develop,
implement, and operate the Crew On-Orbit Support Systems (COSS) software
to support on-orbit requirements on ISS, including participation in
training activities. The contractor shall perform tasks for the training
of onboard computer networks required to meet PGSC mission objectives.
The contractor shall continue the development of EVA/Onboard Training
products and the associated maintenance of those products.

The contractor shall perform tasks for the training of astronauts and
flight controllers on the ISS Inventory Management and Stowage (IMS) and
the Operations Local Area Network (OPS LAN); acquire certification to
teach all DT lessons pertaining to the OPS LAN and IMS, develop
requirements for the OPS LAN laboratory as well as the ISS mock-ups and
Space Station Training Facility (SSTF) simulations and provide
troubleshooting for the OPS LAN system; assist the SSTF team during the
set-up period prior to simulations to ensure that correct software loads
are installed on all ISS laptops; and assist the DT laptop custodian in
the reconfiguration and management of the DT laptops.

#### **1.6.1.1 TRAINING MANAGEMENT**

The contractor shall provide for execution of overall training processes
to assure flight crews and controllers are prepared to carry out their
assigned flight tasks. The contractor shall establish and implement
training requirements based on SSP and ISS manifests and vehicle
configurations. The contractor shall manage and implement flight or
increment specific training in accordance with established program
templates with a goal to reduce/optimize the overall training template
to increase management scheduling flexibility, training effectiveness,
and efficiencies. When requested, the contractor shall provide flight
specific and increment specific training feasibility assessments in
support of defining mission specific production schedules and planning.

##### 1.6.1.1.1 TRAINING RECORDS

The contractor shall maintain flight operations training and
certification records in support of Flight Crew Readiness, Flight
Controller Certification, Instructor Certification and for all
contractor-provided positions requiring personnel certifications to
perform flight design, planning, and analysis (DR 1.6.1.1.1).

##### 1.6.1.1.2 CURRICULUM AND LESSON DEVELOPMENT

The contractor shall manage and document the training processes utilized
in the production of all flight specific and generic training products
in accordance with the Training Development and Support Plan, JSC 36049
(DR 1.6.1.1.2-a). The contractor shall coordinate with appropriate NASA
and external organizations (e.g., International Partners, Payload
Customers) to implement training requirements based on configuration of
the vehicles, flight software, flight plans, flight procedures, and
cargo. Training curriculum and lessons shall meet flight crew flight
readiness requirements prior to launch of their assigned mission and
flight controller, instructor, flight design/planning production, and
analysis certification requirements per their discipline specific
certification plans. Training curriculum and lessons for crews, flight
controllers, instructors, flight design/planning production, and
analysts will in no case negatively impact safety, mission success, or
major program schedule milestones. The contractor will provide avionics,
system, and robotics training for the Russian Segment Trainer (RST) and
participate in RST requirements development, curriculum development and
conducting training exercises. The contractor shall collect data
documenting the quality of delivered training (DR 1.6.1.1.2-b).

##### 1.6.1.1.3 TRAINING SCHEDULING

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

##### 1.6.1.1.4 INSTRUCTORS

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

#### **1.6.1.2 FLIGHT CONTROLLER TRAINING**

The contractor shall develop and maintain the SSP and ISS Flight
Controller Certification Guides (DR 1.6.1.2-a and DR 1.6.1.2-b) for
positions identified in SOW Section 1.6.5. The contractor shall develop,
maintain and conduct training for SSP and ISS Flight Controllers in
accordance with SOW section 1.6.1.1.2. The contractor shall develop and
conduct Integrated Simulations (includes generic, advanced, flight
specific, and increment specific). Contractor shall perform Japan
Segment Trainer (JST) training and operator functions to train
Expedition crews for ISS missions. Contractor shall provide appropriate
SMS, SCA, and SSTF support for generic integrated simulations, flight
specific simulations, and flight specific SSTF load development and
training for SSP and ISS missions.

#### **1.6.1.3 FLIGHT CREW TRAINING**

The contractor shall develop and maintain the SSP Crew Training Catalog
(USA002960) and the ISS Master Course Catalog
(https://mod2.jsc.nasa.gov/dt/focas/catalog/lesson/index.cfm) (DR
1.6.1.3-a). The contractor shall develop, maintain, and conduct SSP and
ISS flight crew training in accordance with SOW section 1.6.1.1.2. (DR
1.6.1.3-b). The contractor shall develop, manage and execute flight
specific or increment specific crew training based on flight or
increment specific requirements (DR 1.6.1.3-c). The contractor shall
coordinate Flight Crew input into all crew training plans, flows,
curricula, and facilities; identify and document crew issues and crew
positions; disseminate Flight Crew positions to the relevant IPT; and
propose areas requiring developmental test objectives (DTO) or risk
mitigation experiments (RME). (See section 1.6.2.5.5.1) The contractor
shall provide Astronaut Candidate Training in accordance with the
Astronaut Candidate Training plan and schedule (DR 1.6.1.3-d).
Contractor shall perform Japan Segment Trainer (JST) training and
operator functions to train Expedition crews for ISS missions. The
contractor shall provide appropriate SMS, SCA, and SSTF support for
generic integrated simulations, flight specific simulations, and flight
specific SSTF load development and training for SSP and ISS missions.

#### **1.6.1.4 FLIGHT TRAINING HARDWARE**

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

### 1.6.2 FLIGHT PREPARATION

The contractor shall provide flight preparation products and services.
This includes flight rules/operations documentation/flight data file,
flight design, flight planning, payload integration, flight crew
integration, data collection and reconfiguration, performance of tasks
for OD initiated ISS laptop processes (e.g. laptop manifesting).

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

The contractor shall provide products and services for the production,
maintenance, and distribution of operations documentation, FDF, and
Operations Data File (ODF). The contractor will provide products and
services including editorial, word processing, fabrication, and
maintenance of Flight Data File (FDF) and Operations Data File (ODF) in
hardcopy and in electronic media, as required.

##### 1.6.2.1.1 RESERVED

##### 1.6.2.1.2 OPERATIONS DOCUMENTATION

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

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

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

The contractor shall develop and maintain applications software and
provide associated training. The contractor will develop and maintain
management documentation covering software products.

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

#### **1.6.2.2 FLIGHT DESIGN**

The contractor shall manage and execute the overall flight design
processes for mission operations for the SSP. These processes include
flight design requirements development, flight design products
generation, flight design post flight reconstruction (Orbit and
Navigation only), flight design process integrity data generation,
Flight Design and Dynamics technical training, and flight design
software sustaining engineering. The contractor shall develop and
integrate new capability into these processes to support current program
requirements. The contractor shall manage and maintain those Flight
Software (FSW) Principle Functions (PF) for which they have been
designated primary responsibility by NASA (see 1.4.3.3).

##### 1.6.2.2.1 FLIGHT DESIGN REQUIREMENTS

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

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

##### 1.6.2.2.2 FLIGHT DESIGN PRODUCTS

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

Products shall be delivered for the functional areas of: Ascent, Orbit
(including rendezvous and proximity operations), Descent, Navigation
(ground and on-board), Flight Integration, and post flight
reconstruction. These products are fully described in Flight Design
Handbook (FDHB) (FDD-FDHB-R-001). The ISSP Flight Design is a Government
Accountable Function and the products are described in the GAFD and in
DM-WI-3303 (ISS Flight Design Handbook). The contractor shall develop
improvements and efficiencies in product development processes and shall
provide complete product definitions and development processes in a
Flight Design Handbook and Product Glossary (DR 1.6.2.2.2-c). The
contractor shall provide recommendations for new capability development
based on the resolutions of in-flight anomalies.

Products shall be delivered per an appropriate number of cycles
consistent with the mission requirements as defined by NASA. Changes can
occur during the flight production template process, and this may
require all or part of the production process cycles to be repeated.

##### 1.6.2.2.3 FLIGHT DESIGN SOFTWARE

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

The contractor shall perform the tasks for rehosting the MCC Flight
Operations application software inventory, supporting data, and required
testing and validation for operational usage and operational readiness.

#### **1.6.2.3 FLIGHT PLANNING**

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

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

#### **1.6.2.4 CARGO INTEGRATION**

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

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

#### **1.6.2.5 FLIGHT CREW**

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

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

The contractor shall develop alternatives to those products and support
tasks that are more efficient and effective by taking advantage of
synergies across the Program(s), by utilization of new technology and
tools, by consolidation of functions, or by other means. The contractor
shall provide technical evaluations of the crew operational and safety
impacts of specific, identified changes to the ISS Flight software. The
contractor shall perform the tasks for the maintenance and sustaining
engineering for the software applications used for Astronaut Appearances
tracking and routing and Astronaut scheduling.

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

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

The contractor shall manage the Change Request (CR) review process for
the Flight Crew, including routing of CRs for Flight Crew evaluations
and maintaining an existing database of all such reviewed CRs for boards
(or their successors).

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

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

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

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

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

The contractor shall deliver briefings to assigned Flight Crew.

##### 1.6.2.5.2 SHUTTLE TRAINING AIRCRAFT SUPPORT

The contractor will be responsible for the maintenance and resolution of
anomalies of rotational hand controller (6) and surface position
indicator (5) equipment used by the Shuttle Training Aircraft, which is
operated by the NASA Aircraft Operations Division, resulting from normal
training activities, including the identification of faulty components,
procurement and/or fabrication of replacement parts as necessary, and
maintenance of equipment within operational performance envelopes.

##### 1.6.2.5.3 EXPEDITION CREW SUPPORT

The contractor shall develop and manage workshops and seminars that
address issues associated with the long duration space flight required
for ISS operations. The contractor shall assist in the development,
implementation, and management of various field exercises designed to
prepare astronauts to be suitable candidates for Shuttle or long
duration ISS space flight. The contractor shall develop training plans,
evaluations, and other documentation to support this effort.

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

The contractor shall manage the requirements of the Flight Crew for FCE
and establish and maintain coordination between the Flight Crew and
hardware suppliers for FCE.

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

The contractor shall participate in the development of requirements for
provisioning, stowage, and manifesting of hardware and crew items and
equipment. The contractor shall be responsible for tracking Astronaut
Office accountable flight hardware such as the Astronaut watches.

##### 1.6.2.5.5 OPERATIONS DEVELOPMENT FOR ISS

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

###### 1.6.2.5.5.1 FLIGHT CREW TRAINING DEVELOPMENT

The contractor shall coordinate Flight Crew input into all crew training
plans, flows, curricula, and facilities, identify and document crew
issues and crew positions, disseminate Flight Crew positions to the
relevant IPT and propose areas requiring developmental test objectives
(DTO) or risk mitigation experiments (RME). The contractor shall provide
reports and assessments of operational impacts of training issues.

###### 1.6.2.5.5.2 RESERVED

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

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

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

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

###### 1.6.2.5.5.4 RESERVED

###### 1.6.2.5.5.5 COMMON DISPLAY DEVELOPMENT

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

###### 1.6.2.5.5.6 RESERVED

###### 1.6.2.5.5.7 RESERVED

##### 1.6.2.5.6 SHUTTLE/ISS INTEGRATION

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

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

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

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

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

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

The contractor shall provide the operations interface between JSC flight
operations in-line tasks and processing or launch operations at KSC and
ISSP international partner sites. The contractor shall implement the
Vehicle Integration Plan for Space Operations (JSC 17519A).

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

#### **1.6.2.7 DATA COLLECTION/ RECONFIGURATION**

The contractor shall operate and maintain the ISS MOD Avionics
reconfiguration tools and processes that will generate command,
telemetry, and display products required to reconfigure flight, Orbiter
Interface Unit (OIU), and ground facilities; shall provide sustaining
engineering support; and shall support the development of recon tools
through development of operations concepts document, RID review of Level
B requirements, and User Acceptance Test (UAT). Production processes
include data management services, production and operations support, and
development and maintenance of related documentation.

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

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

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

#### **1.6.2.8 LAPTOPS**

The contractor shall provide ground and on-orbit ISS Laptops support.
This includes engineering, integration, software application development
and sustaining activities, real-time operational support, and ISS
Laptops manifesting.

#### **1.6.2.9 FLIGHT DIRECTOR OFFICE**

##### 1.6.2.9.1 FLIGHT RULES

The contractor shall develop, maintain, and distribute Flight Rules
documents (DR 1.6.2.1.1). This task includes associated support to
various meetings and reviews used for developing and evaluating Flight
Rules including, but not limited to, Flight Rules Control Board (FRCB),
Flight Techniques meetings, Joint Operations Panels (JOPs), and Flight
Operations Reviews (FORs).

##### 1.6.2.9.2 ADMINISTRATIVE MEETINGS

The contractor shall provide administrative meeting logistical help for
various meetings including, but not limited to, MOD Flight Readiness
Reviews (FRRs), Flight Techniques Panel (FTP) meetings, Joint
Operational Panel (JOP) meetings, MOD Products Integration Board (MPIB)
meetings, and International Display and Graphics Standards (IDAGS)
meetings.

##### 1.6.2.9.3 PROGRAM INTEGRATION

The contractor shall participate in the coordination and review of Space
Shuttle Program and Station Program change request evaluations
(including tracking of actions, issues, anomaly resolutions, and change
documentation). The contractor shall provide technical inputs to the
Mission Operations Directorate (MOD) representatives for the various
Shuttle and ISS Programmatic Boards, associated sub-boards, and panels.
The contractor shall maintain and distribute the Flight Control
Operations Handbook.

##### 1.6.2.9.4 SAFETY INTEGRATION

The contractor shall provide assessments and recommendations on MOD
payload safety requirements and compliance. This includes safety issue
resolution, real-time safety analysis, and safety knowledge for various
pre-flight planning meetings (e.g., Joint Operations Panels). The
contractor shall facilitate and integrate the review and evaluation of
the ISS safety operational hazard controls assessment process and shall
document results of those evaluations in the Operational Controls
Agreement Document (OCAD) per ISS assembly flight. The contractor shall
provide assessments and recommendations on orbiter, ISS, and payload
design/requirements, payload procedures/flight rules, Integrated Cargo
Hazard Analysis (ICHA), Integrated Safety Verification Reports (ISVRs),
safety data packages (SDPs), test assessments, reports, and development
test reviews. The contractor shall participate in payload working
groups, reviews, control boards, and panels as needed.

### 1.6.3 RESERVED

### 1.6.4 FLIGHT OPERATIONS SYSTEMS AND EQUIPMENT

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

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

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

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

The contractor shall maintain, operate, and perform sustaining
engineering and logistics for the Space Station Training Facility (SSTF)
and the Part Task Trainer (PTT) and the American Segment Trainer (AST).

The contractor shall perform tasks to implement the Astronaut and Flight
Controller capability in the SSTF and PPT for the new ISS Regenerative
Environmental Control and Life Support System (ECLSS).

The contractor shall perform tasks to implement the International Space
Station (ISS) Node 3 (N3) training capability for the SSTF.

**Management and Integration**

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

The contractor shall establish external management interfaces and
external interface agreements as well as any other management interfaces
necessary for operations (DR 1.6.4-c).

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

**Maintenance and Operations**

The contractor shall provide maintenance and operations services for all
flight operations systems and equipment in Exhibit 1.6.4-A.

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

**Hardware Sustaining Engineering**

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

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

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

**Software Sustaining Engineering**

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

The contractor shall develop and sustain all flight systems user
applications software including software used in support of SSP and ISS
systems flight design, analysis, planning, training, and flight control.
This includes the development and maintenance of user workstation
applications and displays for Mission Control Center (MCC) and
Integrated Planning System (IPS) platforms.

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

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

**Integration and Installation**

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

**Flight Operations Logistics**

The contractor shall perform logistics for flight operations. The
contractor shall maintain a fully operational logistics system. The
contractor shall provide transportation, shipping, receiving,
warehousing, and distribution services. The contractor shall provide the
necessary level of stand alone, Flight Operations unique logistics to
support all Flight Operations tasks. The contractor shall define,
assess, and ensure that spare parts and consumables are procured or
supplied for Flight Operations Simulators, Trainers, and related support
equipment at JSC.

#### **1.6.4.1 MISSION CONTROL CENTER (MCC)**

The contractor shall develop, maintain and modify user interfaces
vehicle-specific user application software and configuration scripts for
user-configurable software required to support command and control
capabilities for mission operations for SSP and ISSP (including Group
Administration functions for the HSG in Mission Control Center-Moscow
(MCC-M), and development and maintenance of software applications to
monitor crew health and environment aboard the ISS). The contractor
shall ensure SPOC-generated software to be integrated in the MCC is
compliant with MCC standards. The contractor shall ensure that critical
software is compliant with NASA critical processor policies. The
contractor shall develop, maintain, and conduct a training process for
MCC programmers and group administrators (GA) according to MCC
standards. In addition, the GAs shall be certified to meet common Flight
Operations standards. The contractor shall provide mission specific
baseline management and control. The contractor shall perform tasks for
the ISS Program in the areas of ISS Ground System Integration,
including, but not limited to, development of requirements and
integration procedures, International Partner integration, and Ground
Segment verification.

The contractor shall perform additional Software Sustaining Engineering
tasks for Manual Procedures Viewer (MPV), International Procedure Viewer
(iPV), On-board Short-Term Plan Viewer (OSTPV), and workflow
applications.

##### 1.6.4.1.1 RESERVED

##### 1.6.4.1.2 RESERVED

#### **1.6.4.2 INTEGRATED TRAINING FACILITY (ITF)**

The ITF consists of hardware, platform software (custom and COTS), and
mission specific application software required to provide flight crew
and flight controller part task training, standalone and integrated
simulations and testing capabilities for the mission operations in
support of the SSP and ISS. The contractor shall document procedures for
maintenance and operations of training facilities within the ITF SSOH
(DR 1.6.4.2-a). The contractor shall perform the tasks required to
produce payload mockups. The contractor shall be responsible for the
maintenance and operations of the Shuttle Mission Training Facility
(SMTF), Flight Operations Trainers (FOT), and Space Station Training
Facility (SSTF).

#### **1.6.4.3 INTEGRATED PLANNING SYSTEM (IPS)**

The contractor shall provide mission specific baseline management and
control. (See exhibit 1.6.4-A, Flight Operations Systems.)

#### **1.6.4.4 SOFTWARE PRODUCTION FACILITY (SPF)**

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

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

##### 1.6.4.4.1 RESERVED

##### 1.6.4.4.2 SPF-UNIQUE INSTALLATION SERVICES

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

#### **1.6.4.5 RESERVED**

##### 1.6.4.5.1 RESERVED

##### 1.6.4.5.2 RESERVED

#### **1.6.4.6 RESERVED**

#### **1.6.4.7 RESERVED**

#### **1.6.4.8 RESERVED**

#### **1.6.4.9 OPERATIONS SUPPORT SYSTEMS**

The contractor shall provide the services and materials required to
support the management and operations for all technical systems used in
flight operations. Included in this support are Systems and Project
Engineering, Maintenance and Operations for multiple facilities,
Advanced Technology Development, and Fabrication Services.

### 1.6.5 NASA MANAGED MISSION DESIGN, PREPARATION, AND EXECUTION SUPPORT

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

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

The contractor shall participate in the following flight control team
functional areas: Flight Systems, Extravehicular Activity (EVA),
Robotics, Flight Planning/Payloads or Cargo/Assembly, Flight Design and
Dynamics, International partners' coordination, International Operations
and other areas as specified by the government. This participation
includes both execution of flight and mission operations and requisite
flight preparation. Specific examples of contractor participation
include development and execution of flight plans and ISS mission plans;
ISS integrated testing and verification; development and maintenance of
the ISS operations nomenclature; development, training, and execution of
operational generic and flight-specific EVAs; vehicle design and
operations integration; operations requirements development for flight
controller training tools and facilities; operations application
software verification and checkout; development of console reference and
real-time support products; EVA/Robotics and payloads mission
integration; FDF/ODF/Safety Process Integration; development and
execution of flight controller mentor training; pre- and post- flight
analysis; pre-mission facility checkout; and ISS assembly Integration.
Flight controllers shall also participate in the development of new
operations concepts and requirements for the SSP and ISSP, including the
development of new technology prototypes and advanced flight control
software applications. Training for all flight controller personnel is
specified in SOW section 1.6.1.2. Both government and contractor (CAF
and GAF) flight controllers shall be directly involved in the definition
of training requirements. The government will also certify flight
controllers for specific MCC real-time monitoring, analysis, command,
and control operations. In addition to government certification
requirements, the contractor shall certify flight controllers for CAF
FCT positions. The contractor shall provide flight control team
functions at Mission Control Center - Moscow (MCC-M) for the Houston
Support Group (HSG) through the period of the contract \[(including
providing Operations Data File (ODF) coordination to integrate the joint
data file requirements for implementation for ISS missions)\]. The
contractor shall provide the IP Segment Specialist flight control team
functions at the IP Mission Control Centers (Col-CC, ATV-CC, and SSIPC)
for the Houston Support Group through the period of the contract as
documented in the Fiscal Year (FY) Government Accountable Functions
Directive.

The contractor shall train NASA selected civil servant personnel in the
CAF support positions as directed by NASA.

#### **1.6.5.1 FLIGHT SYSTEMS**

The contractor shall provide flight control team functions to accomplish
vehicle and flight systems operations as required to assure safety and
mission success (including H-II Transfer Vehicle (HTV) and Autonomous
Transfer Vehicle (ATV). Requisite vehicle and flight systems flight
control team functions include: Data Processing Systems; Command and
Data Handler Systems; Instrumentation, Communications and Tracking
Systems; EVA; Robotics Systems; Mechanical Systems; Booster Systems;
Guidance Navigation and Control Systems; Propulsion Systems; Motion
Control Systems; Electrical Power Systems; Environmental Control, Life
Support, Thermal Systems; Mechanical/Structures, Logistics and
Maintenance Systems; Shuttle In-flight Maintenance; and ISS Resource
Analysis. Inherent in these functions are the maintenance and
development of associated ground and crew procedures and ground computer
operations. Also, flight controllers shall participate in EVA design and
training, and new operational capability projects. The contractor shall
perform Integrated Verification and Testing for ISS vehicle and ops
facilities. The contractor shall develop ISS Operational products to
support ISS (including Ground and Flight display and computation
development; Flight software reconfiguration product development;
command and telemetry definition; development of ISS ground and onboard
procedures). The contractor shall perform integration tasks for the ISS
Program in the areas of robotics requirements. The contractor shall
perform tasks for the development of ISS procedures, flight rules,
handbook drawings and displays.

The contractor will provide support for International Partner
Integration both pre-flight and in real-time. This includes Flight
Control Support for the IP Segment Specialist, Ops Lead, and Remote
Interface Officer positions.

The contractor shall perform the tasks for the integration and
management of SSTF load development, ISS flight specific Mission
Configuration Tests and perform the role of focal point for IP mission
preparation activities.

The contractor shall perform tasks to develop emergency procedures,
flight product development, pre-launch test and integration, and crew
training material for the ISS Node 3.

The contractor shall perform tasks to develop emergency procedures,
flight product development, pre-launch test and integration, and crew
training material for the ISS Environmental Control and Life Support
Systems (ECLSS).

The contractor shall perform tasks for the Autonomous Transfer Vehicle
(ATV) operations integration to the ISS (including planning and
execution of ATV missions, produce integrated flight products, integrate
multi-element procedure development and testing, and integrate European
International Partner flight controller operations with MOD flight
control elements.

The contractor shall perform tasks for the H-II Transfer Vehicle (HTV)
operations integration to the ISS (including planning and execution of
HTV missions, produce integrated flight products, provide independent
monitoring of HTV, integrate multi-element procedure development and
testing, and integrate JAXA International Partner flight controller
operations with MOD flight control elements.

The contractor shall perform tasks for EVA integration operations with
Russian Orlan suits (including EVA planning and operations product
development, EVA systems and procedures integration for USA and Russian
EVA hardware, EVA crew training in Star City, and flight control console
operations in MCC-Moscow during EVA operations).

#### **1.6.5.2 FLIGHT PLANNING/CARGO/ASSEMBLY**

The contractor shall perform flight control team functions to accomplish
flight planning; cargo transfer operations; ISS inventory development
and maintenance, both pre-increment and real-time support; and ISS
Operations Planning activities and assembly operations as required to
assure safety and mission success. Requisite flight planning, payloads,
and assembly flight control team functions include: flight and mission
activity planning; payload operations and associated integration;
assembly and checkout plan and operations; specialty flight phase
support; attitude timeline and pointing; on-orbit inventory and storage.
Inherent in these functions are the maintenance and development of
associated ground and crew procedures and ground computer operations
(including RF LAN for ISS). The contractor shall perform the activities
for design Integration for ISS assembly mission strategic operations
planning and assessments, design review support, Stage Integration
Review support, and IP negotiations on operations data deliverable items
which are associated with the ISS systems \[{e.g., Node 3, Centrifuge
Accommodations Module (CAM), etc.}\]. The contractor will provide
support to the Assembly and Checkout Officer (ACO) team which will
include, but not be limited to, systems integration for the
shuttle-carried ISS hardware, including Columbus and JEM, the Autonomous
Transfer Vehicle (ATV), the H-II Transfer Vehicle (HTV), and additional
transfer vehicles as required. The contractor shall provide ISO and CIO
activities for real-time operations of the ISS during crew wake up.
Perform off-console inventory management and updates to the IMS
databases for both ground and on-orbit computer system including
response to critical discrepancy reports and modifications to improve
on-board efficiency of the IMS. Contractor ISO activities will include,
but not limited to tracking manifested hardware, stowage, transfer
processes, database maintenance, Russian and US software integration,
and crew concerns resolution. Contractor CIO tasks will include, but not
limited to the PLugin UTilization Officer (PLUTO) and ISO/MPSR
positions.

The contractor shall provide continued development of the Inventory
Management System (IMS) that requires resources to perform system
upgrades, as well as, additional Software Sustaining Engineering when
development is complete. The PLUTO responsibilities will include, but
not be limited to, the Operations Local Area Network (LAN), the
Integrated Stations LAN, and the HAZMAT program.

The contractor shall support meeting logistics and documentation
preparation in support of Flight Operations Reviews (FOR) and Flight
Readiness Reviews.

#### **1.6.5.3 FLIGHT DESIGN AND DYNAMICS**

The contractor shall perform SSP and ISSP flight control team functions
to accomplish flight design and dynamics operations as required to
assure safety and mission success. Requisite flight design and dynamics
flight control team functions include: flight dynamics and trajectory
control; onboard guidance and navigation; ground navigation and
tracking; launch, ascent, and abort analysis; entry, landing and winds
analysis; rendezvous and proximity operations analysis; landing
operations coordination; and debris avoidance. Inherent in these
functions are the maintenance and development of associated ground and
crew procedures, ground computer operations; development and maintenance
of Training Guide documents specified in the GAFD; independent
verification and test; system administration; and programming. The
contractor shall provide an SSP Flight Software Integration function and
an ISSP Visiting Vehicle onboard display design function. The contractor
shall provide a dedicated team for performing independent verification
testing (IVT) for Flight Design and Dynamics MCC ascent/entry/orbit
displays and applications maintained within the Trajectory Operations
Computer Software Support (TOCSS) laboratory.

The contractor shall support the overall flight design processes for
mission operations for the ISSP, including development, integration, and
operation of automated vehicles which are associated with the ISS. These
processes include flight design requirements development, flight design
products generation, flight design post flight reconstruction, flight
design process integrity data generation, flight design technical
training, and flight design software sustaining engineering.

#### **1.6.5.4 FLIGHT OPERATIONS DEVELOPMENT**

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

#### **1.6.5.5 FLIGHT DIRECTOR OFFICE**

The contractor shall perform the real-time operations functions of the
ISS Spacecraft Analysis (SPAN) Manager and Shuttle SPAN Manager console
positions. The contractor shall accomplish flight objectives, ensure
flight safety and mission success, and develop all technical console
operations documentation. Development and integration of mission
operations concepts, plans, and integrated Anomaly and Chit processing
philosophies for the Mission Control Centers in Houston and Moscow
(MCC-H and MCC-M) and other International Partner centers will be
conducted to fit current or planned vehicle operations. Shuttle SPAN
Manager real-time functions shall be a combination of NASA and
contractor personnel.

## 1.7 NASA MANAGED ACTIVITIES

The contractor shall participate in NASA-managed activities as addressed
in the following subsections. Such participation shall be as specified
in appropriate technical direction, including concurrence with annual
SSP and ISSP operating plans.

### 1.7.1 SPECIAL STUDIES AND DEVELOPMENT PROJECTS

The contractor shall participate, when required, in government-initiated
SSP special studies and development projects, as follow:

a.  Development of requirements for initial concept development; design
    reviews providing technical assessments and evaluations as
    appropriate to insure that the design meets the requirements.

b.  Engineering services (including design), procurement, fabrication,
    integration, support to integration by another contractor,
    installation, support to installation by another contractor,
    activation, validation, and turnover activation related to safety,
    performance and obsolescence upgrades; e.g., GSE.

c.  Non-recurring tasks and efforts such as requirements development,
    analysis, and assessments related to SSV/Cargo and SSV/ISS
    integration and to integrated SSV enhancements. Included in this
    activity are analyses required to define generic induced environment
    design and certification envelopes and all systems analyses required
    to demonstrate compliance with all SSP requirements.

d.  The contractor shall conduct design studies, produce engineering
    drawings and associated list(s), configuration documentation,
    installation instructions, performance verification requirements and
    specifications, and acceptance data packages for hardware in
    compliance with NSTS 07700-10-MVP-01, Space Shuttle Master
    Verification Plan.

e.  The contractor shall design, develop, produce, verify, and deliver
    certified cargo bay and crew compartment cargo integration hardware
    to satisfy Shuttle manifest requirements. The contractor shall
    produce design requirements definition documentation (DR
    1.4.1.5.1-a); perform design and analyses (stress, dynamic,
    avionics/electrical, thermal, safety, reliability, etc.; conduct
    design reviews; fabricate, assemble, and integrate the hardware;
    perform design requirements verification; and provide certification
    documentation (DR 1.4.1.5.1-b and DR 1.4.1.5.1-c). The contractor
    shall produce engineering drawings, configuration documentation,
    safety and reliability reports, and performance verification
    requirements and specifications. The contractor shall provide
    acceptance data packages (DR 1.3.3.1) for cargo integration hardware
    transferred to external customers. The contractor shall provide
    cargo integration hardware in compliance with the latest version of
    the Standard End Item Specification (SEIS) for Orbiter/Payload
    Integration Hardware, MJ073-0001, and unique Design Requirements
    Documents. The contractor shall provide cargo integration hardware
    ground support equipment in compliance with the latest version of
    the Cargo Integration Hardware Ground Support Equipment Standard End
    Item Specification (GSE SEIS), MJO73-0010.

f.  The contractor shall provide support to the SSP/ISSP Joint On-Orbit
    Verification Review (JOVR) process and associated Joint Technical
    Working Groups (JTWG). The contractor shall also support other joint
    working groups/teams as requested by NASA. The contractor shall
    provide support to payload design analyses and payload design
    reviews as requested by NASA.

#### **1.7.1.1 KSC SHUTTLE DEVELOPMENT ACTIVITIES**

The contractor shall participate, as required, in government initiated
SSP program special studies and development projects.

#### **1.7.1.2 KSC CONSTRUCTION OF FACILITIES (CofF) ACTIVITIES**

The contractor shall participate, as required, in government initiated
CofF special studies and development projects.

### 1.7.3 RESERVED

### 1.7.4 PROGRAM REIMBURSABLES 

The effort defined herein shall be specifically authorized under the
Program Provisioning Procedure as defined in H.35, entitled Provisioning
Procedures. The contractor shall participate, when required, in
government initiated projects ancillary to the SPOC.

### 1.7.5 SRB DEVELOPMENT ACTIVITIES

The contractor shall participate, as required, in government-initiated
SRB program element special studies and development projects.

## 1.8 RESERVED

## 1.9 PROGRAM TRANSITION

Program Transition is that effort required to bring the Space Shuttle
Program to a logical and orderly end. Within this contract, Program
Transition considers the planning, execution and reporting of activities
necessary to initiate and execute the disposition of assets and
capabilities that are no longer required for performance of the Space
Shuttle mission. This effort may include safing of facilities and
equipment no longer required, studies of various end of Space Shuttle
Program life scenarios, or accomplishment of some other end of life
activities. Effort associated with Program Transition shall be
authorized per H.35, [Provisioning Procedures]{.underline}.

### 1.9.1 RESERVED

### 1.9.2 RESERVED

## 1.10 CONSTELLATION BRIDGE SUPPORT

The contractor shall support Constellation work content in technical,
operations, and processing functions common to both Constellation and
the SSP. The support may include: concept development and trade analyses
for flight operations trajectory planning, mission planning,
development, integration and execution, and facilities and applications
software planning; ground systems operations, maintenance, and
modification; vehicle processing, test, and recovery operations;
assembly and physical integration of Constellation test flight elements;
mission preparation and planning, human spaceflight training, operations
integration, and operations application development; systems and cargo
engineering and integration support to Constellation Program
architecture studies associated with shuttle-derived launch vehicles;
and general Constellation studies. Effort associated with Constellation
Bridge Support shall be authorized per H.35, [Provisioning
Procedures]{.underline}.

## 2.0 RESERVED

## 3.0 RESERVED

**ATTACHMENT J-1-A**

**SPACE PROGRAM OPERATIONS CONTRACT**

**STATEMENT OF WORK**

**EXHIBITS**

1.1.1.1 Contingency Plans

1.4.9 Flight Crew Equipment Groups

1.5.5.1-B SPDMS/IWCS Applications

1.5.5.2 SPOC Support to KSC Institutional Communications Contractor

1.6.4-A SPOC Flight Operations Systems

+-----------------------------+----------------------------------------+
| **ATTACHMENT J-1-A**        |                                        |
|                             |                                        |
| **EXHIBIT 1.1.1.1**         |                                        |
|                             |                                        |
| **Contingency Plans**       |                                        |
+=============================+========================================+
| NPD8710.1                   | NASA Emergency Preparedness Program    |
+-----------------------------+----------------------------------------+
| NPD 8715.2                  | NASA Emergency Preparedness Plan       |
|                             | Procedural Requirements                |
+-----------------------------+----------------------------------------+
| NPD 1040A                   | NASA Continuity of Operations          |
+-----------------------------+----------------------------------------+
| NMI 8821.1                  | Mishap Reporting and Investigation     |
+-----------------------------+----------------------------------------+
| NPR 8715.3                  | NASA Safety Manual                     |
+-----------------------------+----------------------------------------+
| NPR 8621.1                  | NASA Procedural Requirements for       |
|                             | Mishap Reporting, Investigating, and   |
|                             | Recordkeeping                          |
+-----------------------------+----------------------------------------+
| CAP SFO                     | Agency Contingency Action Plan for     |
|                             | Space Flight Operations                |
+-----------------------------+----------------------------------------+
| NSTS Directive 96B          | Shuttle Contingency & Operations       |
+-----------------------------+----------------------------------------+
| NSTS 07700, Vol. VIII, App. | Mission Management Team                |
| D                           |                                        |
+-----------------------------+----------------------------------------+
| NSTS 07700, Vol. VIII, App. | Shuttle Ingress Landing and            |
| G                           | Post-landing Operations                |
|                             | Responsibilities                       |
+-----------------------------+----------------------------------------+
| NSTS 07700, Vol. VIII, App. | Shuttle Contingency Planning and       |
| H                           | Operations Responsibilities            |
+-----------------------------+----------------------------------------+
| NSTS 07700, Vol. VIII, App. | Orbiter Prelaunch and Landing          |
| I                           | Contingency/Rescue Operations          |
|                             | Responsibilities                       |
+-----------------------------+----------------------------------------+
| NSTS 07700, Vol. VIII, App. | Space Shuttle Program: Contingency     |
| R                           | Action Plan                            |
+-----------------------------+----------------------------------------+
| NSTS 07700, Vol. VIII, App. | Space Shuttle Operations: Transoceanic |
| S                           | Abort Landing Orbiter Recovery Plan    |
+-----------------------------+----------------------------------------+
| NSTS 08218                  | Intercenter Photographic and           |
|                             | Television Analysis Contingency Action |
|                             | Plan                                   |
+-----------------------------+----------------------------------------+
|                             | STS Security Classification Guide      |
+-----------------------------+----------------------------------------+
| STDN 550.10                 | NSTS Emergency MCC Interface           |
|                             | Procedures                             |
+-----------------------------+----------------------------------------+
| OSF-SFO-PASCP               | STS Public Affairs Spaceflight         |
|                             | Contingency Plan                       |
+-----------------------------+----------------------------------------+
| JSC 23275                   | Astronaut Flight Crew Family Plan      |
+-----------------------------+----------------------------------------+
| JSC 23616                   | FCOD- Space Shuttle Contingency Action |
|                             | Plan                                   |
+-----------------------------+----------------------------------------+
| NSTS 60549                  | Space Shuttle Program Mission          |
|                             | Evaluation Room Contingency Response   |
|                             | Plan                                   |
+-----------------------------+----------------------------------------+
| 532-CAP-EMCC                | SSP Emergency MCC Activation's &       |
|                             | Operations Procedures                  |
+-----------------------------+----------------------------------------+
| SSC-PTO-001                 | Stennis Space Center Contingency       |
|                             | Action Plan                            |
+-----------------------------+----------------------------------------+
| MSFC-SSCP-5-77              | Space Shuttle Contingency Action Plan  |
+-----------------------------+----------------------------------------+
| K-STSM-09.3.02              | KSC Space Shuttle Data Impoundment and |
|                             | Handling Plan                          |
+-----------------------------+----------------------------------------+
| K-STSM-09.3.1               | Space Shuttle Program Operations Plan  |
|                             | Flight and Ground Crew Rescue          |
+-----------------------------+----------------------------------------+
| KDP-KSC-P-1450              | KSC Contingency Action Procedure       |
+-----------------------------+----------------------------------------+
| KNPR 1040.3                 | Kennedy NASA Procedural Requirements,  |
|                             | Continuity of Operations               |
+-----------------------------+----------------------------------------+
| KSC-PLN-1705                | KSC Shuttle Program Contingency        |
|                             | Procedural Plan                        |
+-----------------------------+----------------------------------------+
| K-RQ-0001.21                | KSC Mishap Investigation Board and     |
|                             | Committee Supporting Personnel         |
+-----------------------------+----------------------------------------+
| K-SF-0005.7                 | National Resource Protection Plan for  |
|                             | KSC                                    |
+-----------------------------+----------------------------------------+
| K-STM-12.4                  | KSC Off-site Transportation Plan/DFRG  |
+-----------------------------+----------------------------------------+
| KVT-PL-0004                 | SSP Emergency Egress System at LC-39   |
+-----------------------------+----------------------------------------+
| KVT-PL-0008                 | Operations Plan for Post-Cryogenic     |
|                             | Loading Pad Access                     |
+-----------------------------+----------------------------------------+
| USA 004376                  | KSC Off-Site Operations Plan           |
+-----------------------------+----------------------------------------+
| SFOC GO 0022                | Convoy Operations Plan                 |
+-----------------------------+----------------------------------------+
| KVT-PL-0016                 | STS Operations Plan, Shuttle Emergency |
|                             | OTV                                    |
+-----------------------------+----------------------------------------+
| SFOC GO 0014                | KSC SSP Salvage Operations Plan        |
+-----------------------------+----------------------------------------+
| JHB 2000                    | Consolidated Comprehensive Emergency   |
|                             | Management Plan (CCEMP)                |
+-----------------------------+----------------------------------------+
| KPH-HB-1040.1               | KSC Shuttle Processing (PH) Hurricane  |
|                             | Plan                                   |
+-----------------------------+----------------------------------------+
| NPR 8715.3                  | KSC Safety Practices Procedural        |
|                             | Requirements                           |
+-----------------------------+----------------------------------------+
| OMI S0003                   | ET Move and Mate SRBs                  |
+-----------------------------+----------------------------------------+
| OMI S0007.500               | Shuttle Countdown-LPS                  |
+-----------------------------+----------------------------------------+
| OMI S0007.600               | Shuttle Countdown-LPS                  |
+-----------------------------+----------------------------------------+
| OMI S0026.500               | Shuttle Landing and Post Landing       |
|                             | Convoy Contingency and Emergency       |
|                             | Operations, DFR                        |
+-----------------------------+----------------------------------------+
| OMI S0028.500               | Shuttle Landing and Post Landing       |
|                             | Convoy Contingency and Emergency       |
|                             | Operations, KSC                        |
+-----------------------------+----------------------------------------+
| OMI S0027.500               | Shuttle Landing and Post Landing       |
|                             | Convoy Contingency and Emergency       |
|                             | Operations, WSSH AOA/EOM               |
+-----------------------------+----------------------------------------+
| OMI S0030                   | Orbiter/ET Demate                      |
+-----------------------------+----------------------------------------+
| OMI S0038                   | Integrated Preparations for SSV/MLP    |
|                             | Return to VAB                          |
+-----------------------------+----------------------------------------+
| OMI B5303 and "dot" books   | SRB Destacking Operations              |
+-----------------------------+----------------------------------------+
| EPD S9904                   | Orbiter Processing Facility OPF        |
|                             | 1/2/3/SSME Shop Emergency Procedure    |
|                             | Document                               |
+-----------------------------+----------------------------------------+
| EPD S9905                   | Hypergol Maintenance Facility (HMF)    |
|                             | Emergency Procedure Document           |
+-----------------------------+----------------------------------------+
| EPD S9906                   | Alternate Landing Site EAFB/DFRC       |
|                             | Emergency Procedures Document          |
+-----------------------------+----------------------------------------+
| EPD S9907                   | Non-CONUS CLS Emergency Procedure      |
|                             | Document                               |
+-----------------------------+----------------------------------------+
| EPD S9908                   | Launch Pad Emergency Procedures        |
|                             | Document                               |
+-----------------------------+----------------------------------------+
| EPD S9909                   | Vehicle Assembly Building (VAB)        |
|                             | Emergency Procedures Document          |
+-----------------------------+----------------------------------------+
| EPD S9910                   | Emergency Preparedness Document for    |
|                             | the O&C                                |
+-----------------------------+----------------------------------------+
| EPD S9911                   | Emergency Preparedness Document for    |
|                             | the VPF                                |
+-----------------------------+----------------------------------------+
| EPD S9926                   | SRB Retrieval and Disassembly Facility |
|                             | Hangar AF Emergency Procedures         |
|                             | Document                               |
+-----------------------------+----------------------------------------+
| EPD S9929                   | Rotation Processing and Surge Facility |
|                             | RPSF Emergency Procedures Document     |
+-----------------------------+----------------------------------------+
| EPD S9932                   | TPSF Emergency Procedures Document     |
+-----------------------------+----------------------------------------+
| EPD S9934                   | CRCA (Wiltech) Emergency Procedures    |
|                             | Document                               |
+-----------------------------+----------------------------------------+
| EPD S9935                   | ARF Complex Emergency Procedures       |
|                             | Document                               |
+-----------------------------+----------------------------------------+
| EPD S9903                   | Launch Control Center (LCC) Emergency  |
|                             | Procedures Document                    |
+-----------------------------+----------------------------------------+
| 3610                        | DOD Manager's Contingency Functional   |
|                             | Plan                                   |
+-----------------------------+----------------------------------------+
| 3611                        | DOD Manager's Turnaround Functional    |
|                             | Plan                                   |
+-----------------------------+----------------------------------------+
|                             | DOD Manager's STS Contingency Support  |
|                             | Procedures Document                    |
+-----------------------------+----------------------------------------+
| DOD 5200.1R                 | Information Security Program           |
|                             | Regulations                            |
+-----------------------------+----------------------------------------+
| ESMC Operations Directive   | Search & Salvage                       |
| (OD) No. 001                |                                        |
+-----------------------------+----------------------------------------+
| ESMC Operations Directive   | ESMC Contingency Support               |
| (OD) No. 004                |                                        |
+-----------------------------+----------------------------------------+

**ATTACHMENT J-1-A**

**EXHIBIT 1.4.9**

**FLIGHT EQUIPMENT GROUPS**

Exhibit 1.4.9 describes the Flight Crew Equipment Groups supporting both
the SSP and ISSP flight and training requirements. This exhibit
represents the broad categories of SPOC accountable Flight Crew
Equipment and includes all approved processing items within the broad
categories. These categories include the associated Ground Support
Equipment. The end items referenced do not reflect a detailed listing of
SPOC accountable FCE or authorized part numbers. Within some groups only
piece parts reside under contractor control and not the final end items.

\(1\) Audio Headsets (e.g. VLHS, GTOE)

\(2\) Audio Microphones (e.g. handheld, wireless, dosimeter)

\(3\) Batteries (e.g. Alkaline, Lithium BCX, Silver Oxide)

\(4\) Cabin Air Cleaner

\(5\) Camera/Still Photography Equipment (e.g. cameras, binoculars,
floodlights, lens, DC power supply)

\(6\) CCTV Hardware (e.g. cameras, lens, blankets, PTU's)

\(7\) Crew Escape Equipment (e.g. ACES, EOS, Quick Donn Mask)

Note: Parachute packing excluded

\(8\) Ergometer (e.g. stowage bag, tools, cover)

\(9\) Food (e.g. pouches, trays, food warmer)

\(10\) GFE cables (e.g. CCTV, camera, laptop, DC power)

\(11\) Housekeeping and Hygiene (e.g. clothing, crew preference,
kneeboard, flashlight)

\(12\) IVA Restraints and Reach and Mobility Aids (e.g. foot restraints,
handholds)

\(13\) IVA Tools and Maintenance Equipment (e.g. IFM tools, tethers, Pin
Kit, Hatch tool)

\(14\) Laptop Computers ISS and SSP (e.g. computers, boards, power
adapters)

\(15\) Liquid Cooling (e.g. garment, jumper)

\(16\) Orbiter Aft Fuselage Gas Sampler System

\(17\) Recorders and Audio Equipment (e.g. cassette, CD)

\(18\) Standard Switch Panel (e.g. closeout/deployment pointing panels,
MPC)

\(19\) Stowage Provisions (e.g. bags, Velcro kits, nets)

\(20\) TCS /Lidar (e.g. TCS, night scope)

\(21\) Video Equipment (e.g. orbiter camcorders, VCR's, minicams)

\(22\) Water Transfer Equipment (e.g. SORG, CWC, filters, hoses)

\(23\) WBSAAMD/SAAMD (e.g. devices, connectors)

**ATTACHMENT J-1-A**

EXHIBIT: 1.5.5.1-B

SPDMS/IWCS APPLICATIONS

+------------------------+---------------------------------------------+
| **BUSINESS ELEMENT**   | **APPLICATIONS (may be modified as          |
|                        | required)**                                 |
+========================+=============================================+
| Flow Requirements      | IDMRD - Intermediate & Depot-level          |
| Management             | maintenance Requirements system             |
|                        |                                             |
|                        | OMRSD - OMRS Documentation                  |
|                        |                                             |
|                        | OMRS/CP - OMRS Change Processing            |
|                        |                                             |
|                        | OMRS/FP - OMRS Flow Planning                |
+------------------------+---------------------------------------------+
| Support Requirements   | ASRS - Automated Support Requirements       |
| Management             | System                                      |
+------------------------+---------------------------------------------+
| Flow Planning          | OMRS/RA - OMRS RCN Assessment               |
|                        |                                             |
|                        | CAPSS - Computer Aided Planning and         |
|                        | Scheduling System                           |
+------------------------+---------------------------------------------+
|                        | GPSS - Ground Processing Scheduling System  |
+------------------------+---------------------------------------------+
| Work Instruction       | OMID - Operations and Maintenance           |
| Development            | Instruction Development                     |
|                        |                                             |
|                        | WAVE -- Work Authorization Validation       |
|                        | Environment                                 |
|                        |                                             |
|                        | MAXIMO                                      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Work Instruction       | DILS - Deviation Index Logging System       |
| Management             |                                             |
|                        | DACS - Document Accounting and Control      |
|                        | System                                      |
|                        |                                             |
|                        | OMID - Operations and Maintenance           |
|                        | Instruction Development                     |
|                        |                                             |
|                        | OMIE - Operations and Maintenance           |
|                        | Instruction Engineering                     |
|                        |                                             |
|                        | PWE/CM - Paperless Work Environment         |
|                        | Configuration Management                    |
|                        |                                             |
|                        | WILMA - Wire List Maintenance System        |
|                        |                                             |
|                        | Documentum                                  |
|                        |                                             |
|                        | MAXIMO                                      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Task Scheduling        | GPSS - Ground Processing Scheduling System  |
|                        |                                             |
|                        | IOS                                         |
|                        |                                             |
|                        | TPSS -- Thermal Protection Scheduling       |
|                        | System                                      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Material Scheduling    | PeopleSoft Production Planning              |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Task Status and        | IOS - Integrated Operations Systems         |
| Tracking               |                                             |
|                        | WAVE                                        |
|                        |                                             |
|                        | MAXIMO                                      |
+------------------------+---------------------------------------------+
| Work Package Build     | OMID - Operations and Maintenance           |
|                        | Instruction Development                     |
|                        |                                             |
|                        | PeopleSoft                                  |
|                        |                                             |
|                        | PWE - Paperless Work Environment            |
+------------------------+---------------------------------------------+
| Work Package           | AMDCS - Automated Management Document       |
| Management             | Control System                              |
|                        |                                             |
|                        | DACS - Document Accountability and Control  |
|                        | System                                      |
|                        |                                             |
|                        | PeopleSoft                                  |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Work Package Execution | DC - Data Collection                        |
|                        |                                             |
|                        | SFC/PAR - Shop Floor Control/ Performance   |
|                        | Analysis Reporting                          |
|                        |                                             |
|                        | CATS -- Constraint Automated Tracking       |
|                        | System                                      |
|                        |                                             |
|                        | FAST -- CPT Flow Automation System Tracking |
|                        | -- Carrier Panel Tracking                   |
|                        |                                             |
|                        | FAST -- CFCT Flow Automation System         |
|                        | Tracking -- CFC Tracking                    |
|                        |                                             |
|                        | FAST -- CT Flow Automation System Tracking  |
|                        | -- Chemical Tracking                        |
|                        |                                             |
|                        | FAST -- TCS Flow Automation System Tracking |
|                        | -- Blanket Removal & Installation Tracking  |
|                        |                                             |
|                        | FAST -- TTS Flow Automation System Tracking |
|                        | -- Tile Tracking & Operations Tracking      |
|                        |                                             |
|                        | FAST -- TC Flow Automation System Tracking  |
|                        | -- Tool Tracking                            |
|                        |                                             |
|                        | DART -- Disconnect Automated Resources      |
|                        | Tracking                                    |
|                        |                                             |
|                        | TSG - Tile Step and Gap                     |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Parts & Materials      | ALRUTS - Automated Line Replaceable Unit    |
| Management             | Tracking System                             |
|                        |                                             |
|                        | AOCS - Automated Ordnance Control System    |
|                        |                                             |
|                        | PeopleSoft Engineering                      |
|                        |                                             |
|                        | PeopleSoft Inventory                        |
|                        |                                             |
|                        | PeopleSoft Production Control               |
|                        |                                             |
|                        | IVD - Item Validation Database              |
|                        |                                             |
|                        | BARS interface - Baseline Accounting and    |
|                        | Reporting System                            |
|                        |                                             |
|                        | KIMS interface - Kennedy Inventory          |
|                        | Management System                           |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Support Equipment      | GRMRS - Global Repetitive Maintenance       |
| Management             | Recall System                               |
|                        |                                             |
|                        | PeopleSoft - Shop Floor Control/ Resource   |
|                        | Tracking                                    |
|                        |                                             |
|                        | CMDS interface - Configuration Management   |
|                        | Data System                                 |
|                        |                                             |
|                        | MAXIMO                                      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Non-conformance        | NCDI - Non-Conformance Data Interface       |
| Management             |                                             |
|                        | PRACA - Problem Reporting and Corrective    |
|                        | Action                                      |
|                        |                                             |
|                        | IMIC interface - Integrated Management      |
|                        | Information Computer interface              |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Workforce Training     | CBT - Computer-Based Training               |
| Management             |                                             |
|                        | OICW - On-line Interactive Courseware       |
|                        |                                             |
|                        | TTSS - Tech Training Scheduling System      |
+------------------------+---------------------------------------------+
|                        |                                             |
+------------------------+---------------------------------------------+
| Business Process       | CIP - Continuous improvement Process        |
| Re-Engineering         |                                             |
|                        | MAP - Management Awareness Process          |
+------------------------+---------------------------------------------+

**ATTACHMENT J-1-A**

**EXHIBIT 1.5.5.2**

**SPOC Support to KSC Institutional Communications Contractor**

1.  The SPOC contractor shall provide a single point of contact for
    validating, coordinating, documenting, communicating, and statusing
    Shuttle administrative and operational communications requirements.

2.  The SPOC contractor shall provide Structural and Power Systems
    Engineering services. Services include, but are not limited to,
    analysis and design support for poles, mounts (concrete or metal),
    pedestals, blast covers, structural supports, cable trays, conduit,
    low voltage and uninterruptible power system (UPS) special
    electrical power within or attached to facilities maintained or used
    by the SPOC contractor.

3.  The SPOC contractor shall provide Instrumentation Systems support
    services. Services include, but are not limited to, in-place
    temperature, humidity, vibration, and acoustic measurements at
    facilities maintained or used by the SPOC contractor.

4.  The SPOC contractor shall provide maintenance and shop support
    services. Services include, but are not limited to, directional
    boring (including providing consumable materials, e.g., casings,
    grease, nuts, bolts); welding; pedestal, mount, and blast cover
    fabrication, removal, installation, painting, and repair; long-run
    (exceeds 200 feet) cable installation, maintenance, and repair;
    cable/connector potting; conduit installation; in place painting;
    corrosion control within the pad perimeter; application of
    ablatives; minor concrete work including roadway repair (including
    providing consumable materials, e.g., grease and oil) but excluding
    roadway asphalt cutting prior to trenching by the institutional
    communications contractor; floor tile removal; fabrication of metal
    tags for use within or attached to facilities maintained or used by
    the SPOC contractor; refurbishment of camera window assemblies;
    utility pole placement and replacement at facilities maintained or
    used by the SPOC contractor; cable tray installation and maintenance
    at facilities maintained or used by the SPOC contractor; outside
    underground cable system air dryer maintenance; purge system and
    purge system connections including flex hoses.

5.  The SPOC contractor shall provide heavy equipment (vehicles
    designated with a Heavy Equipment (HE) number) engineering and
    maintenance support.

6.  MLP 9099 Division of Responsibility

    a.  The SPOC contractor shall:

        i.  Mate/demate 9099 connectors at each MLP location.

        ii. Repair/replace/maintain connectors within the 6-inch
            demarcation on either side of the 9099 interfaces.

7.  Interface between Facilities and Structures maintained or used by
    the SPOC contractor and institutional communications systems:

    a.  The interface between facilities and structures maintained or
        used by the SPOC contractor and institutional communications
        systems is the plane at which the system attaches to the
        facility or structure as documented in system drawings.

    b.  The institutional communications contractor is responsible for
        the design, maintenance, and suitability of attached systems.
        The SPOC contractor shall be responsible for the integration and
        engineering design support, facility modification, and drilling
        and welding; to attach the communication contractor provided
        system to the facility or structure maintained or used by the
        SPOC contractor. Modifications and drilling and welding
        performed by the SPOC contractor shall be accomplished in
        accordance with the institutional communications contractor
        provided, approved, and released drawings.

    c.  Work requests and the design review process will be used by the
        institutional communications contractor to obtain the SPOC
        contractor design support for the institutional communications
        contractor proposed designs.

8.  The SPOC contractor shall be responsible for technical integration
    when multiple contractors have responsibility for components of a
    launch, launch support system, or GSE system. If technical problem
    resolution cannot be achieved, the SPOC contractor will elevate to
    the responsible NASA TMR for mitigation and final resolution.

9.  The SPOC contractor shall identify in detail the data necessary to
    transition non-operational facilities to another entity.

10. The SPOC contractor shall conduct training courses for all
    communications and area access permit requirements to facilitate the
    performance of the institutional communications contractor.

11. The KSC Integrated Control Schedule shall be used by the SPOC
    contractor and institutional communications contractor to schedule
    processing and maintenance support. The institutional communications
    contractor will use the KSC Integrated Control Schedule for
    scheduling high crew and heavy equipment (crane) support for
    communications system Space Shuttle maintenance and test support
    operations.

**ATTACHMENT J-1-A**

**EXHIBIT 1.6.4-A**

**SPOC Flight Operations Systems**

  ------------- ---------------- -------------- -------------- --------------- ---------------- -------------
  **SYSTEM**    **Maintenance\   **Hardware\    **Software\    **Management\   **Integration\   **Flight\
                & Operations**   Sustaining**   Sustaining**   & Integration** & Installation** Readiness\
                                                                                                Assurance**

  Mission                                       C              D               C                A
  Control\                                                                                      
  Center (MCC)\                                                                                 
  Traj apps                                                                                     
  only\                                                                                         
  1.6.4.1                                                                                       

  Integrated    A                A              A              A               A                A
  Training\                                                                                     
  Facility                                                                                      
  (ITF)\                                                                                        
  1.6.4.2                                                                                       

  Integrated                                    B              D                                **A**
  Planning\                                                                                     
  System (IPS)\                                                                                 
  1.6.4.3                                                                                       

  Software      A                A              A              A               A                A
  Production\                                                                                   
  Facility                                                                                      
  (SPF)\                                                                                        
  1.6.4.4                                                                                       

  Operations    A                A              A              A               A                A
  Support\                                                                                      
  Systems                                                                                       
  (OSS)\                                                                                        
  1.6.4.9                                                                                       
  ------------- ---------------- -------------- -------------- --------------- ---------------- -------------

A -- SPOC responsibility

B -- SPOC responsibility for identified SSP and ISS user-related
application software functions (Flight Design and IMARS), all other
responsibilities transition to Operations contractor

C -- SPOC responsibility for Trajectory applications and identified SSP
and ISS user-related applications

D -- Mission specific baseline management and control retained by SPOC

ATTACHMENT J-1-B

PERFORMANCE REQUIREMENTS SUMMARIES

This summary is a cumulative listing of the revised Performance
Requirements contained in RFP Attachment J-1-A, the Space Program
Operations Contract Statement of Work.

Initiatives during the NASA-USA pre-contract "partnering process"
resulted in the revision of the SOW Performance Requirements. These
initiatives are documented in "Decision Packages" developed and approved
by the TMRs and APMs for their respective WBS/SOW areas. Final
disposition of these Decision Packages was accomplished by the SPOC
Convergence Team. The results of this effort are reflected in the
contract SOW and this attachment.

**1.1.6.1 FACILITY MANAGEMENT**

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

Standard: All end products are delivered on schedule

Expectation: 85% of all end products delivered on schedule

MER: 70% of all end products delivered on schedule

Proposed Method of Documenting Performance: TBS

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

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

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

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

Proposed Method of Documenting Performance: TBS

**1.1.6.2 PROPERTY MANAGEMENT**

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

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

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

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

Proposed Method of Documenting Performance: TBS

**1.1.6.3 SECURITY MANAGEMENT**

Required Service: Provide physical access/egress, classified (CI)
information and violence/damage control.

Standard: No security violations, anomalies, unauthorized CI
disclosures, and preventable security incidents.

MER: No violations or incidents that result in compromises, disclosures,
serious personal injury or intentional physical damage.

Proposed Method of Documenting Performance: TBS

**1.4.1.1 RESERVED**

**1.4.1.2 ORBITER LOGISTICS**

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

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

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

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

Proposed Method of Documenting Performance: Logistics ATLAS (Analytical
Trends of Logistics Availability and Supportability) Report - Monthly.

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

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

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

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

Proposed Method of Documenting Performance: Logistics ATLAS Report -
Monthly.

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

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

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

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

Proposed Method of Documenting Performance: Logistics ATLAS Report -
Monthly.

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

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

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

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

Proposed Method of Documenting Performance: Manual feedback from the
TPSF with Briefing Charts - Monthly.

**1.4.1.3 RESERVED**

**1.4.1.5 RESERVED**

**1.4.1.5.2 RESERVED**

**1.4.1.5.4 RESERVED**

**1.4.3.1 ORBITER AND BFS FLIGHT SOFTWARE PROCESSING**

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

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

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

MER: No errors in released test patches caused by BFS for crew training
or testing which cause impacts to mission safety, mission success or
scheduled launch date. There may be errors caused by BFS in the released
test patches which impact areas other than mission safety, mission
success or scheduled launch date.

**1.4.3.3 AVIONICS AND SOFTWARE SYSTEM SUPPORT**

Required Service: Provide I-load Selections.

Standard: Delivered I-loads 100% accurate.

Expectation: No errors requiring redelivery which impacts I-load
development schedules.

MER: No errors requiring patches or waivers or impact safety, mission
success, or major program schedule milestones.

**1.4.3.4 BFS FLIGHT SOFTWARE RECONFIGURATION**

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

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

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

MER: No errors in the BFS flight software configuration caused by BFS
which impact flight safety, mission success, or the applicable scheduled
launch date. There may be errors in the BFS flight software
configuration caused by BFS which impact areas other than mission
safety, mission success or scheduled launch date.

**1.4.3.5 BFS FLIGHT SOFTWARE MODIFICATIONS**

Required Service: BFS OI deliverables.

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

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

MER: No errors in the BFS OI deliverables caused by BFS which impact
flight safety, mission success, or scheduled launch date. There may be
errors in the BFS OI deliverables caused by BFS which impact areas other
than mission safety, mission success or scheduled launch date.

**1.4.3.8 PASS FLIGHT SOFTWARE TOOLS**

Required Service: PASS Application Tools OI deliverables

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

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

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

**1.4.3.9 PASS FLIGHT SOFTWARE IMPLEMENTATION**

Required Service: PASS FSW OI deliverables

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

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

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

**1.4.3.10 PASS FLIGHT SOFTWARE RECONFIGURATION AND MMU INTEGRATION**

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

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

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

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

**1.4.3.13 MEDS MODIFICATION AND MAINTENANCE**

Required Service: MEDS Software Version Increment Deliverables

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

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

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

**1.4.3.14 MEDS SOFTWARE TEST AND OPERATIONS SUPPORT**

Required Service: MEDS Software Interim Release Deliverables

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

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

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

**1.4.3.16 VEHICLE AND PAYLOAD DATA COLLECTION/RECONFIGURATION**

Required Service: Data Reconfiguration Deliverables

Standard: 100% of the data products are error free

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

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

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

Standard: 100% Annex baselined in accordance with PIP schedule

MER: 10% of Annex may be baselined late but in no case impact flight
product deliveries.

**1.4.3.17 SHUTTLE AVIONICS INTEGRATION LABORATORY (SAIL)**

Required Service: SAIL operations system availability.

Standard: 100% SAIL operations system availability

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

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

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

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

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

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

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

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

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

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

**1.4.5.2 RSRM LOGISTICS**

Required services: Spare parts and consumable requests filled from
inventory

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

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

**1.4.5.5 RSRM MODIFICATIONS**

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

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

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

**1.4.6.1 SSME ELEMENT PROCESSING**

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

Standard: 100% baseline configuration certified prior to integration.

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

**1.4.9 FLIGHT CREW EQUIPMENT (FCE) FLIGHT AND TRAINING**\
**HARDWARE PROCESSING**

Required Service: Measure, monitor, and report on time deliveries, head
count, and ciritical skills.

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

MER: 96% of requirements satisfied on or before the negotiated due date.

**1.4.9.4 RESERVED**

**1.5 INTEGRATED LAUNCH AND LANDING OPERATIONS**

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

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

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

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

Proposed Method of Documenting Performance: Shelf Date Objective
Report - Monthly.

Required Service: Meet baselined integrated test schedules.

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

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

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

Proposed Method of Documenting Performance: Automated report to be
developed from KICS system.

**1.5.2.4 LAUNCH READINESS**

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

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

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

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

Proposed Method of Documenting Performance: Current manual constraints
system to be automated on Integrated Work Control System (IWCS).

**1.5.5.2 MAINTENANCE**

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

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

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

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

Proposed Method of Documenting Performance: Facility Operations and
Support Preventive Maintenance Metric Report - Monthly.

**1.5.5.3 SUSTAINING ENGINEERING**

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

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

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

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

Proposed Method of Documenting Performance: Ground Systems Design
Engineering (GSDE) Work Control Database - Monthly.

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

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

Expectation: 98% of all pre-planned contractor-generated CCMS
system/applications software/firmware changes documented prior to
implementation need.

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

Proposed Method of Documenting Performance: GSDE Work Control Database -
Monthly.

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

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

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

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

Proposed Method of Documenting Performance: GSDE Work Control Database -
Monthly.

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

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

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

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

Proposed Method of Documenting Performance: GSDE Work Control Database -
Monthly.

**1.5.5.4 LOGISTICS**

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

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

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

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

Proposed Method of Documenting Performance: DR 1.4-c - Logistics Ground
Customer Support Group.

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

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

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

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

Proposed Method of Documenting Performance: DR 1.4-c - Shop Floor Data
Collection (SFDC).

**1.6.1.3 FLIGHT CREW TRAINING**

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

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

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

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

Proposed Method of Documenting Performance: Flight Operations Process
Integrity Plan.

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

Required Service: Flight critical operations documentation/data

Standard: No significant errors detected real-time in critical flight
operations documentation or data.

Expectation: 1 significant FDF/ODF documentation or data error for each
flight, but in no case impact safety, mission success or major program
schedule milestones.

MER: 2 significant FDF/ODF documentation or data error for each flight,
but in no case impact safety, mission success or major program schedule
milestones.

Standard: On time delivery of all agreed upon FDF/ODF operations
documentation for crew review.

Expectation: One FDF/ODF document per flight delivered late based on the
agreed upon delivery content, but in no case impact safety, mission
success or major program schedule milestones.

MER: Two FDF/ODF documents per flight delivered late based on the agreed
upon delivery content, but in no case impact safety, mission success or
major program schedule milestones.

Proposed Method of Documenting Performance: Flight Operations Process
Integrity Plan.

**1.6.2.2.2 FLIGHT DESIGN PRODUCTS**

Required Service: Provide Flight Design Products (DR 1.6.2.2.2-c).

Standard: No errors in the initial delivery of critical flight design
products.

Expectation: 2 % errors in initial delivery of critical flight design
products, and in no case impact safety, mission success or major program
schedule milestones.

MER: 4 % errors in initial delivery of critical flight design products,
and in no case impact safety, mission success or major program schedule
milestones.

Standard: On time delivery of critical flight design products.

Expectation: 3 % late delivery of critical flight design products, and
in no case impact safety, mission success, or major program schedule
milestones.

MER: 5 % late delivery of critical flight design products, and in no
case impact safety, mission success, or major program schedule
milestones.

Proposed Method of Documenting Performance: Flight Operations Process
Integrity Plan.

**1.6.2.7 DATA COLLECTION/RECONFIGURATION**

Required Service: Data Reconfiguration Deliverables

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

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

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

Proposed Method of Documenting Performance: DR 1.6-b, Flight Operations
Process Integrity Plan

**1.6.4 FLIGHT OPERATIONS SYSTEMS AND EQUIPMENT**

Required Service: Flight operations system availability.

Standard: 100% flight operations system availability for the SMS, SSTF,
and SPF.

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

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

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

Proposed Method of Documenting Performance: Flight Operations Process
Integrity Plan

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

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

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

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

Proposed Method of Documenting Performance: Flight Operations Process
Integrity Plan

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

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

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

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

Proposed Method of Documenting Performance: Flight Operations Process
Integrity Plan

**1.6.4.1 RESERVED**

**1.6.4.3 RESERVED**

ATTACHMENT J-1-C

RESERVED

ATTACHMENT J-1-D

RESERVED

ATTACHMENT J-2

GLOSSARY, ACRONYMS, AND ABBREVIATIONS

Certain terms, acronyms, and abbreviations used in this contract are
listed and defined below. This Attachment J-2 is for informational only.
If and to the extent any definition contained below conflicts with any
other portion of the contract, the other portion of the contract shall
prevail.

ABF Air Bearing Floor

AC Assembly Complete

ACA Associate Contractors' Agreement

ACO Assembly and Checkout Officer

ACOMC Assembly Checkout Operations Maintenance Configuration

ADC Analog-to-Digital Converter

ADCF Analog-to-Digital Converter Function

ADP Automatic Data Processing

Acceptance Data Package

ADTL Additional

A/F Air Force

AFSIG Ascent Flight System Group

AIS Automated Information System

AIT Analysis and Integration Team

ANSI American National Standards Institute

AOSS Astronaut Online Scheduling System

Assigned Flight Crew - Those astronauts assigned to a specific mission.
(See "Flight Crew")

APFPF Attitude & Pointing Flight Production Facility

ARF Assembly Refurbishment Facility

ASCAN Astronaut Candidate - Individual in the first year of training
after being selected to the astronaut corps.

ASDEP Avionics Software Development Environment Pathfinder

ASQC American Society for Quality Control

AST American Segment Trainer

ATA Action Tracking Application

ATL Attitude Timeline

ATP Assembly Training Plan

Authority to Proceed

ATV Autonomous Transfer Vehicle

AWLs Automated Wire Lists

BARS Baseline Accounting and Reporting System

BET Best Estimated Trajectories

BFS Back-up Flight System

BSS Backup System Services

Cannibalization - The removal of a component from an operating flight
system or from critical processing or launch system (facility or
equipment) for immediate reinstallation into an inoperative flight
system or into critical processing or launch system (facility or
equipment) in order to restore it to operational condition.

Critical Process or Product Characteristic - Features of a material,
part, or process whose variation has a controlling influence on a
service or product's attributes such as fit, form, function, service,
life, safety, reliability, risks, cost performance, or schedule
performance.

C&D Command and Data

C&T Communication and Tracking

CAF Contractor Accountable Function

CAM Centrifuge Accommodations Module

Capability -- A bounded function performed for the SSP in order to
accomplish its mission execution requirements. A capability may be
comprised of workforce, facilities/equipment, suppliers and contracts,
which together produce a product or service.

CAR Corrective Action Record

Certification Approval Request

CBM Cargo Bay Mission

CCAS Cape Canaveral Air Station

CCB/D Configuration Control Board/Directive

CCCD Crew Compartment Configuration Drawing

CCCR Crew Compartment Configuration Review

CCR Cargo Compatability Review

CCT Crew Compartment Trainer

CDDT Common Display Development Team

CDR Critical Design Review

CDPA Controlled Document Production Area

CDWG NASA Countdown Working Group

CEI Contract End Item - A principal deliverable under a contract; e.g.,
RSRMs and ETs.

CEIT Crew Equipment Interface Test

Certification (of individual in job or position) - Documentation that an
individual has accomplished all training and qualification requirements
to perform the identified position, job, or duty. Final certification is
granted by the organization responsible for the position, job, or duty.

CFE Contractor-Furnished Equipment

CFM Contractor-Furnished Material

CFM Cubic Feet per Minute

CFP Conceptual Flight Profile

CI Configuration Inspection

CIG Connectors Integrity Group

Critical Flight Design Products - Flight design products which affect
safety, mission success, or have a significant impact to users external
to the flight design process (I-loads, Range Safety, MCC, SMS, FDF)

CIL Critical Items List - A list of all Criticality 1 and 1R items from
the FMEA, the failure of which could result in loss of life or vehicle.
Each failure cause has preventive rationale listed. Prepared in
accordance with NSTS-22206.

CIP Class 1 Integration Plan

CIR Cargo Integration Review

CLS Contingency Landing Site(s)

CM Configuration Management

CMMATs Critical Math Models and Analysis Tools

CMMDB Critical Math Model Database

CMDS Configuration Management Documentation System

CMR Contract Management Reviews

COD Center Operations Directorate (JSC)

CofF Construction of Facilities

CoFR Certificate of Flight Readiness - The process and documents that
certify flight hardware, personnel, and supporting systems are ready to
support flight milestones.

COQ Certificate of Qualification - Contractor statement that all
requirements are met or waived for each major component; requires Level
III approval.

COSS Crew On-orbit Support System

COTR Contracting Officer\'s Technical Representative - A Government
employee authorized by the contracting officer to provide technical
direction to the contractor. (See G.5 of the contract for a definition
of \"technical direction.\") The COTR and Alternate COTR (who may act
only in the COTR\'s absence) are the only Government employees other
than a Contracting Officer who may give technical direction to the
contractor.

COTS Commercial-Off-The-Shelf

COU Concept of Operations and Utilization

COUP Consolidated Operations and Utilization Plan

CPCB Crew Procedures Control Board

Crew Certification Guide - ISS flight crew curriculum and lesson
syllabus.

Crew Training Catalog - SSP flight crew curriculum and lesson syllabus.

Crew Training Plan - Flight/Mission unique plan to accomplish training
requirements within documented guidelines and constraints. Plan is a
function of individual crew capabilities at training start, crew
training catalog or cert guide, and flight/increment specific
requirements. Scope of plan covers all individual and full crew
scheduled activities.

CPDS Computer Program Development Specification

CPIC Capital Planning and Investment Control

CR Certification Requirement or,

Change Request

Critical position -- A position which requires: highly specialized
skill(s), expertise or knowledge, or requires a long training time to
bring someone up to speed. This position must be maintained to ensure
mission success and is at or below minimum staffing levels. (General
rule -- this position is so unique it is identifiable by the
individual's name or specific skill set.)

CSCI Computer Software Configuration Items

CSR Customer Service Room

CV Configuration Verification

CVAS Configuration Verification Accounting System

Data - Scientific, technical, or management information obtained from or
required to support engineering, development, test operations, research
programs, or contract administration. Data denotes recorded information,
specifications, drawings, lists, and standards, and may exist as printed
matter, instrument recordings, holograms, spectrograms, magnetic tapes
and discs, punched cards, micrographics, sound recordings, computer
programs, electronic storage media, and film.

DCN Document Change Notice - Notification of change to a D&V Plan,
Hazard, or CIL; submitted to Level III via an ECP.

DCR Data Change Request

DDS Detailed Design Specification

DEU Display Electronic Unit

DFRC Dryden Flight Research Center

DICM Detailed Integrated Cargo Manifest

DIP Data Integration Plan

DLSR Delta Launch Site Review

DOC Department of Commerce

DoD Department of Defense

DOLILU Day of Launch I-Load Update

DOS Department of State

DOSS DOLILU Operations Support System

DPD Data Procurement Document - A compilation of all documents that
describe the data requirements of this contract.

DPS Data Processing System

DR Disposition Record/Data Requirement

DR Discrepancy Report - Contractor report of an article or material that
does not conform to applicable drawings, specifications, or other
requirements.

DRA Document Release Authorization

DRD Data Requirement Description - A detailed description of a required
data item, including purpose, content, format, references, maintenance
requirements, submittal requirements, and other pertinent information.

DRL Data Requirements List - A list of DRDs applicable to this contract.

DSO Detailed Supplementary Objective

DT -- Mail code for the MOD Training Division.

DTO Developmental Test Objective

D&V Development and Verification - Implementing documentation which
identifies all CEI design requirements versus planned verification
efforts.

EC Engineering Cycle

ECLSS (ISS) Environmental Control and Life Support Systems

ECO Engineering Change Order - Document generated to implement approved
changes to design drawings or specifications of a component.

ECP Engineering Change Proposal - The media for the contractor to
formally present to the appropriate CCB proposed engineering changes to
NASA configuration baselines for complete assessment by NASA.

ECR Engineering Change Request - A NASA-initiated request to change NASA
technical baselines.

ECS Engineering Change Sheet - Documents the implementation of

an ECO; or,

Environmental Control System

EDC Engineering Design Change

EDCPs Engineering Design Change Proposals

ELV Expendable Launch Vehicle

EMA Electromagnetic Measurement and Analysis

EME Electromagnetic Effects

EMU Extravehicular Mobility Unit

EO Engineering Orders

EOC Emergency Operations Center - One of the subelements of the Mission
Control Center (MCC) at JSC.

Essential position -- A position which provides a function which is
required to support the mission. (General rule -- the function is
required but the skill is not so specialized that a specific individual
is required to perform it.)

ET Space Shuttle External Tank - A major component of the Space Shuttle,
to which SRBs are mated.

EVA Earned Value Analysis; or Extravehicular Activity

FAR Federal Acquisition Regulation

FACI First Article Configuration Inspection

Flight Controller - includes all Space Shuttle flight controllers and
Station mission controllers. Flight controllers consist of Flight
Control Room (FCR) and Multi Purpose Support Room (MPSR) positions which
monitor real-time spacecraft operations, execute appropriate command
loads, recommend alternative actions, and otherwise provide integrated
trajectory, payloads, and systems expertise.

Flight Controller Training - Includes all training aspects \-- generic,
flight specific and proficiency \-- leading up to the final
certification of flight controllers and their proficiency.

FAO Flight Activities Officer

Flight Critical - includes all products, services, and decision making
which affect the safety of the crew and/or vehicle.

FC Flight Cycle

FCE Flight Crew Equipment

FCOD Flight Crew Operations Directorate (JSC)

FCOS Flight Computer Operating System

FCP Flight Software Change Proposal

FCR Flight Control Room \[in the MCC\]

FCT Flight Control Teams

FDD Flight Design and Dynamics

FDF Flight Data File Shuttle On-board crew procedures.

FDHB Flight Design Handbook

FDO Flight Dynamics Officer or Fee Determination Official

FDR Functional Design Review

FDRD Flight Definition and Requirements Directive

FEC Field Engineering Change - The method for initiating and expediting
\"make safe/make fit/make operable\" changes at NASA Using Sites (e.g.,
at the launch site), and the documentation thereof.

FEIDS Flight Equipment Interface Devices

FEWG Flight Evaluation Working Group - The coordinator of detailed
assessment and documentation of all MSFC-related hardware, and
inter-center point of contact for historical flight data.

FIDP Flight Implementation Data Pack

FIP Federal Information Processing

FL Final Load

Flight Crew - All astronauts, astronaut candidates, and their
management. (See "Assigned Flight Crew")

Flight Design - includes all trajectory and consumable analysis and
product development required to support a Space Shuttle or ISS mission.
Functional design areas include: ascent, orbit, rendezvous, proximity
operations, descent, navigation, consumables and flight integration.

Flight Planning - The process of preparing a flight plan which contains
a detailed timeline of the crew's activities for a specific flight. The
planning process includes all the premission planning effort necessary
to develop the flight unique consumable loadings, determination of
Shuttle Mass Properties, consumables management plans, unique payload
and system management plans and procedures, integration of payload
systems with respect to Orbiter systems performance and limitations,
PDRS and EVA techniques and procedures. And it includes the
participation in the development and maintenance of Flight Operations
Documentation, Procedures, and Tools.

Flight Specific Orbiter Systems Crew Training - Formal Crew Training
Catalog Orbiter systems and operations training for assigned flight
crews, measured from SMS Training Start through launch. Does not include
Station training, Orbiter payload training and EVA training.

Flight Systems - For purposes of flight control, this includes, but is
not limited to, External Tank, Solid Rocket Boosters, Orbiter and
Station, systems. Examples include Main Propulsion, Electrical,
Environmental, Mechanical, Guidance, Navigation, Data and Communications
Systems. Payload Deploy Retrieval System, Extravehicular Manned
Spaceflight suit, and Inflight Maintenance are also included.

Flight Rules - Document that contains all the preflight approved mission
rules and priorities.

Fly-out -- Assuring that Shuttle assets and capabilities are sustained
through the completion of the manifest.

FMA Flight Margin Assessment

FMEA Failure Mode Effects Analysis - Documents all possible failure
modes in a system design within specified ground rules; identifies items
critical to mission success and vehicle and crew survival, and ranks
them according to their criticality category.

FMR Facility Management Reviews

FOP Flight Operations Panel

FOR Flight Operations Reviews

FOT Flight Operations Trainers

FPM Flight Production Managers

FPS Flight Planning System

FPSB Flight Production Schedules Board

FPSR Flight Planning and Stowage Review

FPSWG Flight Production Schedules Working Group

FRCB Flight Rules Control Board - Responsible for Flight Rule approval.

FRD Flight Requirements Document

FRED Final Reconfiguration Engineering Drawings

FRFR Flight Readiness Firing Review - A CoFR review prior to on-pad
engine tests.

FRR Flight Readiness Review - A CoFR review of open work, technical
issues, etc., prior to flight.

FSHR Flight System Hazard Report - List of potential sources of danger
and recommended resolutions/controls for conditions found in hardware
and software systems, prepared in accordance with NSTS-22254.

FSM Flight Support Motor - A RSRM used for static test firing.

FSS Flight Software System Requirement

FSSR Flight Software Functional Requirements

FSW Flight Software - Onboard GPC software

FSWAT Flight Software Application Tools

FSW/OI \[Orbiter\] Flight Software Operational Increments

GA Group Administrator

GAFD Government Accountable Functions Directive

GCAR Government Certification Approval Request

GCTC Gagarin Cosmonaut Training Center

GEI Ground Environmental Instrumentation - On-pad environment monitoring
hardware.

GFE/M/P Government-Furnished Equipment/Material/Property

GIDEP Government-Industry Data Exchange Program

GLS Ground Launch Sequencer

GMEMS General Purpose Computer Memory Patches

GN&C Guidance, Navigation and Control

GNS Guidance and Navigation Simulator

GOAL Ground Operations Aerospace Language

GORR Ground Operations Readiness Review

GPC General Purpose Computer - Shuttle on-board flight computers.

GPCIPL General Purpose Computer Initial Program Load

GPO Guidance and Procedures Officer

GSO Guidance Support Officer

GSE Ground Support Equipment - Non-flight hardware used in the
transport, handling, launch preparation, and launch of the Shuttle and
its components.

GSRP Ground Safety Review Panel

GUCP Ground Umbilical Carrier Plate

HAL/S High-order Assembly Language/Shuttle

HDX Hardware Dependent Executive

HMF Hypergol Maintenance Facility

HOSC Huntsville Operations Support Center

HW/SW Hardware/Software

HTV Human Thermal Vacuum

H-11 Transfer Vehicle

IBCB Integrated Baseline Control Board

ICD Interface Control Document - Documentation in the form of
specifications, drawings and written record that identifies for each
side of an interface those necessary design requirements between
different contractors and/or Government agencies that will assure an
agreeable and compatible interface (e.g., RSRM interfaces with SRB
items).

ICHA Integrated Cargo Hazard Assessment

ICD Interface Control Document

ICED Integrated Configuration Engineering Data

ICP Inventory Control Point

IDD Interface Design Document

IDP-BSL Integrated Display Processor-Bootstrap Loader

IDR Interim Discrepancy Reports

IDS I-Load Dataset

Integrated Data System

IDRD Increment Definition Requirements Document

IFA In-Flight Anomaly - An anomaly that occurs in the interval from T-6
hours to end of element mission.

IIR Increment Integration Review

ILM I-LOAD Manager

I-LOAD Initialization Load - Mission-unique onboard GPC Flight software
variable.

Integrated Simulation - Training exercise involving a Shuttle or Station
flight EVA in the SMS or SSTF and the Mission Control Team in the MCC.

IMARS ISS MOD Avionics Reconfiguration Systems

IMS ISS Inventory Management and Stowage

IOP Ignition Over Pressure

IP Integration Plan

IPCL Instrumentation Program and Components List

IPL In-Process Loss - An estimating factor derived from project history
to account for manufacturing scrap.

IPT Integrated Product Team

IPS Installation Provided Service/s

IPS Integrated Planning System - Consists of hardware, platform software
(custom and COTS), and application software required to provide planning
and analysis in support of the SSP and ISS. This facility is located in
building 30A, 30S, 30M, 4N, and 17 at the Johnson Space Center, and at
600 Gemini. Included in the IPS Facility management and operations
function are the following subelements; Ascent/Entry Trainers, Proximity
Operations (Prox Ops), Robotics Planning Facility (RPF), Reusable Object
Software Environment (ROSE), Day-of-Launch (DOL) MPSR.

IPS Critical Function - DOLILU

IPV International Procedure Viewer

IRD Interface/Installation Requirement Document

IRN Interface Revision Notice - Used to record approved ICD changes.

ISD Instructional Systems Development (USAF)

ISO International Standardization Organizations

ISS/P International Space Station/Program

ITF Integrated Training Facility - The Integrated Training Facility
(ITF) consists of hardware, platform software (custom and COTS), and
mission-specific application software required to provide flight crew
and mission controller part task training, standalone and integrated
simulations and testing capabilities for the mission operations in
support of the SSP and ISSP. The ITF includes the Shuttle Mission
Simulator (SMS) and the Flight Ops Trainers (FOT) which consist of Bldg.
4S-Single System Trainers (SST), Prototype Part Task Trainer (P2T2),
Payload Trainer (PLT), Playback Trainer (PBT), Flight Control Trainer
(FCT), Crew Software Trainer (CST), International Space Station Part
Task Trainer (ISS PTT)'s, Computer Based Training (CBT), Video Rooms.
The Space Station Training Facility (SSTF) is currently a development
project.

IVT Independent Verification Testing

IWCS Integrated Work Control System

IWG Interface Working Group - Formal committees established to oversee
interface design compatibility between interfacing end items; provides
technical approval of designated ICDs.

JAEL JSC Avionics Engineering Laboratory

JEM Japanese Experiment Module

JHB Johnson Handbook - One identifier of formal JSC policy or procedures
issuances.

JIS Joint Integrated Simulation - Integrated simulation that includes
one or more POCCs.

JMI Johnson Management Instruction - One identifier of formal JSC policy
or procedures issuances.

JMP Joint Management Plan

JOP Joint Operating Procedure

JOVR Joint On-orbit Verification Review

JSC Lyndon B. Johnson Space Center

JST Japan Segment Trainer

JTWG Joint Technical Working Groups

KATS KSC Avionics Test Station

Key Decision Date -- Date at which a disposition decision is needed in
order to promptly begin capability phase out at its last need date.

KHB Kennedy Handbook - One identifier of formal KSC policy or procedures
issuances.

KSC John F. Kennedy Space Center

KW Kilowatt

L-1/L-2 L-1 Milestone Review and L-2 Milestone Review - CoFRs conducted
24 hours and 48 hours, respectively, before Shuttle launch.

Last Need Date -- Date at which the capability can be phased out of the
SSP without incurring any unacceptable risk to mission execution.

LAT Lot Acceptance Test - Qualification of materiel by testing
representative samples of a target population of the materiel.

LC-39 Launch Complex-39

LCC Launch Commit Criteria - Operational constraints for launch.

LCWG Launch Countdown Working Group

LETF Launch Equipment Test Facility

L&L Launch and Landing

LLI Limited Life Item - Materiel restricted to use within a specified
period after manufacture. Also used in reference to limits on time
cycles.

L&M Logistics and Materials/Logistics and Maintenance

LPS Launch Processing System

LRU Line Replaceable Unit - Assemblies and items which can be removed
and replaced as a unit from a system at the operating location.

LSEAT Launch Systems Evaluation Advisory Team

LSFR Launch Site Flow Review

LSO Landing Support Officer

LSRR Launch Site Requirements Review

LSS Launch Site Support - Contractor effort provided at KSC.

Major Findings - (1) The identification of a critical process or product
characteristic, system procedure, or planning function which does not
comply with or effectively achieve the requirements or policies to which
the auditee is held accountable; (2) The identification of one or more
characteristics of a comprehensive plan, system procedure, or process
for which processing trends indicate the potential for failure to
achieve a desired product or service as established by the customer's
requirements and policies; (3) The accumulation of identified findings
which indicate an overall systemic lack of compliance to requirements
and policy standards or the effectiveness in achieving the standards to
which the auditee's process, procedure, or plan is measured. NOTE: The
identification of a finding is based on objective evidence collected
during interviews, examinations of documents or records, process
analysis or observation of activities and conditions in the area of
concern.

M&P Materials and Processes

MAF Michoud Assembly Facility

MAIL Mockup and Integration Laboratory

MAGRS-3S Miniature Airborne Global Positioning System(GPS) Receiver
Shuttle-3 String

MAR Mid-Deck Accommodation Rack

MAST Measurement and Stimuli Database

MATCO Materials Accountability Tracking and Control - Contractor data
base listing materials approved for use in Space Shuttle systems, and
which indicates where they are used.

MBARS MSFC Baseline Accounting and Reporting System

MCAR Minor Construction, Alteration, and Repair

MCB Materials Control Board - Contractor board which establishes and
maintains a listing of materials and components which are acceptable for
use in the fabrication of RSRMs.

MCC Mission Control Center - Consists of all hardware and software,
custom and COTS, required to provide command and control capabilities
for mission operations in support of the SSP and ISSP. This facility is
located in buildings 30M and 30S at the Johnson Space Center. Included
in the MCC Facility management and operations function are the following
subelements: Rapid Prototyping Lab (RPL), Mission Operations Integration
Room (MOIR), Orbiter Data Reduction Center (ODRC), Meteorological
Interactive Data Display System (MIDDS), JSC Emergency Operations Center
(EOC).

MCC Critical Functions - Command, Telemetry, Trajectory, Voice.

MCPP Mission Configuration Program Plan

MCR Master \[Software\] Change Record

MDD Mate/Demate Device

MDF Mission Definition

MDUF Multifunction Display Unit Function

MDUF FVT Multifunction Display Unit Function Formal Verification Test

MDU-UDI Multifunction Display Unit User Development Interface

MECO Main Engine Cut-Off

MECSLSI Mission Equipment Cargo Support Launch Site Integration

MEDS \[Orbiter\] Multi-functional Electronic Display Subsystem

MER Maximum Error Rate

Mission Evaluation Room

MGI Mandatory Government Inspection - Manufacturing and materiel
characteristics requiring inspection by a Government representative.

MHB Marshall Handbook

MIDDS Meteorological Interactive Data Display System - One of the
subelements of the Mission Control Center (MCC) at JSC

MIP Mission Integration Plan, or Mass Memory Integration Plan,

or

Master Inspection Plan - List of all inspections, including MGIs, and
how they will be accomplished.

MIS Management Information System

MLN Management Level Network

MM Marshall Manual - One identifier of formal MSFC policy or procedures
issuances.

MMI Marshall Management Instruction - One identifier of formal MSFC
policy or procedures issuances.

MMUS Mass Memory Unit/Simulator

MOC Mission Occurrence

MOD Mission Operations Directorate

MOIR Mission Operations Integration Room - One of the subelements of the
Mission Control Center (MCC) at JSC

MOM Multifunction Display Unit Object Manipulator

MPLM Mini-Payload Logistics Module (ISS)

MPS Main Propulsion System

MPV Manual Procedures Viewer

MPSR Multi-Purpose Support Room

MRB Materials Review Board - A group composed of Government and
contractor representatives that review and disposition DRs.

MRCS Mission Requirements Control System

MRI Material Review Instruction - Additional instructions provided on a
DR when materiel requires additional inspection, testing, or continued
processing.

MRMDF Multi-Use Remote Manipulator Development Facility

MSA Mission Safety Assessment - Assessment of program activity (e.g.,
waivers) that might cause an impact upon the baseline risk level.

MSFC George C. Marshall Space Flight Center

MSID Measurement Stimulus Identification

MTS Multifunction Electronic Display System Test Station

MVS Multiple Virtual Storage

NACC NASA ADP Consolidation Center

NASA National Aeronautics and Space Administration

NBL Neutral Buoyancy Laboratory

NBT Neutral Buoyancy Trainer

NDE Nondestructive Evaluation - Test and analysis of engineered
equipment that does not alter the useability of that equipment.

Negotiated need date - A date established by the end user and supplier
after the supplier has stated any constraints to immediate delivery of
required items.

NEQA NASA Engineering and Quality Audit

NEWS New Engineering Work System

NFC Non-Flight Constraint

NFS NASA FAR Supplement - NASA's supplement to the FAR; part of the
Federal Acquisition Regulation System

NFS National Federal Schedule

NHB NASA Handbook - One identifier of formal NASA policy or procedures
issuances.

NME Non-Maintainable Equipment

NMI NASA Management Issuance - One identifier of formal NASA policy or
procedures issuances.

Non-flight critical - includes all products, services, decision making
which are not flight critical.

NPA Normal Process Allowance - Estimating factor derived from project
history to account for manufacturing rework requirements and any
incomplete posture of the manufacturing standard.

NPR NASA Procedural Requirement

NSD NASA Standard Detonators

NSI NASA Standard Initiators

NSTS National Space Transportation System - A generic descriptor applied
to Level I and Level II documents, which reflects the name of the
program before it became simply the Space Shuttle Program.

NVR Non-Verification Required

OAS Office Automation System

OASIS Online Appearance Scheduling Information System

OBS Organizational Breakdown Structure - A heirarchical diagram of the
total contract work to be performed. The diagram separates the
organization into elements depicting increasing levels of detail. It is
often combined with a Work Breakdown Structure (WBS) to form a matrix of
work elements by responsible organization(s).

OCTF One-Cycle-to-Flight

ODF Operations Data File ISS onboard crew procedures.

ODRC Orbiter Data Reduction Center - One of the subelements of the
Mission Control Center (MCC) at JSC

OFI Operational Flight Instrumentation - Instrumentation on flight
hardware, such as pressure transducers installed and operative on all
flight motors that measure igniter and motor chamber pressure.

OI Operational Increment - Flight software version indentifier; or,

Operational Instrumentation

OIU Orbiter interface Unit

OMD Operations and Maintenance Directive - Contractor input into the KSC
operating procedures (OMI).

OMDP Orbiter Maintenance Downtime Period

OMI Operations and Maintenance Instruction - KSC procedures which
control the pre-launch through post-launch processing of hardware at
KSC.

OMID Operation and Maintenance Instruction Document

OMRSD Operations and Maintenance Requirements and Specification
Document - Design center requirements imposed on KSC.

OPCB Operations Procedure Control Board

OPF Orbiter Processing Facility

OPS Operations

OPS LAN Operations Local Area Network

ORI Operational Readiness Inspection - Formal inspection and
certification of new equipment and facilities for use.

ORLA Optimum Repair Level Analysis - The process whereby the optimum
repair level is determined. The \"optimum repair level\" is the
maintenance level selected to perform specific tasks and functions for a
given equipment item. The decision to repair equipment at the indicated
maintenance level requires that all authorized maintenance capability
(remove, replace, assemble, or test) be provided to that level.

ORMR Orbiter Rollout/ET Mate Milestone Review

ORR Operations Readiness Review

ORU Orbital Replacement Unit

OSHA Occupational Safety and Health Administration

OTIS Orbiter Test and Information System

Out-of-Family - Operations or performance outside the expected
performance range of parameters or that which has not previously been
experienced is out-of-family. The disposition of discrepancies or
nonconformances which affect the configuration, certification, mission
success, safety critical functions, hazard control, or weight in excess
of two pounds (equivalent performance to orbit) is out-of-family.
Adverse problem trends are out-of-family. Discrepancies or
nonconformances which the operator determines require design element
analysis or assistance for resolution are out-of-family. Unexplained
anomalies or events are out-of-family. Any activity or condition not
expressly defined as in-family is out-of-family.

Oversight - Traditional NASA management philosophy of watchful care or
management; supervision. An intrusive process of gathering Contractor
product or process data through on-site, in-series involvement in the
process. Oversight entails a form of control over the process itself.
Oversight is an involvement in an activity, principally through
inspection with review and approval authority implicit to the degree
necessary to assure that a process or product's key characteristics are
stable and in control.

PABF Precision Air Bearing Floor

PADS Problem Action Data System

Payload Training Requirements - Currently contained in PIP annex 7
(training). Agreement with payload customer, program office, and flight
operations training (currently spaceflight training division) that
establishes detailed requirements and responsibilities for training
payload unique (flight specific) training.

PASS Primary Avionics Software System

PAT Preflight Adaption Trainer

PCASS Program Compliance Assurance and Status System

PCCMU Pulse Control Modulated Master Unit

PCIN Program Change Identification Number - A Space Shuttle Program
identifying number assigned to each change package submitted for
approval.

PCP Project Change Proposal - A contractor-initiated proposal to change
to contractual requirements other than those contained in contract
technical baseline documents.

PDCN Preliminary Document Change Notice - A proposed DCN submitted with
an ECP.

PDL Payload Downlist

PDMS Payload Data Management System

PDR Preliminary Design Review

PDT Payload Data Tape

PEEP Postfire Engineering Evaluation Plan - Provides details of what to
inspect and document during the postflight disassembly and inspection
process

PER Preliminary Engineering Report

PERB Program Engineering Requirements Board

Performance Objective - A measurable, observable learning objective
which provides significant evidence of the ability to execute a required
task. Ideally, performance objectives are stated behaviorally and at the
appropriate level of learning. If required, conditions under which the
student will be tested and standards to which the student must perform
are included.

PF Principal Function

PFAR Postflight Anamoly Report - Documentation of the disassembly
team\'s findings.

PILOT - An on-board simulation loaded onto a portable computer to help
the crew review the entry trajectory during long orbital flights.

PGS Partial Gravity Simulator

PGSC Payload and General Support Computer

PIP Payload Integration Plan

PIRN Preliminary Interface Revision Notice - A proposed ICD change.

PL Payload

PLS Primary Landing Site

PLUTO PLugin Utilization Officer

PMRB Program Material Review Board

PMS Performance Measurement System

PMRB Program Material Review Board

POC/A Portable Onboard Computer/Adjunct

POCC Payload Operations Control Center

POCCB Payload Operations Control Center Board

POP Program Operating Plan - Program budget, formally updated annually
or semi-annually.

POS Parts On Shelf or Probability of Sufficiency

PPTB Program Provisioning Task Book

PR Problem Report - Documentation of anomalous conditions found at KSC.

PRACA Problem Reporting and Corrective Action

PRB Problem Review Board - Level III board that reviews, dispositions,
or recommends the disposition of, SPRs.

PRCB Program Requirements Control Board - Level I: The controlling
authority for changes to the Level I Program Requirements Document and
Level I change criteria; established by the authority of the Director,
Space Shuttle Program. Level II: The controlling authority for all
changes to Level II Program Definition and Requirements Documents,
Master Verification Plan, and Level II Interface Documents; established
by the authority of the Deputy Director, Space Shuttle Program.

PRCBD PRCB Directive

PRD Program Requirement Document

PRF Parachute Refurbishment Facility

PRP Personnel Reliability Program

PRACA Reportable Problems

PRR Payload Readiness Review

PSCN Preliminary Specification Change Notice - A proposed SCN submitted
with an ECP.

PSRP Payload Safety Review Panel

PTC Payload Training Complex - Training simulator located in the
Integrated training facility. The PTC will be utilized for ISS Payload
Training. The ISS payload training requirements and responsibilities
will be defined be the Station Utilization Office.

PTR Performance Test Review

PTT Part Task Trainer

PV Procedure Validation

PVIS Program Verification Information System

PVL Previously Verified Load

PVLR Preliminary Verification Loads Review

PVTR Preliminary Verification Thermal Review

PWC Primary Work Code

QD Quick Disconnect

RACF Resources Access Control Facility

RCN Requirements Change Notice - Documents a proposed OMRSD change.

RDGS Reconfigurable Display Generation System

RDMA Risk Database Management Application

Release Date -- Date when facilities can be turned over to receiving
entity, for example,such as an institutionsor a follow-on program. This
occurs after last need date to allow for any clean-up, safing,
documentation, or other preparation needed to meet handover
requirements.

RF Radio Frequency

RHFAs Reusable Hardware Flight Authorizations

R1 Recon 1

RID Review Item Discrepancy - Formal documentation, during the design
phase of an item, of requirements and hardware discrepancies, with
recommended dispositions tracked to final resolution.

RME Risk Mitigation Experiments

RMS Remote Manipulator System or Random Motion Simulator

RPL Rapid Prototyping Lab - One of the subelements of the Mission
Control Center (MCC) at JSC

RPS Rendezvous Procedures Support

RPSF Rotational, Processing and Support Facility

RSRM Reusable Solid Rocket Motor - A solid rocket motor designed and
manufactured for use with the Space Shuttle. A principal component of
the SRB.

RSS Rotating Service Structure

RST Russian Segment Trainer

RTLS Return to Launch Site

Safing -- Includes the removal of hazardous subsystems, fluids or
materials, deactivation of high pressure gas systems, and deactivation
of electrical systems.

SAS Software Authorization Sheet

SASCB Shuttle Avionics Software Control Board

SAIL Shuttle Avionics Integration Laboratory

SAN Software Authorization Notice

SAR Special Action Requests

SASR Shuttle Avionics Systems Review

SC Systems Control

SCA Shuttle Carrier Aircraft

SCAPE Self-Contained Atmospheric Protective Ensemble

SCN Specification Change Notice - Formal documentation to record exact
changes to all approved specifications.

SCR Software Change Request

SDF Software Development Facility

SDP Shuttle Data Processing

SDS Shuttle Drawing System

SEIS Standard End Item Specification

SIASS Shuttle Integrated Accounting Status System

SICB Systems Integration Control Board

SID Simulation Interface Device

SIP Systems Integration Plan

SIR System Integration Review - Level II review of engineering changes
to evaluate impacts to other systems and components, and how interfaces
may be affected.

SIRMA SSP Integrated Risk Management Application

SLF Shuttle Landing Facility

SLP Standard Laboratory Procedures - Commonly accepted laboratory
procedures which meet the requirements of the cognizant industry or
science association(s).

SLS Secondary Landing Site

SLWT Super Lightweight Tank - A developmental ET whose purpose is to
achieve significant weight savings, thereby improving Shuttle payload
capacity.

SM/SP&S System Management/Special Processes

System Management/Special Processes and Sequences

SMRB Senior Materials Review Board - A MRB composed of top level
contractor and Government engineering/quality personnel that reviews DRs
outside of the history base.

SMS Shuttle Mission Simulator

SMS-FB Shuttle Mission Simulator -- Fixed Base

SMS-MB Shuttle Mission Simulator -- Moving Base

SMTF Shuttle Mission Training Facility

SODB Shuttle Operational Data Book

SODF Shuttle Operations Data File

SOW Statement of Work - A description of the effort the Contractor is to
perform under the contract, including the criteria for determining
whether the requirements are met. This SOW is a performance-based
Statement of Work wherein contract requirements are principally
expressed in terms of outputs and standards.

SPDMS Shuttle Processing Data Management System

SPF Software Production Facility

SPIP Space Station Program Implementation Plan

SPO Shuttle Propulsion Office

SPOC Space Program Operations Contract

SPON Shuttle Program Office NACC

SPR Significant Problem Report - A discrepancy that meets the reporting
requirements of NSTS-08126.

SRB Solid Rocket Booster - A major component of the Space Shuttle,
comprised of a RSRM, and including other critical assemblies such as the
nose cap, frustum, parachute system, forward skirt, aft skirt, and
separation motors.

SRF Software Reconfiguration Facility

SRG Software Requirements Group

SRM Solid Rocket Motor

SRP Space Station Safety Review Panel

SR&QA Safety, Reliability and Quality Assurance - The organizational
designation of those personnel responsible to verify compliance with
safety, reliability, and quality assurance standards for Shuttle
component design, production, and performance.

SRP Standard Repair Procedures

SRR Software Requirements Review

System Requirements Review

SRS Software Requirements Specifications

SRU Shop Replaceable Unit

SSC John C. Stennis Space Center

Shuttle System Contractor

SSCCD Space Station Configuration Control Drawing

SSCR Support Software Change Request

SSDR Support Software Discrepancy Reports

SSEIG Shuttle Systems Engineering and Integration Group

SSME Space Shuttle Main Engine - A major component of the Space Shuttle.

SSPM Software Standards and Procedures Manual

SSRMS Space Station Remote Manipulator System

SSMTF Space Station Mockup and Trainer Facility

SSPM Software Standards and Procedures Manual

SSP/O Space Shuttle Program/Office

SSRP System Safety Review Panel - A Level II panel which reviews Hazard
Report changes.

SSTF Space Station Training Facility

SSV Space Shuttle Vehicle

STA Shuttle Training Aircraft

STATS Shuttle Schedule Tracking and Technical Summary

STE Special Test Equipment - Either single or multi-purpose integrated
test units engineered, designed, fabricated, or modified to accomplish
special purpose testing in performing this contract. (See FAR
45.101(a).)

STR Software Test report

STS Shuttle Test Station

STS Shuttle Transportation System

SYSGEN System Generation

T&O Test and Operations

TA Technical Assistant

TACCS Time, Age, Cycle Control System

TAL Trans-Atlantic Landing

TCDT Terminal Countdown Demonstration Test

TCHR Time-Critical Ground Handling Requirements

TCSR Technical, Cost and Schedule Reviews

TDDP Trajectory Design Data Package

TDMS \[NASA\] Technical Document Management System

TCTI Time Compliance Technical Instruction - Documentation used to make
approved engineering changes to hardware after receipt and acceptance by
the Government.

TIMS Training Information Management System

TIM Technical Interchange Meeting - Periodic meetings between NASA and
the contractor to discuss designated technical issues.

TIPS Tile Information Processing System

TMG Thermal Micro-Meteoroid Garment

TMR Technical Management Representative

TO Telemetry Occurrence

TOCSS Trajectory Operations Computer Software Support

TPS Test Preparation Sheets

Transition & Retirement -- Refers to the efforts of operations and
institutional capabilities associated with ending/completing the SSP
after flight operations have concluded. This includes activities
associated with production, logistics, workforce, equipment, supplier,
tooling, shutdown, transfer, and disposal.

-   Transition -- facilitating the smooth transfer of program
    capabilities to new programs.

-   Retirement -- facilitating the appropriate disposition of unneeded
    capabilities through defined agency processes.

TRR Test Readiness Review

TSE Transportation Support Equipment - Non-flight hardware used in the
transport of the Shuttle and its components.

UA Unexplained Anomaly

UAT/ORR User Acceptance Test/Operations Readiness Review

UF Utilization Flight

UG User Guide

UI User Interface

UL Uplink

ULC Unpressurized Logistics Carrier

UPF Universal Patch Format

VAB Vehicle Assembly Building

VADAR (Loads) Verification Analysis Data Acceptability Review

VAR Verification Acceptance Review

VDF Vehicle Definition

VIP Vendor Inspection Plan - A list of all inspections required by the
Government and the contractor to be accomplished at subcontractor
locations, and how they will be accomplished.

VIP Very Important Persons

VITT Vehicle Integration Test Team

VMS Vertical Motion Simulator

VOC Vehicle Occurrence

WAD Work Authorization Document

WBS Work Breakdown Structure - A hierarchical diagram of the total
contract work to be performed. The diagram separates the work content
into elements depicting increasing levels of detail. It is often
combined with an Organizational Breakdown Structure (OBS) to form a
matrix of work elements by responsible organization(s).

WETF Weightless Environment Training Facility

WSSH White Sands Space Harbor

WSTF White Sands Test Facility

ATTACHMENT J-3

RESERVED

ATTACHMENT J-4

RESERVED

ATTACHMENT J-5

DATA REQUIREMENTS LIST

# TABLE OF CONTENTS

[TABLE OF CONTENTS 26](#table-of-contents)

[1.0 INTRODUCTION 26](#introduction)

[1.1 Scope: 26](#scope)

[1.2 DPD Description: 26](#dpd-description)

[1.3 Data Types for Contractual Efforts:
26](#data-types-for-contractual-efforts)

[2.0 STATEMENT OF GENERAL REQUIREMENTS
26](#statement-of-general-requirements)

[2.1 Applicable Documents: 26](#applicable-documents)

[2.2 Subcontractor Data Requirements:
26](#subcontractor-data-requirements)

[2.3 Printing: 26](#printing)

[2.4 Microfilm: 26](#microfilm)

[2.5 Distribution/Delivery: 26](#distributiondelivery)

[2.6 Contractor's Internal Documents:
26](#contractors-internal-documents)

[2.7 Reserved 26](#reserved-61)

[2.8 Reference to Other Documents in Data Submittals:
26](#reference-to-other-documents-in-data-submittals)

[2.9 Maintenance of Type 1 Document Submittals:
26](#maintenance-of-type-1-document-submittals)

[2.10 "As Required" Annotations: 26](#as-required-annotations)

[3.0 DPD MAINTENANCE PROCEDURES 26](#dpd-maintenance-procedures)

[3.1 NASA-Initiated Change: 26](#nasa-initiated-change)

[3.2 Contractor-Initiated Change: 26](#contractor-initiated-change)

[3.3 DPD Change Procedures: 26](#dpd-change-procedures)

[3.4 DPD Reissues: 26](#dpd-reissues)

[DATA REQUIREMENTS LIST (DRL) 26](#data-requirements-list-drl)

# 1.0 INTRODUCTION

## 1.1 Scope:

> Subject to the Rights in Data clause, this Data Procurement Document
> (DPD) sets forth the data requirements in each Data Requirements
> Description (DRD) and shall govern that data required by the DPD for
> the contract. The contractor shall furnish data defined by the DRD\'s
> listed on the Data Requirements List (DRL) by category of data. Such
> data shall be prepared, maintained, and delivered to NASA in
> accordance with the requirements set forth within this DPD. In cases
> where data requirements are covered by a Federal Acquisition
> Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause,
> the regulation will take precedence over the DPD, per FAR 52.215-8.
> NASA-Owned/Contractor-Held records shall be managed by the Contractor
> in accordance with Title 36 of the code of Federal Regulations,
> Chapter XII B, Records Management, and NPD 1440.6, NASA Records
> Management. The records shall be organized in accordance with the
> instructions in NPR 1441.1D, NASA Records Retention Schedules, as
> applicable. The contractor shall disposition records and non-records
> in accordance with NPR 1441.1D, NASA Records Retention Schedules,
> which has been approved by NASA and the National Archives and Records
> Administration (NARA). All questions on records management issues
> shall be directed through the Contracting Officer to the JSC Records
> Management Officer.

## 1.2 DPD Description:

> This DPD consists of a Table of Contents, an Introduction, a Statement
> of General Requirements, DPD maintenance procedures, a DRL, and the
> DRD\'s.
>
> **1.2.1 General Requirements:** The general requirements specified in
> paragraph 2.0 of this DPD prescribe those requirements applicable to
> the preparation, maintenance, and delivery of data that are better
> defined in aggregate than in the individual DRD\'s.
>
> **1.2.2 Data Requirements List (DRL):** Applicable throughout the
> performance of the contract, the DRL provides a listing by data
> category of the data requirements of the DPD.
>
> **1.2.3 Data Requirements Descriptions (DRD\'s):** Each data
> requirement listed on the DRL is given complete definition by a DRD.
> The DRD prescribes content, format, maintenance instructions, and
> submittal requirements.

## 1.3 Data Types for Contractual Efforts:

> The types of data and their contractually applicable requirements for
> approval and delivery are as follows:
>
> TYPE DESCRIPTION
>
> 1 All issues and interim changes to those issues require written
> approval from the requiring organization before formal release for use
> or implementation.
>
> 2 NASA reserves a time-limited right to disapprove in writing any
> issues and interim changes to those issues. Data shall be submitted to
> the procuring activity for review not less than 45 calendar days or as
> otherwise agreed to between the contractor and the NASA user
> organization prior to its release for use or implementation. The
> contractor shall clearly identify the release target date in the
> "submitted for review" transmittal. If the contractor has not been
> notified of any disapproval prior to the release target date, the data
> shall be considered approved. To be an acceptable delivery,
> disapproved data shall be revised to remove causes for the disapproval
> before its release.
>
> 3 These data shall be delivered by the contractor as required by the
> contract and do not require NASA approval. However, to be a
> satisfactory delivery, the data must satisfy all applicable
> contractual requirements.
>
> 4 These data are produced or used during performance of the contract
> and are retained by the contractor. They shall be delivered when NASA
> requests it according to instructions in the request. The contractor
> shall maintain a list of these data and shall furnish copies of the
> list to NASA when requested to do so.
>
> 5 These data are incidental to contract performance and are retained
> by the contractor in those cases where contracting parties have agreed
> that delivery is not required. However, the Contracting Officer or the
> Contracting Officer's Representative shall have access to and can
> inspect this data at its location in the contractor's or
> subcontractor's facilities.

# 2.0 STATEMENT OF GENERAL REQUIREMENTS

## 2.1 Applicable Documents:

> Documents included as applicable documents in this DPD are the issue
> specified in the Statement of Work, and form a part of the DPD to the
> extent specified herein. References to documents other than applicable
> documents in the data requirements of this DPD may sometimes be
> utilized. These do not constitute a contractual obligation on the
> contractor. They are to be used only as a possible example or to
> provide related information to assist the contractor in developing a
> response to that particular data requirement.

## 2.2 Subcontractor Data Requirements:

> **2.2.1** The contractor shall specify to subcontractors and vendors,
> if any, the availability source of all data required for the
> satisfactory accomplishment of their contracts. The contractor shall
> validate these requirements for documents when appropriate. The
> contractor is encouraged to refer subcontractors to the JSC Scientific
> and Technical Information Center for their document requirements.
>
> **2.2.2** Reference to subcontractor data in the contractor's
> responses is permissible, providing the references are adequate and
> include such identification elements as title, number, revision, etc.,
> and a copy of the referenced data is supplied with the response
> document at time of delivery to NASA.

## 2.3 Printing:

> All reproduction and binding of documentation shall be in accordance
> with NPD 1490.1F, NASA Printing, Duplicating, Copying, Forms, and Mail
> Management, and NFS clause 1852.208-81, and as otherwise approved in
> writing in advance by the Contracting Officer.

## 2.4 Microfilm:

> When microfilm of drawings, specifications, and associated lists are
> required, it shall be 35 mm silver halide negative, first generation
> (Type 1, Class 1) in accordance with 36 CFR Part 1230, Micrographic
> Records Management, and mutual written agreement between the
> Contractor and the Contracting Officer. Input Form DD Form 1562, Dual
> Purpose Engineering Document Card, shall be used for microfilm
> purposes. The microfilm shall be submitted in the form of roll
> microfilm or master microfilm aperture cards. If microfilm rolls are
> used, they shall not exceed 100 feet in length.

## 2.5 Distribution/Delivery:

> **2.5.1** Distribution requirements of required documentation shall be
> in quantities determined by and to the addresses noted on a separate
> distribution list to be furnished by the Contracting Officer.
>
> **2.5.2 When A Reproducible Is Required:** Microfilm or an unbound
> copy shall be provided. The microfilm shall conform to paragraph 2.4.
> The unbound copy shall be of good black and white quality suitable for
> reproduction by microfilm or photocopy (or equivalent process).
>
> **2.5.3 Data Format Using Automated Data Processes:** The contractor
> is encouraged to use automated data formats unless specified otherwise
> in this contract. Choice of automated versus manual formats for
> specific documentation submittals, as required by this DPD, shall be
> made giving full consideration to cost of preparation of the item,
> criticality of schedule performance, and usability of the
> documentation involved. Regardless of which method (automated or
> manual) is selected, the data submittal shall conform to the content
> requirements specified in the applicable data requirements
> description. In instances where minor changes to these content
> requirements will result in significant cost reductions without
> affecting the usability of the documentation involved, the Contracting
> Officer shall be so advised with appropriate recommendation as to
> changes.
>
> **2.5.4 When Electronic Data Submission is Required:**
>
> 2.5.4.1 DRD's will specify if part or all of the data is to be
> provided in an electronic format. A table will be included by the
> contractor in DRD 1.1.4.1-a that identifies anticipated electronic
> delivery formats for the electronic deliverables.
>
> 2.5.4.2 The contractor shall obtain approval of the Contracting
> Officer for deviation from the above standards, or for approval of
> other file formats not specifically listed.
>
> 2.5.4.3 Data transfer (delivery) mechanisms. The contractor shall
> utilize one or more of the following electronic transfer mechanisms to
> deliver data to the Government over the network:
>
> a\. Transmission of data to a Contracting Officer designated FTP
> server utilizing TCP/IP protocols.
>
> b\. Transmission of data to a Contracting Officer designated NT server
> utilizing TCP/IP protocols.
>
> c\. Transmission of data to a Contracting Officer designated Novell
> server utilizing IPX protocols.
>
> d\. Transmission of data to a Contracting Officer designee via
> electronic mail, with the inclusion of file attachments as necessary.
>
> 2.5.4.4 Delivery Protocol. The contractor shall transmit an electronic
> mail message to the Contracting Officer designee clearly identifying
> any deliverables transferred to the Government and the network
> location of the data transferred, if delivery methods 2.5.4.3 a-c are
> used. All files transferred shall be clearly identified as to the
> deliverable data item and sub-part thereof that they represent. For
> deliverables consisting of multiple data files, the order in which
> files are to be perused/printed shall be clearly identified.
>
> 2.5.4.5 Physical Media. The contractor shall utilize DOS or Macintosh
> formatted floppy disks, or CD-ROM (any format) when delivering on
> physical media.

## 2.6 Contractor's Internal Documents:

> The contractor's internal documents shall be used to meet the data
> requirements of this DPD unless a specific format is required by the
> applicable DRD.

## 2.7 Reserved

## 2.8 Reference to Other Documents in Data Submittals:

> All referenced documents shall be made readily available to the
> cognizant NASA organization upon request. The contractor should make
> sure that the references are available to NASA in a manner which does
> not incur delays in the use of the response document.

## 2.9 Maintenance of Type 1 Document Submittals:

> **2.9.1** Revisions of Type 1 documentation may be accomplished by
> individual page revision or by a complete reissue of the document in
> accordance with the required Document Development Plan with the
> exception of drawings (which shall be revised in accordance with
> contract configuration management requirements).
>
> **2.9.2** Individual page revisions shall be made as deemed necessary
> by the contractor or as directed by the Contracting Officer.
>
> **2.9.3** A Type 1 document shall be completely reissued when, in the
> opinion of the contractor and/or NASA, the document has been revised
> to the extent that it is unusable in its present state, or when
> directed by the Contracting Officer. When complete reissues are made,
> the entire contents of the document shall be brought up to date and
> shall incorporate revised pages. All revisions shall be recorded. A
> revision log shall identify complete reissues except for periodic
> reports and documents which are complete within themselves as final.
>
> **2.9.4** Changes of a minor nature to correct obvious typing errors,
> misspelled words, etc., shall only be made when a technical change is
> made, unless the accuracy of the document is affected.
>
> **2.9.5** All revised pages shall be handled in accordance with
> procedures defined in the Document Development Plan. Document change
> histories shall be recorded on JSC form 28 and included in all
> document deliverables.
>
> **2.9.6** Contractor Type 1 documents shall not be submitted
> containing pen and ink markups which correct, add to, or change the
> text, unless schedule problems exist and approval is obtained in
> writing from the Contracting Officer. Such markups, however, shall not
> exceed 20 percent of the page content and shall be acceptable provided
> that the reproduced copies are legible. In addition, hand-drawn
> schematics, block diagrams, data curves, and similar charts may be
> used in original reports in lieu of formally prepared art work, as
> long as legibility of copies is not impaired. Acceptability will be
> determined by the Contracting Officer.

## 2.10 "As Required" Annotations:

> Various DRD's include the annotation "as required" in items 9, Initial
> Submission, 10, Submission Frequency; or 13.5, Maintenance. Unless
> specified otherwise, "as required" means as deemed necessary by the
> contractor, the Government, or applicable documentation.

# 3.0 DPD MAINTENANCE PROCEDURES

## 3.1 NASA-Initiated Change:

> New and/or revised data requirements will be incorporated by contract
> modification to which the new or revised portion of the DPD will be
> appended. The contractor shall notify the Contracting Officer in the
> event a deliverable data requirement is imposed and is not covered by
> a DRD, or when a DRD is changed by a contract modification and for
> which no revision to DPD is appended. In such cases, the contractor
> shall submit the requested changes to NASA for approval. See paragraph
> 3.3.1 for change procedures.

## 3.2 Contractor-Initiated Change:

> Contractor-proposed data requirements, or proposed changes to existing
> requirements shall be submitted to NASA for approval.

## 3.3 DPD Change Procedures:

> Changes to a contractual issue of this DPD will be identified in the
> DRL when incorporated by Supplemental Agreement.

## 3.4 DPD Reissues:

> **3.4.1** When conditions warrant, the DPD will be reissued by NASA
> and will supersede the existing DPD in its entirety. Reissues will be
> implemented by contractual direction.
>
> **3.4.2** All revision symbols (vertical lines and contractual
> direction control numbers) and revision dates will be removed from all
> pages. The issue symbol, which will commence with "A" and progress
> through "Z," will be entered in the DRD identification block of each
> DRD page of the DPD. The date of the contractual direction will be
> entered on the cover page of the DPD. This issue symbol will also be
> entered under the "Status" column on the Page Revision Log adjacent to
> each page and DRD entry. Document Change Logs will otherwise be
> changed in the same manner as for DPD revisions.

# DATA REQUIREMENTS LIST (DRL)

  ------------------------------------------------------------------------------------------
  DRL\   DRD           DATA\     DRD TITLE                          SOW           REVISED\
  \#                   TYPE                                                       BY
  ------ ------------- --------- ---------------------------------- ------------- ----------
  1      1.1.1.1-a     1         Management Plan                    1.1.1.1       

  2      1.1.1.1-b     1         Work Breakdown Structure (WBS) and 1.1.1.1,\     
                                 Dictionary                         1.1.2.1,\     
                                                                    & 1.1.2.2     

  3      1.1.1.1-e     2         Company Emergency Management       1.1.1.1       
                                 Reponse Plan                                     

  4      1.1.1.1-f     1         Space Flight Operations Product    1.1.1.1       
                                 Development Plans                                

  5      1.1.1.1-g     3         Organizational Breakdown Structure 1.1.1.1,\     
                                                                    1.1.2.1,\     
                                                                    & 1.1.2.2     

  6      1.1.1.1-h     2         Property Management Plan           1.1.1.1\      
                                                                    & 1.1.6.2     

  7      1.1.1.1-i     3         New Technology Reporting           1.1.1.1       

  8      1.1.1.1-j     1         Shuttle Ground Processing          1.1, 1.3,\    
                                 Plans/Instructions                 1.4, 1.5,\    
                                                                    & 1.7         

  9      1.1.1.1-k     3         Notification of Significant        1.1.1.1       
                                 Program Management Decisions                     

  10     1.1.1.1-l     3         KSC Emergency Preparedness Plan    1.1.1.1       

  11     1.1.1.2.3     3         Flight Readiness Review            1.1.1.2.2\    
                                                                    & 1.1.1.2.3   

  12     1.1.1.4-a     2         Space Shuttle Program Risk         1.1.1.4       
                                 Management Plan                                  

  13     1.1.1.4-b     3         Risk Assessment Documentation      1.1.1.4\      
                                                                    & 1.3         

  14     1.1.2.1-a     1,3       Financial Management Reports       1.1.1.1\      
                                                                    & 1.1.2.1     

  15     1.1.2.1-b     1,3       Resources Management Reporting     1.1.1.1\      
                                 System                             & 1.1.2.1     

  16     1.1.2.1-d     3         Energy Utilization and Consumption 1.1.2.1       
                                 Report                                           

  17     1.1.2.1-e     4         On-site and Off-site Headcount     1.1.2.1       
                                 Report                                           

  18     1.1.2.1-f     3         Geographical Economic Impact       1.1.2.1       
                                 Report                                           

  19     1.1.2.1-g     3         Notification of Potential Labor                  
                                 Dispute and Contingency Strike                   
                                 Plan                                             

  20     1.1.2.1-h     3         Wage/Salary and Fringe Benefit     1.1.2.1       
                                 Data                                             

  21     1.1.2.1-i     3         Advance Notification of Workforce  1.1.2.1       
                                 Reductions                                       

  22     1.1.2.1-k     1         Annual Property NASA Form (NF)     1.1.2.1       
                                 1018 Report                                      

  23     1.1.2.1-l     2         Contractor-Held Property Financial 1.1.2.1       
                                 Reporting                                        

  24     1.1.2.2-a     3         Performance Measurement System     1.1.1.1,\     
                                 Reports (Development and           1.1.2.1,\     
                                 Production)                        & 1.1.2.2     

  25     1.1.2.2-b     3         Performance Measurement System     1.1.1.1,\     
                                 (PMS) Reports (Operations)         1.1.2.1,\     
                                                                    & 1.1.2.2     

  26     1.1.3.2-a     3         Small Business Subcontracting                    
                                 Report                                           

  27     1.1.3.2-b     3         Small Business Subcontracting Plan               

  28                             RESERVED                                         

  29     1.1.4.1-b     1,3       Information Technology (I/T) Plan  1.1.4\        
                                 & Reports                          & 1.6.4       

  30     1.1.4.1-c     4         Data Accession List                1.1.4.1       

  31     1.1.4.1-d     4         Procurement Data Package                         

  32     1.1.4.1-e     2         Data Management Plan               1.1.4.1       

  33     1.1.4.1-f     2         Records Management Plan            1.1.4.1       

  33A    1.1.4.1-g     2         Enterprise Architecture Reviews    1.1.4.1       

  34     1.1.5.1       2         Configuration Management Plan      1.1.5.1       

  35     1.1.5.2-a     2         Verification Management Plan       1.1.5.2       

  36     1.1.5.2-b     5         Mission Configuration Product Plan 1.1.5.2       
                                 (MCPP)                                           

  37     1.1.6.1-a     1         Facility Management Plan           1.1.6.1\      
                                                                    & 1.5.5.2     

  38     1.1.6.1-b     3         Facility Project Reporting         1.1.6.1       
                                 Requirements                                     

  39     1.1.6.2                 Government Property Inventory,     1.1.6.2       
                                 Record Verification, and                         
                                 Utilization Plan                                 

  40     1.1.6.3-a     1         Security Management Plan           1.1.6.3\      
                                                                    & 1.1.4.1     

  41     1.1.6.3-b     1         Technology Protection Control Plan 1.1.6.3       

  42     1.1.6.3-d     3         Fire Protection                    1.1.6.3\      
                                                                    & 1.1.4.1     

  43     1.1.7-a       1,2,3     Manifest Products                  1.1.7.2       

  44     1.1.7-b       3         Flight Operations Schedules        1.1.7         

  45     1.1.7-c       2         KSC Schedule and Status Summary    1.1.7         
                                 (Gray Book)                                      

  46     1.1.7-d       1         Flight-Specific TV Plan            1.1.7.1       

  47     1.1.7-f       1         Flight Integration Products        1.1.7.1       

  48     1.1.7-g       1,2,3,4   Ground Operations Schedules        1.1.7         

  49     1.1.8         1         Technical Information              1.1.8         
                                 Systems/Software Design Documents                

  50     1.2.1.1-a     1         Flight Derived Dispersions         1.2.1.1       
                                 Database Update                                  

  51     1.2.1.1-b     3         Quick look and Detailed            1.2.1.1       
                                 Post-flight Reconstruction Report                

  52     1.2.1.3-a     3         Generic and Mission-Specific       1.2.1.3.2     
                                 Shuttle Critical Math Model and                  
                                 Analysis Tools (CMMAT)                           

  53     1.2.1.3-b     3         Cargo Thermal and Loads            1.2.1.3.3\    
                                 Verification Analyses              & 1.2.1.3.4   

  54     1.2.1.3-c     3         Safety Evaluation of Orbiter       1.2.1.3.7     
                                 Services for Payload Use                         

  55     1.2.1.3-d     3         Payload Environmental Impact       1.2.1.3.7     
                                 Statement                                        

  56     1.2.1.3-e     3         Payload/Cargo Electromagnetic      1.2.1.3.6     
                                 Effects and Radio Frequency                      
                                 Compatability                                    

  57     1.2.1.5-a     3         Space Shuttle Program (SSP)        11.5.2\       
                                 Drawing Release Change Request     & 1.4.1       
                                 (CR)                                             

  58     1.2.1.5-b     3         Engineering Drawings and           1.2.1.3.5\    
                                 Voltage/Power Analysis Letter      & 1.2.1.5     

  59     1.2.1.6-a     1,3       DOLILU Operations Support System   1.2.1.6       
                                 (DOSS) Flight-Specific Products                  

  60     1.2.1.6-b     3         DOLILU Operations Support System   1.2.1.6       
                                 (DOSS) Non flight-Specific                       
                                 Products                                         

  61     1.2.1.7-b     1         Critical Math Models Database      1.2.1.7       
                                 Maintenance                                      

  62     1.2.1.7-d     1         Ascent Debris/Transport Database   1.2.1.7       
                                 Maintenance                                      

  63     1.2.2.1-a     3         Shuttle Weight, Performance, and   1.2.2.1       
                                 Integrated Mass Properties                       
                                 Database and Status Reports                      

  64     1.2.2.2       3         Trajectory Design Data Package     1.2.2.2       
                                 (TDDP) and Change Notices                        

  65     1.2.2.3-a     3         Adjusted Reusable Solid Rocket     1.2.2.3       
                                 Motor (RSRM) Pre-flight Computer                 
                                 Files                                            

  66     1.2.2.3-b     1         Main Propulsion System (MPS)       1.2.2.3       
                                 Inventory/Budget Update and                      
                                 Documentation                                    

  67     1.2.2.4-a     1, 3      Annex 1 - Payload Data Package     1.2.2.4       

  68     1.2.2.5-a     1         Interface Revision Notice (IRN) to 1.2.2.5       
                                 Systems Interface Control                        
                                 Documents (ICDs)                                 

  69     1.2.2.5-b     1         Preliminary Interface Revision     1.2.2.5.2     
                                 Notice (PIRN) and Interface                      
                                 Revision Notice (IRN) to Program                 
                                 Requirements Interface Control                   
                                 Document (ICD) (CORE) and                        
                                 Interface Definition Documents                   
                                 (IDDs)                                           

  70     1.2.2.6       1, 3      Payload Unique Interface Control   1.2.2.6       
                                 Documents (ICD\'s and Installation               
                                 Requirements Documents (IRD\'s)                  

  71     1.2.2.7       1         Payload Operations and Maintenance 1.2.2.7.1     
                                 Requirements and Specifications                  
                                 (OMRS) Test Requirement                          

  72     1.2.2.7-a     3         Middeck Payloads Time-Critical     1.2.2.7.2     
                                 Ground Handling Requirements                     
                                 (TGHR) Table                                     

  73     1.2.2.10-a    1         Technical Revision to SL-E-0001    1.2.2.10      
                                 and SL-E-0002                                    

  74     1.3-a         2         Mission Assurance Plan             1.3           

  75     1.3-b         3         Safety and Health Plan             1.3           

  76A    1.3.1.1-a     3         Integrated Hazards Analysis        1.3.1.1       

  76B    1.3.1.1-b     3         Integrated Hazards Reports         1.3.1.1       

  76C    1.3.1.1-c     3         Integrated Hazards Report          1.3.1.1       
                                 Verification Tracking Log (VTL)                  

  76     1.3.1.2-b     3         Safety Summary Report (SSR)        1.3.1.2       

  77     1.3.1.2-c     3         Pressure Vessel/System             1.3.1.2       
                                 Recertification                                  

  78     1.3.1.2-d     3         Annual Safety Program Evaluation   1.3.1.2       

  79     1.3.3         2         Quality Plan                       1.3, 1.3.3,\  
                                                                    1.3.3.1,\     
                                                                    & 1.3.3.2     

  80     1.3.3.1       4         Acceptance Data Package (ADP)      1.3.3.1,\     
                                                                    1.2.1.4.2,\   
                                                                    1.4.1.5.2,\   
                                                                    & 1.7.1       

  81     1.4-a         1         KSC Work Authorization Documents   1.4 & 1.5     
                                 (Category 1) Development and                     
                                 Maintenance Plan                                 

  82     1.4-c         3         Logistics Performance Report       1.4,\         
                                                                    1.4.1.2,\     
                                                                    1.4.7.2,\     
                                                                    1.5.5.4,\     
                                                                    & 1.6         

  83     1.4-d         3         Government Furnished Material      1.4           
                                 (GFM) and Propellants Requirements               
                                 Forecast                                         

  84     1.4-e         2         Loss of Capabilities and           1.4           
                                 Corrective Action Report                         

  85     1.4.1.1       1         Corrective Action Record           1.4.1.1       

  86     1.4.1.1.1-b   2         Change Requests (CR\'s) and        1.4.1.5.2     
                                 Reviews                                          

  87     1.4.1.1.1-c   1         Specification Change Notice        1.4.1.5.2     

  88     1.4.1.1.2-a   1         Special Action Requirement (SAR)   1.4.1.3       

  89     1.4.1.1.3-a   1         Operational Maintenance            1.4.1.1       
                                 Requirements and Specifications                  
                                 Document Changes                                 

  90     1.4.1.5.1-a   1,2       Requirement Definition Documents   1.2.1.4.2,\   
                                 for Modifications, Mission Kits,   1.4.1.5.2,\   
                                 and GSE                            & 1.7.1       

  91     1.4.1.5.1-b   1         Certification Requirement (CR)     1.2.1.4.2,\   
                                                                    1.4.1.5.2,\   
                                                                    & 1.7.1       

  92     1.4.1.5.1-c   1         Certification Approval Request     1.2.1.4.2,\   
                                 (CAR)/Qualification Site CAR       1.4.1.5.2,\   
                                                                    & 1.7.1       

  93     1.4.1.6.1-a   2         Inputs to JSC 08934, Shuttle       1.4.1.1       
                                 Operational Data Book (SODB)                     

  94     1.4.1.6.1-d   2         Non-Flight Constraint (NFC)        1.4.1.1       
                                 Disposition                                      

  95     1.4.1.6.1-e   3         Integrated Configuration           1.2.1.5       
                                 Engineering Data (ICED) Library                  

  96     1.4.1.6.1-g   2         Instrumentation Program and        1.4.1.6.1     
                                 Components Lists (IPCL\'s)                       

  97     1.4.2.1-a     2         SRB and Range Safety Command       1.4.2.1       
                                 Destruct System Failure Modes and                
                                 Effects Analysis (FMEA)                          

  98     1.4.2.1-b     2         SRB and Range Safety Command       1.4.2.1       
                                 Destruct System Critical Items                   
                                 List (CIL)                                       

  99     1.4.2.1-d     3         SRB Mass Properties Status Report  1.4.2.1       

  100    1.4.2.1-e     3         SRB Final Flight Evaluation Report 1.4.2.1       

  101    1.4.2.1-f     1         Solid Rocket Booster (SRB) Project 1.4.2.1       
                                 Management Plan                                  

  102    1.4.2.1-g     3         SRB and Range Safety Command       1.4.2.1       
                                 Destruct System Flight Hazard                    
                                 Analysis                                         

  103    1.4.3-a       3         Software Quality Report            1.4.3         

  104    1.4.3.1-a     4         Backup Flight System (BFS)         1.4.3.1       
                                 Software User\'s Manuals for                     
                                 Software Support Tools                           

  105    1.4.3.1-b     3         Backup Flight System (BFS)         1.4.3.1       
                                 Software Requirements and                        
                                 Specifications Documents for                     
                                 Software Support Tools                           

  106    1.4.3.1-c     4         Backup Flight System (BFS)         1.4.3.1       
                                 Software Design Document (SDD) for               
                                 Software Support Tools                           

  107    1.4.3.1-g     3         Backup Flight System (BFS)         1.4.3.1       
                                 Software Authorization Sheet (SAS)               
                                 and Patches                                      

  108    1.4.3.1-k     3         Measurement Stimulus               1.4.3.1       
                                 Identification (MSID) Assignment                 
                                 and Integration                                  
                                 (Downlist/Downlink)                              

  109    1.4.3.1-n     3         Telemetry Format                   1.4.3.1       
                                 Load/Decommutation Format                        
                                 Load/Fetch Pointer Load                          
                                 (TFL/DFL/FPL) Universal Patch                    
                                 Format (UPF) Patches                             

  110    1.4.3.1-q     3         Develop/Evaluate MAST II/STAR      1.4.3.1       
                                 Reconfiguration Data Change                      
                                 Requests (DCRs)                                  

  111    1.4.3.2-a     1         Integrated Hardware and Software   1.4.3.2       
                                 Test Implementation Plan                         

  112    1.4.3.2-b     1         Integrated Avionics Verification   1.4.3.2       
                                 Test Requirements Matrix                         

  113    1.4.3.2-c     1         Shuttle Avionics Integration       1.4.3.2       
                                 Laboratory (SAIL) Test Data                      
                                 Requirements Document                            

  114    1.4.3.2-d     3         Integrated Avionics Test           1.4.3.2       
                                 Requirements Document                            

  115    1.4.3.2-f     3         Avionics Anomaly Reporting and     1.4.3.2       
                                 Resolution                                       

  116    1.4.3.2-g     3         Integrated Avionics Verification   1.4.3.2       
                                 Test and Analysis Report                         

  117    1.4.3.2-h     3         Integrated Avionics Verification   1.4.3.2       
                                 Readiness                                        

  118    1.4.3.3-c     3         Prioritization Recommendation for  1.4.3.3       
                                 New Operational Increment (OI)                   
                                 Build                                            

  119    1.4.3.3-e     3         Initialization Load (I-Load)       1.4.3.3       
                                 Verification Report                              

  120    1.4.3.3-f     4         Level 6/7/8 Flight Software Test   1.4.3.3       
                                 Plan Recommendation                              

  121    1.4.3.3-g     3         Initialization Load (I-Load)       1.4.3.3       
                                 Selection and Comparison Report                  

  122    1.4.3.3-o     3         Backup Flight System (BFS) Program 1.4.3.3       
                                 Requirements Documents (PRD\'s)                  

  123    1.4.3.3-p     3         Primary Avionics Software System   1.4.3.3       
                                 (PASS)/Backup Flight System (BFS)                
                                 Interface Control Documents                      
                                 (ICD\'s)                                         

  124    1.4.3.3-q     3         Functional Subsystem Software      1.4.3.3       
                                 Requirements (FSSRs) Documents                   

  125    1.4.3.3-s     3         Initialization Load (I-Load)       1.4.3.3       
                                 Selection Criteria Databook                      

  126    1.4.3.3-t     4         Parameter Database                 1.4.3.3       

  127    1.4.3.3-u     3         Flight Software Logic              1.4.3.3       
                                 Documentation                                    

  128    1.4.3.3-w     3         Space Shuttle Computer Program     1.4.3.3       
                                 Development Specifications (Six                  
                                 Volumes)                                         

  129    1.4.3.3-x     3         Engineering DCE Support for SASCB  1.4.3.3       
                                 Change Reviews                                   

  130    1.4.3.3-y     3         Develop/Evaluate Flight Software   1.4.3.3       
                                 (FSW) Change Documents                           

  131    1.4.3.3-ab    4         Mapping of Principal Functions and 1.4.3.3       
                                 I-Load Categories to Baselined                   
                                 Hazard Reports                                   

  132    1.4.3.3-ac    3         Integrated Data Processing System  1.4.3.3       
                                 (DPS) Principles of Operation                    
                                 (POO) Document Updates                           

  133    1.4.3.4-d     3         Backup Flight System (BFS)         1.4.3.4       
                                 Reconfiguration Deliverables                     

  134    1.4.3.5-a     3         Backup Flight System (BFS)         1.4.3.5       
                                 Software Configuration Inspection                
                                 Report/Briefing                                  

  135    1.4.3.5-b     3         Backup Flight System (BFS)         1.4.3.5       
                                 Software Standards and Procedures                
                                 Manual (SSPM)                                    

  136    1.4.3.5-c     3         Backup Flight System (BFS)         1.4.3.5       
                                 Software Change Request (SCR) Risk               
                                 Assessment Analysis/Report                       

  137    1.4.3.5-d     3         Backup System Loader (BSL)         1.4.3.5       
                                 Computer Program Description                     
                                 Document                                         

  138    1.4.3.5-e     3         General Purpose Computer Initial   1.4.3.5       
                                 Program Load (GPCIPL) Program                    
                                 Requirements Document                            

  139    1.4.3.5-g     3         Backup Flight System (BFS)         1.4.3.5       
                                 Operational Increment (OI)                       
                                 Deliverables                                     

  140    1.4.3.5-h     3         Backup Flight System (BFS)         1.4.3.5       
                                 High-Order Assembly                              
                                 Language/Shuttle (HAL/S) Compiler                
                                 Audit Reports                                    

  141    1.4.3.5-i     3         Backup Flight System (BFS)         1.4.3.5       
                                 Discrepancy Report (DR) Analysis                 

  142    1.4.3.5-j     3         Backup System Loader (BSL) Program 1.4.3.5       
                                 Requirements Document                            

  143    1.4.3.5-k     3         General Purpose Computer Initial   1.4.3.5       
                                 Program Load (GPCIPL) User\'s                    
                                 Guide                                            

  144    1.4.3.5-l     3         General Purpose Computer Initial   1.4.3.5       
                                 Program Load (GPCIPL) Computer                   
                                 Program Description Document                     

  145    1.4.3.5-m     3         Backup Flight System (BFS) Program 1.4.3.5       
                                 Description Documents (PDD\'s)                   

  146    1.4.3.5-n     3         Backup Flight System (BFS) Coding  1.4.3.5       
                                 Standards Document                               

  147    1.4.3.5-o     3         Backup Flight System (BFS) User\'s 1.4.3.5       
                                 Guide                                            

  148    1.4.3.5-p     3         Backup Flight System (BFS) Test    1.4.3.5       
                                 Coordination Team (TCT) Test                     
                                 Specifications and Performance                   
                                 Test Review (PTR) (Level 7)                      

  149    1.4.3.5-q     3         Backup Flight System (BFS)         1.4.3.5       
                                 Functional Test Report (Level 6)                 

  150    1.4.3.5-r     3         Backup Flight System (BFS)         1.4.3.5       
                                 Performance Test Reports (Level 7)               

  151    1.4.3.5-s     3         Backup Flight System (BFS)         1.4.3.5       
                                 Software First Article                           
                                 Configuration Inspection (FACI)                  
                                 Report/Briefing                                  

  152    1.4.3.5-u     3         Backup Flight System (BFS)         1.4.3.5       
                                 Development/Verification Report                  

  153    1.4.3.5-v     3         Backup Flight System (BFS) Mass    1.4.3.5       
                                 Memory Universal Patch Format                    
                                 (UPF) Patch                                      

  154    1.4.3.7-a     3         Progress Reports                   1.4.3.7 -\    
                                                                    1.4.3.10,\    
                                                                    & 1.4.3.12    

  155    1.4.3.7-b     3         Software Management Plan           1.4.3.7 -\    
                                                                    1.4.3.10,\    
                                                                    & 1.4.3.12    

  156    1.4.3.7-c     4         Computer Resources Requirements    1.4.3.7       
                                 and Utilization                                  

  157    1.4.3.7-d     3         Software Development Plan          1.4.3.7,\     
                                                                    1.4.3.9,\     
                                                                    & 1.4.3.12    

  158    1.4.3.7-e     3         Software Configuration Management  1.4.3.7       
                                 Report (CMDB Report)                             

  159    1.4.3.7-f     3         Software Quality Assurance         1.4.3.7       
                                 Assessment Report                                

  160    1.4.3.7-h     3         Software Quality Assurance (SQA)   1.4.3.7       
                                 Plan                                             

  161    1.4.3.7-i     4         Software Quality Assurance         1.4.3.7       
                                 Audit/Inspection                                 

  162    1.4.3.7-j     3         Flight Software Process Support    1.4.3.7       
                                 Products & Services                              

  163    1.4.3.8-a     3         FSW Applications Tools             1.4.3.8       
                                 Requirements Documents and                       
                                 Interface Control Documents                      

  164    1.4.3.8-b     4         FSW Applications Tools User's      1.4.3.8       
                                 Guides                                           

  165    1.4.3.8-c     3         Flight Software Build and          1.4.3.8       
                                 Reconfiguration Support Tools -                  
                                 JSC 20183                                        

  166    1.4.3.8-d     3         HAL/S FC Compiler Test Plan        1.4.3.8       

  167    1.4.3.8-e     3         HAL/S FC Compiler Test Results     1.4.3.8       
                                 Report                                           

  168    1.4.3.8-f     3         Applications Tools SSDR Analyses   1.4.3.8       
                                 and Waivers                                      

  169    1.4.3.8-g     4         GPC Emulator Simulation Documents  1.4.3.8       

  170    1.4.3.8-h     3         Support Software Change Control    1.4.3.8       
                                 Board (SSCCB) Process Products                   

  171    1.4.3.8-i     3         SPON System Interface and                        
                                 Integration                                      

  172    1.4.3.9-a     3         Orbiter Avionics Software          1.4.3.9       
                                 Programming Standards Document                   

  173    1.4.3.9-b     3         FSW Maintenance Specification      1.4.3.9       
                                 Document                                         

  174    1.4.3.9-c     3         Detail Design Specification (DDS)  1.4.3.9       

  175    1.4.3.9-d     3         Software First Article             1.4.3.8,\     
                                 Configuration Inspection (FACI)    & 1.4.3.9     
                                 Report                                           

  176    1.4.3.9-e     3         Flight Software Capabilities       1.4.3.9       
                                 Verification Plan (Level 6)                      

  177    1.4.3.9-f     3         Flight Software Capabilities       1.4.3.9       
                                 Verification Procedures (Level 6)                

  178    1.4.3.9-g     3         Level 6 Test Cases - Capabilities  1.4.3.9       
                                 Verification Phase                               

  179    1.4.3.9-h     3         FSW Performance Verification Plan  1.4.3.9       
                                 (Level 7)                                        

  180    1.4.3.9-i     3         FSW Test Reports - Performance     1.4.3.9       
                                 Verification (Level 7)                           

  181    1.4.3.9-j     3         Software Configuration Inspection  1.4.3.8,\     
                                 (CI) Report                        & 1.4.3.9     

  182    1.4.3.9-k     3         FSW OI Deliverables                1.4.3.8,\     
                                                                    & 1.4.3.9     

  183    1.4.3.9-l     3         Flight Software Class 1                          
                                 Integration Plan (CIP) - JSC-22320               

  184    1.4.3.9-m     3         Payload Software Capabilities      1.4.3.9       
                                 Overview - JSC 17086                             

  185    1.4.3.9-n     3         Change Request Risk Assessments    1.4.3.9       

  186    1.4.3.9-o     3         Downlist Availability              1.4.3.9       
                                 Configuration                                    

  187    1.4.3.9-p     3         Space Shuttle Programs PASS        1.4.3.9       
                                 Parameter Data Tape Content                      

  188    1.4.3.10-a    3         MMU Reconfiguration Deliverables   1.4.3.10      

  189    1.4.3.10-b    3         Level 8 Products                   1.4.3.10      

  190    1.4.3.10-c    3         Monthly PASS Reconfiguration       1.4.3.10      
                                 Status Report                                    

  191    1.4.3.10-d    3         MMU Integration Plan (MIP) - JSC   1.4.3.10      
                                 08338                                            

  192    1.4.3.10-e    3         Integrated Baseline Control Board  1.4.3.10      
                                 (IBCB) Datapack                                  

  193    1.4.3.10-f    4         Level 8 Performance Test Plan      1.4.3.10      
                                 Document                                         

  194    1.4.3.11-a    3         DPS Reports, Monthly Progress      1.4.3.11      

  195    1.4.3.11-b    3         DPS Report, Engineering and        1.4.3.11      
                                 Technical Data                                   

  196    1.4.3.11-c    4         Simulator Interface Device (SID)   1.4.3.11      
                                 Interface Control Document (ICD)                 

  197    1.4.3.11-d    4         DPS Acceptance Data Packages       1.4.3.11      

  198    1.4.3.12-a    3         Flight Software Test and           1.4.3.12      
                                 Operations Plan - JSC-25392                      

  199    1.4.3.12-c    3         Mission Support Plan               1.4.3.12      

  200    1.4.3.12-d    3         Mission Operation Support Report   1.4.3.12      

  201    1.4.3.12-e    3         DR Analysis and Status Reports     1.4.3.12      

  202    1.4.3.12-f    3         Flight Software Program Notes and  1.4.3.12      
                                 Waivers Document - JSC 19320                     

  203    1.4.3.12-g    3         Program Notes and Waivers          1.4.3.12      

  204    1.4.3.12-h    3         PASS Flight Software User's Guide  1.4.3.12      

  205    1.4.3.12-i    3         Mass Memory Patch                  1.4.3.10,\    
                                                                    & 1.4.3.12    

  206    1.4.3.13-a    3         Software Development Plan (SDP)    1.4.3.13      
                                 for the Multifunction Electronic                 
                                 Display Subsystem (MEDS)                         

  207    1.4.3.13-d    3         MEDS Software Change Authorization 1.4.3.13      

  208    1.4.3.13-e    3         Hardware Dependent Software        1.4.3.13      
                                 Segment Specification (HDSSS) for                
                                 the Multifunction Electronic                     
                                 Display Subsystem (MEDS)                         

  209    1.4.3.13-f    3         General Purpose Computer           1.4.3.13      
                                 (GPC)/Integrated Display Processor               
                                 (IDP) Interface Control Document                 
                                 (ICD)                                            

  210    1.4.3.13-j    3         MEDS Verification Test Readiness   1.4.3.13      
                                 Review (TRR) Briefing                            

  211    1.4.3.13-k    3         Software Requirements              1.4.3.13      
                                 Specifications (SRS) for the                     
                                 Multifunction Electronic Display                 
                                 Subsystem (MEDS)                                 

  212    1.4.3.13-l    3         Interface Requirements/Design      1.4.3.13      
                                 Document (IRDD) for the                          
                                 Multifunction Display Unit                       
                                 Function (MDUF) of the                           
                                 Multifunction Electronic Display                 
                                 Subsystem (MEDS)                                 

  213    1.4.3.13-m    3         Interface Requirements             1.4.3.13      
                                 Specification (IRS) for the                      
                                 Analog-to-Digital Converter (ADC)                
                                 of the Multifunction Electronics                 
                                 Display Subsystem (MEDS)                         

  214    1.4.3.13-n    3         Interface Design Document (IDD)    1.4.3.13      
                                 for the Analog-to-Digital                        
                                 Converter (ADC) of the                           
                                 Multifunction Electronic Display                 
                                 Subsystem (MEDS)                                 

  215    1.4.3.13-o    3         Software Design Documents (SDD)    1.4.3.13      
                                 for the Multifunction Electronic                 
                                 Display Subsystem (MEDS)                         

  216    1.4.3.13-p    4         Software Programmers Manuals for   1.4.3.13      
                                 the Multifunction Electronic                     
                                 Display Subsystem (MEDS)                         

  217    1.4.3.13-q    4         Software Development Folders       1.4.3.13      
                                 (SDFs) for the Multifunction                     
                                 Electronic Display Subsystem                     
                                 (MEDS)                                           

  218    1.4.3.13-r    1         MEDS Release Authorization         1.4.3.13      
                                 Signature Sheet (RASS)                           

  219    1.4.3.13-s    3         Software Test Description (STD)    1.4.3.13      
                                 for the Multifunction Electronic                 
                                 Display Subsystem (MEDS)                         

  220    1.4.3.13-t    3         Software Test Reports (STR) for    1.4.3.13      
                                 the Multifunction Electronic                     
                                 Display Subsystem (MEDS)                         

  221    1.4.3.13-u    3         MEDS Software Version Increment    1.4.3.13      
                                 Deliverables                                     

  222    1.4.3.13-v    3         Version Description Documents for  1.4.3.13      
                                 the Multifunction Electronic                     
                                 Display Subsystem (MEDS)                         

  223    1.4.3.13-w    3         Software Acceptance Review (SAR)   1.4.3.13      
                                 Briefing                                         

  224    1.4.3.13-x    4         User's Manual for the Hardware     1.4.3.13      
                                 Dependent Executive (HDX) Support                
                                 Utilities of the Multifunction                   
                                 Electronic Display Subsystem                     
                                 (MEDS)                                           

  225    1.4.3.13-y    4         MDU Object Manipulator (MOM)       1.4.3.13      
                                 User's Guide                                     

  226    1.4.3.13-z    4         MEDS Software Standards and        1.4.3.13      
                                 Procedures Manual (SSPM)                         

  227    1.4.3.14-a    3         MEDS Software Discrepancy          1.4.3.14      
                                 Resolution Authorization                         

  228    1.4.3.14-b    3         MEDS Software Interim Release      1.4.3.14      
                                 Deliverables                                     

  229    1.4.3.15-a    3         PC-Decom Software Delivery         n/a           
                                 Requirements                                     

  230    1.4.3.16-a    3         Data Reconfiguration Deliverables  1.4.3.1,\     
                                                                    1.4.3.3,\     
                                                                    & 1.4.3.16    

  231    1.4.3.16-b    4         Reconfiguration Tools Requirements 1.4.3.16      
                                 Documents                                        

  232    1.4.3.16-c    3         Flight Software Applications CCP   1.4.3.16      
                                 Controlled Tools Software                        
                                 Inventory                                        

  233    1.4.3.16-d    1         Orbiter Command and Data Annex     1.4.3.16      

  234    1.4.3.16-e    3         SM/PM Level C Functional Subsystem 1.4.3.16      
                                 Requirements (FSR)                               

  235    1.4.3.16-f    3         Operational Shuttle Data           1.4.3.16      
                                 Reconfiguration Plan (OSDR)                      
                                 (JSC-20201)                                      

  236    1.4.3.16-g    1         Standard Integration Plan Annex    1.4.3.16      
                                 No. 4 Command and Data                           
                                 Requirements (NSTS-21000-A04)                    

  237    1.4.3.16-h    1         Shuttle Data Integration Plan      1.4.3.16      
                                 (DIP) (JSC-18206)                                

  238    1.4.3.17-a    2,3,4     SAIL Product Handbook and Product  1.4.3.17      
                                 Glossary                                         

  239    1.4.3.18-a    3         MAGRS-3S Link Certification        1.4.3.18      
                                 Package                                          

  240    1.4.3.18-b    3         MAGRS-3S Interface Control         1.4.3.18      
                                 Document                                         

  241    1.4.3.18-c    3         MAGRS-3S Software Design           1.4.3.18      
                                 Requirements                                     

  242    1.4.3.18-d    3         MAGRS-3S SASCB Discrepancy Report  1.4.3.18      
                                 (DR) Management Forms                            

  243    1.4.3.18-e    3         MAGRS-3S Program Notes and Waivers 1.4.3.18      

  244    1.4.3.18-f    3         MAGRS-3S                           1.4.3.18      
                                 Verification/Qualification Test                  
                                 Reports                                          

  245    1.4.3.18-g    4         MAGRS-3S Link Deliverables         1.4.3.18      

  246    1.4.9-a       3         Drawings, Engineering and          1.4.9         
                                 Associated Lists                                 

  247    1.4.9-b       1         Food Contamination Control Plan    1.4.9         

  248    1.4.9-c       1         Flight Food Acceptance             1.4.9         
                                 Documentation                                    

  249    1.4.9-d       3         Post Test Summary Report           1.4.9         

  250    1.4.9-e       1         Problem Reporting and Corrective   1.4.9         
                                 Action (PRACA)                                   

  251    1.4.9-f       3         Equipment Inventory Report         1.4.9         

  252    1.5.1.2       2         Operations and Contamination       1.5.1.2       
                                 Control Plan for Integrated                      
                                 Processing at Primary (KSC) and                  
                                 Alternate (DRFC/WSTF) Space                      
                                 Shuttle Landing Sites                            

  253    1.5.2.1       1         KSC Ground Launch Sequencer        1.5.2.1       
                                 Configuration Plan                               

  254    1.5.2.3       1         KSC Launch Team Certification Plan 1.5.2.3       

  255    1.5.4.1       2         Post Launch Operation Plans        1.5.4.1       

  256    1.5.5.2       2         Facility and Equipment Maintenance 1.4,\         
                                 Plan and Supporting Data           1.1.6.1,\     
                                                                    & 1.5.5.2     

  257    1.5.5.3       3         Notification of Modifications to   1.5.5.3       
                                 KSC Configured Systems and                       
                                 Equipment Report                                 

  258    1.5.5.4.3-a   3         Training/Certification Plan and    1.5.5.4.3     
                                 Schedule Report                                  

  259    1.6.1.1       2         Annex 7 (Training) - Payload       1.6.1.1,\     
                                 Integration Plan                   1.6.1.2,\     
                                                                    & 1.6.1.3     

  260    1.6.1.1.1     4         Flight Operations Training Records 1.6.1.1.1     

  261    1.6.1.1.2-a   2         Training Development and Support   1.6.1.1.2     
                                 Plan (TDSP) JSC 36049                            

  262    1.6.1.1.2-b   4         Curriculum, Lesson, and Instructor 1.6.1.1.2     
                                 Feedback                                         

  263    1.6.1.1.4     3/4       Instructor Certification Guides    1.6.1.1.4     

  264    1.6.1.2-a     2/3       Flight Controller Certification    1.6.1.2       
                                 Guides                                           

  265    1.6.1.2-b     4         Flight Controller Lessons and      1.6.1.2       
                                 Scripts                                          

  266    1.6.1.3-a     2         Crew Training Catalogs, ISS Master 1.6.1.3       
                                 Course Catalog                                   

  267    1.6.1.3-b     3/4       Crew Training Lessons and Scripts  1.6.1.3       

  268    1.6.1.3-c     3/4       Flight or Increment Specific Crew  1.6.1.3       
                                 Training Plan                                    

  269    1.6.1.3-d     2         Astronaut Candidate Training Plan  1.6.1.3       

  270    1.6.2.1.1     2         Flight Rules Publication           1.6.2.1.1     

  271    1.6.2.1.2     2         Operations Documentation Product   1.6.2.1.2     
                                 Handbook and Product Glossary                    

  272    1.6.2.1.3-a   2         Flight Data File (FDF)/Operations  1.6.2.1.3     
                                 Data File (ODF) Product Handbook                 
                                 and Glossary                                     

  273    1.6.2.1.3-c   2         Portable Onboard Computer (POC)    1.6.2.1.3     
                                 Software Loads Product Handbook                  
                                 and Glossary                                     

  274    1.6.2.2.2-b   3         Flight Design and Dynamics         1.6.2.2.2     
                                 Training and Certification                       
                                 Management Plan                                  

  275    1.6.2.2.2-c   3         Flight Design Handbook and Product 1.6.2.2.2     
                                 Glossary                                         

  276    1.6.2.2.3-a   3         Standards for Flight Design and    1.6.2.2.3     
                                 Dynamics Software                                

  277    1.6.2.2.3-b   3         Flight Design and Dynamics         1.6.2.2.3     
                                 Software Management Plan                         

  278    1.6.2.2.3-c   4         Flight Design Software System      1.6.2.2.3     
                                 Documentation                                    

  279    1.6.2.2.3-d   3         Flight Design and Dynamics Data    1.6.2.2.3     
                                 Management System Data                           
                                 Administration/Database                          
                                 Administration Plan                              

  280    1.6.2.2.3-e   2         Flight Design and Dynamics         1.6.2.2.3     
                                 Operations Center Software                       
                                 Engineering Strategic Plan                       

  281    1.6.2.3-a     2         Planning Requirements              1.6.2.3       
                                 Documents/Databases                              

  282    1.6.2.3-b     2         Flight Planning Product Handbook   1.6.2.3       
                                 and Product Glossary                             

  283    1.6.2.3-d     3         Systems Product Handbook and       1.6.2.3       
                                 Product Glossary                                 

  284    1.6.2.4       2         Payload/Cargo Product/Services     1.6.2.4       
                                 Handbook and Glossary                            

  285    1.6.4-a       2         Project Management Plan            1.6.4         

  286    1.6.4.2-a     3         Integrated Training Facility       1.6.4,\       
                                 Simulation Systems Operations      & 1.6.4.2     
                                 Handbook                                         

  289    1.9.1         1         Human Capital Retention Plan       1.9           
  ------------------------------------------------------------------------------------------

  ---- -------- ------ ---------------------------------- -------- --------
                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   

                                                                   
  ---- -------- ------ ---------------------------------- -------- --------

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 287 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SPOC Program Management Plan

7\. **DESCRIPTION/USE**: To describe the contractor's management
organization, approach and systems.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Within 10 days of contract Authority to
Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annually, unless update is waived by the
NASA OPR

Within 45 days after the addition/deletion of major content to\
the SPOC

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Management Plan shall describe the basis for the
contractor management organization, approach and systems. It shall
provide a comprehensive integration of all management systems of the
prime, subcontractors, and major vendors. The systems will include those
specifically required to accomplish the Statement of Work, as well as
those systems and procedures that are to be set in place by the
contractor.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Management Plan shall address the contractor's
plans for work definition and authorization, scheduling, budgeting, data
accumulation, Safety and Mission Assurance, Program recovery process,
subcontract/material control, indirect cost management, baseline
control, and organization structure.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 288 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Work Breakdown Structure (WBS) and Dictionary

7\. **DESCRIPTION/USE**: To organize the tasks to be accomplished in
this contract in a product-oriented structure. The WBS and dictionary
shall provide the framework for structuring the program implementation
plans, establishing and tracking budgets, preparing schedules,
developing work force and material estimates, preparing work
authorization documents, and reporting contract performance.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Upon request by NASA.

10\. **SUBMISSION FREQUENCY**: N/A

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1, 1.1.2.1 and 1.1.2.2; DRD's
1.1.1.1-g, 1.1.2.1-a, and 1.1.2.2-a.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The WBS shall encompass all the products required to
achieve all the requirements of this contract. The WBS shall subdivide
the work to be accomplished into elements that serve as the basis for
detailed planning and control, and in addition, permit collection of
cost and schedule data for each element.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The WBS shall depict a family tree composed of all
the work required by the contract. The dictionary contains a concise
description of contract tasks to be performed and products to be
delivered, subdivided by WBS element. A WBS element may represent an
identifiable product, a set of data, a service, a task, or a budget
function. The structure shall be at least at the level of detail in the
RFP SOW with additional levels as required by the contract. Lower levels
of detail, which the contractor uses for its own management purposes to
validate information reported to NASA, shall be compatible with NASA
requirements and be accessible to NASA. The relationship between the WBS
and the contractor's internal organizations and processes should also be
provided.

13.4 **FORMAT**: The WBS tree is to be in organization chart format and
the associated WBS narrative (WBS Dictionary) in text form and arranged
as stated in 13.3 of this DRD. The WBS tree and dictionary shall be
provided in both electronic and hard copy form.

13.5 **MAINTENANCE**: The WBS and WBS Dictionary shall be updated to
reflect contract changes as they affect the WBS coverage. Revisions
shall be incorporated by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 289 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-e

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Company Emergency Management Response Plan

7\. **DESCRIPTION/USE**: To document contractor requirements,
responsibilities, processes and implementation approach for specified
contingencies/emergencies.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Contract award plus 60 days.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall document their approach for
developing and maintaining plans for contingency and emergency
situations.

13.2 **APPLICABLE DOCUMENTS**: See Exhibit 1.1.1.1 to the Statement of
Work

13.3 **CONTENTS**: The plan shall outline USA's overarching contingency
and emergency preparedness planning approach that guides the generation
of supporting plans and procedures. The plan shall include a description
of the supporting plans and procedures structure and a description of
the key components of the USA emergency management process.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page (revision level and date) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 290 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-f

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Space Flight Operations Product Development Plans (PDP)

7\. **DESCRIPTION/USE**: To establish the schedule, the metrics, and
baseline all of the plans, procedures, and processes required for the
performance and delivery of operations and flight support and Shuttle
certification products.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC. Upon issuance of a contract change, the contractor shall
update the associated PDPs to reflect all changes within 60 days.

10\. **SUBMISSION FREQUENCY**: Update when processes change as
negotiated with NASA customer.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Space Flight Operations Product Development Plans
(PDP) defines all planned operations flight support, and Shuttle
certification activities provided by the Space Program Operations
Contract. The contractor plans, procedures, processes, and products will
be audited when deemed necessary by the Government.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The plans shall provide a detailed characterization
of the work efforts required to deliver products obligated under this
contract. It shall include, but is not limited to:

a)  Identification of plans, procedures and processes required for
    contract implementation.

b)  Product descriptions and applications, customers, organizational
    hand-offs, math models, databases, schedules, tools, and product
    assurance management systems.

c)  Metrics used to determine compliance with Government requirements.

d)  Metrics used for the identification of process improvement or
    requirements changes.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
electronic change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 291 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Organizational Breakdown Structure

7\. **DESCRIPTION/USE**: To identify the contractor's organization for
performing this contract.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Ten days after contract Authority to Proceed
(ATP)

10\. **SUBMISSION FREQUENCY**: (See 13.5)

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1, 1.1.2.1 and 1.1.2.2; DRD's
1.1.1.1-b, 1.1.2.1-a, and 1.1.2.2-1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The OBS shall encompass all elements of the contractor's
organization involved in performing the requirements of this contract.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: For each organizational element information shall
include the title of the organization and the name of the incumbent
manager (headcount is provided in DRD 1.1.2.1-e), and a cross-reference
to each WBS element where work is performed.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Complete reissue as required; otherwise, annually.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 6. **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-h

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Property Management Plan (PMP)

7\. **DESCRIPTION/USE**: To describe the method of administering
Government personal property.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Preliminary one month after Authority to
Proceed (ATP).

10\. **SUBMISSION FREQUENCY**: Final three months after ATP

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: Paragraph (e)(2) of FAR Clause 52.245-5, SOW
1.1.6.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Government Property Management Plan defines the
contractor's implementation of the life cycle function categories of
Government personal property. It also defines the process for property
disposition for Transition/Retirement.

13.2 **APPLICABLE DOCUMENTS**:

Federal Acquisition Regulation (FAR) Part 45

NASA FAR Supplement (NFS) Part 1845

13.3 **CONTENTS**: This plan shall identify those procedures which
constitute the contractor's Property Management System and shall include
at a minimum the following categories:

a\) Property management. i) Reports.

b\) Acquisition. j) Consumption.

c\) Receiving. k) Utilization.

d\) Identification. l) Maintenance.

e\) Records. m) Subcontractor control.

f\) Movement. n) Disposition.

g\) Storage. o) Contractor close-out.

h\) Physical Inventories.

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

The contractor shall identify excess or obsolete assets and initiate
excessing action. Receipt and disposal of excess property at NASA
centers is a government provided service identified in Attachment J-10.
Property excessing performance shall be reported.

**DRD CONTINUATION SHEET**

**TITLE**: Property Management Plan **DRD NO.**: 1.1.1.1-h

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

The following documents are provided as reference when dealing with NASA
Centers

  ------------------------------------------------------------------------------------------------- -------------------------------------------------------
  Directive ID                                                                                      Subject

  [NPD                                                                                              Supply Support and Material Management Policy
  4100.1A](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PD_4100_001A_&page_name=main)   (Revalidated 10/29/03)

  [NPR                                                                                              NASA Materials Inventory Management Manual (Revalidated
  4100.1D](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_4100_001D_&page_name=main)   3/30/04)

  [NPD                                                                                              Equipment Management
  4200.1A](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PD_4200_001A_&page_name=main)   

  [NPR                                                                                              NASA Equipment Management Manual
  4200.1E](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_4200_001E_&page_name=main)   

  [NPR                                                                                              Equipment Management Manual for Property Custodians
  4200.2B](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_4200_002B_&page_name=main)   w/Change 1, 9/11/03

  [NPD                                                                                              NASA Personal Property Disposal Policy (Revalidated
  4300.1A](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PD_4300_001A_&page_name=main)   12/8/04 of 1 year)

  [NPR                                                                                              NASA Personal Property Disposal Procedural Requirements
  4300.1A](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_4300_001A_&page_name=main)   

  [NPD                                                                                              Use of Space Shuttle and Aerospace Vehicle Materials as
  4300.4D](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PD_4300_004D_&page_name=main)   Mementos (Revalidated 3/29/04)

  [NPR                                                                                              Identification and Disposition of NASA Artifacts
  4310.1](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_4310_0001_&page_name=main)    (Revalidated 12/8/04)
  ------------------------------------------------------------------------------------------------- -------------------------------------------------------

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

  --------------- -------------------------------------------------------
                  

                  

                  

                  

                  

                  

                  

                  

                  

                  
  --------------- -------------------------------------------------------

13.4

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 294 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-i

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: New Technology Reporting

7\. **DESCRIPTION/USE**: Provides NASA with detailed technical
information relating to inventions, discoveries, improvements, and
innovations made by the contractor in the performance of work under this
contract for the purpose of identifying NASA-supported new technology,
and promoting its commercialization and public availability, and also to
ensure that the Government obtains sufficient rights in such technology
to meet its needs.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: See Submission Frequency

10\. **SUBMISSION FREQUENCY**: (1) REPORTABLE ITEMS (New Technology
Reports) shall be submitted to the Contracting Officer within two months
after the inventor discloses it in writing to Contractor personnel
responsible for the administration of the New Technology clause or, if
earlier, within six months after the Contractor becomes aware that a
reportable item has been made, but in any event for subject inventions
before any on sale, public use, or publication of such invention known
to the Contractor. (2) INTERIM REPORTS shall be submitted every 12
months from the date of this contract. (3) The FINAL REPORT shall be
submitted to the Contracting Officer within 3 months after completion of
the contracted work. The TMR\'s will determine the format for the
Interim and Final Reports. Data shall be provided on electronic media.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: NFS 1852.227-70, New Technology Clause

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Contractor shall establish and maintain active and
effective procedures to assure that reportable items are promptly
identified and disclosed to Contractor personnel responsible for the
administration of this New Technology clause within six months of
conception and/or first actual reduction to practice, whichever occurs
first in the performance of work under this contract. These procedures
shall include the maintenance of laboratory notebooks or equivalent
records and other records as are reasonably necessary to document the
conception and/or the first actual reduction to practice of the
reportable items, and records that show that the procedures for
identifying and disclosing reportable items are followed. Upon request,
the Contractor shall furnish the Contracting Officer a description of
such procedures for evaluation and for determination as to their
effectiveness. The contractor shall submit "Reportable Items," or New
Technology Reports, describing any invention, discovery, improvement, or
innovation of the Contractor, whether or not the same is or may be
patentable or otherwise protectible under the U.S. Patent Laws,
conceived or first actually reduced to practice in the performance of
any work under this contract or in the performance of any work that is
reimbursable under any clause in this contract providing for
reimbursement of costs incurred prior to the effective date of this
contract. Contractor shall also submit Interim Reports and a Final
Report providing summary information.

13.2 **APPLICABLE DOCUMENTS**: NFS 18-52.227-70 New Technology Clause

**DRD CONTINUATION SHEET**

**TITLE**: New Technology Reporting **DRD NO.**: 1.1.1.1-i

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13\. **DATA PREPARATION INFORMATION (continued)**:

13.3 **CONTENTS**:

I. REPORTABLE ITEMS (New Technology Reports). These reports shall
include the following elements as appropriate. NASA Form 666A (April
1985) may be used in accordance with instructions on the reverse of the
form. Use of this form is optional, provided all information listed
below is included in each report:

a.  Name and address of the contractor submitting the report.

b.  The contract number of the contract under which the report is being
    submitted.

c.  Title of the item reported.

d.  Brief description (abstract) of the item reported.

e.  Detailed description in the following order:

    1.  General purpose of the item (if not explained in the brief
        description or abstract).

    2.  Improvement and/or advantage over prior methods, materials, or
        devices.

    3.  Detailed description of the item, sufficiently complete in
        technical detail to convey a clear understanding, to the extent
        known at the time of the disclosure, of the nature, purpose,
        operation, and physical, chemical, biological, or electrical
        characteristics. Technical data, drawings, and sketches should
        be included as required to fully describe the item.

    4.  Feature of the item believed to be new.

    5.  Additional information needed to fully describe the item.

f.  Applications: Include potential commercial and other non-aerospace
    uses and users. Identify specific industries, processes, or products
    in which the "Reportable Item" might find application or to which it
    might be related.

g.  Description of possible extensions, or alternate embodiments of this
    item.

h.  Degree of development and use. Indicate applicable stage:

    1.  Concept only.

    2.  Development completed, prototype available.

    3.  Limited production.

    4.  Date of first actual use, or date of first planned use.

i.  Innovator\'s name(s) and social security number(s), mailing address,
    and telephone number.

j.  Identification of any previous publication of the disclosure. List
    publications, manuscripts submitted for publication, or reports
    pertaining to this item, together with relevant dates. If
    company-originated, state where they may be obtained; if not
    company-originated, indicate source and where publication may be
    obtained, if known.

k.  Technical supervisor or innovator(s).

II\. INTERIM REPORTS shall list reportable items during that period, and
certify that all reportable items have been disclosed (or that there are
no reportable items) and that the procedures set forth in Section 13.1
above have been followed.

III\. The FINAL REPORT shall list all reportable items or certify that
there were no such reportable items, and list all subcontracts at any
tier containing a new technology or patent rights clause or certify that
there were no such subcontracts.

13.4 **FORMAT**: Changes shall be incorporated as required by change
page or complete reissue

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 295 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-j

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Shuttle Ground Operations Processing Plans/Instructions

7\. **DESCRIPTION/USE**: To describe and baseline the contractor\'s
standardized technical and operational plans, instructions required for
the performance of Ground Operations processes and definition of the
required Government interfaces. This DRD defines specific action
applicable only to the KSC Ground Operations portion of the SPOC.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Updates annually, as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1, 1.3, 1.4, 1.5, and 1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Ground Operations Processing Plans/Instructions
shall document the contractors planned implementation of and/or support
for the performance of Ground Operations Processing activities
identified in S.O.W./ (Sections 1.1, 1.3, 1.4, 1.5, and 1.7) and other
appropriate Government requirements.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Identification of baseline plans and processes
required for contract implementation including process descriptions,
data flow diagrams and process flow charts; applications, customers and
organizational hand-offs; and process verification/integrity assurance
methodology. The Ground Processing Plans/Instructions shall address the
contractor\'s plans to implement the contractual requirements and
required Government interfaces as a minimum in the following Ground
Operations processes: 1) work flow planning, 2) work instruction
generation, 3) personnel training; 4) parts, material and services
provisioning; 5) facilities and support equipment maintenance; 6) ground
processing task execution, 7) ground processing information
provisioning; 8) surveillance, and 9) requirements control.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 296 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-k

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Notification of Significant Program Management Decisions

7\. **DESCRIPTION/USE**: The purpose of the DRD is to document
potentially significant contractor program management decisions such
that NASA program management will have timely and appropriate insight
prior to their implementation.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: As required by the contractor to meet the
DRD intent, but no later than the SPOC CMR following approval of this
DRD.

10\. **SUBMISSION FREQUENCY**: As required by the contractor to meet the
DRD intent of allowing NASA insight prior to implementation of
applicable decisions.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The purpose of the DRD is to inform the Shuttle Program
Manager of significant program management decisions prior to their
implementation and thus support proactive insight into these decisions.
Target decision areas to be addressed would include significant or
critical resource allocation changes (including reductions, increases or
re-distributions); decisions to make major investments in Program
processes, systems, property or facilities; or decisions to change the
workforce size and/or composition or major organizational/functional
restructuring. While not an absolute criteria, "significant" and "major"
for purposes of this DRD would be expected to encompass decisions
impacting budget plans by more than \$5 million or impacting manpower
plans involving more than 50 employees.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The following information may be delivered in the
form of a presentation or a white paper. At a minimum, the package shall
contain the following information:

a)  A description of the circumstances which lead to this decision.

b)  A discussion of the change being planned and the implementation
    schedule.

c)  An analysis of anticipated productivity improvements, if applicable

d)  An impact analysis that the decision will have on contract
    performance including potential safety, quality, schedule,
    workforce, and cost issues.

e)  A risk assessment performed to support each decision.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 297 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.1-l

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: KSC Emergency Preparedness Plan

7\. **DESCRIPTION/USE**: This plan will be used to define the SPOC
emergency management program and compliance with applicable directives
thereto at KSC.

8\. **DISTRIBUTION**: Per contracting Officer's letter.

9\. **INITIAL SUBMISSION**: 90 days after requirement is added to
contract.

10\. **SUBMISSION FREQUENCY**: Update overall plan annually and at least
monthly, provide documentation of required facility evacuation
exercise/drills performed during that month.

11\. **REMARKS**: Plan must cover an all-hazards approach to emergency
management.

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Contractor shall develop, document and implement the
approaches to ensure that all emergency preparedness documented
procedures listed in the Consolidated Comprehensive Emergency Management
Plan, JHB 2000 are implemented and are effective in maintaining the
mitigation, preparedness, response to, and recovery from all types of
natural and technological emergencies and disasters. The Contractor
shall conduct and support government exercises and simulations that
promote employee awareness and response to the Emergency Egress and
Training Advisory Group (EETAG).

13.2 **APPLICABLE DOCUMENTS**:

NPD 8710.1B NASA Emergency Preparedness Program

NPD 8715.2 NASA Emergency Preparedness Plan Procedural Requirements

JHB 2000 Consolidated Comprehensive Emergency Management Plan

NPD 1040A NASA Continuity of Operations

KNPR 1040.3 Kennedy NASA Procedural Requirements, Continuity of
Operations

13.3 **CONTENTS**:

The management structure, processes and reporting requirements,
techniques and formats must be established and/or defined and documented
to insure adequate visibility and insight for NASA Space Shuttle Program
Management and protection of personnel and resources. Under the
provisions of JHB 2000, and the EETAG, the Contractor shall conduct a
facility evacuation exercise in all flight hardware hazardous operations
facilities at least annually. After actions report following each
emergency exercise will be necessary to document lessons learned and
improvements to the plan. This report shall be provided to the NASA
Emergency Preparedness Officer and the EETAG Chairperson for review.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes to the plan shall be incorporated as
required by change page (Revision level \_\_ and date) or complete
reissue. Changes will be coordinated with the government.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 298 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.2.3

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Readiness Review

7\. **DESCRIPTION/USE**: To certify the completion or disposition of all
contractor tasks and planned work required to prepare for flight
readiness in accordance with NSTS 08117 and SSP 50108.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Prior to each Flight Readiness Review

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.2.2, 1.1.1.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Flight Readiness Review and statements document the
readiness of each function in support of the contractor's Certification
of Flight Readiness (CoFR).

13.2 **APPLICABLE DOCUMENTS**:

NSTS 08117 Requirements and Procedures for Certification of Flight
Readiness

SSP 50108 Certification of Flight Readiness for Space Station

13.3 **CONTENTS**: Data shall include the contractor's internal Flight
Readiness report with readiness statements that coverall processes and
products specified in the applicable documents, as well as any necessary
supporting data, required to satisfy the contractor\'s responsibilities
and readiness to support launch, mission and landing operations as
defined in the applicable documents.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: A historical file of the Flight Readiness Report
and Statements shall be maintained by the contractor. Archives shall be
maintained and archival materials dispositioned in accordance with NASA
and Federal Records Management regulations and procedures.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 299 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.4-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Space Shuttle Program Risk Management Plan

7\. **DESCRIPTION/USE**: To provide a comprehensive plan to manage and
document risk associated with operations of the Space Shuttle Program
(SSP).

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**:

Risk Management Plan (DR 1.1.1.4-a -- Plan): contract award plus 60 days

Reports: See submission frequency below.

10\. **SUBMISSION FREQUENCY**:

Risk Management Plan (DR 1.1.1.4-a -- Plan, Data Type: 2): as required
to document updates and changes.

Risk Management Surveillance Results (DR 1.1.1.4-a -- Surveillance
Results, Data Type: 3): every award fee period.

Risk Management Training Report (DR 1.1.1.4-a -- Training Report, Data
Type: 3): annualy

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Risk Management Plan shall address the
implementation of risk management standards and processes for SPOC.

13.2 **APPLICABLE DOCUMENTS**:

NPR 8000.4 Risk Management Procedural Requirements

NPR 7120.5 NASA Program and Project Management Processes and
Requirements

NSTS 07700 Space Shuttle Program Definition and Requirements

13.3 **CONTENTS**: The SSP Risk Management Plan shall describe how the
contractor proposes to manage risk throughout SPOC. It shall describe
how the contractor will identify, assess and mitigate/control risks
associated with each decision or process. As a minimum, this plan shall
include the following:

a)  Information that illustrates the functional relationships and lines
    of communication, including the involvement of subcontractors and
    major vendors.

b)  Descriptions of the risk management function within the organization
    including the process through which management decisions will be
    made. This will include a description of interfaces with NASA
    organizations and the NASA decision process for areas such as
    critical and catastrophic hazards, corrective actions, mishaps,
    safety variances/waivers, cost, schedule, and mission success.

c)  Description of the management controls that will be used to ensure
    compliance with the risk mitigation process.

d)  Description of flow down of NPR 8000.4 requirements to
    organizational elements including verification method to ensure
    requirements have been met.

e)  Description of surveillance methodologies to be used to measure the
    effectiveness of the risk management program.

**DRD CONTINUATION SHEET**

**TITLE**: Space Shuttle Program Risk Management Plan **DRD NO**.:
1.1.1.4-a

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13\. **CONTENTS (continued)**:

f)  Description of the training approach, including the type of training
    offered, employee requirements for completing training, and the
    frequency of training.

> In addition to the SSP Risk Management Plan, the contractor shall
> deliver a Surveillance Report each award fee period and a Training
> Report annually. The reports shall include the following information:

1.  Surveillance Report:

    a.  Description of the surveillance methodology.

    b.  Surveillance performed in the evaluation period.

    c.  Surveillance findings.

    d.  Plans for improvement.

2.  Training Report:

    a.  Departments or organizations participating in training.

    b.  Type of training (online, classroom)

    c.  Number of employees trained

    d.  Number of employees left to be trained.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per SPOC Attachment J-5.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 300 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.1.4-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Risk Assessment Documentation

7\. **DESCRIPTION/USE**: To provide a documented risk assessment to
Space Shuttle Program (SSP) management when the contractor is either a
requested evaluator on a formal, documented change request, or when the
contractor initiates a formal, documented change request to be
dispositioned at a Space Shuttle Program Board.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: See Submission Frequency below.

10\. **SUBMISSION FREQUENCY**: A risk assessment will be provided with
each formal, documented change evaluation provided by the contractor in
response to formal, documented change requests from Space Shuttle
Program Boards. When less than 2 working days are available for
evaluation, a verbally expressed risk assessment will be provided at the
review forum (this may include expedited items). Documentation of the
risk assessment will follow. A risk assessment will also be provided for
change requests initiated by the contractor and presented to a Space
Shuttle Program Board. If insufficient time is available to assess risk
prior to the disposition of an item, this will be so stated with a
recommendation for deferral.

A summary report (DR 1.1.1.4-b -- Report) shall be submitted quarterly.

11\. **REMARKS**: For purposes of this DR, Space Shuttle Program Boards
are those defined in NSTS 07700, Vol. IV, Book 1, Section 4.2.2,
'Program Boards', with the exception of the MRB, PMRB, and FOICB (and
FOICB delegated boards) unless specifically requrested by the FOICB
Chairman.

12\. **INTERRELATIONSHIP**: SOW 1.3., 1.1.1.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The documented risk assessment provides a formal means
to identify risks, assess risks and identify options for mitigating
risks associated with safety, mission success, schedule, supportability,
and/or cost. A risk assessment including analytical, quantitative or
qualitative methods as appropriate will be developed and provided with
each change evaluation provided by the contractor in response to formal,
documented change requests from Space Shuttle Program Boards, or change
requests initiated by the contractor and presented to Space Shuttle
Program Boards for disposition

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Vol. IV, Book 1, Section 4.2.2, 'Program Boards'.

NPR 8000.4 Risk Management Procedural Requirements

NPR 7120.5 NASA Program and Project Management Processes and
Requirements

13.3 **CONTENTS**: The assessment content shall vary based upon the
consequence/likelihood of risks imposed by a change item.

If no significant increase in risk is identified for a proposed change
item, the assessment shall include:

a)  A statement indicating 'no significant increase in risk'

b)  Justification for assessment as necessary.

**DRD CONTINUATION SHEET**

**TITLE**: Risk Assessment Documentation **DRD NO.**: 1.1.1.4-b

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

c)  Identification of any impact to baselined risk controls (hazard
    reports & CILs)

If a proposed change poses at least one risk whose
consequence/likelihood combination indicates a significant increase in
risk, the assessment shall include:

a)  Identification of the potential risk(s)/impact associated with the
    change, and the causes of these risk(s).

b)  Impact assessment (consequence & likelihood) to safety, mission
    success, schedule, supportability, and/or costs in the event the
    identified risk(s) were to occur.

c)  Options for mitigating the identified risk(s) including the
    contractor's recommendation.

d)  Impacts to baselined risk controls (hazard reports & CILs).

The summary report (DR 1.1.1.4-b -- Report) shall include as a miminum:

a)  The SSP board supported and number of risk assessments submitted

```{=html}
<!-- -->
```
a)  Type of change that was brought to the board, change number, and
    title

b)  Identification of any impact to baselined risk controls (hazard
    reports & CILs)

c)  Increase in risk or not.

d)  Organization performing the risk assessment

13.4 **FORMAT**: Formal delivery of risk assessments shall be made via
the change proposal or change evaluation submittal processes as defined
by each SSP board.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 301 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-a

3\. **DATA TYPE**: Initial 533 Baseline Reports: 1 4. **DATE REVISED**:

NASA Forms 533M/Q: 3 5. **PAGE**: 1/3

6\. **TITLE**: Financial Management Reports

7\. **DESCRIPTION/USE**: To provide financial management reports for
planning, monitoring, and controlling project resources; accounting for
the contract's accumulated expenditures and other liabilities; accruing
cost in NASA\'s accounting system; evaluating contractor cost
performance; and projecting/forecasting cost and work force resource
requirements which realistically support the schedule requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**:

Initial baseline 533 reports - at time of initial submission, and when
the Contracting Officer requires additional detail as necessary such as
when options are exercised.

533M - Monthly, by the 15th working day, but no later than the 23rd
calendar day, of the calendar month following the end of the
contractor\'s accounting month.

533Q - Quarterly, by the 20th working day, but no later than the 30th
calendar day, of the month preceding the quarter being reported on.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1, 1.1.2.1; DRD's 1.1.1.1- a & b,
1.1.2.1-b , 1.1.2.2-a & b; All data shall be reconcilable with data from
all of the reports required by this DRD, the reports required by DRD
1.1.2.1-b, and the Performance Measurement System (DRD 1.1.2.2-a & b).

13\. **DATA PREPARATION INFORMATION**:

13.1 SCOPE: The Report provides data on accumulated costs and funding
projections for management of the contract and shall serve as the basis
for contractor communication with NASA concerning financial planning and
control.

13.2 **APPLICABLE DOCUMENTS**:

NFS 1852.242-73 NASA Contractor Financial Management Reporting

NPD 9501.1G NASA Contractor Financial Management Reporting System

NPR 9501.2D NASA Contractor Financial Management Reporting

13.3 **CONTENTS**: The initial NF533 report is required in the NF533Q
format to be used as a baseline for the life of the contract. The
initial (baseline) NF533Q report shall be submitted by the contractor
within 30 days after authorization to proceed has been granted. The
initial report shall reflect the original contract value detailed by
negotiated reporting categories and shall be the original contract
baseline plan. In addition to the initial (baseline) report, monthly
NF533 reporting shall begin no later than the 15th calendar day of the
month in which contract ATP is issued.

**DRD CONTINUATION SHEET**

**TITLE**: Financial Management Reports **DRD NO.**: 1.1.2.1-a

**DATA TYPE**: Initial Baseline Reports: 1 **PAGE**: 2/3

NASA Forms 533M/Q: 3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

Columns 7b (planned cost incurred/hours worked for the month) and 7d
(cumulative planned cost incurred/hours worked) of the NF533M represent
the negotiated baseline plan for the contract. There may not be a
relationship between the estimates provided in column 8 of the NF533M to
columns 7b and 7d. Columns 7b and 7d represent the legally binding
contract negotiated baseline plan plus all authorized changes.

Short and long-term cost estimates, which include all data entered in
columns 8 and 9a on the NF533M and NF533Q reports, shall be based on the
most current and reliable information available.

Prior period adjustments should be reported in columns 7a and 7c of
NF533M and column 7a of the NF533Q with a footnote discussing the
reasons for and amounts of the adjustments.

Uncompensated overtime hours worked should be reported on NF533 reports
as a separate line item or in the footnotes.

Monthly NF533 reporting is no longer required once the contract is
physically complete, provided the final cost report includes actual cost
only (no estimates or forecasts). The contract must continue to submit
monthly NF533 reports as long as estimates for the following period are
included. If the final cost of a contract changes after the submission
of the "final" contract cost report, the contractor must submit a
revised NF533 report in the month the cost change is recognized.

NASA is required by law to maintain accrual accounting, which requires
cost to be reported in the period in which benefits are received,
without regard to time of payment. For cost accrual purposes, data shall
be reported by NASA specific primary work codes (PWCs), as provided by
NASA.

This data shall be provided in the NF533 format. Data shall identify
price and workforce. Variance analyses will be required for those PWCs
(cumulative to date and monthly) as follows:

All variances greater than \$1 Million

All variances +/- 10% and over \$100K

The cost elements shall be reported as follows:

a)  Direct and indirect elements of cost, fee, subtotal price,
    anticipated changes with fee and total price at WBS level 2 and
    lower levels as directed for specific areas of the WBS.

b)  Equivalent personnel (EP) at WBS level 3 and lower level as directed
    for specific areas. EP's shall be reported for column 7a (current
    month actuals) and column 8a (next month's estimate).

c)  Price will be reported at WBS level 3 and lower levels as directed
    for specific areas.

d)  Price performance summary narratives at WBS level 4 and lower levels
    as directed for specific areas. The narratives shall include cost
    performance variance analyses and recovery plans. Variance Analyses
    will be required for actual cost incurred versus plan (negotiated
    baseline) as follows:

\--All variances greater than \$1 Million

\--All variances +/- 10% and over \$100K

**DRD CONTINUATION SHEET**

**TITLE**: Financial Management Reports **DRD NO.**: 1.1.2.1-a

**DATA TYPE**: Initial 533 Baseline Reports: 1 **PAGE**: 3/3

NASA Forms 533M/Q: 3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

For WBS 1.1.6.1, Facilities, projects greater than \$500,000 shall be
reported uniquely using the NASA project identification number and
title. The project identification number will have a suffix of P for
Preliminary Engineering Report, D for Design, or C for Construction.
(The preceding requirements are being satisfied by SPOC DRD's 1.1.2.1-b,
Resources Reporting Management System (FMS) and the project reporting
activities outlined in the SPOC Facility Management Plan DRD 1.1.6.1-a.)

Example: 95001 - P - Repair Roof - Building 1

95001 - D - Repair Roof - Building 1

95001 - C - Repair Roof - Building 1

The report will include a subtotal line for all projects valued at
\$500K and over.

A summary cost report split by suffix is required for projects valued at
less than \$500K, except that all environmental specific projects shall
be reported at the project level.

A total line will be used which includes all of the facility projects.

Any cost that is not reported within 60 days of the completion of the
project should also be explained.

13.4 **FORMAT**: These reports shall be prepared in accordance with NPR
9501.2D and NFS 1852.242-73, and be provided in hard copy form.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 302 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-b

3\. **DATA TYPE**: Initial Submission: 1 4. **DATE REVISED**:

Subsequent Submissions: 3 5. **PAGE**: 1/2

6\. **TITLE**: Resources Management Reporting System

7\. **DESCRIPTION/USE**: To provide resources management reports for
planning, monitoring, and controlling project resources based on the
NASA budget with respect to program operating plans (POP), fiscal year
operating plans, monthly plan vs. actual statusing, and any special
request reporting as specified by NASA.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**:

POP - as required (Reference section 13.3 of this DRD - a, b, c, d, e,
f, g, h, and i)

Operating plan - as required (Reference section 13.3 of this DRD - a, b,
c, d, e, f, g, h, and i)

Plan vs. actual status - only required if the approved FY Operating Plan
differs from the Contract Value Baseline Plan required for DRD
1.1.2.1-a. If required, then submission will be monthly, by the 15th
working day, but no later than the 23rd calendar day, of the calendar
month following the end of the contractor's accounting month accounting
month (Reference section 13.3 of this DRD - a, g, h, i, j, k).

Special requests - as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1., 1.1.2.1; DRD's 1.1.1.1 - a &
b, 1.1.2.1 - a & c, 1.1.2.2 - a & b. All data shall be reconcilable
between the resources management reports, the NASA Forms 533M and 533Q
(DRD 1.1.2.1 - a), and the Performance Measurement System (DRD 1.1.2.2 -
a & b)

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These reports shall be a source of Contractor program
operating plans, fiscal year operating plans, monthly plan vs. actual
statusing, and any special request reporting as specified by NASA.
Source data shall be at the lowest level collected by the contractor.
Data to be reconcilable to the contract value.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The contents of the report will generally include the
following elements; however, additional data may be included to meet
specific guidelines:

a)  Price (labor/non-labor separately identified) and workforce (e.g. -
    headcount, EP)

b)  Direct and indirect rate assumptions

c)  Workforce/non-labor requirements assumptions

d)  Statement of work/task descriptions (required for selective WBS(s)
    only)

e)  Product detail for tasks -product listing with DRD number, schedule
    delivery date (required for selective WBS(s) only)

f)  Schedule assumptions

g)  Sort by TMR

**DRD CONTINUATION SHEET**

**TITLE**: Resources Management Reporting System **DRD NO.**: 1.1.2.1-b

**DATA TYPE**: Initial Submission: 1 **PAGE**: 2/2

Subsequent Submissions: 3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

h)  NASA specific primary work codes (PWCs), as provided by NASA.

```{=html}
<!-- -->
```
1.  Variance analysis (cumulative to date and monthly)

2.  All variances greater than \$1 million

```{=html}
<!-- -->
```
i)  All variances +/-10% and over \$100K

j)  Periodic year-end analysis

k)  Other (Master Control Record, Operations Centers, etc.)

13.4 **FORMAT**: Contractor shall conform to Government-approved style
and layout formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval. Electronic data shall be formatted and
delivered per Government standards as specified in section J-5,
paragraph 2.5, or per Contracting Officer approval. In cases where
format requirements conflict, Contractor shall obtain resolution from
Contracting Officer.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 303 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Energy Utilization and Consumption Report

7\. **DESCRIPTION/USE**: This report shall serve as a source of
information for direct charges to the appropriate programs or other
users. The energy consumption data included in this report will serve as
a metric for energy reduction goals. This report will also be a source
of information for each Center's Energy Efficiency and Water
Conservation Plans and Progress Assessments submitted by each NASA
Center annually.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: DRD submissions consist of Monthly,
Quarterly, and Annual reports. The Annual serves in place of the
Quarterly report for the 4th Quarter and serves in place of the Monthly
for month of September (Sept. data to be included in annual). The
Quarterly reports serve in place of the Monthly for December, March, and
June with data for those month's included in the Quarterly reports.
Monthly reports shall be submitted in October, November, January,
February, April, May, July, and August. As such, there will be 12
submissions annually comprised of 1 Annual, 3 Quarterlies, and 8
Monthlies. Submissions shall be published by the end of the following
month.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.2.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report shall identify and document essential energy
utilization and cost data on which NASA can base energy management and
conservation decisions. In addition, data from this report will be
utilized for the purpose of energy cost phasing and as a metric for
contractor performance in the area of energy management. The report
shall include a subset of data for each location (i.e. KSC/Launch
Operations, Downey, Palmdale, JSC, etc., as required). Certain data
requested may be site specific as defined below.

13.2 **APPLICABLE DOCUMENTS**:

NASA Procedural Requirements (NPR) 8570.1

Energy Efficiency and Water Conservation

10 CFR 434

10 CFR Part 436

13.3 **CONTENTS**: The contractor shall, as a minimum, submit the
following parts:

a.  Energy Consumption Report: Report by commodity volume and
    consumption per reportable square foot. (KSC cost data will be based
    on rate information provided by the institution contractor.)

> Frequency: Monthly\--Individual Facility Consumption (where metered):
> metered electricity and fuel consumption, and cost for individual
> govt. owned facilities.
>
> Frequency: Quarterly---accumulative consumption for the quarter.

**DRD CONTINUATION SHEET**

TITLE: Energy Utilization and Consumption Report DRD NO.: 1.1.2.1-d

DATA TYPE: 3 PAGE: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

b.  Variance Analysis: Comparisons shall be made between the planned and
    actual electricity, boiler fuel, and natural gas consumption and
    cost. Includes a narrative explaining substantial factors (new
    facilities, rate changes, energy conservation measures, increased
    processing, etc.) that have impacted the totals, when compared to
    the same time period of the previous year.

> Frequency: Quarterly

c.  Forecasts: The forecasts shall support the budget cycle and include
    the current fiscal year and the four succeeding fiscal years. These
    forecasts, (excluding facilities that are reimbursable to NASA),
    shall project consumption and cost for electricity, fuel oil #2,
    propane and natural gas. The forecast shall include a listing and
    description of the projects or activities which may significantly
    impact (positively or negatively) energy consumption. (The
    institution contractor will provide fuel consumption data to the
    SPOC at KSC.)

> Frequency: Quarterly (KSC only)
>
> Frequency: Annually (all others)

d.  Energy Projects and Initiatives: Status of current energy projects
    and initiatives with implementation costs in excess of \$10,000. As
    a minimum, each entry shall include a project description, point of
    contact, planned-versus-actual cost estimate, planned and actual
    energy and cost avoidance (in base units, BTU's, and dollar), and
    planned and actual completion dates. Actual energy and cost
    avoidance data shall be reported for the first two years after
    project is complete.

> Frequency: Quarterly

e.  Annual Report and Compliance Summary: Shall list and describe
    accomplishments (including implemented energy conservation measures
    and initiatives, with measured energy savings) from the preceding
    fiscal year. Also, graphical and tabular data shall be shown to
    compare planned-versus-actual energy consumption, consumption per
    gross square foot, and cost. Tabulations shall also include actual
    energy reduction, for the past 12 months, from the baseline year
    (presently 1985). Any adjustments necessary to the baseline year
    shall be fully justified and documented.

> Frequency: Annually

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 304 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-e

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: On-site and Off-site Headcount Report

7\. **DESCRIPTION/USE**: To provide on-site and off-site headcount data
which is used to provide NASA headquarters required workforce reports
and for future planning for housing requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission of
schedule from the SFOC.

10\. **SUBMISSION FREQUENCY**: Quarterly, by the 17th of the month

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.2.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report provides on-site and off-site end-of-quarter
headcount data containing the breakouts shown under 13.3 for each NASA
Center.

[Definition of Terms]{.underline}

a)  [On site]{.underline} - Those personnel performing on the contract
    occupying physical space on a NASA Center. KSC includes Cape
    Canaveral Air Force Station (CCAFS). It includes those personnel
    temporarily absent from assigned duty stations (e.g., on leave
    without pay, annual/sick leave, TDY).

b)  [Off site]{.underline} - Total of those personnel on the contract
    but physically located outside the environs of a NASA Center.

```{=html}
<!-- -->
```
1.  [Dispossessed]{.underline} - Those personnel who normally would
    occupy physical space within the environs of a NASA Center, but who
    have been located outside due to nonavailability of space.

2.  [Others off-site]{.underline} - Those personnel within total
    contract headcount who are not planned to occupy physical space
    within the environs of a NASA Center.

```{=html}
<!-- -->
```
c)  [Construction subcontractors]{.underline} - Those personnel
    performing on the contract within the environs of a NASA Center.
    Include a brief description or title of the effort.

13.2 **APPLICABLE DOCUMENTS**: None

**DRD CONTINUATION SHEET**

**TITLE**: On-site and Off-site Headcount Report **DRD NO.**: 1.1.2.1-e

**DATA TYPE**: 4 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS**:

+--------------------------+-----------+------------+---------+-------+
| END OF QUARTER           |           |            |         |       |
| CONTRACTOR HEADCOUNT     |           |            |         |       |
| REPORT                   |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| CONTRACT                 | ON-SITE   | OFF-SITE   | O       | TOTAL |
|                          |           | DI         | FF-SITE |       |
|                          |           | SPOSSESSED | OTHER   |       |
+--------------------------+-----------+------------+---------+-------+
| TOTAL PER NASA CENTER    |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| PRIME                    |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| TOTAL OF SUBCONTRACTORS  |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| SUBTOTAL OF              |           |            |         |       |
| SUBCONTRACTORS           |           |            |         |       |
|                          |           |            |         |       |
| (Other than              |           |            |         |       |
| constructions            |           |            |         |       |
| subcontractors)          |           |            |         |       |
|                          |           |            |         |       |
| List each subcontractor  |           |            |         |       |
|                          |           |            |         |       |
| (Include only those with |           |            |         |       |
| on-site personnel)       |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| SUBTOTAL OF CONSTRUCTION |           |            |         |       |
| SUBCONTRACTORS           |           |            |         |       |
|                          |           |            |         |       |
| List each construction   |           |            |         |       |
| subcontractor            |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

[]{.mark}

1\. **DRL NO.**: 305 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Geographical Economic Impact Report

7\. **DESCRIPTION/USE**: To provide cost and workforce geographical
economic impact data which is used to respond to NASA and Congressional
requests.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC and KSC Specific report: October 17, 2006.

10\. **SUBMISSION FREQUENCY**: Annually, 15 working days after request
for report for the SPOC total geographical economic impact data. October
17 of each fiscal year for the KSC Specific Report.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.2.1; data shall be reconcilable to
end of fiscal year NASA Forms 533M.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Geographical Economic Impact Report provides actual
SPOC total cost and workforce geographical economic impact data for each
fiscal year per the breakouts shown under 13.3, or as modified by
request.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**:

+-------------------------------+-------------------+-------------------+
| **Location and Performer**    | Workforce         | Total Cost (\$K)  |
|                               | (DEQs\*)          |                   |
+-------------------------------+-------------------+-------------------+
| Each NASA Center              |                   |                   |
|                               |                   |                   |
| Prime                         |                   |                   |
|                               |                   |                   |
| Each Subcontractor            |                   |                   |
|                               |                   |                   |
| Each major vendor             |                   |                   |
|                               |                   |                   |
| Others as required            |                   |                   |
+-------------------------------+-------------------+-------------------+
|                               |                   |                   |
+-------------------------------+-------------------+-------------------+
| Each State                    |                   |                   |
|                               |                   |                   |
| Prime                         |                   |                   |
|                               |                   |                   |
| Each Subcontractor            |                   |                   |
|                               |                   |                   |
| Each major vendor             |                   |                   |
|                               |                   |                   |
| Others as required            |                   |                   |
+-------------------------------+-------------------+-------------------+
| Each Country                  |                   |                   |
|                               |                   |                   |
| Prime                         |                   |                   |
|                               |                   |                   |
| Each Subcontractor            |                   |                   |
|                               |                   |                   |
| Each major vendor             |                   |                   |
|                               |                   |                   |
| Others as required            |                   |                   |
+-------------------------------+-------------------+-------------------+

\*DEQ = Direct Full-time Equivalents

**DRD CONTINUATION SHEET**

**TITLE**: Geographical Economic Impact Report **DRD NO.**: 1.1.2.1-f

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

The following is a KSC Specific Report that shall be provided separately
from the rest of the data requirements outlined in this document.

+-------------------------------------+--------------------------------+
| **Florida Contracts and Purchases** | Totals (\$)                    |
+-------------------------------------+--------------------------------+
| Amount Spent in Brevard County      |                                |
|                                     |                                |
| USA-Florida Labor                   |                                |
|                                     |                                |
| Contractors Operating On-site at    |                                |
| KSC                                 |                                |
|                                     |                                |
| Off-site Businesses in Brevard      |                                |
| County                              |                                |
|                                     |                                |
| Brevard Subtotal                    |                                |
+-------------------------------------+--------------------------------+
| []{.mark}                           |                                |
+-------------------------------------+--------------------------------+
| Amount Awarded to Florida           |                                |
| Businesses Outside Brevard          |                                |
+-------------------------------------+--------------------------------+
| Florida Totals                      |                                |
+-------------------------------------+--------------------------------+
| Out of State Totals                 |                                |
+-------------------------------------+--------------------------------+
| *GRAND TOTALS*                      |                                |
+-------------------------------------+--------------------------------+

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 306 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5: **PAGE**: 1/1

6\. **TITLE**: Notification of Potential Labor Dispute and Contingency
Strike Plan

7\. **DESCRIPTION/USE**: The Notification of Potential Labor Dispute and
Contingency Strike Plan will be used by the NASA Contracting Officer and
the Industrial Labor Relations Office to facilitate the coordination of
activities between the contractor and the affected NASA operational
directorates to ensure that necessary steps are taken to prepare for any
potential strike situations and to prevent the disruption of work.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: In accordance with 13.1.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: FAR Clause 52.222.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: A Notification of Potential Labor Dispute must be
submitted 45 days prior to the expiration of any collective bargaining
agreements and at the first indication of potential labor unrest, which
could delay the timely performance of the contract. The Notification
shall describe the situation that has the potential of impacting the
contract and provide the corrective actions initiated. A Contingency
Strike Plan must be submitted at contract start and updated if there is
any indication of a potential labor unrest or potential picketing
activity. The Notification of Potential Labor Dispute and Contingency
Strike Plan are required for the prime and any subcontractors supporting
this contract.

13.2 **APPLICABLE DOCUMENTS**: None.

13.3 **CONTENTS**: The Notification of Potential Labor Dispute shall
describe the situation that has the potential of impacting the timely
performance of the contract, it should provide the planned negotiation
dates with organized labor, and describe other corrective actions
initiated. Notification should be made prior to the expiration of
collective bargaining agreements, prior to any significant changes to
existing working conditions or pay practices, or any situation that
could impact the performance of the contract through labor unrest. The
Contingency Strike Plan shall describe the Contractor's plan for
assuring the timely performance of the work under this contract during a
strike or work stoppage situation. As a minimum, contents should
include: information on implementation of the strike plan, a pre-strike
checklist for managers and supervisors, a description of how critical
work will be performed, an organization chart of the strike committee
membership, phone numbers of key management personnel, and standards of
conduct policies during the strike.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 307 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/4

6\. **TITLE**: Wage/Salary and Fringe Benefit Data

7\. **DESCRIPTION/USE**: The Wage/Salary and Fringe Benefit Data will be
used by the NASA Contracting Officer and the Industrial Labor Relations
Office to provide the necessary data for submittal of Standard Form (SF)
98, Notice of Intention to Make a Service Contract and Response to
Notice, to the Department of Labor, and to assist in the monitoring of
Service Contract Act compliance.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Start Date of Contract.

10\. **SUBMISSION FREQUENCY**: Annually, 90 days prior to the
anniversary date of the contract.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.2.1 and FAR 52.222-41

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Wage/Salary and Fringe Benefit Data must be
submitted by the contractor, and any subcontractors which are subject to
the provisions of the Service Contract Act, to the Contracting Federal
Agency. In accordance with FAR regulations 22.1007 and 22.1008, the
Contracting Officer is required to submit a SF 98 to the Department of
Labor, Wage and Hour Division.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Wage/Salary and Fringe Benefit Data should
contain the data included in the enclosed DRD forms, titled "Wage/Salary
Rate Information", "Fringe Benefits for Service Employees", and "Fringe
Benefits per Collective Bargaining Agreement". The Wage/Salary Rate
Information shall contain a listing of all exempt and nonexempt labor
classifications working on the contract. Separate forms should be
utilized for classifications working in different geographic areas and
for each subcontractor. Wage determination numbers, appropriate labor
organization names, and subcontractor names, must be reflected. All
nonexempt labor classifications must be matched to wage determination
classes or to Collective Bargaining Agreement (CBA) classifications for
represented classes. Annotate exempt or nonexempt and union or nonunion.
The current hourly rates should reflect the actual lowest and highest
paid employees, along with a computed average rate. State the number of
employees working in each labor category. Separate Fringe Benefit forms
should be completed for nonrepresented classifications and for each
separate CBA. A separate form must be completed for the prime and each
subcontractor. Three hard copies and one electronic copy of each
Collective Bargaining Agreement are required if organized labor is
represented on your contract.

13.4 **FORMAT**: The Wage/Salary and Fringe Benefit Data should be in a
format substantially the same as enclosed with this DRD. (Forms 2, 3 and
3A).

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

Form 2

  ------------------------------ ------------------------------ ------------------------- ------------------------ ------------------- -------------------------
  WORK SHEET FOR SF-98 DATA                                                                                                            

  WAGE RATE INFORMATION                                                                                                                

                                                                                                                                       

  CONTRACTORS\                   WAGE DETERMINATION\            EXEMPT OR\                UNION OR\                CURRENT\            MYE NO OF\
  LABOR\                         [CLASSIFICATION]{.underline}   [NONEXEMPT]{.underline}   [NONUNION]{.underline}   [HOURLY             [EMPLOYEES]{.underline}
  [CLASSIFICATION]{.underline}                                                                                     RATE]{.underline}   

                                                                                                                                       

  Illustration of required data:                                                                                                       

                                                                                                                                       

  Project Manager                Not Required                   E                         N                        \$40.00             1

  Supervisor                     Not Required                   E                         N                        \$32.00             1

  Electrical Engineer            Not Required                   E                         N                        \$26.50 - 30.00     3

  Engineering Tech, Jr           Engineering Tech, I            N                         N                        \$14.00 - 17.00     12

  Electrical Technician          Electronics Tech Maint II      N                         U                        \$19.02 - \$21.50   4

  Secretary                      Secretary I                    N                         N                        \$14.52 - \$15.50   2

  File Clerk                     General Clerk II               N                         N                        \$9.86              1

  Clerical Data Entry            Word Processor I               N                         N                        \$11.45 - \$12.90   3

                                                                                                                                       

                                                                                                                                       

                                                                                                                                       

  Submit data in the above                                                                                                             
  illustrated format for all                                                                                                           
  labor classifications used, or                                                                                                       
  planned to be used, on this                                                                                                          
  contract.                                                                                                                            

  All contractor labor                                                                                                                 
  classifications must be                                                                                                              
  matched to wage determination                                                                                                        
  classes listed in CBA\'s                                                                                                             
  represented classes                                                                                                                  

  or classes shown in the area                                                                                                         
  wage determination for                                                                                                               
  nonrepresented classes.                                                                                                              

                                                                                                                                       

                                                                                                                                       

                                                                                                                                       

  CONTRACTORS\                   WAGE DETERMINATION\            EXEMPT OR\                UNION OR\                CURRENT\            MYE NO OF\
  LABOR\                         [CLASSIFICATION]{.underline}   [NONEXEMPT]{.underline}   [NONUNION]{.underline}   [HOURLY             [EMPLOYEES]{.underline}
  [CLASSIFICATION]{.underline}                                                                                     RATE]{.underline}   

                                                                                                                                       

                                                                                                                                       

                                                                                                                                       
  ------------------------------ ------------------------------ ------------------------- ------------------------ ------------------- -------------------------

FORM 3

Page 1 of 2

FRINGE BENEFITS PER COLLECTIVE BARGAINING AGREEMENT

For period from \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ to
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Contractor:

Contract Number:

Number of employees in bargaining unit
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Total number of employees on contract
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

1\. Shift Differential: (Describe any pay over and above base rates for
2nd, 3rd, weekend, or other shifts.)

2\. Health and Welfare Items and Other Fringe Items: (Indicate whether
or not coverage is provided to employees and state current average
hourly cost per employee covered by a Collective Bargaining Agreement.)

Coverage Average

Item Provided Hourly Cost

(Yes or No)

a\. Life Insurance

b\. Accidental Death

c\. Disability

d\. Medical and Hospital

e\. Dental

f\. Retirement Plan

g\. Savings/Thrift Plan

h\. Sick Leave

i\. Tuition

j\. Other (Describe)

TOTAL

FORM 3

Page 2 of 2

3\. Paid Absences:

Service Requirement Days per Year

a\. Vacation

b\. Holiday

c\. Sick Leave

d\. Jury Leave

e\. Funeral Leave

f\. Military Leave

g\. Other (Describe)

4\. Severance Pay: (Briefly describe terms and amounts.)

5\. Other Fringe Benefits: (Describe any other fringe benefits not
included above, and show average hourly cost.)

6\. Premium Pay: (Discuss all premium pay provisions not previously
shown on this form.)

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_

Signature of Company Representative Date

FORM 3A

Page 1 of 1

FRINGE BENEFITS FOR SERVICE EMPLOYEES

For Period from \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ to
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Contractor:

Number of nonexempt employees on contract:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Total number of employees on contract:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

1\. Health and Welfare Items and Other Fringe Items: (Indicate whether
or not coverage is provided to employees and state current average
hourly cost per service employee.)

Item Coverage Average

[Provided]{.underline} [Hourly Cost]{.underline}

a\. Life Insurance

b\. Accidental Death

c\. Disability

d\. Medical & Hospital

e\. Dental

f\. Retirement Plan

g\. Savings/Thrift Plan

h\. Sick Leave

i\. Tuition Reimbursement

j\. Other (Describe)

TOTAL

2\. Paid Absences

[Service Requirement]{.underline} [Days per Year]{.underline}

a\. Vacation

b\. Holidays

c\. Sick Leave

d\. Jury Leave

e\. Funeral Leave

f\. Military Leave

g\. Other (Describe)

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Signature of Company Representative Date

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 308 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-i

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Advance Notification of Workforce Reductions

7\. **DESCRIPTION/USE**: The Contractor shall notify in writing, the
SPOC Contracting Officer, the effected Center Industrial Relations
Officer (IRO), with a copy to the corresponding Administrative
Contracting Officer (ACO), at least 14 calendar days in advance of the
notification to employees of any planned workforce reduction of
permanent, full-time, and part-time employees that exceeds 10% of the
total contract workforce at the effected center or 25 employees,
whichever is less.

In addition, if Workforce Adjustment and Retraining Notification (WARN)
Act notification is required, the contractor shall provide the
information required by the WARN Act, section 639.7(c) and a listing of
all organizations to be notified including those required by section
639.6(a), (c), and (d), at least five (5) days prior to issuance of the
notification.

8\. **DISTRIBUTION**:

JSC-BV/Michael J. Lonchambon, SPOC Contracting Officer

JSC-BA/Connie R. Pritchard, JSC Labor Relations Officer

KSC-OP-MS/Bob R. Pirkle, KSC Administrative Contracting Officer

KSC-QA-A-1/Samuel G. Haddad, KSC Industrial Relations Officer

MSFC-PS40/Harry B. Craig, MSFC Administrative Contracting Officer

MSFC-AD60/Talmage R. Reynolds, MSFC Industrial Relations Officer

9\. **INITIAL SUBMISSION**: As required.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.2.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Provides for notification of impending workforce
reductions at NASA Centers where SPOC work is performed.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The notification shall include the reason for the
reduction in workforce, the number of employees impacted, the targeted
classifications, their physical location, and their location within
contract organizational structure.

The notification shall also identify the expected date of the first
separation and the anticipated schedule for making separations, as well
as the name and telephone number of a company official to contact for
further information.

13.4 **FORMAT**: Contractor form is acceptable. Contractor shall conform
to delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be communicated to the distribution
list until the reduction in force is completed.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 309 **ISSUE**: Basic 2. **DRD NO.**: 1.1.2.1-k

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Annual Property NASA Form (NF) 1018 Report

7\. **DESCRIPTION/USE**: To report contractor held NASA Property on an
annual basis.

8\. **DISTRIBUTION**: The annual NASA Form 1018 shall be filed
electronically through the NASA Form 1018 Electronic Submission System
(NESS).

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Annually, November 30th

11\. **REMARKS**: None

12\. **INTERRELATIONSHIP**: NASA FAR Supplement Subpart 1845.505-14,
SPOC Article G.7, SOW 1.1.2.1 and in accordance with approved Property
Control Procedures.

13\. **DATA PREPARATION INFORMATION**: In accordance with NFS 1845.7101

13.1 **SCOPE**: In compliance with NFS 1845.7101

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Property in the custody of the prime contractor and
subcontractors

13.4 **FORMAT**: Per NF 1018 instructions and subpart 1845.71

13.5 **MAINTENANCE**: Corrections/updates are to be reported to the
cognizant Industrial Property Officer (IPO) and submitted through NESS
when directed by the IPO.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 310 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.1-l

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Financial Reporting Contractor-Held Property

7\. **DESCRIPTION/USE**: Report NASA Property in the custody of
contractors on both a monthly and annual basis.

8\. **DISTRIBUTION**:

a\) The monthly reports shall be electronically submitted using the
Contractor-Held Asset Tracking System (CHATS)
(http://nasachats.gsfc.nasa.gov/) using the format described in the
CHATS user\'s manual.

b\) NASA Form (NF) 1018 reports shall be submitted using the NF 1018
Electronic Submission System (NESS) (http://ness.gsfc.nasa.gov).

9\. **INITIAL SUBMISSION**: The first monthly report required is for
October, 2006, and this report is due no later than October 21, 2006.
For the contractor property reporting level, this DRD is in force. The
due date for the first annual report is November 30, 2006. All reports
shall be submitted electronically.

10\. **SUBMISSION FREQUENCY**:

a\) The due date for the Monthly Property Financial Reporting submission
is the 21st day after the close of the month, beginning November 21,
2006. The due date for Annual Property Reporting via NASA Form (NF 1018
is November 30.

b)All reports shall be submitted electronically.

11\. **REMARKS**: None

12\. **INTERRELATIONSHIP**: Procurement Information Circular (PIC)
03-14, 03-18, 04-12, NASA FAR Supplement Subpart 1845.7101, SOW 1.1.2.1
and in accordance with approved Property Control Procedures.

13\. **DATA PREPARATION INFORMATION**:

a\) Monthly Property Financial Reports are required to be submitted
using the format located at the URL referenced in paragraph 8. Monthly
Financial Report will be submitted in accordance with PIC 04-12.

b\) Annual Property NF 1018 reports shall be submitted using the NF 1018
Electronic Submission System (NESS). The NF 1018 report provides annual
summary-level property management and financial data on
government-furnished and contractor-acquired NASA property.

c\) The NF 1018 shall be completed in accordance with NASA FAR
Supplement Subpart 1845.7101 and any supplemental guidance provided by
the Contracting Officer.

13.1 **SCOPE**: Monthly reporting shall be in compliance with NASA PIC
04-12 and report NF 1018 value definitions. The PIC requirement in PIC
Enclosure 2, paragraph 2.d of the NASA PIC 04-12, regarding the Work
Breakdown Structures (WBS) is omitted.

13.2 **APPLICABLE DOCUMENTS**: None

**DRD CONTINUATION SHEET**

**TITLE**: Financial Reporting Contractor-Held Property **DRD NO.**:
1.1.2.1-l

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS**:

Monthly Property Financial Reports

a\) Monthly property financial reports are required with item level
supporting data. This data shall be submitted for all items with an
acquisition cost of \$100,000 or more, in the contractor's and its
subcontractors' possession, in the following classifications: real
property, equipment, special test equipment, special tooling, and agency
peculiar property. Monthly reporting is not required for property in the
above classifications with an acquisition cost under \$100,000. Monthly
data shall also be submitted for items of any acquisition cost in the
classifications of materials and work-in-process (WIP). Itemized monthly
data is required for materials and WIP line items of \$100,000 and over.
Summary monthly data is required for materials and WIP line items under
\$100,000.

b\) Acquisition costs shall be developed using actual costs to the
greatest extent possible, especially costs directly related to
fabrication, such as labor and materials. Supporting documentation shall
be maintained and available for all amounts reported, including any
amounts developed using estimating techniques.

c\) All adjustments shall be thoroughly explained and directly related
to a specific fiscal year. If the fiscal year cannot be determined, the
default shall be the previous fiscal year.

d\) Work Breakdown Structure (WBS) shall NOT be provided for all
Contractor Acquired Property (CAP), WIP, and any new materials acquired.

NF 1018 Reports

a\) Contractors shall report all NASA-owned property in US dollars,
regardless of location.

b\) Negative reports are required.

c\) This reporting shall be completed in accordance with the NASA FAR
Supplement (NFS) Subpart 1845.7101 and any supplemental guidance
provided by the Contracting Officer.

13.4 **FORMAT**: The monthly reports shall be electronically submitted
using the Contractor-Held Asset Tracking System (CHATS)
(http://nasachats.gsfc.nasa.gov/) using the format described in the
CHATS user\'s manual.

13.5 **MAINTENANCE**: Revisions shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 311 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.2-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Performance Measurement System Reports (Development and
Production)

7\. **DESCRIPTION/USE**: To provide technical, cost and schedule
performance summary and assessment based on an earned value performance
measurement system for development and production activities.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from SFOC.

10\. **SUBMISSION FREQUENCY**: No later than the 25th day of the
calendar month.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1, 1.1.2.1, 1.1.2.2; DRD's
1.1.1.1-b & 1.1.2.1-a; and clause H.31. All data shall be reconcilable
between the NASA Forms 533M & 533Q (reference DRD 1.1.2.1-a) and the
Performance Measurement System (PMS) Reports.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The reports shall provide technical, cost, and schedule
performance data and assessments and shall serve as the basis for
contractor communication with NASA concerning earned value performance
management.

13.2 **APPLICABLE DOCUMENTS**: NPD 9501.3, Attachment A

13.3 **CONTENTS**: The PMS system and reporting shall be in accordance
with Attachment A of NASA Policy Directive 9501.3, dated February 18,
1997. The definition of cost accounts is to be mutually agreed upon by
the contractor and NASA.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue. G-1, G-2, and G-3

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO**.: 312 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.2.2-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Performance Measurement System (PMS) Reports (Operations)

7\. **DESCRIPTION/USE**: To provide technical, cost and schedule
performance summary and assessment based on a performance measurement
system for all operations activities (i.e.,
non-development/non-production activities).

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Monthly

11\. **REMARKS**: In addition to the mutually agreed upon metrics
provided routinely by this DRD, NASA will have access to lower level
contractor metrics for audits and insight.

12\. **INTERRELATIONSHIP**: SOW 1.1.1.1, 1.1.2.1, 1.1.2.2; DRD's
1.1.1.1-b & 1.1.2.1-a; and clause H.31. All data shall be reconcilable
between the NASA Forms 533M & 533Q (reference DRD 1.1.2.1-a) and the
Performance Measurement System (PMS) Reports.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The reports shall provide technical, cost, and schedule
performance data and assessments and shall serve as the basis for
contractor communication with NASA concerning performance management.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**:

General: The PMS data and baseline updates shall be reported by
significant third level WBSs as agreed between the contractor and the
appropriate NASA TMRs. Changes or additions shall be by mutual agreement
between the contractor and NASA. Provisions shall be made to separately
identify, account for, and forecast resource requirements for special
projects. The following report packages shall be provided:

a\) SPOC Program Overview Status - Provide an overall program status in
brief narrative form, indicating the progress on all major items.
Include summary status of technical, schedule, and cost performance.
Identify any significant problems and corrective actions.

b\) Performance Metrics Packages - Provide metrics as agreed between the
contractor and the NASA TMRs that reflect the key areas of concern for
performance.

1\. Metrics will address safety, quality, work content, schedule,
efficiency, cost, and other areas, as appropriate.

2\. Metrics will facilitate subsequent government analysis by including
the supporting data (i.e. Excel spreadsheets)

3\. Variance analysis for each metric for deviations beyond established
thresholds or expected trends shall be provided. In addition, corrective
actions will be enumerated for unfavorable variances beyond established
thresholds or expected trends.

**DRD CONTINUATION SHEET**

**TITLE**: Performance Measurement System (PMS) **DRD NO.**: 1.1.2.2-b

Reports (Operations)

**DATA TYPE**: **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 313 **ISSUE**: Basic 2. **DRD NO.**: 1.1.3.2-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Small Business Subcontracting Report

7\. **DESCRIPTION/USE**: To report contractor's efforts and progress
toward meeting the contractor's Small Business (SB), Small Disadvantaged
Business (SDB), Women-Owned Small Business (WOSB), Historically
Underutilized Small Business Zone (HUBZone) Small Business,
Service-Disabled Veteran-Owned Small Business (SDVOSB), Veteran-Owned
Small Business (VOSB), Historically Black College or University/Minority
Institution (HBCU/MI) subcontracting goals established in H.3.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Quarterly, due no later than the 45th day
after the close of the quarter.

11\. **REMARKS**: None

12\. **INTERRELATIONSHIP**: H.3

13\. **DATA PREPARATION INFORMATION**: None

13.1 **SCOPE**: To document prime contractor and subcontractor efforts
and progress to foster subcontracting opportunities for the small
business categories outlined in Item 7, Description/Use, above.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**:

a\) Metrics - the report will provide the contractor's metrics providing
actual expenditures for the preceding quarter, inclusive of lower-tier
subcontractor actuals. Breakdown will include metrics by category as
indicated in H.3.

b\) Reporting of actions taken and a description of efforts expended by
contractor and subcontractors toward enhancing the utilization of the
small business categories outlined in Item 7, Description/Use, above.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 314 **ISSUE**: Basic 2. **DRD NO.**: 1.1.3.2-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Small Business Subcontracting Plan

7\. **DESCRIPTION/USE**: To update the contractor's subcontracting plan
in accordance with FAR 19.702(a)(1).

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Semiannually on February 1st and August
1st of each year. The revision submitted on February 1st shall
incorporate all reportable actions from July 1st to December 31st of the
previous year. The revision submitted on August 1st shall incorporate
all reportable actions from January 1st to June 30th of the present
year. A reportable action is defined as a modification to (Insert new
Contract Number) which increases the contract value by greater than
\$500,000.

11\. **REMARKS**: None

12\. **INTERRELATIONSHIP**: FAR Clause 52.219-9

13\. **DATA PREPARATION INFORMATION**: None

13.1 **SCOPE**: To document prime contractor and subcontractor efforts
to foster subcontracting opportunities for Small Business (SB), small
disadvantaged business (SDB), Women-Owned Small Business (WOSB),
Historically Underutilized Business Zone (HUBZone) Small Business,
Service-Disabled Veteran-Owned Small Business (SDVOSB), Veteran-Owned
Small Business (VOSB), Historically Black College or University/Minority
Institution (HBCU/MI) concerns.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The contents of the revised subcontracting plan shall
be in accordance with paragraph (d) of FAR clause 52.219-9.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 29. **ISSUE**: BASIC 2. **DRD NO.**: 1.1.4.1-b

3\. **DATA TYPE**: 1/3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Information Technology (I/T) Plan and Reports

7\. **DESCRIPTION/USE**: To document the contractor\'s compliance with
Federal and NASA Information Technology (I/T) Planning and Reporting
regulations and requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: I/T plans are required prior to any I/T
acquisition.

I/T standards plan submittals are required prior to the submittal of any
I/T plans.

Initial I/T inventory report submittals are due when requested, but no
more than once per year.

Initial security reports and Master Plan submittals are due at contract
authority to proceed plus 90 days.

10\. **SUBMISSION FREQUENCY**: I/T plans are required twice annually
(POP-1 and POP-2 timeframes), I/T inventory reports are required upon
request but no more than once annually. Security reports are required as
specified in NPR 2810.1 Security of Information Technology.

11\. **REMARKS**: I/T plans and reports shall be presented to the Space
Shuttle Program (SSP) Chief Information Officer (CIO) for subsequent
submittal to the NASA Center CIO's as required.

12\. **INTERRELATIONSHIP**: SOW 1.1.4 and 1.6.4, clause H.11, and clause
H.19

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The plans and reports document the contractor\'s
compliance with Federal and NASA I/T planning and reporting regulations
and requirements. The contractor shall maintain interoperability with
referenced NASA IT standards.

13.2 **REFERENCE DOCUMENTS**:

NASA-STD-2804H (09/21/2004) Minimum Interoperability Software Suite

NASA-STD-2805H (09/21/2004) Minimum Hardware Configurations

NASA-STD-2810 (04/28/1997) UNIX Interoperability Standards

NASA-STD-2814A (06/27/2000) NASA Integrated Information Technology
Architecture

NPD 2800.1a (08/18/2004) Managing Information Technology

NPD 2810.1c (04/07/2004) Security of Information Technology

NPR 2800.1 (09/17/2004) Managing Information Technology

NPR 2810.1 (08/12/2004) Security of Information Technology

13\. **DATA PREPARATION INFORMATION**:

13.3 **CONTENTS**:

a\) An annual, contract-wide I/T Plan, per current SSP CIO
instructions/guidelines.

1\) In concert with the POP-1 each year, a high-level (Level A) 5-year
plan is required. This plan will define and justify the major I/T
initiatives planned for each of the 5 fiscal years, with a corresponding
list of I/T (i.e., hardware and software) platforms required to support
each initiative. Level A plans also include an obsolescence management
plan as described in NASA CIO Executive Notice 03-95. Data type: 1

**DRD CONTINUATION SHEET**

**TITLE**: Information Technology Plan and Reports **DRD NO.**:
1.1.4.1-b

**DATA TYPE**: 1/3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

2\) In concert with the POP-2 each year, a more detailed Level B I/T
Plan for the "next" FY only is required. Level B will describe I/T
purchases by platform standards (in support of approved Level A
initiatives) to be acquired during the year. Data type: 1

b\) De-facto and accepted I/T standards throughout the contract will be
documented, and processes which will result in contract-wide I/T
standards will be established. Included in this report will be how the
contractor is complying with AI-96-035. Data type: 1

c\) At a minimum, the contractor shall comply with direction in the
latest edition of Office of Management and Budget Circular A-130,
Appendix III, Security of Federal Automated Information Resources, and
confirm in writing the following for each applicable system:

1\) That a knowledgeable individual has been assigned security
responsibility for the system.

2\) That a system security plan is in place.

3\) That a review of security controls is conducted upon significant
change to the system, or at least every three years, whichever occurs
first.

4\) That a management official has authorized processing based upon
implementation of its security plan prior to being placed in service,
upon significant change to the system, or at least every three years,
whichever occurs first.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 318 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.4.1-c

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Data Accession List

7\. **DESCRIPTION/USE**: To provide an index of data that is available
on request. It is a medium for identifying contract internal data which
have been generated by the contractor in compliance with the work effort
described in the statement of work and other contract requirements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: As required.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.4.1 and clause H.19

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Data Accession List shall be a cumulative listing of
all contractor-generated documentation.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Data Accession List shall provide a listing of
all data requirement response documentation plus other project-pertinent
documents including drawings through the fourth generation breakdown
level. The format and content of these data shall be prepared by the
contractor to document compliance with the statement of work and other
contract requirements. The list shall be a cumulative listing of
contractor-generated data response documentation generated to date, data
released during the past quarter, and data submitted to NASA. In
addition to other types of data, the list shall reflect type 4 and 5
project documentation not otherwise covered by specific DRD's and shall
describe procedures for obtaining the listed information. The list shall
include a cross-reference to the related section of the statement of
work, number and document identification (DRD number if applicable),
document number, title, date, and revision.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: On-line access to the data listing can be provided
in lieu of hard copy listings.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 319 ISSUE: BASIC 2. **DRD NO.**: 1.1.4.1-d

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Procurement Data Package

7\. **DESCRIPTION/USE**: To provide for maintenance of reproducible
masters of updated technical and process documentation.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: As required.

10\. **SUBMISSION FREQUENCY**: N/A

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: Clause H.30

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This requirement encompasses all technical and process
documentation agreed to by the parties as necessary for this Procurement
Data Package.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Procurement Data Package shall include
reproducible masters of the following documentation:

DOCUMENTATION DRD OR IRD

a)  Management Plan 1.1.1.1-a

b)  Property Management Plan 1.1.1.1-h

c)  Information Management Plan 1.1.4.1-a

d)  Data Management Plan 1.1.4.1-e

e)  Configuration Management Plan 1.1.5.1

f)  Verification Management Plan 1.1.5.2-a

g)  Government Property Inventory, Record Verification, and Utilization
    Plan 1.1.6.2

h)  Space Program Operations Product Development Plans 1.1.1.1-f

i)  Space Shuttle Program Risk Management Plan 1.1.1.4-a

j)  Interface Revision Notice (IRN) to Systems Interface Control
    Documents (ICD\'s) 1.2.2.5-a

k)  Preliminary Interface Revision Notice (PIRN) and Interface Revision
    Notice (IRN) to Program\
    Requirements Interface Control Document (ICD) (CORE) and Interface
    Definition Documents (IDDs) 1.2.2.5-b

l)  Payload Interface Control Documents (ICD\'s and Installation
    Requirements\
    Documents (IRD\'s) 1.2.2.6

m)  Primary Avionics Software System (PASS)/Backup Flight System (BFS)\
    Interface Control Documents (ICD\'s) 1.4.3.3-p

n)  Mission Assurance Plan 1.3-a

o)  Quality Plan 1.3.3

**DRD CONTINUATION SHEET**

**TITLE**: Procurement Data Package **DRD NO.**: 1.1.4.1-d

**DATA TYPE**: 4 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 CONTENTS (continued):

p)  Acceptance Data Package (ADP) (one for each vehicle) 1.3.3.1

q)  Instrumentation Program and Components Lists (IPCL's) 1.4.1.6.1-g

r)  SRB and Range Safety Command Destruct System Failure Modes and
    Effects Analysis (FMEA) 1.4.2.1-a

s)  SRB and Ranges Safety Command Destruct System Critical Items List
    (CIL) 1.4.2.1-b

t)  SRB Project Management Plan 1.4.2.1-f

u)  Equipment Inventory Report 1.4.9.2

v)  Operations Documentation Product Handbook and Product Glossary
    1.6.2.1.2

w)  Flight Data File (FDF)/Operations Data File (ODF) Product Handbook
    and Glossary 1.6.2.1.3-a

x)  Flight Design Handbook and Product Glossary 1.6.2.3

y)  Systems Products Handbook & Product Glossary 1.6.2.3-d

z)  KSC Work Authorization Documents (Category I) 1.4-a

a)  Facility and Equipment Maintenance Plan and Supporting Data 1.5.5.2

b)  Shuttle Ground Processing Plans/Instructions 1.1.1.1-j

c)  Logistics Performance Reports 1.4-c

PDRDs

d)  Ground Support Equipment Inventory Report FE006

e)  Vehicle Integrated Schematics FE008

f)  Subcontractor Engineering Drawings & Associated Lists for GSE FE012

g)  Critical Items List (CIL) FE023

h)  Failure Mode Effects Analysis (FMEA) FE017

i)  EEE Parts As-Designed (Where Used) & Qualifications Status
    Electronics Database FE019

j)  EEE Part Drawings and Specifications FE021

k)  Thermal Protection System (TPS) Maintenance Specifications FE075

l)  Space Shuttle System Drawing Specifications FE044

m)  Engineering Drawings & Associated Lists FE043

n)  Subcontractor Engineering Design Drawings & Associated Lists FE045

o)  Master Dimensions Specification (MDS) Manual FE049

p)  Vehicle End Item (VEI) Specification FE093

13.4 **FORMAT**: Various formats, in accordance with the DRD\'s under
which the documentation is generated.

13.5 **MAINTENANCE**: Documentation included in this package shall be
maintained current, in accordance with the DRD\'s under which the
documentation is generated.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 33A **ISSUE**: BASIC 2. **DRD NO.**: 1.1.4.1-g

3\. **DATA TYPE**: 2 4. **DATE** **REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Enterprise Architecture Reviews

7\. **DESCRIPTION/USE**: To provide architecture reviews and
descriptions of the contractor's information systems.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: None.

10\. **SUBMISSION FREQUENCY**: On request by issuance of a Program
Directive on a case-by-case basis.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.4.1 and clauses H.11 and H.19

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Projects, facilities, and services selected for review.

13.2 **APPLICABLE DOCUMENTS**:

1\) NPD 2800.1A, Managing Information Technology

2\) NPG 2810.1, Security of Information Technology Handbook

3\) NPD 2830.1, NASA Enterprise Architecture

4\) NPR 2810.1A, Security of Information Technology

5\) NPR 2830.1, NASA Enterprise Architecture Procedures

13.3 **CONTENTS**:

1\. Enterprise Architecture Reviews shall be for selected projects or
systems on specific request (or as defined in NPR 2830.1, NASA
Enterprise Architecture Procedures) and require the following
infrastructure to provide and support the creation of the review
product:

a\) Develop conceptual models to facilitate discussions. NASA Enterprise
Architecture (NASA EA) and the Federal Enterprise Architecture (FEA)
encompass information, concepts, and models ranging from the top-level
strategic vision to the detailed implementation of specific
technologies. An initial model shall be constructed using enterprise
architecture COTS toolset of the contractor's choice that can prepare
mappings and reporting in an electronic fashion. Conduct a services
decomposition and prepare a reference architecture for each service
area. The services decomposition activity fully delineates each discrete
service for a given services portfolio and defines each discrete
service. At a minimum, the model shall contain the following information
for each project or service:

i\) Map the project or service to the goals and objectives of the
Mission Directorate(s)

ii\) Map the project or service to the NASA goals and objectives

iii\) Map the project or service to the defined NASA EA reference model

iv\) Map the project pr service tp the FEA business reference model

v\) Map the project or service to the NASA Centers for usage

vi\) Construct a graphical matrix to illustrate the project usage and
impact as it pertains to each of the NASA installations

b\) Construct a reference architecture that is a graphically
represented, high-level system overview and intentionally free of
implementation details. This shall generally include high-level
descriptions of the system components, a definition of relationships
between components, definitions of relationships between system
components and elements external to the system, and identification of
performance drivers and capacity requirements. Where applicable, the
reference architecture shall also provide high-level definitions of key
data sources, data stores produced, and interfaces between the system
components.

c\) Collected knowledge and information for these reviews are a
strategic asset. The requirement for data integrity, high-availability,
reliability, and confidentiality is mandatory.

d\) Include appropriate performance metrics.

2\. The specific Architecture Review for a specific project or service
shall be a presentation constructed from the models and mappings as well
as additional project management and budget information.

3\. The conceptual models and reference architecture shall be initially
constructed at the time the first architecture review is requested.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 320 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.4.1-e

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Data Management Plan

7\. **DESCRIPTION/USE**: To provide a description of the contractor's
tracking system.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 90 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review and as required thereafter.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.4.1 and clause H.19

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Data Management Plan describes the contractor\'s
overall implementation of the data management requirements specified in
the contract as integrated by the prime contractor and subcontractors.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Data Management Plan shall contain the following
sections:

a\) Data Management: This section shall define the scope and depth of
the contractor's efforts including management, organization, planning,
and the relationship of the data management program to the contractor\'s
other administrative and technical organizations. The plan shall specify
the contractor\'s management policies and identify, by specific
reference, standard practices and detailed work instructions to be used
in implementing the data management program. The plan shall include the
following elements: management organization, control procedures, storage
and retrieval procedures, subcontractor control procedures, and special
restrictions. The plan shall include a preliminary data submittal
schedule for fulfilling submittal of data in the specified quantities,
specific media (electronic, paper, other), and due dates required.

b\) Document Development: This section defines the procedures, policies,
and formats used to produce and distribute document contract
deliverables. The section shall include specifics on document numbering
schema; and shall reference the contractors\' documentation which are
used to define internal layout and format requirements, and specific
document setup practices that ensure appropriate hard-copy and/or
electronic output.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 321 **ISSUE**: Basic 2. **DRD NO.**: 1.1.4.1-f

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Records Management Plan

7\. **DESCRIPTION/USE**: To describe the contractor's records management
organization, processes and systems.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: 90 Days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Reviewed annually, issued as required
thereafter.

11\. **REMARKS**: N/A

12\. **INTERRELATIONSHIP**: SOW 1.1.4.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The plan will document the contractors' processes for
identifying, collecting, maintaining and archiving all records generated
during the performance al all task in this SOW. This shall include plans
for disposition of these records at the end of the contract.

13.2 **APPLICABLE DOCUMENTS**:

[NPD
1440.6G](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PD_1440_006G_&page_name=main)

[NPR
1441.1D](http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_1441_001D_&page_name=main)

13.3 **CONTENTS**: The Records Management Plan shall address the
contractor's plans for identifying, collecting, maintaining and
archiving all official records generated under this contract.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 322 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.5.1

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Configuration Management Plan

7\. **DESCRIPTION/USE**: To describe the contractor's method for
accomplishing the configuration management requirements of the contract.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after contract Authority to Proceed
(ATP)

10\. **SUBMISSION FREQUENCY**: Updated annually or as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.5.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The plan shall describe the contractor's management
approach and planned implementation methods for accomplishing the
configuration management requirements of the contract.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Volume IV Configuration Management Requirements

SSP 41170 Configuration Management Requirements

13.3 **CONTENTS**: The plan shall address each of the following
essential elements of CM:

\(1\) configuration identification, (2) configuration control, (3)
configuration status accounting, and (4) configuration verification. The
plan shall describe in relation to these essential elements of CM the
contractor's CM organization, policies, procedures, implementation
approach, and control systems that are to be used to ensure proper
performance of all required contract CM activities. In addition,
satisfaction of all the requirements of the applicable documents in 13.2
shall be addressed within the CM plan.

The plan shall also describe the configuration management activities,
processes and systems to be employed to support the NASA change
evaluation and control process for the approval of program requirements.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 323 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.5.2-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Verification Management Plan

7\. **DESCRIPTION/USE**: To describe the contractor's method for
accomplishing the verification management requirements of the contract.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after contract Authority to Proceed
(ATP)

10\. **SUBMISSION FREQUENCY**: Update as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.5.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The plan shall describe the contractor's management
approach and planned implementation methods for accomplishing the
verification management (VM) requirements of the contract.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Volume XI Systems Integrity Assurance Program Plan

13.3 **CONTENTS**: The plan shall describe the contractor's program to
ensure and demonstrate that the hardware/software processing
requirements have been correctly implemented and to ensure and
demonstrate that the hardware/software as-built configuration is in
accordance with the approved requirements documents and the approved
engineering. The plan shall also describe how identified "deltas"
between the approved requirements/engineering will be handled including
documenting the authority for any approved deltas.

The plan shall describe the contractor's VM organization, policies,
procedures, implementation approach, and control systems that are to be
used to ensure proper performance of all required contract VM
activities. In addition, satisfaction of all the requirements of NSTS
07700, Volume XI shall be addressed within the VM plan.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 324 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.5.2-b

3\. **DATA TYPE**: 5 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Mission Configuration Product Plan (MCPP)

7\. **DESCRIPTION/USE**: To document, as a mission requirements control
system (MRCS) dataset, the individual Shuttle elements\' configurations
based on the flight requirements per Space Shuttle Program (SSP)
direction.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Baselined for each flight at Cargo
Integration Review (CIR) plus 10 days, Launch Site Requirements Review
(LSRR) plus 18 days, Orbiter Roll-out Review (ORR) plus 14 days, Flight
Readiness Review (FRR) plus 14 days, Launch plus 30 days.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.5.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The MCPP consists of documentation and an MRCS Dataset
documenting all system-level drawing requirements and possible ferry
flight requirements with all required modification records for Orbiter,
External Tank (ET), Solid Rocket Booster (SRB), Reusable Solid Rocket
Motor (RSRM), Space Shuttle Main Engine (SSME), Mission Kit Equipment,
and Payloads.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: System-level drawings (including Engineering Orders
(EO\'s)), reflecting mission reconfiguration (i.e., installation and
removal) requirements, and modifications required to satisfy SSP
requirements.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Continuously update in MRCS database.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 325 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.6.1-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Facility Management Plan

7\. **DESCRIPTION/USE**: The Facility Management Plan will be used to
provide insight into the contractor's approach for facility management.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: By February 1 each year (updated or
complete reissue).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.6.1, 1.5.5.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Facility Management Plan shall describe the
contractor's approach to managing facility responsibilities in support
of the SPOC and shall include a 5 year plan which identifies the
facility projects required, regardless of ultimate fund source, for each
year for the five fiscal years beginning three years from the
commencement date of the current fiscal year. This plan shall document
contractor processes and implementation approach for facility management
to include environmental compliance and restoration requirements and
real property reporting and accountability. The plan shall address the
long range goals for the transition of facility management
responsibilities in the future.

13.2 **APPLICABLE** **DOCUMENTS**:

NPD 8820.2, Appendix C Facility Project Implementation Handbook

NPR 8800.15 Real Estate Management Program and Implementation Handbook

NPD 8800.14 Policy for Real Property Management

13.3 **CONTENTS**: The plan shall identify the contractor approach to
the coordination of facility responsibilities and budget priorities to
optimize maintenance, repair, and replacement projects for facilities
and facility systems and environmental compliance and restoration
requirements across the SPOC Government owned locations. Provide a
facility management plan that will encompass facility space utilization
planning and integrated facility project planning and reporting
requirements and real property responsibilities. The management
structure, processes and reporting requirements, techniques and formats
must be established and/or defined and documented to insure adequate
visibility and insight for NASA Space Shuttle Program Management and
Center Facility Management.

**DRD CONTINUATION SHEET**

**TITLE**: Facility Management Plan **DRD NO.**: 1.1.6.1-a

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

The plan shall also address the following:

a)  Process for environmental assessments and permit applications for
    constructed and modified facilities and processes.

b)  Process to insure facility system drawings and as-builts are kept
    current for contractor generated changes and all changes are
    incorporated as required. Contractor shall impose a self audit with
    the results reported annually.

c)  Incorporation of local Government facility project approval process
    and standardization requirements that are in place at affected
    sites. (e.g. Air Force, Army, TAL sites, KSC, etc.)

d)  Propose general guidelines to establish boundaries or limits of
    acceptable facility actions that may be accomplished without
    Contracting Officer involvement. These guidelines must be approved
    by the Contracting Officer prior to use.

e)  Process and management structure to implement facility projects.

f)  Completion milestone definitions for management and reporting of
    projects.

g)  Procedure to allow for in-progress audit and final evaluation of
    project completion and documentation.

13.4 **FORMAT**: Contractor format is acceptable. All documents must be
provided in both electronic and hard copy.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 326 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.6.1-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Facility Project Reporting Requirements

7\. **DESCRIPTION/USE**: The facility project reports will be used to
provide insight into the scope, cost, schedule and performance of
facility projects.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.6.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The project requirements documents shall be provided in
sufficient detail to allow for an independent cost estimate of all scope
and related issues identified to accomplish the project. The other
project documentation shall be submitted for each facility project as
required.

13.2 **APPLICABLE DOCUMENTS**: NPD 8820.2 Appendix C

13.3 **CONTENTS**: The contractor shall submit facility project
documentation and reporting as follows:

a)  Facility projects greater than \$50K and less than \$500 K (for
    documentation purposes)

    1.  NASA Form 1509 and 1510 (prior to project start)

b)  Facility Projects Greater than \$500 K

    1.  Facility project description, justification and cost estimate
        (NASA Form 1509, 1510) (annually and as required for
        revisions/updates)

    2.  Project requirements document (Include all requirements and
        costs associated with a completed project.)

    3.  Facilities Project Implementation Schedule (after award of
        project)

    4.  Final acceptance certificate including a recap of all funding
        (after project completion)

c)  Facility projects greater than \$5M (in addition to the above
    reporting requirements)

    1.  Project Management Plan (Prior to design start)

    2.  Facility Project Pre-Advertisement Review Checklist (NASA
        Form 1580) (After design completion/ prior to advertisement)

d)  A Facilities Construction Completion Report shall be submitted no
    later than thirty (30) days following the financial completion of
    the facility project and transferred to appropriate Center's real
    property records for accountability.

13.4 **FORMAT**: Contractor format is acceptable. All documents must be
provided in both electronic and hard copy form.

13.5 **MAINTENANCE**: Project documentation shall be updated as
required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 327 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.6.2

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Government Property Inventory, Record Verification, and
Utilization Plan

7\. **DESCRIPTION/USE**: To describe the contractor's processes,
resources, and baseline schedule for physical inventory, record
verification, and utilization reviews of government property held by the
contractor, including subcontractors.

8\. **DISTRIBUTION**: Government Program Property Administrator

9\. **INITIAL SUBMISSION**: Plan and reporting matrix formats due 90
days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Status Reports due semiannually at
Property Status Reviews (PSR); Schedule due August 1st previous to each
fiscal year.

11\. **REMARKS**: None

12\. **INTERRELATIONSHIP**: SOW 1.1.6.2

13\. **DATA PREPARATION INFORMATION**: None.

13.1 **SCOPE**: This Plan defines the contractor's processes, resources,
and schedule to ensure that all Government property under the contract
is identified, recorded, and verified.

13.2 **APPLICABLE DOCUMENTS**: None.

13.3 **CONTENTS**: This plan shall address at a minimum the following
categories, including milestones, validation documentation, progress
matrixes, and status reporting.

Records & Utilization/Consumption:

Perform walkthroughs to:

Verify Government property on record

Identify Government property not on record

Identify Bench stock areas and document

Assure records are established and up to date for all Government
Property

Traceability of items to system-level assemblies

Identify items for disposal

Written justification for retention

Estimated date items will be available for disposition

Sub-contractor Control:

Perform analyses of major subcontractors to ensure all government
property is on record and accurate

Assure subcontractors are complying with Finance requirements

Assure subcontractors perform utilization reviews and process written
justification for retention

Disposition:

Assure prompt disposal of items no longer required for contract
performance.

Documentation submitted to NASA within 30 working days from declaration.

**DRD CONTINUATION SHEET**

**TITLE**: Government Property Inventory, Record Verification, **DRD
NO.**: 1.1.6.2

and Utilization Plan

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

Reports:

Develop reports/charts to status progress/milestones and results.

The plan should address submittal to the Government Program Property
Administrator an annual schedule, August 1st prior to each fiscal year,
and how changes resulting from operational access limitations will be
handled.

13.4 **FORMAT**: Contractor format is acceptable

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 328 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.6.3-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Security Management Plan

7\. **DESCRIPTION/USE**: The plan will be used to define the SPOC
security management task.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: 90 days after Authority to Proceed (ATP).

10\. **SUBMISSION FREQUENCY**: Update annually

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.6.3 and 1.1.4.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Security Management Plan shall describe the
Contractor's approach for meeting and maintaining the security integrity
of the security baseline. The plan will address the security
requirements for facilities, systems, equipment, personnel, information,
classified automated information systems, and communications, as well as
COMSEC and Secure Operations Procedures (i.e. MCC, LCC, etc.).

13.2 APPLICABLE DOCUMENTS:

FAR 52.204-2

NISPOM National Industrial Security Program Operating Manual

JSC COMSEC Maintenance Support Plan

COMSEC Logistics Control Guide

STS COMSEC Key Control Agreement

COMSEC Security Procedures (STSOC-PR-001033B)

Arms Export Control Act (AECA)

Executive Order 12958: National Security Information

National Security Decision Memorandum (NSDM) 119

Export Administration Regulations (EAR)

Internation Traffic In Arms Regulation (ITAR)

TEMPEST Countermeasures for Facilities (NTISSI 7000)

NPR 1600.1: NASA Security Program Procedural Requirements

NPD 1600.2c: NASA Security Policy

NPR 1620.2: Physical Security Vulnerability Risk Assessments

NPR 1620.3: Physical Security Requirements for NASA Facilities and
Property

NPD 1660.1: NASA Counterintelligence (CI) Policy

NPR 1660.1: Counterintelligence (CI)/Counterterrorism (CT) Procedural
Requirements

13.3 CONTENTS:

The management structure, processes and reporting requirements,
techniques and formats must be established and/or defined and documented
to insure adequate visibility and insight for NASA

**DRD CONTINUATION SHEET**

**TITLE**: Security Management Plan **DRD NO.**: 1.1.6.3-a

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

Space Shuttle Program Management and Center Security Management. The
Security Management Plan shall include: A description of the
contractor's security management structure and assignment of
responsibilities. The approach for integrating security requirements
into functions as described in the SOW (including interfacing with
subcontractors). Identification of the security interfaces with NASA,
DoD, and other government agencies and contractors. A description of the
security baseline configuration management program. The methodology for
obtaining certifications and re-certifications. The methodology for the
use of risk assessment and the processes to be implemented.

Process for developing security implementation plans as requested by
NASA for new/expanded classified systems/facilities and security
programs.

COMSEC procedures which include, but are not limited to:

a)  Issuance and transfer of COMSEC material

b)  COMSEC personnel responsibilities

c)  Opening and closing procedures for COMSEC facilities

d)  Insecurity reporting procedures

e)  Maintenance and operations procedures

f)  Inventory

g)  Emergency procedures

Secure Operations Procedures which include, but are not limited to:

a)  AUTODIN and SPADOC message transmission, receipt, storage and
    delivery

b)  Classified facsimile message procedures

c)  Opening and closing procedures

d)  Maintenance and operations procedures

e)  Emergency procedures

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 329 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.6.3-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Technology Protection Control Plan

7\. **DESCRIPTION/USE**: The plan will be used to define the SPOC
technology protection mechanisms for all SSP development and operations
activities.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: 120 days after Authority to Proceed.

10\. **SUBMISSION FREQUENCY**: Update annually

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.6.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Technology Protection Control Plan shall describe
the Contractor's approach for meeting and maintaining baseline
requirements for the protection and control of classified controlled
information, unclassified controlled information, hardware, software and
services (including export controlled and proprietary data). The plan
and the requirements contained therein apply to all industry and
academic partners, elements, activities, and locations including
operational facilities where SSP hardware, software, and data is
developed, produced, analyzed, modeled, simulated, tested, maintained,
transported, stored and operated.

13.2 **APPLICABLE DOCUMENTS**:

Federal Acquisition Regulation (FAR)

NASA FAR Supplement

NISPOM National Industrial Security Program Operating Manual

Arms Export Control Act (AECA)

Executive Order 12958: National Security Information

National Security Decision Memorandum (NSDM) 119

Export Administration Regulations (EAR)

International Traffic in Arms Regulation (ITAR)

NSTS 07700, Vol. V, Appendix F

13.3 **CONTENTS**:

The management structure, processes and reporting requirements,
techniques and formats must be established and/or defined and documented
to insure adequate visibility and insight for NASA Space Shuttle Program
Management, Center Security Management, and Center Export Control
Management. The Technology Protection Control Plan shall include:

A description of the contractor's technology protection management
structure and assignment of responsibilities. The approach for
integrating security, export control and proprietary data requirements
into functions as described in the SOW (including interfacing with
subcontractors). Identification of the interfaces with NASA, DoD, DOS,
DOC and other government agencies and contractors. A description of the
technology

**DRD CONTINUATION SHEET**

**TITLE**: Technology Protection Control Plan **DRD NO.**: 1.1.6.3-b

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

protection baseline configuration management program. The methodology
for obtaining licenses and agreements. The methodology for the use of
risk assessment and the processes to be implemented for export control
compliance.

Technology Protection Control Plans will include, but are not limited
to:

a)  Procedures for integrating Security, Export Control and Proprietary
    Data requirements/regulations

b)  Technology Protection personnel responsibilities

c)  Methodology for the application of Risk Assessment

d)  Methodology for developing, submitting and executing licenses with
    the DOC and DOS

e)  Training of employees

f)  Methodology for the communication of regulations/requirements and
    also their influence on schedule with (1) employees, (2)
    subcontractors, and (3) NASA

g)  Process for determining the category of data and procedures for
    handling different categories

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes to the plan shall be incorporated as
required by change page (revision level and date) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 330 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.6.3-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Fire Protection

7\. **DESCRIPTION/USE**: This plan will be used to define the SPOC Fire
Protection Program and compliance with applicable directives thereto.

8\. **DISTRIBUTION**: Per contracting Officer's letter.

9\. **INITIAL SUBMISSION**: 90 days after Authority to Proceed (ATP).

10\. **SUBMISSION FREQUENCY**: Update overall plan bi-annually.

11\. **REMARKS**: Plan must detailed maintenance program for all Fire
Protection systems.

12\. **INTERRELATIONSHIP**: SOW 1.1.6.3 and 1.1.4.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Contractor shall develop, document and implement the
approaches to ensure compliance with all Fire Protection codes and
standards.

13.2 **APPLICABLE DOCUMENTS**:

NASA-STD-8719.11 Safety Standard for Fire Protection

NPR 8715.3 NASA Safety Manual

National Fire Protection Association Codes and Standards

13.3 **CONTENTS**: The Contractor shall ensure that all fire protection
and Life safety systems are designed installed and maintained in
accordance with applicable codes and standards.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes to the plan shall be incorporated as
required by change page (Revision level and date) or complete reissue.
Changes will be coordinated with the government.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 331 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.7-a

3\. **DATA TYPE**: 1/2/ 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Manifest Products

7\. **DESCRIPTION/USE**: Used by the Space Shuttle Program Office in the
development of NASA flight manifest and top-level program schedules.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Twice monthly or as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.7.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Manifest Products provide data needed to support NASA
manifest and top level schedules.

13.2 **APPLICABLE DOCUMENTS**: JSC 25187, Appendix A Flight Production
Generic Template

13.3 **CONTENTS**:

Type 1: Schedule Baseline Change Request

Type 2: Space Shuttle Program Schedules, and Flight Assignment Working
Group (FAWG) Minutes Manifest Chart

Type 3: Flight Production Schedules Board (FPSB) Package, Space Shuttle
and FPSB Planning Calendars, Manifest Decision Chart, Composite Schedule
History, Launch Schedules, Manifest Assessments, Shuttle Payload
Integration and Cargo Evaluation (SPICE) Packages, Cargo Bay
Configuration Drawing for Flight Requirement Document (FRD) & FAWG
Planning Manifest.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Manifest products are prepared for each mission.
Corrections/updates are issued as revisions as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 332 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.7-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/3

6\. **TITLE**: Flight Operations Schedules

7\. **DESCRIPTION/USE**: To provide accurate and reliable implementation
planning, scheduling and assessment tools for operational use at JSC.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: In accordance with Item 13.3g

10\. **SUBMISSION FREQUENCY**: See Item 13.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Flight Operations Schedules define required
scheduling information in support of Shuttle, ISS and Payload-to-Shuttle
integration operations, and assess progress at achieving these
schedules.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: General Criteria:

a)  The contractor shall develop, maintain (update), provide and ensure
    a consistent, accurate, and stable scheduling approach that provides
    for the identification, coordination, sequencing, control,
    implementation and tracking of all operational activities and is
    easily auditable by the Government.

b)  The approach shall provide the ability to fully identify, analyze,
    mitigate and control scheduling risks and impacts; accurately
    identify, coordinate and optimize facility and resource utilization;
    identify and analyze critical path activities; and allow its users
    to easily measure the progress towards achieving the intended plan.

c)  The scheduling approach shall not only represent the scheduled work
    for that operation, but also the requirements commitment from all
    the supporting organizations.

d)  The contractor is encouraged to utilize modern manufacturing
    resource planning, industrial engineering techniques and other
    approaches, (e.g., job standardization, resource leveling and
    optimization, critical path analysis, standardized processing flow
    approaches, etc.) to ensure schedule stability, accuracy,
    reliability, predictability, and achievability.

e)  Schedule consistency shall be defined as the degree to which the
    contractor utilizes standardized scheduling approaches between
    similar processing activities and flows. Accurate scheduling shall
    be defined as the accurate representation of work content and tasks
    duration (predicted vs. actuals). A stable schedule shall refer to
    the degree to which daily schedule changes are minimized and limited
    to unforeseen hardware/software problems or NASA-directed changes.

f)  Scheduling approaches shall address the following information as a
    minimum:

    1.  Scheduling symbology that is consistent with that particular
        operational area.

    2.  Predicted task duration/labor standards derived from accurate
        and objective prediction methodologies.

    3.  Indications of activities by appropriate nomenclature that
        clearly delineates the task to be performed and any associated
        Work Authorization Documents.

**DRD CONTINUATION SHEET**

**TITLE**: Flight Operations Schedules **DRD NO.**: 1.1.7-b

**DATA TYPE**: 3 **PAGE**: 2/3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

4.  Identification of who is responsible for doing the actual work.

5.  Required supporting activities or support from other contractors,
    outside organizations, agencies or centers.

6.  Identification of critical resource requirements.

7.  Clear depiction of the interrelationships and constraints among
    related tasks.

8.  Identification of the critical path, priorities, high risk
    activities and other significant activities.

9.  NASA-approved milestones and Cargo-to-Shuttle interface activity and
    need dates.

10. Major facility/system outages/modifications/O&M activities.

11. Special test activities or requirements.

12. Identification of hazardous operations and special safety
    requirements.

```{=html}
<!-- -->
```
g)  Required data:

JSC Flight Operations Schedules (Data Type 3)

Shall cover as a minimum the following activities in addition to the
above information:

  --------------------------- ----------------------------- -------------
                              Initial Submission            Frequency

  Integrated Simulation       1200 Thursday                 Weekly
  Schedule                                                  

  SMS Schedule                10 AM Friday                  Weekly

  SSTF Schedule               10 AM Friday                  Weekly

  SST Schedule                10 AM Friday                  Weekly

  PTT Schedule                10 AM Friday                  Weekly

  Other Facility Schedules    10 AM Friday                  Weekly

  Crew Training Schedules     10 AM Friday one week prior   Weekly
                              to training start             
  --------------------------- ----------------------------- -------------

JSC Flight Crew Schedules (Data Type 3)

Shall cover as a minimum the following activities in addition to the
above information:

  --------------------------- ----------------------------- -------------
                              Initial Submission            Frequency

  a\. Astronaut Candidate     Friday 10 AM or last workday  Weekly
  Weekly Schedules            of week                       

  b\. Non-assigned Astronaut  Friday 10 AM or last workday  Weekly
  Weekly Schedules            of week                       
  --------------------------- ----------------------------- -------------

JSC ISS Program Operations Scheduling Products (Data Type 3)

Shall cover as a minimum the following activities in addition to the
above information:

  --------------------------- ----------------------------- -------------
                              Initial Submission            Frequency

  a\. Mission Operations      First month after contract    Monthly
  Integrated Schedules        ATP, on the first Monday of   
  (including electronic       month                         
  scheduling interfaces to                                  
  the ISS Program).                                         

  b\. Deliverable             First month after contract    Monthly
  dependencies based on       ATP, on the first Monday of   
  facility and product        month                         
  development schedules.                                    
  --------------------------- ----------------------------- -------------

**DRD CONTINUATION SHEET**

**TITLE**: Flight Operations Schedules **DRD NO.**: 1.1.7-b

**DATA TYPE**: 3 **PAGE**: 3/3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

JSC MOD Flight Management and Schedules Scheduling Products (Data Type
3)

Shall cover as a minimum the following activities in addition to the
above information:

  --------------------------- ---------------------------- ---------------
                              Initial Submission           Frequency

  a\. Mission Operations      First week after contract    Weekly
  Shuttle Flight Preparation  ATP                          
  Schedules                                                

  b\. Mission Operations      First month after contract   Monthly
  Space Station Flight        ATP                          
  Preparation Schedules                                    
  --------------------------- ---------------------------- ---------------

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 333 **ISSUE**: Basic 2. **DRD NO.**: 1.1.7-c

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: KSC Schedule and Status Summary (Gray Book)

7\. **DESCRIPTION/USE**: To display current KSC schedules and summary
information on aspects of the near-term manifest for Shuttle flights.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Updated as follows:

Volume I -- Monthly (May be cancelled or replaced by an alternatversion
of the Grey Book, as requested by NASA-KSC)

Executive Edition -- Weekly (May be cancelled or replaced by an
alternate version of the Grey Book, as requested by NASA-KSC)

Volumes II -- Quarterly (May be cancelled as requested by NASA-KSC)

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The KSC Schedule and Status Summary integrates KSC
planning of near-term and long range hardware, facilities, and other
resources to support schedules and manifest through transition/closeout
and infrastructure decommissioning.

13.2 **APPLICABLE DOCUMENTS**: NSTS 08178 Space Shuttle Program
Schedules

13.3 **CONTENTS**:

a)  Schedule and Status Summary, Volume I Executive Summary\--Current
    planning schedules and summary information for near-term flights,
    focus on Orbiter and Integrated SSV processing.

b)  Schedule and Status Summary, Volume I\--Same as above, but includes
    mission processing status, stand-alone element and MLP status,
    near-term follow-on flights, all remaining flights through
    transition/closeout and infrastructure decommissioning, facility
    schedules through transition/closeout and infrastructure
    decommissioning, and as-run data summaries.

c)  Schedule and Status Summary, Volume II\--KSC standard processing
    factors, assumptions and other information used for KSC manifest
    planning support. Also contains schedule enhancement analysis
    efforts and as-run data summaries.

13.4 **FORMAT**: Contractor format is acceptable with NASA approval.

13.5 **MAINTENANCE**: Changes, as required based on manifest changes,
shall be incorporated by change page or complete reissue. The Contractor
is encouraged to minimize like documentation and consolidate like
planning documentation and processes.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 334 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.7-d

3\. DATA TYPE: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight-Specific TV Plan

7\. **DESCRIPTION/USE**: The flight-specific TV Plan documents the
timeline and the configuration and operation requirements necessary to
satisfy planned video and audio events. Test and operation of new
technology/capabilities are also included.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Prior to each Flight, the requirements
are submitted for approval by Launch minus 2-days (L-2 days).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.7.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor is responsible for collecting and
documenting audio and video requirements for each Shuttle mission.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 08240 Space Shuttle Program (SSP) TV Plan

13.3 **CONTENTS**:

The specific product to be delivered is documented in the NSTS 0824 and
is as follows:

Flight-specific TV Plan

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Electronic and paper copies of all Flight-specific
TV Plans are retained in files by the contractor.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 335 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.7-f

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Flight Integration Products

7\. **DESCRIPTION/USE**: The flight specific FRDs (NSTS 17462-XX)
document Space Shuttle Program (SSP) authorized requirements for each
flight. The FRD Blank Book (NSTS 17462) is used as a guide during
preparation of the flight specific FRDs. Implementation of the
specifications defined within the FRD Blank Book ensures a consistent
definition and format for flight requirements. The FRD ISS Standard
(NSTS-17462-ISS) contains the PRCB-approved requirements for a
standardized ISS flight and is used for the preparation of the flight
specific FRDs for space shuttle flights to the ISS. Additional Flight
Integration products include the Payload pre-Launch Decision Flowchart,
Flight Card and Real Time Contact Sheet.

8\. **DISTRIBUTION**: The flight specific FRDs, the FRD Blank Book, and
FRD ISS Standard shall be delivered electronically by posting the
baseline documents and revisions to the SSP Intranet (SSP Web.) In
addition, hardcopies will be sent per the distribution list. Other
Flight Integration products specified herein are delivered
electronically.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: After the normal review process a basic
flight specific FRD shall be provided for approval immediately following
the baselining of a space shuttle mission in the Flight Definition and
Requirements Document (FDRD), NSTS 07700, Vol. III, Table 4.1. Revisions
to each document shall be performed as defined below in Section 13.5,
"Maintenance". Other Flight Integration products specified herein shall
be delivered according to the requirements defined in the associated
Product Development Plan (PDP).

11\. **REMARKS**: None

12\. **INTERRELATIONSHIP**: SOW 1.1.7.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The flight specific FRD shall define within, or by
reference, requirements to be implemented on a specific space shuttle
flight. All flight preparations shall be consistent with the
requirements specified within the FRD. The scope of other Flight
Integration Products specified herein is defined in the associated PDP.

13.2 **APPLICABLE DOCUMENTS**: NSTS 17462-XX, NSTS 17462-ISS, NSTS
17462-107 through -999. USA 009379, Product Development Plan for Flight
Integration.

13.3 **CONTENTS**: The content of the flight specific FRD is defined by
the FRD Blank Book (NSTS 17462-XX) and the FRD ISS Standard (NSTS
17462-ISS) documents and approved flight-specific change requests. The
contents of other Flight Integration products specified herein are
defined in the associated PDP.

13.4 **FORMAT**: The format of the flight specific FRD is defined by the
FRD Blank Book (NSTS 17462-XX) and the FRD ISS Standard (NSTS 17462-ISS)
documents. The format for other Flight Integration products specified
herein is defined in the associated PDP.

**DRD CONTINUATION SHEET**

**TITLE**: Flight Integration Products **DRD NO.**: 1.1.7-f

**DATA TYPE**: 1 PAGE: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.5 **MAINTENANCE**: Revisions to each flight specific FRD shall be
made as necessary to maintain the currency of the flight specific FRDs.
Revisions to the FRD Blank Book and the FRD ISS Standard shall be made
as necessary to maintain the validity of these documents as a reference
during the preparation of the flight specific FRDs. Revisions for other
Flight Integration products specified herein are defined in the
associated PDP.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 336 **ISSUE**: Basic 2. **DRD NO.**: 1.1.7-g

3\. **DATA TYPE**: 1,2,3,4 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Ground Operations Schedules

7\. **DESCRIPTION/USE**: To provide accurate and reliable implementation
planning, scheduling and assessment tools for operational use at KSC.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: See Item 13.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Ground Operations Schedules define required
scheduling information in support of Shuttle, ISS and Payload-to-Shuttle
integration operations, and assess progress at achieving these
schedules.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: General Criteria:

a)  The contractor shall develop, maintain (update), provide and ensure
    a consistent, accurate, and stable scheduling approach that provides
    for the identification, coordination, sequencing, control,
    implementation and tracking of all operational activities and is
    easily auditable by the Government.

b)  The approach shall provide the ability to fully identify, analyze,
    mitigate and control scheduling risks and impacts; accurately
    identify, coordinate and optimize facility and resource utilization;
    identify and analyze critical path activities; and allow its users
    to easily measure the progress towards achieving the intended plan.

c)  The scheduling approach shall not only represent the scheduled work
    for that operation, but also the requirements commitment from all
    the supporting organizations.

d)  The contractor is encouraged to utilize modern manufacturing
    resource planning, industrial engineering techniques and other
    approaches, (e.g., job standardization, resource leveling and
    optimization, critical path analysis, standardized processing flow
    approaches, etc.) to ensure schedule stability, accuracy,
    reliability, predictability, and achievability.

e)  *Schedule consistency* shall be defined as the degree to which the
    contractor utilizes standardized scheduling approaches between
    similar processing activities and flows. *Accurate scheduling* shall
    be defined as the accurate representation of work content and tasks
    duration (predicted vs. actuals). A *stable schedule* shall refer to
    the degree to which daily schedule changes are minimized and limited
    to unforeseen hardware/software problems or NASA-directed changes.

f)  Scheduling approaches shall address the following information as a
    minimum:

    1.  Scheduling symbology that is consistent with that particular
        operational area.

    2.  Predicted task duration/labor standards derived from accurate
        and objective prediction methodologies.

    3.  Indications of activities by appropriate nomenclature that
        clearly delineates the task to be performed and any associated
        Work Authorization Documents.

    4.  Identification of who is responsible for doing the actual work.

**DRD CONTINUATION SHEET**

**TITLE**: Ground Operations Schedules **DRD NO.**: 1.1.7-g

**DATA TYPE**: 1,2,3,4 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

5.  Required supporting activities or support from other contractors,
    outside organizations, agencies or centers.

6.  Identification of critical resource requirements.

7.  Clear depiction of the interrelationships and constraints among
    related tasks.

8.  Identification of the critical path, priorities, high risk
    activities and other significant activities.

9.  NASA-approved milestones and Cargo-to-Shuttle interface activity and
    need dates.

10. Major facility/system outages/modifications/O&M activities.

11. Special test activities or requirements.

12. Identification of hazardous operations and special safety
    requirements.

```{=html}
<!-- -->
```
g)  Required data shall cover as a minimum the following activities in
    addition to the above information:

  ----------------------------- --------------------- -------------------
                                Initial Submission    Frequency

  a\. LC-39 Overall Integrated  At contract Authority No more than one
  Processing Schedules (Type4)  to Proceed (ATP).     official product a
                                                      day.

  b\. KSC Milestone Interface   FDRD +1 mission       As required.
  Charts                                              

  c\. Detailed Element Level    10 days prior to FDRD As required.
  Assessments (Type 3)          Baseline.             

  d\. OPF Flow Processing       2 weeks prior to FDRD As required.
  Milestone Schedule (Type 3)   Baseline.             

  e\. Flow Integrated           2 weeks prior to FDRD As required.
  Operations Assessment Summary Baseline.             
  Schedule (Type 1)                                   

  f\. Integrated Test Schedules First integrated flow 5 work days prior
  (Type 3)                      after contract award. to test
                                                      Call-to-Stations,
                                                      but no less than 3
                                                      days.

  g\. Integrated Launch and     First integrated flow 8 work days prior
  Landing Schedules (Type 1)    after contract award. to
                                                      Call-to-Stations.

  h\. Assessment of all         First integrated flow Biweekly
  planned, baselined turnaround after contract award. 
  processing tasks against the                        
  as-run schedule performance                         
  (Type 4)                                            

  i\. Comparison of total       First integrated or   Biweekly
  predicted resource (direct    element flow after    
  labor hours) usage for        contract ATP.         
  planned work versus actual                          
  resources utilized throughout                       
  each element and integrated                         
  flow and reported in                                
  conjunction with the above                          
  schedule progress (Type 4)                          

  j\. Planned versus actual     First integrated or   As required.
  number of days to achieve     element flow after    
  major program level           contract ATP.         
  milestone.                                          
  ----------------------------- --------------------- -------------------

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 337 **ISSUE**: BASIC 2. **DRD NO.**: 1.1.8

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Technical Information Systems/Software Design Documents

7\. **DESCRIPTION/USE**: To define the deliverable documentation for
technical information systems software.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: For first software development or
reengineering activity

10\. **SUBMISSION FREQUENCY**: At completion of each software release

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Technical Information Systems/Software Design
Documents define the software requirements, design data elements,
database tables and baseline release contents for specific technical
information systems as defined in PDP MS7-001, Technical Information
Systems and PDP MS8-004, Engineering Information Management Maintenance.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**:

a)  [Software Development Plan]{.underline} - defines the overall
    activities required by USA007683, Technical Information Systems
    (TIS) Defined Software Process, in support of new development
    projects.

b)  [Functional Requirements Specification]{.underline} - describes at a
    high level the functionality and processes of the existing systems
    (including data maintenance and configuration management), as
    applicable. It also defines the functional requirements for the
    proposed system.

c)  [Detailed Requirements and Design Specification]{.underline} -
    expands to a detail level the functional and process requirements to
    ensure clarity for design and construction.

d)  [Data Element and Table Definition Specification]{.underline} -
    describes the database structure including the relationships between
    the various tables and the data elements within each.

e)  [Software Release Plan]{.underline} - defines the overall activities
    required by USA007683, Technical Information Systems (TIS) Defined
    Software Process, in support of maintenance releases, including a
    list of Software Work Requests.

13.4 **FORMAT**: Contractor defined electronic format, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue. Status any modifications to software
baseline release contents documentation approved by NASA.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 338 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.1-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Derived Dispersions Database Update CR

7\. **DESCRIPTION/USE**: To provide statistically reconstructed flight
data for preflight analyses that require Flight Derived Dispersions. An
SSP Change Request (CR) is required to update the configuration
controlled data.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: The Flight Derived Dispersion data shall
be reviewed and updated every 8 flights.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The database shall provide Flight Derived Dispersions
for future preflight analyses.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This data shall contain statistically calculated
reconstructed flight data that protect for Flight Derived Systems
dispersions effects. (The data is updated informally after the
completion of each post-flight assessment with SSEIG approval. Updates
to the Flight Derived Dispersion data used for pre-flight and
day-of-launch assessments are approved by the SICB and PRCB.)

13.4 **FORMAT**: Contractor\'s format is acceptable.

13.5 **MAINTENANCE**: The electronic flight derived dispersions data
shall be formally updated every eight flights.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 339 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.1-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Quick-look and Detailed Post-flight Reconstruction
Reports

7\. **DESCRIPTION/USE**: Provide ascent quick-look reports in support of
the Mission Management Team (MMT) and detailed post-flight
reconstruction reports of the ascent flight phase to ensure the "as
flown" trajectory was as predicted and within certification envelopes.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule.

10\. **SUBMISSION FREQUENCY**: The designated reports shall be generated
and submitted for each STS flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These products provide the necessary insight to the NASA
Systems Engineering and Integration Office and the MMT, anomalous
trajectory and/or integrated vehicle systems discrepancies that might
impact continued mission success or planning and execution of the next
flight in flow. Interim reports shall provide adequate fidelity to
determine anomalous ascent performance characteristics in support of
real time mission execution or flight readiness evaluations for the
upcoming mission.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: All the specified reports are Data Type 3 and are to
be delivered to the Systems Engineering and Integration Office in
support of the forums/meetings as follows:

a.  Ascent Quick-Look Report (Launch + 2 days to MMT)

b.  Final Post-Launch Ascent Assessment (Launch + 5 days to MMT)

c.  Detailed Post-Flight Reconstruction -- Interim Report (Landing + 2
    weeks to Tech Panels)

d.  Detailed Post-Flight Reconstruction -- Interim Report (Landing + 4
    weeks to SICB)

e.  Detailed Post-Flight Reconstruction -- Final Report (Landing + 12
    weeks)

13.4 **FORMAT**: Interim reports shall be briefings to the tech panels
and SICB. Format of the final report shall be contractor letter with
supporting computer files..

13.5 **MAINTENANCE**: All reports are to be retained electronically by
USA/Boeing for trending and other long-term data analyses that may be
required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 340 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.3-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Generic and Mission-Specific Shuttle Critical Math Model
and Analysis Tools (CMMAT)

7\. **DESCRIPTION/USE**: Validated and configuration controlled critical
math models are required as input data for design and verification
analyses of specific Space Shuttle payloads and cargo configurations.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Per Payload request and consistent with
ongoing submission schedule from the SFOC.

10\. **SUBMISSION FREQUENCY**: Per Payload request for each payload on
each Shuttle flight and per the current verification analysis template.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The CMMAT shall provide all critical math models used
for preflight and real-time analyses, mission design,
verification/certification activities, and/or special studies that may
be required, such as the Shuttle Integrated Thermal Math Models (ITMM),
Integration Geometric Math Models (IGMM), and Payload Thermal Math
Models for specific Shuttle payload/cargo configurations; the Shuttle
quasi-static and dynamic structural math models and forcing functions
for specific Shuttle payload/cargo configurations for all phases of
Space Shuttle missions; and the Avionics/electrical and
structural/mechanical models/tools for specific Shuttle payload/cargo
configurations. Models shall be provided and maintained in compliance
with the documents listed in 13.2.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 60534 Critical Math Model and Analysis Tools (CMMAT) Database

NSTS 37329 Structural Integration Analyses Responsibility Definition for
Space Shuttle Vehicle and Cargo Element Developers

NSTS 21522 Space Shuttle Program Guidelines for Payload Thermal
Integration

13.3 **CONTENTS**: The CMMATs are approved math models and analysis
tools identified as critical by NASA SSP management and the engineering
community. These models are mandatory for use in payload design
analyses, cargo compatibility assessments, mission design, verification
and commit to flight readiness activities. They will also be used if
applicable for hardware design, environmental definitions, and
post-flight processes as appropriate.

13.4 FORMAT: Contractor shall provide data deliverables via electronic
media formats, or on an exception basis per Contracting Officer
approval.

13.5 MAINTENANCE: Changes shall be incorporated as required by
electronic update or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 341 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.3-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Cargo Thermal and Loads Verification Analyses

7\. **DESCRIPTION/USE**: To provide passive thermal and active
thermal/Environmental Control and Life Support System (ECLSS)
verification analyses and compatibility assessments for every Space
Shuttle mission payload/cargo configuration for the planned mission
timeline; structural dynamic loads verification analysis and
compatibility assessments for every Space Shuttle mission payload/cargo
configuration, including middeck acoustic assessments; and analyses used
by payloads for verification of compatibility with Shuttle environment.

8\. **DISTRIBUTION**: The cargo thermal and structural
analysis/assessment products and revisions shall be delivered
electronically by posting to the SSP Intranet website. Hardcopies shall
be provided as requested.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Thermal and structural loads
compatibility assessments are due at CIR. Passive thermal report is due
five months prior to launch (L-5). Active/ECLSS report is due five
months prior to launch (L-5). Passive thermal and active thermal/ECLSS
final documentation is due one month prior to launch (L-1). Loads data
dump is due five and one-half months prior to launch (L-5.5). Loads
reports are due four and one-half months prior to launch (L-4.5) and one
month prior to launch (L-1). Integrated middeck acoustics assessments
are due two months prior to launch (L-2). These delivery schedules apply
for every Shuttle mission and may only be adjusted if payload models are
not received in time to support, or as otherwise authorized by the
Contracting Officer's Technical Representative (COTR) or designated
representative.

11\. **REMARKS**: Payload structural dynamic math models will be
furnished by the payload developer and provided to the contractor at
approximately seven and one-half months prior to launch (L-7.5). Payload
thermal math models will be furnished by the payload developer and
provided to the contractor at approximately nine months prior to launch
(L-9). Middeck payload acoustic test data will be furnished by the
payload developer and provided to the contractor at approximately two
and one half months prior to launch (L-2.5).

12\. **INTERRELATIONSHIP**: SOW 1.2.1.3.3; 1.2.1.3.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Results of passive thermal and active thermal/ECLSS
analyses of the Space Shuttle and the designated payloads/cargo for each
mission, both in the payload bay and in the Orbiter cabin. Results of
structural dynamic and quasi-static loads analyses of the Space Shuttle
and payloads/cargo for each mission; results of integrated middeck
acoustics assessments for each mission.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 37329 Structural Integration Analyses Responsibility Definition for
Space Shuttle Vehicle and Cargo Element Developers

NSTS 21522 Space Shuttle Program Guidelines for Payload Thermal
Integration

**DRD CONTINUATION SHEET**

**TITLE**: Cargo Thermal and Loads Verification Analyses **DRD NO.**:
1.2.1.3-b

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS**:

Thermal analyses shall include the following elements:

a)  Summary of the Orbiter/payload/cargo/spacecraft models utilized (as
    applicable in the analysis).

b)  Summary of the selected analysis mission phases (may include
    prelaunch, launch, on-orbit, entry, and post-landing).

c)  Pertinent temperature data/history plots for the analyzed mission
    phases.

d)  Assessment of the thermal interface compatibility of the
    Orbiter/payload/cargo/ spacecraft for the planned mission timeline.

e)  For cargoes where the results of previous thermal analyses are
    applicable and integrated thermal compatibility analysis can be
    eliminated, the documentation shall consist of a description of the
    previous and current configurations, a summary of previous
    analytical results, and an assessment of the
    Orbiter/payload/cargo/spacecraft thermal compatibility.

f)  An integrated thermal compatibility assessment of the Orbiter/ISS
    docked phase attitude timeline and thermal control system
    performance.

g)  A compatibility assessment of payload venting effects into the cargo
    bay.

Each loads verification analysis shall include:

a)  Modal coupling of the Space Shuttle and payloads/cargo for lift-off
    and landing configurations.

b)  Modal and coupled Orbiter/payload lift-off and landing load
    responses.

c)  Orbiter/payload attachment points loads and payload loads.

d)  Quasi-static load and deflection analysis for all selected
    conditions.

e)  On-orbit coupled loads if applicable.

f)  Secondary payloads stress and loads analysis.

g)  Middeck integrated acoustic assessment.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
electronic update or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 342 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.3-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Safety Evaluation of Orbiter Services for Payload Use

7\. **DESCRIPTION/USE**: Safety evaluations of payload planned use of
Orbiter-provided services to identify possible payload-to-Orbiter
interface hazards. The evaluations are based on payload customer Safety
Assessment Reports and are used by the cargo integration member of the
Safety Review Panels.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Five (5) working days prior to the
scheduled meeting of Payload Safety Review Panel (PSRP)/ISS Safety
Review Panel (SRP) or delay justification provided.

11\. **REMARKS**: The Shuttle/ISS Payload Safety Assessment Reports will
be Government-furnished.

12\. **INTERRELATIONSHIP**: SOW 1.2.1.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Provides an evaluation of possible payload hazards
across the payload-to-Orbiter interfaces and assesses the potential
impact to the Orbiter and Station.

13.2 **APPLICABLE DOCUMENTS**: Payload/Station safety documentation,
MIP/PIP, and ICD/IDDs.

13.3 **CONTENTS**: Each Safety Evaluation of payload planned use of
Orbiter-provided payload services for safety critical functions shall:

a)  Interpret payloads possible hazards across the interface and assess
    impact to the Orbiter and Station.

b)  Review and determine if payload/Station hazard reports clearly
    identify safety-critical interfaces with the Orbiter (i.e., hazard
    controls/hazard control monitors).

    1.  If safety critical interfaces are implied in the safety data
        package or other documentation, those interfaces are to be
        listed in the hazard report as items for the payload
        organization to clarify.

    2.  The evaluation will mention that the safety-critical interfaces
        were not clearly identified.

c)  State whether or not the Station/payload-to-Orbiter Interface
    Control Document (ICD) or the Interface Definition Document (IDD) is
    available.

    1.  If the ICD/IDD is available, document the title, ICD/IDD number,
        and the date/revision.

        i.  Make a correlation between the identified safety-critical
            interfaces in the ICD/ IDD to the payload hazard reports or
            determine if a correlation cannot be made.

        ii. Evaluate to ensure that all Orbiter payload services and
            interfaces identified in the payload hazard reports are
            included in the ICD/IDD. If they are not included, list the
            incompatibilities in the evaluation.

**DRD CONTINUATION SHEET**

**TITLE**: Safety Evaluation of Orbiter Services **DRD NO.**: 1.2.1.3-c

for Payload Use

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3. **CONTENTS (continued)**:

2.  If the ICD / IDD is not yet available, then state that it is not
    available in the evaluation and provide an estimated date as to when
    it will be available.

```{=html}
<!-- -->
```
d)  Evaluate to assure that Orbiter failure modes and fault tolerances
    are interpreted correctly by Space Shuttle users. Determine if the
    Station/Payload Safety Assessment Reports correctly describe the use
    of Orbiter payload services required for hazard control/monitoring.
    The required Orbiter payload services that are correctly described
    are to be listed in the evaluation.

e)  Provide an overall evaluation of the completeness of the
    Station/Payload Safety Assessment Report with deficiencies
    identified.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
electronic complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 343 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.3-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Payload Environmental Impact Statement

7\. **DESCRIPTION/USE**: The payload complement for each Shuttle mission
is assessed for potential environmental impact to the earth\'s
atmosphere or population. This evaluation supports NASA Headquarters'
statements as listed in 13.2 regarding potentially adverse environmental
impacts of each Shuttle space flight mission.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Submittal provided L-9 weeks prior to
launch.

11\. **REMARKS**: The Payload Safety Assessment Reports are
Government-furnished.

12\. **INTERRELATIONSHIP**: SOW 1.2.1.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Payload Environmental Assessment relies on the
Payload Safety Assessment Report compliance data packages submitted by
each payload organization. These are examined with respect to the use of
materials which would negatively impact local or global air, land, or
water quality, as well as have predictable unfavorable effects on human
health. Additional insight into the hazardous components of each payload
is provided by the NASA Interagency Nuclear Safety Review Panel and the
JSC Toxicology Group.

13.2 **APPLICABLE DOCUMENTS**:

HDQ Ltr, MZ, 2/21/95 Payload Impact Assessments (PIA) for STS Missions

SSP, JSC, Ltr, MS3-95-054, 4/28/95 Payload Impact Assessments (PIA) for
Space Transportation System (STS) Missions

13.3 **CONTENTS**:

a)  Flight summary.

b)  Primary and secondary payload identification. Detailed Test
    Objectives and Detailed Supplementary Objectives reviewed for
    potential impact.

c)  Data source title and date.

d)  Brief payload description identifying substances of potential impact
    in each payload.

e)  Statement regarding the environmental threat from each payload.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
electronic complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 344 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.3-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Payload/Cargo Electromagnetic Effects and Radio Frequency
Compatibility

7\. **DESCRIPTION/USE**: Electromagnetic effects (EME) compatibility
analysis may include non-ionizing radiation, bonding, grounding,
lightning, electrostatic discharge (ESD), and radio frequency (RF)
management. Beat Frequency Analysis identifies potential RF threats
among payloads, International Space Station (ISS) and the Orbiter
Element RF systems during all flight phases and operations.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with on-going submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.3.6

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: EME analysis verify that the payload/cargo and Orbiter
Element requirements are satisfied and that the equipment will operate
safely in a non-interference electromagnetic and RF environment. The
products may provide rationale for changes to requirements, waivers,
exceptions, and updates to baselined payload-unique documentation.

13.2 **APPLICABLE DOCUMENTS**:

ICD-2-19001 Shuttle Orbiter/Cargo Standard Interfaces

NSTS 21000-IDD-ISS International Space Station Interface Definition
Document

NSTS 21000-IDD-SML Small Payload Accommodation Interface Definition
Document

NSTS 21000-IDD-MDK Middeck Interface Definition Document

NSTS 21288 Required Data/Guidelines for Payload/Shuttle Electromagnetic
Compatibility Analysis

NSTS 37333 The Electromagnetic Compatibility Frequency Analysis Computer
Program EMCFAB1

NSTS 37334 Electromagnetic Compatibility Frequency Analysis Computer
Program Desk Instructions

13.3 **CONTENTS**: The contractor shall provide, on a flight specific
basis, a Payload/Cargo EMC Statement, Beat frequency Analysis, and RF
Threat Assessment.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
electronic change page update or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 345 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.5-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Space Shuttle Program (SSP) Drawing Release Change
Request (CR)

7\. **DESCRIPTION/USE**: To authorize release of the Space Shuttle
Systems Drawings for each flight.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Submitted no later than 18 days following
CIR, or as otherwise authorized by the Contracting Officer's Technical
Representative (COTR) or designated representative

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.1.5.2 and 1.4.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Identify discrete configuration for each flight and
ferry flight in accordance with NSTS 07700, Volume IV, Book 1:

a)  For Flight:

V072-000001-XXX Space Shuttle System

SGD32100XXX-XXX Crew Compartment Configuration Drawing

V072-200XXX-XXX Mission Equipment Cargo Support - Launch Site
Installation

b)  For Ferry Flight:

V072-000001-XXX Space Shuttle System (Ferry Flight)

SGD32100XXX-XXX Crew Compartment Configuration Drawing (Ferry Flight)

V072-200XXX-XXX Mission Equipment Cargo Support - Launch Site
Installation (Ferry Flight)

V072-300XXX-XXX Orbiter/Shuttle Carrier Aircraft (SCA) Ferry
Configuration

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700, Volume IV, Configuration Management Requirements, Book 1

13.3 **CONTENTS**: The SSP Drawing Release Change Request contains
program drawing release to baseline vehicle configuration.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Revisions to be made as required to support
contractor's engineering releases.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 346 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.5-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Engineering Drawings and Voltage/Power Analysis Letter

7\. **DESCRIPTION/USE**: To provide flight-specific cargo integration
reference drawings and the voltage/power analysis letter necessary for
contractor and payload customers to evaluate the compatibility of the
flight cargo mix with the designated Orbiter. To provide the final cargo
integration engineering drawings required for Orbiter reconfiguration.

8\. **DISTRIBUTION**: The engineering drawings shall be released and
posted electronically to the SDS file server for access through the SSP
website. Hardcopies shall be provided as requested.

The voltage and power analysis letter shall be submitted and posted
electronically to the SSP website as part of the CIR data pack.
Hardcopies shall be provided as requested.

The Power Bus Load Diagram shall be submitted and posted electronically
to the SSP website as part of the CIR data pack. Hardcopies shall be
provided as requested.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Reference Drawings and MECSLSI -- twice
per flight (CIR datapack and FRED), new tech orders/EOs once per flight
(FRED), with updates as required.

Voltage/Power Analysis letter -- once per flight CIR datapack, with
updates as required.

Power Bus Load Diagrams will be submitted once per flight to support CIR
with updates as required. Submittal of the diagram will be accompanied
by a cover letter, dated and numbered. The diagram will be posted by USA
with CIR data.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.3.5 and 1.2.1.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Drawings are prepared in conformance with the
contractor\'s Drawing Requirements Manual and serve as the controlled
source of physical and functional information necessary to:

a)  Maintain physical and functional compatibility between the Orbiter,
    payload(s), and related payload integration hardware.

b)  Communicate applicable coordinated payload agreements with subsystem
    disciplines.

c)  Document cargo configuration of each mission/flight configuration.

The Voltage/Power Analysis letter is prepared as part of the cargo
compatibility process to determine whether the manifest is compatible
with the orbiter power subsystem. The Voltage/Power Analysis letter
shall include the following:

**DRD CONTINUATION SHEET**

**TITLE**: Engineering Drawings and Voltage/Power **DRD NO.**: 1.2.1.5-b

Analysis Letter

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.1 **SCOPE (continued)**:

a)  Summary of voltage and power analysis results listing fuel cells
    curve levels required to meet payload minimum voltage requirements
    during all mission phases.

b)  Power table summarizing payload power loads used on the analysis.

c)  Output of power analysis program.

The Power Bus Load Diagrams are simplified electrical block diagrams,
which show the mission loading of the different Orbiter power sources in
the cargo bay and the crew compartment (Primary Payload Bus, Aft Buses,
Cabin PL Buses, Aux Buses, etc).

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Engineering drawings shall include the following:

a\. Mission Equipment Cargo Support - Launch Site Installation
(V072-200XXX-XXX).

b\. Cargo Arrangement Drawing (VA72-200XXX).

c\. Electrical Interface Diagram (VD72-200XXX).

d\. Integrated Schematic (VS72-200XXX).

e\. Installation Technical Orders (M072-XXXXXX).

f\. Retention Schematic Diagram (VS70-540XXX).

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic formats, or on an exception basis per Contracting Officer
approval.

13.5 **MAINTENANCE**: Revisions to engineering drawings shall be in
accordance with contractor\'s engineering and change control system.
Changes to voltage/power letters and power bus diagrams shall be
incorporated as required by electronic change page update or complete
reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 347 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.6-a

3\. **DATA TYPE**: 1/3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: DOLILU Operations Support System (DOSS) Flight-Specific
Products

7\. **DESCRIPTION/USE**: To provide flight-specific products to DOSS for
assessment.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Each flight as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.6

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These products provide all required DOSS
flight-to-flight verification results, DOL comparison results, preflight
readiness statements, and mission-specific database definition.

13.2 **APPLICABLE DOCUMENTS**: NSTS 08329, DOLILU Operations Support
Plan

13.3 **CONTENTS**: The specific products to be delivered are documented
in NSTS 08329, Vol. VIII and are as follows (Data Type 1 unless
indicated otherwise):

a)  DOSS Database Change Request (CR) (Data Type 1).

b)  DOSS Verification Test Cases (Data Type 1).

c)  DOSS End-to-End Test (L-3 weeks) (Data Type 3).

d)  DOSS L-7 Readiness Briefing (Data Type 3).

e)  DOSS End-to-End Test (L-3 Days) (Data Type 3).

f)  DOSS Day-of-Launch Data Pack (Data Type 3).

g)  DOSS Post Flight Report (Data Type 3).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: All technical assessment results retained in DOSS
historical files for actual launches. Launch attempt data and pre-launch
test results deleted after actual launch occurs. Generic math model
updates require NASA approval.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 348 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.6-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: DOLILU Operations Support System (DOSS) Non
Flight-Specific Products

7\. **DESCRIPTION/USE**: To support periodic block updates for DOSS
software and resolution of USA/ SE&I involved DOSS anomalies.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As needed to support DOSS software
updates and resolution of anomalies.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.6

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These products provide definition and delivery of the
USA SE&I software and database updates associated with DOSS block
updates and anomaly resolution.

13.2 **APPLICABLE DOCUMENTS**: NSTS 08329 DOLILU Operations Support Plan

13.3 **CONTENTS**: The specific products to be delivered are documented
in NSTS 08329, Vol. VIII and are as follows:

DOSS block update support.

DOSS block update definition inputs.

13.4 **FORMAT**: Contractor format for briefings; Space Station Program
(SSP) Change Requests (CR's) and data format per NSTS 08329, Vol. VIII,
Appendix A.

13.5 **MAINTENANCE**: Contractor briefings maintained in Day-of-Launch
Working Group files until after first flight of block update. SSP CR's
maintained by meeting support group.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 349 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.7-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Critical Math Models Data Maintenance

7\. **DESCRIPTION/USE**: Provide and maintain validated and
configuration controlled critical math models in support of integrated
vehicle analyses and systems engineering assessments.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: The Critical Math Models Data shall be
reviewed and updated per approved SSP changes or a minimum of once a
year.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Critical Math Models Database (CMMDB) shall provide
a listing of all critical math models used for preflight Flight Margins
Assessments, real-time analyses, verification/certification activities,
and/or special studies that may be required.

13.2 **APPLICABLE DOCUMENTS**: NSTS 08209 Volume V

13.3 **CONTENTS**: The Critical Math Model Data Base (CMMDB), NSTS
08209, Volume V, provides a listing of math models identified as
critical by NASA SSP management and the engineering community. These
models are mandatory for use in mission design, Commit-to-Flight (CTF)
analysis, and Day-of-Launch (DOL) assessments. They will also be used if
applicable for hardware design, environmental definitions, and
post-flight processes as appropriate. The scope of the CMMDB is to
provide an electronic, configuration controlled source for all the
baselined CMMs information, exclusive of the actual models themselves.
Updates to the CMMDB are approved by the SICB.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: The electronic data shall be audited annually and
updated as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 350 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.1.7-d

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Ascent Debris/Transport Data

7\. **DESCRIPTION/USE**: Provide and maintain a data for all expected
and unexpected debris sources, inclusive of historical debris transport
analyses.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: The Ascent Debris/Transport data shall be
reviewed and updated per approved SSP changes and/or post flight
evaluations that dictate an update. At a minimum, the data shall be
updated once a year.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The data shall include all expected and unexpected
debris source information and previously run transport results for
pre-launch and/or post-launch evaluation of potential or detected
anomalous debris events.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Ascent Debris/Transport database(s) shall contain
all debris source and flight acceptance information as defined by the
SSP elements and reviewed/approved by the SSP. The database(s) shall
further contain all debris transport results which can easily be
searched and referenced for previous debris sources and resulting
transport trajectory impacts.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: The electronic data shall be updated once a year
and maintained by USA.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 63. **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.1-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Shuttle Weight, Performance, and Integrated Mass
Properties Data Maintenance and Status Reports

7\. **DESCRIPTION/USE**: To provide integrated mass properties data and
reports necessary to support mission-specific vehicle weight statements
and provide management insight for each mission in process, selected
reference missions, and special requests.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Weekly and/or as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall combine mass property submittals
from each element/project and maintain the data in an integrated vehicle
mass properties database. The contractor reports integrated vehicle
center-of-gravity, down weights, ascent performance, and other important
mission parameters.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The contractor shall develop and maintain the
following items:

a)  Integrated mass properties database, including all vehicle and
    mission-kit installation mass properties, estimated and calculated
    mass properties to support mission planning, upweights, downweights,
    and performance-margin data for each approved
    mission/flight/payloads configuration.

b)  Electronic file reports accessible to all Shuttle Integrated
    Accounting Status System (SIASS) users including:

    1.  Weekly Space Shuttle Vehicle (SSV) weight and performance
        database updates.

    2.  Quarterly Shuttle Systems weight and performance status report
        (NSTS 09095).

    3.  Weekly flight dynamics mission summary.

    4.  Assessment mass properties updates for Cargo Integration Review
        (CIR) and Flight Planning and Stowage Review (FPSR).

    5.  Launch Site Requirements Review (LSRR) and Launch Site Flow
        Review (LSFR) mass property briefings.

    6.  The contractor shall publish mission management report
        containing designated mission parameters.

```{=html}
<!-- -->
```
a)  

b)  1.  
    2.  
    3.  
    4.  
    5.  
    6.  

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Contractor shall maintain integrated mass
properties data on an on-going basis, using submitted mass property
data, comments discrepancy information, problem/resolutions inputs, and
mission kit data. Hard copies of each weekly update will be maintained
for at least one year.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 64. **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.2

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Trajectory Design Data Package (TDDP) and Change Notices

7\. **DESCRIPTION/USE**: To document selected mission configuration,
ground rules, vehicle performance characteristics, and data for various
flight design organizations.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Production of TDDPs is the assumption of
ongoing requirement; no break in existing submission schedule.
Submission of Change Notices (CNs) will be as required

10\. **SUBMISSION FREQUENCY**: Normally, six TDDPs are scheduled for
each mission. The initial document is published approximately 13 months
before a launch. In addition, special mission and study TDDPs may be
required. Schedule is defined by the Flight Production Schedules Board
on a per-mission basis.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The TDDP contains pertinent mission and vehicle
information used to start the flight design process as well as special
design studies and assessments. The TDDP ensures all simulation groups
use the same initiation data, constraints, and Shuttle Program
direction. CN's update pertinent mission and vehicle information
contained in a previously released TDDP.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Typical information included is: Vehicle summary
weight statement (mass properties), Space Shuttle Main Engine (SSME) tag
data, Reusable Solid Rocket Motor (RSRM) performance data, Main
Propulsion System (MPS) propellant inventories, dynamic pressure
constraints, Alpha and Beta constraints, current mission requirements
and appropriate references. Other information is included as needed per
customer direction.

Change notices shall be issued as information updates between scheduled
TDDPs.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Document preparation software is updated
semi-annually, with critical revisions made as requested by the
customer. All TDDPs will be maintained by CNs and archived. Archives
shall be maintained and archival materials dispositioned in accordance
with NASA and Federal Records Management regulations and procedures.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 353 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.3-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Adjusted Reusable Solid Rocket Motor (RSRM) Pre-flight
Computer Files

7\. **DESCRIPTION/USE**: To generate adjusted RSRM block motor
characteristics for trajectory simulations.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Adjusted RSRM Pre-flight Computer Files adjust
MSFC-provided RSRM-specific characteristics based on reconstructed
flight history.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Computer dataset with RSRM-specific characteristics.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: A historical file shall be maintained by the
contractor.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 354 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.3-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Main Propulsion System (MPS) Inventory/Budget Update and
Documentation

7\. **DESCRIPTION/USE**: To document the loading and consumption of MPS
propellants in the External Tank.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: MPS inventory/budget documents the loading and
consumption of MPS propellants in the External Tank.

13.2 **APPLICABLE DOCUMENTS**: NSTS 08209, Vol. I, Shuttle Performance
Assessment Data Book

13.3 **CONTENTS**: MPS loading and consumption for NOM,
AOA/Trans-Atlantic Landing (TAL), and Return to Launch Site (RTLS).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: NSTS 08209, Volume 1, will be updated by the
contractor as required to provide current inventory as well as
historical cross-reference of MPS inventory versus Shuttle
Transportation System (STS) mission. Archives shall be maintained and
archival materials dispositioned in accordance with NASA and Federal
Records Management regulations and procedures.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 355 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.4-a

3\. **DATA TYPE**: 1, 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Annex 1 - Payload Data Package.

7\. **DESCRIPTION/USE**: To be used by contractor and payload customer
as an agreed-to source for the payloads configuration, weight and mass
properties, avionics, and physical function data for installation,
deployment, and/or retrieval of the payload as related to the Orbiter.
The Annex 1 substantiates the as-built payload properties to the
agreed-to design interfaces as described in the payload unique ICD.

8\. **DISTRIBUTION**: The Annex 1 payload specific and blank book
baseline documentation and revisions shall be delivered and posted
electronically to the SSP website. Hardcopies shall be provided as
requested.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Three times per payload per flight and
update as required.

11\. **REMARKS**: Drawings referenced in the payload annex shall be
maintained in a central payload data facility or electronic database for
review and distribution of reference payload data.

12\. **INTERRELATIONSHIP**: SOW 1.2.2.4.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This package provides annexes for all payloads and
payload equipment flying in the cargo bay.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 21000-A01 Payload Data Package Blank Book Annex 1 -- Type 1

NSTS XXXX-A01 Unique Payload Data Package Annex -- Type 3

13.3 **CONTENTS**: Annex 1 - Payload Data Package shall contain:

a)  Payload Configuration.

b)  Weight and Mass Properties.

c)  Payload Physical Function Data.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by electronic change
page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 356 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.5-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Interface Revision Notice (IRN) to Systems Interface
Control Documents (ICDs).

7\. **DESCRIPTION/USE**: To define changes to System ICDs.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Following each NASA-approved IRN.

11\. **REMARKS**: ICD's define the technical interfaces between the
Shuttle System and other systems, and between elements of the Shuttle
System.

12\. **INTERRELATIONSHIP**: SOW 1.2.2.5.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The IRNs define changes to functional and/or physical
interfaces (1) between the Shuttle System, or elements thereof, and
other systems, or elements thereof, and (2) between Shuttle System
elements involving two or more major program participants, i.e., NASA
Centers, System Contractor, Associate/Element Contractors. IRNs are
limited to the applicable documents listed in 13.2.

13.2 **APPLICABLE DOCUMENTS**:

ICD-13M15000 Space Shuttle Orbiter Vehicle/Main Engine

ICD-2-0A001 Shuttle System/Launch Platform Stacking and VAB Servicing

ICD-2-0A002 Space Shuttle Launch Pad & Platform

ICD-2-0A003 Flight Vehicle/LPS Computational Systems Interfaces

ICD-2-0A004 Space Shuttle System/KSC RF Communications & Tracking

ICD-2-0D003 JSC/USAF Space Shuttle/SCF RF Communications & Tracking

ICD-2-0D004 JSC/GSFC Space Shuttle RF Communications & Tracking

ICD-2-0H001 Shuttle Vehicle/Ground Range Safety System

ICD-2-00001 Shuttle Vehicle Mold Lines and Protuberances

ICD-2-1A001 Orbiter/KSC Landing Station

ICD-2-1A002 Orbiter Processing Facility/Orbiter Maintenance & Checkout
Facility

ICD-2-1A003 Orbiter /Hypergolic Station

ICD-2-1D003 Orbiter Landing/Safing & Deservicing Stations

ICD-2-1D004 Orbiter & Carrier Aircraft/Mate-Demate Interfaces

ICD-2-12001 Orbiter Vehicle/External Tank

ICD-2-14001 Orbiter Vehicle/Solid Rocket Booster

ICD-2-17001 Orbiter Vehicle/Carrier Aircraft

ICD-2-2A001 External Tank/Receiving, Storage & Checkout Station

ICD-2-24001 External Tank/Solid Rocket Booster

ICD-2-4A001 Solid Rocket Booster/Receiving Processing Station

**DRD CONTINUATION SHEET**

**TITLE**: Interface Revision Notice (IRN) to Element **DRD NO.**:
1.2.2.5-a

Interface Control Documents (ICDs).

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS**: IRNs shall contain functional and/or physical
interface requirements and rationale in sufficient detail to provide an
adequate baseline for planned design efforts by the interfacing
elements. Design requirements/constraints contained in the IRNs are
limited to only those necessary to define and control the subject
interface(s).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: ICDs to be maintained by IRN incorporation or
total reissuance as applicable. The contractor shall prepare changes,
coordinate technical review, resolve issues with the technical
community, and present changes to NASA for disposition.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 357 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.5-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Preliminary Interface Revision Notice (PIRN) and
Interface Revision Notice (IRN) to Program Requirements Interface
Control Document (ICD) (CORE) and Interface Definition Documents (IDDs).

7\. **DESCRIPTION/USE**: To propose and define changes to Program
Requirements ICD (CORE) and IDDs.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: PIRNs are submitted against the CORE and
IDDs as necessary to define and refine program requirements.

11\. **REMARKS**: The CORE and IDDs are design-to documents that define
Orbiter provided interfaces and services available to the payload, and
establish commonality with respect to analytical approaches, models,
technical data and definitions for integrated analysis. Payload unique
ICDs are built from the CORE or IDD requirements.

12\. **INTERRELATIONSHIP**: SOW 1.2.2.5.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: PIRNs and IRNs define changes to interfaces and/or
services provided by the Orbiter to the payload, or in analytical
methods. PIRNs and IRNs are limited to the applicable documents listed
in 13.2.

13.2 **APPLICABLE DOCUMENTS**:

ICD-2-19001 Shuttle/Orbiter/Cargo Standard Interfaces (CORE)

NSTS21000-IDD-ISS International Space Station Interface Definition
Document

NSTS21000-IDD-MDK Shuttle/Payload Interface Definition Document Middeck
Accommodations

NSTS 21000-IDD-SML Shuttle/Payload Interface Definition Document for
Small Payload Accommodations

13.3 **CONTENTS**: PIRNs/IRNs shall contain functional and/or physical
interface requirements and rationale in sufficient detail to provide an
adequate baseline for planned design efforts by the interfacing
elements. Design requirements/constraints contained in the PIRNs/IRNs
are limited to only those necessary to define and control the subject
interface(s).

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media, or on an exception basis per Contracting Officer
approval.

13.5 **MAINTENANCE**: The CORE and IDDs are maintained through the
PIRN/IRN process as defined in the applicable PDP. Changes shall be
incorporated as required by electronic change page update or complete
reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 358 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.6

3\. **DATA TYPE**: 1 and 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Payload Unique Interface Control Documents (ICDs) and
Installation Requirements Documents (IRDs).

7\. **DESCRIPTION/USE**: ICDs define the technical interfaces agreed to
between the Space Shuttle Vehicle (SSV) and the unique payload or ISS
on-orbit assembly. ICDs provide necessary requirements for interface
definition to support integration hardware design, payload design and
flight product development. IRDs define the installation assembly
requirements for the installation of payload-to-payload elements within
the Orbiter by the Space Shuttle Program. An IRD is not required for
payloads that are fully assembled prior to installation into the
Orbiter.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Payload ICDs and IRDs are submitted per
payload and with updates as required. On-Orbit ICDs are submitted once
per mission and with updates as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.6

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The payload-unique ICDs provide definition of the
technical interfaces between the SSV and the unique payload for selected
configurations of the payload as applicable. The ISS On-Orbit ICDs
provide definition of the technical interfaces between the SSV and the
ISS On-Orbit assembly. The payload IRDs provide definition of the
installation and assembly requirements of payload-to-payload interfaces
in the Orbiter. ICDs and IRDs are derived from the applicable documents
as appropriate.

13.2 **APPLICABLE DOCUMENTS**:

NSTS-07700, Volume IV, Book 1, Configuration Management Requirements

ICD-2-19001 Shuttle Orbiter/Cargo Standard Interfaces (CORE)

Attachment I (ICD-2-19001)

NSTS-21000-IDD-SML Shuttle/Payload Interface Definition Document for
Small Payload Accommodations

NSTS-21000-IDD-MDK Shuttle/Payload Interface Definition Document for
Middeck Accommodations

NSTS-21000-IDD-ISS International Space Station Interface Definition
Document

ICD-A-XXXXX Payload Unique ICD, Type 3

ICD-A-XXXXX-OOR Payload Unique On-Orbit ICD, Type 1 (NASA concurrence)

IRD-XXXXX Payload Unique IRD , Type 3

13.3 **CONTENTS**: The contents are based on the applicable documents as
appropriate.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: ICDs and IRDs are maintained through the PIRN/IRN
process as defined in the applicable PDP. Changes shall be incorporated
as required by electronic change page update or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 359 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.7

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Payload Operations and Maintenance Requirements and
Specifications (OMRS) Test Requirements.

7\. **DESCRIPTION/USE**: To provide the OMRS pre-mate and post-mate test
requirements for verification of Space Station Program (SSP) hardware
interfaces with the payload to satisfy NSTS 14046, Section 5.3.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Per Flight: File II, Volumes 2 and 6,
submittal per current template, basic RCN release at CIR -- 1 month,
Baseline approval date release determined by Payload OMRS Working Group
(POG) during CIR. Update as necessary. File II, Volume 4 RCNs will be
baselined at FRED + 1 month. Update as necessary.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.7.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Integrated OMRSD File II, Volumes 2, 4, and 6 cover
requirements for verification of interfaces and related operational
requirements of installed hardware supporting payloads, Detailed
Supplementary Objectives (DSOs), Payload and Developmental Test
Objectives (DTOs) requirements, Human Exploration and Development of
Space Technology requirements (HTDs), and applicable Requirements Change
Notices (RCNs).

13.2 **APPLICABLE DOCUMENTS**:

NSTS-08171, Files I, II and III, Operations and Maintenance Requirements
and Specification Document

NSTS 14046, Payload Verification Requirements

13.3 **CONTENTS**: RCNs for the OMRSD shall include requirement numbers,
descriptions, measurement/stimuli identification, specification
(pass/fail criteria) and internal/constraints/ remarks information as
defined in NSTS 08171, File I.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats, or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: OMRSD shall be changed/maintained using RCNs as
described in NSTS 08171, File I.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 360 **ISSUE**: Basic 2. **DRD NO.**: 1.2.2.7-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Middeck Payloads Time-critical Ground Handling
Requirements (TGHR) Table.

7\. **DESCRIPTION/USE**: Interface with the payload customers/experiment
sponsors to develop, baseline and maintain the mission-unique TGHR
Table.

8\. **DISTRIBUTION**: The review draft of the TGHR Table is distributed
for review via e-mail and the baselined TGHR table and subsequent
revisions are maintained on the TGHR Table web page. The distribution
list is maintained by USA.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Initial Input at L-4 months, draft
release at L-3 months, baseline at L-2 months, update as necessary, up
to launch minus 1 day for pre-launch requirements and landing minus 1
day for post-landing requirements.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.7.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Time-critical Ground Handling Requirements Table
documents mission-unique payload/experiment time-critical and schedule
driven crew compartment requirements to be performed at the launch and
landing sites.

13.2 **APPLICABLE DOCUMENTS**:

Mission Unique TGHR Table

NSTS 08171, Files I and II, volumes 2 and 6

13.3 **CONTENTS**: TGHR Tables include requirements for late stow, power
interrupts, orientation constraints, early destow, locker location, and
part numbers as defined in PDP MS3-012 and the TGHR Table Integration
Engineer's Handbook.

13.4 **FORMAT**: Contractor shall provide data deliverables via
electronic media formats or on an exception basis per Contracting
Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by electronic change
page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 361 **ISSUE**: BASIC 2. **DRD NO.**: 1.2.2.10-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Technical Revision to SL-E-0001 and SL-E-0002

7\. **DESCRIPTION/USE**: Management and maintenance of SL-E-0001 and
SL-E-0002 will be conducted in support of, and in direct coordination
with, the NASA Space Shuttle Electromagnetic Environmental Effects (E3)
Control Technical Panel with approval from the Systems Integration
Control Board (SICB).

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.2.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The products provide changes to requirements, waivers,
deviations and exceptions, and associated rationale for the proposed
modifications.

13.2 **APPLICABLE DOCUMENTS**:

SL-E-0001 Specification Electromagnetic Compatibility Requirements

SL-E-0002 Specification Electromagnetic Interference Characteristics,
Requirements for Equipment

Book 1 - Existing Hardware

Book 2 - New or Modified Hardware

13.3 **CONTENTS**: The contractor shall conduct Technical Interchange
Meetings to establish new requirements. Appropriate change requests
shall be documented and processed through the appropriate Space Shuttle
Program (SSP) board/panel.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 362 **ISSUE**: BASIC 2. **DRD NO.**: 1.3-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Mission Assurance Plan

7\. **DESCRIPTION/USE**: To describe the contractor's plan for meeting
the safety and mission assurance requirements, including system safety,
reliability, and maintainability, of NSTS 07700, volume X, book 1; and
NSTS 5300.4 (1D-2).

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Contract award plus 60 days

10\. **SUBMISSION FREQUENCY**: As required to document updates and
changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Develop/compile, maintain, and distribute technical data
as defined in the applicable documents.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700, Vol X, Bk 1, Space Shuttle Flight and Ground System
Specification

NSTS 5300.4 (1D-2), Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program

13.3 **CONTENTS**: The plan shall describe the implementation of the
policies and processes related to safety and mission assurance at each
site where the contractor is operational to assure the identification,
evaluation and elimination/control of safety and mission assurance
issues throughout the complete life cycle (design, development,
manufacture, test, operations, maintenance, and disposal) of the
associated hardware. As a minimum, the plan shall include the following:

a)  Organization charts which illustrate the functional relationships
    and lines of communication between the mission assurance
    organization, CEO and other organizational elements.

b)  Descriptions of the management functions within the organization
    including the process through which management decisions will be
    made.

c)  Description of the responsibility, authority, and accountability of
    mission assurance personnel.

d)  Description of the system safety review process leading to the
    Certificate of Flight Readiness (COFR)

e)  Description of the boards and panels controlled by the mission
    assurance organization.

f)  Description of surveillance methodology, metrics and/or leading
    indicators used by the mission assurance organization to maintain
    insight/oversight of the mission assurance function throughout the
    contractor organization.

g)  Description of flow down of NSTS 5300.4 (1D-2) requirements to
    organizational elements including verification method to ensure
    requirements have been met.

**DRD CONTINUATION SHEET**

**TITLE**: Mission Assurance Plan **DRD NO.**: 1.3-a

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 363 **ISSUE**: BASIC 2. **DRD NO.**: 1.3-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Safety and Health Plan

7\. **DESCRIPTION/USE**: To describe the contractor's safety and health
plan for each NASA site.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Contract award plus 60 days.

10\. **SUBMISSION FREQUENCY**: As required to document updates and
changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: Clause H.22, SOW 1.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Applicable to all NASA centers and sites where the
contractor is operational.

13.2 **APPLICABLE DOCUMENTS**:

NPR 8715.3 NASA Safety Manual

29 CFR 1910 Department of Labor

NPR 8715.1 NASA Safety and Health Handbook Occupational Safety and
Health Standards Programs

29 CFR 1960 Basic Program Elements for Federal Employee Occupational
Safety and Health Programs and Related Matters

13.3 **CONTENTS**: The plan shall describe tasks and activities of
safety and health management at each site where the contractor is
operational to assure the identification, evaluation and
elimination/control of safety and health concerns. As a minimum, the
plan shall include the following:

a)  Organization charts(s) which illustrate the functional relationships
    and lines of communication between safety, the Safety and Health
    organization and other organizational elements.

b)  Descriptions of the Safety and Health management function within the
    organization including the process through which management
    decisions will be made, including notification of the local NASA
    Safety and Health organization of critical and catastrophic hazards,
    corrective actions, mishaps and deviations or waivers to NASA safety
    and health requirements.

c)  Description of the responsibility, authority, and accountability of
    Safety and Health personnel, other contractor organizational
    elements involved in the safety and health effort and subcontractor
    safety and health personnel. Include the organizational unit
    responsible for the execution of safety and health tasks and the
    position with the authority to resolve all identified safety and
    health issues.

d)  Description of the management controls that will be used to ensure
    compliance with safety and health regulations.

e)  Cross-reference of safety program requirements (e.g., OSHA, NASA,
    local NASA Center, State) and contractor procedures to avoid
    duplication of effort.

f)  Description of the safety program measurement system, including
    measurements, metrics, and trend analysis methods. The performance
    measurement system should describe responsibility for identifying
    and implementing remedial action, recurrence control, and corrective
    actions that are necessary to improve performance as indicated by
    the performance measurement system.

**DRD CONTINUATION SHEET**

**TITLE**: Safety and Health Plan **DRD NO.**: 1.3-b

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 76A. **ISSUE**: BASIC 2. **DRD NO.**: 1.3.1.1-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Hazards Analysis

7\. **DESCRIPTION/USE**: Maintain the Integrated Hazard Analysis for
Integrated Hazard Reports contained in WebPCASS.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter

9\. **INITIAL SUBMISSION**: Upon Request.

10\. **SUBMISSION FREQUENCY**: Upon Request.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3.1.1; DRD 1.3.1.1-b and 1.3.1.1-c

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Integrated Hazards Analysis is a supplement to the
Integrated Hazard Reports and Verification Tracking Logs. It contains
supporting data and information used in the development of the
Integrated Hazard Report. It also contains the applicable revision
levels for the referenced documents contained in the Integrated Hazard
Reports. It contains information relative to in-flight anomalies,
nonconformances, and SSP approved changes that impact the Integrated
Hazard Analysis and Reports. Evaluation of changes is required on a
flight specific basis to maintain technical accuracy and SSP risk
awareness.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 22254 Methodology for Conduct of Space Shuttle Program Hazard
Analyses

13.3 **CONTENTS**: The Integrated Hazard Analysis contains items such
as:

a)  List of reference documents and the Revision level that the Hazard
    Report is based on.

b)  Any associated documents that are not part of the SSP baseline
    (e.g., white papers, test reports, technical presentations.)

c)  List of associated failure history, including PRACA references.

d)  Any other supporting data that is pertinent to the baselined Hazard
    Report.

13.4 **FORMAT**: Consistent with the format and media type of original
supporting data and information used in the development of the
Integrated Hazard Report.

13.5 **MAINTENANCE**: Provide technical support, prepare analysis,
coordinate technical reviews, and maintain data.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 76B. **ISSUE**: BASIC 2. **DRD NO.**: 1.3.1.1-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Integrated Hazards Reports

7\. **DESCRIPTION/USE**: Maintain the Integrated Hazard Reports,
including the corresponding Fault Trees contained in WebPCASS.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter

9\. **INITIAL SUBMISSION**: Per approved schedule

10\. **SUBMISSION FREQUENCY**: As required by NSTS-22254.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3.1.1; DRD 1.3.1.1-a and 1.3.1.1-c

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Integrated Hazards Reports identify hazards to
personnel, vehicle, and other systems associated with the integrated SSV
and its associated interfaces. This includes the delineation of
responsibilities at the cause level and the technical coordination of
the integrated hazards with the projects/elements to ensure
completeness, establish an integrated effort, and to avoid overlaps and
conflicts among the technical disciplines.

Integrated hazard reports are developed for risk causes that cross
element interfaces and impact the integrated vehicle performance.
Additionally, integrated hazard reports are written when controls from
one or more SSP elements are required are written when controls from one
or more SSP elements are required to control a risk cause in another
element. The contractor maintains integrated fault trees as basis for
identifying integrated risk causes that require controls.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 22254 Methodology for Conduct of Space Shuttle Program Hazard
Analyses

13.3 **CONTENTS**: The contents should be consistent with NSTS 22254,
including the follwoing:

a)  Fault Tree: Developed down to the level where integrated controls
    are applied or element accountability is assigned.

b)  Mission Phase

c)  Risk Matrix: Maps integrated causes and open work.

d)  Hazardous Condition Description: Include a list of hazard reports
    whose effects are controlled in this hazard report.

e)  Acceptance Rationale

f)  Likelihood Justification: Includes justification for each cause/open
    work contained in the IHR risk matrix.

**DRD CONTINUATION SHEET**

**TITLE**: Integrated Hazards Reports **DRD NO.**: 1.3.1.1-b

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

g)  Fault Tree Description: Executive summary of fault tree major
    components.

h)  Causes Summary: Includes responsible organization for each cause,
    and which causes are classified as accepted risk.

i)  Causes/Hazard Assessment: Includes cause ID, cause title, associated
    fault tree block, description, effect, severity, likelihood,
    control, and verification.

j)  Open Work: Includes action (defined by PRCBD), acceptance rationale,
    severity, likelihood, classification, element controls, element
    verifications, and flight effectivity (flight(s) for which the
    acceptance rationale applies).

k)  References

l)  Background

m)  Undeveloped Events: A list of the fault tree events not documented
    in the Cause/Hazard Assessment section and associated justification.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: The contractor shall provide technical support,
prepare evaluations, coordinate technical review, and maintain data.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 76C. **ISSUE**: BASIC 2. **DRD NO.**: 1.3.1.1-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Hazards Report Verification Tracking Log (VTL)

7\. **DESCRIPTION/USE**: Develop and maintain Verification Tracking Logs
for each Integrated Hazard Report.

8\. **DISTRIBUTION**: Per Contracting Officer\'s Letter

9\. **INITIAL SUBMISSION**: A VTL is required for each Integrated Hazard
Report at FRR.

10\. **SUBMISSION FREQUENCY**: A VTL is required for each Integrated
Hazard Report at FRR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3.1.1; DRD 1.3.1.1-a and 1.3.1.1-b

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The VTL is a consolidated closed loop record of all
issues pertinent to the Integrated Hazards . The VTL provides a status
of liens against the Integrated Hazard Reports for reporting at FRR.
Included in the VTL are in-flight anomalies, nonconformances, and SSP
changes that impact the Integrated Hazard Analysis and Reports.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 22254 Methodology for Conduct of Space Shuttle Program Hazard
Analyses

13.3 **CONTENTS**: The VTL contains items pertinent to the Integrated
Hazard and are tracked against a specific flight. VTL items include SSP
changes such as IFAs, CRs, LCNs, IRNs, Testing, Flight Rules Changes,
Analysis, and hardware design changes. Each VTL is for a specific Hazard
Report and includes a Description, Applicable Flight, Impact Assessment,
Closure Status.

13.4 **FORMAT**: Conform to delivery media formats and electronic data
formats per DRD 1.1.4.1-e, Data Management Plan, or per Contracting
Officer approval.

13.5 **MAINTENANCE**: Provide technical support and maintain a current
VTL for each Hazard Report.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 364 **ISSUE**: BASIC 2. **DRD NO.**: 1.3.1.2-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Safety Summary Report (SSR)

7\. **DESCRIPTION/USE**: To provide information to each NASA location on
accidents affecting the contractor\'s performance.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: By the 15th of the second month after
contract award

10\. **SUBMISSION FREQUENCY**: Monthly, on or before the 15th of each
month, for the previous month

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Safety Summary Report provides information on
accidents affecting the contractor's performance.

13.2 **APPLICABLE** **DOCUMENTS**: None

13.3 **CONTENTS**: The SSR shall contain the following information for
each NASA location monthly:

a)  Number of man-hours worked.

b)  Number of new Day Away From Work cases.

c)  Number of days away from work for the month (including previous
    month\'s cases from the current fiscal year reporting period).

d)  Number of Restricted Duty or Job Transfer cases.

e)  Number of restricted or job transfer days.

f)  Number of Remained at Work (Other Recordable) cases.

g)  Number of first aid cases.

h)  Number of miles driven in Government-provided vehicles.

i)  Number of vehicle accidents with damage greater than \$1000.

j)  Total damage cost due to motor vehicle accidents resulting in damage
    \> \$1,000.

k)  Number of accidents which resulted in NASA property damage greater
    than \$1000.

l)  Total damage cost to NASA property as a result of accident resulting
    in damage \> \$1,000.

m)  Number of Incident Reports (NASA form 1627 or equivalent) for
    incidents which occurred during the reporting period.

n)  Status on all open incident reports from previous months of the
    current fiscal year.

o)  Number and report on any OSHA or EPA violations or inspections.

p)  Number of non-SPOC personnel injured during SPOC operations and
    summary status.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 365 **ISSUE**: BASIC 2. **DRD NO.**: 1.3.1.2-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Pressure Vessel/System Recertification

7\. **DESCRIPTION/USE**: Data required to demonstrate implementation of
NMI 1710.3 using the guidelines of NHB 1700.6, on insurance that all
ground-based pressure vessels and pressurized systems are certified safe
to operate and are recertified periodically.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after contract award

10\. **SUBMISSION FREQUENCY**: Annually

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Pressure Vessel/System Recertification covers all
ground-based pressure vessels and pressurized systems under the
contractor's responsibility.

13.2 **APPLICABLE DOCUMENTS**:

NMI 1710.3 Safety Program for Pressure Vessels and Pressurized Systems

NHB 1700.6 Guide for In-service Inspection of Ground-Based Pressure
Vessels and Systems

13.3 **CONTENTS**: In accordance with guidelines in NHB 1700.6.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. DPD NO.: 366 ISSUE: BASIC 2. DRD NO.: 1.3.1.2-d

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/3

6\. TITLE: Annual Safety Program Evaluation

7\. DESCRIPTION/USE: To provide an assessment to each NASA location on
the effectiveness of the contractor's safety and health management
system.

8\. DISTRIBUTION: Per Contracting Officer\'s letter

9\. INITIAL SUBMISSION: By the 15th of February of the first calendar
year following contract issue.

10\. SUBMISSION FREQUENCY: Annually, on or before the 15th of February,
for each calendar year

11\. REMARKS:

12\. INTERRELATIONSHIP: SOW 1.3.1.2

13\. DATA PREPARATION INFORMATION:

13.1 SCOPE: The Safety Program Evaluation provides information on the
effectiveness on the contractor's safety and health management system.

13.2 APPLICABLE DOCUMENTS: None

13.3 CONTENTS: The evaluation must include assessments of the
effectiveness of all elements and sub-elements of the participant\'s
safety and health management system. The evaluation includes reviewing
written programs, walking through the workplace, and interviewing
employees. During this process participants should be answering the
following questions relating to each element and sub-element of their
safety and health management system:

a)  Is it comprehensive?

b)  Is it operating effectively and meeting established goals and
    objectives?

c)  What improvements can be made to make it even more effective?

d)  What goal modifications should be made for the upcoming year?

13.4 The written Annual Evaluation shall contain the following
information:

a)  Injury and Illness rate information (See Attachment 1)

b)  Significant changes or events in the Safety & Health Program. Note:
    Describe the impact of any significant changes (management,
    corporate buy-outs, etc.) and events (fatality, catastrophe,
    accident, complaints, etc.) and steps taken to ensure or restore
    worker safety and health.

c)  Narrative Evaluation of Safety and Health Management System. Note:
    In narrative form, assess the effectiveness of each of the four
    elements and their sub-elements in your safety and health management
    system.

    1.  Management Leadership and Employee Involvement

        i.  Management Commitment to Safety and Health Protection and to
            VPP Participation

        ii. Policy

        iii. Goals, Objectives, and Planning

**DRD CONTINUATION SHEET**

**TITLE**: Annual Safety Program Evaluation **DRD NO.**: 1.3.1.2-d

**DATA TYPE**: 2 **PAGE**: 2/3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

iv. Visible Top Management Leadership

v.  Responsibility and Authority

vi. Line Accountability

vii. Resources

viii. Employee Involvement

ix. Contract Worker Coverage

x.  Written Safety and Health Management System

```{=html}
<!-- -->
```
2.  Worksite Analysis

    i.  Hazard Analysis of Routine Jobs, Tasks, and Processes

    ii. Hazard Analysis of Significant Changes, New Processes, and
        Non-Routine Tasks Including pre-use analysis and new baselines

    iii. Routine Self-Inspections

    iv. Hazard Reporting System for Employees

    v.  Industrial Hygiene Program

    vi. Investigation of Accidents and Near-Misses

    vii. Trend/ Pattern Analysis

3.  Hazard Prevention and Control

    i.  Certified Professional Resources

    ii. Hazard Elimination and Control Methods

        1.  Engineering Controls

        2.  Administrative Controls

        3.  Work Practice Controls and Hazard Control Programs

        4.  Personal Protective Equipment

    iii. Process Safety Management (if applicable)

    iv. Occupational Health Care Program

    v.  Preventive/Predictive Maintenance

    vi. Tracking of Hazard Correction

    vii. Emergency Preparedness

4.  Safety and Health Training

    i.  Managers

    ii. Supervisors

    iii. Employees

    iv. Emergencies

    v.  PPE

Note: For each sub-element include a description of:

-   Improvements made since the previous year and completion of the
    previous year\'s recommendations

-   Any deficiencies identified, recommendations for improvement, the
    person(s) responsible for fulfilling each new recommendation, target
    dates for their completion, and the data/information reviewed to
    assess the effectiveness of the sub-element.

13.4 FORMAT: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 MAINTENANCE: None required

**DRD CONTINUATION SHEET**

**TITLE**: Annual Safety Program Evaluation **DRD NO.**: 1.3.1.2-d

**DATA TYPE**: 2 **PAGE**: 3/3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Attachment 1

  ------------ ------- ---------- ----------- ----------- ----------- ------------ ------------ ------------ -------------
  Recordable                                                                                                 
  Injury and                                                                                                 
  Illness Case                                                                                               
  Incidence                                                                                                  
  Rates                                                                                                      

  1            2       3          4           5           6           7            8            9            10

  Year         Total   Total \#   Total \# of Total \# of Total Case  Total \# of  Total \# of  Sum of       Days Away,
               Work    of         Illnesses   Injuries &  incidence   Injuries     Injuries     Injury &     Restricted,
               Hours   Injuries               Illnesses   Rate for    Involving    Involving    Illness      and/or
                                                          Injuries    Days Away    Days Away    Cases        Transfer Case
                                                          and         from Work,   from Work,   Involving    Incidence
                                                          Illnesses   Restricted   Restricted   Days Away    Rate (DART
                                                          (TCIR       Work         Work         from Work,   rate)
                                                                      Activity,    Activity,    Restricted   
                                                                      and/or Job   and/or Job   Work         
                                                                      Transfer     Transfer     Activity,    
                                                                                                and/or/ Job  
                                                                                                Transfer     

  Last Year                                                                                                   

  Most recent                                                                                                 
  published                                                                                                  
  BLS rate                                                                                                   

  \% Above or                                                                                                
  below                                                                                                      
  National                                                                                                   
  Average                                                                                                    
  ------------ ------- ---------- ----------- ----------- ----------- ------------ ------------ ------------ -------------

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 367 **ISSUE**: BASIC 2. **DRD NO.**: 1.3.3

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Quality Plan

7\. **DESCRIPTION/USE**: To describe the contractor's plan for meeting
the quality requirements of NSTS 07700, volume X, book 1; and NSTS
5300.4 (1D-2) 1D500.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Contract award plus 60 days

10\. **SUBMISSION FREQUENCY**:

Quality Plan DRD 1.3.3 -- Quality Plan, Data Type 2: As required to
document updates and changes.

Quality Surveillance Results DRD 1.3.3 -- Surveillance Results, Data
Type 3: Every award fee period.

Quality Training Report DRD 1.3.3 -- Training Report, Data Type 3:
annually.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3; 1.3.3; 1.3.3.1; and 1.3.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This plan shall cover all products and processes under
SPOC.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700, Vol X, Bk 1, Space Shuttle Flight and Ground System
Specification

NSTS 5300.4 (1D-2) Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program

NSTS 08126 Space Shuttle Problem Reporting and Corrective Action (PRACA)
System Requirements

JSC 28035 Program Problem Reporting and Corrective Action Requirements
for Johnson Space Center Government Furnished Equipment

SSP 30223 Problem Reporting and Corrective Action (PRACA) for the Space
Station Program

13.3 **CONTENTS**: The plan shall describe the implementation of the
quality policies and processes that will assure compliance with the
requirements of SOW paragraphs 1.3.3, NSTS 07700 Vol. X, Book 1, and
NSTS 5300.4 (1D-2) D500 including Software Quality Assurance. As a
minimum, the plan shall include the following:

a)  Organization charts which illustrate the functional relationships
    and lines of communication between the organizations executing the
    quality requirements, CEO, and other organizational elements.

b)  Descriptions of the quality management functions within the
    organization including the process through which management
    decisions will be made.

c)  Description of the responsibility, authority, and accountability of
    Quality personnel.

d)  Description of the boards and panels serving the Quality
    organization.

**DRD CONTINUATION SHEET**

**TITLE**: Quality Plan **DRD NO.**: 1.3.3

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

e)  Description of inspection requirements, surveillance methodology,
    metrics and/or leading indicators used to maintain insight/oversight
    of the Quality function throughout the contractor organization.

f)  Description of flow down of NSTS 5300.4 (1D-2) 1D500 requirements to
    contractor quality management system documents organizational
    elements including verification method to ensure requirements have
    been met.

g)  Description of surveillance methodologies to be used to measure the
    effectiveness of the quality program.

h)  Description of the certification/qualification training approach,
    including listing all processes/tasks/positions that require
    certification or qualification and the requirements for getting that
    certification or qualification. The
    certification/qualification/training requirements shall include the
    type of training offered, employee requirements for completing
    training, and the frequency of training.

In addition to the Quality Plan, the contractor shall deliver a
Surveillance Report each award fee period and a Training Report
annually. The reports shall include the following information:

Surveillance Report:

a)  Description of the surveillance methodology for internal
    surveillance and supplier surveillance.

b)  Internal and Supplier Surveillance performed in the evaluation
    period.

c)  Internal and Supplier Surveillance findings.

d)  Plans for improvement.

Certification/Qualification Training Report:

a)  Listing of all processes/tasks/positions that require certification
    or qualification and the requirements for getting that certification
    or qualification

b)  Departments, organizations, or positions participating in training,
    certification, or qualification.

c)  Type of training (online, classroom).

d)  Number of employees trained, qualified, or certified.

e)  Number of employees left to be trained, qualified, or certified.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 368 **ISSUE**: BASIC 2. **DRD NO.**: 1.3.3.1

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Acceptance Data Package (ADP)

7\. **DESCRIPTION/USE**: The ADP is an accumulation of documentation
that provides a verified, complete, and current status of deliverable
hardware/software needed by the procuring/using organization to enable
the continuation of required activities.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Submitted with shipment/transfer of each
hardware item or software delivery.

10\. **SUBMISSION FREQUENCY**: Required with each delivery of hardware
or software from a manufacturer/developer to a using site or deliveries
between using sites.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.3.3.1, 1.2.1.4.2, 1.4.1.5.2, and 1.7.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: ADP\'s are required for all deliverable hardware items
and program software products (and their approved changes).

13.2 **APPLICABLE DOCUMENTS**:

SN-S-0008 Software Deliverable Data Package Requirements Specification

SN-D-0007 Acceptance Data Package Requirements

SSP 30695 Acceptance Data Package Requirement Specification

13.3 **CONTENTS**: The ADP shall be prepared in accordance with
SN-S-0008, SN-D-0007, and SSP 30695, as appropriate.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 369 **ISSUE**: BASIC 2. **DRD NO.**: 1.4-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: KSC Work Authorization Documents (Category 1) Development
and Maintenance Plan

7\. **DESCRIPTION/USE**: To define and document standardized processes,
formats, and responsibilities required for developing, maintaining,
approving, and changing KSC Work Authorization Documents (WADs).

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Submission of each WAD will be
established in accordance with the approval of the Operations and
Maintenance Documentation (OMD) Control Board and will be revised in
accordance with the approved WAD change processes and plans.

11\. **REMARKS**: The Technical Operations Procedure Preparation
Handbook (formerly NASA/DOD STS and Cargo Technical Operating Procedures
(TOPS) Preparation Handbook) provides guidance and direction for the
preparation and processing of Work Authorization Documents (WADs) such
as Operations and Maintenance Instructions (OMI's) and related products
of OMD. It provides coordination, update, and maintenance of a document
that establishes a single authoritative source setting forth the
concepts, practices, organization and format requirements to be adhered
to in the development, preparation, processing, review, approval, and
changes to all organizational level documents which are considered to be
Category 1 TOP's.

Operations and Maintenance Instructions (OMI's) are a subset of WADS and
are used to define & control the detailed activities required for site
activation, validation, acceptance, handling build-up, test, and
maintenance of the Shuttle flight elements, including interfacing direct
supporting GSE/facility systems and the assemble Shuttle vehicle.

Submission of each WAD will be established in accordance with approval
of the OMD Control Board and revised in accordance with the ICR Change
Process.

12\. **INTERRELATIONSHIP**: SOW 1.4 and 1.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The KSC Work Authorization Documents (Category 1)
Development and Maintenance Plan shall define contractor
responsibilities for the development and maintenance of Category 1
Shuttle processing procedures.

13.2 **APPLICABLE DOCUMENTS**:

S00000-2, File 1 Technical Operations Procedure Preparation Handbook

KVT-HB-0002 OIS Call Sign/Word Handbook

**DRD CONTINUATION SHEET**

**TITLE**: KSC Work Authorization Documents (Category 1) **DRD NO.**:
1.4-a

Development and Maintenance Plan

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS**: The KSC Work Authorization Documents (Category 1)
Development and Maintenance Plan shall:

a)  Describe the standardized approach to maintain, update, and control
    the configuration of existing and future WAD\'s (as a minimum
    Category 1) required for each planned flight hardware turnaround
    activity, as well as for support equipment for which the contractor
    has O&M responsibility in accordance with S00000-2, File 1.

WAD's will be consistent with the following guidance:

a)  Existing WAD's will be maintained and updated as required for each
    planned flight hardware turnaround activity, as well as for the GSE
    and facility equipment for which the contractor is assigned O&M
    responsibility.

b)  WAD's will be developed in a format to be compatible with potential
    LPS system capability, and per OMD Control Board policy.

c)  WAD update requirements will be done on a per-launch or per mission
    basis.

d)  WAD's will include manual instructions and automated test programs
    for checkout of the Shuttle and associated GSE.

e)  Maintain and update existing WAD's for Shuttle processing emergency
    procedures.

f)  Maintain and update all levels of existing facility and GSE
    operations and maintenance documentation.

The OIS Call Sign/Word Handbook (KVT-HB-002) shall provide definition of
all the KSC Operational Intercommunications System (OIS) call signs and
call words used during operational Shuttle processing. The handbook
shall designate the OIS call signs/words to be used during all
activities at or with KSC involving the OIS system.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.** 370 **ISSUE**: Basic 2. **DRD NO.**: 1.4-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Logistics Performance Report

7\. **DESCRIPTION/USE**: To provide trend analyses of key logistics
performance indicators to ensure the infrastructure is capable of
sustaining contract requirements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Monthly Reports

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4, 1.4.1.2, 1.4.7.2, 1.5.5.4, and 1.6

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report shall cover the total logistics support of
all areas of the SPOC.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The monthly report shall be submitted in writing and
upon request shall be presented as an oral briefing. The contractor
shall maximize the use of electronic data transfer. The contractor shall
provide NASA with electronic access to the supporting data. The elements
of the report are:

a)  Executive summary of performance trending, issues, concerns, and
    recommendations.

b)  Program enhancements and major initiatives which are in work by the
    contractor.

c)  General overview of monthly expenditures for manpower and material.

d)  Performance against standards designated in the SOW.

e)  Additional performance indicators:

    1.  Logistics actual work force versus budgeted work force (EP).

    2.  Transportation and Receiving: Dock to stock time.

    3.  Flight Operations Logistics Supply Fill Rate

    4.  Provide a measure of orbiter hardware demands for inventory
        items which have been inactive for a minimum of 24 months.

    5.  Active inventory items at zero balance.

        a.  Number of Orbiter active inventory items at zero balance.

            1.  Number of Reparable inventory items at zero balance.

                A.  Number of Reparable inventory items at zero balance
                    with quantity due-out to customer.

                B.  If data is available, list recurring items at zero
                    balance with quantity due-out to customer.

            2.  Number of Non-reparable inventory items at zero balance.

                A.  Number of Non-reparable inventory items at zero
                    balance with quantity due-out to customer.

                B.  If data is available, list recurring items at zero
                    balance with quantity due-out to customer.

**DRD CONTINUATION SHEET**

**TITLE**: Logistics Performance Report **DRD NO.**: 1.4-c

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

b.  Number of Ground active inventory items at zero balance.

    1.  Number of Reparable inventory items at zero balance.

        A.  Number of Reparable inventory items at zero balance with
            quantity due-out to customer.

        B.  If data is available, list recurring items at zero balance
            with quantity due-out to customer.

    2.  Number of Non-reparable inventory items at zero balance.

        A.  Number of Non-reparable inventory items at zero balance with
            quantity due-out to customer.

        B.  If data is available, list recurring items at zero balance
            with quantity due-out to customer.

    3.  Number of Non-reparable inventory items at zero balance which
        require cleaning or calibration.

        A.  Number of Non-reparable inventory items at zero balance
            which require cleaning or calibration with quantity due-out
            to customer.

        B.  If data is available, list recurring items at zero balance
            which require cleaning or calibration with quantity due-out
            to customer.

```{=html}
<!-- -->
```
6.  Provide the number of Orbiter non-stock listed demands and the
    number of total demands.

7.  Provide a metric on the NSLD Resources, workload and backlog

8.  Integrated Logistics shall provide MTAR and ATLAS documents or a
    streamlined/combined equivalent.

9.  Provide insight and/or access to all working level metrics utilized
    in the performance of SPOC.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 371 **ISSUE**: BASIC 2. **DRD NO.**: 1.4-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Government Furnished Material (GFM) and Propellants
Requirements Forecast

7\. **DESCRIPTION/USE**: To assure adequate propellant and GFM supply
and distribution planning in support of this contract.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Six months (beginning after initial
submission)

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4 and Attachment J-9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: See item 13.3 and Attachment J-9.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The contractor shall prepare three-year propellant
and GFM forecast. The forecasts shall be derived from user inputs and
historical data.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 372 **ISSUE**: Basic 2. **DRD NO.**: 1.4-e

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Loss of Capabilities and Corrective Action Report

7\. **DESCRIPTION/USE**: To report and prioritize through an established
risk assessment process supportability issues and to plan corrective
action for flight, flight GSE and critical GSE hardware.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Government notification as soon as the
Contractor is aware of a loss of repair, failure analysis, and
production capability. Otherwise, monthly submission of DRD report.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report shall cover the total Logistics support of
all areas of the SPOC.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The contractor shall:

a)  Provide immediate notification in writing, or electronically, to
    NASA OPR loss of repair, failure analysis, and production
    capabilities. Provide written notification in the next DRD report
    submission with preliminary plan of corrective action.

b)  Provide a prioritized risk assessment of supportability issues for
    flight, flight GSE and critical GSE hardware. A recovery plan shall
    be provided within 3 months of identification of all supportability
    issues. The plan shall, as a minimum, include the supportability
    issue, corrective action, and projected resolution date for each
    piece of hardware affected.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 373 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.1

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Corrective Action Record (CAR)

7\. **DESCRIPTION/USE**: To document the necessary investigations to
determine the cause of an identified hardware problem and the corrective
actions to preclude recurrence of the problem.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**:

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall investigate reported hardware
problems and provide corrective actions necessary to resolve the
identified problems and preclude problem recurrence, as required.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 37325 JSC Orbiter Problem Reporting and Corrective Action (PRACA)
Requirements

13.3 **CONTENTS**:

13.4 **FORMAT**: Per NSTS 37325, JSC Orbiter Problem Reporting and
Corrective Action (PRACA) Requirements

13.5 **MAINTENANCE**:

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 374 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.1.1-b

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Change Requests (CR's) and Reviews

7\. **DESCRIPTION/USE**: To document proposed changes to the contractor
or baseline effort, including applicable program requirements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.5.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall:

a)  Submit a CR to revise any contract-referenced requirement, or to
    submit Class 1 engineering design change proposals (EDCPs) or
    reusable hardware flight authorizations (RHFAs) for NASA review and
    approval.

b)  Comment upon NASA-provided CRs originating outside this contract
    relating to flight elements.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: A CR submitted to revise a contract-referenced
requirement shall comply with the change content guidelines listed in
the affected requirement. A CR submitted for approval of Class 1 EDCPs
or RHFAs may include briefings, schematics, drawings, or other
documentation deemed appropriate by the contractor.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 375 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.1.1-c

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Specification Change Notice

7\. **DESCRIPTION/USE**: To document the approval of changes to specific
contract controlling specifications.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: As required to correct or update
contract-referenced specifications

10\. **SUBMISSION FREQUENCY**: As required to correct or update
contract-referenced specifications.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.5.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: A Specification Change Notice details specific changes
to contract controlling specifications.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: A Specification Change Notice shall include the
following information, as applicable:

a)  Contractor's name, address, and identification code.

b)  Specification change tracking references, including the number and
    revision level of the affected specification, a sequence number and
    revision letter serially assigned uniquely for changes to the
    affected specification, a contract revision number, engineering
    change proposal number, or program change identification number, the
    configuration item number covered by the affected specification, and
    the serial number(s) of the article(s) affected by the change.

c)  Verbatim changes to be made to the text, tables, or figures in the
    affected specification.

d)  Contractual change authority reference added upon approval of the
    change.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 376 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.1.2-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Special Action Requirement (SAR)

7\. **DESCRIPTION/USE**: To establish requirements for special action by
field sites.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: As required to provide authority for
accomplishing a special action on hardware or software end items

10\. **SUBMISSION FREQUENCY**: N/A

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: A SAR shall be issued to establish requirements for
problem-related troubleshooting, inspections, nondestructive evaluation
(NDE), transfer of critical hardware, or other one-time-only tests or
operations.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: A SAR shall describe the system involved, action
required, pass/fail criteria, retest requirements, action effectivity,
and rationale supporting the action requirement as applicable. The SAR
shall include a title, tracking number, date, point-of-contact, and a
record of approval signatures.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 377 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.1.3-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Operational Maintenance Requirements and Specifications
Document Changes

7\. **DESCRIPTION/USE**: To implement creation, revision or deletion of
Shuttle system operational maintenance requirements and specifications
in accordance with Master Verification Plan requirements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: As required to support launch site test
planning or as otherwise authorized by the Contracting Officer's
Technical Representative (COTR) or designee

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Operational Maintenance Requirements and
Specifications Document (OMRSD) establishes the checkout, validation,
servicing, and maintenance retest requirements for Space Shuttle Vehicle
and ground support equipment as detailed in NSTS 08171 OMRSD File I.
OMRSD changes shall be submitted as required by applicable documents to
reflect Master Verification Plan changes, modifications, and mission
unique configurations. OMRSD changes may also be submitted in response
to experience gained from prior turnaround testing, acceptance testing,
or anomaly resolution activities.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700-10-MVP-01 Space Shuttle Master Verification Plan

NSTS 08171 Operational Maintenance Requirements and Specifications
Document (OMRSD)

13.3 **CONTENTS**: OMRSD change content requirements are detailed in
NSTS 08171 OMRSD File I.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated into the OMRSD in
accordance with NSTS 08171 OMRSD File I requirements.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 378 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.5.1-a

3\. **DATA TYPE**: 1, 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Requirement Definition Documents for Modifications,
Mission Kits and GSE

7\. **DESCRIPTION/USE**: To establish and control the design,
performance, and verification requirements for system modifications,
Orbiter and payload integration mission kits, and ground support
equipment from preliminary design through delivery.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Initial Requirement Definition Document
drafts are submitted one month prior to preliminary design review.

10\. **SUBMISSION FREQUENCY**: Revisions submitted as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.4.2, 1.4.1.5.2, 1.7.1.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: A Data Type 1 Requirement Definition Document is
required for new modification, mission kit, and GSE designs which
provide or impact a critical flight or ground function. A Data Type 2
Requirement Definition Document is required for non-critical designs and
designs which are to be certified by similarity with certified and
proven hardware.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700, Volume IV Configuration Management Requirements

NSTS 07700 Volume X Space Shuttle Flight and Ground Systems
Specification

NSTS 07700 Volume XIV Space Shuttle System Payload Accommodations

NSTS 07700-10-MVP-01 Space Shuttle Master Verification Plan

13.3 **CONTENTS**: A Requirement Definition Document shall contain a
definition including system requirements for capability, performance,
configuration, operation, interfaces, safety, reliability, life,
storage, verification. The document shall also include a list of design
and review documentation products required for certification.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by page
change or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 379 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.5.1-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Certification Requirement (CR)

7\. **DESCRIPTION/USE**: To define the testing and/or analysis required
to certify the design of a hardware item or subsystem.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Certification requirement - no later than 60
days prior to the scheduled start of certification testing. Hardware
certification requirement - no later than 90 days prior to the scheduled
submittal of certification analysis reports when certification is by
analysis in lieu of testing.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.4.2, 1.4.1.5.2, 1.7.1.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: A CR is submitted to define the test and/or analysis
required to certify the design of a new hardware item or subsystem. A
certification requirement change is submitted to revise or define any
new test and/or analysis required to certify the design of an existing
or modified hardware item and subsystem. Certification requirements for
a hardware item or subsystem shall comply with the requirements
specified in the applicable documents.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Volume IV Configuration Management Requirements

NSTS 07700 Volume X Space Shuttle Flight and Ground System Specification

NSTS 07700 Volume XIV Space Shuttle System Payload Accommodations

NSTS 07700-10-MVP-01 Shuttle Master Verification Plan

13.3 **CONTENTS**: A certification requirement shall contain the
following information, as applicable:

a)  Certification requirement reference and tracking information,
    including a certification requirement number, certified part or
    subsystem name(s) and number(s), vehicle location(s), vehicle
    effectivity.

b)  Certification method (test or analysis) including sequence and
    environment (shall include supporting rationale for analysis instead
    of test).

c)  Testing requirements (as applicable), including pretest functional
    verification requirements, test type, test duration, test
    constraints, test article operating mode, pass/fail criteria and
    tolerances, and post-test functional verification requirements.

d)  Test article information (as applicable) including test part
    serial/lot number(s); the number of test specimens and test
    allocations; and test request, procedure, and report references and
    tracking information.

e)  Description and explanation of any differences between test parts
    and certified parts.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by page
change or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 380 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.5.1-c

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Certification Approval Request (CAR)/Qualification Site
CAR

7\. **DESCRIPTION/USE**: To document certification testing and analysis
results, and the approval of certification of a hardware item or
subsystem design. A qualification site CAR, used for high cost or
sophisticated certification tests, documents test results for review
prior to test teardown and the tentative approval of certification of a
hardware item or subsystem design pending formal report preparation,
submittal, and approval.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: CAR - no later than 60 days after completion
of certification testing and analysis, but no less than 60 days prior to
the event constrained by item certification. Qualification site CAR may
be submitted prior to test teardown and formal report preparation.

10\. **SUBMISSION FREQUENCY**:

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.4.2, 1.4.1.5.2, and 1.7.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: A CAR is submitted with all associated test or analysis
reports to request approval of certification of the design of a new or
modified hardware item or subsystem. A CAR for qualification site
approval pending preparation and submittal of formal reports may be
utilized for high cost or sophisticated certification tests where test
is constraining program milestones.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Volume IV Configuration Management Requirements

NSTS 07700 Volume X Space Shuttle Flight and Ground System Specification

NSTS 07700 Volume XIV Space Shuttle System Payload Accommodations

NSTS 07700-10-MVP-01 Shuttle Master Verification Plan

13.3 **CONTENTS**: CAR's shall contain the following information, as
applicable:

a)  Certification reference and tracking information, including the
    associated certification requirement number, certified part or
    subsystem name(s) and number(s), vehicle location(s), and vehicle
    effectivity.

b)  Certified item supplier information, including supplier name,
    supplier part number(s), and supplier purchase order number.

c)  Test reports (as applicable), including test agency name and
    location, test objectives, test hardware and setup description
    including drawings and photographs, test start and completion dates,
    validated as-run test procedures and variance descriptions,
    validated test results, data, laboratory notes, and associated
    analysis results, and test anomaly and test hardware failure
    descriptions, analyses, and resolutions.

d)  Analysis reports (as applicable), including analysis objectives,
    detailed analysis logic, and analysis results and conclusions.

e)  Formal certification recommandations.

**DRD CONTINUATION SHEET**

**TITLE**: Certification Approval Request (CAR)/ **DRD NO.**:
1.4.1.5.1-c

Qualification Site CAR

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

CAR's for qualification site approval pending preparation and submittal
of formal reports shall contain the following information, as
applicable:

a)  Certification reference for tracking information, including the
    associated certification requirement number, certified part or
    subsystem name(s) and number(s), vehicle location(s), and vehicle
    effectivity.

b)  Test reports, including test agency name and location, test
    objectives, test hardware and setup description, test start and
    completion dates, test environments and sequence descriptions,
    verification of calibration, adjustment, and proper operation of
    test facilities or instruments, key test results (parametric) and
    associated test evaluations, and test anomaly and test hardware
    failure descriptions, evaluations, and resolutions.

c)  Formal certification recommendations.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 381 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.6.1-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Inputs to JSC 08934, Shuttle Operational Data Book (SODB)

7\. **DESCRIPTION/USE**: The Shuttle Operational Data Book (SODB), a
part of the Operational Data Exchange System, is the single
authoritative flight planning and operations support source for
validated Orbiter performance, configuration, mass property, and
emergency rescue data. SODB inputs consist of updates reflecting
configuration or system performance changes for specific vehicles or
missions, and responses to requests for off-nominal performance
characteristics or constraints data.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: As required

10\. **SUBMISSION FREQUENCY**: Updates submitted as required to assure
current and accurate configuration and system performance data are
available for flight planning and operations support.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: SODB updates are required to reflect modifications and
mission-specific configuration and system performance characteristics.
SODB updates are also required to incorporate pertinent Shuttle
operational data developed in response to NASA requests.

13.2 **APPLICABLE DOCUMENTS**:

JSC 08934 Shuttle Operational Data Book

13.3 **CONTENTS**: SODB updates shall contain data as follows:

a)  Volume I updates shall contain Shuttle flight performance
    characteristic, system limitation, and operational constraint
    revisions by system and by vehicle.

b)  Volume II updates shall contain Orbiter and payload mass property
    revisions by vehicle and by flight.

c)  Volume III updates shall contain off-nominal system performance
    characteristic revisions.

d)  Volume IV updates shall contain Orbiter configuration, hazard,
    ground operation, and requirement revisions for crew rescue
    following landing. Orbiter configuration shall include vehicle
    structure, subsystems, plumbing, wiring, mission kits, and cargo.
    Volume IV part 1 updates shall include source reference document
    revisions for Orbiter landing emergency rescue data, and part 2
    updates shall include changes to crew rescue and emergency situation
    quick-reference guides for contingency response teams.

e)  Volume V updates shall contain Orbiter flight capability envelope
    revisions.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Volume changes shall be incorporated by page
change or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 382 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.6.1-d

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Non-Flight Constraint (NFC) Disposition

7\. **DESCRIPTION/USE**: To document a determination for each vehicle
and each flight that an open anomaly does not constrain flight.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Within 10 working days of problem
confirmation

10\. **SUBMISSION FREQUENCY**: Prior to each flight for each open
anomaly

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Refer to NSTS 08126 to determine which open anomalies
require NFC dispositions.

13.2 **APPLICABLE DOCUMENTS**

NSTS 08126 Problem Reporting and Corrective Action Requirements

13.3 **CONTENTS**: NFC dispositions shall include all information used
to develop the contractor's recommendation and supporting rationale. NFC
dispositions shall comply with NSTS 08126.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by page change or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 383 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.6.1-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Configuration Engineering Data (ICED) Library

7\. **DESCRIPTION/USE**: To provide a library of Computer-Aided Design
(CAD) models of non-ISS payloads and required mission kits that will be
installed in the payload bay for use primarily in flight operations and
ground operations assessments.

8\. **DISTRIBUTION**: Release to ICED file server for access by users.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Payload models available once
configuration is documented in Interface Control Document (ICD). Mission
kit models available following release of Cargo Arrangement drawing in
support of Flight Reconfiguration Engineering Drawing (FRED) release or
as negotiated.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.2.1.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The ICED library shall be populated with CAD non-ISS
payload and required mission kit models as requested by NASA. The ICED
library shall be accessible to NASA electronically.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The ICED library shall include CAD files of
mission-specific non-ISS payloads and mission kits installed that will
be in the Orbiter payload bay.

13.4 **FORMAT**: Contractor shall post ICED library in OBJ format.

13.5 **MAINTENANCE**: Changes shall be incorporated by electronic
transmission of revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 384 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.1.6.1-g

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Instrumentation Program and Components Lists (IPCLs)

7\. **DESCRIPTION/USE**: To identify measurement channelization, signal
routing, and probable measurement inaccuracies, and control the
configuration of the Orbiter Instrumentation System for each Orbiter
flight.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 45 days prior to each Orbiter flight, or as
otherwise authorized by the Contracting Officer Technical Representative
(COTR) or designee

10\. **SUBMISSION FREQUENCY**:

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.1.6.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: IPCLs shall for each Orbiter flight shall describe and
control the configuration of sensors, signal conditioners, and data
acquisition equipment encompassing both Operational Instrumentation (OI)
and Modular Auxiliary Data Systems (MADS) Instrumentation. IPCLs do not
cover sensors or signal conditioners unique to a subsystem or those
functions uniquely transferred between computer(s) and the Pulse Code
Modulator (PCM) system.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: IPCL documents shall be divided into the following
major sections and shall include a legend explaining headings, fields,
and codes used in the document.

a)  Equipment List - identifies the location, part numbers, sensor
    reference designators, and installation drawings of sensors and
    signal conditioners used to implement OI and DFI measurements.

b)  Signal Conditioner and Telemetry Loading - presents details of
    signal conditioners, defines signal routing from sensor to signal
    conditioner to Multiplexer/Demultiplexer (MDM) or PCM Multiplexer
    (PCM-MUX) or Frequency Division Multiplexer (FDM), Displays and
    Controls (D&C) and recorder data acquisition equipment. Also
    provides MDM/FDM/PCM-MUX channel identification.

c)  PCM-MUX and Downlink Format - includes details on MDM/FDM loading
    and PCM downlink formats.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 385 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.2.1-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: SRB and Range Safety Command Destruct System Failure
Modes and Effects Analysis (FMEA)

7\. **DESCRIPTION/USE**:

a)  To determine the possible modes of each failure, and the effects of
    each failure.

b)  To classify the criticality of all hardware.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**:

a)  SRB and Range Safety Command Destruct System Level FMEA - One time
    with revisions

b)  Component Level FMEA - One time with revisions

10\. SUBMISSION FREQUENCY:

a)  SRB FMEA

Immediate updates six (6) weeks prior to Flight Readiness Review (FRR)

Periodic updates a minimum of once per year

b)  Component Level FMEA

Submitted with Critical Design Review (CDR) data package, revisions as
required

Initial submission four (4) weeks prior to transfer of first flight
article

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: DRD 1.4.2.1-b

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD establishes the content, format, maintenance,
and submission requirements for the SRB FMEA's and Component Level
FMEA's.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 5300.4(1D-2) Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program

NSTS 22206, Rev. A Instructions for Preparation of Failure Modes and
Effects Analysis (FMEA) and Critical Items List (CIL)

13.3 **CONTENTS**: The FMEA's shall document qualitative reliability
analyses, identify failure modes and effects, and classify failure mode
criticalities.

a)  The SRB and Range Safety Command Destruct System Level FMEA shall
    meet the intent of the NSTS 5300.4(1D-2) and shall be performed
    using NSTS 22206, Rev. A as a guide.

b)  The Component Level FMEA's shall be prepared and/or updated on
    criticality 1, 1R, and 3 hardware under the Contractor's design
    responsibility. The Component Level FMEA's shall meet the intent of
    NSTS 5300.4(1D-2) and shall be performed using NSTS 22206, Rev. A as
    a guide.

13.4 **FORMAT**: As specified in NSTS 22206, Rev. A or as mutually
agreed to by the Contractor.

**DRD CONTINUATION SHEET**

**TITLE**: SRB and Range Safety Command Destruct System **DRD NO.**:
1.4.2.1-a

Failure Modes and Effects Analysis (FMEA)

**DATA TYPE**: 1 **PAGE**: 2/2

13.5 **MAINTENANCE**:

a.  The System Level FMEA shall be revised as necessary for each flight.
    All applicable changes shall be incorporated. Changes shall be
    accomplished by change pages or a complete reissue.

b.  The Component Level FMEA shall be revised by the Contractor or his
    vendor whenever a design change that can affect the FMEA's is
    performed.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 386 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.2.1-b

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SRB and Range Safety Command Destruct System Critical
Items List (CIL)

7\. **DESCRIPTION/USE**: To provide a listing of all criticality
category 1, 1R, and 3 hardware identified in the SRB and Range Safety
Command Destruct System Level FMEA.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: One time with revisions four (4) weeks prior
to transfer of first flight articles.

10\. **SUBMISSION FREQUENCY**: One time with revisions: (a) Immediate
updates six (6) weeks prior to Flight Readiness Review (FRR); and (b)
Periodic updates a minimum of one (1) per year.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: DRD 1.4.2.1-a

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD establishes the content, format, maintenance,
and submission requirements for the SRB CIL.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 5300.4(1D-2) Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program

NSTS 22206, Rev. A Instructions for Preparation of Failure Modes and
Effects Analysis (FMEA) and Critical Items List (CIL)

13.3 **CONTENTS**: The CIL shall document and provide rational for
retention for the critical SRB and Range Safety Command Destruct System
failure modes and effects identified in the SRB and Range Safety Command
Destruct System Level FMEA.

The CIL shall meet the intent of NSTS 5300.4(1D-2). The CIL shall be
prepared using NSTS 22206, Rev. A, Instructions for Preparation of
Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL).

13.4 **FORMAT**: As specified in NSTS 22206, Rev. A or as mutually
agreed to by the Contractor.

13.5 **MAINTENANCE**: The SRB and Range Safety Command Destruct System
CIL shall be revised as necessary for each flight. All applicable
changes shall be incorporated. Changes shall be accomplished by change
pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 387 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.2.1-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SRB Mass Properties Status Report

7\. **DESCRIPTION/USE**: To provide necessary mass properties data for
test, flight evaluation, and recovery.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Beginning with first flight after Authority
to Proceed (ATP) and in accordance with the frequency stated in Block
10.

10\. **SUBMISSION FREQUENCY**: A Preflight Status Report will be
delivered for each flight. The report date is contingent upon flight
schedule dates. Quarterly status reports will be submitted within ten
(10) working days after receipt of Solid Rocket Motor (SRM) data.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD establishes the requirements for mass
properties evaluations and reporting.

13.2 **APPLICABLE DOCUMENTS**: All SRB documentation for test and flight
hardware.

13.3 **CONTENTS**: The content shall comply with the content established
in the initial preparations of the evaluations and reports.

13.4 **FORMAT**: The format shall comply with the format established in
the initial preparations of the evaluations and reports.

13.5 **MAINTENANCE**: The reports shall be supported by detailed backup
data from the computer base and associated Mass Properties tape.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 388 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.2.1-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SRB Final Flight Evaluation Report

7\. **DESCRIPTION/USE**: To provide a report which contains results of
the SRB/Shuttle Range Safety System (SRSS) flight performance
evaluation.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: See Block 10.

10\. **SUBMISSION FREQUENCY**: Deliver within 65 days after a shuttle
launch.

11\. **REMARKS**: The subject document consists of results from the
flight data evaluation and post flight damage assessment.

12\. **INTERRELATIONSHIP**: SOW 1.4.2.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD establishes the requirements to prepare a
detailed report specifying SRB/SRSS flight performance in the following
areas:

a)  SRB Mass Properties

b)  SRB Thrust Vector Control (TVC) System

c)  SRB Structures and Loads

d)  Pressure, Vibration and Acoustic Environments

e)  SRB Ascent, Reentry and Ascent Base Aerodynamic Heating

f)  SRB Temperature and Thermal Protection System (TPS) Performance

g)  SRB Electronics and Instrumentation

h)  SRB Separation, Reentry and Recovery Subsystems

i)  SRB Hardware Assessment

j)  Shuttle Range Safety System (SRSS)

13.2 **APPLICABLE DOCUMENTS**:

MSFC-PLAN-1228 Operational Space Shuttle Flight Evaluation Plan

13.3 **CONTENTS**:

The report shall contain, but not be limited to the following
information:

a)  Evaluation of SRB hardware performance and operational
    characteristics

b)  Correlation of data with ground test results and design analysis in
    support of system requirements

c)  Effects on overall system performance and operational
    characteristics

d)  Verification of performance of configuration modifications for the
    SRB

e)  Identification of performance trends associated with SRB operation,
    which might lead to a future problem or issue

f)  History of previous hardware performance and/or problems, issues and
    In-Flight Anomalies (IFA's)

g)  Post-flight inspection results

13.4 **FORMAT**: The Contractor's format is acceptable.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 389 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.2.1-f

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Solid Rocket Booster (SRB) Project Management Plan

7\. **DESCRIPTION/USE**: To provide a description of the Contractor's
methods for accomplishing the SRB Program requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Updates as required to reflect current
management philosophy.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD establishes the content, format, maintenance,
and submission requirements for the SRB Management Plan. The plan shall
be summary in nature with references to the internal procedures and
shall describe the Contractor's practice and approach for, managing and
controlling the SRB Program Tasks, management interfaces, time phased
relationships of tasks and program elements and the criteria against
which performance may be judged.

13.2 **APPLICABLE DOCUMENTS**:

10CEI-0001, Contract End Item Specification, Part 1 Integrated Solid
Rocket Booster (ISRB) Operational Flights (BI007 and Subsequent Flights)

NSTS 07700, Volume V , Space Shuttle Information Management Requirements

13.3 **CONTENTS**: The plan shall summarize the Contractor's methods for
accomplishing and managing the SRB Program tasks. In addition, the plan
shall describe those management systems utilized in defining and
delegating task assignments and define the organizational relationships
of the Contractor and the Government. The plan includes Class I Change
and Senior MRB definitions. Any organizational consolidation and/or
horizontal integration activities shall be documented in the plan.

13.4 **FORMAT**: The Contractor's format is acceptable.

13.5 **MAINTENANCE**: The plan shall be maintained current by page
revision or complete reissue, to reflect all approved program changes.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 390 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.2.1-g

3\. **DATA TYPE**: 3 4. **DATA REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SRB and Range Safety Command Destruct System Flight
Hazard Analysis

7\. **DESCRIPTION/USE**: To document SRB flight hazards and to provide
status of their resolution.

8\. **DISTRIBUTION**: Per the Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: See below.

10\. **SUBMISSION FREQUENCY**: One time and revisions, updated annually
or prior to each flight if mandated by NSTS 22254 criteria for mission
updates.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: DRD 1.4.2.1-a, SRB Failure Modes and Effects
Analysis (FMEA) and DRD 1.4.2.1-b, SRB and Range Safety Command Destruct
System Critical Items List (CIL)

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD establishes the preparation, maintenance, and
submission requirements for the Hazard Analysis Report.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 5300.4 Safety, Reliability, Maintainability and Quality Provisions
for the Space

Shuttle Program; System Safety

NSTS 22254 Methodology for Conduct of NSTS Hazard Analysis

13.3 **CONTENTS**: The Hazard Analysis Report shall contain hazard
reports and hazard fault trees. The hazard reports shall meet the
requirements as defined in NSTS 22254.

13.4 **FORMAT**: As specified in NSTS 22254 or as mutually agreed to by
the Contractor.

13.5 **MAINTENANCE**: The SRB Flight Hazard Analysis shall be revised
annually or as necessary for each flight. All applicable changes shall
be incorporated. Changes shall be accomplished by change pages or
complete reissue of the document.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **DRL NO.**: 391 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3-a

3\. DATA TYPE: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Software Quality Report

7\. **DESCRIPTION/USE**: To provide management and customer visibility
into the status of the software quality for the PASS, BFS, MEDS, MAGR,
FSWAT, Data Recon, and SAIL Applications Software.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted semi-annually
as authorized by the Contracting Officer Technical Representative (COTR)
or designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Software Quality Report covers activities occurring
during a period of six months (January through June and July through
December).

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The report shall contain the following:

For PASS:

1.  Historical trends of quality measurements since OI release 1
    including process errors, product errors, early detection rates,
    verification effectiveness, and released product errors. Both charts
    and tabular history data will be presented

2.  Historical trends of reliability measurements and estimated time to
    the next problem will be computed using statistical and reliability
    engineering models

3.  Overview of quality improvement activities undertaken by the
    contractor and the results of their usage

4.  Selected metrics of the software process will be maintained and
    reported. All metrics defined under the contract will be reported
    and evaluated for trends

For BFS

Summary of quality metrics for the reporting period. These metrics
include trend analysis charts with information on early detection
percentages and process and product error rates for Operational
Increments (OI\'s). Corrective actions to the software process are
included for the post First Article Configuration Inspection (FACI) and
post Configuration Inspection (CI) product errors. Corrective actions
are tracked until closure.

For MEDS

Summary of quality metrics for the reporting period. These metrics trend
analysis charts with information on early detection percentages and
process and product error rates for software increments. Corrective
actions to the software process are included for the post Test Readiness
Review (TRR) and post Software Acceptance Review (SAR) product errors.
Previous reported corrective actions are tracked until closure.

**DRD CONTINUATION SHEET**

**TITLE**: Software Quality Report **DRD NO.**: 1.4.3-a

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

For MAGR FSWAT, Data Recon, and SAIL Software Applications a summary of
the quality metrics for the reporting period.

For BFS and MEDS a summary of Software Quality Assurance (SQA)
activities that include the following:

1.  Software procedural and method enhancements.

2.  Quality and configuration audits.

3.  Product release verifications.

4.  Program change control.

5.  SQA quality metrics summary

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 392 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-a

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software User\'s Manuals for
Software Support Tools

7\. **DESCRIPTION/USE**: To define procedures for assisting the user in
execution of the BFS software support tools.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10 **SUBMISSION FREQUENCY**: As required; products will be submitted at
CI for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The documents provide procedures for executing the BFS
support tools during the FSW development builds and reconfiguration
processes.

13.2 **APPLICABLE DOCUMENTS**:

JSC-20183 Flight Software Build and Reconfiguration Support Tools

13.3 **CONTENTS**: Deliverable documentation is specified in JSC-20183,
Flight Software Build and Reconfiguration Support Tools. These documents
shall contain:

a)  Reference documents.

b)  Execution instructions.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 393 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software Requirements and
Specifications Documents for Software Support Tools

7\. **DESCRIPTION/USE**: These documents define the requirements and
specifications for BFS software support tools used to perform FSWAT
development.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required; products will be submitted
at CI for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The documents cover the requirements and specifications
for BFS software support tools used for FSWAT development.

13.2 **APPLICABLE DOCUMENTS**:

JSC-20183 Flight Software Build and Reconfiguration Support Tools

13.3 **CONTENTS**: Deliverable documentation is specified in JSC-20183,
Flight Software Build and Reconfiguration Support Tools. These documents
shall contain:

a)  Programming requirements.

b)  Design requirements.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 394 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-c

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software Design Document (SDD)
for Software Support Tools

7\. **DESCRIPTION/USE**: To document the detailed design of the BFS
software support tools.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required; products will be submitted
at CI for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document provides a high-level description of the
software program and a description of each procedure in the program.

13.2 **APPLICABLE DOCUMENTS**:

JSC-20183 Flight Software Build and Reconfiguration Support Tools

13.3 **CONTENTS**: Deliverable documentation is specified in JSC-20183,
Flight Software Build and Reconfiguration Support Tools. These documents
shall contain:

a)  System requirements.

b)  Program overview.

c)  Program language.

d)  Program interfaces.

e)  Limitations.

f)  Procedures.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 395 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software Authorization Sheet
(SAS) and Patches

7\. **DESCRIPTION/USE**: To formally release software developed to
satisfy testing, training, and mission objectives in the laboratory
environment.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: SAS is a form utilized to request a patch (modify
software) to support facility testing. It is submitted/requested through
the Test and Operations (T&O) Board.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: SASs shall contain:

a)  Descriptive title.

b)  SAS number.

c)  Software system affected.

d)  Originator.

e)  Need date of change.

f)  Type change.

g)  Type patch.

h)  Reason for change.

i)  Concurrence.

j)  Authorized facility.

k)  Description of change.

l)  General Purpose Computer (GPC) configuration.

m)  Mass Memory Unit (MMU) areas affected.

n)  Type release - restricted/unrestricted.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 396 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-k

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Measurement Stimulus Identification (MSID) Assignment and
Integration (Downlist/Downlink)

7\. **DESCRIPTION/USE**: To establish Measurement Stimulus
Identification (MSID) numbers and channelization for vehicle hardware
and software measurements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Representative (COTR) or designated
representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Upon request from SCR and DCR initiators, and subsystem
users, MSID numbers and channelization are assigned for all vehicle
hardware and software parameters.

13.2 **APPLICABLE DOCUMENTS**: Master Change Records (MCRs), Software
Change Requests (SCRs), Program Requirements Control Board Directives
(PRCBD), and the Data Integration Plan (DIP), Volume III.

13.3 **CONTENTS**: The measurement numbers and channelization are
assigned using a MSID Assignment Database and a Channelization Database,
respectively, per the requirements in the Data Integration Plan (DIP),
Volume III and per the requirements of the modification and engineering
configuration drawings.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by MCRs,
SCRs, and PRCBDs.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 397 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-n

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Telemetry Format Load/Decommutation Format Load/Fetch
Pointer Load (TFL/DFL/FPL) Universal Patch Format (UPF) Patches

7\. **DESCRIPTION/USE**: To revise the TFL/DFL/FPL contents of the Mass
Memory Unit (MMU) after a MMU build.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Patch to be delivered no later than seven
working days following approval of the authorizing Change Request (CR)
by the Shuttle Avionics Software Control Board (SASCB) or per SASCB
negotiated schedules.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The patch contains revised TFL/DFL/FPL contents with
associated MMU memory locations.

13.2 **APPLICABLE DOCUMENTS**: Software Change Requests (SCRs)

JSC 08338, Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP)

13.3 **CONTENTS**: Release of TFL/DFL/FPL UPF patch includes products
specified in the Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP), JSC 08338, as deliverables for each patch.
Explicit patch contents are defined in the MIP.

13.4 **FORMAT**: The patch format is controlled through the MIP, JSC
08338. The patch is delivered in an electronic dataset.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 398 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.1-q

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Develop/Evaluate MAST II/STAR Reconfiguration Data Change
Requests (DCRs)

7\. **DESCRIPTION/USE**: To request a change to the Flight Software
reconfigurable data.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as required
to support Flight Software reconfiguration schedules.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: MAST II/STAR DCRs are used to request a change to the
Flight Software reconfigurable data including vehicle, payload, system
management, booster, main engine, and remote manipulator system (RMS).

13.2 **APPLICABLE DOCUMENTS**:

NSTS 10784 Space Shuttle Telemetered and Recorded Data Format
Requirements

JSC 20201 Operational Shuttle Data Reconfiguration

JSC 18206 Shuttle Data Integration Plan Volumes I and III

SCR 89053 SASCB Process Documentation: MAST II/STAR Reconfiguration

13.3 **CONTENTS**: The following DCRs are included:

a)  Vehicle Definition (VDF)

b)  Vehicle Occurrence (VOC)

c)  Mission Definition (MDF)

d)  Mission Occurrence (MOC)

e)  MAST II Mission Build Specification

f)  STAR SM Mission Build Specification

g)  System management (SM) VE/VEH

h)  Cargo Element (payload unit)

i)  Cargo Bay Mission (CBM)

j)  Orbiter Interface Unit (OIU) Recon Tables

k)  Telemetry Occurrence (TOC)

l)  RMS Level C paper DCRs

m)  SSME paper DCRs

n)  SRB/SRM Calibration paper DCRs

o)  Data Integration Plan (DIP) paper DCRs

p)  Special KSC payload/vehicle paper DCRs

q)  Shuttle Data Processing (SDP) Calibration Mod Update paper DCRs

**DRD CONTINUATION SHEET**

**TITLE**: Develop/Evaluate MAST II/STAR Reconfiguration **DRD NO.**:
1.4.3.1-q

Data Change Requests (DCRs)

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 399 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.2-a

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Hardware and Software Test Implementation Plan

7\. **DESCRIPTION/USE**: This document establishes the preliminary plan
for allocating all hardware and software changes to Shuttle Avionics
Integration Laboratory (SAIL) test cases or other alternative
verification method.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Once per Operation Increment (OI); update
as required. Draft Plan Launch minus 349 days (L-349) and Final Plan
Launch minus 293 days (L-293) prior to first flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This plan establishes the method and responsible
organization for verification of each hardware and software changes
associated with the OI software release for which it was developed. A
hardware change that is not associated with a specific OI release will
be submitted with the OI that it will be first flown.

13.2 **APPLICABLE DOCUMENTS**: OI content listings for Primary Avionics
Software System (PASS) and Backup Flight System (BFS) OIs, Multifunction
Electronic Display Subsystem (MEDS) Version Incremements (VIs), Link
content listings for the Miniature Airborne Global Positioning System
(GPS) for Shuttle -- Three String (MAGRS-3S); Software Change Requests
(SCRs); Discrepancy Report (DRs); and Program Requirements Control Board
(PRCB) directives.

13.3 **CONTENTS**: The plan shall include a table of all hardware and
software changes cross-referenced with verification test cases or
alternative verification methods, responsible organizations, and
PASS/BFS/MEDS/MAGRS-3S applicability. The following information shall be
given for each hardware or software change: title, reference SCRs/DRs,
flight software modules affected if applicable, reason for change, and
test requirements. Each proposed test case shall describe the events
necessary to assure verification of the changes addressed in the test.
Anticipated unique SAIL configuration or math model requirements will
also be identified.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 400 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.2-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Avionics Verification Test Requirements Matrix

7\. **DESCRIPTION/USE**: To document the test requirements for the
Shuttle Avionics Software Control Board (SASCB) to baseline.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission from the
SFOC.

10\. **SUBMISSION FREQUENCY**: Base Cycle: once per Operational
Increment (OI) release. Base Patch Cycle: once per flight, or as
required. Base Cycle: Draft - Launch minus 272 days (L-272), Final -
Launch minus 251 days (L-251). Base Patch Cycle: Draft - Launch minus
140 days (L-140), Final - Launch minus 112 days (L-112). Regression and
Site Acceptance, as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document identifies the test cases to be performed
in a test series.

13.2 **APPLICABLE DOCUMENTS**: Software Change Requests (CRs),
Discrepancy Reports (DRs), General Purpose Computer Memory Patches
(GMEMs), Program Requirements Control Board (PRCB) Directives, and
Developmental Test Objectives (DTOs). Data will be available in
databases, FACI/CI/VI datapacks and PRCB minutes.

13.3 **CONTENTS**: The document shall contain a listing of all test
cases to be performed. Included is supporting rationale for the test
including cross-reference to SCRs, DRs, GMEMs, DTOs, or PRCB directive.
Each SCR, DR, GMEM, and applicable PRCB directive shall be
cross-referenced to a Shuttle Avionics Integration Laboratory (SAIL)
test case or alternative verification method. Responsible organizations
and individuals shall be identified for each test case.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 401 **ISSUE**: BASIC 2. **DRD NO.:** 1.4.3.2-c

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Shuttle Avionics Integration Laboratory (SAIL) Test Data
Requirements Document

7\. **DESCRIPTION/USE**: To provide requirements for the generation and
processing of SAIL test data.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Update as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document defines SAIL test data products and
Orbiter Data Reduction Complex (ODRC) processing requirements.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The document shall define post data products, a data
matrix format for requesting these products, and data processing
requirements.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 402 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.2-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Avionics Test Requirements Document

7\. **DESCRIPTION/USE**: To establish the detailed plans for integrated
system level avionics verification, site acceptance, and regression
testing. This document is used to support planning and execution of test
cases.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Once each Operational Increment (OI) and
updated for each flight or as required. Base Cycle: Launch minus 237
days (L-237). Base Patch Cycle: Launch minus 105 days (L-105).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document establishes specific content for Shuttle
Avionics Integration Laboratory (SAIL) test cases or alternate
evaluation methods to be applied in verifying integrated hardware and
software changes to the Space Shuttle.

13.2 **APPLICABLE DOCUMENTS**: OI/VI content listings for Primary
Avionics Software System (PASS), BFS, and MEDS, and Link content
listings for MAGRS-3S; Software Change Requests (SCRs) and Discrepancy
Reports (DRs); Developmental Test Objectives (DTOs) and unique mission
configuration or operational changes; SAIL modifications and math model
changes. Data will be available in databases, MICB minutes, Program
Requirements Change Board (PRCB) minutes, or in SAIL.

13.3 **CONTENTS**: The document shall identify all SAIL verification
test cases to be performed. Supporting rationale is provided, including
cross-reference to applicable SCRs, DRs, DTOs, General Purpose Computer
Memory Patches (GMEMs), flight hardware changes, site modifications, or
regression objects. Alternative verification methodologies are
identified where applicable, and responsible organizations and
individuals are identified for each test case.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 403 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.2-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Avionics Anomaly Reporting and Resolution

7\. **DESCRIPTION/USE**: To report and coordinate resolution of
anomalies observed during Shuttle Avionics Integration Laboratory (SAIL)
testing.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As Required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This documentation encompasses flight hardware and
software discrepancy and interim discrepancy reports, including
information necessary to resolve and disposition the anomalies.

13.2 **APPLICABLE DOCUMENTS**: SAIL anomaly logs, status reports, and
verification test data

13.3 **CONTENTS**: The documentation shall include anomaly logs and
status reports, preliminary resolution analysis findings, and anomaly
closure actions.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 404 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.2-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Avionics Verification Test and Analysis Report

7\. **DESCRIPTION/USE**: To document the test results for all
verification, site acceptance, and regression testing.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSIO**N: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: One after each set of Operational
Increment (OI) tests and one after each set of flight tests. Base cycle
reports will be submitted 90 days following completion of flight cycle
testing for the 1st flight of a new OI. Base Patch cycle reports will be
submitted prior to Launch minus 4 days (L-4).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These reports shall present test results, analysis
results, and conclusions for all test cases or alternate analysis
methods used for verification, site acceptance, or regression testing.

13.2 **APPLICABLE DOCUMENTS**: Shuttle Avionics Integration Laboratory
(SAIL) IDR log, SAIL verification test data.

13.3 **CONTENTS**: The reports shall summarize test and analysis results
by flight phase. Each phase includes a detailed description of the
results and conclusions for each test or analysis performed. Sufficient
data should be presented to verify that the verification objectives have
been met.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 405 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.2-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Avionics Verification Readiness

7\. **DESCRIPTION/USE**: To provide a summary of the verification status
at the Software Readiness Review (SRR).

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Each flight at approximately Launch minus
35 days (L-35) for the Draft and Launch minus 28 days (L-28) for the
Final.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report presents a status of the verification
objectives for a given mission.

13.2 **APPLICABLE DOCUMENTS**: Shuttle Avionics Integration Laboratory
(SAIL) IDR log, SAIL verification test data, Software Production
Facility (SPF) data

13.3 **CONTENTS**: The report summarizes the status of each verification
test case, identifies all known issues resulting from the test, and
presents a plan of resolution for outstanding issues to be resolved
prior to flight.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 406 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Prioritization Recommendation for New Operational
Increment (OI) Build

7\. **DESCRIPTION/USE**: Recommendation is used by NASA in final
determination of the OI/VI content. The input is also used in
development of the Shuttle Avionics Software Control Board (SASCB)
Three-Year Plan presented to the Program Requirements Control Board
(PRCB).

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal annually.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Recommendation considers program goals and
directives to ensure long range flight software planning is in support
of program plans and goals.

13.2 **APPLICABLE DOCUMENTS**: SASCB Three-Year Plan; applicable PRCB
directives.

13.3 **CONTENTS**: The Recommendation includes individual flight
software change proposals (FCPs), software change requests (SCRs), SCR
corrections for software discrepancies (DRs), and priority rationale for
each change, including recommendation for applicability to Primary
Avionics Software System (PASS), Backup Flight System (BFS) and/or MEDS.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 407 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Initialization Load (I-Load) Verification Report

7\. **DESCRIPTION/USE**: To ensure I-Load values in the Flight Software
(FSW) are compatible with specific mission objectives and program
constraints.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal within five weeks
following baseline of I-Loads at the Shuttle Avionics Software Control
Board (SASCB). Launch minus 81 days (L-081).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: I-Load audits are performed for each shuttle mission as
specified in SCR 89054, SASCB Process Documentation: I-Load Data Change
Request (DCR).

13.2 **APPLICABLE DOCUMENTS**:

SCR 89054, SASCB Process Documentation: I-Load Data Change Request (DCR)

13.3 **CONTENTS**: The report contains the approval of each I-Load owner
involved in the audit and identifies any discrepancies found between the
SASCB-baselined I-Load values and the as-built IDS to be applied to the
Mass Memory Unit (MMU).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 408 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-f

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Level 6/7/8 Flight Software Test Plan Recommendation

7\. **DESCRIPTION/USE**: Used to enhance Level 6/7/8 Test Plan content,
and incorporate verification objectives that can be satisfied using
Software Production Facility (SPF) test cases.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Recommendation encompasses all SPF Level 6/7/8
testing performed for a new Operation Increment (OI).

13.2 **APPLICABLE DOCUMENTS**: Preliminary SPF Level 6/7/8 Test Plan

13.3 **CONTENTS**: Recommendations are by test case and include
adjustments to simulation conditions or scenarios.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 409 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Initialization Load (I-Load) Selection and Comparison
Report

7\. **DESCRIPTION/USE**: The I-Load selection and comparison report
identifies any differences in selection between I-Load owners and
initiates the resolution process. Resolution of differences is made
prior to Shuttle Avionics Software Control Board (SASCB) I-Load
approval.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal within one week of the
I-Load Mission Definition Data Change Request (DCR) submittal.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: I-Load selection comparison is performed on each Base
cycle and also for each Base Patch cycle.

13.2 **APPLICABLE DOCUMENTS**: I-Load selections for the Mission
Definition DCR

SCR 89054, SASCB Process Documentation: I-Load Data Change Request (DCR)

13.3 **CONTENTS**: Comparison includes callout of all miscompares
between independent I-Load selections for each category.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 410 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-o

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Program Requirements Documents
(PRDs)

7\. **DESCRIPTION/USE**: To establish the software requirements for the
BFS.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned complete release approximately
12 weeks following Operational Increment (OI) content baseline by the
Shuttle Avionics Software Control Board (SASCB).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The documents cover the software requirements for the
BFS program.

13.2 **APPLICABLE DOCUMENTS**: The Government shall furnish the latest
update of the software change request (SCR) implementation baseline.

13.3 **CONTENTS**: The documents contain the following:

a)  Functional description.

b)  Operational flight program requirements:

    1.  BFS overview.

    2.  Backup System Services (BSS).

    3.  Guidance, Navigation, and Control (GN&C).

    4.  GN&C flight control.

    5.  GN&C hardware interface programs.

    6.  System Management/Special Processes (SM/SP), Payloads (PL).

    7.  Sequencing (SEQ).

c)  Glossary.

d)  Appendices.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 411 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-p

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Primary Avionics Software System (PASS)/Backup Flight
System (BFS) Interface Control Documents (ICDs)

7\. **DESCRIPTION/USE**: To establish the specific technical
requirements of the functional interface between the PASS and the BFS,
and the interface between the Contractor-developed GPC Initial Program
Load (IPL) software and any data systems produced by contract agencies.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents cover the technical requirements of the
interfaces in the following areas:

a)  Functional interface between the PASS and the BFS.

b)  Interface between the General Purpose Computer Initial Program Load
    (GPCIPL) software and data systems or portions produced by
    contracted agencies. The contracted agency developed systems
    include:

    1.  IPL Bootstrap Loader - PASS.

    2.  PASS System Software Loader (SSL) - PASS.

    3.  BFS Backup System Loader (BSL) - BFS.

    4.  Mass Memory Build System.

13.2 **APPLICABLE DOCUMENTS**: The Government shall furnish the latest
update of the Software Change Request (SCR) implementation baseline SCR
or applicable report.

13.3 **CONTENTS**: These documents shall contain the following, as
applicable:

a)  Functional overviews.

b)  General requirements.

c)  Interfaces.

d)  Software loading requirements.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 412 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-q

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Functional Subsystem Software Requirements (FSSRs)
Documents

7\. **DESCRIPTION/USE**: To define flight software requirements for
development team use.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted in accordance
with the System Requirements and Verification Schedule, or as otherwise
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned release approximately
12 weeks following Operational Increment (OI) content baseline by the
Shuttle Avionics Software Control Board (SASCB).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents are applicable to Primary Avionics
Software System (PASS) Flight Software (FSW) requirements and display
requirements for both PASS and Backup Flight System (BFS).

13.2 **APPLICABLE DOCUMENTS**: Software Change Requests (SCRs)
constituting OI baseline.

13.3 **CONTENTS**: The documents contain the following:

a)  Overview.

b)  Detailed requirements:

    1.  GN&C, Part A, Entry Through Landing Guidance.

    2.  GN&C, Part A, Guidance Ascent/RTLS.

    3.  GN&C, Part A, Guidance On-Orbit/De-Orbit.

    4.  GN&C, Part B, Entry Through Landing Navigation.

    5.  GN&C, Part B, Navigation Ascent/Return to Launch Site (RTLS).

    6.  GN&C, Part B, On-Orbit Navigation.

    7.  GN&C, Part C, Flight Control Entry - GRTLS.

    8.  GN&C, Part C, Flight Control, Volume 1, Ascent Flight Phase;
        Volume 2, Ascent.

    9.  GN&C, Part C, Flight Control Orbit DAP.

    10. GN&C, Part D, Redundancy Management.

> 11\. and 12. Not applicable.
>
> 13\. GN&C, Part E, Inertial Measurement Unit Subsystem Operating
> Program.
>
> 14\. GN&C, Part E, Volume 1, Navigation Aids Subsystem Operating
> Program; Volume 2, Star Tracker Subsystem Operating Program.
>
> 15\. GN&C, Part E, Subsystem Operating Programs, Flight Cycle (FC)
> Sensor/Controller.
>
> 16\. GN&C, Part E, Subsystem Operating Programs, FC Effector.
>
> 17\. Remote Manipulator System.
>
> 18\. and 19. Not applicable.
>
> 20\. Volume 1, Displays and Controls; Volume 2, Systems Management;
> Volume 3, Appendices A, B, and F.

**DRD CONTINUATION SHEET**

**TITLE**: Functional Subsystem Software Requirements **DRD NO.**:
1.4.3.3-q

(FSSRs) Documents

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

> 21\. through 25. Not applicable.
>
> 26\. GN&C, Sequencing.

c)  Supplemental Material.

d)  Appendices.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 413 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-s

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Initialization Load (I-Load) Selection Criteria Databook

7\. **DESCRIPTION/USE**: To establish contractor\'s selection criteria
for I-Load usage within a given Operational Increment (OI).

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal once per OI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The document encompasses all GN&C and Sequencing
I-Loads.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Databook shall contain I-Load categories and
occurrences with historical information, rationale for selection, and
interrelationships between I-Loads and categories.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 414 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-t

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Parameter Database

7\. **DESCRIPTION/USE**: To maintain consistency between flight data
parameters.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As requested

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The database includes all flight software parameters and
measurements.

13.2 **APPLICABLE DOCUMENTS**: Shuttle Avionics Software Control Board
(SASCB) approved changes which affect data or measurement
characteristics.

13.3 **CONTENTS**: The database includes input/output parameters by
principal function, with data type, frequency, precision, and parameter
title.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by SASCB
approval of SCRs affecting flight data parameters.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 415 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-u

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Logic Documentation

7\. **DESCRIPTION/USE**: To document, in flowchart form, the logic
design of the Primary Avionics Software System (PASS) and Backup Flight
System (BFS) GN&C Sequencing and Redundancy Management (RM) Flight
Software (FSW).

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal for each FSW
Operational Increment (OI) baseline release.

11\. **REMARKS**: None.

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The document shall provide a detailed description, in
logic flowchart form, of the PASS and BFS GN&C Sequencing and RM FSW.
Logic flowcharts depicting the FSW design for each release will be
provided.

13.2 **APPLICABLE DOCUMENTS**: Initial copy of electronic files of the
three documents reflecting current configuration.

13.3 **CONTENTS**:

a)  PASS GN&C Sequencing:

    1.  Section 1: Introduction.

    2.  Section 2: Summary.

    3.  Section 3: Sequencing principle.

    4.  Section 4: Change history.

b)  BFS GN&C Sequencing:

    1.  Section 1: Introduction.

    2.  Section 2: Summary.

    3.  Section 3: BFS sequencing functions.

    4.  Section 4: Backup event controller.

    5.  Section 5: Change history.

c)  RM FSW:

    1.  Section 1: Introduction.

    2.  Section 2: Summary/overviews.

    3.  Section 3: Detailed sequencing principle functions.

    4.  Section 4: Change history.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 416 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-w

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Space Shuttle Computer Program Development Specifications
(Six Volumes)

7\. **DESCRIPTION/USE**: Primary Avionics Software System (PASS) flight
software Level A (System) and Level B (Functional) requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Once per Operational Increment (OI) of
the flight software to be published by FACI with subsequent updates as
required to maintain a document with current requirements.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.3

13\. **DATA PREPARATION INFORMATION**: Delivery may be by publication of
the complete document or Page Change Notice (PCN) depending on the
magnitude of the changes.

13.1 **SCOPE**: Defines the PASS Level a (System) and Level B
(Functional) software requirements for the Orbiter General Purpose
Computers.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Contains the PASS flight software requirements for
the System Software- Operating System and User Interface,
Downlist/Uplink, Launch Data Bus and the functional level requirements
for the applications - Guidance Navigation and Control (GN&C), Systems
Management (SM), and Vehicle Utility (VU) as defined in the following
documents:

SS-P-0002-140 SS Downlist/Uplink Software Requirements

SS-P-0002-150 SS LDB Software Interface Requirements

SS-P-0002-170 SS System Level A Software Requirements

SS-P-0002-510 SS Functional Level Requirements, GN&C

SS-P-0002-550 SS Functional Level Requirements, Vehicle Utility

SS-P-0002-580 SS Functional Level Requirements, Systems Management

Each document contains the requirements in the Software Change Requests
(SCRs) approved by the Shuttle Avionics Change Control Board (SASCB).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 417 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-x

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Engineering DCE Support for SASCB Change Reviews

7\. **DESCRIPTION/USE**: Defines the products delivered in support of
Engineering review of New Design/Development, Non-Transitioned, and
I-Load DCRs.

8\. **DISTRIBUTION**:

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Weekly in support of the Engineering
Change Review Board (CRB) and Shuttle Data Control Board (SDCB).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SASCB and SDCB agendas.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These products are required for the operation of the
Engineering DCE/NSE review process and Engineering Change Review Board.

13.2 **APPLICABLE DOCUMENTS**: STAR and MAST Data Integration Plan (vol.
I & III) and I-Load Data Change Request SCR 89054

13.3 **CONTENTS**:

a)  DCR Analysis Reports - Definition and entry of STAR and MAST II DCR
    reports for vehicle data and transmittal to JSC those designated as
    requiring Engineering DCE review

b)  I-Loads Definitions/Review - Definition and entry of I-Loads DCRs
    into STAR as required for Engineering I-Load owners and transmittal
    to JSC of each I-Load DCR designated as requiring Engineering DCE
    review.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 418 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-y

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Develop/Evaluate Flight Software (FSW) Change Documents

7\. **DESCRIPTION/USE**: To request a change or document a discrepancy
in the Flight Software or associated software development tools.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Flight Software change documents are used to request a
change to the Primary Avionics Software System (PASS), Backup Flight
System (BFS) Software, Multifunction Electronic Display Subsystem
(MEDS), Miniature Airborne Global Positioning System (GPS) for Shuttle
-- Three String (MAGRS-3S), main engine controller software, Flight
Software development tools, or the Flight Software Initialization Loads
(I-Loads). The Discrepancy Report is used to document discrepancies
found in delivered software or associated tools.

13.2 **APPLICABLE DOCUMENTS**:

SASCB Three-Year Plan

Program Requirements Control Board (PRCB) Directives

Mission manifests

Flight Production Schedules Working Group (FPSWG) directives

Software Change Requests (SCRs)

Shuttle Avionics Integration Laboratory (SAIL) Interim Discrepancy
Reports (IDRs)

Computer Program Development Specification (CPDS)

Functional Subsystem Software Requirements (FSSR)

BFS Program Requirements Document (PRD)

PASS/BFS Interface Control Document (ICD)

SCR 89050 SASCB Process Documentation Overview

13.3 **CONTENTS**: The following FSW change documents are included:

a)  Flight Software Change Proposal (FCP)

b)  Software Change Request (SCR)

c)  Discrepancy Report/Requirements Issue Tracking (DR/RIT)

d)  I-Load Data Change Request (DCR)

e)  Software Authorization Notice (SAN)

f)  Requirement Change Notice (RCN)

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 419 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-ab

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Mapping of Principal Functions and I-Load Categories to
Baselined Hazard Reports

7\. **DESCRIPTION/USE**: Used to determine impacts to baselined hazard
reports from Software Change Requests, Discrepancy Reports and I-Load
Data Change Requests.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Mapping restricted to PASS and BFS Principal Functions,
and I-Load categories that Contractor provides ownership. Contractor
responsibilities for I-Load Categories are defined in SASCB SCR 98032
and responsibilities for Principal Functions are defined in SCR 98350.

13.2 **APPLICABLE DOCUMENTS**:

a.  SCR 98032, FSW I-Load Owner Assignments

b.  SCR 98350, FSW Requirements Management Assessment Baseline

13.3 **CONTENTS**: File containing correlation of Principal Functions
and I-Loads to baselined hazard reports.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 420 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.3-ac

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Data Processing System (DPS) Principles of
Operation (POO) Document Updates

7\. **DESCRIPTION/USE**: To document the design, interfaces, and POO of
the Shuttle Integrated DPS, including Multi-functional Electronic
Display Subsystem (MEDS), for knowledge capture, analysis, and training
purposes.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The document shall provide a detailed description of the
DPS of the Space Shuttle Avionics (including MEDS), including major
element interfaces, controls, and user operations of the subsystem.

13.2 **APPLICABLE DOCUMENTS**:

MEDS POO

13.3 **CONTENTS**: The update shall consist of three sections:

a)  Overview, providing the necessary orientation and background.

b)  Definition of the configuration, modes of operation, and performance
    characteristics of the modified DPS System with the emphasis on user
    operations characteristics.

c)  Description of the characteristics of the DPS User Operations
    Interface.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 421 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.4-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Reconfiguration Deliverables

7\. **DESCRIPTION/USE**: The BFS Flight Software (FSW) deliverables and
supporting documentation are provided to the FSW community in support of
Shuttle missions.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required to support reconfiguration
concurrent with delivery of each Software End Item designed as a
Configuration Item (CI).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Deliverables include the BFS FSW datasets, FSW tapes,
optical disk or applicable device, and applicable documentation.

13.2 **APPLICABLE DOCUMENTS**

JSC 08338 Shuttle Avionics Mass Memory Unit Computer Program Integration
Plan (MIP)

13.3 **CONTENTS**: Release of BFS flight software includes products
specified in the Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP), JSC 08338.

13.4 **FORMAT**: Products will be generated in the formats described in
the MIP, JSC 08338. MIP contents are under configuration control by the
SASCB.

13.5 **MAINTENANCE**: In the event that changes are required to the
previously deliverable software items, the products will be revised and
redelivered with the appropriate documentation.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 422 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software Configuration
Inspection Report/Briefing

7\. **DESCRIPTION/USE**: This report/briefing presents to NASA the
delivery of the Operational Increment (OI) software milestone. It
officially documents the completion of the development and verification
of the BFS software to assure the customer that the software was
developed per the requirements and is ready to support Shuttle missions.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR) or
designated representative, with planned submittal at Configuration
Inspection (CI) which is negotiated at the Shuttle Avionics Software
Control Board (SASCB).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Backup Flight System (BFS) Software Configuration
Inspection Report/Briefing describes the development process, the
verification process and results, and configuration control performed in
support of a new FSW OI.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: This report/briefing shall contain a summary of both
Flight Software and Flight Software Application Tools and status of all
software changes, Discrepancy Reports, waivers and user notes,
verification testing and certification related to a specific OI system.
It will include a summary of processes leading to CI and will identify
any open work post CI. At a minimum the report/briefing shall include:

a)  An overview of the OI history and new major capabilities.

b)  Identification of each SCR/SSCR and DR/SSDR change applied to the
    OI.

c)  Summary of all FSW and FSWAT Ops Notes, User Notes, and Waivers
    deleted and still applicable to this OI.

d)  Summary of all verification and performance testing for this OI and
    test mapping to SCRs and DRs.

e)  Status of all open DR\'s applicable to this OI.

f)  Summary of open items.

g)  Summary and status of quality metrics historically and for this OI.

h)  Briefing Package.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 423 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software Standards and
Procedures Manual (SSPM)

7\. **DESCRIPTION/USE**: To document BFS tasks and duties, including
work procedures, checklists, and general information for all functional
areas of the BFS project.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: The SSPM will be released once a year in
February. Procedure Change Notices (PCNs) will be released on a monthly
basis as deemed necessary. Full revisions as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The SSPM contains standards and procedures used during
the development of all Computer Software Configuration Items (CSCIs)
developed by the Software Engineering department.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Software Standards and Procedures Manual contains
work procedures, checklists, forms, and general information used to
develop CSCIs for the following:

a)  Backup Flight System (BFS).

b)  General Purpose Computer Initial Program Load (GPCIPL).

c)  Backup System Loader (BSL).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 424 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software Change Request (SCR)
Risk Assessment Analysis/Report

7\. **DESCRIPTION/USE**: To assess the risk of changing the existing
code to implement the requested change.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required to support Software Change
Requests (SCRs) for all code changes

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report evaluates the risk of implementing the
change in terms of size, complexity, criticality, and manpower utilized.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The report shall contain:

a)  Summary of benefits.

b)  Estimated size of change.

c)  Complexity.

d)  Criticality.

e)  Code paths.

f)  Failures.

g)  Operational phases.

h)  New or existing code.

i)  Area of code last changed.

j)  Manpower impact.

k)  Testability.

l)  Other comments.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 425 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup System Loader (BSL) Computer Program Description
Document

7\. **DESCRIPTION/USE**: To support software maintenance of the BSL,
under configuration control.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document defines the requirements and functions of
the BSL. This software is transferred from the Mass Memory Unit (MMU) to
the General Purpose Computer (GPC) \[by the GPC Initial Program Load
(GPCIPL) program\] when the Backup Flight System (BFS) Program Load
function is initiated by the crew during GPCIPL. The BSL shall (1)
manage the resources of the GPC communicating with the MMU; (2)
communicate with the display processor; (3) load the BFS; (4) pass
control to the BFS after BFS is loaded upon user request, and (5)
enunciate all detected errors.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The BSL Computer Program Description Document shall
contain:

a)  Scope: describes the usage and provides a functional summary of the
    BSL computer program.

b)  Applicable documents: covers both Government and non-Government
    documents.

c)  Requirements: defines computer program, interface requirements, part
    numbers and labeling, and tape delivery format.

d)  Detailed functional requirements: covers real-time processor,
    real-time control, GPC initialization, BSL interrupt handling/error
    logging, display processor interface, display processor poll,
    display processor poll response, display processor update, Mass
    Memory interface, GPCIPL interface, BFS interface, and BFS MMU build
    system interface.

e)  Quality assurance: includes provisions for quality assurance
    (verification and validation).

f)  Deliverables: covers provision for delivery (including deliverables
    definition).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 426 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: General Purpose Computer Initial Program Load (GPCIPL)
Program Requirements Document

7\. **DESCRIPTION/USE**: To establish the requirements for performance,
design, and verification of the GPCIPL programs.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document establishes the requirements for design
and development of the GPCIPL program. The GPCIPL is used to determine
the operational readiness of the General Purpose Computer (GPC), to
initiate the loading of Flight System Software and to control and
monitor memory purge operations. The Flight System Software consists of
either the Primary Avionics Software System (PASS) or Backup Flight
System (BFS) software.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The GPCIPL Program Requirements Document shall
contain (as applicable):

a.  Architecture:

    1.  Input/Output (I/O) interfaces.

    2.  Data pools.

    3.  Flow charts.

b.  Program:

    1.  Functional overview.

    2.  Program structure requirements.

    3.  Initialization requirements.

    4.  Tables of hardware elements and instructions.

    5.  Functional diagrams.

c.  Engineering Orders (EOs)

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 427 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Operational Increment (OI)
Deliverables

7\. **DESCRIPTION/USE**: The BFS OI products will be delivered for use
by the reconfiguration organization for production of training and
flight loads in support of Shuttle missions.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BFS OI Deliverables consist of the FSW and FSW
Applications Tools software and products required for execution of the
flight to flight reconfiguration processes.

13.2 **APPLICABLE DOCUMENTS**:

JSC 22320, Class 1 Integration Plan (CIP)

13.3 **CONTENTS**: Includes all deliverable products specified in the
FSW Class 1 Integration Plan (CIP), JSC 22320, as deliverables for each
OI.

13.4 **FORMAT**: Products will be generated in Software Development
Facility (SDF) datasets per the formats described in the CIP. The CIP
contents are under configuration control by the SASCB.

13.5 **MAINTENANCE**: In the event that changes to the previously
delivered software items are required, the products will be revised and
redelivered with the appropriate documentation.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 428 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) High-order Assembly
Language/Shuttle (HAL/S) Compiler Audit Reports

7\. **DESCRIPTION/USE**: To provide analysis of audit results on the BFS
Flight Software for problems found in the HAL/S compiler.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BFS HAL/S Compiler Audit Reports document audit
criteria (if applicable), audit results, and analysis of audit results
performed on the BFS Flight Software per Compiler Change Requests and
Compiler Discrepancy Reports.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Compiler Audit Form shall contain:

a)  Document number.

b)  Audit date.

c)  Compiler version.

d)  BFS Flight Software version and Operational Increment (OI) number.

e)  Document title.

f)  Audit criteria.

g)  Audit results/analysis.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 429 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-i

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Discrepancy Report (DR)
Analysis

7\. **DESCRIPTION/USE**: Detailed DR analysis and recommended
disposition for DR\'s written against the BFS Flight software are
documented on a BFS DR Analysis Form. A summary of the technical
analyses and recommended closure disposition with supporting rational is
documented on a FSW DR Management Form. Both of these are provided to
NASA for review and concurrence/approval.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each DR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BFS Discrepancy Report Analysis and DR Management
Form documents the evaluation of a problem or anomaly and recommended
disposition.

13.2 **APPLICABLE DOCUMENTS**:

SCR 89052 Space Shuttle Flight Software Discrepancy Report Procedures

13.3 **CONTENTS**: Contents of the DR Management Form are defined in SCR
89052, Space Shuttle Flight Software Discrepancy Report Procedures. The
DR Analysis Form shall contain:

a)  Title/DR number.

b)  Description of problem.

c)  How user sees effects.

d)  Requirement violated/inadequacy.

e)  Testing required.

f)  Rationale for disposition.

g)  Process Improvement.

h)  Analysis.

i)  Workaround/recovery procedure.

j)  Functional area.

k)  Implementation impact.

l)  Additional information.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 430 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-j

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Backup System Loader (BSL) Program Requirements Document

7\. **DESCRIPTION/USE**: To establish the requirements for performance,
design, and verification of the BSL.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BSL Program Requirements Document describes the
functions and organization of the BSL program including interrupt
handling, executive, display processor interface, and Mass Memory Unit
(MMU) interface.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The document shall contain the following, as
applicable:

a.  Architecture:

    1.  Input/Output (I/O) interfaces.

    2.  Data pools.

    3.  Flow charts.

b.  Program descriptions:

    1.  Functional overview.

    2.  Program structure.

    3.  Initialization.

    4.  Tables.

    5.  Flow charts.

c.  Engineering Orders (EOs)

The following sections will be included in the document:

a)  Scope: covers identification and tape delivery format.

b)  Applicable documents: includes Government and non-Government
    documents.

c)  Requirements: includes General Purpose Computer (GPC) architecture,
    GPC interrupt structure, GPC I/O (Input/Output Processor) structures
    , BSL overview, overview summary, and IPL MENU selection and usage.

d)  Functional description: describes real-time processor, interrupt
    handlers, real-time executive which includes the following: display
    poll routine (CIM 4 POLL); display processor response analysis
    routine (POLLRSP), IOP interface master sequence controller
    programs, IOP Scheduler (MSCINTF), Mass Memory (MM) I/O handlers
    (MSCINTF2); data bus I/O control (DBCNTL), the MM I/O interface for
    the BSL foreground processing routine (BSL2F), and BSL background
    processing routine (BSL2B), BSL control transfer routine (MOVEPSA),
    GPC Initial Program Load (GPCIPL) interface, and MMU build system
    interface.

**DRD CONTINUATION SHEET**

**TITLE**: Backup System Loader (BSL) Program **DRD NO.**: 1.4.3.5-j

Requirements Document

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

e)  BSL error/advisory message

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 431 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-k

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: General Purpose Computer Initial Program Load (GPCIPL)
User\'s Guide

7\. **DESCRIPTION/USE**: To provide utilization information relative to
the GPCIPL operations and capabilities.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The GPCIPL User\'s Guide provides an overview of
software capabilities including descriptions of the GPCIPL services,
operating system, and control operations. Also included is information
relative to the orbiter\'s cabin controls (switches, etc.) as they
affect operations of the GPCIPL.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The document shall contain the following:

a)  GPCIPL overview.

b)  GPCIPL capabilities overview.

c)  Displays description including hardware/software interfaces.

d)  Switches description.

e)  Fault annunciation and messages description.

f)  Downlist description.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 432 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-l

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: General Purpose Computer Initial Program Load (GPCIPL)
Computer Program Description Document

7\. **DESCRIPTION/USE**: To support software maintenance of the GPCIPL
program under configuration control.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The GPCIPL Computer Program Description Document defines
the requirements and functions of the GPCIPL. This software is
transferred from the Mass Memory Unit (MMU) to the General Purpose
Computer (GPC) by the Bootstrap Loader when IPL is initiated by the crew
during GPCIPL. The GPCIPL shall (1) manage the resources of the GPC
communicating with the MMU; (2) communicate with the display processor;
(3) load the Backup Flight System (BFS); (4) pass control to the Backup
System Loader (BSL) after the BSL is loaded at user request; and (5)
enunciate all detected errors.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The document shall contain the following:

a)  Scope: describes the usage and provides a functional summary of the
    GPCIPL computer program.

b)  Applicable documents: covers both Government and non-Government
    documents.

c)  Requirements: defines computer program, interface requirements, part
    numbers and labeling, and tape delivery format.

d)  Detailed functional requirements: covers real-time processor,
    real-time control, GPC initialization, GPCIPL interrupt
    handling/error logging, display processor interface, display
    processor poll, display processor poll response, Mass Memory
    interface, BSL interface, Primary Flight System (PFS) interface, and
    BFS MMU build system interface.

e)  Quality assurance: includes provisions for quality assurance
    (verification and validation).

f)  Deliverables: covers provisions for delivery (including deliverables
    definition).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 433 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-m

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Program Description Documents
(PDD\'s)

7\. **DESCRIPTION/USE**: To support software maintenance of the Backup
Flight System under configuration control.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BFS Program Description Documents provide a
description of the program structure and logic flow of the program code
which implements the specific requirements of the Backup Flight System
for each of the following major functional areas:

a)  Guidance, Navigation, and Control (GN&C).

b)  System Management/Special Processes (SM/SP) and Payloads.

c)  Sequencing (SEQ).

d)  Backup System Services (BSS).

e)  Displays and Control (D&C).

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The documents shall contain the following, as
applicable:

a)  Architecture:

```{=html}
<!-- -->
```
1.  Input/Output (I/O) interfaces.

2.  Data pools.

3.  Flow charts.

```{=html}
<!-- -->
```
b)  Program Descriptions:

```{=html}
<!-- -->
```
1.  Functional overview.

2.  Program structure.

3.  Initialization.

4.  Tables.

5.  Flow charts.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 434 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-n

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Coding Standards Document

7\. **DESCRIPTION/USE**: To identify software programming standards
utilized in the development and testing of the BFS.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BFS Coding Standards Document provides a compilation
of both BFS programming and supporting standards that define the
function, implementation, and compliance control of each standard.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The documents shall contain categorized standards
consisting of the following:

a.  Coding standard identification number: The following categories,
    under which the coding standards are placed during the compilation
    process, are assigned an upper case letter as follows:

    1.  A - standards pertaining to error detection, prevention, and
        recovery.

    2.  B - standards imposed by the programming language.

    3.  C - standards that represent good programming practices.

    4.  D - standards imposed by system requirements.

    5.  E - standards pertaining to patches.

b.  Coding standard statement: describes the rationale for the
    assignment of the coding standard.

c.  Applicable language.

d.  Implementation methods.

e.  Compliance control procedures, as applicable.

f.  Remarks applicable to the standard.

g.  Auditing classifications: assigned to the coding standards as
    follows:

    1.  Mandatory - must be followed.

    2.  Guideline - desirable but not mandatory (improves visibility,
        readability, etc.).

    3.  Compiler or pilot imposed (e.g., will not compile if violated).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 435 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-o

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Backup Flight System (BFS) User\'s Guide

7\. **DESCRIPTION/USE**: To be used as a training and testing aid
providing information relative to the Backup Flight System\'s operation
and capabilities.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with the planned submittal prior to the first
flight of the Operational Increment (OI).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The BFS User\'s Guide provides an overview of software
capabilities including descriptions of the backup system services;
backup operation system; guidance, navigation, and control operations;
and those operations classified as systems management/special processes
and sequencing. Also included is information relative to payload
support.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The document shall contain the following:

a)  Backup Flight System Overview: includes the BFS purpose, PFS/BFS
    hardware configuration overview, BFS capabilities, PFS/BFS interface
    and interactions, BFS software structure, and BFS functional
    summary.

b)  Backup Flight System Capabilities Overview: includes the Operational
    Sequences (OPS) and Major Modes (MM) description; BFS general
    description; mass memory interface; system initialization; and BFS
    crew functional and hardware interfaces.

c)  Displays Description including hardware/software interfaces: for
    dedicated indicators and controls and Cathode Ray Tube (CRT)
    displays.

d)  Dedicated Displays Description: addresses the attitude director
    indicator, alpha/mach indicator, altitude vertical velocity
    indicator, horizontal situation indicator, and surface position
    indicator.

e)  Data Processing System: provides selected information concerning the
    Shuttle Data Processing System (DPS). Emphasis is to be placed on
    the various data buses and their operating characteristics.

f)  Caution, Warning, and Alert System Description: the BFS Fault
    Detection and Annunciation (FDA) function will primarily support the
    backup C&W and SM alert systems. The BFS FDA is to monitor specified
    parameters from Guidance, Navigation and Control (GN&C), Backup
    System Services (BSS), and System Management/Special Processes and
    Sequencing (SM/SP&S).

**DRD CONTINUATION SHEET**

**TITLE**: Backup Flight System (BFS) User\'s Guide **DRD NO.**:
1.4.3.5-o

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

Backup Flight System Downlist: the downlist is to be the name of a major
communication link between the Space Shuttle Orbiter and the ground
support equipment. The purpose of the downlist description is to
identify precisely the usage of each 16-bit word in the downlist format.
This will be accomplished with the master measurement database, the
downlist matrices, and the BFS downlist word definitions.

Payload Overview: includes payload support functions used on Orbiter
flight which require payload support. Consists of payload management,
FDA, scaling, display, and downlist processing.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 436 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-p

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Backup Flight System (BFS) Test Coordination Team (TCT)
Test Specifications and Performance Test Review (PTR) (Level 7)

7\. **DESCRIPTION/USE**: The BFS TCT test specifications identify the
performance test procedures that will be performed on a particular
Operational Increment (OI) and are used by the FSW technical community
to assure the accuracy of the BFS FSW performance verification approach.
The Level 7 PTR provides the FSW technical community with a summary of
the Level 7 performance testing, identifies variances to the procedures,
and any ongoing work/investigations.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSIO**N: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned delivery of the TCT Test Plan no
later than four weeks prior to First Article Configuration Inspection
(FACI) in support of the TCT briefing which is held no later than one
week prior to FACI. The PTR briefing is conducted no later than 1.5
weeks prior to CI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The TCT test specifications identify the performance
test procedures and specifications to be exercised for the OI. The PTR
provides the FSW technical community with a summary of the outcome of
performance testing. Both of these are presented to the FSW technical
community in the form of a briefing.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 08271, Flight and Ground Software Verification and Validation
Requirements

13.3 **CONTENTS**:

a.  Level 7 performance testing is categorized into three areas:
    Capability, Stress and Integrity testing. Each Level 7 Test
    Specification shall include:

    1.  Identification name for the test case.

    2.  Title/Description of the test case.

    3.  Principal functions tested.

    4.  Major Mode being tested.

    5.  Test Objectives.

    6.  Testing Approach.

**DRD CONTINUATION SHEET**

**TITLE**: Backup Flight System (BFS) Test Coordination **DRD NO.**:
1.4.3.5-p

Team (TCT) Test Specifications and Performance

Test Review (PTR) (Level 7)

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

b.  The PTR shall contain:

    1.  Software configuration.

    2.  Software versions.

    3.  Performance test plan.

    4.  Software Change Requests (SCRs) tested.

    5.  SCR test matrix.

    6.  Software patch test configuration.

    7.  Flight software anomalies.

    8.  Miscellaneous anomalies.

    9.  Open items.

    10. Performance test report summaries.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 437 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-q

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Functional Test Reports (Level
6)

7\. **DESCRIPTION/USE**: Functional Test Reports document the results of
the Level 6 testing. These are provided to, and accepted by, NASA as a
certification that the delivered software conforms to NASA approved
requirements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned delivery no later than six weeks
prior to Configuration Inspection (CI).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The report shall contain the approved changes that were
to be tested, the test procedure, test data, and a statement by the
tester on the success of the test.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 08271 Flight and Ground Software Verification and Validation
Requirements

13.3 **CONTENTS**: Each report shall contain:

a)  Test procedure.

b)  Software Modification Sheet (SMS), Software Change Request (SCR),
    and/or Discrepancy Report (DR).

c)  Test on-line output.

d)  Post-processed data.

e)  Test summary sheet.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **DRL NO.**: 438 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-r

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Performance Test Reports
(Level 7)

7\. **DESCRIPTION/USE**: Level 7 test results are provided to, and
reviewed by, the FSW technical community to determine correct
performance of the software prior to CI software acceptance.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned delivery no later than six weeks
prior to Configuration Inspection (CI) for new OI releases and no later
than four weeks prior to launch for flight-specific configured loads
other than Complementary Loads, if required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Each report contains the results of each performance
test as specified in the Test Coordination Team test specifications (DRD
1.4.3.5-p).

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The report shall contain:

a)  Test specification and procedure.

b)  Software anomalies.

c)  Miscellaneous anomalies.

d)  Test configuration.

e)  Patch summary description.

f)  Summary tables.

g)  Pass/fail performance summary.

h)  Appendices of plotted data.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 439 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-s

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Software First Article
Configuration Inspection (FACI) Report/Briefing

7\. **DESCRIPTION/USE**: This report/briefing presents to NASA the
status of the OI software development release in preparation for the
start of verification activities and officially reports the
contractor\'s OI development completion of baselined requirements.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal at FACI which is
negotiated at the Shuttle Avionics Software Control Board (SASCB).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Covers the results of all Flight Software development
activities and the development testing performed prior to the release of
the OI software for verification.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: This report/briefing shall contain both Flight
Software and Flight Software Application Tools summary and status of all
software changes, Discrepancy Reports, waivers and user notes, major
capability changes, and the Level 6 and Level 7 verification plans
related to a specific OI system. It will include a summary of processes
leading to FACI and will identify any planned post FACI development
work. At a minimum the report shall include:

a)  Schedule.

b)  Baseline/build genesis.

c)  Identification of each SCR, DR, SSCR, and SSDR change applied to the
    OI system.

d)  Development and development test summary leading up to FACI.

e)  Summary and description of all FSW and FSWAT Waivers and Operations
    Notes deleted by this OI and still applicable to this OI.

f)  Open Issues.

g)  Identification of all post FACI open work including opening DRs
    potentially applicable to the OI.

h)  Summary and status of the quality metrics historically and for this
    OI.

i)  Identification of the Level 6 and 7 Verification plans.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 440 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-u

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Development/Verification
Report

7\. **DESCRIPTION/USE**: Provides a status of the BFS development and
verification activities for Operational Increments (OIs) and
Reconfiguration loads.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Report shall be submitted monthly, with
submission deadline as negotiated with the Contracting Officer\'s
Technical Representative (COTR), or designated representative, in
support of the scheduled BFS Development/Verification Status Meeting.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report shall include status of both BFS and General
Purpose Computer Initial Program Load/Backup System Loader (GPCIPL/BSL)
effort.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Backup Flight system (BFS)
Development/Verification Report shall include at a minimum the
following. Changes to the content can be negotiated with the Contracting
Officer\'s Technical Representative (COTR), or designated
representative.

a.  General Information

    1.  HAL/S Compiler Issues

    2.  General Operational Increment (OI) Planning

b.  Development/Verification Status for each OI Currently in Development
    or Field Use

    1.  OI schedule, including Change Request Baseline, build dates,
        First Article Configuration Inspection, Level 6 and Level 7
        Verification Complete, Configuration Inspection, Level 7
        Reviews, and other relevant milestones

    2.  Development Status, including build contents (SCRs and DRs
        incorporated) and issues

    3.  Integration Testing Status, including schedules and issues

    4.  Level 6 Testing Status, including schedules, issues, and a
        summary which shows status of all test procedures and test cases

    5.  Level 7 Testing Status, including schedules, issues, and a
        summary which shows status of all performance test cases

c.  Status of reconfiguration loads

d.  BFS Issues and Concerns

e.  Special Topics

f.  Action Items

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: No maintenance requirements.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 441 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.5-v

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Backup Flight System (BFS) Mass Memory Universal Patch
Format (UPF) Patch

7\. **DESCRIPTION/USE**: A BFS UPF Patch is used to modify the BFS Mass
Memory without altering the established memory maps.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required following approval by the
Shuttle Avionics Software Control Board (SASCB) authorizing Software
Change Request (SCR) or Discrepancy Report (DR).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.5

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Provides a means of delivering modifications to the BFS
software to an end user. The development and delivery of the patch
requires a NASA approved Flight Software SCR or DR.

13.2 **APPLICABLE DOCUMENTS**:

JSC 08338 Shuttle Avionics Mass Memory Unit Computer Program Integration
Plan (MIP)

13.3 **CONTENTS**: BFS flight software UPF patch contents and products
are specified in the Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP), JSC 08338.

13.4 **FORMAT**: Products will be generated in the formats described in
the MIP, JSC 08338. MIP contents are under configuration control by the
SASCB.

13.5 **MAINTENANCE**: None Required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 442 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Progress Report

7\. **DESCRIPTION/USE**: To be used for monitoring of the progress,
significant accomplishments, major activities, problems, and corrective
actions.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Progress Report will be submitted monthly
on the 18th.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7, 1.4.3.8, 1.4.3.9, 1.4.3.10,
1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Covers all work accomplished during each month of
contract performance.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: A progress report shall include but not be limited to
the following.

A quantitative description of overall progress, including:

a)  Identification of current problems which can impede the scheduled
    progress or jeopardize the quality or any technical objectives and
    the proposed or implemented corrective action.

b)  Identification of all deliveries and significant activities for the
    last month including specific statement of the schedule performance
    for each deliverable.

c)  Updated program schedules. With a discussion of the work to be
    performed during the next monthly reporting period.

d)  Topical discussion of significant activities within the categories
    of Flights, Operational Increments, Facility Support, Flight
    Software, Flight Software Application Tools, and General.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 443 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Management Plan

7\. **DESCRIPTION/USE**: To describe the software contractor's approach
to managing the development of Orbiter software and to specify internal
procedures and interfacing NASA procedures.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: The Software Management Plan will be
released annually.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7, 1.4.3.8, 1.4.3.9, 1.4.3.10,
1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Defines the overall process expected of the software
contractor in support of Space Shuttle Orbiter avionics software
development from initiation through completion of each software element
delivery.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**:

a)  Contractor's approach to accomplishing the delivery of Shuttle
    software in the following areas:

```{=html}
<!-- -->
```
1.  Organization definition, responsibilities, and management controls

2.  Detailed software development process description for Shuttle
    onboard FSW and for ground FSWAT tools

3.  Configuration management description of control processes and
    automated tools

4.  Configuration accounting documents use and handling

5.  Delivery procedures for FSW and FSWAT end items

6.  Deliverable items definition

7.  Reconfiguration activities for flight-to-flight builds

```{=html}
<!-- -->
```
b)  Contractor's detailed verification plan, including specific methods
    to accomplish the following:

```{=html}
<!-- -->
```
1.  Independent verification to assure that the software is
    mathematically and logically correct

2.  Show that valid software results exist throughout the expected
    performance range of the established requirements

3.  Plans for verification or reverification following software changes
    during code and test and during formal verification

4.  Traceability to test requirements and repeatability of verification
    test results

5.  Procedures and interfaces associated with ensuring software
    conformance to the appropriately authorized configuration management
    data base

6.  Interfaces with NASA

7.  Adherence to NSTS 08271 verification and validation requirements

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 444 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-c

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Computer Resource Requirements and Utilization

7\. **DESCRIPTION/USE**: To provide a basis to plan for computer
resources.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products will be produced every 6 months.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Identifies the SRF & SDF mainframe and network computer
resources required by the contractor and provided by the Government.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: A computer utilization forecast with identification
of estimated resource use for the next 24 months and actual usage
compared to projected for the past 12 months.

The contractor shall collect and report to the one month granularity
both computer resource requirements and past actual usage. Each report
shall include a 12-month past history, a next 6-month projection and a
next 2 year projection of needs.

The reported resource needs shall include:

a)  Terminal connect session per week

b)  Short, Medium, and Long Batch jobs per week

c)  Tape mount jobs per week

d)  Short, Medium, and Long IMS jobs per week

e)  Local and Remote print support in thousands of lines per week

f)  DASD storage in megabytes average over the month

g)  Tape volumes in library during month

h)  FEID single, dual, and triple string jobs per week

i)  FEID connect hours per month

j)  Other categories as defined by NASA

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 445 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Development Plan

7\. **DESCRIPTION/USE**: To provide project and functional area
management with the level of detail into plans, schedules, and status
information necessary for proper control and direction of effort in all
areas of the project.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted monthly.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7, 1.4.3.9, 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The development plan shall describe the major managed
deliverables and milestones for the overall performance and status of
work efforts assigned to each task order.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Individual development plans from the task order
areas shall be combined into a project wide development plan containing
actions, issues, deliverables, and milestones to a level of detail which
provides NASA an accurate status of all products. The development plan
shall include but is not limited to:

a)  Shuttle flight schedule history and plan with an OI to flight
    mapping

b)  Flight-to-flight release schedule for each mass memory load being
    planned

c)  Action item assignments and due dates

d)  Detailed reconfiguration schedule for each flight

e)  Detailed schedule for all builds and milestone points in OI
    development

f)  OI development issues and actions tracking

g)  OI Level 6 and 7 detailed status of testing

h)  Contractor actions to write SCRs

i)  Compiler audit schedules and status

j)  Training development plans and schedules

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 446 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Configuration Management Report (CMDB Report)

7\. **DESCRIPTION/USE**: Allows NASA to determine the current status and
disposition of any SCR or DR control document.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted weekly.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Records the configuration management activities
associated with each Flight Software Change Request and Discrepancy
Report and it's relation to software delivery end items.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: All SCRs and DRs across the history of the Shuttle
FSW are maintained in a CMDB and reported by number along with the
following tracking data at a minimum:

a)  Title and date reported or submitted

b)  FSW release applicability

c)  Severity of problem (for DRs only)

d)  NASA board dispositions and date

e)  Contractor organization assigned corrective action

f)  FSW OI release incorporating code changes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 447 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Quality Assurance Assessment Report

7\. **DESCRIPTION/USE**: To provide management (contractor and NASA)
with a summary of contractor's SQA assessment of FSW development and
verification at CI.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted at CI for each
OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: SQA assessment of contractor's adherence to established
design and development standards employed in the phases implementation
of the FSW. The contractor SQA assessment will be in accordance with
contractor SQA assessment activities defined in the Space Shuttle
Orbiter Avionics software Quality Assurance Plan. (DRD 1.4.3.7-h)

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  Traceability between requirements, delivered software, and
    verification testing specification and results

b)  Adherence to established design and programming standards and to
    applicable embedded verification and validation standards

c)  Configuration management conformance to standards

d)  Verification test conduct adherence to procedures and test
    requirements

e)  Deliverables handling adherence to quality procedures and
    deliverables adherence to DRD requirements

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 448 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Software Quality Assurance (SQA) Plan

7\. **DESCRIPTION/USE**: To describe the SQA approach and to specify
procedures used for internal and external SQA interface activities.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted annually.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: SQA activity specified for SQA assessment and
involvement in plans, processes, and procedures relevant to satisfy
contractual requirements.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

1.  Introduction

This paragraph shall summarize the purpose and contents of the plan
relative to the OBS flight software project activities.

2.  Reference Documents

This paragraph shall list, by document, number and title of all
documents listed in this plan.

3.  Software Quality Organization and Responsibilities

This section shall define the SQA organization responsibilities,
organizational structure and reporting requirements.

4.  SQA Training Certification

The contractor shall identify the SQA training program and the
procedures followed in certifying the SQA personnel.

5.  SQA Interfaces

The contractor shall define the SQA organization's interfaces with the
following:

-   Software Development Organization

-   Configuration Management

-   Documentation Management

**DRD CONTINUATION SHEET**

**TITLE**: Software Quality Assurance (SQA) Plan **DRD NO.**: 1.4.3.7-h

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

6.  Subcontract Management

The contractor shall define that all applicable SQA requirements which
are flowdown to subcontractor(s). The contractor shall ensure that the
subcontractor(s) SQA implementation is in accordance with the SQA
contractual requirements.

7.  SQA Role in the Software Life Cycle

This section shall identify and define the SQA participation in the life
cycle milestones. This shall identify the life cycle in terms of the
following:

-   Requirements Definition

-   Design Phase

-   Code and Test Phase

-   Software Acceptance and Release

-   Post Turnover Support

8.  Software Quality Assurance Audits

The contractor shall conduct annual audits to verify compliance to
approved planned, procedures, processes, and standards. As a minimum,
these audits shall include:

-   Configuration Management

-   Software Development Library Controls

-   Software Testing

-   Documentation Management and Procedures

-   Software Development Processes

9.  Corrective Action

-   The corrective action monitoring and statusing procedures shall be
    specified in this section.

10. SQA Records Retention

-   This subparagraph shall describe the contractor's plans for
    preparing and maintaining records of each quality evaluation/audit
    performed.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 449 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-i

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Quality Assurance Audit/Inspection

7\. **DESCRIPTION/USE**: To provide management with the findings and
results of audits, inspections, and product deliveries. A copy of each
report shall be retained in the contractor's SQA record retention files.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required per the Quality Assurance
Plan

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Software Quality Assurance findings resulting from
conducting audits and inspections, FSW and FSWAT development and
flight-to-flight maintenance activity.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  Date Performed

b)  SQA Involvement

c)  Evaluation/Audit Criteria

d)  Findings, including detected problems, with reference to software
    problem report(s) as appropriate

e)  Recommended Corrective Action

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 450 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.7-j

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Flight Software Process Support Products & Services

7\. **DESCRIPTION/USE**: The products and services required to support
the flight software process and NASA Engineering Directorate control
boards, meetings, databases, records, documentation, agendas and
reports.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Weekly for most products

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the control board and meeting coordination,
the maintenance of databases and document and report generation.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

CONTROL BOARDS AND MEETINGS: This includes the administration of formal
boards and meetings including the responsibility for agendas,
scheduling, reporting of results and maintaining records. The specific
control boards and meetings include, but are not limited to the
following:

a)  Test and Operations Board

b)  Flight Software Discrepancy Review (DR) Control Board

c)  Support Software Boards (Change Request, DR, Compiler)

d)  Operational Increment (OI) Meetings

e)  Change Review Board

f)  Discrepancy Pre-Board Support

DATABASE SUPPORT AND RECORDS FUNCTION: This includes the maintenance and
operation of various databases that contain technical and administrative
data pertaining to flight software documents. A record of software
change instruments Shuttle Program Documents are also maintained.
Continuous access to record contents is provided. The following list
describes the databases and records maintained

a)  Support Software Databases (Change Request, DR, Compiler)

b)  Program Notes and Waivers

c)  Verification Test Procedures and Verification Test Report Data
    Coordination

d)  EV Library of Flight Software Requirements and Delivered Products

**DRD CONTINUATION SHEET**

**TITLE**: Flight Software Process Support **DRD NO.**: 1.4.3.7-j

Products & Services

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

DOCUMENTATION AND REPORT GENERATION: This includes the scheduling,
tracking and distribution of configuration control meeting support
documents for FSW Process and NASA Engineering Directorate Support. This
includes, but is not limited to, the distribution of products as well as
maintenance of copies and records of the products. All documentation
associated with the elements listed in 13.3.1 is included. Standard and
specialized reports are to be produced from the databases listed in
13.3.2 as required.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 451 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: FSW Applications Tools Requirements Documents and
Interface Control Documents

7\. **DESCRIPTION/USE**: Defines the requirements, specifications, and
controlled interfaces for the FSW Applications Tools used to perform the
FSW and FSWAT processes.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at CI
for each OI system and approved changes as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The requirements documents, specifications, and
interface control documents for the FSW Applications Tools used for the
FSW and FSWAT development, build, reconfiguration, verification, and
configuration management processes.

13.2 **APPLICABLE DOCUMENTS**: Support Software Change Requests (SSCRs)
authorizing changes to these requirements.

13.3 **CONTENTS**: These documents specify detailed software, data, and
interface requirements and requirements design assumptions. The
individual Requirements Documents are defined in the Flight Software
Build and Reconfiguration Support Tools - JSC 20183 document ( DRD
1.4.3.8-c ).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 452 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-b

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: FSW Applications Tools User's Guides

7\. **DESCRIPTION/USE**: A technical description of how to utilize the
FSW Applications Tools.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required, updated at CI

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: User information for the FSW Applications Tools used for
the FSW and FSWAT development, build, reconfiguration, verification, and
configuration management processes.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: These documents contain descriptions of how to
execute the FSW Applications Tools and how to interpret output messages.

The individual User's Guide documents are defined in the Flight Software
Build and Reconfiguration Support Tools - JSC 20183 document ( DRD
1.4.3.8-c ).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 453 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Build and Reconfiguration Support Tools -
JSC 20183

7\. **DESCRIPTION/USE**: An inventory and brief description of the
Flight Software Application Tools (FSWAT) which are used to develop,
verify, and reconfigure fight software.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Once per Operational Increment (OI) to be
published six weeks after CI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Category A tools for the Primary Avionics Software
System (PASS) and Backup Flight System (BFS). The document also contains
sections describing the operating system level tools and the High Order
Assembly Language (HAL) Compilers.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENT**: Each tool will be identified by functional area and
will include the following information: a brief description, applicable
computer system, language the tool is written in, number of source lines
of code (SLOCS), users of the tool, functional area, and identification
of reference documentation (requirements, design, users guide).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 454 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: HAL/S FC Compiler Test Plan

7\. **DESCRIPTION/USE**: For each release, the compiler test plan is
presented for review to assure testing of the compiler is adequate.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal 1 week
prior to compiler verification start for each compiler system

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the tests planned for in use in verifying all
changes to the compiler.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Compiler Test Plan presents the methodology and
procedures to be used to verify each of the changes implemented in the
compiler for the release and the integrity of the integrated compiler
itself:

This plan lists:

a)  All SSCR's/SSDR's implemented on the release

b)  Those SSCR's/SSDR's requiring compiler source code changes

c)  Those SSCR's/SSDR's causing object code changes

d)  Those SSCR's/SSDR's affecting error messages

e)  Those SSCR's/SSDR's having other unusual impacts

f)  External tools used in the compiler build

g)  Changes in compiler build procedures from the previous release

h)  External tools used in compiler testing

i)  Changes in test procedures from the previous release

j)  Expected deviations from normal test results

k)  Schedule for testing of the release

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 455 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: HAL/S FC Compiler Test Results Report

7\. **DESCRIPTION/USE**: For each release, the compiler test results
report is presented to assure that the testing of the compiler is
complete and correct.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal 1 week
prior to each compiler release.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the results of the tests used to verify all
changes to the compiler.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Compiler Test Results Report describes the
methodology and procedures that were used to verify each of the changes
implemented in the compiler for the release and the integrity of the
integrated compiler itself and the results of these tests.

This report lists:

a)  All SSCR's/SSDR's implemented on the release

b)  Changes in the baseline since the test plan review

c)  SSCR's/SSDR's that caused object code changes

d)  SSCR's/SSDR's that affected error messages

e)  SSCR's/SSDR's that had other unusual impacts

f)  Changes in compiler build procedures from those presented in the
    test plan

g)  Changes in test procedures from those presented in the test plan

h)  Actual deviations from expected results

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 456 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Applications Tools SSDR Analyses and Waivers

7\. **DESCRIPTION/USE**: To document an analysis recommendation for
SSDR's written against the FSW Applications Tools.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted bi-weekly as
required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Provided for all SSDR's written against the Applications
Tools.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: For each SSDR to be dispositioned, an analysis form
containing the following shall be provided.

The DR analysis form shall include:

a)  DR number and title

b)  Releases to which the analysis applies

c)  Analysis completion date and DR priority

d)  Investigator

e)  How the problem was discovered

f)  Detailed technical description of the problem

g)  Fix resource estimates and suggested modification

h)  Other pertinent data

For those SSDRs that require a waiver, the waiver form shall include:

a)  DR number and title

b)  Releases to which the waiver applies

c)  Investigator

d)  Detailed description of how the user sees the problem

e)  Justification for waiver

f)  Other pertinent data

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 457 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-g

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: GPC Emulator Simulation Documents

7\. **DESCRIPTION/USE**: Provides detailed descriptions of the math
model software, system requirements and procedures for running the
Simulation, and the operator interface software for the GPC Emulator
Simulation.

8\. **DISTRIBUTION**:

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Covers all the documentation associated with the GPC
Emulator Simulation system.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: These documents include a general description of how
the math models interact with each other, identify the RS/6000 system
requirements, the components of the Simulation, and the process and
procedures for modifying, building, and executing the Simulation, and
include a general description of the operator interface software.

The documents are:

GPC Emulator Simulation Math Model Software Detailed Description
Document

GPC Emulator Simulation Maintenance System User's Guide

GPC Emulator Simulation Operator Interface Maintenance Manual

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 458 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Support Software Change Control Board (SSCCB) Process
Products

7\. **DESCRIPTION/USE**: Products used in support of the SSCCB.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: ref. 13.3 below. a - once per year, b -
once per OI with completion in time for SCR approval by CI, c. -- as
determined by SSCCB Chairman, d - FACI and CI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents are required for the operation of the
Support Software Change Control Board.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  Support Software Change Control Board Procedures Document - Defines
    the procedures for the operation of the SSCCB.

b)  Tool baseline SCR's for both the PASS and the BFS - Flight software
    SCR's that define the tool baseline for the OI by listing the SSCR's
    and SSDR's approved for the release.

c)  Changes to baseline SCR's- SCR mods that define the movers for the
    PASS and BFS tools delivered after CI. The SSCR's and SSDR's are
    listed as deltas to the baseline along with a brief description of
    the change to the tool.

d)  Audit of SSCR/SSDR Oracle Database to ensure accuracy with the
    CMDB - Differences are noted and investigated to determine if
    updates to either database is required.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 459 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.8-i

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SPON System Interface and Integration

7\. **DESCRIPTION/USE**: To document the IMIC system integration,
application support, and user support needed for the NACC insight.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**: N/A

12\. **INTERRELATIONSHIP**: N/A

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This requirement specification establishes the SPON's
system integration, application support, and user support.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document/task shall contain:

a)  Scope

b)  NACC Integration and Synchronization

c)  Application Computer Resource Management

d)  Change Management

e)  Problem Management and Help Desk Support

f)  Security administration and ID administration

g)  Independent Systems Assurance

h)  System Data Base Administration

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 460 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Orbiter Avionics Software Programming Standards Document

7\. **DESCRIPTION/USE**: The Programming Standards Document will define
for programmers the standards to be employed in the development of
software for the Space Shuttle Primary Avionics Flight Software.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted annually

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Defines the programming standards to be used for the
development of FSW for the Space Shuttle Orbiter.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The standards document will contain complete and
explicit definitions, restrictions, and style guidelines for the
following aspects of software development.

a)  The definition of structured programming methods to be used

b)  A definition of naming conventions for all types of variables, data
    sets, segments, labels, procedures, functions, compools, and other
    data structures

c)  Special restrictions and guidelines in the use of HAL/S language
    features including data exchange, event variable, process priority,
    realtime features, I/O transactions, and interprocess variables

d)  The definition of a program, task, procedure, and function, and
    guidelines on when to use each

e)  Guidelines to be placed on the programmer in the use of diagnostic
    messages, data referencing, restricted HAL statements, and data
    initialization

f)  Standards to be applied to source code documentation including
    prologues, inline statement comments, and design specifications

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 461 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: FSW Maintenance Specification Document

7\. **DESCRIPTION/USE**: This document provides a high level technical
description of the PASS FSW and the environment in which it operates.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at CI
for each new OI release.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Maintenance Specification Document was created to
document the Flight Software (FSW) at a higher level than the Detailed
Design Specification (DDS) document. It is a unique user document
created to help current and future programmers and analysts maintain the
FSW. It contains functional overview of each principal function or
functional area and information to help people better understand the FSW
code.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The maintenance specification consists of three parts
as follows:

a)  GN&C (contains Guidance, Navigation, Flight Control & Sequencing)

b)  SSW (contains System Software)

c)  VCS (contains SM/PL, Vehicle Utility and RMS)

Each maintenance Specification Document will include the following:

a)  Text

```{=html}
<!-- -->
```
1.  Purpose/Usage

2.  Initiation/Termination Criteria

3.  Function Description

4.  Implementation Description

5.  Sequencing Description

6.  Design Considerations

7.  References

```{=html}
<!-- -->
```
b)  Flowcharts

```{=html}
<!-- -->
```
1.  Control and Flowcharts

2.  Data Flowcharts

3.  Sequencing Flowcharts

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 462 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Detail Design Specification (DDS)

7\. **DESCRIPTION/USE**: To define the detailed and data dependent
design for each program end item.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at
FACI plus six weeks. Post FACI changes will be delivered at CI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Presents the detailed design of all the source code
modules comprising the PASS software that runs in the on board computers
of the Space Shuttle.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The DDS is a document consisting of detailed design
descriptions for each of the code modules comprising the software that
runs in the onboard computers of the Space Shuttle.

The documentation for each module relates directly to the corresponding
module's source code, and specifies the following information:

a)  Module Name: The name of the module described in the section. Both
    an English and a HAL/S or Assembly name shall be provided

b)  Introductory Paragraph: A brief description of the functions
    performed by the module

c)  Control Interface: An identification of all the other modules that
    use or invoke this module, the form in which this module must be
    invoked, and the execution rate and priority at which this module is
    executed in each case

d)  Input Data: A list of all the parameters used as inputs by this
    module and their source.

e)  Process Description: A narrative that functionally describes the
    processing performed by the module as control flows through it. This
    description shall include algorithms and equations where necessary
    to explicitly define the design

f)  Output Data: A list of all the parameters computed by this module
    and their destinations

g)  Module References: A list of all the external modules referenced,
    invoked, activated or deactivated, by this module

h)  Module Type and Attributes for HAL/S modules: The HAL/S type of
    module (PROGRAMS, PROCEDURE, FUNCTION, COMPOOL, etc.) and attributes
    (EXCLUSIVE, REENTRANT, DEPENDENT, etc.) of the module

i)  Template References: A list of data templates and include segments
    referenced by the module

j)  Error Handling: Descriptions of how the code in the module responds
    to specific, error conditions anticipated

k)  Constraints and Assumptions: The processing limitation of the
    module, and the assumptions reflected in the design

l)  Flow Diagrams: Graphical representations of the functional flow of
    control through the module

**DRD CONTINUATION SHEET**

**TITLE**: Detail Design Specification (DDS) **DRD NO.**: 1.4.3.9-c

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

The DDS document is organized according to software functions as
follows:

-   System Services

    -   Part 1 - Flight Control Services (FCOS)

    -   Part 2 - User Interface (UI)

    -   Part 3 - System Control (SC)

-   Applications

    -   Part 1 - Guidance, Navigation and Control (GN&C)

    -   Part 2 - Systems Management (SM)

    -   Part 3 - Vehicle Utility (VU)

For each book or published part, a list of SCR numbers which have been
incorporated into the document and on which OI release shall be
included.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 463 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software First Article Configuration Inspection (FACI)
Report

7\. **DESCRIPTION/USE**: This report presents to NASA the status of the
OI software development release for verification. This report officially
reports the contractor's OI development completion of baselined
requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at
FACI for each OI system

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8, 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Covers the results of all Flight Software development
and development testing performed prior to release of the OI software
for verification.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This documentation shall present for both Flight
Software and Flight Software Application Tools a summary and status of
all software changes, DR's, waivers and user notes, major capability
changes, and the Level 6 and 7 verification plans related to a specific
OI system. It shall include a summary of processes leading to FACI and
shall identify any post FACI development work in line to CI. At a
minimum, the reporting shall include:

a)  Overview of the development process leading up to FACI

b)  Identification of each SCR and DR change applied to the OI software

c)  A summary by major functional areas of new major capabilities
    provided with the new OI software

d)  Summary and description of all FSW and FSWAT waivers and Operations
    Notes deleted by this OI and still applicable to the OI.

e)  Definition of all post FACI open work including open DR's,
    potentially applicable to the OI.

f)  Summary and status of the quality metrics historically and for this
    OI

g)  A definition of the Level 6 and 7 verification plans

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 464 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Capabilities Verification Plan (Level 6)

7\. **DESCRIPTION/USE**: Verification test plan is used to determine
work load over the life of the delivery and to allow NASA to plan and
manage the NASA review of testing.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at
FACI for each OI system. Review copy shall be provided 4 weeks prior to
FACI

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the specific testing activity for each FSW
change request and projected dates of start and completion for each
detailed verification test as planned at that time.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Test Plan consists of the following:

a)  Cover Sheet: Memo addressed to the FDSD OI Coordinator stating the
    start of the test planning cycle and containing a statement of the
    areas in FSW to be tested and any off nominal items for the upcoming
    test phase

b)  Overview: A breakdown of SCRs/DRs and their individual testing
    requirements as well as graphical and/or table depiction's of FSW
    area (e.g., Guidance, Nav, etc.) workload balance

c)  Listing of SCRs: A listing generated from the configuration database
    showing all SCR's currently scheduled for the current FSW release
    under test

d)  Listing of DRs: A listing generated from the configuration database
    showing all DRs currently scheduled for the current FSW release
    under test

e)  Listing of Test Cases: A listing generated from the configuration
    database showing all planned Level 6 detailed verification test
    cases including the projected start and completion dates for each
    individual test case

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 465 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Capabilities Verification Procedures
(Level 6)

7\. **DESCRIPTION/USE**: Verification test procedures (VTP) are reviewed
by the contractor and NASA to assure accuracy of capabilities tests.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each OI system with
planned submittal prior to CI or by the SRR of the appropriate flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the specific testing content and methods to be
used in verifying all new capabilities and error corrections in the FSW.
This product is required for all pre-CI and post-CI approved changes to
the FSW which are identified as requiring testing.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The VTP consists of the following:

a)  The prologue: The prologue describes the testing environment, the
    related requirements documentation, the functional objective of the
    test, the change authorization which documents or describes the FSW
    change being tested, and the current testing objective

b)  The test log: The test log describes the test objective and the
    applicable steps in the test

c)  An initialization description: The initialization description
    describes the initial test conditions such as Shuttle systems
    states, avionics failures and flight phase conditions

d)  Test step descriptions: The test step descriptions list each step in
    the testcase. For each step, there will be a listing of the
    requirements referenced for that step, a detailed description of the
    step and what the expected results of that step are

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 466 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Level 6 Test Cases -- Capabilities Verification Phase

7\. **DESCRIPTION/USE**: Verification tests results allow acceptance of
FSW programs and approval of delivery for reconfiguration.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each OI system with
planned submittal prior to CI or by the SRR of the appropriate flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Verification Test Cases contain the materials generated
during the execution, analysis, and inspection of the flight software
end item tests.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  JSTEP Expansion - A listing of the syntax checker which verifies the
    simulation control commands that were used to run the test

b)  FEID Online - Detailed listing of actual time stamped simulation
    events, both user induced and simulation induced, which serves as a
    simulation timeline record.

c)  Post Processor Output - This contains results of the interaction
    between the flight software and the testing scenario/environment.
    This output may include such things as:

```{=html}
<!-- -->
```
1.  Trace routines - Lists the flight software program execution path
    along with the execution times of each program step

2.  Display images - Relevant display images that assist in establishing
    what happened during the test and in determining whether the display
    programs are operating correctly

3.  Parameter snaps - A time history listing of all significant
    parameters showing flight time versus parameter value tables

```{=html}
<!-- -->
```
d)  Epilogue - Individual test case summary report which contains such
    information as:

```{=html}
<!-- -->
```
1.  Flight software authorization either partially or totally closed by
    this test case

2.  Discrepancies discovered against flight software to support software
    which influence the outcome of the test case

3.  Observations and results

4.  Deviations from expected results

5.  Conclusions

```{=html}
<!-- -->
```
e)  Any additional material that further demonstrates the correctness of
    the test approach, i.e., bench program output, annotated code and
    output listings, resulting discrepancies, etc.

**DRD CONTINUATION SHEET**

**TITLE**: Level 6 Test Cases -- Capabilities **DRD NO.**: 1.4.3.9-g

Verification Phase

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 467 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: FSW Performance Verification Plan (Level 7)

7\. **DESCRIPTION/USE**: Performance verification test plans are
required by NASA to assure accuracy of FSW performance verification
approach.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal no
later than 5 weeks prior to FACI and at FACI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes a set of tests for NASA community review which
prove the accuracy and performance of the FSW with respect to expected
results from requirements change effects across the major software
regions.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

The test plan consists of the following major regions:

a)  GN&C performance tests

b)  System Services performance tests

c)  VCS performance tests

Level 7 test specifications will contain:

a)  Identification name for the test case

b)  Title/Description of the test case

c)  Principal functions tested

d)  Major mode being tested

e)  The testing objective

f)  The testing approach

g)  Special Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 468 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-i

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: FSW Test Reports - Performance Verification (Level 7)

7\. **DESCRIPTION/USE**: Level 7 test results reports are reviewed by
the technical community to determine correct performance of software
prior to CI software acceptance.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal 8
weeks prior to CI, or as specified by the Contracting Officer's
Technical Representative (COTR), or designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The results of each performance test as specified in the
FSW Performance Verification Plan (DRD-1.4.3.9-h).

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The performance test results consisting of:

a)  The SCR tested - specify the particular SCR's that were tested by
    each L7 test case

b)  The test specification - contains the identification name, title,
    description of each test case, Ops and major modes tested, testing
    objective, and testing approach

c)  Deviation from test specification - The deviations from the original
    test specification (established at CI).

d)  General system description - The general system description defining
    the flight software version, mission definition, mission data,
    simulator base, computer configuration, simulator SCR/DR patches
    required, and the FSW SCR/DR patches required

e)  Test procedure - A step-by-step instruction of all the steps used to
    test the software

f)  Detailed test results - The detailed results of each test case will
    be described sequentially for each major capability that is being
    tested. Issues that are raised or uncovered by the testing will be
    noted

g)  Conclusions - Conclusions about the testing philosophy and results
    will be noted. Specifically, whether the test was successful and
    whether the vehicle and flight software performed satisfactorily
    will be stated

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 469 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-j

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Configuration Inspection (CI) Report

7\. **DESCRIPTION/USE**: This report presents to NASA the delivery of an
Operational Increment (OI) software milestone. This report officially
documents the contractor's completion of OI development and
verification.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at CI
for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8, 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Covers the results of all Flight Software development,
verification, documentation, and configuration control performed in
support of a new FSW Operational Increment (OI)

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This documentation shall present for both Flight
Software and Flight Software Application Tools a summary and status of
all software changes, DR's, waivers and user notes, verification
testing, certification, FSW memory sizing, and FSW CPU loading estimates
related to a specific OI system. It shall include a summary of the
processes leading to CI and shall identify any open work post CI. At a
minimum, the reporting shall include:

a)  An overview of the OI history and new major capabilities

b)  Identification of each SCR and DR change applied to the OI software

c)  Summary of all verification and performance testing for this OI and
    test mapping to SCRs and DRs

d)  Summary of all FSW and FSWAT waivers, Ops Notes and User Notes
    deleted and still applicable to the OI

e)  Definition of the memory space allocation and CPU performance status
    and margins with this OI

f)  Summary and status of the quality metrics historically and with this
    OI

g)  Status of all open DRs applicable to this OI software

h)  Flight Software Memory sizing and CPU Loading Estimates

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 470 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-k

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: FSW OI Deliverables

7\. **DESCRIPTION/USE**: FSW operational increment (OI) products will be
delivered for use by the reconfiguration organization for production of
training and flight loads.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal for
each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.8, 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The FSW and FSW Applications Tools software and products
required for execution of the flight to flight reconfiguration
processes.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Includes all deliverable products specified in the
FSW Class I Integration Plan (CIP), JSC 22320, as deliverables for each
OI.

13.4 **FORMAT**: Products will be generated in Software Development
Facility (SDF) data sets in the formats described in the CIP. The CIP
contents are under configuration control by the SASCB.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 471 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-l

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Flight Software Class 1 Integration Plan (CIP) -
JSC-22320

7\. **DESCRIPTION/USE**: Defines the Primary Avionics Software System
(PASS) and Backup Flight System (BFS) flight software products which
comprise an Operational Increment (OI) system, and the flight software
development tools which develop the flight to flight reconfiguration.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Once for each new Operational Increment
of flight software to be NASA approved by the Configuration Inspection
for that OI

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: Shuttle Avionics Mass Memory Unit Computer
Program Integration Plan (MIP), JSC-08338; Flight Software and Mission
Data Reconfiguration Tools Document, JSC-20183

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the content and format of flight software
products and reconfiguration tools delivered to NASA by the development
contractors.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  PASS flight software:

```{=html}
<!-- -->
```
1.  Details the OI products (format, media, and method of delivery) to
    be delivered to NASA at CI, including: source code, flight software
    build documentation, products used for flight to flight
    reconfiguration.

2.  Describes the subset of OI products (format, media and method of
    delivery) to be delivered to other contractors and organizations.

3.  Describes the authorization, format and delivery of all flight
    software patches to be performed prior to, or post CI, on the OI
    base system, and on a recon system intended for flight.

4.  Lists the software tools delivered to support PASS/BFS development
    and PASS reconfiguration

```{=html}
<!-- -->
```
b)  BFS flight software:

```{=html}
<!-- -->
```
1.  Details the OI products (format, media, and method of delivery) to
    be delivered to NASA at CI, including: source code, flight software
    build documentation, products used for flight to flight
    reconfiguration.

2.  Describes the subset of OI products (format, media and method of
    delivery) to be delivered to other contractors and organizations.

3.  Describes the authorization, format and delivery of all flight
    software patches to be performed prior to, or post CI, on the OI
    base system, and on a recon system intended for flight.

4.  Lists the software tools delivered to support BFS development and
    reconfiguration

**DRD CONTINUATION SHEET**

**TITLE**: Flight Software Class 1 Integration Plan (CIP) - **DRD NO.**:
1.4.3.9-l

JSC-22320

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 472 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-m

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Payload Software Capabilities Overview - JSC 17086

7\. **DESCRIPTION/USE**: Provides a high level description of the
payload software capabilities provided on-orbit by the Systems
Management application of the PASS flight software. The payload
customers may choose to use these capabilities for the flight. The
document is intended for distribution to payload customers.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: When a capability changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document is limited to a description of the payload
software capabilities provided on-orbit by the Systems Management
application.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: A detailed description of the payload software
capabilities.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 473 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-n

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Change Request Risk Assessments

7\. **DESCRIPTION/USE**: To give NASA management an estimate of the cost
associated with implementing a SCR, the risk associated with the SCR,
and any impacts to other work.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required to support Software Change
Request (SCR) for all code changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The risk assessment will define costs, schedule impacts
to existing work, and risks or implementation for all SCRs.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

The VCS and SSW risk factors assessed are:

a)  Describe the current operation of the software system

b)  Describe code operation after implementation of change

c)  Define work-a-rounds or consequences if change is not implemented

d)  Recommendations for or against implementation

e)  Size of change in modules affected and lines of code or patch size

f)  Complexity of change whether low, medium, or high and the reason

g)  Criticality of Function being modified

h)  Fit into current design or special design required

i)  Frequency of execution of affected code paths

j)  List the functional areas involved in the change

k)  Identify recent change activity in the functional area

l)  Define all flight phases affected

m)  Identify the interactions or dependencies with other changes

n)  Provide number of SCR mods

o)  Provide number of requirements issues

p)  Provide number of requirements inspections

q)  List DR's closed by the change

r)  Define manpower impact in manweeks

s)  Define the GPC memory space impacts in code and data space

t)  Performance impacts to the Shuttle system

u)  Define the verification costs in test cases and manweeks

v)  Additional comments

**DRD CONTINUATION SHEET**

**TITLE**: Chang Request Risk Assessments **DRD NO.**: 1.4.3.9-n

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3. **CONTENTS (continued)**:

The GN&C and RMS risk factors assessed are:

a)  Provide a short summary of benefits of the change

b)  Estimated size of change

c)  Complexity of change whether low, medium, or high and the reason

d)  Criticality of areas affected

e)  Change affects abort or error paths vs. Nominal code paths

f)  Number of failures required to exercise this code

g)  Define the operational phases affected

h)  Indicate whether new or existing code is affect

i)  Describe recent change activity in the area of code

j)  Describe other change activity in the area on the OI

k)  Identify number of affected Principal Functions

l)  Identify number of mods required for the SCR

m)  Describe requirements issues and their dispositions

n)  Describe number of requirements inspections/reinspections (Author
    Involvement)

o)  Define the development manpower impact in critical skills

p)  Define the GPC memory space impacts in code and data space

q)  Identify CPU performance impacts

r)  Provide verification impacts (cost, risk)

s)  Identify required tool modifications

t)  Additional comments

Any additional FSW Tool risks.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 474 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-o

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Downlist Availability Configuration

7\. **DESCRIPTION/USE**: The FSW community uses this document to
identify what parameters are available for downlist.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at CI
for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document reports in a single source, information
specifying the actual availability of Primary Avionics Software System
(PASS) measurements for downlist on a given Operational Increment (OI).

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This Downlist Availability Configuration document
contains two reports - a Requirements by MSID report (in which all
non-reconfigurable measurements that are available for downlist are
listed) and a Parent/Child Correlation report (in which all
non-reconfigurable Parent measurements are listed with their associated
child measurement). Each report is explained in more detail below.

The data in the requirements by MSID report is sorted by measurement
number (MSID). The 4th, 9th, and 10th characters are ignored in the
sort. The following list describes each of the fields within the report.

MSID - Measurement number of the parameter which is available for
downlist

Parent - Measurement number of the parent parameter associated with this
MSID

Parameter Nomenclature - The nomenclature of the parameter

Type - The data type of the measurement number

Units - The units of the parameter date

"0" 0 If the parameter is of type DISCRETE then the data in this field
indicates the meaning of the parameter when it has a value of binary 0

"1" - If the parameter is of type DISCRETE then the data in this field
indicates the meaning of the parameter when it has a value of binary 1

Format - D/L format and rate in which the parameter is downlisted

The data in the Parent/Child correlation report is sorted first by
parent measurement number (MSID) and then by child MSID. The 4th, 9th,
and 10th characters are ignored in the sort. The following list
describes each of the fields in the report.

**DRD CONTINUATION SHEET**

**TITLE**: Downlist Availability Configuration **DRD NO.**: 1.4.3.9-o

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3. **CONTENTS (continued)**:

Parent - Measurement number of the parent parameter which is available
for downlist

Child MSID - Measurement number of the child parameter associated with
the PARENT MSID

Parameter Nomenclature - The nomenclature of the parameter

"0" - The data in this field indicates the meaning of the child
parameter when it has a value of binary 0

"1" - The data in this field indicates the meaning of the child
parameter when it has a value of binary 1

Format - D/L format and rate in which the parameter is downlisted

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 475 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.9-p

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Space Shuttle Programs PASS Parameter Data Tape Content

7\. **DESCRIPTION/USE**: Defines the requirements for the parameters to
be included in the PASS Parameter Data Tape (PDT).

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at CI
for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the PASS flight software HAL/S parameters
which are required to be included on the Parameter Data Tape (PDT).

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Specifies only PASS parameters which are on the PDT.
The parameters may apply to the flight software areas of Guidance,
Navigation and Control; Systems Management; Vehicle Utilities; and/or
System Software (FCOS). It shall contain as a minimum:

a)  Purpose - The purpose of this document is to specify the PASS flight
    software HAL/S parameters which are required to be included on the
    Parameter Data Tape (PDT). Parameters are listed in a table in
    alphabetical order by HAL/S name.

b)  Scope - This document specifies only PASS parameters which are on
    the PDT; no other parameters are listed. The parameters may apply to
    the flight software areas of Guidance, Navigation and Control;
    Systems Management; Vehicle Utilities; and/or System Software
    (FCOS). Note that only HAL/S name, FSSR name, MSID, and units fields
    are specified in this document and that the FSSR name, MSID and
    units fields are optional for all parameters but are included and
    verified when supplied in the authorizing SCR.

c)  Applicable Documents - The format of the PDT is defined in JSC 08338
    (Memory Integration Plan), Appendix A.

d)  Table Format - This list is in alphabetical order by HAL/S name. The
    lit is in tabular form and includes the following fields:

```{=html}
<!-- -->
```
1.  HAL -- the HAL/S name of the flight software parameter

2.  FSSR Name -- the parameter name as defined by the source principal
    function

3.  MSID -- the MSID of the parameter as defined by the Shuttle Data
    Integration Plan measurement and stimulus system

4.  Units -- the units of the parameter

```{=html}
<!-- -->
```
e)  PDT Parameters - The actual formatted list of parameters contained
    on the Parameter Data Tape.

**DRD CONTINUATION SHEET**

**TITLE**: Space Shuttle Program PASS Parameter Data **DRD NO.**:
1.4.3.9-p

Tape Content

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 476 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.10-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MMU Reconfiguration Deliverables

7\. **DESCRIPTION/USE**: Shuttle MMU and PASS release deliverables and
supporting information to be sent to the various facilities.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION:** Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: To provide Shuttle MMU and PASS release deliverables and
supporting information that is sent to the various facilities.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Includes products specified in the Shuttle Avionics
Mass Memory Unit Computer Program Integrated Plan (MIP), JSC 08338, as
deliverables for each Flight or Special System.

13.4 **FORMAT**: Products will be generated in the formats described in
the MIP. The MIP contents are under configuration control by the Shuttle
Avionics Software Control Board (SASCB).

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 477 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.10-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Level 8 Products

7\. **DESCRIPTION/USE**: Level 8 test reports and products for review
and analysis use by technical community.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each Reconfiguration
release

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10

**13. DATA PREPARATION INFORMATION:**

13.1 **SCOPE**: Level 8 test reports and products for review and
analysis use by technical community.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Includes products specified in the Flight Software
Reconfiguration Performance Test Plan (PTP), USA 005574, as deliverables
for each Flight System.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 478 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.10-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Monthly PASS Reconfiguration Status Report

7\. **DESCRIPTION/USE**: Describes the status and metrics of the PASS
flight software reconfiguration and the MMU reconfiguration
deliverables.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted monthly with
planned submittal at status meetings.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the status, schedule, quality, and timeliness
of the reconfiguration process.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  Flight reconfiguration and issues status

b)  Reconfiguration schedules

c)  Process change status

d)  Reconfiguration product delivery summary information (actual and
    projected)

e)  Reconfiguration and level 8 metrics including quantity, timeliness,
    reconfiguration DR's and DR detection

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 479 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.10-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MMU Integration Plan (MIP) - JSC 08338

7\. **DESCRIPTION/USE**: Defines the Mass Memory Unit related products
which are to be delivered for flight and field systems.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the content and format of flight software
products for flight and field systems delivered by the FSW
reconfiguration contractors.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Defines the requirements for inputs and outputs for
processing and delivery of Mass Memory Unit contents for release to the
field sites and use for flight. Defines the specific product formats and
delivery mechanisms.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 480 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.10-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Baseline Control Board (IBCB) Datapack

7\. **DESCRIPTION/USE**: Shows the detailed schedules for FSW
reconfiguration activities required to generate field and flight system
flight software loads.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Weekly

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Detailed planned and actual schedules for flight
software reconfiguration activities and other information related to
reconfigured systems and reconfiguration processes.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  Detailed planned and actual schedules by flight system

b)  Flight system designators

c)  Flight system SCR and DR implementation plans and matrix

d)  Historical summary of flights

e)  Reconfiguration process agreements

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 481 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.10-f

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Level 8 Performance Test Plan Document

7\. **DESCRIPTION/USE**: Documents the test approach, products, and test
specifications for FSW reconfiguration verification (Level 8) to be
performed on flight system flight software loads.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The requirements and specifications for testing
conducted by the FSW reconfiguration contractors to verify integrated
FSW performance and assure product quality and integrity.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**:

a)  Philosophy, Approach, Quality Assurance and Process Control, and
    Applicable Documents

b)  Test Nomenclature, Description, Effectivity

c)  PASS GN&C Verification Test Specifications

d)  PASS VCS Verification Test Specifications

e)  MM Load Content Verification Specifications

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 482 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.11-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: DPS Reports, Monthly Progress

7\. **DESCRIPTION/USE**: To summarize all work accomplished during each
month of contract performance in a comprehensive narrative report that
presents, for information or evaluation purposes, the Contractor's
overall program progress.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: The first initial report should cover a
minimum of 1 complete month with a cutoff date on the 30th/31st.
Thereafter, the report should cover 1 complete month with the cutoff
date on the 30th/31st. All reports are due to received by NASA on or
before the 10th of the following month.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.11

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**:

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Contractor's Monthly Progress Reports shall be in
a narrative form, brief, and informal in content.

The Monthly Progress Report shall include, but not limited to, the
following areas:

a)  A quantitative description of overall progress against the program
    schedule with reasons for significant differences

b)  Progress of individual major areas of the contract

c)  Progress of all major end items, description of the significant
    current discrepancies on problems, proposed corrective action and
    status

d)  A discussion of the work to be performed during the next monthly
    reporting period

e)  Configuration matrix of current hardware locations

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 483 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.11-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: DPS Report, Engineering and Technical Data

7\. **DESCRIPTION/USE**: To provide technical information on the
contractual effort.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.11

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Contractor shall prepare technical reports which
describe the studies, analyses, and results of the specific contractual
efforts.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The individual report shall include, but not be
limited to, such technical specialties as theoretical analyses,
engineering verifications, current problems and proposed solutions, and
conclusions and recommendations.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 484 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.11-c

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Simulator Interface Device (SID) Interface Control
Document (ICD).

7\. **DESCRIPTION/USE**: Establish a means for defining and controlling
interface requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with submittal due 30 days
after change or modification incorporated.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.11

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This Data Requirements Description establishes a
requirement for preparation of ICDs which will define the physical and
functional interfaces between the SID and co-functioning equipment.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: An ICD depicts physical and functional interface
engineering requirements of a subsystem which affects the design control
documents, delineating subsystems. These documents are used as design
control documents, delineating subsystem interface engineering data
coordination for purposes of:

a)  establishing and maintaining compatibility between co-functioning
    subsystems.

b)  controlling interface designs, thereby preventing changes to system
    requirements which could affect compatibility with co-functioning
    systems.

c)  communicating design decisions and changes to participating
    activities.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 485 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.11-d

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: DPS Acceptance Data Packages

7\. **DESCRIPTION/USE**: To document original configuration of hardware
and track changes to configuration through repairs and modifications.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.11

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall maintain data packages for all
flight-like hardware (GPC's, DEU's, DU's)

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The data packages shall contain, as a minimum:

a)  As-Build Configuration documentation

b)  Repair activity

c)  Modification activity

d)  Discrepancy Reports generated against the hardware

e)  Acceptance test data

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 486 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Test and Operations Plan - JSC-25392

7\. **DESCRIPTION/USE**: This document provides a single source
reference for information and procedures related to the Flight Software
Test and Operations Board and for providing T&O support at the various
support sites.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required to incorporate changes in the
Test and Operation Board and support process.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document defines how the Flight Software Test and
Operations (T&O) Board controls and how the software contractor supports
facility unique configuration changes of formally released Orbiter
avionics software used for vehicle checkout, engineering evaluation,
payload checkout, crew training, and flight software verification
testing.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document identifies a method for accomplishing
the T&O board and site support processes and also defines the approval
process for program notes and waivers. This document shall include the
following:

a)  Purpose

b)  Board authority and limitations

c)  Configuration-control functions

d)  Personnel support

e)  Instructions for completing Software Approval Sheets, Maintenance
    Integration Plan change requests, program notes, and emergency
    facility patches.

f)  General and facility unique T&O duties.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 487 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Mission Support Plan

7\. **DESCRIPTION/USE**: To describe the software contractor's approach
to providing mission operational support.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted annually

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Defines activities of the software contractor in support
of Space Shuttle operational missions, including preflight preparation,
flight support, and post-flight closeout of any questions or anomalies.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The mission support plan will define the procedures,
communication protocol, personnel requirements, data gathering, response
time, facility requirements, console support, contractor facility
support and data processing capabilities used during mission support.

The document will discuss in text and through flow charts the definitive
processes and capabilities provided by the contractor. The major areas
to be covered will include:

a)  Support team skills and functions in the Mission Evaluation Room
    (MER) and in the contractor's facility

b)  Coordination and communication procedures

c)  Data gathering requirements, capabilities and procedures

d)  Dump and other electronic data processing procedures

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 488 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Mission Operation Support Report

7\. **DESCRIPTION/USE**: To describe the contractor's participation,
achievement, and resources expended in real time support of each Shuttle
mission operations.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal within
10 working days of all Shuttle flight landings.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes the contractor's participation, achievement,
and resources expended in support of mission operations, as well as
other applicable historical data. A single summary report will be issued
to cover all the mission operation support provided for each mission.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Mission Operation Support Report shall contain
the periods of support for launch, the actual launch and landing times,
the Orbiter identifier and name, the mission objectives, major mission
milestones and a statement outlining the mission support team activities
during the mission. The report shall list in order all subjects (i.e.,
CHITS, comments, etc.) that the mission support team was involved with
during the flight. A summary of the hardware and software health will be
provided at the end of the report.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 489 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: DR Analysis and Status Reports

7\. **DESCRIPTION/USE**: To document an analysis recommendation for DR's
written against the Shuttle Primary Avionics Flight Software.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted weekly as
required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**:

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: For each DR being dispositioned, a complete analysis
description containing:

a)  Technical details of the conditions and failures necessary to cause
    the problem

b)  Definition of the exact results and signature of the problem

c)  Detailed code analysis of the mechanism by which the software
    performs under the scenario conditions

d)  Description of all visible user effects

e)  Analysis of how the problem was missed in the inspection, review,
    development, and testing process

f)  Recommendations for closure of the DR and for process changes to
    avoid similar problems

When requested, a listing of all open DR's by functional area. This
listing shall include systems affected, probable severity and
dispositions.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 490 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Program Notes and Waivers Document - JSC
19320

7\. **DESCRIPTION/USE**: This publication documents program anomalies to
the Primary Avionics Software System (PASS), the Backup Flight System
(BFS), the General Purpose Computer (GPC), the Self-Test Program (STP),
and the DEU Control Program (DCP) software.

8\. **DISTRIBUTION**: As specified in current Program Notes and Waivers
document - JSC 19320

9\. **INITIAL SUBMISSION**: Two weeks prior to the first flight after
contract start

10\. **SUBMISSION FREQUENCY**: Updated for each Flight Software
Operational Increment and addenda published prior to each Shuttle Flight

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document specifically explains currently known
anomalies that have been approved by the Test and Operations (T&O) Board
and the Shuttle Avionics Software Control Board (SASCB).

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall consist (but is not all
inclusive) of currently known anomalies that have been approved by the
Test and Operations (T&O) Board and the Shuttle Avionics Software
Control Board (SASCB). The document shall include the following:

a)  Introduction

b)  Cross Reference Dictionary

c)  Program Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 491 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-g

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Program Notes and Waivers

7\. **DESCRIPTION/USE**: Used to update the PASS FSW Program Note and
Waiver document to describe software operations.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: There are three types of Program Notes:

a)  Operations Note -- Describes an error discrepancy in a released
    version of the FSW and provides user level descriptions of the
    visible affects.

b)  User Note -- Describes the per requirements behavior of the FSW from
    a user visibility perspective.

c)  Waiver -- Documents a violation of FSW requirements. A waiver on the
    requirement not met accompanies an Ops Note. A waiver may be issued
    without a companion Ops Note.

13.2 **APPLICABLE DOCUMENTS**: JSC 19320

13.3 **CONTENTS**: Based on DR closure, the appropriate note and/or
waiver is produced, containing a description of the problem, question,
or idiosyncrasy along with an avoidance techniques or other User
information.

The Program Notes and Waivers are delivered to the T&O Board as
individual pages in the form approved by the T&O Board. They will be
published in a Program Notes and Waivers document after receiving Space
Shuttle community concurrence through the T&O Board.

13.4 **FORMAT**: 8 ½ x 11 page size in electronic form using the T&O
board defined note templates.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 492 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-h

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: PASS Flight Software User's Guide

7\. **DESCRIPTION/USE**: This document provides the information
necessary to operate and control the PASS FSW.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at 2
months after CI for each OI system

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Describes how the flight software is loaded into the
flight computers, and how it is used. Provides the procedural details of
interfacing with the program inputs, display outputs, error conditions
and messages, and recovery options.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain a compilation of
information, procedures, and techniques necessary and useful for the
users to interface with the PASS FSW. Included shall be the following:

Introduction - This section will include general information about the
User's Guide (UG) such as the purpose, scope, applicable documents, and
Flight Software (FSW) deliverables.

System - This section of the UG will provide general information about
the Primary Avionics Software System (PASS). It will include a
description of the Mass Memory Unit, system initialization and overall
operation.

CRT Displays - This UG section will give a description of the
interactive user interface to the PASS. It will describe the hardware
used to provide this interface and explain the display interface
hierarchy and priorities. It will provide a description of the display
format and define the generic fields. The various type of displays and
their hierarchy will be discusses and a drawing and description of each
display available will be included.

Dedicated Displays - In this section of the UG, the definition of
dedicated displays will be provided. A description of the various
displays will be included with a drawing where appropriate. The meaning
of the information presented and when it is valid will be delineated.

Switches - This section of the UG will provide a list of all switch
functions which are required for the proper functioning of the PASS. The
list will be in tabular format and include information about the switch
such as the name, type, where located, when valid, frequency of sensing,
identifier, number of states and a definition.

**DRD CONTINUATION SHEET**

**TITLE**: PASS Flight Software User's Guide **DRD NO.**: 1.4.3.12-h

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

Fault Annunciation and Messages - In this section of the UG, fault
detection will be discussed. The discussion will include types of faults
and their classification. A brief discussion of each class will be
included. A description of the format of each message that may be
annunciated will be provided.

Ground/GPC Interfaces - This section will describe the communications
between the vehicle and the ground control centers. Included will be
detailed discussions of the launch data bus interface, uplink
capabilities and downlist of selected data from the vehicle.

Data Analysis - This section will provide information on the data and
tools available to investigate and resolve issues that may arise while
working with the PASS.

Appendices - The UG will contain various appendices as deemed necessary
to support the main body of the document. This will include cross
reference listings, notes, information on tools and expanded message
explanations.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 493 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.12-i

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Mass Memory Patch

7\. **DESCRIPTION/USE**: The Mass Memory Patch is used to modify the
Flight Software without altering the AP101 memory maps.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.10, 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Provides the means of delivering modifications of the
flight software to an end user. The development and delivery of the
patch requires a NASA approved Flight Software SCR or DR.

13.2 **APPLICABLE DOCUMENTS**: JSC 08338

13.3 **CONTENTS**: The patch contents and format are defined in the MMU
Integration Plan (MIP)- JSC 08338 (DRD 1.4.3.10-d)

13.4 **FORMAT**: The patch format is controlled through the Memory
Integration Plan (MIP), JSC document number JSC 08338. The patch is
delivered to NASA in an electronic dataset on the SDF or SPF.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 494 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Development Plan (SDP) for the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To provide NASA with visibility into the
software maintenance process.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document describes the overall plan for the
maintenance of the MEDS software.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Software Development Plan

d)  Software Engineering

e)  Verification Testing

f)  Software Product Evaluations

g)  Software Configuration Management

h)  Other Software Development Functions

i)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 495 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Software Change Authorization

7\. **DESCRIPTION/USE**: Products used to propose detailed changes to
the MEDS Flight Software. Consists of:

a)  MEDS Flight Software Change Proposal (FCP), used to obtain
    preliminary customer concurrence for development of software change
    requests

b)  MEDS Software Change Request (SCR), used to propose changes to the
    MEDS flight software requirements

c)  MEDS Change Request (CR) Risk Assessment Analysis Report, used to
    assess the risk of changing the existing code to implement the
    requested change

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Includes products required to authorize MEDS software
requirements changes approved by the customer.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: Products used to propose detailed changes to the MEDS
Flight Software. Consists of:

a)  MEDS Flight Software Change Proposal (FCP), used to obtain
    preliminary customer concurrence for development of software change
    requests

b)  MEDS Software Change Request (SCR), used to propose changes to the
    MEDS flight software requirements

c)  MEDS Change Request (CR) Risk Assessment Analysis Report, used to
    assess the risk of changing the existing code to implement the
    requested change

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 496 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Hardware Dependent Software Segment Specification (HDSSS)
for the Multifunction Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To provide the functional requirements for the
Hardware Dependent Software (HDS).

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittal should be scheduled
approximately 14 days prior to the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document specifies functional software/firmware
requirements for the HDS. It also specifies the HDS interface
requirements with the MEDS application software.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Applicable Documents

c)  Segment Requirements

d)  Quality Assurance Provisions

e)  Preparation for Delivery

f)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 497 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: General Purpose Computer (GPC)/Integrated Display
Processor (IDP) Interface Control Document (ICD)

7\. **DESCRIPTION/USE**: To describe the MEDS interface to the Space
Shuttle GPC and the appropriate Orbiter panel switches and keyboards
with the IDP to perform the Man-Machine Crew Interface function of the
Space Shuttle Orbiter.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document addresses the interface requirements
between the IDP and the GPC and delineated Orbiter panel switches and
the Orbiter keyboard.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Introduction

b)  Applicable Documents

c)  Requirements

d)  Acronyms and Abbreviations

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 498 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-j

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Verification Test Readiness Review (TRR) Briefing

7\. **DESCRIPTION/USE**: To provide a description of the development
completeness and verification readiness of the MEDS software to assure
the customer that the software was developed per the requirements and is
ready for verification testing.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittals should be scheduled
approximately 1 day prior to the start of verification testing.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The MEDS TRR briefing describes the development work
completed, the verification work to be performed, and confirms that the
software is ready for verification testing.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: This briefing package shall contain:

a)  Development activities

b)  Verification activities

c)  SQE Status

d)  Schedule

e)  Open Items

f)  SPCR/SCR/DR Cross refrence

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 499 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-k

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Requirements Specifications (SRS) for the
Multifunction Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To document the engineering requirements
imposed on the software.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittals should be scheduled
approximately 14 days prior to the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents establish the requirements for the MEDS
software.

13.2 **APPLICABLE DOCUMENTS**: None.

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Applicable Documents

c)  Engineering Requirements

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

5.  MTS

6.  MEDS Critical Tools

```{=html}
<!-- -->
```
d)  Verification Requirements

e)  Preparation of Delivery

f)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 500 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-l

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Interface Requirements/Design Document (IRDD) for the
Multifunction Display Unit Function (MDUF) of the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To establish the interface requirements and
design for the Multifunction Display Unit Function (MDUF) which includes
the MDUF software and MDUF firmware.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittals should be scheduled
approximately 14 days prior to the MDUF SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document establishes the interface requirements and
design for the Multifunction Display Unit Function (MDUF) which includes
the MDUF software and MDUF firmware.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Interface Design

d)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 501 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-m

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Interface Requirements Specification (IRS) for the
Analog-to-Digital Converter (ADC) of the Multifunction Electronics
Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To define the interface requirements for the
ADC firmware.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittals should be scheduled
approximately 14 days prior to the ADC Firmware SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This specification provides the interface requirements
for the ADC firmware.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Applicable Documents

c)  Interface Specification

d)  Quality Assurance

e)  Preparation for Delivery

f)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 502 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-n

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Interface Design Document (IDD) for the Analog-to-Digital
Converter (ADC) of the Multifunction Electronic Display Subsystem
(MEDS).

7\. **DESCRIPTION/USE**: To describe the interface design for the ADC
firmware.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittals should be scheduled
approximately 60 days after the ADC Firmware SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document describes the interface design of the ADC
firmware.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Applicable Documents

c)  Interface Design

d)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 503 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-o

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Design Documents (SDD) for the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To establish the software design of the MEDS
software.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative. Planned submittals should be scheduled
approximately 60 days after the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents establish the software design of the
MEDS software.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Preliminary Design

d)  Detailed Design

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

5.  MTS

```{=html}
<!-- -->
```
e)  CSCI Data

f)  CSCI Data Files

g)  Requirements Traceability

h)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 504 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-p

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Programmers Manuals for the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To aid in the modifying and testing of the MEDS
software.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as requested
by the Contracting Officer's Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents describe the organization and techniques
used to modify and test changes to the MEDS software.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Software Programming Environment

d)  Programming Information

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

```{=html}
<!-- -->
```
e)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 505 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-q

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Development Folders (SDFs) for the Multifunction
Electronic Display Subsystem (MEDS).

7\. **DESCRIPTION/USE**:

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As requested.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents provide a repository for information the
Flight Software developers need to maintain the FSW (e.g., current
requirements, code design, schedules, notes, etc.).

13.2 **APPLICABLE DOCUMENTS**: None.

13.3 **CONTENTS**: This document shall contain:

a)  Design considerations and constraints

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

5.  MEDS Critical Tools

```{=html}
<!-- -->
```
b)  Design documentation and data

c)  Schedule and status information

d)  Test requirements and responsibilities

e)  Test cases, procedures, and results

13.4 **FORMAT**: Contractor format.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 506 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-r

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Release Authorization Signature Sheet (RASS)

7\. **DESCRIPTION/USE**: The Release Authorization Signature Sheet
(RASS) provides authorization for the MEDS flight software to be
released.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each MEDS flight software
increment and in support of each flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Release Authorization Signature Sheet (RASS)
provides authorization for the MEDS flight software to be released. This
sheet must be approved by the chairman of the SASCB prior to the
software being released.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: The RASS shall contain:

a)  Product identification

b)  Purpose and description

c)  List of facilities authorized to use the software

d)  Any restrictions place on the release

e)  Description of the products contained in the release

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 507 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-s

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Test Description (STD) for the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To establish the test cases and procedures to
be used for verification of the MEDS software releases.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative, with baseline prior to the Test Readiness
Review (TRR) and delivery no later than 2 weeks prior to the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents establish the test cases and test
procedures for the MEDS software which are necessary to perform
Verification tests.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Verification Test Preparations

d)  Verification Test Descriptions

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

```{=html}
<!-- -->
```
e)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 508 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-t

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Test Reports (STR) for the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To provide documentation of the test results of
the verification tests performed on the MEDS software.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative, with planned delivery no latter than one week
prior to the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**:

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document provides a record of the verification
tests performed on the MEDS software.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Overview of Test Results

d)  Detailed Test Results

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

```{=html}
<!-- -->
```
e)  Test Log

f)  Notes

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 509 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-u

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Software Version Increment Deliverables

7\. **DESCRIPTION/USE**: To provide MEDS Flight Software and support
tools utilized to fly and support Shuttle missions.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative, with planned delivery at the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The MEDS Software Version Increment deliverables consist
of the files necessary for the MEDS flight software and support tools as
utilized to fly and support shuttle missions.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: The MEDS Software Version Increment deliverables
include:

a)  MEDS flight software files

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software

4.  MDU UDI

5.  ADCF

```{=html}
<!-- -->
```
b)  MEDS support software files

```{=html}
<!-- -->
```
1.  IDP Support Software

2.  MTS

3.  MTS Support Software

4.  MDUF FQT

5.  MOM

6.  AFTS

7.  Portable Loader Software

```{=html}
<!-- -->
```
c)  Flight software documentation

d)  Support Tools documentation

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 510 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-v

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Version Description Documents for the Multifunction
Electronic Display Subsystem (MEDS)

7\. **DESCRIPTION/USE**: To provide the configuration data required to
support software delivery to using sites.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative, with planned submittal with each MEDS
software deliverable.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents describe the configuration status
accounting that identifies the as-built configuration of the software.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Scope: identifies this document and its relationship to the system.

b)  Referenced Documents: identifies all documents referenced in this
    document.

c)  Version Description: describes the contents, revision, date,
    delivery instructions, media description, changes, and installation
    instructions.

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software

4.  MDU UDI

5.  ADCF

6.  MTS

7.  MTS Support Software

8.  IDP Support Software

9.  MDUF FQT

10. MOM

11. AFTS

12. Portable Loader Software

```{=html}
<!-- -->
```
d)  Notes: contains general information that aids in understanding this
    document, including a list of acronyms used within this document.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 511 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-w

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Software Acceptance Review (SAR) Briefing

7\. **DESCRIPTION/USE**: To provide a description of the development and
verification of the MEDS software to assure the customer that the
software was developed per the requirements and is ready to support
Shuttle missions.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer's Technical Representative (COTR), or
designated representative, with planned submittal at the SAR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The MEDS SAR briefing describes the development process,
the verification process and results, and verification that the software
is ready to support Shuttle missions.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: This briefing package shall cover:

a)  Schedule

b)  Notes and Waivers

c)  Verification

d)  Open Items

e)  Performance Metrics

f)  Quality Metrics

g)  MEDS software tools

h)  Conclusion

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 512 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-x

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: User's Manual for the Hardware Dependent Executive (HDX)
Support Utilities of the Multifunction Electronic Display Subsystem
(MEDS)

7\. **DESCRIPTION/USE**: To describe the user interface and execution of
the HDX Support Utilities (HSU).

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As requested.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document contains descriptions of the user
interface and execution of the HSU in terms of its function,
performance, and external interface capabilities.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain:

a)  Introduction

b)  General Description

c)  Utility Descriptions

d)  Notes

e)  Index

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 513 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-y

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MDU Object Manipulator (MOM) User's Guide

7\. **DESCRIPTION/USE**: To describe the user interface and execution of
the MOM.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as requested
by the Contracting Officer's Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document contains descriptions of the user
interface, commands, and execution of the MOM in terms of its function,
performance, and external interface capabilities.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: This document shall contain descriptions of:

a)  Startup

b)  Keyboard Inputs

c)  Script Files

d)  Data Manipulation and Flow Control

e)  Graphics Commands

f)  General Notes on Graphics Templates

g)  MOM Editor

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 514 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.13-z

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Software Standards and Procedures Manual (SSPM)

7\. **DESCRIPTION/USE**: To document MEDS tasks and duties, including
procedures, checklists, and general information for all areas of the
MEDS Project.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as requested
by the Contracting Officer's Technical Representative (COTR), or
designated representative.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.13

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The SSPM contains standard and procedures used during
the development of all Computer Software Configuration Items (CSCIs)
developed.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: The SSPM contains procedures, checklists, forms, and
general information used to develop CSCIs for the MEDS.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 515 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.14-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Software Discrepancy Resolution Authorization

7\. **DESCRIPTION/USE**: Consists of:

a)  MEDS Software Discrepancy Report (DR), used to document MEDS
    software issues

b)  MEDS Software Discrepancy Report (DR) Management Form, used to
    provide the rationale for selecting the appropriate disposition on a
    DR.

c)  As required MEDS Waiver, used to describe anomalous behavior of the
    MEDS flight software that is in violation of the software
    requirements but will be flown anyway

d)  As required MEDS Note, used to describe anomalous idiosyncrasies of
    the MEDS flight software observable by the crew, by the ground
    flight controllers, or from the analysis of data dumped during a
    flight.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.14

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Includes products used by the Shuttle Avionics Software
Control Board (SASCB) to authorize discrepancy resolutions against the
MEDS flight software and critical tools.

13.2 **APPLICABLE DOCUMENTS**: none.

13.3 **CONTENTS**:

a)  MEDS Software Discrepancy Report (DR)

b)  MEDS Software Discrepancy Report (DR) Management Form

c)  MEDS Waiver

d)  MEDS Note

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 516 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.14-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MEDS Software Interim Release Deliverables

7\. **DESCRIPTION/USE**: To formally release MEDS software developed to
satisfy testing, training, and mission objectives in the laboratory
environment.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.14

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The MEDS Software Interim Release deliverables consist
of the files necessary for the use of the interim release for testing,
training, and mission objectives in the laboratory environment.

13.2 **APPLICABLE DOCUMENTS**: none

13.3 **CONTENTS**: The MEDS Software Interim Release deliverables
include:

a)  MEDS flight software files

```{=html}
<!-- -->
```
1.  IDP Software

2.  MDUF Software

3.  Portable Loader Software

```{=html}
<!-- -->
```
b)  Version Description Document

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 517 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.15-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: PC-Decom Software Delivery Requirements

7\. **DESCRIPTION/USE**: Describes the expected deliveries and schedules
for PC-Decom software deliverables.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: Submission of products shall be divided
into the following categories:

1.  System Releases: Release schedules will be specified in and approved
    by the POCCB.

2.  Configurables: First use of PC-Decom software following release of
    FSW Operational Increment as well as required by changes in downlist
    specifications after the OI is released.

3.  Support Program Releases: Release schedules will be specified in and
    approved by the POCCB.

4.  Customer Support: As required.

11\. **REMARKS**: N/A

12\. **INTERRELATIONSHIP**: N/A

13\. **DATA PREPARATION INFORMATION**: N/A

13.1 **SCOPE**: Covers all PC-Decom software development and maintenance

13.2 **APPLICABLE DOCUMENTS**: Payload and General Support Computer

(PGSC) Interface Definition Document

Shuttle Data Integration Plan (DIP), JSC-18206,

Vol. III

13.3 **DATA/PROGRAM CONTENTS**:

a)  System Releases: New versions of PC-Decom software delivery contents
    and delivery dates shall be approved at the POCCB. Documentation
    delivered shall be consistent with expectations of Original
    Equipment Manufacturer (OEM) program deliveries.

b)  Configurables : Delivery contents and delivery dates shall coincide
    with requirements for use configurables on first PGSC training load.
    Contents for this delivery shall only consist of data (no program
    code).

c)  Support Program Releases: New or re-released support program
    contents and delivery dates shall be approved at the POCCB.
    Documentation delivered shall be consistent with expectations of
    Original Equipment Manufacturer (OEM) program deliveries.

d)  Customer Support: As required.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 518 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Data Reconfiguration Deliverables

7\. **DESCRIPTION/USE**: To reconfigure various Shuttle facilities and
flight software for each mission.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each flight

11\. **REMARKS**: Data content for the reconfiguration database is
controlled by Data Change Request (DCR\'s) approved by NASA. Deliverable
products are sent to external organizations for each mission.

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16, 1.4.3.1, 1.4.3.3

13.0 **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The FSW data reconfiguration products required for STS
mission reconfiguration.

13.2 **APPLICABLE DOCUMENTS**:

NSTS-21000-A04 Standard Integration Plan Annex 4, Command and Data (C&D)
Requirements

JSC\--10784 Space Shuttle Telemetered and Recorded Data Format
Requirements

JSC-18206 Shuttle Data Integration Plan(DIP) Volumes I and III

JSC-22438 STS Calibration Handling Handbook

JSC-20201 Operational Shuttle Data Reconfiguration Plan (OSDR)

Volume I OSDR Plan and Procedures

Volume II Space Transportation Automated Reconfiguration (STAR) Data
Collection and

Integration Procedures

Volume III Measurement and Stimuli (MAST II) Data Collection and
Integration User\'s Guide

JSC-08338 Shuttle Avionics MASS Memory Computer Program Integration Plan
(MIP)

SS-P-002-580 Space Shuttle Computer Program Development Specifications
(CPDS)

Functional Level Requirements, Systems Management

13.3 **CONTENTS**: The categories include:

a)  Level C Datasets (LVLC DS): Reconfigurable SM/PM FSW data
    requirements formatted for input to the PASS and BFS preprocessors

b)  Channelization File (CHANFILE): OI, PDI and PL buss channelization
    used in the generation of Level C datasets

c)  Telemetry Format Load (TFL): Micro code that executes within the
    PCMMU Formatters and extracts data for transmission to end ground
    facilities

d)  Decommutation Format Load (DFL): Micro code that executes within a
    PDI decom for decommutation of payload data streams

e)  Fetch Point Load (FPL): Micro code that executes within the FPM to
    ensure access to all PDI toggle buffer data.

f)  Payload Dataset (PDS): Four files for each payload unit containing
    all payload hardware and software measurements as well as onboard,
    uplink and buildable commands

**DRD CONTINUATION SHEET**

**TITLE**: Data Reconfiguration Deliverables **DRD NO.**: 1.4.3.16-a

**DATA TYPE**: 3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

g)  Shuttle Dataset (SDS) (also known as the Shuttle Data Tape): Seven
    files that contain attributes of all valid flight measurements such
    as channelization, telemetry loading, calibration, real time and
    multiple real time commands valid for the flight

h)  Telemetry Descriptor Dataset (TDS): Four files that contain all PSP
    configuration messages, all defined telemetry configurations and
    each individual format structure

i)  Prestored Command Data (PCD): The set of prestored commands

j)  Master Measurement Listing (MML): A subset of data attributes for
    applicable MSIDs

All deliverable products must be accompanied with appropriate
descriptions and release authorization as shown in the Operational
Shuttle Data Reconfiguration Plan, JSC-20201 DRD 1.4.3.16-f.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required, by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 519 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-b

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Reconfiguration Tools Requirements Documents

7\. **DESCRIPTION/USE**: Defines the requirements and specifications for
the Reconfiguration Tools used to perform the Shuttle Reconfiguration
processes.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with approved changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The requirements documents for the Reconfiguration Tools
used for the Shuttle Reconfiguration processes.

13.2 **APPLICABLE DOCUMENTS**:

Support Requests (SRs) authorizing changes to these requirements.

Flight Software Applications CCP Controlled Tools Software Inventory
(DRD-1.4.3.16-C)

13.3 **CONTENTS**: These documents specific software requirements. The
individual Requirements Documents are defined in the Flight Software
Applications CCP Controlled Tools Software Inventory.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 520 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Software Applications CCP Controlled Tools
Software Inventory

7\. **DESCRIPTION/USE**: An inventory and brief description of the CCP
controlled Flight Software Application Tools (FSWAT) which are used to
update and verify the data used to generate flight-to-flight
reconfiguration products for the Space Shuttle Transportation System.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required with approved changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The inventory defines the Reconfiguration Application
Systems Software necessary to support Data Reconfiguration for Shuttle
flight.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Each tool will be identified and will include the
following information: a brief description, applicable computer system,
language the tool is written in, number of source lines of code (SLOCS),
users of the tool, and identification of reference documentation
(requirements, design, users guide).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by PCN's
or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 521 **ISSUE**: basic 2. **DRD NO.**: 1.4.3.16-d

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Orbiter Command and Data Annex

7\. **DESCRIPTION/USE**: This document defines and documents the Shuttle
payload command and data software requirements for use by Mission
Operations Directorate, the payload customer, and the flight software
community.

8\. **DISTRIBUTION**: Per contracting officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required for each flight

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document defines the shuttle payload command and
data software requirements provided by the payload customer and JSC
payload operations personnel. These requirements shall be provided in
accordance with NSTS-21000-A04 Standard Integration Plan (SIP) Annex No.
4 Command and Data Requirements.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 21000-A04 SIP Annex No. 4 Command and Data Requirements

13.3 **CONTENTS**: This document shall contain the command and data
annex tables as reflected in section 2.0 of appendix F of
NSTS-21000-A04, SIP Annex No. 4 Command and Data Requirements as
applicable to the Payload.

13.4 **FORMAT**: To be prepared in accordance with NSTS-21000-A04, SIP
Annex No. 4 Command and Data Requirements.

13.5 **MAINTENANCE**: Changes will be updated as required by page change
notice (PCNs) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 522 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: SM/PM Level C Functional Subsystem Requirements (FSR)

7\. **DESCRIPTION/USE**: To document the detailed Level C software
reconfiguration data for all shuttle orbiter and payload systems.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As needed and as required for each flight

11\. **REMARKS**: Data Content is controlled by Data Change Requests
(DCRs) approved by NASA.

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents define the payload and SM Level C data
used in the Flight Software Reconfiguration Process.

13.2 **APPLICABLE DOCUMENTS**:

SS-P-0002-580 SM Level B Computer Program Development Specification
(CPDS), Volume V, Book 8

JSC-18206 Shuttle Data Integration Plan Volume III

NSTS-21000-A04 Standard Integration Plan Annex No. 4 Command and Data
Requirements

13.3 **CONTENTS**:

a)  Systems Management Level C Flight Software Requirements (FSR)
    JSC-19590

> Contains the detailed Level C SM reconfiguration data for all shuttle
> orbiter systems

b)  Payload Management Level C Flight Software Requirements (FSR)
    JSC-19478 (delivered for each flight)

> Contains the detailed Level C payload and mission dependant RMS FSW
> requirements
>
> Sections 1-4 generic information (delivered as needed)
>
> Sections 5-8 flight specific information (delivered for each flight)

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by page
change notice (PCN\'s) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 523 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Operational Shuttle Data Reconfiguration Plan (OSDR)
(JSC-20201)

7\. **DESCRIPTION/USE**: To establish the plans and procedures for using
the STAR and MAST II systems to accomplish the reconfiguration process.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with the ongoing submission
schedule from the SFOC.

10\. **SUBMISSION FREQUENCY**: Reviewed yearly, updated as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents define plans and procedures used by the
Reconfiguration process to generate products for STS mission
reconfiguration.

13.2 **APPLICABLE DOCUMENTS**:

JSC-18206 Shuttle Data Integration Plan Volumes I and III

13.3 **CONTENTS**:

a)  Volume I OSDR Plan

```{=html}
<!-- -->
```
1.  Functions, interfaces, and Operational procedures

2.  Organizational responsibilities for collection, integration,
    production, and release

```{=html}
<!-- -->
```
b)  Volume II STAR Data Collection and Integration Procedures

```{=html}
<!-- -->
```
1.  Procedures for Payload, Vehicle command, Telemetry, and Calibration

```{=html}
<!-- -->
```
c)  Volume III MAST II Data Collection and Integration User's Guide

```{=html}
<!-- -->
```
1.  Operational procedures

2.  Data base structure/operation

3.  Validation and verification tools

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by page
change notice (PCNs) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 524 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-g

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Standard Integration Plan Annex No. 4 Command and Data
Requirements (NSTS-21000-A04)

7\. **DESCRIPTION/USE**: To define the format and content of the payload
data required for Space Shuttle Program elements to integrate a payload
into the flight and ground operations. This document is also known as
the "generic blank book".

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Reviewed yearly, updated as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document is used by the payload customer to define
the payload requirements used by the FSW Data Reconfiguration process to
generate products for STS mission reconfiguration.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Vol XIV Space Shuttle System Payload Accommodations

ICD 2-19001 Shuttle Orbiter/Cargo Standard Interfaces

NSTS 21063-POC-CAP POCC Capabilities Document

SS-P-002-580 Space Shuttle Computer Program Development Specifications
(CPDS) Functional Level Requirements, Systems Management

SS-P-002-140 Space Shuttle Computer Program Development Specifications
(CPDS) Downlist/Uplink Software Requirements

JSC-18206 Shuttle Data Integration Plan Volume III

13.3 **CONTENTS**:

a)  Data Submission Requirements

b)  Requirements Integration

c)  Telemetry Standards

d)  Payload Measurement/Stimulus Identification Format

e)  Payload Data Tape Description

f)  Data element descriptions and values

g)  Cross Reference Tables

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by page
change notice (PCNs) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 525 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.16-h

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Shuttle Data Integration Plan (DIP) (JSC-18206)

7\. **DESCRIPTION/USE**: To define responsibilities, release control,
and deliverable products from the Measurement and Stimuli (MAST) and
Space Transportation Automated Reconfiguration (STAR) data base systems
to support Space Transportation System (STS) operational flight planning
and implementation.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Reviewed yearly, updated as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.16

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: These documents define procedures, formats, and controls
used by the FSW Data Reconfiguration process to generate products for
STS mission reconfiguration.

13.2 **APPLICABLE DOCUMENTS**:

JSC-20201 Operational Shuttle Data Reconfiguration

Volume II Space Transportation Automated Reconfiguration (STAR) Data
Collection and Integration Procedures

Volume III Measurement and Stimuli (MAST) Data Collection and
Integration User\'s Guide

JSC-08338 Shuttle Avionics MASS Memory Computer Program Integration Plan
(MIP)

SS-P-002-580 Space Shuttle Computer Program Development Specifications
(CPDS) Functional Level Requirements, Systems Management

SS-P-002-140 Space Shuttle Computer Program Development Specifications
(CPDS) Downlist/Uplink Software Requirements

NSTS-21000-A04 Standard Integration Plan Annex No. 4 Command and Data
Requirements (blank book)

13.3 **CONTENTS**:

Volume 1 Procedures and Responsibilities

a)  Responsibilities

b)  Version and Release Definitions

c)  Configuration Control

d)  Data Test and Operations Board

e)  Release logistics and authorization

f)  Product labeling and Identification

Volume 3 MAST II/STAR Deliverable Products

a)  Data Management Concepts

b)  Description of Data Group Identifiers, Units and categories, and
    Data Elements

c)  Data Element Values

d)  Product Descriptions

**DRD CONTINUATION SHEET**

**TITLE**: Shuttle Data Integration Plan (DIP) (JSC-18206) **DRD NO.**:
1.4.3.16-h

**DATA TYPE**: 1 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by page
change notice (PCNs) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 526 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.17-a

3\. **DATA TYPE**: 2/3/4 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: SAIL Product Handbook and Product Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each SAIL test and documentation product.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to to keep documentation current with procedures, products, and
customer list. Products and deliverables will be in consonance with the
existing schedules.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.17

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The SAIL Product Handbook product glossary provides
detailed product definitions including use, types, government furnished
data, and delivery requirements for each SAIL product and deliverable.

13.2 **APPLICABLE DOCUMENTS**:

JSC 08663, Volume 1 SAIL Project Plan

JSC 08663, Volume 2 SAIL Configuration Management Plan

JSC 08663, Volume 3 SAIL Operations Management Plan

JSC 08663, Volume 4 SAIL Safety, Reliability and Quality Assurance
Support Plan

JSC 08663, Volume 5 SAIL Integrated Logistics Support Plan

USA000597 SAIL Master Upgrade Plan

USA002190 SAIL Flight Hardware/Software Mission Report

USA000275 SAIL MMES Configuration Definition Document

USA000276 SAIL MMES Configuration Definition Document

USA000277 SAIL MMES Configuration Definition Document

USA000278 SAIL MMES Configuration Definition Document

SAIL Laboratory Upgrade Requirements

SAIL Status for Bi-Weekly Shuttle Avionics Software Control Board

SAIL Test Requests

SAIL Process Flows

SAIL Flight Software Technical and Management Review

SAIL Configuration Control Panel Meeting Minutes

SAIL Software/Math Model Requirements

SAIL Standard Operating Procedures

SAIL Technical Reports

SAIL Data Products

SAIL Accomplishments Data Base

SAIL Test Control Documentation

SAIL Test and Implementation Plans

**DRD CONTINUATION SHEET**

**TITLE**: SAIL Product Handbook and Product Glossary **DRD NO.**:
1.4.3.17-a

**DATA TYPE**: 2/3/4 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.2 **APPLICABLE DOCUMENTS (continued)**:

SAIL Mission Support Plan

SAIL Software Readiness Review

SAIL 72-Hour Schedule

13.3 **CONTENTS**: The SAIL product handbook and glossary shall include
the functional areas of SAIL flight system and laboratory, logistics at
JSC SAIL, other NASA field centers, data/procedures/processes pertaining
to use/operation and upkeep/maintenance of laboratory elements and
flight system hardware and software, safety, reliability, etc.

DATA TYPE 2 deliverables shall include the following:

a)  The 5 NASA SAIL Management volumes -

Volume 1 SAIL Project Plan

Volume 2 SAIL Configuration Management Plan

Volume 3 SAIL Operations Management Plan

Volume 4 SAIL Safety, Reliability and Quality Assurance Support Plan

Volume 5 SAIL Integrated Logistics Support Plan

b)  The SAIL Master Upgrade Plan which defines the laboratory element
    upgrade plan for replacement of worn/aged equipment replacements,
    new or upgraded equipment or capability developments, etc.

c)  SAIL Test and Implementation Plans

d)  SAIL Laboratory Upgrade Requirements

DATA TYPE 3 deliverables shall include the following:

a)  SAIL Fight Software Technical Management Reviews

b)  SAIL Software and Math Model Requirements

c)  SAIL Standard Operating Procedures

d)  SAIL Accomplishments Data Base

e)  SAIL Status for Bi-Weekly Shuttle Avionics Software Control Board

f)  SAIL Mission Support Plan

g)  SAIL Software Readiness Review

h)  SAIL Test Requests

i)  SAIL MMES Configuration Definition Document

DATA TYPE 4 deliverables shall include the following:

a)  SAIL Process Flows

b)  SAIL Technical Reports

c)  SAIL Data Products

d)  SAIL Configuration Control Panel Meeting Minutes

e)  SAIL Test Control Documentation such as Test Preparation Sheets,
    Test and Checkout Procedures, Interim Discrepancy Reports,
    Discrepancy Reports, Test Constraints Reviews, etc.

f)  SAIL 72-Hour Schedule

g)  SAIL Flight Hardware/Software Mission Reports

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 527 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S Link Certification Package

7\. **DESCRIPTION/USE**: Briefing package will provide a summary of
changes and verification results. Package will discuss open issues and a
recommendation for field use of MAGRS-3S production link. The
Certification package serves as basis for the flight Release
Authorization Signature Sheet (RASS).

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with planned submittal prior to the Software
Readiness Review (SRR) of the first flight of a new Link.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**:

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Package shall consist of summary of link changes and
verification results. Package will list any open issues with technical
recommendations.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: N/A.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 528 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S Interface Control Document

7\. **DESCRIPTION/USE**: The MAGRS-3S Serial Input/Output Interface
Control Document specifies the interface requirements between the
MAGRS-3S Line Replaceable Unit and the Orbiter Avionics system. The
document is under the control of the SASCB.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with submittals planned as required. If
changed, submittal will occur at the earlier of the following (a) within
12 weeks of completion of functional qualification of the new production
release or (b) prior to SRR of the first flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18

13\. **DATA PREPARATION INFORMATION**: Vendor Format.

13.1 **SCOPE**: Limited to avionics interface between MAGRS-3S and
Orbiter Avionics suite.

13.2 **APPLICABLE DOCUMENTS**:

a)  MAGRS-3S Software Design Requirements Document

b)  Three String GPS System Requirements Document

c)  FSSRs

d)  BFS PRDs

13.3 **CONTENTS**: Specification of interface, including data messages,
between MAGRS-3S and Orbiter Avionics and Data Processing system.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 529 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S Software Design Requirements

7\. **DESCRIPTION/USE**: The MAGRS-3S Software Design Requirements
specify changes made to adapt the Rockwell Collins Miniaturized Airborne
GPS Receiver for Space Shuttle Program (SSP) use. The MAGRS-3S Software
Design Requirements, along with the Rockwell Collins MAGR SDR, form the
total specification set for the MAGRS-3S receiver.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as authorized
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative, with submittals planned as required. If
changed, submittal will occur at the earlier of the following (a) within
12 weeks of completion of functional qualification of the new production
release or (b) prior to SRR of the first flight.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Documents only contain modifications required to adapt
the MAGR for the SSP.

13.2 **APPLICABLE DOCUMENTS**:

a)  Rockwell Collins MAGR Software Design Requirements Document

b)  Three String GPS System Requirements Document

13.3 **CONTENTS**: Documents contain, at a minimum

a)  Scope

b)  Applicable Documents

c)  Functional Requirements

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: As required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 530 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S SASCB Discrepancy Report (DR) Management Forms

7\. **DESCRIPTION/USE**: MAGRS-3S SASCB Discrepancy Report Management
Forms are used to disposition for SASCB Discrepancy Reports written
against MAGRS-3S software.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required to support SSP program
schedules.

11\. **REMARKS**: DRD also covers analysis of Discrepancy Reports
required to arrive at a recommended disposition of DRs. DRs shall be
processed in accordance with SASCB Living SCR 89052.

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18.

13\. **DATA PREPARATION INFORMATION**: DR Management forms shall be
prepared and reviewed in accordance with SASCB SCR 89052 (SASCB DR
Procedures).

13.1 **SCOPE**: Limited to discrepant conditions or conditions requiring
a User Note.

13.2 **APPLICABLE DOCUMENTS**:

MAGRS-3S Software Design Requirements

MAGRS-3S Interface Control Document

MAGRS-3S Program Notes and Waivers

13.3 **CONTENTS**: As specified in SASCB Living SCR 89052.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Maintenance of the document will be performed in
accordance with the process document SASCB SCR 89052.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 531 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-e

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S Program Notes and Waivers

7\. **DESCRIPTION/USE**: If a SASCB Discrepancy Report is dispositioned
requiring either a requirement waiver or user note, a program note
and/or waiver is required to document the condition.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required, to support Space Shuttle
Program schedules.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: MAGRS-3S Discrepancy Reports requiring a program note
waiver, in accordance with SASCB Living SCR 89052.

13.2 **APPLICABLE DOCUMENTS**:

a)  MAGRS-3S Interface Control Document

b)  Rockwell Collins MAGR Software Design Requirements Document

c)  Three String GPS System Requirements Document

13.3 **CONTENTS**: In accordance with SASCB Living SCR 89052.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 532 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S Verification/Qualification Test Reports

7\. **DESCRIPTION/USE**: The MAGRS-3S Verification Test Reports contain
results of formal verification activities performed to assure that the
MAGRS-3S software meets functional and performance requirements.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as requested
by the Contracting Officer\'s Technical Representative (COTR), or
designated representative.

11\. **REMARKS**: This DRD describes verification test reports created
by the developing contractor, and are not intended to apply to
Integrated Avionics Verification Reports.

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This DRD describes verification test reports created by
the developing contractor, and are not intended to apply to Integrated
Avionics Verification Reports.

13.2 **APPLICABLE DOCUMENTS**:

a)  SASCB SCRs applicable to the MAGRS-3S software

b)  SASCB DRs applicable to the MAGRS-3S software

c)  MAGRS-3S Software Design Requirements

d)  MAGRS-3S Interface Control Document

13.3 **CONTENTS**: Description of verification test results.

13.4 **FORMAT**: Vendor Format acceptable.

13.5 **MAINTENANCE**: Not Applicable.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 533 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.3.18-g

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: MAGRS-3S Link Deliverables

7\. **DESCRIPTION/USE**: For each production release of MAGRS-3S
software, the following link deliverables will be compiled: The vendor
qualification test plan, test procedures, the MAGRS-3S source code,
vendor detailed design documentation, and the MAGRS-3S Link
Reprogramming package.

The MAGRS-3S Reprogramming Data Package is generated upon completion of
reprogramming a MAGRS-3S LRU. The data package consists of the completed
Parts Re-work/Replacement form, and the QA stamped reprogramming
procedure. The data package is used to a) provide objective evidence of
completion of receiver reprogramming and as the authorizing document to
update the receiver software configuration in the Orbiter configuration
management system. There is one Reprogramming Data Package for each LRU
reprogrammed.

The MAGRS-3S Detailed Design Documentation is used as reference material
to bridge the gap between the MAGRS-3S Software Design Requirements and
the MAGRS-3S source code. The vendor refers to detailed design
documentation as the MAGRS-3S B5/C5 documents.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Products shall be submitted as requested
by the Contracting Officer's Technical Representative (COTR), or
designated representative.

11\. **REMARKS**: None.

12\. **INTERRELATIONSHIP**: SOW 1.4.3.18

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**:

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: Upon request, the delivery shall include:

a)  Qualification Test Plan

b)  Qualification Test Procedures

c)  Vendor Detailed Design Documentation

d)  MAGRS-3S Reprogramming Data Package (also referred to as a QA12 Data
    Package) (hard copy only

e)  MAGRS-3S Source Code Listings

13.4 **FORMAT**: Vendor format is acceptable.

13.5 **MAINTENANCE**: Not Applicable.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 534 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.9-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Drawings, Engineering and Associated Lists

7\. **DESCRIPTION/USE**: To establish the requirements for the
maintenance, revision, and/or preparation of all drawings and associated
lists by a contractor.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Assumption of an on-going requirement; no
break in existing submission schedule.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall utilize and submit engineering
drawings in accordance with ASME Y14.00, Engineering Drawing Practices,
latest revision.

13.2 **APPLICABLE DOCUMENTS**: ASME Y14.00 Engineering Drawing
Practices, latest revision.

13.3 **CONTENTS**:

13.4 **FORMAT**: Contractor's format is acceptable.

13.5 **MAINTENANCE**:

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 535 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.9-b

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Food Contamination Control Plan

7\. **DESCRIPTION/USE**: To define the program to be implemented for
effective contamination control for the food production facility.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Updated as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall provide a document describing the
overall approach for implementation of an effective contamination
control program for the food and the food production facility.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The plan shall, as a minimum, specifically address
control of contamination by micro organisms, dust, pests, rodents,
chemicals, condensates, and other unsanitary sources as well as use of
clean room facilities and clean work stations and cleanliness levels to
be maintained.

The contractor shall maintain the plan as necessary to assure that it
accurately reflects his approach to contamination control in the food
and the food production facility.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 536 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.9-c

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Food Acceptance Documentation

7\. **DESCRIPTION/USE**: To provide documentation supporting the
acceptance of flight food assemblies for each mission.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: As required or upon NASA request

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The contractor shall maintain acceptance documentation
which shall show adherence of the food processes, procedures, and
analyses to required standards and specifications and provide the basis
for certification of the flight food assemblies for each mission. This
data shall be available to NASA upon request.

13.2 **APPLICABLE DOCUMENTS**: 528-48xxx. This is a flight unique
drawing which documents all food stowed for each mission. A copy of this
drawing shall be provided by the contractor to NASA 2 weeks prior to the
launch of each Shuttle mission.

13.3 **CONTENTS**: This documentation shall include as a minimum:
product identification; lot number; food manufacturing specification;
source; date of manufacture; microbiological; organoleptic and other
test results required for specific foods; waivers, deviations and MRB
actions; and the mission-specific Food Installation Drawing prepared in
accordance with DRD 1.4.9-a.

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 537 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.9-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Post Test Summary Report

7\. **DESCRIPTION/USE**: To fully report results of testing and/or
events of importance that involve support equipment, and Crew Escape
Equipment (CEE) (flight and training) a post test summary report shall
be generated.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Updates as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**:

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**:

13.4 **FORMAT**: Contractor format is acceptable.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 538 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.9-e

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Problem Reporting and Corrective Action (PRACA)

7\. **DESCRIPTION/USE**: To fully report problems, support disposition
of PPRs (as described below) and describe their resolutions

8\. **DISTRIBUTION**: JSC PRACA Center

NASA/JSC NT42/Bldg 45

Houston, TX 77058

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Updates as required

11\. **REMARKS**: Provide copies as requested.

12\. **INTERRELATIONSHIP**: SOW 1.4.9

13\. **DATA PREPARATION INFORMATION:**

13.1 **SCOPE**: PRACA reportable problems are defined as functional
failures, overstress or potential overstress of hardware, unsatisfactory
conditions, and unexplained anomalies which occur on flight products,
flight-like products, or safety critical ground support equipment (GSE)
during qualification testing and during or subsequent to acceptance
testing. GSE reporting is limited to GSE problems that could result in
loss of personnel capability or loss of vehicle systems.

13.2 **APPLICABLE DOCUMENTS**:

JSC 28035 JSC Government-Furnished Equipment (GFE) Problem Reporting and
Corrective Action (PRACA) Requirements, Latest Revision

13.3 **CONTENTS**:

13.4 **FORMAT**:

13.5 **MAINTENANCE**: Update as required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 539 **ISSUE**: BASIC 2. **DRD NO.**: 1.4.9-f

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Equipment Inventory Report

7\. **DESCRIPTION/USE**: To provide inventory oversight.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**:

10\. **SUBMISSION FREQUENCY**: Revisions as required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.4.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Equipment Inventory Report provides visibility of
the inventory of material, parts, subassemblies, and end items.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Equipment Inventory Report shall contain the
status of Government-furnished property (GFP) to include the following:

a)  Flight status: quantity.

b)  Repair and/or Refurbish status: current status report(flight and
    training).

c)  Quantity of material, parts, subassemblies, and end items:

```{=html}
<!-- -->
```
a)  On-hand.

b)  On order and projected order.

c)  Projected required to support the most current NSTS mission model.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 540 **ISSUE**: BASIC 2. **DRD NO.**: 1.5.1.2

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Operations and Contamination Control Plan for Integrated
Processing at Primary (KSC) and Alternate (DRFC/WSTF) Space Shuttle
Landing Sites.

7\. **DESCRIPTION/USE**: To document the approach to Shuttle/Payload
integrated processing and contamination control at the Primary Landing
Site (Orbiter Processing Facilities (OPF\'s) and Launch Pads) and
Alternate Landing Sites.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Annual revisions, as required

11\. **REMARKS**: The KSC Payload Changeout Room (PCR) Operations Plan
(KVT-PL-0024) develops and documents the STS approach to Shuttle Payload
integrated processing through the PAD PCR. The contents of this plan are
required to be consistent with the applicable documents shown in section
13.2 below as well as the Shuttle Facility Contamination Control
Implementation Plan (KSC-PL-0025).

The Shuttle Facility/Orbiter Contamination Control Implementation Plan
(KVT-PL-0025) develops and documents the STS approach to Payload
requirements for contamination controls. The contents of this plan are
required to be consistent with the applicable documents shown in section
13.2 below as well as KVT-PL-0024.

12\. **INTERRELATIONSHIP**: SOW 1.5.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Operations and Contamination Control Plan for
Integrated Processing at Space Shuttle Landing Sites develop and define
the contractor\'s approach to payload element processing during
integration activities at the Primary Landing Site during integration
activities at the Launch Pad and OPFs and at Alternate Landing Sites
during landing turnaround operations, and to document contamination
control processes and responsibilities at these sites.

13.2 **APPLICABLE DOCUMENTS**:

K-STSM-14.2.1 KSC Cargo Facility Contamination Control Plan

NSTS 08242 Space Shuttle Limitations for Non-Flight Materials and
Equipment Used In and Around the SSV

KVT-PL-0026 OPF Payload Operations Plan

13.3 **CONTENTS**: The contractor\'s approach and plan shall be
consistent with the scope and content of the applicable documents. The
contractor shall produce the following plans.

KVT-PL-0024 PCR Payload Operations Plan

This plan should include, but not be limited to, identification of key
positions and roles and responsibilities; contractor inter-element roles
and responsibilities; STS Payload interfaces for day-to-day operations;
meeting, scheduling, and working group requirements; STS approach to
local and test operations controls and discipline; processing support
requirements; concepts of control and operations; operational
requirements; emergency considerations; rules and regulations; standard
instructions; training requirements; and other information as may be
appropriate for user guidance during PCR processing.

**DRD CONTINUATION SHEET**

**TITLE**: Operations and Contamination Control Plan for **DRD NO.**:
1.5.1.2

Integrated Processing at Primary (KSC) and

Alternate (DRFC/WSTF) Space Shuttle Landing Sites.

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

KSC-PL-0025 Shuttle Facility Contamination Control Implementation Plan

This plan should include, but not be limited to, concepts of operations;
roles and responsibilities; contractor inter-element roles and
responsibilities; quality approach to inspection and compliance
assurance; problem reporting and corrective action procedures;
emergencies; rules and regulations; standard instructions; training
requirements; monitoring; garmet requirements and other planning
information as appropriate for effective operations or STS facilities to
meet payload highly sensitive contamination control requirements.

USA008839 Alternate Landing Site Shuttle Facility/Orbiter Contamination
Control Plan

The contractor is encouraged to minimize like documentation by
consolidating like plans and documentation.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change page or
complete reissue (indicate revision level and date).

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 541 **ISSUE**: BASIC 2. **DRD NO.**: 1.5.2.1

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: KSC Ground Launch Sequencer Configuration Plan

7\. **DESCRIPTION/USE**: To define the Ground Launch Sequencer
configuration for Launch Countdowns at KSC.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Per mission basis

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.5.2.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This plan defines the approach for implementing and
monitoring the approved Ground Launch Sequencer configuration.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 16007 Launch Commit Criteria and Background

KLO-82-0071 GLS Configuration

13.3 **CONTENTS**: This plan shall document an approach for implementing
and monitoring the approved Ground Launch Sequencer configuration. The
scope and content of this plan shall contain as a minimum the
KLO-82-0071/GLS Configuration plan.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Update 14 days prior to launch countdown
Call-to-Station.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 542 **ISSUE**: BASIC 2. **DRD NO.**: 1.5.2.3

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: KSC Launch Team Certification Plan

7\. **DESCRIPTION/USE**: To document the training, qualification and
certification process for the KSC Launch Control Team.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Assumption of an on-going requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: Annual revisions as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.5.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The KSC Launch Team Certification Plan documents, at a
minimum, the launch team certification process for Countdown
Call-to-Stations through Launch or scrub turnaround safing.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The plan shall document a standardized approach for
training the combined contractor/Government launch team for conducting
launch operations, providing flight crew pad emergency egress training,
and certifying that the contractor\'s engineers and operations managers
are fully qualified for conducting a launch countdown. The plan shall
encompass individual proficiency for each respective discipline as well
as in the launch process itself. Training plans shall include as a
minimum launch countdown simulations, active participation in integrated
testing activities, tanking simulations, detailed training on the
operation and maintenance of flight hardware, software, and support
equipment; and requirements, procedures, and related requirements and
processes.

13.4 **FORMAT**: Contractor format is acceptable with NASA approval.

13.5 **MAINTENANCE**: Changes shall be incorporated by change pages or
complete revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 543 **ISSUE**: BASIC 2. **DRD NO.**: 1.5.4.1

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Post Launch Operations Plans

7\. **DESCRIPTION/USE**: To document processes, products and
responsibilities for supporting landing and recovery operations at
locations other than KSC.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Annual review with revisions as required

11\. **REMARKS**: USA publishes the KSC Offsite Operations Plan in
response to this DRD. This plan is currently designated USA004376 and it
supersedes both SFOC GO0041and KVT-PL-0014.

USA publishes the KSC, Space Shuttle Program, Salvage Operations Plan in
response to this DRD. This plan is currently designated SFOC-GO0014 and
it supersedes the KSC NSTS Salvage Plan (KVT-PL-0021).

USA publishes the Convoy Operations Plan in response to this DRD. This
plan is currently designated SFOC-GO0022 and it supersedes Convoy
Operation Plan (KVT-PL-0015).

12\. **INTERRELATIONSHIP**: SOW 1.5.4.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Post Launch Operations plans describe government and
contractor responsibilities and implementation procedures for KSC
landings, off-site landings, convoy operations, salvage operations, and
transportation of personnel and equipment to and from off-site
locations.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700 Vol. VIII, Appendix G

NSTS 17462 XXX Flight Requirements Document

13.3 **CONTENTS**: The contractor shall develop and maintain (update)
plans that cover support, including but not limited to personnel and
equipment, for an Orbiter landing and recovery at primary, secondary, or
contingency landing sites, convoy operations and transportation of
personnel and equipment to off-site locations. The plan(s) shall specify
the order and mode by which personnel and equipment will be sent to and
returned from the designated landing site. These plans shall encompass
the scope and content of the applicable KSC and SSP documents in 13.2.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 256. **ISSUE**: BASIC 2. **DRD NO.**: 1.5.5.2

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/3

6\. **TITLE**: Facility and Equipment Maintenance Plan and Supporting
Data

7\. **DESCRIPTION/USE**: To document the contractor\'s method of
integrating the proper mix of preventive, predictive, programmed, and
run-to-failure maintenance on facilities, systems and equipment, and
software associated with hardware maintenance actions. To document the
required identification, schedules, budgets, and implementation methods
for the above maintenance-related activities of facilities, systems, and
equipment assigned to the contractor. This DRD has two parts, Facilities
and Collateral Equipment Requirements (Part I) and Non-Collateral
Equipment (Part II). Part I is applicable for all SPOC Facilities,
facility systems and collateral equipment responsibilities. Part II is
applicable to only Launch & Landing/Ground Ops. Non-collateral Equipment
(GSE, LPS). The contractor shall provide a subset of content applicable
for each location for all requirements in Part I (e.g., Ground Ops.,
SRB, Palmdale). The contractor shall provide content applicable for only
Ground Ops. for all requirements in Part II.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter.

9\. **INITIAL SUBMISSION**: Plan - 60 days after contract award.

10\. **SUBMISSION FREQUENCY**:

a)  Provide plan (updated or complete reissue) annually, each fiscal
    year; November 15.

b)  Provide annual deliverables (Table 13-1) each fiscal year by
    November 15.

c)  Provide trend analysis reports, 2 times a year; April 30 and
    November 15.

d)  Provide support to NASA Headquarters maintenance reporting calls
    with data collected within existing database sources in determining,
    as a minimum, Projected BMAR Estimates, NRC Maintenance and Repair
    Estimates and Unconstrained NRC Maintenance and Repair Estimates for
    requested fiscal years.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.5.5.2, 1.4, 1.1.6.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Plan shall include the contractors\' methodology of
integrating and reporting condition assessments for facilities, systems
and equipment within their associated maintenance programs, and their
planning efforts in identifying and reducing the Backlog of Maintenance
and Repair (BMAR). The plan shall also address their method in
implementing a proactive corrosion control program to insure facilities,
systems, and equipment receive proper attention to insure they achieve
or exceed their design life.

13.2 **APPLICABLE DOCUMENTS**:

NASA Directive NPD 8831.1D Maintenance of Institutional and Program
Facilities, and

Related Equipment

NASA Directive NPR 8831.2D Facility Maintenance Management

13.3 **CONTENTS**:

Deliverables include metrics and reports listed in Table 13-1 below.

**DRD CONTINUATION SHEET**

**TITLE**: Facility and Equipment Maintenance Plan and **DRD NO.**:
1.5.5.2

Supporting Data

DATA TYPE: 2 **PAGE**: 2/3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13\. **CONTENTS (continued)**:

Table 13-1:

+---+-------------------------------------------+------------+----------+
|   | Deliverable                               | PART I     | PART II  |
|   |                                           |            |          |
|   |                                           | (SPOC      | (Ground  |
|   |                                           | Wide)      | Ops.     |
|   |                                           |            | only)    |
|   |                                           | Facilities |          |
|   |                                           | &          | Non-co   |
|   |                                           | Collateral | llateral |
|   |                                           | Equip.     | E        |
|   |                                           |            | quipment |
+---+-------------------------------------------+------------+----------+
| a | No longer used.                           |            |          |
| \ |                                           |            |          |
| ) |                                           |            |          |
+---+-------------------------------------------+------------+----------+
| b | No longer used                            |            |          |
| \ |                                           |            |          |
| ) |                                           |            |          |
+---+-------------------------------------------+------------+----------+
| c | No longer used.                           |            |          |
| \ |                                           |            |          |
| ) |                                           |            |          |
+---+-------------------------------------------+------------+----------+
| d | BUDGET: Maintenance funding planned for   | Annual     | Annual   |
| \ | the next fiscal year (Initial Operating   |            |          |
| ) | Plan for M&R), in accordance with         |            |          |
|   | approved WBS structure, with a breakdown  |            |          |
|   | of Preventive Maintenance, Corrective     |            |          |
|   | Maintenance (including Trouble Calls),    |            |          |
|   | Programmed Maintenance and PT&I. (Ground  |            |          |
|   | Ops. tracks Trouble Calls as a separate   |            |          |
|   | category.)                                |            |          |
+---+-------------------------------------------+------------+----------+
| e | CONDITION ASSESSMENT: Aggregate condition | Annual     | Annual   |
| \ | assessment code data: one chart depicting |            |          |
| ) | aggregate facility data, and another      |            |          |
|   | presenting aggregate non-facility data.   |            |          |
|   | Applicability of condition assessment to  |            |          |
|   | individual pieces of equipment to be      |            |          |
|   | partnered with the Government.            |            |          |
+---+-------------------------------------------+------------+----------+
| f | CONDITION ASSESSMENT BACKLOG: Aggregate   | Semi       | Semi     |
| \ | proportion of Condition Assessments       | Annual     | Annual   |
| ) | overdue.                                  |            |          |
+---+-------------------------------------------+------------+----------+
| g | CORRECTIVE ACTIONS: A report identifying  | Semi       | Semi     |
| \ | corrective actions associated with any    | Annual     | Annual   |
| ) | maintenance metric whose indicators are   |            |          |
|   | below expectations.                       |            |          |
+---+-------------------------------------------+------------+----------+
| h | CORROSION CONTROL: A status report        | Annual     |          |
| \ | addressing corrosion issues by facility   |            |          |
| ) | and equipment. Report indicates repair    |            |          |
|   | costs, activity, backlog, and scheduled   |            |          |
|   | corrective action dates. This requirement |            |          |
|   | shall be partnered with each site's       |            |          |
|   | applicable Government counterpart.        |            |          |
+---+-------------------------------------------+------------+----------+
| i | PM/Total Maintenance: Ratio of PM cost to | Sem        | Semi     |
| \ | Total Maintenance Costs (Cost by          | i-Annually | Annually |
| ) | facility/system for Ground Ops only.)     |            |          |
+---+-------------------------------------------+------------+----------+
| j | CM/Total Maintenance: Ratio of CM to      | Semi       | Semi     |
| \ | Total Maintenance Costs (Cost by          | Annually   | Annually |
| ) | facility/system for Ground Ops. only.)    |            |          |
+---+-------------------------------------------+------------+----------+
| k | Annual M&R Funding w/o CoF: Operating     | Annual     |          |
| \ | Plan for current year.                    |            |          |
| ) |                                           |            |          |
+---+-------------------------------------------+------------+----------+
| l | UNCONSTRAINED M&R w/o CoF: Total          | Annual     |          |
| \ | requirement for current year.             |            |          |
| ) |                                           |            |          |
+---+-------------------------------------------+------------+----------+
| m | PM PERFORMANCE: Ratio of performed PM     | Monthly    | Monthly  |
| \ | tasks to scheduled PM tasks.              |            | (        |
| ) |                                           | (provided  | provided |
|   |                                           | in PMS)    | in PMS)  |
+---+-------------------------------------------+------------+----------+

**DRD CONTINUATION SHEET**

**TITLE**: Facility and Equipment Maintenance Plan and **DRD NO.**:
1.5.5.2

Supporting Data

**DATA TYPE**: 2 **PAGE**: 3/3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

Table 13-1 (Continued):

+---+------------------------------------------+------------+----------+
|   | Deliverable                              | PART I     | PART II  |
|   |                                          |            |          |
|   |                                          | (SPOC      | (Ground  |
|   |                                          | Wide)      | Ops.     |
|   |                                          |            | only)    |
|   |                                          | Facilities |          |
|   |                                          | &          | Non-co   |
|   |                                          | Collateral | llateral |
|   |                                          | Equip.     | E        |
|   |                                          |            | quipment |
+---+------------------------------------------+------------+----------+
| n | PLAN vs. ACTUAL COSTS: Cost variance     | Annual     | Annual   |
| \ | (dollar and percentage) in accordance    |            |          |
| ) | with approved WBS structure and          |            |          |
|   | maintenance type ( Preventive            |            |          |
|   | Maintenance, Corrective Maintenance      |            |          |
|   | (including Trouble Calls), Programmed    |            |          |
|   | Maintenance and PT&I.) (Ground Ops.      |            |          |
|   | track Trouble Calls as a separate        |            |          |
|   | category.)                               |            |          |
+---+------------------------------------------+------------+----------+
| o | COST TREND REPORT: Maintenance           | Annual     | Annual   |
| \ | expenditure trends report by in          |            |          |
| ) | accordance with approved WBS structure   |            |          |
|   | and maintenance type Preventive          |            |          |
|   | Maintenance, Corrective Maintenance,     |            |          |
|   | Programmed Maintenance and PT&I.)        |            |          |
+---+------------------------------------------+------------+----------+
| p | No longer used.                          |            |          |
| \ |                                          |            |          |
| ) |                                          |            |          |
+---+------------------------------------------+------------+----------+
| q | No longer used                           |            |          |
| \ |                                          |            |          |
| ) |                                          |            |          |
+---+------------------------------------------+------------+----------+
| r | PT&I Finds                               | Annual     |          |
| \ |                                          |            |          |
| ) |                                          |            |          |
+---+------------------------------------------+------------+----------+
| s | Cost of Scheduled Work: Cost of          | Annual     |          |
| \ | scheduled work consisting of PM, PT&I,   |            |          |
| ) | PGM, ROI and PT&I finds repair costs.)   |            |          |
+---+------------------------------------------+------------+----------+

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

e)  
f)  
g)  
h)  

  --- ------------------------------------------- ------------ ----------
                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               
  --- ------------------------------------------- ------------ ----------

  ---- ------------------------------------------- ------------ ----------
                                                                

                                                                

                                                                

                                                                

                                                                

                                                                

                                                                
  ---- ------------------------------------------- ------------ ----------

13.4

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 546 **ISSUE**: BASIC 2. **DRD NO.**: 1.5.5.3

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Notification of Modifications to KSC Configured Systems
and Equipment Report

7\. **DESCRIPTION/USE**: To notify the Government of contractor planned
and/or initiated modifications to KSC configured systems, facilities,
and equipment, including hardware, software, and operating procedures.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: Within 7 days of project/change approval
by the contractor, but in all cases prior to implementation.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.5.5.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This report provides notification to the Government of
modifications to KSC configured systems, facilities, and equipment.

13.2 **APPLICABLE DOCUMENTS**:

KSC Drawing 79K09579 identifies the configured systems and equipment.

13.3 **CONTENTS**: This report shall describe the modification of the
hardware, software, and/or operating procedures for the configured
systems and equipment, and provide the justification for making the
change.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 547 **ISSUE**: BASIC 2. **DRD NO.**: 1.5.5.4.3-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Training/Certification Plan and Schedule Report

7\. **DESCRIPTION/USE**: To describe the contractor\'s method for
training and certifying contractor and non-contractor personnel, and the
procedures for getting training.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Consistent with ongoing submission schedule
from the SFOC.

10\. **SUBMISSION FREQUENCY**: MONTHLY

11\. **REMARKS**: NAS10-10900, DRL item 031

12\. **INTERRELATIONSHIP**: SOW 1.5.5.4.3; DRD 1.4-c

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This plan and report shall apply only to technical
training related to flight hardware and associated GSE.

13.2 **APPLICABLE DOCUMENTS**:

NHB 5300.4 (ID-2), Safety, Reliability, Maintainability and Quality

paragraph ID500.7 Provisions for the Space Shuttle Program

13.3 **CONTENTS**:

a)  The plan shall include:

```{=html}
<!-- -->
```
1.  Description of the contractor certification program including a list
    of certifications.

2.  Training requirements to meet each of those certifications.

3.  Procedure that establishes the individual\'s certification.

4.  How certification records will be maintained.

5.  Procedures by which NASA and other contractor personnel may obtain
    training.

```{=html}
<!-- -->
```
b)  The contractor shall periodically publish a training schedule.

c)  The contractor shall report on any ground or flight processing
    incidents that were due to lack of training or certification.
    Corrective action shall be reported.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 548 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.1

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Annex 7 (Training) - Payload Integration Plan

7\. **DESCRIPTION/USE**: Agreement with Space Shuttle Program (SSP)
Program Office and payload customer which includes training
responsibilities and requirements for flight controllers and flight
crew.

8\. **DISTRIBUTION**: Per Space Shuttle Program Office procedures

9\. **INITIAL SUBMISSION**: First Cargo Integration Review after
Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Submitted per payload, per flight, to
support the Cargo Integration Review if required by the Payload
Integration Plan (PIP) as negotiated between the payload customer and
the Annex 7 Book Manager.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.1, 1.6.1.2, 1.6.1.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Annex 7 (Training) - Payload Integration Plan
defines facility requirements and lesson responsibilities of
payload-specific training for SSP flight controllers and flight crew.

13.2 **APPLICABLE DOCUMENTS**:

NSTS 07700, Vol. 4 SSP Configuration Management Requirements and
Customer and Flight Integration Configuration Management Work
Instructions

NSTS-2100-A07 Training Annex Data Requirements Payload Integration Plan
(Blank Book)

13.3 **CONTENTS**: In accordance with NSTS-2100-A07, Annex 7 shall
contain specifications and agreements of Space Transportation System
(STS) crew training requirements (skills, training facilities, training
duration and schedule), Integrated Training Facility (ITF) model
requirements, integrated Mission Control Center (MCC)/Operations Support
Center (OSC) training requirements, integration simulation requirements,
and schedules.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per Training Annex Data Requirements Blank Book.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 549 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.1.1

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Operations Training Records.

7\. **DESCRIPTION/USE**: Records of as-performed training for purposes
of Flight Crew, Flight Controller, Instructor and Contractor Accountable
Function (CAF) Certification.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Upon request.

10\. **SUBMISSION FREQUENCY**: As requested.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.1.1.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Records required demonstrating that training was
conducted for flight crews and position unique certification for flight
controllers and any contractor supplied services that require
certification.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Contractor shall input and maintain training records
when lessons are complete and record all significant student, lesson,
integrated training objectives (when applicable), and facility data. At
a minimum, the records should include: student name, lesson title,
lesson code, date training was conducted, time training was conducted,
facility designation, time the facility was unavailable for training,
and whether or not the lesson was successfully accomplished.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Records and data should be accessible within 10
days after completion of lesson.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 550 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.1.2-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. P**A**GE: 1/1

6\. **TITLE**: Training Development and Support Plan (TDSP) JSC 36049.

7\. **DESCRIPTION/USE**: To document processes that are utilized for
curriculum and lesson development.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: 30 days after contract award.

10\. **SUBMISSION FREQUENCY**: Annually if required. If no updates are
required, the document does not have to be resubmitted. The DT NASA
Resident Office will be notified.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.1.2.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Training Development Support Plan (JSC 36049)
defines curriculum (training flow) and lesson development processes that
will be used to develop new Shuttle lessons and Station lessons as
defined in crew training catalogs and flight controller/instructor
certification guides.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The Training Development and Support Plan will
document curriculum and lesson development processes. Processes will be
differentiated as a function of lesson delivery media. The Training
Development and Support Plan shall document lesson plan formats.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue. The document is to be reviewed annually
for accuracy and completeness. If the document does not require changes,
the document does not have to be resubmitted. However, the NASA Resident
Office should be notified that no changes were required and the document
is up to date.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 551 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.1.2-b

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Curriculum, Lesson, and Instructor Feedback

7\. **DESCRIPTION/USE:** To document quality of Space Shuttle (SS) and
International Space Station (ISS) flight operations curriculum and
lessons.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Upon request

10\. **SUBMISSION FREQUENCY**: Be available to support all Process
Integrity Reviews

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Curriculum and lesson feedback data shall document
appraisals of flight operations training as delivered for SS and ISS
flight crews and flight controllers.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Collect and maintain student feedback data on lesson
quality and performance.

a)  Lesson data collected should appraise: lesson effectiveness, lesson
    efficiency, and placement in the curriculum.

b)  Instructor performance data collected should appraise: Instructor's
    presentation and technical competence.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Records and data accessible within 10 days after
completion of lesson. A process will be set up that meets NASA and
contractor needs in order to sort and store these records.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 552 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.1.4

3\. **DATA TYPE**: 3/4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Instructor Certification Guides

7\. **DESCRIPTION/USE**: To define process to certify flight operations
instructors for Shuttle. To provide a document containing the process to
certify flight operation instructors for Station.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Upon request

10\. **SUBMISSION FREQUENCY**: Certification Guide for each instructor
certifiable position: copy per revision (Type 3 for CAF and GAF) Shuttle
Training Division Assignment Sheet and certification records: as
requested (Type 4).

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.1.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Shuttle Instructor Certification guides shall
identify how the instructor will demonstrate qualification for all
formal flight operations training lessons. The Station Instructor and
Extravehicular Activity (EVA) Certification guides will be managed under
USA configuration control per DT NASA request.

13.2 **APPLICABLE DOCUMENTS**:

JSC 36049 Training Development and Support Plan

DA-WI-16 MOD Space Flight Personnel Certification Plan

13.3 **CONTENTS**: The Shuttle Instructor Certification Guides shall
include a description of curriculum, lesson descriptions, training
objectives, and final certification criteria. The Shuttle Training
Division Assignment Sheet shall identify instructor assignments to
training teams and be maintained for one year. The contractor shall
maintain certification records and documentation for all instructors in
accordance with the MOD Space Flight Personnel Certification Plan
(DA-WI-16).

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 553 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.2-a

3\. **DATA TYPE**: 2/3 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Flight Controller Certification Guides

7\. **DESCRIPTION/USE**: Certification curriculum and requirements for
SSP and ISSP NASA Civil Service flight controller certifiable positions
and for contractor-provided certifiable positions.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annually, or on a flight-specific basis
if special training requirements are identified

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The document covers flight controller certification and
lesson as required by the MOD Resident Office. Positions will be jointly
agreed to by responsible MOD Resident Office and SPOC Flight Operations
organization. Government accountable positions will be specified in the
annual Government Accountable Function Directive (GAFD). The contractor
develops certification and lessons based on NASA Flight Control task
requirements. ISSP flight controller certification and lesson
requirements will be transitioned to the contractor when they mature and
stabilize.

13.2 **APPLICABLE DOCUMENTS**:

JSC 36049 Training Development and Support Plan

DW-WI-16 MOD Space Flight Personnel Certification Plan

13.3 **CONTENTS**: The contractor shall submit a description of
curriculum, lesson descriptions, and final certification criteria. The
document shall contain the following:

a)  Reference to the required training material including manuals,
    workbooks, texts, videos, computer based training lessons,
    briefings, tours, and any other material required for certification.

b)  Requirements for simulation support, and on-the-job training needed
    for certification.

c)  Descriptions for tasks which must be demonstrated by trainees prior
    to certification.

d)  Training flows including any prerequisite training certification.

e)  Statement of certification forms.

f)  Requirements for maintenance of training currency and proficiency as
    specified by the MOD Space Flight Personnel .

The Contractor shall document flight and flight controller training
objectives. The document shall contain Performance Objectives required
for Certification. The Objectives shall be categorized by discipline and
according to Integrated and Standalone Training.

NASA directed positions are Data Type 2; contractor provided positions
are Data Type 3.

**DRD CONTINUATION SHEET**

**TITLE**: Flight Controller Certification Guides **DRD NO.**: 1.6.1.2-a

**DATA TYPE**: 2/3 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 554 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.2-b

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Controller Lessons and Scripts.

7\. **DESCRIPTION/USE**: Lessons and integrated simulation scripts
required for certification of flight controllers and for preparation of
flight control team, and lessons for all contractor-provided certifiable
positions

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Upon request.

10\. **SUBMISSION FREQUENCY**: Upon request.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.2; DRD 1.6.1.2-a

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Lessons defined in blue books or certification guides
and integrated simulation scripts that are required to certify flight
controllers and prepare flight control teams for each mission, and
certify all contractor-provided certifiable positions.

13.2 **APPLICABLE DOCUMENTS**:

JSC 36049 Training Development and Support Plan

13.3 **CONTENTS**: Lessons shall be developed based on Flight Controller
Certification Guides (DRD 1.6.1.2-a) requirements. Produce lessons in
accordance with Training Development and Support Plan Standards. Lessons
must fulfill performance objectives as identified in specified
certification guides.

Integrated simulation scripts shall be based on NASA flight-specific or
generic integrated simulation requirements and flight controller
objective requirements.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 555 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.3-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Crew Training Catalogs \[Shuttle Crew Training Catalog
(USA002960), ISS Master Course Catalog
(<https://mod2.jsc.nasa.gov/dt/focas/catalog/lesson/index.cfm>).

7\. **DESCRIPTION/USE**: Curriculum and training requirements for Space
Shuttle and International Space Station (ISS) Flight Crews.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP).

10\. **SUBMISSION FREQUENCY**: Annually for the Shuttle Crew Training
Catalog; semi-annually for the ISS Master Course Catalog.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.3.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Space Shuttle Crew Training Catalog guide shall
cover crew training curricula. The contractor will work with Flight
Crews to identify and implement changes to curriculum or lessons based
on Flight Crew in-flight task requirements. The ISS Master Course
Catalog curricula and delivery media is managed by NASA.

13.2 **APPLICABLE DOCUMENTS**:

JSC 36049 Training Development and Support Plan (ISS only)

13.3 **CONTENTS**: The contractor shall deliver the Space Shuttle Crew
Training Catalog covering training for systems, operations, and
integrated simulations. It shall be baselined to include; a lesson
sequence flow chart and a description of each individual lesson
(including duration, media and training objectives). Flow introductions,
requirement tables showing hours and crew positions to be trained and a
summary of crew and facility hours will also be provided. Content will
be based on agreement with customer. The ISS Master Course Catalog
exists in an electronic format, and is managed by NASA. The contractor
is only responsible for data input, tracking, and the associated
configuration control of the ISS Master Course Catalog.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats for the Space Shuttle Crew Training Catalog per
DRD 1.1.4.1-e, Data Management Plan, or per Contracting Officer
approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 556 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.3-b

3\. **DATA TYPE**: 3/4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Crew Training Lessons and Scripts

7\. **DESCRIPTION/USE**: Lessons required to train Space Shuttle Program
(SSP) and International Space Station (ISS) Flight Crews.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Upon request.

10\. **SUBMISSION FREQUENCY**: As requested.

11\. **REMARKS**: Curriculum or training flows are designed to contain
performance objectives required for flight crew flight readiness or
flight controller certification. For both Crews and Flight Controllers,
the training curriculum and lessons will be in no case negatively impact
safety, mission success, or major program schedule milestones.

12\. **INTERRELATIONSHIP**: SOW 1.6.1.3.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document covers lessons and other documents that
are required to train and prepare astronauts and astronaut flight crews
for each mission. Development of lessons will be based on the Training
Development and Support Plan and Crew Training Catalog requirements.

13.2 **APPLICABLE DOCUMENTS**:

USA 002960 Shuttle Crew Training Catalog

JSC 36301 Station Crew Training Catalog

JSC 36049 Training Development and Support Plan

13.3 **CONTENTS**: The contractor shall produce lessons in accordance
with Training Development and Support Plan Standards. Lessons must
fulfill performance objectives defined in the crew training catalog or
certification guide. (Data Type 4)

The contractor shall maintain the Shuttle Crew Operations Manual.
INITIAL SUBMISSION: contract ATP plus six months; submission frequency:
once per Flight Software Operational Increment. (Data Type 3)

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 557 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.3-c

3\. **DATA TYPE**: 3/4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight or Increment Specific Crew Training Plan.

7\. **DESCRIPTION/USE**: To define a plan to train Flight Crews for each
flight.

8\. **DISTRIBUTION**: Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: N/A

10\. **SUBMISSION FREQUENCY**: Once per flight no later than "DT
SCHEDULED START" plus 30 days for Shuttle Training Plans only. Increment
Crew Training plans are submitted on request by customer.

11\. **REMARKS**: Curriculum or training flows are designed to contain
performance objectives required for flight crew flight readiness or
flight controller certification. For both Crews and Flight Controllers,
the training curriculum and lessons will be in no case negatively impact
safety, mission success, or major program schedule milestones.

The Flight-Specific Shuttle training will be accomplished according to
the agreed upon Flight-Specific Training Template and will be adjusted
to fit any slip(s) to that flight's launch date in order that all
training objectives are accomplished before launch. This training will
in no case negatively impact safety, mission success, or major program
schedule milestones.

12\. **INTERRELATIONSHIP**: SOW 1.6.1.3.

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Contains all flight or increment specific crew training
requirements that will prepare Space Shuttle Program (SSP -- Type 3) and
International Space Station (ISS -- Type 4) Flight Crews to accomplish
required in-flight tasks.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Shuttle document shall provide a
beginning-to-launch training plan that includes all lesson requirements
required for flight readiness and shall be broken into weekly allotments
of time. This document shall identify the flight-specific crew training
plan which will be established according to the Flight Specific Training
Template and will be adjusted to accommodate any slip(s) to that
flight's launch date in order that all lessons are accomplished prior to
launch. The plan will be developed based on the Crew Training Catalog
and NASA flight-specific requirements. The plan will include projected
weekly metrics of training hours for each crew member including but not
limited to: total training hours, time in each discipline, and projected
weekly hours until launch date. The Increment Specific document will
contain at a minimum a summary of planned training events (currently the
information is delivered via the ITI homepage. In no case will the
Flight or Increment Specific Training Plans negatively impact safety,
mission success, or major program schedule milestones.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 558 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.1.3-d

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Astronaut Candidate Training Plan

7\. **DESCRIPTION/USE**: Defines plan to train Astronaut candidates.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days before first astronaut class start
after ATP.

10\. **SUBMISSION FREQUENCY**: 30 days before each astronaut class
start.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.1.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: Contains all technical and other identified training
requirements that will prepare SSP and ISS Astronauts for assignment to
flight crews.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The document shall provide a start-to-finish training
plan that includes all lesson requirements, broken into weekly
requirements. This document shall identify the Astronaut Candidate
Training plan. The plan will be developed based on the Crew Training
Catalog and NASA flight or increment-specific requirements. The plan
will include weekly schedule for the Astronaut Candidate class
including: total training hours each week and time in each facility (or
facility group) for each week.

13.4 **FORMAT**: Contractor format acceptable with Astronaut Office
concurrence.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 559 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.1.1

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Rules Publication

7\. **DESCRIPTION/USE**: Flight rules publication and change processing
to support flight preparation and flight execution. Documentation for
Flight Rules Control Board, Flight Technique Technical Forums, Joint
Operations Panels, Mission Management Team, and other related technical
flight rules forums.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Products and deliverables will be in
consonance with the existing schedules.

10\. **SUBMISSION FREQUENCY**:

a)  All-Flight Rules and Flight Specific Rules - Submit All-Flight Rules
    per periodic update schedule. Submit Flight Specific Flight Rules
    per flight specific schedules.

b)  Documentation for Flight Rules - Submit per Flight Rules Control
    Board schedule.

c)  Documentation for Flight Techniques - Submit per Flight Techniques
    Panel schedules.

d)  Documentation for JOP and other required forums - Submit per JOP
    schedules.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.9.1

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**:

13.2 **APPLICABLE DOCUMENTS**: Flight Requirements Document

13.3 **CONTENTS**: All Flight and Flight Specific Flight Rules
publication and change processing, documentation for Flight Rules
Control Board, Flight Technique Technical Forums, Joint Operations
Panels, Mission Management Team, and other related technical flight
rules forums.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: All-Flight Rules and Flight Specific Rules:
Changes should be incorporated as required by page change or complete
revision and/or electronically via the baseline MOD operations
electronic documentation system for distribution within and external to
the MCC.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 560 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.1.2

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Operations Documentation Product Handbook and Product
Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each operations documentation product, provide documented procedures
required for each operations documentation product, and provide
consistent product standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to keep documentation current with procedures, products, and
delivery requirements.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Operations Documentation Product Handbook provides
the procedures, development process/product flows, dependencies, and
levels of quality assurance used in the development of operations
products. The associated Operations Documentation Product Glossary
provides detailed product definitions and delivery requirements for each
operations product.

13.2 **APPLICABLE DOCUMENTS**: Flight Requirements Document

13.3 **CONTENTS**: The Operations Documentation Product Handbook and
Product Glossary shall include the functional areas of operations
documentation (typical list described): The content of the OD PH &
Glossary have been developed in the following appendixes:

a)  Appendix A -- Acronyms and Abbreviations

b)  Appendix B -- Systems (SPP/ISS)

c)  Appendix C -- EVA, Robotics & Crew Systems Operations

d)  Appendix D -- Flight Design Operations Documentation

e)  Appendix E -- Flight Operations Technical Library Services Support

f)  Appendix F -- International Operations Documentation (TBD)

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page to keep documentation current with procedures, products and
customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 561 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.1.3-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Data File (FDF)/Operations Data File (ODF) Product
Handbook and Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each FDF/ODF, provide documented procedures required for delivery of
each product, and provide consistent product standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: ATP plus 30 days.

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to maintain documentation consistency with procedures, products,
and delivery requirements.

11\. **REMARKS**: Some terminology used in the DRD for ODF and ODF
associated data is being developed and is based on the FDF counterpart
to convey the nature of the data required.

12\. **INTERRELATIONSHIP**: SOW 1.6.2.1.3 and DRD 1.6.2.1.3-c

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The FDF/ODF product handbook provides references to
detailed product definitions and delivery requirements and the
procedures, development process/product flows, dependencies, and quality
assurance requirements used in the development of FDF/ODF products.

13.2 **APPLICABLE DOCUMENTS**: Flight Requirements Document

13.3 **CONTENTS**: The FDF/ODF Product Handbook and shall include, but
not be limited to, the functional areas of FDF/ODF documentation as
described below:

a)  FDF/ODF documentation - Procedures and related data for the
    activities specified in the generic FDF/ODF Definition documents and
    the flight-specific FDF/ODF Structure Sheets. The FDF contains
    primarily crew procedures while the ODF includes both crew and
    ground executable procedures where the latter effects onboard
    systems action.

b)  FDF/ODF Flight Set - Flight and flight-like sets will consist of
    flight quality copies of the above procedures in book or electronic
    file format as appropriate. Additionally, the flight set will
    contain quantities and related FDF/ODF aids, e.g., cue cards,
    overlays, flipbooks, maps, floppy disks, tethers, post-it-notes,
    cuff checklists, etc., as specified in the flight/increment specific
    manifest.

c)  Associated documentation - Source data, rationale and as-flown
    configuration information relating to the FDF/ODF, e.g., vehicle and
    payload operations data, Flight Procedures Handbooks, PV/DSI
    records, configuration records, etc.

d)  Specification standards and process documentation: Flight materials
    and process configuration management plans, CPCB/SODF CB support
    plans, and FDF/ODF configuration status for simulations and flight
    production process plans.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes to paper documents will be incorporated as
required by complete revisions or page change notices to keep
documentation consistent with procedures, products, and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 562 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.1.3-c

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Portable Onboard Computer (POC) Software Loads Product
Handbook and Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each POC product, provide documented procedures required for each POC
product, and provide consistent product standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to keep documentation current with procedures, products, and
delivery requirements.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.1.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The POC Handbook provides the procedures, development
process/product flows, dependencies, and levels of quality assurance
used in the development of POC products. The associated POC Product
Glossary provides detailed product definitions and delivery requirements
for each POC product.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The POC Product Handbook and Glossary shall include
the functional areas of new POC applications software, existing POC
application maintenance and associated training.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page to keep documentation current with procedures, products and
customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 563 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.2-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Design and Dynamics Training and Certification
Management Plan

7\. **DESCRIPTION/USE**: To provide insight into the flight design
training and certification process used for the flight design team.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 10 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Updates as required to provide
consistency with DRD 1.6.2.2.2-c, Flight Design Handbook and Product
Glossary

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.2; DRD 1.6.2.2.2-c

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document shall specify the curriculum and
certification process at the flight design functional and discipline
level as described in SOW 1.6.2.2.2 (ascent, orbit, descent, navigation,
and flight integration).

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: To be defined by contractor based upon the scope of
this document.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue to provide consistency with DRD
1.6.2.2.2-c.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 564 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.2-c

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Design Handbook and Product Glossary

7\. **DESCRIPTION/USE**: To define the content of each flight design
product, provide documented procedures required for each flight design
product, and provide consistent product standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 10 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Updates as contractor requires to keep
documentation current with procedures, products and customer lists

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Flight Design Handbook and Product Glossary provide
the procedures, detailed product definitions including product
development process flows, input data, procedural process, output data,
levels of quality assurance, and complete product customer listings for
each flight design product.

13.2 **APPLICABLE DOCUMENTS**: N/A

13.3 **CONTENTS**: The Flight Design Handbook and Product Glossary shall
include:

a)  Procedures for all flight design processes.

b)  Flight design product glossary.

c)  Flight design product definition including requirements,
    input/output data, quality assurance levels and quality assurance
    process.

d)  Process/product flows and dependencies.

Products shall include the functional areas of: ascent, orbit (including
rendezvous and proximity operations), descent, navigation (ground and
onboard), flight integration, and post-flight reconstruction.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Update by change page as required to keep
documentation current with procedures, products and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 565 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.3-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Standards for Flight Design and Dynamics Software

7\. **DESCRIPTION/USE**: To define the maintenance and development
standards for all flight design software maintained by the contractor.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 10 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: As updates required to standards

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document provides standards for all flight design
software maintained by the contractor. This includes analysis,
production, real time support and other application and database
software used in flight design, flight preparation, flight execution,
and post-flight reconstruction. Standards shall be provided for new
software development and modifications to existing software.

13.2 **APPLICABLE DOCUMENTS**:

IRD-SE-1527T Flight Design and Dynamics Software Management Plan

JSC-27029 Software Management Plan for Mission Control Center
Applications

13.3 **CONTENTS**: Standards shall include required documentation,
software life cycle phases, user interfaces, operations data policies,
and other aspects of software development, maintenance and programming
standards.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 566 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.3-b

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Design and Dynamics Software Management Plan

7\. **DESCRIPTION/USE**: To define the contractor\'s policies,
procedures and management tools used to provide software sustaining
engineering activities and interfaces for flight design.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 10 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: As required to maintain currency with
software management plans

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document shall define management structures and
responsibilities for all flight design software sustaining engineering.

13.2 **APPLICABLE DOCUMENTS**:

JSC-27029 Software Management Plan for MCC Applications

JSC-08211 LSEAT Integration Support Plan

JSC-23474 MCC Critical Processor Certification Policy

13.3 **CONTENTS**: The plan shall contain management structures, and
roles and responsibilities; procedures for work planning and work
tracking; software change processes; software life cycle management;
software configuration management; software quality assurance; critical
software certification process. Non-flight critical software reporting
is limited to applications used to generate flight design products as
defined in the Product Glossary.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 567 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.3-c

3\. **DATA TYPE**: 4 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Design Software System Documentation

7\. **DESCRIPTION/USE**: The complete set of application software life
cycle documentation, including source and executable code, for all FDD
applications, under development or in production. This includes test
documents, test data, and test case libraries.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Upon Request

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**: This request will be made via STF from NASA for any
documentation not available electronically on either the FADS or SELS.

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.3, DRD 1.6.2.2.3-b

13\. **DATA PREPARATION INFORMATION:**

13.1 **SCOPE:** This document provides as requested either all
documentation for a specific application or a listing of the
documentation available for all flight design user applications
maintained under formal configuration management per the Flight Design
Software Management Plan (DRD 1.6.2.2.3-b) or discipline c.m. developed
under contract. This documentation is not required for previously
exempted applications unless specifically requested by the Government.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: As required, a listing of available documentation for
all applications or specific software life cycle documentation, as well
as source code and executable code.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 568 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.3-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Design and Dynamics Data Management System Data
Administration/Database Administration Plan

**7. DESCRIPTION/USE**: To provide a plan for how FDD manages data and
databases owned by FDD, residing on the IPS and MCC computer platform.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 10 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Upon request

11\. **REMARKS**: This plan is also used by NASA/DM to manage GAF owned
data.

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This documents a plan for data administration for all
flight design computer hardware platforms used by FDD.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Flight Design Data Administration Plan for
Platform Hardware shall include the following to support the FDD and DM,
ISS and Shuttle design, reconfiguration, and operating processes:

a)  Plans for using data archival and mass storage.

b)  Data loss recovery plans.

c)  Metrics that provide measures of user data management and mass
    storage resources.

d)  Management organization and responsibility.

e)  Operations data responsibilities.

f)  Data ownership and control policy.

g)  Data change process.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **DRL NO.**: 569 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.2.3-e

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Design and Dynamics Operations Center Software
Engineering Strategic Plan

7\. **DESCRIPTION/USE**: To provide an overall plan and strategy for the
upgrade of systems, tools, applications; to position the Flight Design
and Dynamics (FDD) software systems for responsiveness to NASA programs;
to provide the visions and paths for the evolution of the FDD software
systems; to be used by NASA and the contractor to make decisions
impacting FDD software long term goals and objectives.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Initial draft 10 days after Authority to
Proceed (ATP); final version approved at ATP plus 40 days

10\. **SUBMISSION FREQUENCY**: Updates annually (no later than April
1st) or as required by NASA

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The plan shall include goals and strategies for FDD
software addressing both short term (3-5 years) and long term (5-10
years). This plan shall define the long-range plans for upgrading FDD
software to remain responsive to current and future NASA programs that
they must support.

13.2 **APPLICABLE DOCUMENTS**:

NAS9-18000, IRD-SE-1526-T Flight Design and Dynamics Software Strategic
Plan

STSOC PN -001264 Flight Design and Dynamics Software Strategic Plan

13.3 **CONTENTS**: Domains that shall be addressed by the strategic plan
include management and engineering processes, data management, technical
upgrades, quality, information management and communication, and growth,
evolution, and extensibility.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 570 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.3-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Planning Requirements Documents/Databases

7\. **DESCRIPTION/USE**: To be used for flight plan development and
flight plan execution.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: Products and deliverable will be in
consonance with the existing publication schedules.

10\. **SUBMISSION FREQUENCY**:

a)  Planning Databases, Submit to support flight-specific flight plan
    publication schedules and update as required for planned/actual
    launch dates and flight execution.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: See item 13.3.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Databases shall contain:

a)  Generic, flight- specific and increment planning (ISS) databases.

Timeline data should be loaded into the planning system and timeline
pages edited and prepared for publication.

Planning data bases should be developed per flight planning preparation
standards and FDF preparation standards.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**:

a)  Planning Databases - Changes shall be incorporated by change page or
    complete revision and capable of electronic distribution via the
    baseline MOD operations electronic distribution system, e.g., EDP,
    within the MCC and external to the MCC.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 571 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.3-b

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Flight Planning Product Handbook and Product Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each flight planning product, provide documented procedures required
for each flight planning product, and provide consistent product
standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to keep documentation current with procedures, products, and
delivery requirements.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Flight Planning Product Handbook provides the
procedures, development process/product flows, dependencies, and levels
of quality assurance used in the development of flight planning
products. The associated Flight Planning Product Glossary provides
detailed product definitions and delivery requirements for each flight
planning product.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Flight Planning Product Handbook and Product
Glossary shall include the functional areas of:

a)  [Technical Assessments/Testing/Requirements]{.underline} to support
    required flight-specific technical forums such as CIR, FPSR, IPT,
    POWG, FOR, COWG, CoFR, and FRR.

```{=html}
<!-- -->
```
1.  Attitude and Pointing Assessments and Reports.

2.  Documentation for Technical Forums.

3.  Requirements for Pointing Software Applications.

```{=html}
<!-- -->
```
b)  [Software Applications]{.underline} to support the flight planning
    process. Documentation of the requirements for pointing and orbiter
    text information system software applications. Development of
    additional application software.

c)  [Flight-Specific Attitude and Pointing Products]{.underline} to
    support the publication of the Basic and Final versions of the
    Flight Data File and flight execution. These include the Attitude
    Timeline (ATL), ATL databases, S-band and Ku-band communication
    data, blockage diagrams, and other flight-specific attitudes.

d)  Planning Product: Pre-increment and tactical plans and process
    definition.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Update by change page as required to keep
documentation current with procedures, products and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 572 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.3-d

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Systems Product Handbook and Product Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each systems product, provide documented procedures required for each
systems product, and provide consistent product standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to keep documentation current with procedures, products, and
customer lists.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.3

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Systems Product Handbook provides the procedures,
development process/product flows, dependencies, and levels of quality
assurance used in developing systems products. The associated Systems
Product Glossary provides detailed product definitions including product
input data, output data, delivery requirements, and complete product
customer listings for each systems product.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: Products shall include the functional areas of
electrical, environmental, propulsion, and thermal systems analysis and
consumables; sequential vehicle mass properties analysis and management;
robotics integration and analysis; photo/TV; crew systems; in-flight
maintenance; and station resource management. Products are to be
provided for design, analysis, flight planning and integration, flight
product development, vehicle consumables loading, flight software
reconfiguration, flight control systems technical assessments, flight
execution, and post-flight reconstruction.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Update by change page as required to keep
documentation current with procedures, products, and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 573 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.2.4

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Payload/Cargo Product/Services Handbook and Glossary

7\. **DESCRIPTION/USE**: To define the content and delivery requirements
of each payload product or service, provide documented procedures
required for each payload/cargo product or service, and provide
consistent product or service standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to keep documentation current with procedures, products, and
delivery requirements.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.2.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Payload/Cargo Product/Service Handbook provides the
procedures, development process/product flows, dependencies, and levels
of quality assurance used in developing payload/cargo products and
services. The glossary provides detailed product definitions and
delivery requirements for each payload product or service.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Payload/Cargo Product/Service Handbook and
Glossary shall include the functional areas of:

a)  Payload/Cargo Operations Documentation Cargo Systems Manuals,
    Payload Command Plan, Procedures Handbook, Operations Support
    Timelines, Joint Operations Interface Procedures, Operations Support
    Timelines, Preflight Notes of Interest, and the applicable
    documentation related to the ISS Assembly Operations.

b)  Payload/Cargo Technical Reports/Inputs for typical forums such as
    CIR, FPSR, IPT, POWG, FOR, COWG, CoFR, and FRR.

    1.  Payload/Cargo Assessments.

    2.  Payload/Cargo Test Inputs and Reports.

    3.  Review Packages for Payload/Cargo Technical Forums.

    4.  PIP/MIP/Annex inputs.

    5.  Payload/Cargo Operations Documentation Input.

c)  Technical Forums Services required for Payload/Cargo Operations

    1.  Forum Scheduling and logistics

    2.  Meeting Documentation

    3.  Data Package assembly and distribution

d)  Operations Safety Documentation to provide payload safety compliance
    evaluation, ISS safety compliance evaluation, flight documentation
    safety evaluation (ISVR), 482 Flight Rule change request evaluation,
    and flight techniques/PRCB support, safety policy/process
    evaluation, S/MM Joint Safety Development/Compliance evaluation and
    safety activities status report.

**DRD CONTINUATION SHEET**

**TITLE**: Payload/Cargo Product/Services Handbook **DRD NO.**: 1.6.2.4

and Glossary

**DATA TYPE**: 2 **PAGE**: 2/2

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

13.3 **CONTENTS (continued)**:

e)  Payload Facilities Definition and Implementation Data to provide for
    integration of payload customer requirements into Mission Control
    Center (MCC) facilities; and additional software computations,
    displays, and telemetry/command requirements that are required for
    flight preparation and flight execution using the MCC.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes should be incorporated as required by page
change to keep documentation current with procedures, products, and
customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 574 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.4-a

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Project Management Plan

7\. **DESCRIPTION/USE**: To describe significant new capability
development, capability upgrades, or other modifications to existing
contractor managed systems.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: As required

10\. **SUBMISSION FREQUENCY**: As required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Project Management Plan shall describe the high
level objectives, cost estimates, schedules, and management
plans/processes for significant enhancements or modifications to
contractor managed systems.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The Project Management Plan shall consist of the
following:

a)  Project objectives description.

b)  Project management team organization.

c)  Baseline control process description.

d)  Risk management plan.

e)  Project milestone definition.

f)  Project cost estimates.

g)  Project schedule estimates.

h)  Requirements verification and validation plan.

i)  Operations transition plan.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **MAINTENANCE**: Changes shall be incorporated as required, by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 575 **ISSUE**: BASIC 2. **DRD NO.**: 1.6.4.2-a

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Integrated Training Facility Simulation Systems
Operations Handbook

7\. **DESCRIPTION/USE**: Defines the standard operating procedures,
processes, and guidelines for the operating positions, maintenance
coordination, and users of the Integrated Training Facility (ITF)
including both the Shuttle Mission Simulator (SMS) and the Space Station
Training Facility (SSTF) managed by the contractor.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: Before the end of FY98.

10\. **SUBMISSION FREQUENCY**: Annually

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.6.4, 1.6.4.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: This document defines the standard operating procedures,
processes, and guidelines at the Integrated Training Facility (ITF),
including the Shuttle Mission Simulators (SMS), Guidance & Navigation
Simulator (GNS) and the Space Station Training Facility (SSTF). An
operation's appendix will be provided for the trainers listed below when
an operations interface is established with existing ITF resources. The
trainers include Single System Trainers (SST), Flight Controller Trainer
(FCT), Playback Trainer (PBT), Payload Trainer (PLT), Crew Software
Trainer (CST) Part Task Trainer (PTT), and other trainers developed or
upgraded to provide Shuttle or ISS systems training.

13.2 **APPLICABLE DOCUMENTS**: None

13.3 **CONTENTS**: The following types of procedures shall be included:
Administration/management, general, anomaly administration,
software/hardware, power, safety/emergency, other operational support.

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval. General procedures shall be identified
that apply to all trainers. Each trainer shall have a section, which
identifies unique procedures. Each procedure shall define the purpose,
participants, and procedure steps.

13.5 **MAINTENANCE**: Changes shall be incorporated as required by
change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRL NO.**: 289. **ISSUE**: BASIC 2. **DRD NO.**: 1.9.1

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Human Capital Retention Plan

7\. **DESCRIPTION/USE**: Establish a comprehensive strategic and
tactical retention plan phased by fiscal year that outlines the
initiatives implemented to retain critical skills within the prime and
critical subcontractors until the end of the Space Shuttle Program.

8\. **DISTRIBUTION**: Per Contracting Officer's letter

9\. **INITIAL SUBMISSION**: May 2007

10\. **SUBMISSION FREQUENCY**: The Human Capital Retention Plan shall be
reviewed, updated, and submitted to NASA as major events dictate, but no
less frequent than quarterly starting in January 2008. It is understood
by both parties that most quarterly updates will primarily involve
transmittal of the latest metrics data.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 1.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **SCOPE**: The Human Capital Retention Plan shall include all
contributory elements to ensure human capital resources are maintained
to safely and successfully execute the manifest through the end of the
Space Shuttle Program.

13.2 **APPLICABLE DOCUMENTS**:

13.3 **CONTENTS**: The plan shall include the following content:

a)  Definition and identification of each critical skill and the
    standard to support the designation of "critical" in each Program
    Element functional area that must be maintained, along with
    identification of acceptable date for loss of each particular
    critical skill.

b)  Identify and distinguish essential workforce from critical skills,
    and identify the essential workforce that must be maintained in each
    Program Element functional area, along with identification of
    acceptable date for loss of "segregable" portions of essential
    workforce in a functional area.

c)  Reference to retention policies adopted and other policies and
    actions being pursued specifically for the retention of critical
    skills and essential workforce for this contract, as laid out in the
    plan. In support of policies implemented by the contractor, provide
    linkage to benchmarking of human capital retention issues across the
    aerospace industry, focusing on retention policies successfully
    adopted in industry to combat loss of critical skills in an "end of
    program life" posture.

d)  Demonstrate linkage between the critical skills and essential
    workforce identified under this plan and the retention policies the
    contractor has or proposes to adopt to combat loss of critical
    skills and essential personnel under this contract. Include the
    rationale for how the need for any workforce retention features was
    determined.

e)  Detail the metrics for judging performance against the plan, and the
    strategy for adjusting the plan and any linked retention policies.
    Minimum metrics at the element and total levels should include:
    attrition of personnel with and without retention features;
    accounting of attrition versus reason for leaving, if known; and
    projected phased allocation of costs for the various policies.

13.4 **FORMAT**: Contractor format is acceptable.

5.  **MAINTENANCE**: The product shall be actively managed and updated
    annually by the contractor and submitted electronically to NASA.

ATTACHMENT J-6

STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES

Refer to Attachment J-7 for the Statement of Equivalent Rates for
Federal Hires.

ATTACHMENT J-7

WAGE DETERMINATIONS

The following Department of Labor Wage Determinations are enclosed and
hereby made a part of this Attachment J-7:

  ----------------- ----------------- ----------------- -----------------
  Wage              Revision          Date of Revision  No. of Pages
  Determination                                         

  05-2516           1                 05-23-2005        11

  05-2118           1                 05-23-2005        12

  05-2044           2                 05-23-2005        12

  05-2008           1                 05-23-2005        12
  ----------------- ----------------- ----------------- -----------------

[Click to open Wage
Determinations](../22%20SPOC%20Compiled%20Wage%20Determination%20SF%2098E%20SPOC-10-06.pdf)

ATTACHMENT J-8

FEE PLAN

# Introduction

This contract is a cost-plus-award-fee contract (with an indefinite
delivery/indefinite quantity feature) which supports the primary goals
of the NASA Space Flight Program: fly safely, meet the manifest, and
maintain critical assets and capabilities. This fee plan includes a
combination of Award Fee, Performance Fee, and End of Program (EOP) Fee
designed to emphasize excellence in managerial, technical, schedule,
subcontract management, and cost performance while providing the
contractor with the appropriate motivation to achieve Program goals.

# Award Fee Provisions

The award fee serves as a tool to measure the contractor's performance
on the health of the program and motivate continued improvement. The
contractor can earn award fee from a minimum of zero dollars to a
maximum stated in Clause B.2 of this contract. Changes to these award
fee provisions will be via bilateral modification, except for internal
NASA processes and evaluation factors which are established unilaterally
by NASA.

Under Award Fee Provisions, NASA may evaluate the contractor on any area
of performance within the spectrum of the contract. A significant
element of any award fee evaluation shall be the contractor's
demonstrated performance in meeting or exceeding the statement of work
(SOW) performance standards. Thus, while the award fee process is
subjective, it may include consideration of predetermined objective
performance criteria and these standards may be used in award fee
evaluation.

### **Organizational Responsibilities** {#organizational-responsibilities .z:Heading-3}

### **Performance Monitors** {#performance-monitors .z:Heading-3}

NASA performance monitors will evaluate and assess the contractor's
performance in assigned areas, and discuss the evaluation results with
contractor counterparts as appropriate. The performance monitors will
use, at their discretion, evaluations and assessments from NASA
officials in preparing their report on assigned areas. Additionally,
performance monitors will periodically prepare reports for the
Performance Evaluation Integration Team (PEIT) and Performance
Evaluation Board (PEB).

### **Performance Evaluation Integration Team (PEIT)**  {#performance-evaluation-integration-team-peit .z:Heading-3}

The PEIT is comprised of the SPOC Technical Management Representatives
(TMRs) who are responsible for assessing the contractor's performance
related to the evaluation factors listed in Section 2.3.

### **Performance Evaluation Board (PEB)** {#performance-evaluation-board-peb .z:Heading-3}

The PEB is comprised of NASA officials who are responsible for assessing
the contractor's performance, and establishing specific evaluation
criteria related to the evaluation factors listed in Section 2.3.

### **PEB Chair** {#peb-chair .z:Heading-3}

The Manager, Space Shuttle Program (or Deputy), will serve as the PEB
Chair. The PEB Chair may reassign performance monitors PEIT members, or
PEB members at any time without advance notice to the contractor.

### **Fee Determination Official (FDO)** {#fee-determination-official-fdo .z:Heading-3}

The Associate Administrator for Space Operations (or Deputy) will serve
as the FDO. The FDO, after considering available pertinent information
and recommendations, shall make a unilateral determination in accordance
with the provisions of this plan.

### **Periodic (Six Month) Evaluation Procedures** {#periodic-six-month-evaluation-procedures .z:Heading-3}

All periodic performance evaluations will be final. A determination of
the performance score and the related dollars earned for each evaluation
period will be made by the FDO within 45 days after the end of each
period. A contract modification recognizing the dollars earned will be
issued within 60 days after the end of the period. Procedures to be
followed in monitoring, assessing, and evaluating contractor performance
during each period, are described below.

### No later than 45 calendar days prior to the start of each evaluation period, the contractor may submit to the Contracting Officer recommended areas of emphasis for the ensuing evaluation period that are within the general factors listed in Section 2.3 of this plan. Consideration will be given to the contractor's recommendations; however, it is the Government's responsibility to establish the specific areas of emphasis for each evaluation period. {#no-later-than-45-calendar-days-prior-to-the-start-of-each-evaluation-period-the-contractor-may-submit-to-the-contracting-officer-recommended-areas-of-emphasis-for-the-ensuing-evaluation-period-that-are-within-the-general-factors-listed-in-section-2.3-of-this-plan.-consideration-will-be-given-to-the-contractors-recommendations-however-it-is-the-governments-responsibility-to-establish-the-specific-areas-of-emphasis-for-each-evaluation-period. .z:Heading-3}

### No later than 30 days prior to the start of each new six-month evaluation period, the contractor will be notified by the Contracting Officer of the selected areas of emphasis for that period as well as any weightings NASA wishes to specify. Emphasis will be directed at particular areas under the contract which appear to the Government to be deserving of special attention and will be used in judging the contractor's performance. These areas of emphasis may or may not cover the entire spectrum of performance that will be evaluated in determining award fee scores and dollars earned. Other pertinent factors included under the contract and general factors bearing upon overall performance will be considered. {#no-later-than-30-days-prior-to-the-start-of-each-new-six-month-evaluation-period-the-contractor-will-be-notified-by-the-contracting-officer-of-the-selected-areas-of-emphasis-for-that-period-as-well-as-any-weightings-nasa-wishes-to-specify.-emphasis-will-be-directed-at-particular-areas-under-the-contract-which-appear-to-the-government-to-be-deserving-of-special-attention-and-will-be-used-in-judging-the-contractors-performance.-these-areas-of-emphasis-may-or-may-not-cover-the-entire-spectrum-of-performance-that-will-be-evaluated-in-determining-award-fee-scores-and-dollars-earned.-other-pertinent-factors-included-under-the-contract-and-general-factors-bearing-upon-overall-performance-will-be-considered. .z:Heading-3}

### The Contracting Officer's Technical Representative (COTR) shall meet with the contractor at the mid-point of each evaluation period and at other such times as is deemed appropriate to apprise the contractor of its performance assessment. These meetings shall address specific areas where contractor performance requires improvement. The contractor will be provided a written assessment. The contractor's mid-point performance will not be scored. At this time, the contractor will also be provided written feedback on its performance under End of Program Fee evaluation factors in accordance with Section 7.0 of this plan. {#the-contracting-officers-technical-representative-cotr-shall-meet-with-the-contractor-at-the-mid-point-of-each-evaluation-period-and-at-other-such-times-as-is-deemed-appropriate-to-apprise-the-contractor-of-its-performance-assessment.-these-meetings-shall-address-specific-areas-where-contractor-performance-requires-improvement.-the-contractor-will-be-provided-a-written-assessment.-the-contractors-mid-point-performance-will-not-be-scored.-at-this-time-the-contractor-will-also-be-provided-written-feedback-on-its-performance-under-end-of-program-fee-evaluation-factors-in-accordance-with-section-7.0-of-this-plan. .z:Heading-3}

### The contractor may furnish a self-evaluation report within 10 calendar days after the expiration of each evaluation period. This self-evaluation report shall not exceed 20 pages in length. The PEB will not submit its recommendation to the FDO until (1) the contractor's self-evaluation report has been received and considered, or (2) the contractor has provided written notification that a self-evaluation report will not be submitted, or (3) the 10-day period provided for submission of the report has expired. {#the-contractor-may-furnish-a-self-evaluation-report-within-10-calendar-days-after-the-expiration-of-each-evaluation-period.-this-self-evaluation-report-shall-not-exceed-20-pages-in-length.-the-peb-will-not-submit-its-recommendation-to-the-fdo-until-1-the-contractors-self-evaluation-report-has-been-received-and-considered-or-2-the-contractor-has-provided-written-notification-that-a-self-evaluation-report-will-not-be-submitted-or-3-the-10-day-period-provided-for-submission-of-the-report-has-expired. .z:Heading-3}

### After the end of each six-month evaluation period (as identified in the Attachment II, Table B -- Mission Execution Fee), the PEIT will prepare a written report documenting its evaluation. This report shall include recommendations for an adjective rating and numerical score to be assigned to the contractor's performance during the evaluation period. This PEIT report will be presented to the Performance Evaluation Board (PEB).  {#after-the-end-of-each-six-month-evaluation-period-as-identified-in-the-attachment-ii-table-b-mission-execution-fee-the-peit-will-prepare-a-written-report-documenting-its-evaluation.-this-report-shall-include-recommendations-for-an-adjective-rating-and-numerical-score-to-be-assigned-to-the-contractors-performance-during-the-evaluation-period.-this-peit-report-will-be-presented-to-the-performance-evaluation-board-peb. .z:Heading-3}

### Upon receipt of the PEIT report, the PEB shall meet to consider all the performance information it has obtained. At the meeting, the PEB will summarize its preliminary findings and recommendation in the Performance Evaluation Board Report (PEBR). The PEBR shall include recommendations for an adjective rating and numerical score to be assigned to the contractor's performance during the evaluation period. This report as well as a PEB presentation will be provided to the FDO. The contractor shall have the opportunity to make a presentation to the PEB if they so desire. (See 2.2.7)  {#upon-receipt-of-the-peit-report-the-peb-shall-meet-to-consider-all-the-performance-information-it-has-obtained.-at-the-meeting-the-peb-will-summarize-its-preliminary-findings-and-recommendation-in-the-performance-evaluation-board-report-pebr.-the-pebr-shall-include-recommendations-for-an-adjective-rating-and-numerical-score-to-be-assigned-to-the-contractors-performance-during-the-evaluation-period.-this-report-as-well-as-a-peb-presentation-will-be-provided-to-the-fdo.-the-contractor-shall-have-the-opportunity-to-make-a-presentation-to-the-peb-if-they-so-desire.-see-2.2.7 .z:Heading-3}

### In addition to the information cited in Section 2.2.4, the contractor may choose to make a presentation to the PEB. If the contractor chooses to make a presentation for a particular period, notification must be made to the Contracting Officer no later than seven working days after the end of the applicable award fee period. The presentation, if provided, will be limited to one hour in length. {#in-addition-to-the-information-cited-in-section-2.2.4-the-contractor-may-choose-to-make-a-presentation-to-the-peb.-if-the-contractor-chooses-to-make-a-presentation-for-a-particular-period-notification-must-be-made-to-the-contracting-officer-no-later-than-seven-working-days-after-the-end-of-the-applicable-award-fee-period.-the-presentation-if-provided-will-be-limited-to-one-hour-in-length. .z:Heading-3}

### The PEB Chair is responsible for the preparation of the PEBR and will present the findings and recommendation to the FDO. The report will include an adjective rating, a recommended overall performance score, and recommended safety score with supporting documentation.  {#the-peb-chair-is-responsible-for-the-preparation-of-the-pebr-and-will-present-the-findings-and-recommendation-to-the-fdo.-the-report-will-include-an-adjective-rating-a-recommended-overall-performance-score-and-recommended-safety-score-with-supporting-documentation. .z:Heading-3}

### The FDO will consider the recommendations of the following sources in determining the rating and score: (1) PEB; (2) PEIT; (3) information provided by the contractor; and (4) any other pertinent information. The FDO's determination of the scores will be stated in a written Award Fee Determination (AFD). {#the-fdo-will-consider-the-recommendations-of-the-following-sources-in-determining-the-rating-and-score-1-peb-2-peit-3-information-provided-by-the-contractor-and-4-any-other-pertinent-information.-the-fdos-determination-of-the-scores-will-be-stated-in-a-written-award-fee-determination-afd. .z:Heading-3}

### The contractor will be notified by the Contracting Officer of the FDO rating and score, and will be provided a summary of the PEBR. The contractor may provide additional information for consideration by the FDO by notifying the Contracting Officer of its desire to do so. This is an opportunity for the contractor to provide any information which the contractor believes is relevant to its performance and which may affect the FDO's determination. Any additional information should be provided to the Contracting Officer within 5 calendar days of contractor receipt of the FDO rating, scores, and PEBR. This additional contractor information will be provided to the FDO by the Contracting Officer through the PEB Chair. {#the-contractor-will-be-notified-by-the-contracting-officer-of-the-fdo-rating-and-score-and-will-be-provided-a-summary-of-the-pebr.-the-contractor-may-provide-additional-information-for-consideration-by-the-fdo-by-notifying-the-contracting-officer-of-its-desire-to-do-so.-this-is-an-opportunity-for-the-contractor-to-provide-any-information-which-the-contractor-believes-is-relevant-to-its-performance-and-which-may-affect-the-fdos-determination.-any-additional-information-should-be-provided-to-the-contracting-officer-within-5-calendar-days-of-contractor-receipt-of-the-fdo-rating-scores-and-pebr.-this-additional-contractor-information-will-be-provided-to-the-fdo-by-the-contracting-officer-through-the-peb-chair. .z:Heading-3}

### The AFD will be provided to the contractor by the Contracting Officer, along with the performance evaluations prepared by the TMRs. The contractor may, after notification of the determination, request, through the Contracting Officer, a briefing by the PEB Chair. This briefing shall be conducted no later than 14 days following the written request by the contractor. Additionally, the contractor will be provided written feedback on its performance under End of Program Fee evaluation factors in accordance with Section 7.0 of this plan. {#the-afd-will-be-provided-to-the-contractor-by-the-contracting-officer-along-with-the-performance-evaluations-prepared-by-the-tmrs.-the-contractor-may-after-notification-of-the-determination-request-through-the-contracting-officer-a-briefing-by-the-peb-chair.-this-briefing-shall-be-conducted-no-later-than-14-days-following-the-written-request-by-the-contractor.-additionally-the-contractor-will-be-provided-written-feedback-on-its-performance-under-end-of-program-fee-evaluation-factors-in-accordance-with-section-7.0-of-this-plan. .z:Heading-3}

### The contractor shall provide the Government a Corrective Action Plan (CAP), or an explanation of why corrective action is not required, for each weakness identified in the PEB report. The CAP should include a description of the non- conformance, determination of the root cause of the non-conformance, action required to correct the weakness and prevent recurrences, and the schedule for completion of the action. One copy of the report shall be delivered to the Contracting Officer, and two copies of the report shall be delivered to the COTR within 30 calendar days after receipt of the PEB report. Additionally, a quarterly report shall be submitted to provide the status of the open CAPs. {#the-contractor-shall-provide-the-government-a-corrective-action-plan-cap-or-an-explanation-of-why-corrective-action-is-not-required-for-each-weakness-identified-in-the-peb-report.-the-cap-should-include-a-description-of-the-non--conformance-determination-of-the-root-cause-of-the-non-conformance-action-required-to-correct-the-weakness-and-prevent-recurrences-and-the-schedule-for-completion-of-the-action.-one-copy-of-the-report-shall-be-delivered-to-the-contracting-officer-and-two-copies-of-the-report-shall-be-delivered-to-the-cotr-within-30-calendar-days-after-receipt-of-the-peb-report.-additionally-a-quarterly-report-shall-be-submitted-to-provide-the-status-of-the-open-caps. .z:Heading-3}

### **Evaluation Factors** {#evaluation-factors .z:Heading-3}

NASA may evaluate the contractor on any area of performance within the
spectrum of the contract. A significant element of any award fee
evaluation shall be the contractor's demonstrated performance in meeting
or exceeding the SOW performance standards. The following are examples
of critical factors which will be included in any evaluation:

### **Management Effectiveness** {#management-effectiveness .z:Heading-3}

The contractor will be evaluated based upon management performance in
providing a balanced, coordinated and motivated approach to managerial
excellence. This includes an assessment of the contractor's performance
in the development, analysis and utilization of management data,
managing resources to sustain performance, and program controls to
effectively accomplish contract requirements. This will involve the
assessment of contractor performance in planning, controlling, and
managing Government facilities and property, as well as contract and
subcontract management. Also included is the contractor's track record
on the assessment and mitigation of risk.

### **Operational Safety** {#operational-safety .z:Heading-3}

Operational safety is of supreme importance to NASA. This includes
flight safety issues involving the flight crew, potential risks to
flight assets, and ground processing safety affecting personnel or
facilities. Consideration will be given to the maintenance of process
and product quality at all levels, and includes the implementation of
performance measures as an indication of quality. A specific score will
be provided for this factor (see paragraph 2.5).

### **Quality** {#quality .z:Heading-3}

The contractor will be evaluated on the maintenance of the program
processes with required product quality at all levels, and
implementation of performance measures related to quality.

### **Schedule and Manifest Effectiveness** {#schedule-and-manifest-effectiveness .z:Heading-3}

The contractor will be evaluated against program schedules and key
interim milestones, including non-recurring elements such as performance
enhancements. This evaluation will consider all aspects of planning,
processing and operation in support of the NASA manifest, including not
only the effectiveness and quality of meeting the manifest, but also the
development and demonstration of flexibility and robustness in this
capability. The contractor will also be evaluated on its support of long
range manifest needs across the life of the Space Shuttle Program
through a program of maintenance, repair refurbishment, and logistics
planning that assures Program capability.

### **Supportability** {#supportability .z:Heading-3}

The contractor will be evaluated on its approach and plans for the
health and viability of the Program to support the flight manifest. This
evaluation will assess the contractor's performance against the
overarching program goals and the ability of the contractor to balance
program health and assure product and process integrity.

### **Small Business Subcontracting Performance** {#small-business-subcontracting-performance .z:Heading-3}

The contractor will be evaluated on its efforts in achieving small
business subcontracting goals, as described in Article H.3, "Small
Business Subcontracting Goals (JSC 52.219-90) (Jan 2003)", and
Attachment J-14, "Small Business Subcontracting Plan" of the contract.
Efforts in performing small business outreach activities will be
considered, along with any honors that the contractor has been awarded.
The Award Fee weighting for small business performance will be 15
percent of the technical factors.

### **Cost Management** {#cost-management .z:Heading-3}

This evaluation will be related to actual cost performance versus the
estimated cost for the effort, including any requirement changes. The
Award Fee weighting for cost performance will be 25 percent of the
available Award Fee pool.

### **Evaluation Periods and Award Fee Calculation** {#evaluation-periods-and-award-fee-calculation .z:Heading-3}

### **Maximum Available Award Fee** {#maximum-available-award-fee .z:Heading-3}

The maximum available award fee is identified in Clause B.2.

### **Evaluation Periods and Award Fee Available** {#evaluation-periods-and-award-fee-available .z:Heading-3}

The available award fee dollars for each evaluation period are
delineated in Attachment II, Table B -- Mission Execution Fee. For
evaluation purposes the amounts available in Attachment II, Table B -
Mission Execution, will be reduced in the appropriate period for any
Performance Fee associated with missions flown but for which a
unilateral modification has not yet been issued as described in section
4.1.5.

### Dollars Earned {#dollars-earned .z:Heading-3}

Upon the FDO's determination of contractor's performance for each
period, the graded score, as a percentage, will be applied to the
dollars available in the period, as stated in Attachment II, Table B --
Mission Execution Fee, to determine the dollars earned.

### Dollars Not Earned {#dollars-not-earned .z:Heading-3}

All award fee dollars available for each evaluation period not earned
will not roll forward to subsequent award fee periods. A unilateral
contract modification will be issued to remove these unearned dollars
from maximum award fee available on the contract. Dollars not earned
will also be captured in Attachment II, Table B -- Mission Execution
Fee.

### **Evaluation Scale and Adjectival Rating** {#evaluation-scale-and-adjectival-rating .z:Heading-3}

Attachment I, Table A -- Award Fee and EOP Fee Scoring System, includes
adjective ratings as well as a numerical scoring system from 0 - 100.
For this plan, earned award fee dollars are calculated by applying the
total numerical score to available dollars. For example, a numerical
score of 85 yields 85 percent of available award fee dollars.
Notwithstanding the preceding, the contractor will not earn award fee
for any evaluation period when the performance score is
"poor/unsatisfactory" (less than 61). A Safety score will be provided
for each period in addition to the total numerical score. The purpose of
the Safety score is to emphasize the importance of safety concerns.
There is no separate fee pool associated with the Safety score.

### **Provisional Payment of Award Fee** {#provisional-payment-of-award-fee .z:Heading-3}

### Pending a determination of the amount of award fee earned for periodic evaluations, a portion of the available award fee for that period will be provisionally paid to the contractor on a monthly basis. The provisional payment shall never exceed 80%. The amount of provisional fee which may be paid monthly in any evaluation period shall be prorated equally to the number of months in that period. {#pending-a-determination-of-the-amount-of-award-fee-earned-for-periodic-evaluations-a-portion-of-the-available-award-fee-for-that-period-will-be-provisionally-paid-to-the-contractor-on-a-monthly-basis.-the-provisional-payment-shall-never-exceed-80.-the-amount-of-provisional-fee-which-may-be-paid-monthly-in-any-evaluation-period-shall-be-prorated-equally-to-the-number-of-months-in-that-period. .z:Heading-3}

### Should, at any time, the Contracting Officer determine that the contractor will not achieve a level of performance commensurate with the provisional rate, such rate may be unilaterally reduced or discontinued. {#should-at-any-time-the-contracting-officer-determine-that-the-contractor-will-not-achieve-a-level-of-performance-commensurate-with-the-provisional-rate-such-rate-may-be-unilaterally-reduced-or-discontinued. .z:Heading-3}

### The Contracting Officer shall notify the contractor, in writing, if it's determined that a reduction or discontinuance of provisional award fee payments is to be made. This determination is not subject to "Disputes" clause. {#the-contracting-officer-shall-notify-the-contractor-in-writing-if-its-determined-that-a-reduction-or-discontinuance-of-provisional-award-fee-payments-is-to-be-made.-this-determination-is-not-subject-to-disputes-clause. .z:Heading-3}

### All provisional award fee payments will be superseded by the periodic evaluation. If the FDO's determination for a period results in earned award fee above that provisionally provided, the Contracting Officer will issue a unilateral modification to recognize such and payment will be made based upon the unilateral modification. If the amount of award fee earned, as determined by the FDO, is less than the sum of the provisional payments for that period, the contractor will either credit the next payment voucher for the amount over-paid or refund the difference to the Government, as directed by the Contracting Officer. {#all-provisional-award-fee-payments-will-be-superseded-by-the-periodic-evaluation.-if-the-fdos-determination-for-a-period-results-in-earned-award-fee-above-that-provisionally-provided-the-contracting-officer-will-issue-a-unilateral-modification-to-recognize-such-and-payment-will-be-made-based-upon-the-unilateral-modification.-if-the-amount-of-award-fee-earned-as-determined-by-the-fdo-is-less-than-the-sum-of-the-provisional-payments-for-that-period-the-contractor-will-either-credit-the-next-payment-voucher-for-the-amount-over-paid-or-refund-the-difference-to-the-government-as-directed-by-the-contracting-officer. .z:Heading-3}

### Provisional payment of periodic award fee will be made prior to the first award fee determination by the Government. {#provisional-payment-of-periodic-award-fee-will-be-made-prior-to-the-first-award-fee-determination-by-the-government. .z:Heading-3}

### **Fee Reduction for Catastrophic Loss** {#fee-reduction-for-catastrophic-loss .z:Heading-3}

Any available award fee for the current six month evaluation period is
subject to the section contained hereafter entitled "Fee Reduction for
Catastrophic Loss".

# RESERVED

# Performance Fee

The Performance Fee serves to motivate and ensure safe and successful
missions utilizing objective, mission specific criteria. The Performance
Fee shall be determined in accordance with the following process.

# Evaluation Procedures

### The contractor will be evaluated for each Space Shuttle Mission in accordance with the Performance Fee criteria identified in this plan. In a letter to the contractor, 30 calendar days prior to each flight, the COTR shall identify the major mission objectives associated with each mission. {#the-contractor-will-be-evaluated-for-each-space-shuttle-mission-in-accordance-with-the-performance-fee-criteria-identified-in-this-plan.-in-a-letter-to-the-contractor-30-calendar-days-prior-to-each-flight-the-cotr-shall-identify-the-major-mission-objectives-associated-with-each-mission. .z:Heading-3}

### Within 10 days after the completion of a mission, the contractor shall submit a written report to the Contracting Officer with its recommendation as to the successful accomplishment of each Performance Fee criteria. {#within-10-days-after-the-completion-of-a-mission-the-contractor-shall-submit-a-written-report-to-the-contracting-officer-with-its-recommendation-as-to-the-successful-accomplishment-of-each-performance-fee-criteria. .z:Heading-3}

### The Contracting Officer shall, in conjunction with the COTR and Space Shuttle Program Manager, confirm the successful accomplishment of each Performance Fee criteria. The Contracting Officer will issue a unilateral modification to the contractor recognizing the earning of the specific Performance Fees within 30 days of receipt of the contractor's written report.  {#the-contracting-officer-shall-in-conjunction-with-the-cotr-and-space-shuttle-program-manager-confirm-the-successful-accomplishment-of-each-performance-fee-criteria.-the-contracting-officer-will-issue-a-unilateral-modification-to-the-contractor-recognizing-the-earning-of-the-specific-performance-fees-within-30-days-of-receipt-of-the-contractors-written-report. .z:Heading-3}

### Payment of the authorized Performance Fee shall be executed by the NASA Financial Management Office upon receipt of the unilateral contract modification. {#payment-of-the-authorized-performance-fee-shall-be-executed-by-the-nasa-financial-management-office-upon-receipt-of-the-unilateral-contract-modification. .z:Heading-3}

### A single unilateral contract modification will be issued to remove all performance fee associated with the mission from the available Award Fee for the period and to remove all unearned performance fee dollars from performance fee available on the contract. Dollars not earned will also be captured in Attachment II, Table B -- Mission Execution Fee. {#a-single-unilateral-contract-modification-will-be-issued-to-remove-all-performance-fee-associated-with-the-mission-from-the-available-award-fee-for-the-period-and-to-remove-all-unearned-performance-fee-dollars-from-performance-fee-available-on-the-contract.-dollars-not-earned-will-also-be-captured-in-attachment-ii-table-b-mission-execution-fee. .z:Heading-3}

### The Contracting Officer's determination for Performance Fee is subject to the "Disputes" clause of the contract. {#the-contracting-officers-determination-for-performance-fee-is-subject-to-the-disputes-clause-of-the-contract. .z:Heading-3}

# Performance Fee Criteria

### The contractor's performance in meeting major program objectives will be measured utilizing the objective, predefined criteria established below. The fee associated with successful completion of these criteria is stated below. These criteria, as well as the associated fee, will change only through bilateral agreement. The following criteria are established per flight.  {#the-contractors-performance-in-meeting-major-program-objectives-will-be-measured-utilizing-the-objective-predefined-criteria-established-below.-the-fee-associated-with-successful-completion-of-these-criteria-is-stated-below.-these-criteria-as-well-as-the-associated-fee-will-change-only-through-bilateral-agreement.-the-following-criteria-are-established-per-flight. .z:Heading-3}

### Total Available Award Fee and Performance Fee is documented in Attachment II, Table B -- Mission Execution Fee. As Performance Fee is determined to be either earned or unearned in accordance with the Evaluation Procedures above, that fee will no longer be available to be earned within the Award Fee feature of the contract. Performance Fee shall be earned as described below for the number of flights described in H.33, Launch Schedule Variations. Should a flight be deleted from the manifest or delayed from one Award Fee period to another, the performance fee allocated to that flight shall be converted and added to Maximum Available Award Fee, and Attachment II, Table B -- Mission Execution Fee, shall be adjusted, in the period in which the flight was removed. Should deferral or acceleration of a flight from one Award Fee period to another cause the total required Performance Fee for that period as displayed in Attachment 1, Table B to be insufficient, an equivalent amount of Award Fee will be made available in that period for the flight as Performance Fee. {#total-available-award-fee-and-performance-fee-is-documented-in-attachment-ii-table-b-mission-execution-fee.-as-performance-fee-is-determined-to-be-either-earned-or-unearned-in-accordance-with-the-evaluation-procedures-above-that-fee-will-no-longer-be-available-to-be-earned-within-the-award-fee-feature-of-the-contract.-performance-fee-shall-be-earned-as-described-below-for-the-number-of-flights-described-in-h.33-launch-schedule-variations.-should-a-flight-be-deleted-from-the-manifest-or-delayed-from-one-award-fee-period-to-another-the-performance-fee-allocated-to-that-flight-shall-be-converted-and-added-to-maximum-available-award-fee-and-attachment-ii-table-b-mission-execution-fee-shall-be-adjusted-in-the-period-in-which-the-flight-was-removed.-should-deferral-or-acceleration-of-a-flight-from-one-award-fee-period-to-another-cause-the-total-required-performance-fee-for-that-period-as-displayed-in-attachment-1-table-b-to-be-insufficient-an-equivalent-amount-of-award-fee-will-be-made-available-in-that-period-for-the-flight-as-performance-fee. .z:Heading-3}

### The maximum available Performance Fee associated with each successfully completed flight is \$7.00M, subject to the performance criteria below. {#the-maximum-available-performance-fee-associated-with-each-successfully-completed-flight-is-7.00m-subject-to-the-performance-criteria-below. .z:Heading-3}

  ------------------------------------------- ---------------------------
  Performance Criteria for Each Mission       Incentive/Penalty Amount

  Landing, Recovery, and Safe Return          \$7.00M

  Failure to Achieve Major Mission Objectives Up to (\$5.60M)

  Early Mission Termination                   Up to (\$1.40M)

                                              
  ------------------------------------------- ---------------------------

### The Performance Fee criteria are as follows: {#the-performance-fee-criteria-are-as-follows .z:Heading-3}

### Landing, Recovery, and Safe Return {#landing-recovery-and-safe-return .z:Heading-3}

"Successful accomplishment" is evidenced by completion of a safe landing
and recovery of the crew and the Orbiter. It also includes SRB recovery.
Successful accomplishment of the SRB recovery is when the SRB Recovery
System performs in accordance with the requirements of the Part I CEI
Specification.

### Failure to Achieve Major Mission Objectives (Reduction in Fee) {#failure-to-achieve-major-mission-objectives-reduction-in-fee .z:Heading-3}

If a major mission objective(s) is not achieved, then the contractor
shall be assessed a reduction in fee up to a maximum of the amount as
shown in Section 4.2.3, if it is determined that flight or ground
anomalies attributed to the contractor's performance precluded the
accomplishment of those major mission objectives..

### Early Mission Termination (Reduction in Fee) {#early-mission-termination-reduction-in-fee .z:Heading-3}

If an early mission termination occurs due to flight or ground anomalies
attributed to the contractor's performance, the contractor shall be
assessed a reduction in fee up to a maximum of the amount as shown in
Section 4.2.3.

# Contractor Accountability

For purposes of defining performance fee accountability, the contractor
is accountable for all performance during the contract period. This
includes, but is not limited to, the contractor's subcontractor's (at
any tier) performance under the contract. Additionally, the contractor
shall be held accountable for the performance of the Stakeholders and
their subcontractors at any tier, of effort performed as part of the
SPOC.

Performance problems, which are a result of original defects in design,
manufacturing, or workmanship are not accountable to the contractor
unless it is determined that an existing defect in design,
manufacturing, or workmanship was not discovered due to a lack of
reasonable test, inspection, procedures, or processing by the contractor
or its subcontractor (at any tier). In such cases, the contractor shall
be accountable for this failure irrespective of when the hardware was
built, or what contract the hardware was built under.

# Provisional Payments

Performance Fee is not subject to provisional billing.

# Fee Reduction for Catastrophic Loss

## A fee reduction will be assessed in the event of loss of an Orbiter or individuals associated with Space Program Operations when such loss is caused by the acts or omissions of the contractor in performance of effort under this contract. {#a-fee-reduction-will-be-assessed-in-the-event-of-loss-of-an-orbiter-or-individuals-associated-with-space-program-operations-when-such-loss-is-caused-by-the-acts-or-omissions-of-the-contractor-in-performance-of-effort-under-this-contract. .z:Heading-2}

## For purposes of this article, "loss" means the loss of life which occurs because of an Orbiter mission or total loss, at any time, of an Orbiter vehicle. "Orbiter Mission" commences with fueling of the external tank through actual flight to safe return of the crew. "Total loss" means that an Orbiter is permanently inoperable. {#for-purposes-of-this-article-loss-means-the-loss-of-life-which-occurs-because-of-an-orbiter-mission-or-total-loss-at-any-time-of-an-orbiter-vehicle.-orbiter-mission-commences-with-fueling-of-the-external-tank-through-actual-flight-to-safe-return-of-the-crew.-total-loss-means-that-an-orbiter-is-permanently-inoperable. .z:Heading-2}

## In the event of loss, the Contracting Officer in conjunction with a Board of Investigation shall make a determination as to the cause of the loss. The members of the Board of Investigation shall be appointed by the Fee Determination Official or other senior NASA official. If the loss is determined to be caused in whole or in part by the acts or omissions of the contractor, the Fee Determination Official shall make a determination as to the amount of the fee reduction to be assessed, in an amount not to exceed: (1) the available award fee pool for the period in which the loss occurs and; (2) the performance fee applicable to the mission. The Contracting Officer shall notify the contractor in writing of such determination. Repayment of any fee, if required, shall be made within 30 days of notification of a final determination by the Contracting Officer. {#in-the-event-of-loss-the-contracting-officer-in-conjunction-with-a-board-of-investigation-shall-make-a-determination-as-to-the-cause-of-the-loss.-the-members-of-the-board-of-investigation-shall-be-appointed-by-the-fee-determination-official-or-other-senior-nasa-official.-if-the-loss-is-determined-to-be-caused-in-whole-or-in-part-by-the-acts-or-omissions-of-the-contractor-the-fee-determination-official-shall-make-a-determination-as-to-the-amount-of-the-fee-reduction-to-be-assessed-in-an-amount-not-to-exceed-1-the-available-award-fee-pool-for-the-period-in-which-the-loss-occurs-and-2-the-performance-fee-applicable-to-the-mission.-the-contracting-officer-shall-notify-the-contractor-in-writing-of-such-determination.-repayment-of-any-fee-if-required-shall-be-made-within-30-days-of-notification-of-a-final-determination-by-the-contracting-officer. .z:Heading-2}

## The Contracting Officer's determination is subject to the "Disputes" clause of the contract. {#the-contracting-officers-determination-is-subject-to-the-disputes-clause-of-the-contract. .z:Heading-2}

# Value Engineering

VECPs serve as a tool in reducing the overall projected cost to the
agency without impairing its essential functions. As identified in
Clause H.40, VALUE ENGINEERING, the contractor is encouraged to develop,
prepare, and submit value engineering change proposals (VECPs)
voluntarily. The contractor shall share in any net acquisition savings
reductions for each accepted VECP as identified below.

# End of Program (EOP) Fee

## The purpose of the EOP Fee is to motivate the contractor to maintain the appropriate level of skills and resources to safely complete the program objectives. {#the-purpose-of-the-eop-fee-is-to-motivate-the-contractor-to-maintain-the-appropriate-level-of-skills-and-resources-to-safely-complete-the-program-objectives. .z:Heading-2}

### EOP Fee will be made available upon the end of mission execution. For the purposes of this plan, mission execution is defined as the completion of down-mission processing following the last shuttle flight. The contractor will submit a letter notifying the Contracting Officer of the end of mission execution. The Contracting Officer will provide written concurrence, or non-concurrence along with supporting rationale, within 15 days of receipt of the Contractors letter. A determination of the performance score and the related dollars earned for the EOP Fee will be made by the FDO not later than 45 days after the end of the mission execution. In the event that a manifest change moves the end of mission execution to a date beyond CY2010, the contractor will be evaluated and an EOP fee determination issued for settlement of the EOP fee pool, in accordance with the schedule noted herein, at the conclusion of the basic period of performance of the contract. A contract modification recognizing the dollars earned will be issued within 15 days after the FDO determination. Best efforts will be made to issue the contract modification within CY 2010. The EOP Fee is subject to the scoring system delineated in Attachment I, Table A -- Award Fee and EOP Fee Scoring System. The available EOP Fee dollars are stated in B.2, [Estimated Cost and Fee]{.underline}, and in Attachment II, Table B -- Mission Execution Fee, and are separate from the available Award Fee and Performance Fee dollars. The EOP Fee is subject to provisional billing. Pending a determination of the amount of EOP fee earned, a portion of the available EOP fee for a period will be provisionally paid to the contractor on a monthly basis. The provisional payment shall never exceed 80%. The amount of provisional fee which may be paid monthly commencing in evaluation period 9 shall be prorated equally to the number of months in that period. Procedures to be followed in monitoring, assessing, and evaluating contractor performance are described below. {#eop-fee-will-be-made-available-upon-the-end-of-mission-execution.-for-the-purposes-of-this-plan-mission-execution-is-defined-as-the-completion-of-down-mission-processing-following-the-last-shuttle-flight.-the-contractor-will-submit-a-letter-notifying-the-contracting-officer-of-the-end-of-mission-execution.-the-contracting-officer-will-provide-written-concurrence-or-non-concurrence-along-with-supporting-rationale-within-15-days-of-receipt-of-the-contractors-letter.-a-determination-of-the-performance-score-and-the-related-dollars-earned-for-the-eop-fee-will-be-made-by-the-fdo-not-later-than-45-days-after-the-end-of-the-mission-execution.-in-the-event-that-a-manifest-change-moves-the-end-of-mission-execution-to-a-date-beyond-cy2010-the-contractor-will-be-evaluated-and-an-eop-fee-determination-issued-for-settlement-of-the-eop-fee-pool-in-accordance-with-the-schedule-noted-herein-at-the-conclusion-of-the-basic-period-of-performance-of-the-contract.-a-contract-modification-recognizing-the-dollars-earned-will-be-issued-within-15-days-after-the-fdo-determination.-best-efforts-will-be-made-to-issue-the-contract-modification-within-cy-2010.-the-eop-fee-is-subject-to-the-scoring-system-delineated-in-attachment-i-table-a-award-fee-and-eop-fee-scoring-system.-the-available-eop-fee-dollars-are-stated-in-b.2-estimated-cost-and-fee-and-in-attachment-ii-table-b-mission-execution-fee-and-are-separate-from-the-available-award-fee-and-performance-fee-dollars.-the-eop-fee-is-subject-to-provisional-billing.-pending-a-determination-of-the-amount-of-eop-fee-earned-a-portion-of-the-available-eop-fee-for-a-period-will-be-provisionally-paid-to-the-contractor-on-a-monthly-basis.-the-provisional-payment-shall-never-exceed-80.-the-amount-of-provisional-fee-which-may-be-paid-monthly-commencing-in-evaluation-period-9-shall-be-prorated-equally-to-the-number-of-months-in-that-period.-procedures-to-be-followed-in-monitoring-assessing-and-evaluating-contractor-performance-are-described-below. .z:Heading-3}

### The contractor may furnish a self-evaluation report within 10 calendar days after the conclusion of the mission execution. This self-evaluation report shall not exceed 20 pages in length. The PEB will not submit its recommendation to the FDO until (1) the contractor's self-evaluation report has been received and considered, or (2) the contractor has provided written notification that a self-evaluation report will not be submitted, or (3) the 10-day period provided for submission of the report has expired. {#the-contractor-may-furnish-a-self-evaluation-report-within-10-calendar-days-after-the-conclusion-of-the-mission-execution.-this-self-evaluation-report-shall-not-exceed-20-pages-in-length.-the-peb-will-not-submit-its-recommendation-to-the-fdo-until-1-the-contractors-self-evaluation-report-has-been-received-and-considered-or-2-the-contractor-has-provided-written-notification-that-a-self-evaluation-report-will-not-be-submitted-or-3-the-10-day-period-provided-for-submission-of-the-report-has-expired. .z:Heading-3}

### At the end of mission execution, the PEIT will prepare a written report documenting its evaluation which shall include recommendations for an adjective rating and numerical score to be assigned to the contractor's performance in meeting the EOP Fee objectives. This PEIT report will be presented to the PEB. {#at-the-end-of-mission-execution-the-peit-will-prepare-a-written-report-documenting-its-evaluation-which-shall-include-recommendations-for-an-adjective-rating-and-numerical-score-to-be-assigned-to-the-contractors-performance-in-meeting-the-eop-fee-objectives.-this-peit-report-will-be-presented-to-the-peb. .z:Heading-3}

### Upon receipt of the PEIT report, the PEB shall meet to consider all of the performance information it has obtained. At the meeting, the PEB will summarize its preliminary findings and recommendations in the Performance Evaluation Board -- EOP Fee Report (PEB-EFR). The PEB-EFR shall include recommendations for an adjectival rating and numerical score to be assigned to the contractor's performance in meeting the EOP Fee objectives. This report as well as a PEB presentation will be provided to the FDO. The contractor shall have the opportunity to make a presentation to the PEB if they so desire. {#upon-receipt-of-the-peit-report-the-peb-shall-meet-to-consider-all-of-the-performance-information-it-has-obtained.-at-the-meeting-the-peb-will-summarize-its-preliminary-findings-and-recommendations-in-the-performance-evaluation-board-eop-fee-report-peb-efr.-the-peb-efr-shall-include-recommendations-for-an-adjectival-rating-and-numerical-score-to-be-assigned-to-the-contractors-performance-in-meeting-the-eop-fee-objectives.-this-report-as-well-as-a-peb-presentation-will-be-provided-to-the-fdo.-the-contractor-shall-have-the-opportunity-to-make-a-presentation-to-the-peb-if-they-so-desire. .z:Heading-3}

### The contractor may choose to make a presentation to the PEB. If the contractor chooses to make a presentation, notification must be made to the Contracting Officer no later than 15 working days after the end of mission execution. The presentation, if provided, will be limited to one hour in length. {#the-contractor-may-choose-to-make-a-presentation-to-the-peb.-if-the-contractor-chooses-to-make-a-presentation-notification-must-be-made-to-the-contracting-officer-no-later-than-15-working-days-after-the-end-of-mission-execution.-the-presentation-if-provided-will-be-limited-to-one-hour-in-length. .z:Heading-3}

### The PEB Chair is responsible for the preparation of the PEB-EFR and will present the findings and recommendation to the FDO. The report will include an adjective rating and a recommended overall performance score with supporting documentation. {#the-peb-chair-is-responsible-for-the-preparation-of-the-peb-efr-and-will-present-the-findings-and-recommendation-to-the-fdo.-the-report-will-include-an-adjective-rating-and-a-recommended-overall-performance-score-with-supporting-documentation. .z:Heading-3}

### The FDO will consider the recommendations of the following sources in determining the performance score: (1) PEB; (2) PEIT; (3) information provided by the contractor; and (4) any other pertinent information. The FDO's determination of the scores will be stated in a written EOP Fee Determination (EFD). {#the-fdo-will-consider-the-recommendations-of-the-following-sources-in-determining-the-performance-score-1-peb-2-peit-3-information-provided-by-the-contractor-and-4-any-other-pertinent-information.-the-fdos-determination-of-the-scores-will-be-stated-in-a-written-eop-fee-determination-efd. .z:Heading-3}

### The contractor will be notified by the Contracting Officer of the FDO performance score, and will be provided a summary of the PEB-EFR. The contractor may provide additional information for consideration by the FDO by notifying the Contracting Officer of its desire to do so. This is an opportunity for the contractor to provide any information which the contractor believes is relevant to its performance and which may affect the FDO's determination. Any additional information should be provided to the Contracting Officer within 5 calendar days of contractor receipt of the FDO adjectival rating, numerical score, and PEB-EFR. This additional contractor information will be provided to the FDO by the Contracting Officer through the PEB Chair. {#the-contractor-will-be-notified-by-the-contracting-officer-of-the-fdo-performance-score-and-will-be-provided-a-summary-of-the-peb-efr.-the-contractor-may-provide-additional-information-for-consideration-by-the-fdo-by-notifying-the-contracting-officer-of-its-desire-to-do-so.-this-is-an-opportunity-for-the-contractor-to-provide-any-information-which-the-contractor-believes-is-relevant-to-its-performance-and-which-may-affect-the-fdos-determination.-any-additional-information-should-be-provided-to-the-contracting-officer-within-5-calendar-days-of-contractor-receipt-of-the-fdo-adjectival-rating-numerical-score-and-peb-efr.-this-additional-contractor-information-will-be-provided-to-the-fdo-by-the-contracting-officer-through-the-peb-chair. .z:Heading-3}

### The EFD will be provided to the contractor by the Contracting Officer, along with the performance evaluations prepared by the TMRs. The contractor may, after notification of the determination, request, through the Contracting Officer, a briefing by the PEB Chair. This briefing shall be conducted no later than 14 days following the written request by the contractor. {#the-efd-will-be-provided-to-the-contractor-by-the-contracting-officer-along-with-the-performance-evaluations-prepared-by-the-tmrs.-the-contractor-may-after-notification-of-the-determination-request-through-the-contracting-officer-a-briefing-by-the-peb-chair.-this-briefing-shall-be-conducted-no-later-than-14-days-following-the-written-request-by-the-contractor. .z:Heading-3}

### The EFD provided by the Contracting Officer is subject to the "Disputes" clause of the contract. {#the-efd-provided-by-the-contracting-officer-is-subject-to-the-disputes-clause-of-the-contract. .z:Heading-3}

# Evaluation Factors

## NASA will evaluate the contractor on its performance in meeting the EOP Fee objectives. Actions taken by the Contractor to reduce costs to comply with NASA funding limitations shall be taken into consideration in this evaluation. Evaluation factors include: {#nasa-will-evaluate-the-contractor-on-its-performance-in-meeting-the-eop-fee-objectives.-actions-taken-by-the-contractor-to-reduce-costs-to-comply-with-nasa-funding-limitations-shall-be-taken-into-consideration-in-this-evaluation.-evaluation-factors-include .z:Heading-2}

#### **The contractor's performance in the retention of critical skills and capabilities to ensure sustainability based on criteria mutually agreed upon by the Contracting Officer's Technical Representative and the contractor's Program Manager.**

#### **The contractor's performance in transition and closeout work, to the extent authorized and funded.**

#### **The contractor's performance in sustaining assets and infrastructure to safely complete the manifest based on criteria mutually agreed upon by the Contracting Officer's Technical Representative and the contractor's Program Manager.**

#### **The contractor's performance in maintaining a proper balance between spares to support fly-out of the Program and end of Program inventory based on criteria mutually agreed upon by the Contracting Officer's Technical Representative and the contractor's Program Manager.**

#### **The contractor's performance in managing the balance of workforce levels for accomplishment of required work and the best efforts outplacement of personnel in concert with Program closeout, based on criteria mutually agreed upon by the Contracting Officer's Technical Representative and the contractor's Program Manager.**

#### **The contractor's performance in avoiding impacts which would preclude the completion of a seventeen flight manifest.**

## The AFD or TMR performance evaluations stated in 2.2.3 and 2.2.11will include constructive feedback, as appropriate, to evaluate the contractor's progress in meeting the EOP Fee objectives; scoring will not be provided on this periodic feedback. {#the-afd-or-tmr-performance-evaluations-stated-in-2.2.3-and-2.2.11will-include-constructive-feedback-as-appropriate-to-evaluate-the-contractors-progress-in-meeting-the-eop-fee-objectives-scoring-will-not-be-provided-on-this-periodic-feedback. .z:Heading-2}

# Updates to EOP Fee for Future Shuttle-Related Changes

Future Shuttle-related debit changes which add content to the SPOC shall
contribute at least 25% of the total available fee for the individual
debit change to the End of Program Fee pool in periods 7 and/or 8. 
After negotiations establish the amount of fee associated with future
Shuttle-related Core credit changes, the credit fee removed from End of
Program fee in periods 7 and/or 8 shall not exceed 11.88% of the total
available fee for the individual credit change.  Shuttle-related debit
changes may include Core, Provisioning, and IDIQ type changes;
Shuttle-related debit changes in direct support of Constellation are not
subject to this paragraph.

**ATTACHMENT I**

**Table A - Award Fee and EOP Fee Scoring System**

+-----------------+------------------+---------------------------------+
| **ADJECTIVE     | **RANGE OF       | **DESCRIPTION**                 |
| RATING**        | POINTS**         |                                 |
+-----------------+------------------+---------------------------------+
| Excellent       | 100 - 91         | Of exceptional merit; exemplary |
|                 |                  | performance in a timely,        |
|                 |                  | efficient manner; performance   |
|                 |                  | meets or exceeds contract       |
|                 |                  | requirements (e.g., contract    |
|                 |                  | standards) ; very minor (if     |
|                 |                  | any) deficiencies with no       |
|                 |                  | adverse effect on overall       |
|                 |                  | performance                     |
+-----------------+------------------+---------------------------------+
| Very Good       | 90 - 81          | Effective performance;          |
|                 |                  | requirements accomplished in a  |
|                 |                  | timely, efficient manner for    |
|                 |                  | the most part; substantially    |
|                 |                  | exceeds minimum contract        |
|                 |                  | requirements (e.g., Maximum     |
|                 |                  | Error Rates) with only minor    |
|                 |                  | deficiencies.                   |
+-----------------+------------------+---------------------------------+
| Good            | 80 - 71          | Effective performance; exceeds  |
|                 |                  | minimum contract requirements   |
|                 |                  | (e.g., Maximum Error Rates);    |
|                 |                  | reportable deficiencies, but    |
|                 |                  | with little identifiable effect |
|                 |                  | on overall performance.         |
+-----------------+------------------+---------------------------------+
| Satisfactory    | 70 - 61          | Performance which meets minimum |
|                 |                  | contract requirements (e.g.,    |
|                 |                  | Maximum Error Rates);           |
|                 |                  | reportable deficiencies with    |
|                 |                  | identifiable, but not           |
|                 |                  | substantial, effects on overall |
|                 |                  | performance.                    |
+-----------------+------------------+---------------------------------+
| Poor/           | 60 - 0           | Overall performance does not    |
|                 |                  | meet minimum contract           |
| Unsatisfactory  |                  | requirements (e.g., Maximum     |
|                 |                  | Error Rates); remedial action   |
|                 |                  | required in one or more areas;  |
|                 |                  | numerous deficiencies which     |
|                 |                  | adversely affect performance.   |
+-----------------+------------------+---------------------------------+

<table style="width:100%;">
<colgroup>
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 9%" />
<col style="width: 3%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 6%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 1%" />
<col style="width: 8%" />
<col style="width: 9%" />
<col style="width: 10%" />
<col style="width: 1%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="16"><strong>Attachment II</strong></td>
<td></td>
</tr>
<tr class="even">
<td colspan="16"><strong>Table B - Mission Execution Fee</strong></td>
<td></td>
</tr>
<tr class="odd">
<td><strong> </strong></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2" rowspan="2"><p>Fiscal Year</p>
<p>Evaluation Period</p></td>
<td colspan="3">FY07</td>
<td colspan="4">FY08</td>
<td colspan="4">FY09</td>
<td colspan="2">FY10</td>
<td rowspan="2">Total</td>
<td></td>
</tr>
<tr class="odd">
<td>1</td>
<td colspan="2">2</td>
<td colspan="2">3</td>
<td colspan="2">4</td>
<td colspan="2">5</td>
<td colspan="2">6</td>
<td>7</td>
<td>8</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"><strong>Fee Type</strong></td>
<td>10/01/2006 to 03/31/2007</td>
<td colspan="2">04/01/2007 to 09/30/2007</td>
<td colspan="2">10/01/2007 to 03/31/2008</td>
<td colspan="2">04/01/2008 to 09/30/2008</td>
<td colspan="2">10/01/2008 to 03/31/2009</td>
<td colspan="2">04/01/2009 to 09/30/2009</td>
<td>10/01/2009 to 03/31/2010</td>
<td>04/01/2010 to 09/30/2010</td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>Award Fee and Performance Fee</strong></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total Available Award Fee</td>
<td>$66,999,296</td>
<td colspan="2">$66,999,300</td>
<td colspan="2">$57,763,409</td>
<td colspan="2">$64,763,410</td>
<td colspan="2">$51,965,520</td>
<td colspan="2">$58,965,522</td>
<td>$25,872,175</td>
<td>$32,872,175</td>
<td>$426,200,807</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Total Available Performance Fee</td>
<td>$14,000,000</td>
<td colspan="2">$14,000,000</td>
<td colspan="2">$21,000,000</td>
<td colspan="2">$14,000,000</td>
<td colspan="2">$21,000,000</td>
<td colspan="2">$14,000,000</td>
<td>$14,000,000</td>
<td>$7,000,000</td>
<td>$119,000,000</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total Available Award and Performance Fees</td>
<td>$80,999,296</td>
<td colspan="2">$80,999,300</td>
<td colspan="2">$78,763,409</td>
<td colspan="2">$78,763,410</td>
<td colspan="2">$72,965,520</td>
<td colspan="2">$72,965,522</td>
<td>$39,872,175</td>
<td>$39,872,175</td>
<td>$545,200,807</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Performance Fee Earned</td>
<td> $7,000,000</td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td>$7,000,000 </td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Unearned Performance Fee</td>
<td> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Net Available Award Fee</td>
<td>$73,999,296</td>
<td colspan="2">$80,999,300</td>
<td colspan="2">$78,763,409</td>
<td colspan="2">$78,763,410</td>
<td colspan="2">$72,965,520</td>
<td colspan="2">$72,965,522</td>
<td>$39,872,175</td>
<td>$39,872,175</td>
<td>$538,200,807</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total Award Fee Earned</td>
<td> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Unearned Award Fee</td>
<td> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total Performance and Award Fees Earned</td>
<td>$7,000,000 </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td>$7,000,000 </td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>End of Program Fee</strong></td>
<td> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total EOP Fee Available</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>$36,550,000</td>
<td>$36,550,000</td>
<td>$73,100,000</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Unearned EOP Fee</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>TBD</td>
<td>TBD</td>
<td>TBD</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total EOP Fee Earned</td>
<td>N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td colspan="2">N/A</td>
<td>TBD</td>
<td>TBD</td>
<td>TBD</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td> </td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total Available Fee</td>
<td>$80,999,296</td>
<td colspan="2">$80,999,300</td>
<td colspan="2">$78,763,409</td>
<td colspan="2">$78,763,410</td>
<td colspan="2">$72,965,520</td>
<td colspan="2">$72,965,522</td>
<td>$76,422,175</td>
<td>$76,422,175</td>
<td>$618,300,807</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2">Total Unearned Fee</td>
<td> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td colspan="2"> </td>
<td> </td>
<td> </td>
<td>$0</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">Total Fee Earned</td>
<td>$7,000,000</td>
<td colspan="2">$0</td>
<td colspan="2">$0</td>
<td colspan="2">$0</td>
<td colspan="2">$0</td>
<td colspan="2">$0</td>
<td>$0</td>
<td>$0</td>
<td>$7,000,000</td>
<td></td>
</tr>
</tbody>
</table>

**ATTACHMENT J-9**

**GOVERNMENT FURNISHED PROPERTY**

PURPOSE:

The following is Government Furnished Property (GFP) provided at various
sites under this contract.

For purposes of this letter contract, the overall number of line items
and the associated dollar value of Government Furnished Property (GFP)
that will be transferred from NAS 9-20000, grouped by classification, is
provided in the following table. At the time of contract award, an
updated CD-ROM listing of all GFP that will be transferred from NAS
9-20000 will be incorporated into the Space Program Operations Contract
(SPOC).

  -------------------------------------- -------------- -----------------
  **Classification**                     **\# Line      **Value**
                                         Items**        

                                                        

  Buildings 100K & Over                  6              \$2,217,323

  Other Struct & Facilities 100K and     1              \$349,760
  over                                                  

                                                        

  Equipment under 100K                   56,776         \$239,611,041

  Equipment over 100K                    675            \$168,580,236

                                                        

  Special Test Equip under 100K          6,555          \$42,660,356

  Special Test Equip over 100K           175            \$65,227,125

                                                        

  Special Tooling under 100K             22,291         \$52,423,333

  Special Tooling over 100K              56             \$17,858,177

                                                        

  Agency Peculiar under 100K             24,609         \$133,963,212

  Agency Peculiar over 100K              976            \$4,367,390,550

                                                        

  Material                                              \$3,403,585,264

                                                        

  TOTAL                                  112,120        \$8,493,866,377
  -------------------------------------- -------------- -----------------

**SECTION J-9-A JOHNSON SPACE CENTER** [Page]{.underline}

Part J-9-A-1 Equipment J-9-[3](#a1)

J-9-A-2 Special Tooling/Test Equipment J-9-[4](#A2)

J-9-A-3 Materials J-9-[6](#A3)

J-9-A-4 Software J-9-[7](#A4)

J-9-A-5 Facilities J-9-[9](#a5)

J-9-A-6 Data J-9-[12](#a6)

J-9-A-7 List of Installation Provided Property J-9-[13](#a7)

**SECTION J-9-B KENNEDY SPACE CENTER**

Part J-9-B-1 Equipment J-9-[14](#b1)

J-9-B-2 Special Tooling/Test Equipment J-9-[15](#b2)

######  J-9-B-3 Materials J-9-[16](#b3)

J-9-B-4 Software J-9-[17](#b4)

J-9-B-5 Facilities J-9-[18](#b5)

**SECTION J-9-C MARSHALL SPACE FLIGHT SPACE CENTER**

Part J-9-C-1 Equipment J-9-[51](#c1)

J-9-C-2 Special Tooling/Test Equipment J-9-[52](#c2)

J-9-C-3 Reserved J-9-[53](#C3)

J-9-C-4 Software J-9-[54](#C4)

########  J-9-C-5 Facilities J-9-[55](#c5)

**SECTION J-9-D DRYDEN FLIGHT RESEARCH CENTER/EDWARDS AFB CA**

Part J-9-D-1 Equipment J-9-[56](#d1)

J-9-D-2 Reserved J-9-[57](#D2)

J-9-D-3 Reserved J-9-[58](#D3)

J-9-D-4 Software J-9-[59](#D4)

**SECTION J-9-E RESERVED**

**SECTION J-9-F RESERVED**

**SECTION J-9-G WHITE SANDS SPACE HARBOR**

Part J-9-G-1 Equipment J-9-[62](#g1)

**PART J-9-A-1**

[]{#a1 .anchor}**JOHNSON SPACE CENTER**

**GOVERNMENT FURNISHED EQUIPMENT**

The following Government Furnished Equipment (GFE) will be provided for
the performance of work under this contract.

CD-ROM entitled SPOC-1, lists the Government Furnished Equipment
provided under this contract.

The GFE for WCS Processing is set forth in USA Subcontract 6000076641,
dated 10/01/02.

[]{#A2 .anchor}**PART J-9-A-2**

**JOHNSON SPACE CENTER**

**GOVERNMENT FURNISHED SPECIAL TOOLING/TEST EQUIPMENT**

The following Government Furnished Special Tooling and Test Equipment
(GFST/TE) will be provided for the performance of the work under this
contract:

CD-ROM entitled SPOC-1, includes equipment lists for SFOC NAS9-20000.

This includes, but is not limited to, the following:

[ITEM]{.underline} [P/N]{.underline}

Caution and Warning MC409-012-0123

Drill Plate Tool GD1507122

Mod Kit (1 shipset\*) K724-340009

\*Shipset consists of quantity of parts for one port side and one
starboard side of the Orbiter.

PIC VIBRATION FIXTURE AT809101-001

PIC TRANSFORMER & 200 PWB PHASE AT809104-001

PIC DIGIDAT TEST ADAPTER AT809110-001

PIC DIGIDAT TEST ADAPTER AT809110-002

PIC BREAKOUT TOOL AT809111-001

BREAKOUT TOOL AT809113-001

INJECTION MOLD NS006328

PIC PROTECTIVE PLATE SA1249-001

HOLDING FIXTURE SA1275-999

FIXTURE CONDUCTOR LEAS TRIMMIN SA1409-002

POLARITY VERIFICATION TEMPLATE SA1658-001

POLARITY VERIFICATION TEMPLATE SA1658-003

POLARITY VERIFICATION TEMPLATE SA1658-004

PIC MASKING TOOL SA1734-001

PREWIRE TOOL SA1816-003

PREWIRE TOOL SA1816-004

XISTOR PREWIRE TOOL SA1816-005

XISTOR PREWIRE TOOL SA1816-006

XISTOR PREWIRE TOOL SA1816-007

XISTOR PREWIRE TOOL SA1816-008

XISTOR PREWIRE TOOL SA1816-009

XISTOR PREWIRE TOOL SA1816-010

XISTOR PREWIRE TOOL SA1816-011

TEST HOLDING FIXTURE SA2061-001

DIMENSION CHECK PREIMPREGN SA2063-001

DIMENSION CHECK PREIMPREGN SA2063-002

TINNING FIXTURE CONNECTOR SA2071-002

TRANSISTOR MOUNTING BRACKET SA2084-999

STUFFING FIXTURE SA2085-001

ASSEMBLY FIXTURE SA2099-001

ASSEMBLY FIXTURE SA2099-002

MAGNETIC TIMING BOARD SA2254-999

PIC PLACEMENT TOOL SA2261-001

PIC PLACEMENT TOOL SA2261-002

PIC-FINAL ASSY FIXTURE 17453511-999

PIC-LEAD BENDING TOOL 17445312-001

PIC-LEAD BENDING TOOL 17445312-002

PIC-ALIGNMENT FIXTURE 17466733-001

PIC-ALIGNMENT FIXTURE 17466733-002

PIC-ALIGNMENT FIXTURE 17466733-003

Reference USA Subcontract 6000076641 for additional equipment.

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   JSC uses NEMS (NASA System) and Shuttle Equipment Tracking System
    (SETS) for the tracking of equipment.

    []{#A3 .anchor}**PART J-9-A-3**

    **JOHNSON SPACE CENTER**

    **GOVERNMENT FURNISHED MATERIALS**

The following Government Furnished Materials (GFM) will be provided for
the performance of work under this contract as required, and in the
quantities required.

[PRESSURANTS/PROPELLANTS AND MISCELLANEOUS GFM]{.underline}

Air, Breathing

Air, Liquid

Ammonia (NH~3~)

Detonators

Dichlorofluoromethane \[Refrigerant-21 (R-21)\]

Dichlorotetrafluoroethane

Fluonnet Electronic Liquid, lFC 40 (3M)\]

Freon TF 8 Refrigerant

Halon 1301 (Fire Suppression)

Helium, Gaseous (GHe)

Helium, Liquid (LHe)

Hexanitrostilbene (Explosive) HNS

Hydrazine, Monomethyl (MMH)

Hydrazine, Mono-Propellant (N2H4)

Hydrogen, Gaseous (GH2)

Hydrogen, Liquid (LN2)

Inconel 718 Valve Bodies and Sleeve, Seal and Poppet Assemblies for
manufacture of GO-2 Flow Control Valves with ignition resistant parts.

Neon, Liquid

Nitrogen, Gaseous (GN2)

Nitrogen, Liquid (LN2)

Nitrogen Tetroxide (N204 MON3)

Oxygen, Gaseous (GO2)

Oxygen, Gaseous, Breathing

Oxygen, Liquid (LO2)

Pyro Initiator Controller (PIC)

Pyrotechnics

Standard Initiators, Type I

Trichlorotrifluoroethane, [TF Type 2/PCA Solvent Type 1]{.underline} 113

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Materials to be provided to the
contractor for the performance of this contract:

-   JSC uses WIMS (USA System) and SETS (USA System) for the tracking of
    Material

-   KSC uses PeopleSoft Inventory Module (USA System), IPCS (NASA
    System), CSLIMS (Boeing System), and CARS (USA System) and MACPAC
    (USA System) for the tracking of Material.

###### PART J-9-A-4 {#part-j-9-a-4 .unnumbered}

**JOHNSON SPACE CENTER**

**GOVERNMENT FURNISHED SOFTWARE**

**A. GENERAL**

The following Government‑Furnished Software (GFS) including supporting
documentation will be provided as required to the contractor for work
under this contract:

-   Avionics and hardware development in Space Systems Development/Test
    (SSDT) Facility.

-   Flight software.

-   Operational software for the Test Operations Center (TOC)/SAIL.

-   Launch Processing System (LPS)/SAIL software.

-   Mission Evaluation Workstation System (MEWS) Software.

-   SINDA

-   TRASYS

-   IDEAS

-   CSAR/NASTRAN

-   MSC/NASTRAN

-   ORACLE

-   PATRAN

-   ISS Risk Management Application (IRMA)

-   SSP Integrated Risk Management Application (SPIRMA)

The following GFS including supporting documentation will be provided as
required to the contractor for work performed by the Flight Design and
Dynamics Department (FDDD)(including FDDD's subcontractors) only for the
Government purpose of Constellation support. The Contracting Officer in
cooperation with JSC/Engineering shall approve the need for any
organization other than FDDD, including FDDD's subcontractors, to have
access and/or use of the software.

.

-   ANTARES (Advanced NASA Technology Architecture for Exploration
    Studies) (in performance of task FDD-114 and FDD-118)

-   MBDYN (Multibody Dynamics)

-   JEOD (JSC Engineering Orbital Dynamics)

-   TRICK

**B. REQUIREMENTS**

Delivered GFS shall be verified to be in conformance with the following
requirements documents as applicable and currently in force:

-   NPR 2800.1 Managing Information Technology

-   NPR 2810.1 Security of Information Technology

Additional requirements for the GFS supporting Constellation:

-   If the SOFTWARE and/or any documentation provided with the SOFTWARE
    includes a copyright notice, or other restrictive marking or legend,
    identifying it as a work of a third party, the third party software
    or documentation will be governed by the terms and conditions of its
    copyright, or other restrictive marking.

-   

-   

-   The contractor will inform its employees and subcontractors given
    access to the SOFTWARE of these restrictions.

**PART J-9-A-5**

[]{#a5 .anchor}**JOHNSON SPACE CENTER**

**GOVERNMENT FURNISHED FACILITIES**

The following facilities will be furnished to the contractor for use in
performance of work under this contract. The contractor has no
responsibility for maintenance and sustaining engineering for these
facilities.

  ---------------------- -------------------- ---------------------------------------------------
  [CENTER]{.underline}   [BLDG]{.underline}   [TITLE]{.underline}

                                              

  JSC                    4S                   Flight Operations Trainer Facility

  JSC                    4S                   Part Task Trainer (PTT)

  JSC                    5N                   Shuttle Mission Training Facility (SMTF)

  JSC                    5S                   Space Station Training Facility

  JSC                    7                    Crew Systems Laboratory

                                              Space Station Airlock Test Article Facility

  JSC                    9                    Systems Integration Facility

                                              Space Station Mockups/Trainer Facility

                                              Precision Air Bearing Floor

  JSC                    14                   Antenna and Tracking Development Laboratory

                                              Anechoic Chamber

  JSC                    29                   Weightless Environment Training Facility

  JSC                    32                   Space Environment Simulation Laboratory

                                              Chamber A

                                              Chamber B

  JSC                    44                   Communications and Tracking Development Laboratory

                                              Electronic System Test Lab

  JSC                    49                   Vibration and Acoustics Test Facility Vibroacoustic
                                              Test Facility

  JSC                    267                  Space Materials Research Laboratory

                                              Hypervelocity Impact Test Facility

  JSC                    272                  Hazardous Hypervelocity Impact Test Facility

  JSC                    16                   Inertial Systems Laboratory

  JSC                    990                  Maintenance Hangar

  Ellington                                   KC‑135 Reduced Gravity Aircraft

  WSTF                                        RVS Engine Depot

  WSTF                                        Hazardous Hypervelocity Impact Test facility

  JSC                    35                   Mission Simulation Development Facility

  JSC                    35                   Controlled Data Preparation Area (CDPA)

  JSC                    16                   Shuttle Avionics Intergration Laboratory (SAIL)

  JSC                    16                   Electrical Power Systems Laboratory

  JSC                    16                   JSC Avionics Engineering Laboratory (JAEL)

  JSC                    30                   Mission Control

  JSC                    4                    Environmental Control Laboratory

  JSC                    NBL                  Sunny Carter Training Facility (NBL)

  JSC                    NBL                  Software Development Integration Laboratory (SDIL)
  ---------------------- -------------------- ---------------------------------------------------

**Palmdale, CA**

  -------------------- -------------------------------------------------------------
  [BLDG]{.underline}   [TITLE]{.underline}

  122T                 OLF Office

  0150                 Shuttle Orbiter Final Assmb. Bldg.

  151C                 Canopy

  3001                 Land Surrounding B/150

  3002                 Storm Drain Service Line Bldg AG

  3003                 Periphery Security Fence

  3004                 Concrete Aprons Sidewalk

  3005                 Power Distribution Line, B/150

  3006                 Power Distribution Line, B/150

  3007                 Potable Water Main, B/150

  3008                 Fire Protection Water Main, B/150

  3009                 Gas Storage & Transfer Area

  3010                 Concrete Apron & Ramp Paving

  3011                 Parking Area

  3012                 Roadway Facilities

  3013                 Land Preparation

  3014                 Exterior Lighting

  3015                 Fence

  3016                 Water System

  3017                 Fire Protection System

  3018                 Gas System

  3019                 Sewer System

  3020                 Drainage System

  3021                 RSI Bonding Shop Within B/150

  3022                 Electrical & Phone Svc Line B/743

  3023                 Exten. Of Utilities, B/163,164 & 165

  3024                 Land Preparation

  3025                 Asphalt Paving Yards

  3026                 Fence

  3027                 Fire Protection

  3028                 Sewer System-Sanitary Svc Extension

  3029                 Water System

  3030                 Wash Rack

  3031                 Electrical Distribution

  3032                 Fire Alarm Autocall Extension

  3033                 Telephone Utility Extension

  3034                 Utilities-Computer System

  3035                 Storage Yard Concrete Paving

  3036                 Gas Fueling System

  3038                 Loading Dock & Levellor

  3039                 Concrete Paving (513 Storage Area)

  3040                 Parking Lot North

  3041                 Landscaped Area

  3153                 Thermal Protection Building

  3154                 Modular Office Unit

  3158                 Storage Canopy

  3163                 Modular Office Unit

  3164                 Modular Office

  3165                 Modular Office Unit

  3171                 Modular Office Unit

  3172                 Modular Office Unit

  3173                 Modular Office Unit

  3181                 Canopy

  3183                 Operation Shed

  3187                 Hazardous Storage Canopy

  3188                 Hazardous Storage Canopy

  3191                 Electrical Substation Building

  3193                 Storage Canopy

  3197                 Guard House

  3198                 Modular Office
  -------------------- -------------------------------------------------------------

**PART J-9-A-6**

[]{#a6 .anchor}**JOHNSON SPACE CENTER**

**GOVERNMENT FURNISHED DATA**

The following Government‑Furnished Data (GFD) will be furnished to the
contractor for the performance of work under this contract:

-   Real-time air‑to-ground and Flight Director's voice communications
    and real-time Orbiter Flight data.

-   Copies of the PASS l‑Loads used by BFS software (via
    computer‑readable media as defined in SS-P-0002.195).

-   Data supporting verification of the mission capability of the
    Shuttle vehicle with standard payload interfaces, and with selected
    unique payloads and payload interfaces.

-   Shuttle Program Milestone Schedules.

-   Flight Data.

-   Launch Data.

**PART J-9-A-7**

[]{#a7 .anchor}**JOHNSON SPACE CENTER**

**LIST OF INSTALLATION-PROVIDED PROPERTY**

**1. [General]{.underline}**

a.  The contractor is authorized use of the types of
    installation-provided property listed below, to the extent they are
    available, at the Johnson Space Center (JSC).

b.  As used herein, "onsite" means within the physical boundaries of
    JSC, the area it occupies and uses at Ellington Field, and buildings
    which JSC directly leases near its physical site; "offsite" refers
    to contractor facilities (leased or owned) in the Houston, Texas,
    area (Harris and Galveston Counties).

c.  The contractor shall not bring onsite for use under this contract
    any property that is owned or leased by the contractor, or other
    property that the contractor is accountable for under any other
    government contract, without the prior written approval of the JSC
    Supply and Equipment Management Officer (SEMO) and the Contracting
    Officer.

d.  If the contractor requests property which is not available or cannot
    be made available from the government to meet the contractor's
    schedule needs, the requesting document will be canceled and
    returned to the contractor. The contractor will thereafter be
    responsible for acquiring the needed items or services.

e.  If the contractor initiates a transfer of accountability (DD
    Form 1149) from the contractor to the government, the contractor
    shall continue to account for the property in question until
    contractor receives notification that the form has been signed by
    the JSC Supply and Equipment Management Officer (SEMO) or his/her
    authorized representative. If the contractor does not receive such
    notice in a reasonable time, contractor will make inquiry through
    the Property Administrator as to the status of the transfer.

**2. [Property Which May Be Furnished]{.underline}**

a.  Equipment to be made available at the Johnson Space Center to the
    contractor for use in performance of this contract is listed in
    attachment J-9-A.

b.  Supplies, office furniture, gasses, and hazardous materials at the
    Johnson Space Center or available from other Federal depots (onsite
    only).

c.  Publications and blank forms stocked by the installation (onsite and
    offsite).

**3. [Contractor Responsibilities]{.underline}**

The responsibilities of the contractor as contemplated by paragraph (a)
of the Installation-Accountable Government Property clause are defined
in the following:

NFS 1852.245-71, Installation-Accountable Government Property (NOV 2004)
-- Alternate 1 (NOV 2004)

**PART J-9-B-1**

[]{#b1 .anchor}**KENNEDY SPACE CENTER**

**GOVERNMENT FURNISHED EQUIPMENT**

The GFE furnished to the contractor for the performance of work under
this contract is transitioned from NAS9-20000 and is listed in technical
report TR-1287. This data is provided on CD-ROM SPOC-1.

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   KSC use NEMS (NASA System) and CARS (USA System) for the tracking of
    Equipment

    **PART J-9-B-2**

    []{#b2 .anchor}**KENNEDY SPACE CENTER**

    **GOVERNMENT FURNISHED SPECIAL TOOLING & TEST EQUIPMENT**

The contractor will be furnished (transitioned at inception from
NAS9-20000) the items listed from technical report TR-1287, designated
LSOC, and Rockwell Report TR-1287 listed items which will be furnished
to the contractor include the Launch Processing System (LPS) and the
Shuttle Data Management System (SPDMS).

This data is provided on CD-ROM No. KSC-3.

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   KSC use NEMS (NASA System) and CARS (USA System) for the tracking of
    Equipment

    **PART J-9-B-3**

    []{#b3 .anchor}**KENNEDY SPACE CENTER**

    **GOVERNMENT FURNISHED MATERIALS**

The following GFM will be provided to the contractor as required, and in
the quantities required.

[PRESSURANTS/PROPELLANTS]{.underline}

Air, Breathing (Bair)

Air, Liquid (Lair)

Ammonia (NH3)

Argon, Liquid (Largon)

Detonators

Halon 1301 (Fire Suppression)

HCFC-225G (AK-225G)

Helium, Gaseous (GHe)

Helium, High Purity

Helium, Liquid (LHe)

HFE-7100

Hydrazine, Monomethyl (MMH)

Hydrazine, Mono-propellant (MPH)

Hydrogen Peroxide (H2O2)

Hydrogen, Gaseous (GH2)

Hydrogen, Liquid (LH2)

Initiators, Standard, Type 1

Jet Propellant-8 (JP-8)

Nitrogen Tetroxide (N204 MON3)

Nitrogen, Gaseous (GN2)

Nitrogen, Liquid (LN2)

Oxygen, Gaseous (GO2)

Oxygen, Gaseous, Breathing

Oxygen, High Purity Gaseous (GO~2~HP)

Oxygen, High Purity Liquid (LO2 HP)

Oxygen, Liquid (LO2)

Dichlorofluoromethane \[Refrigerant-21 (R-21)\]

Shuttle Hydraulic Fluid (Mil-PRF-83282D)

Sodium Hydroxide (NaOH)

Trichlorotrifluoroethane, [TF Type 2/PCA Solvent Type 1]{.underline} 113

Vertrel MCA

Vertrel DCE Recharge Kit

The contractor shall be responsible for the replenishment of all other
materials furnished and/or required under the SPOC NNJ06VA01C.

KSC uses Peoplesoft Inventory Module (USA System), IPCS (NASA System),
CSLIMS, CARS and MACPAC for the tracking of Material.

**PART J-9-B-4**

[]{#b4 .anchor}**KENNEDY SPACE CENTER**

**GOVERNMENT FURNISHED SOFTWARE**

The following in-house developed and commercial computer operating and
applications software will be provided to the contractor for use in the
performance of the SPOC contract.

-   LPS Program, Applications, Systems and Control Logic Software

-   Lockheed Software Development Network (LSDN)

-   Shuttle Electronic Tie-In (SETI)

-   Shuttle Processing Data Management Software (SPDMS)

Additional information provided on CD-ROM No. KSC-1, KSC Software.

**PART J-9-B-5**

[]{#b5 .anchor}**KENNEDY SPACE CENTER**

**GOVERNMENT FURNISHED FACILITIES**

The following facilities at KSC, CCAFS, and Contingency Landing Sites
(CLS) will be furnished to the contractor for use in performance of the
SPOC Contract. The contractor\'s responsibilities for maintenance and
sustaining engineering on facility systems at KSC and CCAFS are limited
to the specific systems listed under the facility number and name. The
following listing is current as of the inception date of the contract.
The current listing of responsibilities for facilities is found in the
**KSC OMEU matrix**. In addition to the following lists, the contractor
shall also be responsible for the crawlerway maintenance and the
dredging for the channels and turn basins in the Banana River required
for ET barge and SRB retrieval operations.

**PART 1**

+----+---------+-----------------------------------------------+-----+
| ** | ***FA   | ***FACILITY NAME***                           | *** |
| *I | CILITY\ |                                               | Use |
| TE | NU      | ***O- Operator M- Maintainer E- Sustain Engr  | r/\ |
| M* | MBER*** | U- User***                                    | M   |
| ** |         |                                               | ain |
|    |         |                                               | t/\ |
|    |         |                                               | Su  |
|    |         |                                               | st. |
|    |         |                                               | *** |
+====+=========+===============================================+=====+
|    |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
|    |         | **All SRB RELATED FACILITIES HAVE MOVED TO    |     |
|    |         | ITEM #274**                                   |     |
+----+---------+-----------------------------------------------+-----+
| 1. | H5-2274 | MICROWAVE SCAN BEAM L/S (MSBLS) R/W 33        | U   |
|    |         |                                               |     |
|    |         | \- STRUCTURE                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2. | H5-2324 | MSBLS MONITOR R/W 33 NORTH                    | U   |
|    |         |                                               |     |
|    |         | \- STRUCTURE - Low Voltage AC Power           | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 3. | J5-0386 | SLF OPTICAL TRACKER SITE A                    | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 4. | J5-0441 | TACAN SITE                                    | O   |
|    |         |                                               | MEU |
|    |         | \- Tacan System                               |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage                                | MEU |
|    |         |                                               |     |
|    |         | \- Generator (Fixed)                          | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 5. | J5-0533 | MSBLS MONITOR R/W 15 NORTH                    | O   |
|    |         |                                               | MEU |
|    |         | \- Microwave Scanning Beam Landing System     |     |
|    |         | (MSBLS) Monitor R/W                           | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 6. | J5-0583 | MSBLS ELEVATION R/W 15 STATION                | O   |
|    |         |                                               | MEU |
|    |         | \- Microwave Scanning Beam Landing System     |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 7. | J5-0583 | MSBLS ELEVATION R/W 15 STATION                | O   |
|    |         |                                               | MEU |
|    |         | \- Microwave Scanning Beam Landing System     |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 8. | J5-0677 | TV TOWER NO.2                                 | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | OME |
|    |         | \- Hoist                                      |     |
|    |         |                                               | O   |
|    |         | \- Complex Control System                     | MEU |
+----+---------+-----------------------------------------------+-----+
| 9. | J5-2000 | MSBLS ELEVATION R/W 33 STATION                | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 10 | J5-2050 | MSBLS MONITOR R/W 33 SOUTH                    | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 11 | J6-0490 | EQUIPMENT BUILDING (500 FT. WEATHER TOWER)    | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage Power                          |     |
+----+---------+-----------------------------------------------+-----+
| 12 | J       | EQUIPMENT BUILDING (500 FT. WEATHER TOWER)    | O   |
| .  | 6-0490A |                                               | MEU |
|    |         | \- Low Voltage Power                          |     |
|    |         |                                               | O   |
|    |         | \- Fixed Generator                            | MEU |
|    |         |                                               |     |
|    |         | \- Elevator                                   | O   |
|    |         |                                               | MEU |
|    |         | \- Crane/Hoist                                |     |
|    |         |                                               | O   |
|    |         | \- Tower                                      | MEU |
|    |         |                                               |     |
|    |         | \- Lights                                     | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 13 | J       | EQUIPMENT BUILDING (60 FT WEATHER TOWER 313B  | O   |
| .  | 6-0490B |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 14 | J6-1808 | TV TOWER UNIT NO.1                            | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage Electrical                     |     |
|    |         |                                               | OME |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Crane/Hoist                                | MEU |
+----+---------+-----------------------------------------------+-----+
| 15 | J6-2262 | ORBITER MATE/DEMATE DEVICE                    | O   |
| .  |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage Power                          | MEU |
|    |         |                                               |     |
|    |         | \- Hoist                                      | O   |
|    |         |                                               | MEU |
|    |         | \- Grounding                                  |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 16 | J6-2327 | CLAMSHELL #4                                  | O   |
| .  |         |                                               | MEU |
|    |         | > \- Low Voltage AC Power                     |     |
|    |         | >                                             | O   |
|    |         | > \- Structure                                | MEU |
+----+---------+-----------------------------------------------+-----+
| 17 | J6-2364 | MSBLS-JR CERTIFICATION FACILITY               | O   |
| .  |         |                                               | MEU |
|    |         | \- Microwave Scanning Beam Landing System JR  |     |
|    |         | Antenna                                       |     |
+----+---------+-----------------------------------------------+-----+
| 18 | J6-2365 | MSBLS STORAGE BUILDING                        | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
|    |         |                                               |     |
|    |         | \- STRUCTURE                                  | E   |
+----+---------+-----------------------------------------------+-----+
| 19 | J6-2377 | CONTRACTOR SUPPORT BUILDING NO.7              | U   |
| .  |         |                                               |     |
|    |         | \- Low Voltage Power                          | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 20 | J6-2428 | COMMUNICATIONS CROSS CONNECT TERMINAL         | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 21 | J7-0132 | OPERATIONS SUPPORT BUILDING B-1               | O   |
| .  |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 22 | J       | LOX OFFICE BUILDING                           | O   |
| .  | 7-0132A |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 23 | J7-0140 | HIGH PRESSURE GH2 FACILITY                    | U   |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 24 | J7-0182 | LOX FACILITY                                  | U   |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 25 | J7-0183 | CAMERA PAD NO.6                               | U   |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 26 | J7-0191 | CAMERA PAD NO.1                               | U   |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 27 | J7-0192 | LIQUID HYDROGEN (LH2) FACILITY                | U   |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 28 | J7-0231 | ELECTRICAL EQUIPMENT BLDG. NO.2 (LOX)         | O   |
| .  |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 29 | J7-0240 | FLARESTACK                                    | O   |
| .  |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 30 | J7-0241 | ELECTRICAL EQUIPMENT BLDG NO.1 (RP-1)         | O   |
| .  |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 31 | J7-0243 | OPERATIONS SUPPORT BUILDING B-2               | O   |
| .  |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 32 | J       | TEMP. BLDG. NO. 35 (TR1-689 AND 690)          | O   |
| .  | 7-0243A |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 33 | J7-0286 | ENVIRONMENTAL CONTROL & LIFE SUPPORT SYSTEM   | O   |
| .  |         | BLDG.(ECLSS)                                  | MEU |
+----+---------+-----------------------------------------------+-----+
| 34 | J7-0288 | WATER TANK                                    | O   |
| .  |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | O   |
|    |         | \- Lights                                     | MEU |
+----+---------+-----------------------------------------------+-----+
| 35 | J7-0337 | LAUNCH PAD 39BReference TR-1287 (OMEU) for    |     |
| .  |         | identification of systems and equipment.      |     |
+----+---------+-----------------------------------------------+-----+
| 36 | J       | TEMP. BLDG. NO. 30 (TR1-644 THRU 658)         |     |
| .  | 7-0337A | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 37 | J       | TEMP. BLDG. NO. 31 (TR1-659 THRU 673)         |     |
| .  | 7-0337B | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 38 | J       | TEMP. BLDG. NO. 32 (TR1-674 THRU 680)         |     |
| .  | 7-0337C | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 39 | J       | TEMP. BLDG. NO. 33 (TR1-681 THRU 686          |     |
| .  | 7-0337D | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 40 | J       | TEMP. BLDG. NO. 34 (TR1-511, 687 AND 688)     |     |
| .  | 7-0337E | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 41 | J       | TEMP. BLDG. NO. 37 Reference TR-1287 (OMEU)   |     |
| .  | 7-0337F | for identification of systems and equipment.  |     |
+----+---------+-----------------------------------------------+-----+
| 42 | J       | TEMP. BLDG. NO. 68 (TR1-499, 502, 503 AND     |     |
| .  | 7-0337H | 505-509)                                      |     |
|    |         |                                               |     |
|    |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 43 | J       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| .  | 7-0337I |                                               |     |
|    |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 44 | J       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| .  | 7-0337J | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 45 | J7-0338 | COMPRESSED AIR BUILDING                       | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation/Sewer                           |     |
+----+---------+-----------------------------------------------+-----+
| 46 | J7-0342 | CAMERA NO.2 PAD B                             | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 47 | J7-0385 | WATER CHILLER BUILDING                        | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 48 | J7-0432 | REMOTE AIR INTAKE BUILDING                    | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 49 | J7-0490 | HYPERGOL OXIDIZER FACILITY                    | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 50 | J7-0491 | ELECTRIC EQUIPMENT BLDG NO.3 (OXIDIZER)       | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 51 | J7-0535 | ELECTRIC EQUIPMENT BUILDING NO.4 (FUEL)       | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 52 | J7-0584 | CAMERA PAD NO.4                               | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 53 | J7-0588 | COMMUNICATIONS BUILDING                       | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 54 | J7-0688 | OPERATIONS BUILDING NO.1                      | U   |
| .  |         |                                               |     |
|    |         | Low Voltage Power                             | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Structure                                  | MEU |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewer                         | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 55 | J7-0986 | REPEATER BUILDING NO.6                        | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage Power                          |     |
|    |         |                                               | OME |
|    |         | > \- HVAC                                     |     |
|    |         | >                                             | U   |
|    |         | > \- Grounding                                |     |
|    |         | >                                             | U   |
|    |         | > \- Structure                                |     |
|    |         | >                                             | U   |
|    |         | > \- Lightning Protection                     |     |
+----+---------+-----------------------------------------------+-----+
| 56 | J7-1338 | SCAPE BUILDING                                | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 57 | J7-1387 | GROUND WATER STORAGE TANK                     | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Cathodic Protection                        | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | O   |
|    |         | \- Firex Piping                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 58 | J7-1388 | INDUSTRIAL WATER PUMPING STATION              | U   |
| .  |         |                                               |     |
|    |         | \- Cranes (fixed)                             | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage Electrical                     | MEU |
|    |         |                                               |     |
|    |         | \- Power, UPS 3 KW                            | O   |
|    |         |                                               | MEU |
|    |         | \- Compressed Air                             |     |
|    |         |                                               | O   |
|    |         | \- Water Pump Station                         | MEU |
|    |         |                                               |     |
|    |         | \- Firex                                      | O   |
|    |         |                                               | MEU |
|    |         | > \- Cross Country Lines                      |     |
|    |         | >                                             | O   |
|    |         | > \- Electrical Control System                | MEU |
|    |         | >                                             |     |
|    |         | > \- Jockey Pump/Motors                       | O   |
|    |         | >                                             | MEU |
|    |         | > \- Pump Station                             |     |
|    |         |                                               | O   |
|    |         | \- Diesel Engine                              | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 59 | J7-1389 | GROUND WATER STORATE TANK                     | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Grounding                                  | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Firex                                      |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 60 | J7-1736 | REPEATER BUILDING NO.5                        | OME |
| .  |         |                                               |     |
|    |         | \- HVAC                                       | OME |
|    |         |                                               |     |
|    |         | \- Low Voltage Electrical                     | U   |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 61 | J7-2162 | UNIVERSAL CAMERA PAD #17                      | OME |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 62 | J8-1462 | HIGH PRESSURE GH2 FACILITY                    | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  | OMU |
|    |         |                                               |     |
|    |         | \- KCCS                                       |     |
+----+---------+-----------------------------------------------+-----+
| 63 | J8-1502 | LOX FACILITY                                  | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 64 | J8-1503 | OPERATIONS SUPPORT BUILDING A-1               | O   |
| .  |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 65 | # J     | LOX ENGINEERING OFFICE BLDG                   | O   |
| .  | 8-1503B |                                               | MEU |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 66 | J8-1512 | CAMERA PAD NO.1                               | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage Electrical Power               |     |
+----+---------+-----------------------------------------------+-----+
| 67 | J8-1553 | ELECTRICAL EQUIPMENT BLDG. NO.2 (LOX)         | U   |
| .  |         |                                               |     |
|    |         | \- KCCS                                       | OMU |
|    |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 68 | J8-1554 | CAMERA PAD NO.6                               | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 69 | J8-1563 | ELECTRICAL EQUIPMENT BLDG NO.1 (RP-1)         | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 70 | J8-1567 | CABLE TERMINAL BUILDING                       | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage Power                          |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 71 | J8-1610 | WATER TANK                                    | O   |
| .  |         |                                               | MEU |
|    |         | \- Lights                                     |     |
|    |         |                                               | O   |
|    |         | \- Structure                                  | MEU |
+----+---------+-----------------------------------------------+-----+
| 72 | J8-1611 | FLARESTACK                                    | O   |
| .  |         |                                               | MEU |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 73 | J8-1614 | OPERATIONS SUPPORT BUILDING A-2               | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 74 | J       | LH2 ENGINEERING OFFICE BLDG                   | O   |
| .  | 8-1614A |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 75 | J8-1707 | WATER CHILLER BUILDING                        | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
+----+---------+-----------------------------------------------+-----+
| 76 | J8-1708 | LAUNCH PAD 39A                                |     |
| .  |         |                                               |     |
|    |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 77 | J       | TEMP. BLDG. NO. 1 (TR1-377 THRU 395)          | U   |
| .  | 8-1708A |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 78 | J       | TEMP. BLDG. NO. 2 (TR1-396 THRU 407)          | U   |
| .  | 8-1708B |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 79 | J       | TEMP. BLDG. NO. 3 (TR1-459 THRU 468)          | U   |
| .  | 8-1708C |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 80 | J       | TEMP. BLDG. NO. 4 (TR1-411 THRU 414)          | U   |
| .  | 8-1708D |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 81 | J       | TEMP. BLDG. NO. 5 (TR1-409 AND 410)           | U   |
| .  | 8-1708E |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 82 | J       | TEMP. BLDG. NO. 6 (TR1-561 AND 562)           | U   |
| .  | 8-1708F |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 83 | J       | TEMP. BLDG. NO. 7 (TR1-563 AND 564)           | U   |
| .  | 8-1708G |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 84 | J       | TEMP. BLDG. NO. 69 (TR1-492 THRU 498, 500, &  | U   |
| .  | 8-1708I | 504)                                          |     |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 85 | J8-1753 | REMOTE AIR INTAKE BUILDING                    | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 86 | J8-1768 | ENVIRONMENTAL CONTROL & LIFE SUPPORT SYSTEM   | O   |
| .  |         | BUILDING(ECLSS)                               | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 87 | J8-1811 | ELECT. EQUIPMENT BLDG NO.3 (OXIDIZER)         | O   |
| .  |         |                                               | MEU |
|    |         | \- Structure (U)                              |     |
|    |         |                                               |     |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 88 | J8-1856 | ELECTRICAL EQUIPMENT BLDG NO.4 (FUEL)         | U   |
| .  |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 89 | J8-1862 | HYPERGOL OXIDIZER FACILITY                    | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 90 | J8-1906 | HYPERGOL FUEL FACILITY                        | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 91 | J8-1961 | CAMERA PAD NO.3                               | U   |
| .  |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 92 | J8-2009 | OPERATIONS BUILDING NO.1                      | U   |
| .  |         |                                               |     |
|    |         | Low Voltage AC Power                          | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Structure                                  | MEU |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewer                         | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 93 | J8-2109 | PAD A OPERATIONS SUPPORT BUILDING             | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 94 | J8-2204 | REPEATER BUILDING NO.4                        | OME |
| .  |         |                                               |     |
|    |         | \- HVAC                                       | OME |
|    |         |                                               |     |
|    |         | \- Low Voltage AC Power                       | U   |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Lightning Protection                       | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 95 | K6-0258 | MSBLS MONITOR R/W 15                          | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power (LV Interface at      |     |
|    |         | 120/208 Volt Bushing Terminals of the         |     |
|    |         | Facility Transformer)                         |     |
+----+---------+-----------------------------------------------+-----+
| 96 | K6-0309 | MSBLS AZ/DME R/W 15                           | O   |
| .  |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power (LV Interface at      | MEU |
|    |         | 120/208 Volt Bushing Terminals of the         |     |
|    |         | Facility Transformer)                         |     |
+----+---------+-----------------------------------------------+-----+
| 97 | K6-0345 | SURGE BUILDING NO.2                           | O   |
| .  |         |                                               | MEU |
|    |         | #2 HB Rollup Door #2 LB Rollup Door Structure |     |
|    |         | Sanitation / Sewage Potable Water ESS         | O   |
|    |         |                                               | MEU |
|    |         | \- Lightning Protection                       |     |
|    |         |                                               | U   |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 98 | K6-0445 | CONTRACTOR SUPPORT BUILDING NO.4              | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Lightning Protection                       |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | #   |
|    |         | \- Sanitation / Sewage                        | # U |
+----+---------+-----------------------------------------------+-----+
| 99 | K6-0446 | SHOP/STORAGE BUILDING                         | O   |
| .  |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0494 | ROTATION/PROCESSING BUILDING                  |     |
| 00 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.-Compressed Air      |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0495 | ROTATION/PROCESSING SUPPORT BUILDING          | U   |
| 01 |         |                                               |     |
| .  |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         | \- Fire Sprinkler                             |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0497 | SURGE BUILDING NO.1                           | O   |
| 02 |         |                                               | MEU |
| .  |         | \- Powered Doors                              |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0545 | GENERAL WAREHOUSE                             | O   |
| 03 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0546 | MLP REFURBISHMENT AREA                        | U   |
| 04 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Firex                                      | MEU |
|    |         |                                               |     |
|    |         | \- Pneumatics                                 | O   |
|    |         |                                               | MEU |
|    |         | \- MLP Mount Mechanisms                       |     |
|    |         |                                               | O   |
|    |         | \- Compressed Air                             | MEU |
|    |         |                                               |     |
|    |         | \- Facility Cable                             | O   |
|    |         |                                               | MEU |
|    |         | \- GN2 Interconnect System                    |     |
|    |         |                                               | O   |
|    |         | \- GHE Electrical Dist/Cabling System         | MEU |
|    |         |                                               |     |
|    |         | \- Towers                                     | O   |
|    |         |                                               | MEU |
|    |         | \- Safewaste                                  |     |
|    |         |                                               | O   |
|    |         | \- Potable Water                              | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0696 | ORBITER PROCESSING FACILITY HIGH BAY 3        |     |
| 05 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 06 | 6-0696C |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | ENVIRONMENTAL CONTROL BUILDING                |     |
| 07 | 6-0696D |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0742 | HAZARDOUS WASTE STAGING SHELTER               | O   |
| 08 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0743 | CRAWLER TRANSPORTER MAINTENANCE BLDG.         | O   |
| 09 |         |                                               | MEU |
| .  |         | \- Low Voltage Power                          |     |
|    |         |                                               | OME |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Powered Doors                              | MEU |
|    |         |                                               |     |
|    |         | > \- Compressed Air                           | O   |
|    |         | >                                             | MEU |
|    |         | > \- Structure                                |     |
|    |         | >                                             | U   |
|    |         | > \- Sanitation / Sewage                      |     |
|    |         | >                                             | U   |
|    |         | > \- Potable Water                            |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 10 | 6-0743A |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 11 | 6-0743B |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 12 | 6-0743C |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0793 | CRAWLER TRANSPORTER SERVICE BUILDING          | U   |
| 13 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-794  | THERMAL PROTECTION SYSTEM FACILITY            |     |
| 14 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | POL                                           | U   |
| 15 | 6-0794A |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-794B | POL                                           | U   |
| 16 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0844 | ECLSS/HYDRAULICS GSE SUPPORT BUILDING         | U   |
| 17 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0848 | VEHICLE ASSEMBLY BUILDING                     |     |
| 18 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0894 | ORBITER PROCESSING FACILITY ( High Bays 1 &   |     |
| 19 |         | 2)                                            |     |
| .  |         |                                               |     |
|    |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | ENVIRONMENTAL CONTROL SYSTEM BLDG (E)         | U   |
| 20 | 6-0894A |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | ENVIRONMENTAL CONTROL SYSTEM BLDG (W)         | U   |
| 21 | 6-0894B |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | OPF/GSE STORAGE BUILDING                      | U   |
| 22 | 6-0894D |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-894E | GATE HOUSE (OPF)                              | U   |
| 23 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 24 | 6-0894F |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 25 | 6-0894G |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0895 | PUMPHOUSE (OPF)                               | O   |
| 26 |         |                                               | MEU |
| .  |         | \- Firex System: (OPF Pump House K-895)       |     |
|    |         |                                               | O   |
|    |         | Includes:                                     | MEU |
|    |         |                                               |     |
|    |         | \- Three- 750 HP/3780 GPM Diesel Driven Pumps | O   |
|    |         |                                               | MEU |
|    |         | \- Compressed Air System                      |     |
|    |         |                                               | O   |
|    |         | \- Diesel Engine                              | MEU |
|    |         |                                               |     |
|    |         | \- Control System                             | O   |
|    |         |                                               | MEU |
|    |         | \- Jockey Pump                                |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- Hoist                                      | O   |
|    |         |                                               | MEU |
|    |         | \- Fiber Optic                                |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Fire Sprinkler                             |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0900 | LAUNCH CONTROL CENTER                         | U   |
| 27 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | BATTERY ROOM BUILDING                         | O   |
| 28 | 6-0900A |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | OME |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Breakout Box                               | MEU |
|    |         |                                               |     |
|    |         | \- Battery Maintenance Test Station           | O   |
|    |         |                                               | MEU |
|    |         | \- Battery Checkout Rack                      |     |
|    |         |                                               | O   |
|    |         | \- Auto. Checkout Equipment                   | MEU |
|    |         |                                               |     |
|    |         | \- Battery Activation & Checkout Lab          | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0943 | HAZARDOUS WASTE STAGING SHELTER               | O   |
| 29 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0946 | GROUND WATER STORAGE TANK                     | O   |
| 30 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Grounding                                  | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Firex                                      |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0947 | UTILITY ANNEX                                 | O   |
| 31 |         |                                               | MEU |
| .  |         | \- Firex                                      |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0995 | GROUND STORAGE RESERVOIR                      | O   |
| 32 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Cathodic Protection                        | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | O   |
|    |         | \- Firex                                      | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0996 | PAINT OIL STORAGE                             | OME |
| 33 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | > \- Crane/Hoist ( 1-Ton)                     | MEU |
|    |         | >                                             |     |
|    |         | > \- Fire Sprinkler                           | U   |
|    |         | >                                             |     |
|    |         | > \- Tank                                     | U   |
|    |         | >                                             |     |
|    |         | > \- Structure                                | U   |
|    |         | >                                             |     |
|    |         | > \- Sanitation / Sewage                      | U   |
|    |         | >                                             |     |
|    |         | > \- Potable Water                            | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-0998 | HAZARDOUS WASTE STAGING BUILDING              | U   |
| 34 |         |                                               |     |
| .  |         | \- Lightning Protection Structure Sanitation  | U   |
|    |         | / Sewage                                      |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1046 | STORAGE BUILDING                              | O   |
| 35 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1094 | PROCESSING CONTROL CENTER                     | OME |
| 36 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Uninterruptable Power System               | MEU |
|    |         |                                               |     |
|    |         | \- Compressed Air System                      | O   |
|    |         |                                               | MEU |
|    |         | \- Elevators                                  |     |
|    |         |                                               | OME |
|    |         | \- Complex Control System                     |     |
|    |         |                                               | O   |
|    |         | \- Grounding                                  | MEU |
|    |         |                                               |     |
|    |         | \- ESS                                        | U   |
|    |         |                                               |     |
|    |         | \- Lightning Protection                       | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1096 | OPERATIONS SUPPORT BUILDING                   | OME |
| 37 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | OME |
|    |         | \- Elevators                                  |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Lightning Protection                       |     |
|    |         |                                               | U   |
|    |         | \- Power UPS                                  |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1193 | REPEATER BUILDING                             | OME |
| 38 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | OME |
|    |         | \- Complex Control System                     |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | O   |
|    |         | \- Emergency Power                            | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Fire Sprinkler                             | U   |
|    |         |                                               |     |
|    |         | \- CCS                                        | OME |
|    |         |                                               |     |
|    |         | \- KCCS                                       | OMU |
|    |         |                                               |     |
|    |         | \- Power                                      | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | VAB MODULAR OFFICE BUILDING                   | U   |
| 39 | 6-1200C |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | VAB MODULAR OFFICE BUILDING                   | OME |
| 40 | 6-1200G |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | VAB MODULAR OFFICE BUILDING                   | OME |
| 41 | 6-1200H |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewer                         |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | VAB MODULAR OFFICE BUILDING                   | OME |
| 42 | 6-1200I |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | TEMP. BLDG. NO. 13 (TR1-512 THRU 531)         | OME |
| 43 | 6-1200J |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1247 | LAUNCH EQUIPMENT SHOP                         | OME |
| 44 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power -- Trailer Park       | MEU |
|    |         |                                               |     |
|    |         | \- Compressed Air                             | O   |
|    |         |                                               | MEU |
|    |         | \- Cranes/Hoists                              |     |
|    |         |                                               | O   |
|    |         | \- Equipment -- Misc.                         | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Power Door                                 |     |
|    |         |                                               | U   |
|    |         | \- Standpipes                                 |     |
|    |         |                                               | O   |
|    |         | \- Storage Carousal                           | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | O   |
|    |         |                                               | MEU |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1298 | MISSION SUPPORT BUILDING                      | OME |
| 45 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power -- Trailer Park       | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1346 | PNEUMATICS SHOP                               | O   |
| 46 |         |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- Crane/Hoists                               | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1347 | HAZARDOUS WASTE STAGING SHELTER               | O   |
| 47 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Lightning Protection                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1396 | HAZARDOUS WASTE STAGING SHELTER               | U   |
| 48 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Lightning Protection                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1397 | PAINT SHOP                                    | O   |
| 49 |         |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1449 | GENERAL WAREHOUSE                             | O   |
| 50 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1547 | LOGISTICS FACILITY                            |     |
| 51 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.For Buildings        |     |
|    |         | K6-1547A thru K6-1547H SFOC will have         |     |
|    |         | responsibility for the systems within (e.g.,  |     |
|    |         | HVAC and electric)                            |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | POL                                           | U   |
| 52 | 6-1547A |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | BARREL SHED                                   | U   |
| 53 | 6-1547B |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | SUPPORT BUILDING                              | U   |
| 54 | 6-1547C |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | CABLE REEL SHED                               | U   |
| 55 | 6-1547D |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | EXPLOSIVES STAGING SHED                       | U   |
| 56 | 6-1547E |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | LOADING DOCK                                  | U   |
| 57 | 6-1547F |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | STORAGE SHED                                  | U   |
| 58 | 6-1547G |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | ENVIRONMENTAL SHELTER                         | U   |
| 59 | 6-1547H |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1696 | COMPONENT REFURB. AND CHEMICAL ANALYSIS       |     |
| 60 |         | FACILITY                                      |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1745 | COMMUNICATIONS CROSS CONNECT TERMINAL         | OME |
| 61 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | OME |
|    |         |                                               |     |
|    |         | \- HVAC                                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1747 | HYPERGOL DECONTAMINATION BLDG                 | O   |
| 62 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1748 | DRY CHEMICAL STORAGE BLDG                     | O   |
| 63 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Hoist                                      | MEU |
|    |         |                                               |     |
|    |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STORAGE BLDG                  | O   |
| 64 | 6-1748A |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1847 | GENERATOR MAINTENANCE SHOP                    | O   |
| 65 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
|    |         |                                               |     |
|    |         | \- Rollup Door                                | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | GENERATOR OFFICE                              | O   |
| 66 | 6-1847A |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | GENERATOR CHECKOUT SHED                       | O   |
| 67 | 6-1847B |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | GENERATOR STORAGE SHED                        | O   |
| 68 | 6-1847C |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1896 | CONT. SUPPORT BLDG #8                         | U   |
| 69 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1995 | HEAVY EQUIPMENT MAINTENANCE SHOP              | U   |
| 70 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Grounding                                  | MEU |
|    |         |                                               |     |
|    |         | \- Lightning Protection                       | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-1996 | ELECTRONICS/HEAVY EQUIPMENT SHOP              | U   |
| 71 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Hoists                                     | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Tensile Testing Machine                    |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | CARPENTRY AND STORAGE FACILITY                | O   |
| 72 | 6-1996D |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STORAGE                       | O   |
| 73 | 6-1996F |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | ASBESTOS CONTAINMENT BUILDING                 | O   |
| 74 | 6-1996G |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HEAVY EQUIPMENT OFFICE BUILDING               | U   |
| 75 | 6-1996H |                                               |     |
| .  |         | \- Low Voltage Electrical Power               | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | O   |
|    |         | \- Sanitation / Sewage                        | MEU |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Lift Station                               | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-2044 | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | O   |
| 76 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-2045 | HIGH CREW STORAGE BUILDING                    | U   |
| 77 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Power Roll Up Doors                        | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Lift Station                               |     |
|    |         |                                               | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K6-2095 | HAZARDOUS WASTE STAGING BUILDING/PORTABLE     | U   |
| 78 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- Grounding                                  |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0089 | REPEATER BUILDING NO.3                        | O   |
| 79 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | OME |
|    |         | \- HVAC                                       |     |
|    |         |                                               | U   |
|    |         | \- Lightning Protection                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0187 | MSS PARKSITE ELECT. INTERFACE BLDG.           | U   |
| 80 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | OME |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0188 | MOBILE SERVICE STRUCTURE PARK SITE            | U   |
| 81 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | PUMP HOUSE                                    | U   |
| 82 | 7-0188A |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0255 | MAGAZINE NO. 1 (ORDNANCE STORAGE)             | U   |
| 83 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- Cranes                                     |     |
|    |         |                                               | O   |
|    |         | \- Lightning Protection                       | MEU |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0306 | MAGAZINE NO.2 (ORDNANCE STORAGE)              | U   |
| 84 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | > \- Cranes                                   |     |
|    |         | >                                             | O   |
|    |         | > \- Fire Alarm                               | MEU |
|    |         | >                                             |     |
|    |         | > \- Lightning Protection                     | U   |
|    |         | >                                             |     |
|    |         | > \- Structure                                | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0356 | MAGAZINE NO.3 (ORDNANCE STORAGE)              | U   |
| 85 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | > \- Cranes                                   |     |
|    |         | >                                             | O   |
|    |         | > \- Lightning Protection                     | MEU |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0367 | AMMONIA BOILER REFURBISHMENT FACILITY         | U   |
| 86 |         |                                               |     |
| .  |         | > \- Low Voltage AC Power                     | O   |
|    |         | >                                             | MEU |
|    |         | > \- Grounding                                |     |
|    |         | >                                             | U   |
|    |         | > \- Lightning Protection                     |     |
|    |         | >                                             | U   |
|    |         | > \- Structure                                |     |
|    |         | >                                             | U   |
|    |         | > \- Potable Water                            |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0405 | MAGAZINE NO. 4(ORDNANCE STORAGE)              | U   |
| 87 |         |                                               |     |
| .  |         | > \- Low Voltage AC Power                     | O   |
|    |         | >                                             | MEU |
|    |         | > \- Fire Alarm                               |     |
|    |         | >                                             | U   |
|    |         | > \- Lightning Protection                     |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0417 | POL                                           | U   |
| 88 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0422 | REPEATER BUILDING NO.2                        | O   |
| 89 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
|    |         |                                               |     |
|    |         | \- Uninterruptible Power Supply               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0506 | ORDNANCE LABORATORY NO. 1                     | U   |
| 90 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Cranes                                     | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Lightning Protection                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         | \- Test System                                |     |
|    |         |                                               | U   |
|    |         |                                               |     |
|    |         |                                               | OMU |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0513 | WASTE WATER TREATMENT PLANT                   | O   |
| 91 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0558 | ORDNANCE OPERATIONS BLDG.                     | O   |
| 92 |         |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | OME |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0562 | CLEANED COMPONENTS/EQUIPMENT STORAGE BLDG.    | O   |
| 93 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0563 | PROPELLANT TRANSPORTER REPAIR/MAINT SHED      | U   |
| 94 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Crane                                      |     |
|    |         |                                               | O   |
|    |         | \- Compressed Air                             | MEU |
|    |         |                                               |     |
|    |         | \- Low Voltage AC Power                       | OMU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | O   |
|    |         |                                               | MEU |
|    |         | \- Structure                                  |     |
|    |         |                                               | U   |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               | U   |
|    |         | \- Potable Water                              |     |
|    |         |                                               | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0569 | CONVERTER/COMPRESSOR OPERATIONS BLDG.         | U   |
| 95 |         |                                               |     |
| .  |         | \- HVAC                                       | OME |
|    |         |                                               |     |
|    |         | \- Low Voltage Power                          | E   |
+----+---------+-----------------------------------------------+-----+
| 1  | K       | HAZARDOUS WASTE STAGING SHELTER               | O   |
| 96 | 7-0569B |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0612 | POL                                           | U   |
| 97 |         |                                               |     |
| .  |         | \- Lightning Protection                       | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0621 | HAZARDOUS WASTE STAGING SHELTER               | O   |
| 98 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 1  | K7-0709 | REPEATER BUILDING NO.1                        | O   |
| 99 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 2  | K7-0853 | HIGH PRESSURE GAS STORAGE BUILDING            | O   |
| 00 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- GHe Battery                                | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
+----+---------+-----------------------------------------------+-----+
| 2  | K7-0901 | MATERIAL DISTRIBUTION/MAINTENANCE BLDG        | E   |
| 01 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | K7-1005 | BARGE TERMINAL FACILITY                       | U   |
| 02 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 2  | K       | PRESS SITE CABLE TERMINAL BLDG                | O   |
| 03 | 7-1205B |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | OMU |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | K7-1557 | INSTRUMENTATION BUILDING                      | OME |
| 04 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- Quick Response Measuring System            | MEU |
|    |         |                                               |     |
|    |         | \- Grounding                                  | U   |
|    |         |                                               |     |
|    |         | \- PMS Test Equipment                         | O   |
|    |         |                                               | MEU |
|    |         | \- Lightning Protection                       |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 2  | K7-2468 | SANDBLAST/PAINT FACILITY                      | U   |
| 05 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- Protective Sandblast Skirt                 |     |
|    |         |                                               | O   |
|    |         | \- Grounding                                  | MEU |
|    |         |                                               |     |
|    |         | \- Lightning Protection                       | U   |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 2  | M5-0791 | COLLIMATION TOWER EQUIPMENT BLDG              | E   |
| 06 |         |                                               |     |
| .  |         | \- Compressed Air                             |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M5-1544 | HYDROMECHANICAL BLDG                          | O   |
| 07 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M5-1545 | TRANSMITTER BLDG                              | O   |
| 08 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0038 | STORAGE SHED                                  | U   |
| 09 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | O   |
|    |         |                                               | MEU |
|    |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Potable Water                              | MEU |
|    |         |                                               |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0138 | COMMUNICATIONS DISTRIBUTION/SWITCHING CTR     | OME |
| 10 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       | OME |
|    |         |                                               |     |
|    |         | \- HVAC                                       | OMU |
|    |         |                                               |     |
|    |         | \- Uninterruptable Power System               | OM  |
|    |         |                                               |     |
|    |         | \- Complex Control System                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0342 | CENTRAL INSTRUMENTATION FACILITY              | O   |
| 11 |         |                                               | MEU |
| .  |         | \- Wave Analysis Laboratory                   |     |
|    |         |                                               | U   |
|    |         | \- Flowmeter Calib. Supply Panel              |     |
|    |         |                                               | O   |
|    |         | \- Test Equipment DAS                         | MEU |
|    |         |                                               |     |
|    |         | \- LN2 System                                 | O   |
|    |         |                                               | MEU |
|    |         | \- Bleed Screw Fitting                        |     |
|    |         |                                               | O   |
|    |         | \- Oxygen Deficiency Analyzer Assembly        | MEU |
|    |         |                                               |     |
|    |         |                                               | OME |
+----+---------+-----------------------------------------------+-----+
| 2  | M       | HAZARDOURS WASTE STAGING SHELTER              | OME |
| 12 | 6-0342B |                                               |     |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0392 | TOXIC HAZARDS LABORATORY                      | OME |
| 13 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage Power                          |     |
|    |         |                                               |     |
|    |         | \- Structure                                  |     |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        |     |
|    |         |                                               |     |
|    |         | \- Potable Water                              |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0399 | KSC HEADQUARTERS BLDG                         | O   |
| 14 |         |                                               | MEU |
| .  |         | \- UPS 10KVA Power                            |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0493 | INDUSTRIAL AREA SUPPORT BLDG                  | O   |
| 15 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power -- Trailer Park       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0539 | STORAGE SHED                                  | O   |
| 16 |         |                                               | MEU |
| .  |         | > \- Low Voltage Electrical                   |     |
|    |         | >                                             | U   |
|    |         | > \- Grounding                                |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0589 | SUPPORT BUILDING                              | O   |
| 17 |         |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | > \- Low Voltage Electrical                   | MEU |
|    |         | >                                             |     |
|    |         | > \- Structure                                | O   |
|    |         | >                                             | MEU |
|    |         | > \- Sanitation / Sewage                      |     |
|    |         | >                                             | U   |
|    |         | > \- Potable Water                            |     |
|    |         |                                               | U   |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0790 | COMMUNICATION CROSS CONNECT                   | OME |
| 18 |         |                                               |     |
| .  |         | \- HVAC                                       | OME |
|    |         |                                               |     |
|    |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M6-0791 | COMMUNICATION MAINTENANCE AND STORAGE         | O   |
| 19 |         |                                               | MEU |
| .  |         | \- HVAC                                       |     |
|    |         |                                               | O   |
|    |         | \- Low Voltage AC Power                       | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | U   |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- Potable Water                              | U   |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0355 | OPERATIONS and CHECKOUT BUILDING              | E   |
| 20 |         |                                               |     |
| .  |         | \- LIOH Cartridge Set                         | O   |
|    |         |                                               | MEU |
|    |         | \- UPS 10KVA Power                            |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M       | LAUNCH EQUIPMENT TEST FACILITY                |     |
| 21 | 7-0505A |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0531 | BANANA RIVER REPEATER STATION                 | OME |
| 22 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage Electrical                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0554 | POL                                           | E   |
| 23 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0656 | PARACHUTE REFURBISHMENT FACILTY               | U   |
| 24 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0657 | PARACHUTE REFURBISHMENT FACILITY              | O   |
| 25 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- 25 Ton Lowbed Trailer                      | MEU |
|    |         |                                               |     |
|    |         | \- Compressed Air                             | OMU |
+----+---------+-----------------------------------------------+-----+
| 2  | M       | POL                                           | U   |
| 26 | 7-0657A |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0809 | COMMUNICATION CROSS CONNECT                   | O   |
| 27 |         |                                               | MEU |
| .  |         | \- Low Voltage Power                          |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0862 | HAZARDOUS WASTE STAGING SHELTER               | O   |
| 28 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0867 | BORESIGHT CONTROL BLDG                        | OME |
| 29 |         |                                               |     |
| .  |         | > \- Low Voltage AC Power                     | OME |
|    |         | >                                             |     |
|    |         | > \- HVAC                                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0912 | GENERAL WAREHOUSE                             | O   |
| 30 |         |                                               | MEU |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-0961 | HYPERGOL MODULE PROCESSING (NORTH)            |     |
| 31 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1011 | GSE STORAGE BUILDING                          | OM  |
| 32 |         |                                               | EU\ |
| .  |         | \- Cranes                                     | OM  |
|    |         |                                               | EU\ |
|    |         | \- Storage Carousel                           | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage Electrical                     |     |
|    |         |                                               | U   |
|    |         | \- Structure                                  |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1059 | HYPERGOLIC MAINTENANCE FACILITY SUPPORT BLDG  | O   |
| 33 |         | #2                                            | MEU |
| .  |         |                                               |     |
|    |         | > \- Low Voltage AC Power                     | O   |
|    |         | >                                             | MEU |
|    |         | > \- Compressed Air                           |     |
|    |         | >                                             | O   |
|    |         | > \- HVAC                                     | MEU |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1061 | HYPERGOL SUPPORT BUILDING (Shared with        | OME |
| 34 |         | Payloads)                                     |     |
| .  |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
|    |         |                                               |     |
|    |         | \- Low voltage Power                          | O   |
|    |         |                                               | MEU |
|    |         | \- Firex Electrical Control System            |     |
|    |         |                                               | O   |
|    |         | \- Breathing Air                              | MEU |
|    |         |                                               |     |
|    |         | \- Complex Control System                     | E   |
+----+---------+-----------------------------------------------+-----+
| 2  | M       | GHe and GN2 Storage                           | O   |
| 35 | 7-1061A |                                               | MEU |
| .  |         | \- Breathing Air                              |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1212 | HYPERGOL MODULE PROCESSING (SOUTH)            | U   |
| 36 |         |                                               |     |
| .  |         | \- Forward Reaction Control System Fuel &     | OM  |
|    |         | Oxidizer (includiing flush fluids)            | EU\ |
|    |         |                                               | \   |
|    |         | \- Right & Left Hand Aft Propulsion System    | OM  |
|    |         | Fuel & Oxdizer (including flush fluids)       | EU\ |
|    |         |                                               | \   |
|    |         | \- Payload Bay Kit Fuel & Oxidizer Fluids     | OM  |
|    |         | Forward Reaction Control System Fuel &        | EU\ |
|    |         | Oxidizer                                      | \   |
|    |         |                                               | O   |
|    |         | \- OMS/RCS Thruster Trickle Purge Panel       | MEU |
|    |         |                                               |     |
|    |         | \- Platforms                                  | OM  |
|    |         |                                               | EU\ |
|    |         | \- Compressed Air                             | OM  |
|    |         |                                               | EU\ |
|    |         | \- Firex Electrical Control                   | OM  |
|    |         |                                               | EU\ |
|    |         | \- Pneumatics ( GN2, Ghe, & Compressed Air)   | OM  |
|    |         |                                               | EU\ |
|    |         | \- Facility Cranes                            | OM  |
|    |         |                                               | EU\ |
|    |         | \- Powered Doors                              | OM  |
|    |         |                                               | EU\ |
|    |         | \- Firex Deluge Systems-                      | OM  |
|    |         |                                               | EU\ |
|    |         | \- Breathing Air                              | OM  |
|    |         |                                               | EU\ |
|    |         | \- Power:                                     | \   |
|    |         |                                               | OM  |
|    |         | \- Low Voltage Dist. System                   | EU\ |
|    |         |                                               | O   |
|    |         | \- Lighting                                   | MEU |
|    |         |                                               |     |
|    |         | \- 400 Hz                                     | O   |
|    |         |                                               | MEU |
|    |         | \- DC Ground                                  |     |
|    |         |                                               | O   |
|    |         | \- HVAC System                                | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-     | FIREX PUMP STATION                            | OM  |
| 37 | 1362    |                                               | EU\ |
| .  |         | \- Compressed Air System                      | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage AC Power                       |     |
|    |         |                                               | O   |
|    |         | \- HVAC                                       | MEU |
|    |         |                                               |     |
|    |         | \- Structure                                  | OME |
|    |         |                                               |     |
|    |         | \- Sanitation / Sewage                        | U   |
|    |         |                                               |     |
|    |         | \- KCCS                                       | U   |
|    |         |                                               |     |
|    |         | \- Electric Firex System                      | OMU |
|    |         |                                               |     |
|    |         | \- Firex Jockey                               | O   |
|    |         |                                               | MEU |
|    |         | \- Firex Diesel                               |     |
|    |         |                                               | O   |
|    |         | \- Firex Pumps                                | MEU |
|    |         |                                               |     |
|    |         | \- Potable Water                              | O   |
|    |         |                                               | MEU |
|    |         |                                               |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 2  | M       | HMF WATER STORAGE TANK                        | O   |
| 38 | 7-1362A |                                               | MEU |
| .  |         | > \- Low Voltage AC Power                     |     |
|    |         | >                                             | O   |
|    |         | > \- Cathodic Protection                      | MEU |
|    |         | >                                             |     |
|    |         | > \- Grounding                                | O   |
|    |         | >                                             | MEU |
|    |         | > \- Structure                                |     |
|    |         |                                               | O   |
|    |         |                                               | MEU |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1410 | HYPERGOL MODULE STORAGE -- WEST               | E   |
| 39 |         |                                               |     |
| .  |         | > \- Low Voltage AC Power                     | O   |
|    |         | >                                             | MEU |
|    |         | > \- GN2 Regulator Panel                      |     |
|    |         | >                                             | O   |
|    |         | > \- Ghe Charger/Regulator Panel              | MEU |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1412 | HYPERGOL MODULE STORAGE -- EAST               | O   |
| 40 |         |                                               | MEU |
| .  |         | > \- Low Voltage AC Power                     |     |
|    |         | >                                             | OMU |
|    |         | > \- HVAC                                     |     |
|    |         | >                                             | OM  |
|    |         | > \- Firex Deluge                             |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1417 | ORDNANCE LABORATORY NO.2                      | OME |
| 41 |         |                                               |     |
| .  |         | \- HVAC                                       | O   |
|    |         |                                               | MEU |
|    |         | \- Low Voltage Electrical                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | M7-1509 | LOX IMPACT TEST CELL                          | OME |
| 42 |         |                                               |     |
| .  |         | \- Low Voltage AC Power                       |     |
+----+---------+-----------------------------------------------+-----+
| 2  | N6-1118 | SOUTH REPEATER BUILDING                       | O   |
| 43 |         |                                               | MEU |
| .  | \       | \- Low Voltage AC Power                       |     |
|    | _\_\_\_ |                                               | OME |
|    | \_\_\_\ | \- HVAC                                       |     |
|    | _\_\_\_ |                                               | \_\ |
|    |         | \_\_\_                                        | _\_ |
|    |         | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ | \_\ |
|    |         | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ | _\_ |
|    |         |                                               |     |
|    |         | Temporary Facilities, Buildings, Trailers &   |     |
|    |         | Boxcars:                                      |     |
|    |         |                                               |     |
|    |         | Note: SFOC's responsibility for the           |     |
|    |         | facilities identified below includes low      |     |
|    |         | voltage power and air-conditioning for those  |     |
|    |         | designated as "U" .                           |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 44 | R1-0475 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 45 | R1-0476 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | Toilet Facility -- VAB Modular Office Area    | U   |
| 46 | R1-0487 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 47 | R1-0501 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 48 | R1-0510 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 49 | R1-0585 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 50 | R1-0591 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 51 | R1-0600 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 52 | R1-0611 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | Toilet Facility -- Pad A Gate                 | U   |
| 53 | R1-0612 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 54 | R1-0621 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 55 | R1-0691 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | Toilet Facility -- Pad B Gate                 | U   |
| 56 | R1-0703 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 57 | R1-0709 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 58 | R1-0710 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED BOXCAR                             | U   |
| 59 | R1-0711 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 60 | R1-0717 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | Toilet Facility -- Pad B Boxcar Area          | U   |
| 61 | R1-0719 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 62 | R1-0723 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | NASA OWNED TRAILER                            | U   |
| 63 | R1-0755 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | Toilet Facility -- NW OPF                     | U   |
| 64 | R1-0756 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | T       | Toilet Facility -- - Pad B Gate               | U   |
| 65 | R1-0758 |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-019 | TEMP. BLDG. NO. 36 (TR1-695 AND 696)          | U   |
| 66 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-021 | TEMP. BLDG. NO. 40                            | U   |
| 67 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-023 | TEMP. BLDG. NO. 42                            | U   |
| 68 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-024 | TEMP. BLDG. NO. 43                            | U   |
| 69 |         |                                               |     |
| .  |         | Reference TR-1287 (OMEU) for identification   |     |
|    |         | of systems and equipment.                     |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-026 | TEMP. BLDG. NO. 45                            | U   |
| 70 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-027 | TEMP. BLDG. NO. 46                            | U   |
| 71 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-031 | TEMP. BLDG. NO. 50                            | U   |
| 72 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+
| 2  | TRM-033 | TEMP. BLDG. NO. 52                            | U   |
| 73 |         |                                               |     |
| .  |         |                                               |     |
+----+---------+-----------------------------------------------+-----+

+----+----------+-----------------------------------------------+-----+
|    |          | **[KSC / MSFC FACILITIES]{.underline}**       |     |
|    |          |                                               |     |
|    |          | **ASSEMBLY & REFURBISHMENT FACILITY COMPLEX** |     |
|    |          |                                               |     |
|    |          | **See MSFC/KSC Memorandum of Agreement Signed |     |
|    |          | 02/04/2004 for OMEU Requirements**            |     |
+----+----------+-----------------------------------------------+-----+
|    |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | L6       | ENGINEERING & ADMINISTRATION BUILDING         |     |
| 74 | **-**146 |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- ANSUL Fire System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Brick And Mortar                        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Building Automation System              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Building E&A                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Building Interior                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Chilled Water System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Data Lines                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Elevator System                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Fire Suppression System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Government Telephone System             | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Grounding System                        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** HVAC System                             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Janitorial Service Administrative       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Lightning Protection                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Low Voltage                             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Potable Water, E&A Building             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Public Address System                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Sanitary Sewer System                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Security System And Turnstiles          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** Television System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **-** UPS System (Bas And Main Frame)         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-147   | CHILLER BUILDING                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Air Compressor System Chiller              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Chilled Water System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Chiller Plant                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fuel Oil Tank System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- High Voltage (Chiller)                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water Boilers                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | -.HVAC System                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Natural Gas Pipe Line                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitary Sewer System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Two Way Radio                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Water Treatment System                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-247   | MANUFACTURING BUILDING (MFG)                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Chilled Water System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Cranes                                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Dock, Loading                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Elevator System                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- GN2 System                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Helium System                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- High Voltage                               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Process                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Monorail                                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Oxygen Monitoring System                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitary Sewer System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Security System And Turnstiles             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- TVC Tank Farm                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- UPS System (ABACS, E&I, IDLM)              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Vacuum Cleaning System                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-248   | SERVICE BUILDING (SVC)                        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- GN2 System                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Revetments System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitary Sewer System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-249   | SERVICE BUILDING ANNEX                        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Exhaust System                             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Revetments System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ventilation System                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-295   | WASTE STAGING FACILITY (WASTE)                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Gates, Fence                               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Revetments System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Security System And Turnstiles             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ventilation System                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-297   | MANUFACTURING PROCESS SUPPORT FACILITY (MPSF) | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Chilled Water System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressor System MPSF                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Dock, Loading                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Elevator System                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitary Sewer System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Security System And Turnstiles             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Walk In Cooler Systems                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L7-201   | AFT SKIRT TEST FACILITY POL                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- POL Structure                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L7-251   | AFT SKIRT TEST FACILITY (ASTF)                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Cranes                                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Deluge System                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash And Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hydrazine Monitor                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Oxygen Monitoring System                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitary Sewer System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Security System And Turnstiles             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ups System (ABACS)                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | TR3-034  | MODULAR OFFICE BUILDING (MOB)                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitary Sewer System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Security System And Turnstiles             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | L6-195   | GUARD BUILDING (GUARD)                        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Lightning Protection                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment And Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | **PARACHUTE REFURBISHMENT FACILITY COMPLEX**  |     |
+----+----------+-----------------------------------------------+-----+
|    | M7-656   | PRF WAREHOUSE                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick And Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System PRF     | O   |
|    |          | Warehouse                                     | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Exhaust System                             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- PRF Warehouse Building                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ventilation System                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | M7-657   | PARACHUTE REFURBISHMENT FACILITY              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick and Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Automation System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building PRF                               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Chilled Water System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Chiller Plant PRF                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Commercial Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System PRF     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Cranes                                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash and Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Alarm System PRF                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fire Suppression System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Grounding System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- High Voltage                               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hoists                                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water System                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Administrative          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Process                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Monorail                                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment and Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Parachute Wash and Dry System              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Building Distribution        | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water, Domestic                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Powered Doors                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Public Address System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    | M7-0657A | PRF POL                                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Brick and Mortar                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building Interior                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Eyewash and Safety Shower                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | **SRB REFURBISHMENT FACILITY**                |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 01726\*  | HANGER "S"                                    | U   |
| 75 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | **SRB REFURBISHMENT FACILITY**                |     |
|    |          |                                               |     |
|    |          | **HANGAR "N" COMPLEX**                        |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 01728\*  | HANGER \"N\"                                  | U   |
| 76 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Acid Exhaust Hood NDE                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Process                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Dust Collector                             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Electric Walk In Furnace                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Exhaust Fans and Hoods                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hoist (N)                                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment and Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Oxygen Monitoring System                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Pull test Monorail Crane                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Refrigerated Air Dryer                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Solid Film Lube Spray Booth                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- UPS System (Hgr N)                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 27 | 01728E\* | FUEL TANK                                     | U   |
| 6A |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 27 | 01729\*  | HIGH VOLTAGE SUBSTATION                       | U   |
| 6B |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 15730\*  | STORAGE FACILITY (Blockhouse 19)              | U   |
| 77 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 21900H\* | ENGINERRING SUPPORT BUIDING (Partial)         | U   |
| 78 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 21917\*  | HAZARDOUS WASTE STORAGE SHED                  | U   |
| 79 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 21918\*  | HAZARDOUS WASTE STORAGE SHED                  | U   |
| 80 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 21919\*  | HAZARDOUS WASTE STORAGE SHED                  | U   |
| 81 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 33000\*  | RECORDS STORAGE BUILDING (Partial)            | U   |
| 82 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 54926\*  | WASTE STAGING FACILTY (N. POL)                | U   |
| 83 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 2  | 54928\*  | LITTLE "N" STORAGE BUILDING                   | U   |
| 84 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment and Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 55005\*  | **HANGAR M ANNEX**                            | U   |
| 85 |          |                                               |     |
| .  |          | \- CO2 Absorb Cartridge Assembly              | O   |
|    |          |                                               | MEU |
|    |          | \- Compressed Air                             |     |
|    |          |                                               | U   |
|    |          | \- Lightning Protection                       |     |
|    |          |                                               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | **SRB REFURBISHMENT FACILTY**                 |     |
|    |          |                                               |     |
|    |          | **HANGAR "AF" COMPLEX**                       |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 60629\*  | POL SHELTER                                   | U   |
| 86 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 60630\*  | POL FACILITY, HANGAR AF                       | U   |
| 87 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ansul Fire Protection                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Building AF POL                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 2  | 66200\*  | PAINT STORAGE BUILDING                        | U   |
| 88 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66234\*  | PROPANE STORAGE TANK AND DISTRIBUTION SYSTEM  | O   |
| 89 |          |                                               | MEU |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66236\*  | HAZARDOUS WASTE STAGING SHELTER               | U   |
| 90 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66237\*  | HAZARDOUS WASTE STAGING SHELTER               | U   |
| 91 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66238\*  | HAZARDOUS WASTE STAGING SHELTER               | U   |
| 92 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66239\*  | HAZARDOUS WASTE STAGING SHELTER               | U   |
| 93 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66240\*  | EAST HIGH PRESSURE WASH FACILTY (EAST WASH)   | U   |
| 94 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Crane                                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Fixed Level Work Stand                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hydrolase Water System                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment and Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water (Process) (CCAS)             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Turntable                                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 2  | 66241\*  | DE-IONIZED WATER TANK                         | O   |
| 95 |          |                                               | MEU |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66242\*  | FIRST WASH BUILDING (SRB)                     | U   |
| 96 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air System West Wash            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Exhaust System                             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hydrolase Water Process System             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water (Process) (CCAS)             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 2  | 66244\*  | SRB RECOVERY SLIP                             | U   |
| 97 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66245\*  | HIGH VOLTAGE SUBSTATION                       | U   |
| 98 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 2  | 66246\*  | 100,000 GALLON STORAGE TANK AND ASSOCIATED    | O   |
| 99 |          | PIPING/DISTRIBUTION SYSTEM                    | MEU |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66248\*  | 72,000 GALLON STORAGE TANK AND ASSOCIATED     | O   |
| 00 |          | PIPING/DISTRIBUTION SYSTEM                    | MEU |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66249\*  | THRUST VECTOR CONTROL (TVC) DISSERVICE BLDG   | U   |
| 01 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Distribution System         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air System (TVCDF)              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- GN2 System (TVCDF)                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hot Water Process (TVCDF)                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process) (CCAS)               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment and Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Oxygen Monitoring System                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water (Process) (CCAS)             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- UPS System (TVCDF)                         | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Video Monitoring System                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66250\*  | SRB RECOVERY BUILDING HANGER AF               | U   |
| 02 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air Process AF                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- De-Ionized Water                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service (Process)               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Office Equipment and Furniture             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Portable Eyewash                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Process (CCAS)               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Small Parts Alodine System                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Small Parts Bake Oven                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Small Parts Cleaning System                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Small Parts Make Up Air Unit               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Small Parts Monorail System                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Small Parts Paint Booth                    | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Television System                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Walk-In Cooler System                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66251\*  | HIGH PRESSURE GAS BUILDING                    | U   |
| 03 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Data Lines                                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- JIB Crane                                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone System                | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Portable Eye Wash                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66252\*  | HIGH VOLTAGE SUBSTATION                       | U   |
| 04 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66256\*  | WASTE WATER TANK                              | U   |
| 05 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66257\*  | BOILER BUILDING                               | U   |
| 06 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66259\*  | HYDROLASE WATER OZONE BUILDING                | U   |
| 07 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air System Process (Ozone)      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Hydrolase Water Process System             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ozone Generator                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Portable Eyewash                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66265\*  | HIGH VOLTAGE SUBSTATION                       | U   |
| 08 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66266\*  | TVCDF POL                                     | U   |
| 09 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reel and Static Lines               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66267\*  | TVCDF TANK FARM AREA                          | U   |
| 10 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reel and Static Lines               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water Process (CCAS)               | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66295\*  | SRB RECOVERY SHIP BERTH SOUTH                 | U   |
| 11 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66296\*  | SRB RECOVERY SHIP BERTH NORTH                 | U   |
| 12 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66310\*  | SRB PAINT FACILITY (SPF)                      | U   |
| 13 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Crane                                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Power Door                                 | OMU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Sanitation/Sewage                          | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Alodine Waste System                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air System SPF                  | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Exhaust System Process                     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- HVAC System (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Janitorial Service Process                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Make Up Air Heater (SPF)                   | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Media Blast Booth                          | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Paint Booth                                | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Potable Water (Process) (CCAS)             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- SPF Compressed Air Distribution System     | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66       | PROPANE STORAGE TANK AND DISTRIBUTION SYSTEM  | O   |
| 14 | 310A-D\* |                                               | MEU |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66311\*  | HIGH VOLTAGE SUBSTATION                       | U   |
| 15 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66320\*  | ROBOT WASH BUILDING                           | U   |
| 16 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66321\*  | LIFT STATION                                  | U   |
| 17 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66330\*  | WAREHOUSE                                     | U   |
| 18 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66332\*  | SEPTIC TANK                                   | U   |
| 19 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
| 3  | 66336\*  | JOINT USE WASTE STAGING FACILITY (JUWS)       | U   |
| 20 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Ground Reels and Static Lines              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | 66340\*  | MULTI-MEDIA BLAST FACILITY                    | U   |
| 21 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Breathing Air                              | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Compressed Air System MMBF                 | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Government Telephone Systems               | U   |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Low Voltage (Process)                      | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Media Blast Pots                           | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Spiral Conveyor                            | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Torritt Dust Collection System             | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
|    |          | \- Vacuum System (MMBF)                       | O   |
|    |          |                                               | MEU |
+----+----------+-----------------------------------------------+-----+
| 3  | NONE\*   | MMBF STEPDOWN TRANSFORMER                     | U   |
| 22 |          |                                               |     |
| .  |          |                                               |     |
+----+----------+-----------------------------------------------+-----+

**NOTE: 1) USA/SRB Element is responsible for all OMEU/CMDS requirements
listed under item \# 274 KSC/MSFC Element Facilities.**

> **2) \* SRB items are located on Cape Canaveral Air Force Station. The
> JBOSC contractor has OME responsibilities per Memorandum Of
> Understanding (KCA 1777) dated February 11, 2004. (Exceptions as
> noted.)**

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Facilities systems and equipment
to be provided to the contractor for the performance of this contract:

-   CMDS - Configuration Management Data System (NASA System) =
    Technical Report 1287 (obtained through OMEU Matrix)

**PART J-9-B-5**

**KENNEDY SPACE CENTER**

**GOVERNMENT FURNISHED FACILITIES**

**PART 2**

**KENNEDY SPACE CENTER AND**

**OFFSITE LANDING FACILITIES & SYSTEMS**

**TASK DESCRIPTION:**

O -- Operator M-Maintenance E -- Sustaining Engineering U -- User

+---------------------------------------------------------+------------+
| **[DESCRIPTION]{.underline}**                           | **         |
|                                                         | [TASK]{.un |
|                                                         | derline}** |
+---------------------------------------------------------+------------+
| **KSC LANDING SITE, KSC FLORIDA**                       |            |
+---------------------------------------------------------+------------+
| ######### **Operational Buildings**                     |            |
+---------------------------------------------------------+------------+
| Landing Support Complex                                 | OMEU       |
+---------------------------------------------------------+------------+
| T-Shelter                                               | OMEU       |
+---------------------------------------------------------+------------+
| Low voltage power                                       | OMEU       |
+---------------------------------------------------------+------------+
| HVAC                                                    | OMEU       |
+---------------------------------------------------------+------------+
| ######### **Shuttle Convoy Vehicles**                   |            |
+---------------------------------------------------------+------------+
| NASA Convoy Command Vehicle                             | OMEU       |
+---------------------------------------------------------+------------+
| Crew Hatch Access Vehicle                               | OMEU       |
+---------------------------------------------------------+------------+
| Crew Transporter Vehicle                                | OMEU       |
+---------------------------------------------------------+------------+
| Astrovan                                                | OMEU       |
+---------------------------------------------------------+------------+
| Tow Tugs                                                | OMEU       |
+---------------------------------------------------------+------------+
| Cool Stair Truck                                        | OMEU       |
+---------------------------------------------------------+------------+
| Purge Stair Truck                                       | OMEU       |
+---------------------------------------------------------+------------+
| Fan Truck and Fan Unit                                  | OMEU       |
+---------------------------------------------------------+------------+
| Cool Transporter (tractor & trailer)                    | OMEU       |
+---------------------------------------------------------+------------+
| Purge Transporter (kmag)                                | OMEU       |
+---------------------------------------------------------+------------+
| TV-1                                                    | OMEU       |
+---------------------------------------------------------+------------+
| TV-2                                                    | OMEU       |
+---------------------------------------------------------+------------+
| C70-1115 Unit                                           | OMEU       |
+---------------------------------------------------------+------------+
| Mini PPU (unit, generator, trailer)                     | OMEU       |
+---------------------------------------------------------+------------+
| CLS Purge Unit                                          | OMEU       |
+---------------------------------------------------------+------------+
| Four Scape GSA Vans                                     | U          |
+---------------------------------------------------------+------------+
| Convoy Support Vehicles (various GSA vans and trucks)   | U          |
+---------------------------------------------------------+------------+
| Flight Crew De-stow Vehicle                             | OMEU       |
+---------------------------------------------------------+------------+
| Mate De-mate Device                                     | OMEU       |
+---------------------------------------------------------+------------+
| Orbiter GSE                                             | OMEU       |
+---------------------------------------------------------+------------+
| PAPI Light System (Precision Approach Path Indicator    | OMEU       |
| Lights)                                                 |            |
+---------------------------------------------------------+------------+
| Ball / Bar System                                       | OMEU       |
+---------------------------------------------------------+------------+
| MSBLS (Microwave Scanning Beam Landing System) &        | OMEU       |
| Facilities                                              |            |
+---------------------------------------------------------+------------+
| TACAN (Tactical Air Navigation System)                  | OMEU       |
+---------------------------------------------------------+------------+
| Xenon Lights & Generators                               | U          |
+---------------------------------------------------------+------------+
| DGPS (Differential Global Positioning System)           | OME        |
+---------------------------------------------------------+------------+
| Communications                                          | U          |
+---------------------------------------------------------+------------+
| Orbiter Super Simulator                                 | OMEU       |
+---------------------------------------------------------+------------+
| Remote Weather Station (2 ea)                           | OMEU       |
+---------------------------------------------------------+------------+
|                                                         |            |
+---------------------------------------------------------+------------+
| **WHITE SANDS SPACE HARBOR, NEW MEXICO**                |            |
+---------------------------------------------------------+------------+
| MSBLS and Facilities                                    | M(LRU      |
|                                                         | repair)EU  |
+---------------------------------------------------------+------------+
| TACAN & Facilities (Honeywell maintained)               | U          |
+---------------------------------------------------------+------------+
| PAPI Light System                                       | EU         |
+---------------------------------------------------------+------------+
| Ball / Bar System                                       | EU         |
+---------------------------------------------------------+------------+
| Shuttle Convoy Vehicles                                 |            |
+---------------------------------------------------------+------------+
| Astrovan                                                | U          |
+---------------------------------------------------------+------------+
| WSSH Convoy Command Vehicle                             | U          |
+---------------------------------------------------------+------------+
| Crew Hatch Access Vehicle                               | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Tug                                                     | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Fan Unit                                                | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Operations Control Center (WOCC)                        | U          |
+---------------------------------------------------------+------------+
| USA Operations Building                                 | U          |
+---------------------------------------------------------+------------+
| Communications                                          | U          |
+---------------------------------------------------------+------------+
| Orbiter GSE                                             | OMEU       |
+---------------------------------------------------------+------------+
| Xenon Lights & Generators                               | U          |
+---------------------------------------------------------+------------+
| Convoy Support Vehicles (various GSA vans and trucks)   | U          |
+---------------------------------------------------------+------------+
|                                                         |            |
+---------------------------------------------------------+------------+
| **DRYDEN FLIGHT RESEARCH CENTER, EAFB CALIFORNIA**      |            |
+---------------------------------------------------------+------------+
| MSBLS and Facilities                                    | M(LRU      |
|                                                         | Repair)EU  |
+---------------------------------------------------------+------------+
| TACAN (USAF)                                            | U          |
+---------------------------------------------------------+------------+
| Communications                                          | U          |
+---------------------------------------------------------+------------+
| PAPI Light System                                       | EU         |
+---------------------------------------------------------+------------+
| Ball / Bar System                                       | EU         |
+---------------------------------------------------------+------------+
| Orbiter GSE & Hyper Scrubbers                           | OMEU       |
+---------------------------------------------------------+------------+
| Mate De-mate Device                                     | OEU        |
+---------------------------------------------------------+------------+
| MDD Load Test Equipment (slings, riggings, weights)     | OMEU       |
+---------------------------------------------------------+------------+
| Hanger Crane and Doors                                  | EU         |
+---------------------------------------------------------+------------+
| Xenon Lights & Generators                               | U          |
+---------------------------------------------------------+------------+
| Shuttle Convoy Vehicles                                 |            |
+---------------------------------------------------------+------------+
| NASA Convoy Command Vehicle                             | U          |
+---------------------------------------------------------+------------+
| Astrovan                                                | U          |
+---------------------------------------------------------+------------+
| High Ranger                                             | U          |
+---------------------------------------------------------+------------+
| Convoy Support Vehicles (various GSA vans and trucks)   | U          |
+---------------------------------------------------------+------------+
| White Room Truck                                        | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Purge Stair Truck                                       | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Cool Stair Truck                                        | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Fan Truck & Fan Unit                                    | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Crew Transport Vehicle                                  | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Flat Bed Truck                                          | U          |
+---------------------------------------------------------+------------+
| Cool Transporter (tractor & trailer)                    | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Purge Transporter (kmag)                                | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Scape 1 Box Van (GSA/SGS)                               | U          |
+---------------------------------------------------------+------------+
| T-300 Tug                                               | U          |
+---------------------------------------------------------+------------+
| Flight Crew Destow Vehicle                              | O          |
|                                                         | M(major)EU |
+---------------------------------------------------------+------------+
| Convoy & Turnaround Generators (4ea - 350kw, 2ea        | EU         |
| -125kw)                                                 |            |
+---------------------------------------------------------+------------+
| USA Operations Support Offices                          | U          |
+---------------------------------------------------------+------------+
|                                                         |            |
+---------------------------------------------------------+------------+
| **MORON AB TAL SITE, SPAIN**                            |            |
+---------------------------------------------------------+------------+
| Orbiter GSE                                             | OMEU       |
+---------------------------------------------------------+------------+
| Convoy Support Vehicles (various GSA)                   | U          |
+---------------------------------------------------------+------------+
| Tow Tug                                                 | U          |
+---------------------------------------------------------+------------+
| Crew Compartment Access Stand                           | U          |
+---------------------------------------------------------+------------+
| Generators                                              | OMEU       |
+---------------------------------------------------------+------------+
| PAPI Light System                                       | OMEU       |
+---------------------------------------------------------+------------+
| Ball / Bar System                                       | OMEU       |
+---------------------------------------------------------+------------+
| MSBLS                                                   | OMEU       |
+---------------------------------------------------------+------------+
| TACAN (USAF)                                            | U          |
+---------------------------------------------------------+------------+
| Xenon Lights & Generators                               | U          |
+---------------------------------------------------------+------------+
| Remote Weather Station                                  | OMEU       |
+---------------------------------------------------------+------------+
| Communications                                          | U          |
+---------------------------------------------------------+------------+
| Operations Support Offices and Warehouse                | U          |
+---------------------------------------------------------+------------+
|                                                         |            |
+---------------------------------------------------------+------------+
| **ZARAGOZA AB TAL SITE, SPAIN**                         |            |
+---------------------------------------------------------+------------+
| Orbiter GSE                                             | OMEU       |
+---------------------------------------------------------+------------+
| Convoy Support Vehicles (various GSA and SAF)           | U          |
+---------------------------------------------------------+------------+
| Tow Tug                                                 | U          |
+---------------------------------------------------------+------------+
| Crew Compartment Access Stand                           | U          |
+---------------------------------------------------------+------------+
| Generators                                              | OMEU       |
+---------------------------------------------------------+------------+
| PAPI Light System                                       | OMEU       |
+---------------------------------------------------------+------------+
| Ball / Bar System                                       | OMEU       |
+---------------------------------------------------------+------------+
| MSBLS                                                   | OMEU       |
+---------------------------------------------------------+------------+
| TACAN (NASA / Spanish Air Force maintained)             | U          |
+---------------------------------------------------------+------------+
| Xenon Lights & Generators                               | U          |
+---------------------------------------------------------+------------+
| Remote Weather Station                                  | OMEU       |
+---------------------------------------------------------+------------+
| Communications                                          | U          |
+---------------------------------------------------------+------------+
| Threshold/Approach Lighting                             | OMEU       |
+---------------------------------------------------------+------------+
| Hangar / Operations Support Offices                     | U          |
+---------------------------------------------------------+------------+
|                                                         |            |
+---------------------------------------------------------+------------+
| **ISTRES AB TAL SITE, FRANCE**                          |            |
+---------------------------------------------------------+------------+
| Orbiter GSE                                             | OMEU       |
+---------------------------------------------------------+------------+
| Convoy Support Vehicles (various rental trucks and vans | U          |
| and FAFB)                                               |            |
+---------------------------------------------------------+------------+
| Tow Tug                                                 | U          |
+---------------------------------------------------------+------------+
| Crew Compartment Access Stand                           | U          |
+---------------------------------------------------------+------------+
| ###### Generators                                       | OMEU       |
+---------------------------------------------------------+------------+
| PAPI Light System (2 ea)                                | OMEU       |
+---------------------------------------------------------+------------+
| Ball / Bar System (2 ea)                                | OMEU       |
+---------------------------------------------------------+------------+
| MSBLS & Facilities                                      | OMEU       |
+---------------------------------------------------------+------------+
| TACAN & Facilities                                      | OMEU       |
+---------------------------------------------------------+------------+
| Xenon Lights, Generators & Flatbed Trailers             | U          |
+---------------------------------------------------------+------------+
| Remote Weather Station                                  | OMEU       |
+---------------------------------------------------------+------------+
| Communications                                          | U          |
+---------------------------------------------------------+------------+
| Operations Support Offices                              | U          |
+---------------------------------------------------------+------------+
| Threshold/Approach Lighting                             | OMEU       |
+---------------------------------------------------------+------------+
| Loadbank                                                | OMEU       |
+---------------------------------------------------------+------------+
| Forklift (5K)                                           | OMEU       |
+---------------------------------------------------------+------------+
| Light Banks (2 ea)                                      | OMEU       |
+---------------------------------------------------------+------------+
|                                                         |            |
+---------------------------------------------------------+------------+
| **PALMDALE, CALIFORNIA**                                |            |
+---------------------------------------------------------+------------+
| Orbiter Lifting Fixture                                 | OMEU       |
+---------------------------------------------------------+------------+
| NOTE: Contractor is responsible for maintenance only.   |            |
| No replacement of vehicles                              |            |
+---------------------------------------------------------+------------+
| or equipment.                                           |            |
+---------------------------------------------------------+------------+

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Facilities systems and equipment
to be provided to the contractor for the performance of this contract:

-   CMDS - Configuration Management Data System (NASA System) -
    Technical Report 1287 (obtained through OMEU Matrix)

**PART J-9-C-1**

[]{#c1 .anchor}**MARSHALL SPACE FLIGHT CENTER**

**GOVERNMENT FURNISHED EQUIPMENT**

The following GFP will be provided to the contractor:

[ITEM]{.underline} [P/N]{.underline}

Rail Cars (End Rings) NLAX 175/176

Pegasus, Model No. YFNB EQ. Control No. 1964554 (Barge)

+-------+-------------+---------+--------+---------+---------+------+
| TAG   | ITEM NAME   | ORDER   | S/N    | MODEL   | MFG.    | COST |
| NO.   |             |         |        | NO.     | NAME    |      |
|       |             | DOC NO. |        |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
|       |             |         |        |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | COMPUTER,   | M5-     | 102661 | 1000    | CRYSTAL | 845  |
| 33493 | MICRO       | 403723E |        |         | DATA    |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO3   | TYPEWRITER, | JO-69   | 3      | 89      | IBM     | 735  |
| 48497 | ELEC        | 300-200 | 141330 |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| GO0   | CABINET     | MDFC57  | N/A    | N/A     | JEBCO   | 200  |
| 61869 |             |         |        |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| GO0   | CABINET     | MSFC    | N/A    | N/A     | STEEL   | 200  |
| 61877 |             | 57-1592 |        |         | AGE     |      |
+-------+-------------+---------+--------+---------+---------+------+
| GO0   | CABINET     | MDFC    | N/A    | N/A     | ST      | 200  |
| 61878 |             | 57-1592 |        |         | EELCASE |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | PRINTER,    | M8-     | 2801   | 33440A  | HP      | 1700 |
| 27809 | LASER       | 404357E | J08259 |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | BINDER      | M9-     | 7      | 28H     | NSC     | 695  |
| 30454 | MACH.       | 403132E | 710105 |         | INTER.  |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | TYPEWRITER  | M9-     | 857373 | WHEEL 3 | IBM     |      |
| 30457 | 3           | 403136E |        |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | VIEWGRAPH   | M9-     | 505538 | 2130    | 3M      | 485  |
| 30459 |             | 403210E |        |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | VIEWGRAPH   | M9-     | 505583 | 2130    | 3M      | 485  |
| 30460 |             | 403210E |        |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | VCR         | M0-     | 8080   | 26      | RE      | 270  |
| 32505 | RECORDER    | 403750E | 102709 |         | ALISTIC |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | PUNCH       | M0-     | B      | 111PM-2 | GBC     | 2097 |
| 32506 | MACHINE     | 403730E | J01961 |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | PRINTER,    | M1-     | 3033   | 33449-A | HP      | 1932 |
| 32587 | LASERJET    | 403918E | A78611 |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | PRINTER,    | M2-     | 3129   | III P   | HP      | 1107 |
| 33182 | LASER       | 404707E | JA0TB1 |         |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| FO0   | PRINTER,    | M2-     | 3124   | SCANJET | HP      | 1539 |
| 33183 | LASER       | 404707E | A19043 | II C    |         |      |
+-------+-------------+---------+--------+---------+---------+------+
| GO0   | CABINET     | MSFC57  | N/A    | N/A     | STEEL   | 420  |
| 81866 |             |         |        |         | AGE     |      |
+-------+-------------+---------+--------+---------+---------+------+
| GO0   | CABINET     | MSFC57  | N/A    | N/A     | STEEL   | 420  |
| 81867 |             |         |        |         | AGE     |      |
+-------+-------------+---------+--------+---------+---------+------+
| ** ** | ** **       | **17**  | **I    | ** **   | **Total | **\$ |
|       |             |         | tems** |         | cost    | 13,3 |
|       |             |         |        |         | e       | 30** |
|       |             |         |        |         | quals** |      |
+-------+-------------+---------+--------+---------+---------+------+

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   JSC uses NEMS (NASA System) and Shuttle Equipment Tracking System
    (SETS) for the tracking of equipment

**PART J-9-C-2**

[]{#c2 .anchor}**MARSHALL SPACE FLIGHT CENTER**

**GOVERNMENT FURNISHED SPECIAL TOOLING/TEST EQUIPMENT**

Special tools and equipment as required and available. Hand tools will
not be Government furnished. (Personal tools will be provided by the
contractor.)

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   KSC uses NEMS (NASA System) and CARS (USA System) for the tracking
    of Equipment.

[]{#C3 .anchor}**PART J-9-C-3**

**MARSHALL SPACE FLIGHT CENTER**

**RESERVED**

[]{#C4 .anchor}**PART J-9-C-4**

**MARSHALL SPACE FLIGHT CENTER**

**GOVERNMENT FURNISHED SOFTWARE**

The following GFS will be provided to the contractor:

-   Lab Notebook

-   Presentation Manager

**PART J-9-C-5**

[]{#c5 .anchor}**MARSHALL SPACE FLIGHT CENTER**

**GOVERNMENT FURNISHED FACILITIES**

The following facilities will be furnished to the contractor for use in
performance of work under this contract. The contractor has no
responsibility for maintenance and sustaining engineering for these
facilities.

  --------- -------- ----------------------------------------------------
  MSFC      4477     Audioreverberant Chamber

                     Audio Lab

  MSFC      4487     LAB AND OFFICE BUILDING

                     Electrical Systems Integration Lab

  MSFC      4530     PROPULSION SYSTEM COMPONENT TEST STAND

                     Environment Simulation Chamber

  MSFC      4572     PROPULSION AND STRUCTURAL TEST FACILITY

                     Structural Test Facility

  MSFC      4619     STRUCTURES AND MECHANICS LABORATORY

                     Environmental Testing Lab

                     Structural Facility

                     Dynamic Facility

  MSFC      4663     COMPUTER FACILITY

                     Mechanism Test Bed

  MSFC      4708     ENGINEERING AND DEVELOPMENT LABORATORY

                     Engineering and Development Lab

                     Environmental Testing Lab

                     Seal Development Lab

  MSFC      4755     HIGH‑BAY ASSEMBLY FACILITY

  MSFC      4203     Office Building (part of facility)

  MSFC      4625     Shuttle Hardware Storage (part of facility)

  MSFC      4707     Productivity Enhancement Complex (part of facility)

  MSFC      4712     Office Building (part of facility)

  MSFC      4759     Hazardous Material Mach. Facility (part of facility)
  --------- -------- ----------------------------------------------------

**[NOTE:]{.underline}**

**\"Reference Government-Furnished Property, Section J-9-B-5 - Kennedy
Space Flight Center Line Item \# 274 through 322 for facilities used by
USA for SRB Element support.\"**

**PART J-9-D-1**

[]{#d1 .anchor}**DRYDEN FLIGHT RESEARCH CENTER**

**GOVERNMENT FURNISHED EQUIPMENT**

The following Ground Support Equipment (GSE) and Support Equipment (SE)
will be furnished to the contractor for use in performance of work under
this contract. The contractor shall maintain responsibility for
engineering, parts and material, equipment replacement, repair and/or
refurbishment as required. Excluded is NASA contracted labor for the
performance of routine preventive maintenance and minor equipment
repairs.

  --------------------------- -------------------------------------------
  EQUIPMENT NO                DESCRIPTION

  55-98                       Cool Trailer

  55-97                       Purge Trailer

  55-189                      Stair Truck

  55-70                       Stair Truck

  55-100                      Fan Van

  55-71                       Wind Machine

  55-101                      Mack Tractor

  55-102                      Mack Tractor

  55-68                       Crew Match Access Vehicle

  55-22                       CTV

  \*                          Cabin Purge Unit

  \*\*                        Cargo Lift Transporter

  \*                          Portable Purge Convoy Vehicle
  --------------------------- -------------------------------------------

\* Number not available

\*\* NASA ECN 666239

The equipment added to this attachment by S/A 983 of NAS9-20000 shall
remain accountable to contract NAS4-99030, and shall not be transferred
to the SPOC Contract.

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   KSC uses NEMS (NASA System) and CARS (USA System) for the tracking
    of Equipment.

    []{#D2 .anchor}**PART J-9-D-2**

    **DRYDEN FLIGHT RESEARCH CENTER**

    **RESERVED**

    []{#D3 .anchor}**PART J-9-D-3**

    **DRYDEN FLIGHT RESEARCH CENTER**

    **RESERVED**

    []{#D4 .anchor}**PART J-9-D-4**

    **DRYDEN FLIGHT RESEARCH CENTER**

**GOVERNMENT FURNISHED SOFTWARE**

The following GFS will be provided, as needed, to the contractor.

-   Software to support checkout activity at Dryden Flight Research
    Facility (DFRF).

    **PART J-9-E**

    **RESERVED**

    **PART J-9-F**

    **RESERVED**

**PART J-9-G-1**

[]{#g1 .anchor}**WHITE SANDS SPACE HARBOR**

**GOVERNMENT FURNISHED EQUIPMENT**

The following Ground Support Equipment (GSE) and Support Equipment (SE)
will be furnished to the contractor for use in performance of work under
this contract. The contractor shall maintain responsibility for
engineering, parts and material, equipment replacement, repair and/or
refurbishment as required. Excluded is NASA contracted labor for the
performance of routine preventive maintenance and minor equipment
repairs.

-   T-300 Tug

-   Wind Machine

-   Crew Hatch Access Vehicle

The equipment added to this attachment by S/A 983 of NAS9-20000 shall
remain accountable to contract NAS9-99100, and shall not be transferred
to the SPOC contract.

The following systems shall be utilized to maintain the accurate and
current listing of Government Furnished Equipment to be provided to the
contractor for the performance of this contract:

-   KSC use NEMS (NASA System) and CARS (USA System) for the tracking of
    Equipment.

ATTACHMENT J-10

INSTALLATION PROVIDED SERVICES

**J-10 INTRODUCTION:**

**PURPOSE:** The following delineates the Installation Provided Services
(IPS) to be furnished by the Government at sites listed below. Since the
IPS is to be provided on a no-charge-for-use basis, the Contractor shall
make every effort to anticipate support requirements so the Government
may effect orderly scheduling and requisitioning of services to be
furnished hereunder.

**INSTRUCTIONS:**

1.  Requests for specific support to be furnished by the Government in
    accordance with Clause G.12 and this Attachment shall be made by the
    Contractor to the NASA Contracting Officer's Technical
    Representative. The completion of any forms needed to obtain the
    services required shall be accomplished by the Contractor.

2.  Services will be provided by the Government only within the confines
    of statutory, regulatory, and contractual limitations and as may be
    required for performance under this contract.

3.  Any support not provided by the Government in this exhibit or
    elsewhere in the contract will be the responsibility of the
    Contractor.

4.  The responsibilities of the Contractor are defined in the following:

> **NFS 1852.245-71, INSTALLTATION-ACCOUNTABLE GOVERNMENT PROPERTY (NOV
> 2004) -- ALTERNATE 1 (NOV 2004)**

(a) The Government property described in the clause at 1852.245-77, List
    of Installation- Accountable Property and Services, shall be made
    available to the Contractor on a no-charge basis for use in
    performance of this contract. This property shall be utilized only
    within the physical confines of the NASA installation that provided
    the property. Under this clause, the Government retains
    accountability for, and title to, the property, and the Contractor
    assumes the following user responsibilities:\
    \
    The contractor shall retain responsibility for ensuring proper use,
    care, and protection (safeguarding) of all Installation-Accountable
    Government Property (IAGP) under his/her custody and control.
    Individual users shall be responsible for the following: (1)
    Ensuring IAGP is used only in pursuit of approved programs and
    projects, or as otherwise authorized; (2) Notifying cognizant
    Property Support Assistant (PSA) and/or Property Custodian, of all
    assigned equipment location changes; (3) Ensuring that any lost,
    missing or damaged IAGP is officially reported to his/her
    supervisor, the appropriate PSA, and the Protective Services
    Department; (4) Notifying PSA of IAGP not being actively used; (5)
    Ensuring that IAGP is turned in to the Property Disposal Officer
    through the PSA when no longer needed. Under no circumstances will
    the contractor dispose of IAPG, whether tagged or untagged; and, (6)
    Notifying the Contracting Officer, cognizant PSA, and the Center's
    Supply and Equipment Management Officer upon termination of
    employment.\
    \
    The contractor shall establish and adhere to a system of written
    procedures for compliance with these user responsibilities. Such
    procedures must include holding employees liable, when appropriate,
    for loss, damage, or destruction of Government property.

(b) \(1\) The official accountable recordkeeping, physical inventory,
    financial control, and reporting of the property subject to this
    clause shall be retained by the Government and accomplished by the
    installation Supply and Equipment Management Officer (SEMO) and
    Financial Management Officer. If this contract provides for the
    contractor to acquire property, title to which will vest in the
    Government, the following additional procedures apply:

```{=html}
<!-- -->
```
(i) The contractor shall not utilize the installation's central
    receiving facility for receipt of Contractor-acquired property.
    However, the Contractor shall provide listings suitable for
    establishing accountable records of all such property received, on a
    quarterly basis, to the Contracting Officer and the Supply and
    Equipment Management Officer.

(ii) The contractor shall furnish a copy of each purchase order, prior
     to delivery by the vendor, to the installation central receiving
     area:

(iii) The contractor shall establish a record of the property as
      required by FAR 45.5 and 1845.5 and furnish to the Industrial
      Property Officer a DD Form 1149 Requisition and Invoice/Shipping
      Document (or installation equivalent) to transfer accountability
      to the Government within 5 working days after receipt of the
      property by the contractor. The contractor is accountable for all
      contractor-acquired property until the property is transferred to
      the Government\'s accountability.

(iv) Contractor use of Government property at an off-site location and
     off-site subcontractor use require advance approval of the
     contracting officer and notification of the SEMO. The contractor
     shall assume accountability and financial reporting responsibility
     for such property. The contractor shall establish records and
     property control procedures and maintain the property in accordance
     with the requirements of FAR Part 45.5 until its return to the
     installation.

```{=html}
<!-- -->
```
(2) After transfer of accountability to the Government, the contractor
    shall continue to maintain such internal records as are necessary to
    execute the user responsibilities identified in paragraph (a) and
    document the acquisition, billing, and disposition of the property.
    These records and supporting documentation shall be made available,
    upon request, to the SEMO and any other authorized representatives
    of the contracting officer.

(End of clause)

ATTACHMENT J-10-A

INSTALLATION PROVIDED SERVICES

JOHNSON SPACE CENTER

10.1 The Installation Provided Services (IPS) to be provided at JSC are
encapsulated in the following:

\(a\) Clause: **LIST OF INSTALLATION-ACCOUNTABLE PROPERTY AND SERVICES
(NASA 1852.245-77) (JUL 1997) (JSC VERSION APR 2003)**

In accordance with the clause 1852.245-71, Installation - Accountable
Government Property the Contractor is authorized use of the types of
property and services listed below, to the extent they are available, in
the performance of this contract within the physical borders of the
installation which may include buildings and space owned or directly
leased by NASA in close proximity to the installation, if so designated
by the Contracting Officer.

(a) Office space, work area space, and utilities. Government telephones
    are available for official purposes only; pay telephones are
    available for contractor employees for unofficial calls.

(b) General - and special-purpose equipment, including office furniture.

    a.  Equipment to be made available is listed in Attachment J-9. The
        Government retains accountability for this property under the
        clause at 1852.245-71, Installation-Accountable Government
        Property, regardless of its authorized location.

    b.  If the contractor acquires property, title to which vests in the
        Government pursuant to other provisions of this contract, this
        property also shall become accountable to the Government upon
        its entry into Government records as required by the clause at
        1852.245-71, Installation-Accountable Government Property.

    c.  The Contractor shall not bring to the installation for use under
        this contract any property owned or leased by the Contractor, or
        other property that the Contractor is accountable for under any
        other Government contract, without the Contracting Officer's
        prior written approval.

(c) Publications and blank forms stocked by the installation.

(d) Safety and fire protection for Contractor personnel and facilities.

(e) Installation service facilities:

```{=html}
<!-- -->
```
(1) Audiovisual: Presentation services, sound services, Release Print
    Film Library, Film Repository, and loan of audiovisual equipment.

(2) Automatic Data Processing (ADP) Services (onsite only): Generally,
    this includes access to large general-purpose computer systems,
    workstations, and the accessing media; i.e., terminals, printers,
    data communications, and consultation and training in the use of
    said systems. Unless otherwise specified in the contract, this does
    not include providing computer systems or ADP services for the
    Contractor business management, accounting, and administrative
    functions.

(3) Transportation: Shuttle bus service for Contractor employees within
    the parameters provided for Government employees.

(4) Disposal Services: Disposal services for excess onsite and offsite
    Contractor-held/Government-owned property.

(5) Fabrication Services: Fabrication services such as machining, sheet
    metal and welding, electronics, metal finishing, model and plastics,
    and precision cleaning.

(6) Photography, Processing, and Closed-Circuit Television: For
    technical and scientific photography, photographic processing,
    photographic sciences, and closed-circuit television.

(7) Pickup and Delivery of Official Mail: Within the Center and to and
    from the Albert Thomas Post Office, provided the mail is properly
    sealed and stamped. Such mail will be picked up or dropped from only
    one point as designated by JSC or, if preferred, JSC will provide a
    box in the central mailroom for the Contractor to pick up and
    deposit its mail.

```{=html}
<!-- -->
```
(f) Medical treatment of a first-aid nature for Contractor personnel
    injuries or illnesses sustained during on-site duty.

(g) Cafeteria privileges for Contractor employees during normal
    operating hours.

(h) Building maintenance for facilities occupied by Contractor
    personnel.

(i) Moving and hauling for office moves, movement of large equipment,
    and delivery of supplies. Moving services shall be provided on-site,
    as approved by the Contracting Officer.

(j) The user responsibilities of the Contractor are defined in
    paragraph (a) of the clause at 1852.245-71, Installation-Accountable
    Government Property.

(End of Clause)

\(b\) Memorandum of Understanding and Standard Interface Plan Between
Center Operations and Directorate and Missions Operations Directorate.
(JSC 27049).

10.2 The following services are also provided:

Welding services (includes machine work of various types, cleaning,
plating, and hydrostating).

10.3 Government-Provided Russian Language and Logistics Services (RLLS)

The contractor is authorized use of the following RLLS in performance of
this contract or any subcontract entered into under this contract:

1.  Russian Translations

2.  Russian Interpretations

3.  Russian Language training

4.  Russian Logistics services (both in the U.S. and in Russia),
    including

```{=html}
<!-- -->
```
(a) Ground Services (e.g. airport pickup/drop-off, transportation
    between hotels and meeting locations)

(b) Meeting Services (e.g. coordination of schedules, agendas and
    protocols)

(c) Hotel Reservations at the Penta Hotel in Russia

(d) Visa Coordination

The Contracting Officer shall be promptly notified by the contractor
upon identification of a need for RLLS. The Contracting Officer shall
provide instructions as to the point of contact for submitting a request
for RLLS. Failure of the Government to provide adequate or timely RLLS
shall entitle the contractor to an equitable adjustment in all affected
contract terms and conditions, exclusive of any adjustment in fee. This
provision, including this flow-down requirement, shall be inserted in
all subcontracts where it is anticipated that RLLS may be necessary for
contract performance.

ATTACHMENT J-10-B

INSTALLATION PROVIDED SERVICES

KENNEDY SPACE CENTER

1.  **Hazardous Waste Management**

Services include hazardous and controlled waste handling, treatment,
collection, and disposal. Generators of waste shall contain, document,
and store waste for pickup and disposal by the government.

2.  **Printing and Micrographics**

Preparation and distribution of forms will be provided as well as
publications such as telephone directories and Public Affair materials.
Printing and micrographics requirements are provided through, the KSC
Print Plant and off-site Government Printing Office contract printing.

3.  **Non-destructive Evaluation (NDE) Radiography**

NDE radiography testing services are provided. Real-time priority
requirements are normally supported within 2 hours (standard shift) to 4
hours (off-shift). All other NDE shall be performed by the contractor,
reference SOW paragraph 1.5.5.1.

4.  **KSC Reference Standards**

KSC Reference Standards are maintained with traceability to the National
Institute of Standards and Technology and are provided to the contractor
for use in comparing the contractor's working standards.

5.  **Range Safety Services**

Services include launch area and SRB impact area surveillance, Flight
Termination Systems, Command Destruct System, tracking sources,
compliance with weather constraints, Shuttle controllability
verification, toxic and blast requirements compliance, and Flight
Control Officer and Flight Director/Flight Dynamics Officer
communications.

6.  **Launch Vehicle Ordnance**

Services include receipt, receiving inspection, delivery, storage,
shipment of explosives and pyrotechnic ordnance, inspection, and
kitting. The government will also provide disposal of unserviceable or
damaged ordnance. (JOP 15E-3-15)

7.  **CCAS Security**

Services include clearing and controlling personnel from the impact
limit line on CCAS property for Shuttle launches and security support
for Hangar AF SRB operations. Access control into Hangar AF includes one
security post for personnel entrance/exit into the hazardous area for a
two week period during SRB deservicing after each SRB recovery. Services
also include escort during transportation of critical flight hardware.

8.  **Radar and Telemetry**

Services include C-band radar (launch, on-orbit, and landing) and
telemetry **(**launch).

9.  **Xenon Light Support**

Services include the maintenance, testing, operation, and spares
provisioning of 20KW xenon lights at KSC and contingency landing sites.
Deployment at KSC is provided by the government. The contractor shall be
responsible for shipping xenon lights between KSC and the contingency
landing sites**.** (JOP 15E-3-12)

10. **Timing and Range Control**

Services include the O&M, quality assurance, engineering, repair, and
spares provisioning for the KSC Timing and Countdown, LC-39 Photo
Sequencer Control, SLF Photo Control System, and the Photo Optical
Control System. Support includes the O&M of LC-39 A & B camera blast
covers, cables, and mounts. The government also provides system
operating parameters such as timing correlation signals, countdown
signals, and KSC/CCAS timing compatibility**.** (JOP 15E-3-32)

11. **Photography Support**

Services include motion picture, still, and video support for major
operations and milestones such as processing, launch, and landing.
Support includes visual image acquisition, processing, and distribution
of the documentary support for processing. (JOP 15E-3-3) Excluded from
this service is closeout photography which is the responsibility of the
contractor.

12. **AF Weather Support**

Services include weather forecasting and real-time support for
contractor operations such as: (JOP 15E-3-7)

(a) Mission support for launches and landings

(b) Toxic dispersion boundary limit predictions

(c) Rocket exhaust effluent dispersion prediction

(d) Hurricane forecasting

(e) Funnel cloud, storm warning

(f) O&M of all weather systems on KSC except LC-39 A & B

    1.  **Remote Site Tracking Network**

Services include seven separate ranges providing tracking services to
the Shuttle Program with an average of ten radars required to support a
Shuttle mission. The number of ranges involved along with the number of
radars varies to accommodate mission requirements.

2.  **Hold Down Post Load Calibration**

This calibration is performed in the LETF and provides data to be used
by the STS Loads Panel to determine the stress distribution in the SRM
aft skirts.

3.  **SRM Lifting Beams and Associated Equipment Annual Proofload**
    **Tests**

These annual load tests are performed on the 600 Ton test fixture
located in the LETF.

4.  **Biomedical Laboratory**

Support for: OMIs S-0007, S-0028, and S-0017 and requirements generated
in the Connector Integrity Group (CIG) log; environmental and ecological
impacts; modeling of contamination in environmental media; review of
environmental impact checklist and facility siting submissions;
operation of the Environmental Evaluation Console, interpretation of the
outputs from the exhaust cloud prediction model, coordination of cloud
tracking photography, and development and distribution of "quick look"
and final reports; testing of the ECLESS potable water, detection and
recovery of microorganisms, microbial surface and air sampling inside
the Orbiter; clinical laboratory support for the flight crew and the
prime crew contacts.

5.  **Material Sciences Laboratory**

The contractor may also submit task requests for mechanical, electrical
or electronic component failure analysis and material identification/
characterization and chemical process related anomalies. From the
Microchemical Analysis Branch (MAB), Failure Analysis and Materials
Evaluation Branch (FAMEB) and White Sands Test Facility, services also
include material certification for use in GSE, Facilities, and systems
that are required to support the processing of flight hardware.

6.  **Instrumentation and Controls Laboratory**

Services include support in the resolutions of hardware problems
relating to LPS and PMS transducers and signal conditioners through the
use of scientific, technological, and engineering approaches between the
laboratory, field, systems users, and manufacturer.

7.  **Utilities**

Water, electricity, natural gas, propane, sewage treatment, and fuel oil
will be provided by the government to the contractor's assigned
facilities. Chilled water, high temperature hot water, and compressed
air are provided to the contractor's assigned facilities by the
government from the Utility Annex, Industrial Area Chiller Plant,
Hypergol Maintenance Facility Heat Plant, and the Central Heat Plant.

8.  **Flight Crew Rescue**

Services include Orbiter Flight Crew Rescue for the Launch Pads (Modes
III and IV) during launch, the SLF (Mode VI) and KSC (Mode VII) during
launch and landing. The Pad Team responds to and aides in egress/rescue
of the Flight Crew, Close-out Crew, or any Red Crew that needs
assistance in the event of an emergency. The SAR Team aides in
egress/rescuing the Flight Crew at the SLF and within a 25 mile radius
of the SLF on KSC, excluding the ocean. The DOD provides sea rescue.

9.  **Electromagnetic Measurement and Analysis (EMA)**

EMA services provided include electromagnetic compatibility, frequency
control and analysis, and payload re-radiation antenna system O&M and
test support. STS flow and landing support includes radar transponder
tests, press site RF surveillance, range command spectrum monitoring,
and communications/nav. aids spectrum monitoring.

10. **Life Support Maintenance**

Life support equipment and training will be provided by the government.
The contractor is responsible for suiting of contractor operators.

11. **Runway/Aviation**

Services include O&M for the SLF (except landing aids and other
contractor O&M responsibilities specified in Attachment J-9) and
operation of the Landing Aids Control Building. The SLF is operational
two shifts per day, seven days per week with the control tower activated
first shift, five days per week. Additional operating hours are
scheduled as required to support contractor activities.

12. **Railroad Operations**

Government provided services include the O&M of all railroad
locomotives, cars and equipment and the movement of all railroad cars on
KSC in support of contractor operations, and in the event of any
unforeseen contingency movement or emergency evacuation of any RSRM
railcars from KSC property. Provided services also include maintaining
two specially constructed SRB component railcars identified as NLAX 170
and NLAX 171, for the exclusive use of the SRB Manufacturing, Assembly
and Refurbishment Project, including managing and funding all aspects of
the cross-country use.

13. **Communications Services**

Services provided by the government:

1.  Audio services including administrative telephones and secure voice,
    Paging and Area Warning (P&AWS), operational voice (OIS, Astrocomm,
    TAL Site communications), radio systems (RF Comm) and voice
    recording systems.

2.  Video services including operational television (OTV), Broadband
    institutional television (BCDS), and public affairs television.

3.  Transmission services including T-Carrier, SONET, ATM, and wideband
    fiber optics (PCO).

4.  Institutional network services (KNET).

5.  Cable plant support services including building premises wiring,
    inside and outside plant (fiber optic and copper cables). Timing and
    Countdown Systems support.

The following communications services will be provided for the ARF and
PRF Complexes on KSC:

1.  Services shall be provided to maintain all telephones and telephone
    lines (outside and inside plant) throughout the ARF and PRF
    Complexes.

2.  Services shall be provided to maintain all TV, Data and P&AW up to
    the ARF Building Terminating Strips on the ground floor of the E&A
    Building and the Motor Control Center at the PRF.

3.  Services shall be provided to maintain the OIS system with the
    exception of the SRB Manufacturing Process OIS system.

4.  Services shall be provided to install and maintain BCDS systems
    throughout the ARF and PRF Complexes.

    1.  **Roads and Grounds**

Services provided include maintenance and repair of roads, ditches, and
water retention areas. Also included are trash collection and disposal,
pest control (interior and exterior of all facilities including the ARF
and PRF complexes, and mosquito fogging at the ARF and PRF complexes),
and mowing. Grass mowing at the ARF and PRF shall be outside the fence
perimeter and between the ARF north fence line and Schwartz Road.
Services include application of herbicide at the ARF and PRF perimeter
fence lines.

2.  **Unified S-Band**

Services include Space Flight Tracking and Data Network (STDN)
communications support for spacecraft checkout, launch, ascent and
orbital phases of Shuttle Missions.

3.  **SPECSINTACT**

Facility and facility system design specifications are maintained
current and provided to the contractor in electronic form and hard copy.

4.  **Firefighting**

The government provides 24 hour/7 day firefighting capabilities for all
contractor facilities and operations. Services include rescue, fire
prevention planning, and fire engineering. Fire alarms and suppression
systems maintenance is also provided by the government except for
contractor assigned firex and deluge systems. Fire alarms and Fire
Suppression systems at the ARF and PRF complexes are maintained by the
contractor.

5.  **KSC Security**

Services include perimeter control, traffic control, locksmith, badging,
PRP, ESS and all requirements for armed security. Positive internal
access control required by the contractor is provided by the contractor.

6.  **Mail**

Routine mail and distribution services are provided once daily to all
contractor offices. An on-site branch U.S. Post Office is provided with
full customer services, including remote stamp vending machines and mail
drops as well as mail transportation between KSC and Orlando
International Airport.

7.  **Library**

Reference and loan materials are provided for information on basic and
applied research pertaining to aeronautics and space science technology.
Services include storage, retrieval, and dissemination of contractor
requested materials.

8.  **Janitorial**

Services include cleaning of offices, corridors, restrooms, conference
rooms, stairwells, lobbies, break rooms, and food service areas, except
for the ARF and PRF Complexes. The contractor is responsible for
cleaning assigned operational/technical areas and clean rooms.

9.  **Bus Service**

Bus service is provided on a weekday, first shift schedule between the
major areas of KSC and CCAS for use by all contractor personnel.

10. **Sandblast Shop**

Blasting and coating services are provided using a variety of blasting
media by NACE certified personnel. The contractor will deliver items to
the sandblast shop for service.

11. **CLS Support**

Security services are provided at TAL sites for the planning, surveys,
and training of security personnel required for the protection of
government property. In the event of a TAL site landing, security is
provided throughout the recovery/turnaround operations.

12. **Medical Support**

Services include a comprehensive Occupational Medicine and Environmental
Health Program (except the Contractor Environmental Health
responsibilities specified in the RFP), and environmental surveys.
Occupational Medicine includes physical examinations, health education,
emergency medical treatment, employee assistance counseling, and medical
training. Environmental Health includes industrial hygiene health
physics, and sanitation and pollution control. (Reference KNPD 1810.1.)
Ambulance service to off site hospitals is provided as needed.

13. **Performance Oriented Packaging**

Services provided include maintenance and operation of a facility for
the testing of packaging to be used in the transport of hazardous
materials.

14. **Excess Property Disposal**

Services include the receipt and disposal of excess property for
contractors and other government organizations.

15. **KSC Computer Aided Engineering System**

Support from the Data Processing System (DPS) for data acquisition,
reduction, analysis, and historical storage of launch data, and from the
Engineering Analysis System (EAS) and Intergraph System (IGS) for
computational and graphics support in the disciplines of electrical,
mechanical, civil, electronics and architectural engineering will be
provided. This support will be provided at a level consistent with
current support at KSC through October 1997, after which time the
contractor may procure these services.

16. **Transportation Services**

Government Bills of Lading (GBL): GBL\'s for shipment of government
property located on site and off site.

17. **Cape Canaveral Air Force Station Facilities**

Services at CCAFS Facilities shall include janitorial, standby medical,
crane and power doors maintenance; building maintenance; lighting, HVAC,
and high and low voltage distribution.

18. **Pneumatics, Fluid and Gas**

Services shall include pneumatic services to maintain GN2 bottles at
Hangar AF. Pickup and delivery of fluid and gas shall be provided except
breathing air and commercial chemicals.

19. **Tool Crib**

Use of the KSC Tool Loan Services on an \"as available basis\" shall be
provided. Contractor shall furnish special tools.

20. **Heavy Equipment**

KSC heavy equipment shall be provided on an \"as available basis\".
Heavy equipment and generators, 30 kw and larger, require the contractor
sub‑authorization for operations.

21. **Reserved**

22. **General Services**

General services such as badging, locksmith services, food services, and
duty officer shall be provided.

23. **Computer Services**

The government will furnish computer services to the contractor for
required Solid Rocket Booster activities during the period of
performance of this contract, including but not limited to the
following:

1.  Computer processing access.

```{=html}
<!-- -->
```
a)  BLOC: Analog to digital telemetry data reduction for post flight
    assessment; workstation access for real-time shuttle flight
    assessment support.

b)  Droid 5: Post flight processing of SRB elements performed by
    USA-managed system, Droid 5.

c)  MAPTIS: Materials and Processes Technical Information System
    (MAPTIS) for all SRB materials; mass properties analyses (located at
    MSFC).

```{=html}
<!-- -->
```
2.  Network services.

```{=html}
<!-- -->
```
a)  Reserved

b)  TCP/IP: Mail/enclosures and file transfers.

c)  Data circuits: Transmission between MSFC and contractor SRB element,
    and between contractor SRB element locations at KSC, Huntsville, and
    other locations; corporate data processing; Still Video
    transmission.

d)  Mail network access: Electronic mail connections to NASA and other
    prime contractors.

e)  SMTP communications: Maintenance of protocols to interface with
    multiple mail systems.

f)  Video teleconferencing.

g)  NASA Select video signal input.

```{=html}
<!-- -->
```
3.  RAIOS document repository.

```{=html}
<!-- -->
```
a)  Document storage and imaging.

b)  Access to MSFC forms.

```{=html}
<!-- -->
```
4.  WebPCASS

> Access to Johnson Space Center trouble reports.

5.  MPCAS

> Problem and corrective action items.

1.  **SRB Element General**

For purposes of determining the available base support services from KSC
or from the Joint Base Operations Support Contractor (JBOSC), the
contractor shall refer to the following referenced documents for SRB
Element Base Support Services:

> SA45‑025‑91‑RK Letter (05/24/91)
>
> KCA-1777 MSFC/KSC MOA, latest revision (02/04/04)

ATTACHMENT J-10-C

INSTALLATION PROVIDED SERVICES

MARSHALL SPACE FLIGHT CENTER

In accordance with the Installation Provided Government Property clause
of this Contract, the Contractor is authorized use of the types of
property and services listed below, and to the extent they are
available, while on site at the NASA installation.

The responsibilities of the Contractor as contemplated by the
Installation-Provided Government clause are defined in the following:

**NFS 1852.245-77, LIST OF INSTALLATION-ACCOUNTABLE PROPERTY AND
SERVICES (JUL 1997)**

In accordance with the clause at 1852.245-71, Installation-Accountable
Government Property, the Contractor is authorized use of the types of
property and services listed below, to the extent they are available, in
the performance of this contract within the physical borders of the
installation which may include buildings and space owned or directly
leased by NASA in close proximity to the installation, if so designated
by the Contracting Officer.

(a) Office space, work area space, and utilities. Government telephones
    are available for official purposes only; pay telephones are
    available for contractor employees for unofficial calls.

(b) General- and special-purpose equipment, including office furniture.

```{=html}
<!-- -->
```
(1) Equipment to be made available is listed in Attachment J-9-C-1. The
    Government retains accountability for this property under the clause
    at 1852.245-71, Installation-Accountable Government Property,
    regardless of its authorized location.

(2) If the Contractor acquires property, title to which vests in the
    Government pursuant to other provisions of this contract, this
    property also shall become accountable to the Government upon its
    entry into Government records as required by the clause at
    1852.245-71, Installation-Accountable Government Property.

(3) The Contractor shall not bring to the installation for use under
    this contract any property owned or leased by the Contractor, or
    other property that the Contractor is accountable for under any
    other Government contract, without the Contracting Officer\'s prior
    written approval.

```{=html}
<!-- -->
```
(c) Supplies from stores stock.

(d) Publications and blank forms stocked by the installation.

(e) Safety and fire protection for Contractor personnel and facilities.

(f) Installation service facilities: See Attachment J-9-C-5.

(g) Medical treatment of a first-aid nature for Contractor personnel
    injuries or illnesses sustained during on-site duty.

(h) Cafeteria privileges for Contractor employees during normal
    operating hours.

(i) Building maintenance for facilities occupied by Contractor
    personnel.

(j) Moving and hauling for office moves, movement of large equipment,
    and delivery of supplies. Moving services shall be provided on-site,
    as approved by the Contracting Officer.

(k) The user responsibilities of the Contractor are defined in
    paragraph (a) of the clause at 1852.245-71, Installation-Accountable
    Government Property.

(End of clause)

ATTACHMENT J-10-D

INSTALLATION PROVIDED SERVICES

WHITE SANDS TEST FACILITY

1.  Repair and/or testing of Logistics assets (hardware and components)
    for which the facility has been certified, including Thrusters, OMS
    Engines, OMS Tank, AC Motor and Manual Valves, Relief Valves, Burst
    Disks, Quad Check Valves, Hydrogen Recirculation Pumps.

2.  Hardware/component compatibility testing for commodities including
    oxygen, hydrogen, N~2~O~2~, hypergolic, helium.

ATTACHMENT J-10-E

INSTALLATION PROVIDED SERVICES

WRIGHT PATTERSON AIR FORCE BASE

1.  Pre-roll and shearography testing for the orbiter tires.

ATTACHMENT J-10-F

INSTALLATION PROVIDED SERVICES

DRYDEN FLIGHT RESEARCH CENTER

1.  The Installation Provided Services to be provided at Dryden Flight
    Research Center (DFRC) are encapsulated in the following:

**LIST OF INSTALLATION-ACCOUNTABLE PROPERTY AND SERVICES (NFS
1852.245-77) (JUL 1997)**

In accordance with the clause at 1852.245-71, Installation- Accountable
Government Property, the Contractor is authorized use of the types of
property and services listed below, to the extent they are available, in
the performance of this contract within the physical borders of the
installation which may include buildings and space owned or directly
leased by NASA in close proximity to the installation, if so designated
by the Contracting Officer.

(a) Office space, work area space, and utilities. Government telephones
    are available for official purposes only; pay telephones are
    available for contractor employees for unofficial calls.

(b) General- and special-purpose equipment, including office furniture.

```{=html}
<!-- -->
```
(1) Property to be made available is listed in Attachment J-9. The
    Government retains accountability for this property under the clause
    at 1852.245-71, Installation- Accountable Government Property,
    regardless of its authorized location.

(2) If the Contractor acquires property, title to which vests in the
    Government pursuant to other provisions of this contract, this
    property also shall become accountable to the Government upon its
    entry into Government records as required by the clause at
    1852.245-71, Installation-Accountable Government Property.

(3) The Contractor shall not bring to the installation for use under
    this contract any property owned or leased by the Contractor, or
    other property that the Contractor is accountable for under any
    other Government contract, without the Contracting Officer\'s prior
    written approval.

```{=html}
<!-- -->
```
(c) Supplies from stores stock.

(d) Publications and blank forms stocked by the installation.

(e) Safety and fire protection for Contractor personnel and facilities.

(f) Installation service facilities: Travel Office and Backshop Support.

(g) Medical treatment of a first-aid nature for Contractor personnel
    injuries or illnesses sustained during on-site duty. Access to
    medical facilities for job related physicals.

(h) Cafeteria privileges for Contractor employees during normal
    operating hours.

(i) Building maintenance for facilities occupied by Contractor
    personnel.

(j) Moving and hauling for office moves, movement of large equipment,
    and delivery of supplies. Moving services shall be provided on-site,
    as approved by the Contracting Officer.

(k) The user responsibilities of the Contractor are defined in
    paragraph (a) of the clause at 1852.245-71, Installation-
    Accountable Government Property.

(End of Clause)

10.2 The following services are also provided:

(a) DFRC will provide facility and support services to the Contractor as
    outlined in the current Launch and Landing program Requirements
    Document.

(b) DFRC will provide in place support for the operation and maintenance
    of the MDD, generators, support equipment, vehicles, communications
    and landing aids. The Contractor will be responsible for engineering
    support, major repairs and overhauls (greater than \$50), and
    sustainability of these elements (excluding communications and MSBLS
    support equipment).

(c) DFRC will provide to the Contractor available support equipment
    (such as aerial lift, forklifts). The Contractor will be responsible
    for supplying like equipment if not available from DFRC resources.

ATTACHMENT J-10-G

INSTALLATION PROVIDED SERVICES

WHITE SANDS SPACE HARBOR

-   White Sands Space Harbor (WSSH) will provide facility and support
    services to the Contractor as outlined in the current Launch and
    Landing Program Requirements Document.

-   WSSH will provide in place support for the operation and maintenance
    of generators, support equipment, vehicles, communications and
    landing aids. The Contractor will be responsible for engineering
    support, major repairs and overhauls (greater that \$150), and
    sustainability of these elements (excluding communications and TACAN
    and support equipment).

-   WSSH will provide to the Contractor available support equipment
    (such as aerial lift, forklifts). The Contractor will be responsible
    for supplying like equipment if not available from WSSH resources.

ATTACHMENT J-11

APPLICABLE NASA POLICIES AND PROCEDURES

  ----------------- -------------------------------------------- ------------------
  Attachment Number Title                                        Page

  J-11-A            NASA Agencywide Policies and Procedures      J-11-[2](#J11A)

  J-11-B            Johnson Space Center Policies and Procedures J-11-[8](#j11b)

  J-11-C            Kennedy Space Center Policies and Procedures J-11-[9](#j11c)

  J-11-D            Marshall Space Flight Center Policies and    J-11-[12](#j11d)
                    Procedures                                   

  J-11-E            RESERVED                                     J-11-[13](#j11e)

  J-11-F            Dryden Flight Research Center Policies and   J-11-[14](#j11f)
                    Procedures                                   
  ----------------- -------------------------------------------- ------------------

ATTACHMENT J-11-A

NASA AGENCYWIDE POLICIES AND PROCEDURES

A.  The following policies and procedures apply to work performed on
    NASA centers and other field installations:

[NASA POLICY DIRECTIVES]{.underline}

  ---------------- ------------------------------------------------------
  NPD 1040.4       NASA Continuity of Operations

  NPD 1440.6       NASA Records Management

  NPD 1490.1       NASA Printing, Duplicating, Copying, Forms and Mail
                   Management

  NPD 1600.2       NASA Security Policy

  NPD 1660.1       NASA Counterintelligence (CI) Policy

  NPD 2540.1       Personal Use of Government Office Equipment Including
                   Information Technology

  NPD 2800.1       Managing Information Technology

  NPD 2810.1       NASA Information Security Policy

  NPD 2820.1       NASA Software Policy (Applicable only to software
                   developments or software procurements that are
                   entirely new, not upgrades to existing systems, valued
                   at over \$2 million, and are for delivery as products
                   to NASA for NASA use.)

  NPD 4100.1       Supply Support and Material Management Policy

  NPD 4200.1       Equipment Management

  NPD 4300.1       NASA Personal Property Disposal Policy

  NPD 4300.4       Use of Space Shuttle and Aerospace Vehicle Materials
                   as Mementos

  NPD 8010.2       Use of the SI (Metric) System of Measurement in NASA
                   Programs

  NPD 8500.1       NASA Environmental Management

  NPD 8710.1       NASA Emergency Preparedness Program

  NPD 8710.5       NASA Safety Policy for Pressure Vessels and
                   Pressurized Systems

  NPD 8800.14      Policy for Real Property Management

  NPD 8820.3       Facility Sustainable Design

  NPD 8831.1       Maintenance of Institutional and Program Facilities
                   and Related Equipment

  NPD 9501.1       NASA Contractor Financial Management Reporting System
  ---------------- ------------------------------------------------------

[NASA PROCEDURAL REQUIREMENTS AND STANDARDS]{.underline}

  ---------------- ------------------------------------------------------
  NPR 1441.1       NASA Records Retention Schedules

  NPR 1490.1F      NASA Printing, Duplicating, and Copying, Forms, and
                   Mail Management

  NPR 1600.1       NASA Security Program Procedural Requirements (Dated
                   11/03/04)

  NPR 1620.2       Physical Security Vulnerability Risk Assessments

  NPR 1620.3       Physical Security Requirements for NASA Facilities and
                   Property

  NPR 1660.1       Counterintelligence (CI)/Counterterrorism (CT)
                   Procedural Requirements

  NPR 2800.1       Managing Information Technology

  NPR 2810.1A      Security of Information Technology

  NPR 4100.1       NASA Materials Inventory Management Manual

  NPR 4200.1       NASA Equipment Management Manual

  NPR 4200.2       Equipment Management Manual for Property Custodians

  NPR 4300.1       NASA Personal Property Disposal Procedural
                   Requirements

  NPR 4310.1       Identification and Disposition of NASA Artifacts

  NPR 5200.1       Industrial Labor Relations Manual

  NPR 6000.1       Requirements for Packaging, Handling, and
                   Transportation for Aeronautical and Space Systems,
                   Equipment and Associated Components

  NPR 7120.5C      NASA Program and Project Management Processes and
                   Requirements

  NPR 8000.4       Risk Management Procedural Requirements

  NPR 8553.1       NASA Environmental Management System (EMS)

  NPR 8570.1       Energy Efficiency and Water Conservation

  NPR 8715.1       NASA Safety and Health Handbook Occupational Safety
                   and Health Programs

  NPR 8715.3       NASA Safety Manual

  NPR 8715.4       Inservice Inspection of Ground-Based Pressure Vessels
                   and Systems (3/29/04)

  NPR 8735.1       Procedures for Exchanging Parts, Materials, and Safety
                   Problem Data Utilizing the Government-Industry Data
                   Exchange Program and NASA Advisories

  NPR 8800.15      Real Estate Management Program Implementation Manual

  NPR 8820.2       Facility Project Implementation Guide

  NPR 8831.2       Facilities Maintenance Management

  NPR 9501.2       NASA Contractor Financial Management Reporting

                   
  ---------------- ------------------------------------------------------

[OTHER NASA POLICY ISSUANCES]{.underline}

NASA Guidance for Implementation of Executive Order 12856, Federal
Compliance with Right-to-Know Laws and Pollution Prevention Requirements
and Related Environmental Executive Orders (December 1994)

NASA Environmental Justice Strategy (March 1995)

Technical Memorandum 108606, NASA Metric Transition Plan (February 10,
1992)

[POLICY ISSUANCES EXTERNAL TO NASA]{.underline}

  ------------------------ ----------------------------------------------
  Executive Order 13123    Greening the Government Through Efficient
                           Energy Management

  Executive Order 13148    Greening the Government Through Leadership in
                           Environmental Management

  SAE, AS9100              Quality Management Systems- Aerospace
                           Requirements

  ANSI/ISO/ASQ Q9001-2000  American National Standard Quality Management
                           System - Required

  ANSI/NCSL Z540-1-1994    Calibration Laboratories and Measuring and
                           Test Equipment
  ------------------------ ----------------------------------------------

B.  

  ---------------- ------------------------------------------------------
                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   
  ---------------- ------------------------------------------------------

  ---------------- ------------------------------------------------------
                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   

                   
  ---------------- ------------------------------------------------------

  ------------------------ ----------------------------------------------
                           

                           

                           

                           

                           
  ------------------------ ----------------------------------------------

ATTACHMENT J-11-B

[]{#j11b .anchor}JOHNSON SPACE CENTER POLICIES AND PROCEDURES

The following policies and procedures apply only to work performed at
JSC:

[JOHNSON PROCEDURAL DIRECTIVES]{.underline}

  ---------------- ------------------------------------------------------
  JPD 1620.1       Establishment of Security Areas at JSC

  JPD 1710.1       Design, Inspection, and Certification of Pressure
                   Vessels and Pressurized Systems

  JPD 2314.2       Managing Internal JSC Documents

  JPD 8080.2       JSC Design and Procedural Standards

  JPD 8500.1       JSC Environmental Excellence Policy

  JPD 8820.2       Facility Construction, Rehabilitation, Modification,
                   and Repair
  ---------------- ------------------------------------------------------

[JOHNSON POLICY GUIDELINES AND PROCEDURAL REQUIREMENTS]{.underline}

  ---------------- ------------------------------------------------------
  JPR 1700.1       JSC Safety and Total Health Handbook

  JPR 1710.13      Design, Inspection, and Certification of Pressure
                   Vessels and Pressurized Systems

  JPR 8080.5       JSC Design and Procedural Standards

  JPR 8550.1       JSC Environmental Compliance Procedural Requirements

  JPR 8553.1       JSC Environmental Management System (EMS) Manual
  ---------------- ------------------------------------------------------

[OTHER POLICIES AND PROCEDURES]{.underline}

  ---------------- ------------------------------------------------------
  JSC 17773        Instruction for Preparation of Hazard Analyses for JSC
                   Ground Operations

  JSC 26549        Control of Program Stock - Customer

  JSC 27301        Materials Control Plan for JSC Flight Hardware

  JSC 28484        Program Requirements Document for Johnson Space Center
                   Non Critical Government Furnished Equipment
  ---------------- ------------------------------------------------------

ATTACHMENT J-11-C

[]{#j11c .anchor}KENNEDY SPACE CENTER POLICIES AND PROCEDURES

A.  The following policies and procedures apply only to work performed
    at KSC:

[KENNEDY PROCEDURAL DIRECTIVES]{.underline}

  ---------------- ------------------------------------------------------
  KNPD 1150.24     KSC Councils, Boards and Committees

  KNPD 1216.1      Smoke-Free Workplace

  KNPD 1420.1      KSC Forms Management Program

  KNPD 1440.1      KSC Records Management and Vital Records Program

  KNPD 1490.2      Printing, Duplicating, Micrographics and Office Copier
                   Services

  KNPD 1530.1      KSC Mail Management Program and Locator Directory

  KNPD 1590.2      KSC Bulletin, Bulletin Boards and Hallway Displays

  KNPD 1800.1      Environmental Health Program

  KNPD 1800.2      KSC Hazard Communication Program

  KNPD 1810.1      KSC Occupational Medicine Program

  KNPD 1860.1      KSC Radiation Protection Program

  KNPD 3792.1      Employee Assistance Program (EAP)

  KNPD 8500.1      KSC Environmental Management
  ---------------- ------------------------------------------------------

[KENNEDY HANDBOOKS AND PROCEDURAL REQUIREMENTS]{.underline}

  ---------------- ------------------------------------------------------
  JHB 2000         Consolidated Comprehensive Emergency Management Plan
                   (CCEMP)

  KNPR 1040.3      Continuity of Operations Planning (COOP) Procedural
                   Requirements

  KNPR 1600.1      KSC Security Procedural Requirements

  KNPR 1820.3      KSC Hearing Loss Prevention Program

  KNPR 1820.4      KSC Respiratory Protection Program

  KNPR 1840.19     KSC Industrial Hygiene Programs

  KNPR 1860.1      KSC Ionizing Radiation Protection Program

  KNPR 1860.2      KSC Non-Ionizing Radiation Protection Program

  KNPR 1870.1      KSC Sanitation Handbook

  KNPR 2540.1      KSC Telecommunications Services

  KNPR 2570.1      KSC Radio Frequency Spectrum Management Procedural
                   Requirement

  KNPR 4000.1      Supply and Equipment System Manual, Chapter 5,
                   Equipment Management

  KNPR 6000.1      Transportation Support System Manual

  KNPR 8040.4      International Space Station/Payload Processing
                   Configuration Management Procedural Requirements

  KNPR 8072.1      KSC Materials and Processes (M&P) Control Procedural
                   Requirements

  KNPR 8500.1      KSC Environmental Requirements

  KNPR 8630.3      KSC Shuttle Processing Flight Readiness/Certification
                   Review Plan

  KNPR 8715.3      Kennedy Space Center Safety Practices Procedural
                   Requirements

  KNPR 8720.1      Reliability, Maintainability and Quality Assurance
                   Procedural Requirement

  KNPR 8830.1      Facilities and Real Property Management Procedural
                   Requirements
  ---------------- ------------------------------------------------------

[KENNEDY GENERAL PROCEDURES]{.underline}

  ----------------- -----------------------------------------------------
  KSC-CCAFS-6747    Cape Canaveral Spaceport Facilities

  GP-14-3           Facilities Space Control Document, Single Wide
                    Trailers/Boxcars, Launch Complex 39 Facilities,
                    Merritt Island Industrial Area Facilities, and Cape
                    Area Facilities
  ----------------- -----------------------------------------------------

[OTHER POLICIES AND PROCEDURES]{.underline}

  ---------------- ------------------------------------------------------
  KSC-DE-512-SM    Facility, System, and Equipment General Design
                   Requirements

  ---------------- ------------------------------------------------------

[POLICY ISSUANCE'S EXTERNAL TO KSC]{.underline}

  ------------------------------ ----------------------------------------
  ESMC Regulation 127-1          Range Safety Manual

  (ESMC = USAF Eastern Space and 
  Missile Center)                

  45th Space Wing Instruction    Radiation Protection Program
  40-201                         
  ------------------------------ ----------------------------------------

[ESMC/KSC JOINT OPERATING PROCEDURES (JOP)]{.underline}

  ------------------- ---------------------------------------------------
  15E-2-2 (KCA 1354)  Joint Operating and Support Agreement Between ESMC
                      and KSC

  15E-2-8 (KCA 1305)  Missile/Space Vehicle Safety

  15E-3-2 (KCA 1358)  Labor Relations

  15E-3-7 (KCA 1105)  Meteorological Support

  15E-3-9 (KCA 1284)  Communications Support

  15E-3-11 (KCA 1311) Coordination of Actions in Hurricane or Tropical
                      Storm Emergency

  15E-3-14 (KCA 1308) Joint Operating Procedure Between 45th Space Wing
                      and JFK Space Center for Safety (45 SW 15E-3-14)

  15E-3-35 (KCA 1333) Joint Operating Procedure Between 45th Space Wing
                      and JFK Space Center for Public Affairs and
                      Protocol Activities (45 SW 15E-3-35)
  ------------------- ---------------------------------------------------

B.  The following policies and procedures are for reference when
    performing work at KSC:

  --------------- --------------------------------------------------------
  K-STSM-14.1     Launch Site Accommodations Handbook for Payloads

  K-STSM-14.2.1   KSC Cargo Facility Contamination Control
                  Requirements/Plan

  79K09579        KSC Facilities, Systems, and Equipment Organizational
                  Level OMD (Baseline)
  --------------- --------------------------------------------------------

ATTACHMENT J-11-D

[]{#j11d .anchor}MARSHALL SPACE FLIGHT CENTER POLICIES AND PROCEDURES

The following policies and procedures apply only to work performed at
MSFC:

[MARSHALL PROCEDURAL REQUIREMENTS]{.underline}

  -------------- --------------------------------------------------------
  MPR 1040.3     MSFC Emergency Plan

  MPR 1600.1     MSFC Security Procedural Requirements

  MPR 2500.1     Marshall Telecommunication Services and Audio Visual
                 Services

  MPR 2810.1     Security of Information Technology

  MPR 6700.1     Motor Vehicle and Motor Pool Operations

  MPR 8500.1     MSFC Environmental Management Program

  MPR 8715.1     Marshall Safety, Health, and Environmental (SHE) Program

  MPR 8812.1     Requests for Facility Services at MSFC
  -------------- --------------------------------------------------------

[MISCELLANEOUS POLICIES AND PROCEDURES]{.underline}

  -------------- --------------------------------------------------------
  MPD 1800.1     MSFC Smoking Policy

  MWI 2210.1     MSFC Documentation Repository Input/Output and Data
                 Management Project Requests
  -------------- --------------------------------------------------------

ATTACHMENT J-11-E

[]{#j11e .anchor}RESERVED

ATTACHMENT J-11-F

[]{#j11f .anchor}DRYDEN FLIGHT RESEARCH CENTER POLICIES AND PROCEDURES

The following policies and procedures apply only to work performed at
DFRC:

[DRYDEN POLICY DIRECTIVES AND PROCEDURAL REQUIREMENTS]{.underline}

  -------------- --------------------------------------------------------
  DPD 1610.1     Personal Identification -- Badges and Passes

  -------------- --------------------------------------------------------

ATTACHMENT J-12

RESERVED

ATTACHMENT J-13

MAKE OR BUY PLAN

WITHHELD FOIA EXEMPTION (b)(4)

  ------------------------- ----- ------ --------- -----------------------
                                                   

                                                   

                                                   

                                                   

                                                   
  ------------------------- ----- ------ --------- -----------------------

Error: Reference source not found (continued)

  ------------------------- ----- ------ --------- -----------------------
                                                   

                                                   

                                                   

                                                   

                                                   

                                                   

                                                   

                                                   

                                                   

                                                   

                                                   
  ------------------------- ----- ------ --------- -----------------------

Error: Reference source not found (concluded)

+-------------------------+----+-----+--------+-----------------------+
| Major item/work effort  | Mu | M   | Can    | Remarks               |
|                         | st | ust | either |                       |
|                         | ma | buy | ma     |                       |
|                         | ke |     | ke/buy |                       |
+=========================+====+=====+========+=======================+
|                         |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+
|                         |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+
|                         |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+
| -                       |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+
| -                       |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+
|                         |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+
|                         |    |     |        |                       |
+-------------------------+----+-----+--------+-----------------------+

Table 7.4.3-1.

Table 7.4.3‑1. Source listing of subcontracted work effort

  ------------------------------- ------------------------------ ---------
                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 

                                                                 
  ------------------------------- ------------------------------ ---------

ATTACHMENT J-14

SMALL BUSINESS SUBCONTRACTING PLAN

CONTENTS

Section Page

[11.1 INTRODUCTION J-14-26](#__RefHeading___Toc144610404)

> [11.1.1 Subcontracting Plan Administration
> J-14-26](#__RefHeading___Toc144610405)
>
> [11.1.2 Subcontracting Plan Goals
> J-14-26](#__RefHeading___Toc144610406)
>
> [11.1.3 Description Of Efforts J-14-26](#__RefHeading___Toc144610407)
>
> [11.1.4 Clause Flow Down J-14-26](#__RefHeading___Toc144610408)
>
> [11.1.5 Subcontractor Performance
> J-14-26](#__RefHeading___Toc144610409)
>
> [11.1.6 Reports and Surveys J-14-26](#__RefHeading___Toc144610410)
>
> [11.1.7 Records J-14-26](#__RefHeading___Toc144610411)

*United Space Alliance\'s Small Business Subcontracting Plan calls for
proactive, meaningful participation and motivation to provide the
maximum practicable utilization of Small Businesses.*

# 11.1 INTRODUCTION

USA and its subcontractors are committed to support NASA's Small
Business program. It is the policy of USA to exert its best effort to
ensure that subcontracts awarded be made available to Small Business
(SB), Small Disadvantaged Business (SDB), Woman-Owned Small Business
(WOSB), Historically Black Colleges and Universities/Minority
Institutions (HBCU/MI), Historically Underutilized Business Zone Small
Business (HUBZone), Veteran Owned Small Business (VOSB), and
Service-Disabled Veteran-Owned Small Business (SDVOSB) concerns. In
consideration of NASA's goals of Operational Safety, Mission Success and
Schedule, and Cost Reduction, USA's Small Business Program will retain a
major focus within the company.

USA will strive to support this objective through semi-annually
established subcontracting goals. NASA's Contract Clause H.3 is hereby
interwoven into this USA Small Business Subcontracting Plan, and is
intended to be compliant to both FAR 52.219-9 (Sept 2006) and
contract-stated goals.

For purposes of this plan, references to Small Business will include
Small Business (SB), Small Disadvantaged Business (SDB), Woman-Owned
Small Business (WOSB), Historically Black Colleges and
Universities/Minority Institutions (HBCU/MI), Historically Underutilized
Business Zone Small Business (HUBZone), Veteran Owned Small Business
(VOSB), and Service Disabled Veteran Owned Small Business (SDVOSB)
concerns.

# Subcontracting Plan Administration

The Vice President of Logistics and Material, a direct report to USA's
President and Chief Executive Officer, coordinates the implementation of
this plan and monitors/manages the Small Business Program performance.
Procurement Management also provides guidance to assure administrative
advocacy, consistency in subcontracting, and conformance with company
procedures.

Procurement Management provides the following support:

. Establish and implement procedures for SB programs that will provide
subcontractors the opportunity to compete equitably for the procurement
of goods and services.

. Ensure procedures are consistent with sound procurement policies,
contractual requirements, and Federal procurement regulations.

. Maintain surveillance over program status and activities, assuring
affirmative implementation and compliance with contractual requirements,
and cooperative responses to requests for data.

. Maintain visibility of SB subcontracting activities and
accomplishments in company and external media.

The Vice President of Logistics and Material identifies administrators
of this plan who are given the responsibility for the development of
procedures to ensure that an effective Small Business Program is
implemented. The administrators' responsibilities are as follows:

. Assist in the preparation and negotiation of the Subcontracting Plan
with the cognizant Contracting Officer (CO).

. Assist in the preparation of individual Subcontracting Plans and the
establishment of goals as required by prime contracts.

. Counsel and discuss subcontracting opportunities with representatives
of small business concerns.

. Ensure an equitable opportunity for SBs to compete for goods and
services by:

. Assisting in the early planning stages of procurement requirements.

. Identifying SB candidates using available directories, publications,
supplier evaluation records, and various search engines.

. Encouraging the placement of a fair portion of total acquisitions for
goods and services with SBs.

. Assisting with the identification of potential commodities or service
types for possible set-aside consideration.

. Maintain and make available to all buyers current source data files
and reference materials consisting of Government, company, and local
publications.

. Assist buyers in locating SBs.

. Provide contractually-required reports, and submit as necessary.

. Receive written notification of the approved prime contract
subcontracting plan from the CO.

. Maintain a copy of individual plans for the local U.S. Small Business
Administration (SBA) cognizant specialist.

. Conduct training for program and procurement representatives involved
in the performance of the prime contract. This training addresses the
following topics:

. Percentage goals

. Categories of SB concerns

. Acquisitions planned for SBs

. Requirements for subcontracting plans from contractors

. Participate in all SBA subcontracting plan performance reviews, and
prepare the review package, if requested by the SBA Small Business
Specialist.

. Review compliance and noncompliance reports and provide
recommendations for corrective action, if applicable.

. Review SB subcontract performance with procurement organizations and
company management to ensure continued motivation and performance.

. Consult with SB acquisition programs and councils to discuss contract
opportunities with representatives of these entities.

. Maintain directories and capability data on SBs.

. Maintain an active exchange of experience, problem resolution, and
other positive actions related to the Small Business Program with small
business representatives.

. Act as a liaison with Senior Management as required.

. Maintain awareness of legislative and regulatory changes that impact
the socioeconomic subcontracting program.

. Actively participate in company-wide award programs that recognize SBs
that perform in an exceptional manner.

. Recognize USA employees for their outstanding contributions to the
Small Business Program.

Additionally, to ensure that all personnel continue their focus on the
program, the Vice President of Logistics and Material, his direct
reports, and the plan administrators meet on a monthly basis to discuss
key areas of the program. The meetings focus on the current state of the
program, initiatives to improve the program, outreach events,
significant upcoming procurements, etc.

The individuals responsible for administering this plan are named in
Exhibit "A."

# Subcontracting Plan Goals

Subcontracting plan goals are set forth in Exhibit "A" of this plan.
Goals are expressed as a percentage of total dollars planned to be
subcontracted to all suppliers. Effective with the inclusion of FAR
52.219-9 (Sept 2006) in the designated contract, USA will track HUBZone,
VOSB and SDVOSB concerns.

Subcontracting plan goals are derived from a detailed examination of the
prime or subcontract requirements within Bills of Material, Hardware
Utilization Lists and other procurement records. This examination
includes an in-depth evaluation of the major item procurement, complex
articles, and components to determine the suitability for procurement
from SBs.

Subcontracting plans for subcontracts containing options that meet the
required threshold of more than \$550,000 (\$1,000,000 for construction
of any public facility) will separately address goals for the basic
contract terms and each option.

# Description Of Efforts

USA has whole-heartedly embraced its Small Business Program, which is
evidenced through the following efforts:

. USA Company Policy No. B-05 states in part that, "It is the policy of
USA to make all of its purchases on the basis of quality, delivery, and
price or best value." Additionally, "It is also the policy of the
company that small business suppliers, including those owned by women,
and by socially and economically disadvantaged individuals, shall have
the maximum practicable opportunity to participate in the competitive
process for the company's purchases of materials, supplies, and
services." The company's administrators serve as focal points to provide
technical guidance in carrying out these policies and procedures. The
Vice President of Logistics and Material manages the plan, and the
administrators administer the plan. All are participants in the
development of the plan, concur with its approach, and are committed to
achieving the goals established.

. USA executive management provides the Small Business Program support
and direction through written policy and procedures, and reviews
statistical information to ensure program effectiveness. Small Business
statistics are compiled and reported on a monthly basis as part of the
Business Management review to management.

. The Small Business Program goals, objectives, outreach efforts, and
related issues are conveyed in formal and informal training sessions to
personnel who are in a position to implement or influence decisions
concerning source selection. Individuals who have made significant
contributions toward the achievement of SB objectives are periodically
recognized.

. USA actively seeks new SB concerns for development as qualified
suppliers, and, when appropriate, provides specifications, drawings, and
other pertinent data to qualified or qualifiable SBs to aid them in
preparing their bids.

. USA also makes allowances consistent with contract requirements and
good procurement practices to permit delivery of economical quantities
within reasonable delivery schedules. When mutually beneficial, USA
provides management and technical assistance to SBs. The type of
assistance offered may include, but not be limited to, quality control
guidance, technical, manufacturing and financial consultation and
assistance.

. Industry and Government source directories and lists are obtained by
each location and utilized in establishing potential bidders lists. USA
representatives attend procurement conferences, seminars, trade fairs,
and other functions to seek out additional qualified or qualifiable
small businesses.

. USA's Make or Buy Committee meets as necessary to review and rule on
all make or buy decisions. The Vice President of Logistics and Material
participates in the committee meeting to ensure that consideration is
given to SBs. The Vice President of Logistics and Material serves as
permanent Secretary of the committee.

. Procurement personnel may set aside purchases for which there is a
reasonable expectation of obtaining an offer from at least two
responsible SB concerns, in accordance with established policies.

. USA uses its best efforts to give Indian organizations and
Indian-owned economic enterprises as defined in (25 U.S.C. 1544) the
maximum practicable opportunity to participate in the subcontracts it
awards, to the fullest extent consistent with efficient performance of
its contract (Ref.: FAR Clause 52.226-1, June 2000).

. USA established a Supplier Mentoring Program to foster the
establishment of long-term business relationships. USA may utilize the
NASA Mentor-Protégé Program to encourage USA to assist SB concerns in
enhancing their capabilities to perform NASA contracts and subcontracts,
or the USA Supplier Mentoring Program as established in USA policy.
Further, USA fosters the establishment of long-term business
relationships between USA and those entities. In addition, the program
increases the overall number of those entities that receive NASA
contract and subcontract awards. USA may make application(s) to NASA to
participate in the NASA Mentor-Protégé Program to the maximum extent
practicable in support of the goals specified in Clause H.3 of the
designated contract, and NASA FAR Supplement, Clause 1852.219-77 (May
1999) and -79 (March 1999).

. USA will use its best efforts to award subcontracts to SB concerns
located in rural areas. "Rural area" means any county with a population
of fewer than twenty thousand individuals (Ref.: NASA FAR Supplement,
Clause 1852.219-74, September 1990).

. USA will maintain records on all subcontract solicitations over
\$100,000, on each solicitation (where applicable) indicating (1)
whether SB concerns were solicited, and if not, why not, (2) whether
veteran-owned SB concerns were solicited, and if not, why not, (3)
whether service-disabled veteran-owned small business concerns were
solicited, and if not, why not, (4) whether HUBZone small business
concerns were solicited, and if not, why not, (5) whether SDB concerns
were solicited, and if not, why not, (6) whether WOSB concerns were
solicited, and if not, why not, and (7) if applicable, the reason award
was not made to a SB concern.

# Clause Flow Down

In compliance with its Government prime contracts, USA will: (1) include
in each subcontract that offers further subcontracting opportunity the
FAR 52.219-8 (May 2004) entitled, "Utilization of Small Business
Concerns," and (2) require all subcontractors (except SB concerns) who
receive subcontracts in excess of \$550,000 (\$1,000,000 for
construction of any public facility) to adopt a plan in accordance with
FAR 52.219-9 (Sept 2006) entitled, "Small Business Subcontracting Plan".
Subcontracts for the purchase of commercial items, pursuant to FAR Part
12, are not subject to the above referenced clause.

# Subcontractor Performance

. USA will secure subcontracting plans, similar to that agreed to by
USA, from its subcontractors (except SB concerns) that receive
subcontracts awarded under a Government prime contract in excess of
\$550,000 (\$1,000,000 for construction of any public facility). Plans
received will be reviewed by the administrator and the cognizant buyer
for compliance with applicable regulations, and will be kept in the case
file or in the cognizant administrator's office. Subcontracts issued
pursuant to FAR Part 12 are not required to submit a subcontracting
plan.

. Subcontractors shall be required to update a subcontracting plan by
submission of a revised plan whenever there are changes to an order in
excess of \$550,000 (\$l,000,000 for construction of any public
facility).

. USA may determine, when it is in the best interests of the Government,
USA, and/or the subcontractor, to allow consolidation of subcontractor's
updates to subcontracting plans on a semi-annual basis. Such updates
would encompass all modifications over the specified time period and
reduce administrative effort.

. USA will provide notice to subcontractors concerning penalties and
remedies for misrepresentations of business status as SB concerns for
the purpose of obtaining a subcontract in all solicitations exceeding
\$10,000, for requirements issued under Government contracts.
Additionally, all new suppliers are required to complete a certification
of business status with the notice concerning penalties and remedies for
misrepresentation.

. USA will encourage subcontractors to use their best efforts to award
subcontracts to SB concerns located in rural areas.

# Reports and Surveys

USA will provide quarterly reporting of procurement commitments and
percentage metrics against the goals as outlined in this plan, as well
as Clause H.3 of the designated contract. Additionally, USA will review
this plan and submit updates to the plan each six-month period based on
changes occurring during the prior six months. USA will file an
electronic Individual Subcontract Report (ISR) and a Summary Subcontract
Report (SSR) according to the instructions provided. USA, when
applicable, will require its subcontractors to submit such reports. As
required, USA will cooperate in any studies or surveys.

# Records

USA will maintain records that ensure implementation of an aggressive
and effective Small Business Program and provide management visibility
of program achievement. Examples of such records are:

. Primary Source Lists:

. Internal company source lists

. Central Contractor Registration (CCR)

. National Minority Supplier Development Council (NMSDC) Source guides

. Regional Minority Supplier Development Councils' listings

. Minority Business Development Agency Source guides

. Minority Trade Organizations and Business Associations' listings

. HBCU/MI directories

. Regional Small Business Development Councils' listings

. Listings of Veteran-Owned, Service-Disabled Veteran-Owned, and HUBZone
small businesses, where available

. Women's trade associations

. Organizations contacted for small business sources

. Records to support efforts such as:

. Contacts with disadvantaged and SB trade associations

. Contacts with business development organizations

. Attendance at Government and industry SB procurement conferences and
trade fairs

. Records to support internal activities to guide and encourage buyers
such as:

. Workshops, seminars, training programs, etc.

. Monitoring activities to evaluate compliance

. Participation in industry and Government small business networking and
education functions

. Recognition programs to encourage and reward outstanding performance

**EXHIBIT "A"**

**SMALL BUSINESS SUBCONTRACTING PLAN GOALS**

REFERENCE: NNJ06VA01C

DESCRIPTION: Insert Description

INDIVIDUALS RESPONSIBLE FOR ADMINISTERING PLAN:

+---------------------------------------------------+------------------+
| Michael H. Jones -- Vice President - Logistics    | \(281\) 212-6228 |
| and Material                                      |                  |
|                                                   | \(321\) 799-6654 |
| James D. Herring                                  |                  |
|                                                   | \(321\) 861-5249 |
| Joellen Moore                                     |                  |
|                                                   | \(281\) 282-2740 |
| Cheryl Linville                                   |                  |
+---------------------------------------------------+------------------+

SUBCONTRACTING PLAN GOALS

**USA has established the following goals for awards to Small Business
concerns through September 30, 2010:**

  ------------------------------- ---------------------- ----------------
  Total to be Subcontracted       \$2,012,811,020        100.0%

  . Large Business (LB)           1,520,933,451          75.6%

  . Small Business (SB)           491,877,569            24.4%

  . SDB\*                         173,101,748            8.6%

  . Women Owned (WOSB)\*\*        201,281,102            10.0%

  . HUBZone\*\*\*                 6,100,000              0.3%

  . VOSB\*\*\*                    41,000,000             2.0%

  . SDVOSB \*\*\*                 14,400,000             0.7%

  . HBCU/MI                       \--                    0%
  ------------------------------- ---------------------- ----------------

Descriptions of Suppliers and Services to be subcontracted to Small
Business Concerns

  ---------- ------------------------------------------------------------
  Category   Supply or Service

  SB         Flight and non-flight aerospace hardware, aircraft fittings,
             paints/coatings, facilities services, filters, construction,
             office furniture

  VOSB       Engineering support, office supplies, tools, construction,
             clean room garments

  SDVOSB     Contract labor, precision machining, obsolete/ hard-to-find
             cabling and electronic parts

  HUBZone    Hardware fabrication, IM support, GSE fabrication,
             electrical supplies

  SDB        Component cleaning and decontamination, logistics support,
             documentation/IM services, contract labor, clean room
             environment services, laboratory supplies

  WOSB       Engineering support, technical documentation, ctr.
             operations, cleaning services, contract labor, plumbing/HVAC
             supplies, construction services

             
  ---------- ------------------------------------------------------------

. Indirect purchases:

( ) Are not included in this plan

\(X\) Are included in this plan and will be allocated to all prime
contracts/subcontracts. Section Page

  --------------------------------------------------- -------------------
                                                      

  --------------------------------------------------- -------------------

  ------------------------------- ---------------------- ----------------
                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         

                                                         
  ------------------------------- ---------------------- ----------------

  ---------- ------------------------------------------------------------
             

             

             

             

             

             

             

             
  ---------- ------------------------------------------------------------

ATTACHMENT J-15

RESERVED

ATTACHMENT J‑16

Continuous Improvement (CI) Plan\
for the\
Space Program Operations Contract (SPOC)

WITHHELD FOIA EXEMPTION (b)(4) ATTACHMENT J-17

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

(See next two pages.)

![](media/image1.wmf){width="7.491666666666666in"
height="9.147916666666667in"}

![](media/image2.wmf){width="7.491666666666666in"
height="9.116666666666667in"}

ATTACHMENT J-18

NASA CENTER SPECIFIC CLAUSES

  ------------------- ------------------------------------------ ------------------
  Attachment Number   Title                                      Page

  J-18-A              Johnson Space Center Specific Clauses      J-18-[8](#j18a)

  J-18-B              Kennedy Space Center Specific Clauses      J-18-[12](#j18b)

  J-18-C              Marshall Space Flight Center Specific      J-18-[20](#j18c)
                      Clauses                                    

  J-18-D              Stennis Space Center Specific Clauses      J-18-[22](#j18d)

  J-18-E              Dryden Flight Research Center Specific     J-18-[24](#j18e)
                      Clauses                                    
  ------------------- ------------------------------------------ ------------------

ATTACHMENT J-18-A

[]{#j18a .anchor}JOHNSON SPACE CENTER SPECIFIC CLAUSES

The following clauses apply only to SPOC effort performed at Johnson
Space Center (JSC):

1.  [JSC HAZARDOUS MATERIALS USE (JSC 52.223-92) (DEC 1999)]{.underline}

    a.  The clause is JSC-unique, and the requirements are in addition
        to any U.S. Environmental Protection Agency, U.S. Occupational
        Safety and Health Administration, or other state or Federal
        regulation or statute. Therefore, the following requirements do
        NOT supercede any statutory or regulatory requirements for any
        entity subject to this clause.

    b.  "Hazardous materials," for the purposes of this clause, consist
        of the following:

        1.  Those materials defined as "highly hazardous chemicals" in
            Occupational Safety and Health Administration Process Safety
            Management Regulation, 29 Code of Federal Regulation
            1010.119, without regard for quantity.

        2.  Those "extremely hazardous substances" subject to the
            emergency planning requirements in the Environmental
            Protection Agency Emergency Planning and Community
            Right-to-Know Regulation, 40 Code of Federal Regulation 355,
            Part 355, without regard for quantity.

        3.  Those "hazardous substances" subject to the release
            notification requirements under Environmental Protection
            Agency's Emergency Planning and Community Right-to-Know
            Regulation, 40 Code of Federal Regulation 302.4, without
            regard for quantity.

        4.  Any radioisotope material or device that produces ionizing
            radiation.

        5.  Any Class II, III, or IV laser, as defined by the American
            National Standards Institute No. Z136.1 (1986)

        6.  Any explosive or any pyrotechnics.

        7.  Any pesticide.

    c.  The contractor shall develop and maintain an inventory listing
        the identity and quantity of hazardous materials stored or used
        on site at JSC for the performance of the contract.

    d.  The contractor shall ensure that the proper training of its
        employees in the use and inherent hazards of these materials is
        accomplished prior to use.

    e.  The contractor shall notify the JSC Occupational Health and Test
        Support Office (SD13) prior to any initial use or different
        application of these materials.

    f.  The contractor shall use all hazardous materials properly and
        take all necessary precautions to ensure no harm is done to
        humans or the environment.

    g.  The contractor shall insert the substance of this clause,
        including this Paragraph G with appropriate changes of
        designations of the parties, in subcontracts under which
        hazardous material will be utilized, or may reasonably be
        expected to be utilized, on site at JSC.

    h.  In the event the contractor fails or refuses to comply with any
        aspect of this clause, such failure or refusal may be considered
        a material breach of this contract.

(End of clause)

2.  [RESERVED]{.underline}

(End of clause)

3.  [IDENTIFICATION OF EMPLOYEES (JSC 52.242 92) (AUG]{.underline}
    [2006)]{.underline}

At all times while on Government property, the contractor,
subcontractors, their employees, and agents shall wear badges which will
be issued by the NASA Badging & Visitor Control Office, located in
Building 110 at the Johnson Space Center (JSC), or at the Main Gate at
the White Sands Test Facility (WSTF). JSC employee credentials and
visitor badges will be issued only between the hours of 6:00 a.m. to
7:30 p.m., Monday through Friday, and 7:30 a.m. to 3:00 p.m. on
Saturday. WSTF visitor badges will be issued on a 7-day-a-week,
24-hour-a-day basis. Resident aliens and foreign
nationals/representatives shall be issued green foreign national badges.

Each individual who wears a badge shall be required to sign personally
sign for the badge. The contractor shall be held accountable for issued
badges and all other related items and must assure that they are
returned to the NASA Badging and Visitor Control Offices upon completion
of work under the contract in accordance with Security Management
Directive (SMD) 500-15, "Security Termination Procedures." Failure to
comply with the NASA contractor termination procedures upon completion
of the work (e.g., return of badges, decals, keys, Controlled Access
Area cards, clearance terminations, JSC Public Key Infrastructure
(PKI)/special program deletions, etc.) may result in final payment being
delayed.

(End of clause)

4.  [SHIPPING INSTRUCTIONS (JSC 52.247-94) (APR 2006)]{.underline}

All documentation shall be shipped to the addresses cited in E.2.

Shipment of all other items shall be as follows:

> Parcel Post Shipments and Freight Shipments
>
> Ship to: NASA Johnson Space Center,
>
> Building 421
>
> 2101 NASA Parkway
>
> Houston, TX 77058-3696
>
> Mark for: Accountable Property Officer
>
> Mark with: Contract Number: NNJ06VA01C
>
> For reissue to:
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> (Name) (Mail Code) (Bldg) (Rm)

(End of clause)

ATTACHMENT J-18-B

[]{#j18b .anchor}KENNEDY SPACE CENTER SPECIFIC CLAUSES

The following clauses apply only to SPOC effort performed at Kennedy
Space Center (KSC):

1.  [KSC 52.204-90 SECURITY CONTROLS AT KSC (NOV 2000)]{.underline}

```{=html}
<!-- -->
```
A.  Identification of Employees

    1.  The contractor shall require each employee engaged on the work
        site to display NASA furnished identification badges and special
        access badges at all times. The contractor shall obtain and
        submit badging request forms for each person employed or to be
        employed by the contractor under this contract. The contractor
        shall designate its own security and badging officials to act as
        points-of-contact for the KSC Security Office. Prior to
        proceeding with onsite performance, the contractor shall submit
        the following information to the Protective Services Branch,
        Code TA-E2, Kennedy Space Center:

        a.  Contract number and location of work site(s)

        b.  Contract commencement and completion dates

        c.  Status as prime or subcontractor

        d.  Names of designated security and badging officials

    2.  Identification and badging of employees shall be accomplished as
        soon as practicable after award of the contract. During
        performance of the contract, the contractor shall, upon
        termination of an employee, immediately deliver badges and/or
        passes issued to the employee to the NASA Security Office. It is
        agreed and understood that all NASA identification badges/passes
        remain the property of NASA, and the government reserves the
        right to invalidate such badges/passes at any time.

B.  Access to Controlled Areas within KSC

```{=html}
<!-- -->
```
1.  Certain areas within KSC have been designated as Controlled Areas.
    These are normally surrounded by fencing and have an entrance gate
    monitored by a guard or monitoring device. Access into such areas is
    classified into \"escorted\" or \"unescorted\" access. For each
    employee for which the contractor desires to have unescorted access,
    the prescribed forms must be submitted to the NASA Security Office.
    Due to the time required to process requests for unescorted access,
    the contractor is advised to complete and submit the required forms
    as soon as practicable after contract award. Within 14 working days
    after the receipt of the forms, the NASA Security Office will
    determine whether the person is eligible for unescorted access.

2.  The prime contractor is responsible for providing escort services
    for any of his employees and/or any subcontractor employees who are
    not eligible for unescorted access.

3.  All requests for unescorted access by subcontractors will be
    submitted through the prime contractor for forwarding to the NASA
    Security Office.

(End of clause)

2.  [KSC 52.223-100 PERMANENTLY INSTALLED SAFETY SYSTEMS (SEP
    1990)]{.underline}

The contractor shall protect and in no way interrupt the service of any
installed safety systems or personnel safety devices.

In the event that the contractor requires entrance into systems serving
safety devices, the contractor shall obtain prior approval from the
Contracting Officer. In the event the contractor determines that it is
necessary to temporarily remove or render inoperable any personnel
safety devices in order to accomplish contract requirements, the
contractor shall provide alternate means of protection prior to removing
or rendering inoperable any permanently installed safety devices or
equipment and shall obtain prior approval of the Contracting Officer.

(End of clause)

3.  [KSC 52.223-101 CONFINED SPACE WORK REQUIREMENTS (APR
    2003)]{.underline}

```{=html}
<!-- -->
```
A.  Special requirements, coordination, and precautions will apply to
    any contract work taking place in confined spaces. Each contractor
    contracted to perform work in confined spaces is required to provide
    a written program for such work as part of its health and safety
    plan which is consistent with the requirements of 29 CFR 1910.146.
    For work in telecommunications manholes, provisions of 29 CFR
    1910.268(o) are also applicable. The contractor shall coordinate any
    such work in confined spaces with SGS Environmental Health, SGS Fire
    Services, and any other resident government or contractor
    organization whose employees may have access to the work location.
    The provision of Environmental Health services by the government
    does not prohibit the contractor from providing their own
    atmospheric testing. Government provided services include
    environmental health monitoring and consultation support for testing
    of atmospheres in confined spaces as well as fire rescue and
    emergency medical services.

B.  Entry into and work in confined spaces shall be in accordance with
    the requirements of KNPR 1820.4, "KSC Respiratory Protection
    Program," KNPR 1840.19, "KSC Industrial Hygiene Handbook," and all
    other applicable clauses of this contract.

C.  Confined spaces, which contain water, shall be pumped out by the
    contractor prior to scheduling a confined space entry check.

D.  In addition to the requirements set forth above, the contractor
    shall notify and obtain approval from the Power Coordinator,
    telephone 321-867-7300, and/or from Communications Control,
    telephone 321-867-4141, respectively, prior to performing work in
    electrical and/or communications manholes.

(End of clause)

4.  [KSC 52.223-105 EMERGENCY MEDICAL TREATMENT (JUL 2000)]{.underline}

The contractor shall immediately call (see below for applicable
telephone numbers) for assistance with personnel injury or illness for
any incident requiring emergency medical treatment for contractor or
subcontractor personnel, or invitees on KSC, or if any person on the job
site is rendered unconscious. The contractor shall require the victim to
sign an appropriate "refusal of treatment" form, if medical
evaluation/treatment is offered and refused.

> From KSC or CCAFS property: 911
>
> From a KSC issued cellular telephone: 867-7911
>
> From other than a KSC issued cellular telephone: 321-867-7911
>
> Commercial telephone users on KSC or CCAFS property: 911

(End of clause)

5.  [KSC 52.223-107 DISPOSAL AND SALVAGE OF MATERIALS (APR
    2004)]{.underline}

Construction and demolition debris shall be removed by the contractor to
the designated disposal area which is located not more than 10 miles
from the work site. \"Construction and demolition debris\" means
materials generally considered not to be water soluble and non-hazardous
in nature, including but not limited to glass, brick, concrete, asphalt
material, pipe, gypsum wallboard, and lumber. The term includes
materials from the construction or destruction of a structure as part of
a construction or demolition project or from the renovation of a
structure. The term includes rocks, soils, tree remains, trees, and
other vegetative matter which normally results from land clearing or
land development operations for a construction project including such
debris from construction of structures at a site remote from the
construction or demolition project site. Painted structural materials
must be tested prior to disposal in landfill.

All items of materials designated by the Contracting Officer to be
diverted from solid waste disposal as part of the KSC landfill diversion
effort shall be segregated from other mixed construction and demolition
debris and taken via separate load by the contractor to the designated
disposal area. Segregated items include concrete, wood, soils and
vegetative materials.

The contractor should make every effort to deliver vegetative material
to the appropriate disposal area. The contractor, however, may burn
combustible vegetative materials, at a designated location within the
confines of KSC or CCAFS, upon approval by the Contracting Officer. Burn
permits issued by KSC or CCAFS are required before materials are burned.
Burning may be limited or prohibited during periods of dry weather, or
when sensitive flight hardware is housed in the vicinity of the burn
site. Burn Permits must be scheduled a minimum of 48 hrs. in advance,
and are to be requested through the Fire Services Scheduler at 861-3840
between the hours of 0800-1100 & 1200-1430, Monday through Friday.

All items of materials designated by the Contracting Officer to be
salvaged shall remain the property of the government and will be cleaned
of non-salvable debris, segregated, itemized, delivered, and off-loaded
by the contractor at the disposal area. Scrap metal will be treated as
salvage. The contractor shall maintain adequate property control records
for all materials or equipment specified by the Contracting Officer to
be salvaged. These records may be in accordance with the contractor\'s
system of property control if approved by the Contracting Officer. The
contractor shall be responsible for adequate storage and protection of
salvaged materials and equipment pending delivery to the disposal area
until the Contracting Officer otherwise dispositions it.

The contractor shall ensure that all salvable materials delivered to the
designated disposal area meet the following conditions:

-   All items must be accompanied by required documentation, KSC Form
    7-49 (or equivalent), and identified with a full, written commercial
    description.

-   No leakage of any type of fluid from equipment or containers.

-   No visible indication of old spills/releases on outside of equipment
    or containers that could be washed off from rainfall.

-   Oil filled equipment shall be drained of free-flowing liquids. Items
    which previously contained dielectric fluid must be accompanied by a
    copy of analytical results taken within the past 6 months,
    documenting that the fluid did not contain Polychlorinated Biphenyls
    ((PCBs) in concentrations equal to or greater than 50 ppm. Fluid
    sampling will be performed by the government.

-   Unserviceable equipment containing Ozone-Depleting Substances (ODS,
    e.g. Freon) must be drained (ODS recovered) and labeled "Empty".
    Serviceable equipment containing ODS needs a certification that the
    equipment is not leaking. Serviceable equipment shall not be
    drained.

-   Scrap metal must be visually clean of all residual oil/contaminants.

The contractor shall burn combustible materials, at a location
designated by the Contracting Officer. Burn permits issued by KSC or
CCAS are required before materials are burned. Burning may be limited
during periods of dry weather. Burn Permits must be scheduled a minimum
of 48hrs in advance. Burn Permits are to be requested through the Fire
Services Scheduler at 861-3840 between the hours of 0800-1100 &
1200-1430, Monday through Friday. Subject areas will be within the
confines of KSC or CCAS.

Hazardous waste shall be managed in accordance with KNPR 8500.1, KSC
Environmental Requirements. Asbestos waste material shall be deposited
in the Brevard County Landfill located on Adamson Road in West Cocoa,
Florida. The contractor shall obtain a receipt from the landfill
operator for each load of waste deposited and furnish a copy of the
receipt to the Contracting Officer.

A normal state of cleanliness at the work site is expected. The
contractor shall clean up and dispose of debris from the work site
daily.

(End of clause)

6.  [KSC 52.223-118 BREATHING AIR COMPATIBILITY (APR 2000)]{.underline}

The contractor shall take precautions to assure that connectors used in
contractor-supplied breathing air systems are incompatible with
connectors present on either KSC gas systems or on contractor-supplied
systems that are used to supply non-respirable gases. KSC-STD-Z0008,
'Standard for Design of Ground Life Support Systems and Equipment',
establishes requirements for connectors to be used in KSC facility
breathing air and non-respirable gas systems. Facility breathing air
systems located at KSC/CCAFS are to use a Hansen 3/8 inch quick
disconnect as a breathing air distribution interface. KSC facility
non-respirable gas systems are to use ¼ inch quick disconnects for gas
distribution interfaces. Although most facility systems were designed in
accordance with this standard, there are nonconforming locations at
KSC/CCAFS.

The contractor may use KSC facility breathing air systems, if available
at the work location. The contractor shall perform a pre-work site
inspection to identify coupling types in use at the work location before
mobilizing or using any breathing air equipment. The contractor shall
also submit a written certification to show the contractor's breathing
air system has been recently inspected and meets Grade D breathing air
standards. Alternately, the contractor may arrange for on-site testing
of contractor-supplied breathing air by the government at least five
days prior to start of work. In addition, the contractor shall also
provide a work site evaluation for the NASA Safety Office to review
before using any breathing air system. The breathing air test and the
safety inspection can be coordinated through the Contracting Officer,
and will be at no cost to the contractor.

The contractor shall tag or label connector ends of all lines and
flexible hoses of contractor-provided breathing air or non-respirable
gas distribution systems. The tags or labels will clearly identify the
contents of the lines or hoses.

The contractor shall provide a description of the steps taken to comply
with the requirements of this clause in their safety plan submittal.

(End of clause)

7.  [KSC 52.223-119 ASBESTOS-CONTAINING BUILDING MATERIALS (APR
    2004)]{.underline}

```{=html}
<!-- -->
```
A.  Asbestos-Containing Building Materials (ACBM) are known to be
    present in facilities assigned under the scope of this contract. The
    government will provide information regarding the location and
    quantity of known ACBM in NASA/KSC facilities to the facility tenant
    organizations through the JBOSC Environmental Health office.

B.  Special requirements, coordination, and precautions will apply to
    any work taking place under contracts that involves disturbance of
    ACBM. Contractors whose contracts require work involving ACBM are
    required to provide a written program for such work as part of its
    health and safety plan which is consistent with the requirements of
    29 CFR 1926.1101 and address the NESHAP and Florida Administrative
    Code requirements under 40 CFR 61 Subpart M and FAC 62-257
    respectively. The contractor shall coordinate any such work
    involving ACBM with JBOSC Environmental Health, SGS Fire Services,
    and any other resident government or contractor organization whose
    employees may have access to the work location.

C.  Asbestos waste shall be managed in accordance with KNPR 8500.1, KSC
    Environmental Requirements.

(End of clause)

8.  [KSC 52.236-91 TRAFFIC RESTRICTIONS (SEP 1990)]{.underline}

The Contractor will not move oversized loads and/or slow moving vehicles
on established roads within the Kennedy Space Center from 6:30 A.M. to
8:30 A.M. and 3:30 P.M. to 5:30 P.M. on week days. Other than the above
restricted hours, the Contractor may move oversize and/or slow moving
vehicles to the work site provided all requirements of the Florida State
Highway Department have been met.

Movement of any Contractor vehicle in excess of maximum width, height
and length specified by Florida Statues Chapter 316 shall be accompanied
by the Contractor\'s designated Convoy Commander. The Contractor\'s
Convoy Commander shall be totally responsible for the oversized
vehicular movement to include making a physical inspection for possible
obstructions along the intended route and obtaining all required special
permits.

(End of clause)

9.  [KSC 52.236-95 STORAGE AND PROTECTION OF MATERIAL TO BE RE-USED (FEB
    1999)]{.underline}

All items of material to be removed and re-installed by the contractor
shall be protected during removal and stored in a manner such that the
material will not be damaged during removal or storage. Any material
designated for re-use, which is not suitable due to the contractor\'s
damage, will be replaced by the contractor at no additional cost to the
government.

(End of clause)

10. [KSC 52.236-97 AVIATION OBSTRUCTION LIGHTS (MAR 1999)]{.underline}

Contractor will provide at least two Aviation Red Obstruction Lights or
two High Intensity White Obstruction Lights on all structures over 100
feet above ground level. All construction cranes/booms shall be lighted
regardless of height. Lights must be constructed and installed in
accordance with U.S. Department of Transportation, Federal Aviation
Administration publication AC 70/7460-1F (as revised), Chapter 4,
paragraph 15, subparagraph e. Lights will be operated during all periods
of reduced visibility, between sunset and sunrise, and as directed by
the Contracting Officer.

(End of clause)

11. [KSC 52.236-106 INTERFERENCES AND COORDINATION OF WORK (FEB
    1991)]{.underline}

The contractor shall coordinate construction layout, systems
configuration and work scheduling to avoid interference's between the
various construction trades and their installations. Interferences and
obstructions resulting from lack of contractor coordination shall be
corrected by the contractor as approved by the Contracting Officer. All
components, fittings and reworking necessary for such corrections shall
be provided by the contractor at no additional cost to the government.

Dimensions shown for existing work, and all dimensions required for work
that is to connect to existing work, shall be verified by the contractor
by actual field measurement of the existing work. Any work at variance
with that specified or shown in the drawings shall not be performed by
the contractor until approved in writing by the Contracting Officer.

To the extent possible, the as-built dimensions of all new work shall be
verified by actual field measurement prior to ordering or fabricating
mechanical, electrical, or specialty equipment and materials to be
installed. If such field measurement is not possible, then the contract
drawings and applicable shop drawings shall be checked by the contractor
for dimensional accuracy prior to ordering or fabricating equipment and
materials to ensure proper fit for field installation.

The contractor shall be responsible for correction of all field fitup
problems and interferences which could have been avoided by field
measurement or drawing checks prior to equipment fabrication.

(End of clause)

12. [KSC 52.236-130 CONDUCT OF FACILITY PROJECTS (APR 2000)]{.underline}

```{=html}
<!-- -->
```
A.  Approval

> The contractor shall not award or otherwise proceed with
> implementation of any facility project without a NASA approved
> Facility Project -- Brief Project Document (NASA Form 1509). The
> contractor shall prepare or otherwise support the preparation of NASA
> Form 1509\'s in accordance with the current edition of NPG 8820.2,
> Facility Project Implementation Handbook, and the current version of
> the KSC procedure for Facility Project Approval and Implementation.
> For purposes of this requirement a Facility Project is defined as any
> new construction, repair, and /or modification affecting government
> real property located on KSC regardless of the source of funding, or
> located elsewhere and funded by KSC, and costing more than \$50,000.
> Planning and design activities leading to the implementation of the
> actual construction, repair or modification work normally can be
> accomplished prior to 1509 approval. When in doubt, guidance as to
> whether or not a particular activity is a Facility Project, is
> \"implementation\" versus \"planning and design,\" and / or the
> applicability of this requirement in relation to specific projects
> should be obtained from the KSC Spaceport Services Management
> Integration Office.

B.  File Documentation

> Construction subcontract file documentation shall include a copy of
> the approved NASA Form 1509 authorizing the project. For construction
> subcontracts requiring Contracting Officer consent, the consent file
> shall include a copy of the approved NASA Form 1509 authorizing the
> project.

(End of clause)

ATTACHMENT J-18-C

[]{#j18c .anchor}MARSHALL SPACE FLIGHT CENTER SPECIFIC CLAUSES

The following clauses apply only to SPOC effort performed at Marshall
Space Flight Center (MSFC):

1.  [CONTRACTOR EMPLOYEE BADGING AND EMPLOYMENT TERMINATION CLEARANCE
    (MSFC 52.204-90)]{.underline}

    a.  It is anticipated that performance of the requirements of this
        contract will require employee access to and picture badging by
        the Marshall Space Flight Center. Contractor requests for
        badging of employees shall be by MSFC Form 1739, \"MSFC
        Contractor Badge/Decal Application.\" Requests for badging shall
        be submitted to the appointed Contracting Officer Technical
        Representative for completion and approval prior to processing
        by the MSFC Protective Services Department.

    b.  The Contractor shall establish procedures to ensure that each
        badged employee is properly cleared in accordance with MSFC Form
        383-1, \"Contractor Employee Clearance Document,\" prior to
        finalization of employment termination.

    c.  Requests for copies of MSFC Forms 383-1, and 1739 shall be
        directed to the MSFC Protective Services Department, Marshall
        Space Flight Center, Alabama 35812.

(End of clause)

2.  [ASBESTOS MATERIAL (MSFC 52.223-90) (JUN 2002)]{.underline}

During performance of this contract, Contractor personnel performing
work in MSFC buildings may come in contact with materials containing
asbestos. MSFC Buildings 4200, 4201, 4202, 4663 and 4666 are of special
concern since they are known to contain a sprayed on fire insulation on
or above the ceiling, usually located on the metal or concrete structure
of the buildings. These buildings and all other MSFC buildings may
contain asbestos in floor tile, pipe and lagging insulation, exterior
siding, roofing felt, and many other building materials. Prior to
disturbing suspected asbestos material in any manner, the Contractor
shall notify MSFC\'s Occupational Medicine and Environmental Health
Services, for guidance. Contractor shall be responsible for ensuring
that all Contractor personnel working onsite are made aware of and
comply with this clause.

(End of clause)

3.  [HAZARDOUS MATERIAL REPORTING (MSFC 52.223-91) (APR
    2003)]{.underline}

```{=html}
<!-- -->
```
a.  If during the performance of this contract, the Contractor brings
    any hazardous materials (hazardous as defined under the latest
    version of Federal Standard No. 313, including revisions adopted
    during the term of the contract) on-site to the Marshall Space
    Flight Center, a completed MSFC Form 4099 (MSFC Chemical Inventory
    Addition) shall be immediately forwarded to the address on the form.
    The Contractor shall be responsible for ensuring that all
    Contractor/subcontractor personnel are made aware of and comply with
    this clause.

b.  Nothing contained in this clause shall relieve the Contractor from
    complying with applicable Federal, State, and local laws, codes,
    ordinances, and regulations (including the obtaining of licenses and
    permits) in connection with hazardous material; or with other
    clauses regarding hazardous materials which may be contained in the
    contract.

(End of clause)

ATTACHMENT J-18-D

[]{#j18d .anchor}STENNIS SPACE CENTER SPECIFIC CLAUSES

The following clauses apply only to SPOC effort performed at Stennis
Space Center (SSC):

1.  [ASBESTOS MATERIAL]{.underline}

```{=html}
<!-- -->
```
a.  During performance of this contract, Contractor and subcontractor
    personnel performing work in SSC buildings may come in contact with
    materials containing asbestos. Portions of SSC buildings 1000, 1100,
    1105, 1200, 2101, and 2201 contain asbestos spray-applied
    insulation. Other building may contain asbestos around pipes,
    valves, ducts, boilers, and tanks. The Contractor shall be
    responsible for ensuring all applicable codes, standards and
    regulations are adhered to and enforced, including OSHA Standard 29
    CFR 1910.1001, OSHA Standard 29 CFR 1926.58, and USEPA 40 CFR 61,
    Subpart M. Prior to disturbing this material in any manner, the
    Contractor shall notify the NASA Environmental Office for guidance.
    The Contractor shall be responsible for ensuring all Contractor and
    subcontractor personnel are made aware of and comply with this
    clause.

b.  SSC has an Asbestos Abatement Plan which addresses procedures for
    work involving potential asbestos exposure. The Contractor will be
    requirement to comply with the provisions of this plan whenever its
    work involves the potential for exposure to asbestos. Reference SSC
    Asbestos Management and Abatement Program Plan dated August 17,
    1992.

(End of clause)

2.  [HAZARDOUS MATERIAL AND HAZARDOUS WASTE MANAGEMENT]{.underline}

During the performance of this contract, the Contractor or
subcontractors may be required to requisition, handle and manage
hazardous materials in support of specific projects. The Contractor may
also be collecting waste generated by its activities for ultimate
disposal by NASA. In the performance of these activities, the Contractor
shall abide by the most recent version of SMI 4130.1, Control of
Hazardous Materials, SHB 4130.2, Hazardous Materials, Hazardous Waste
and Solid Waste Management Plan, the SSC Contingency Plan for Response
to Spills of Oil and Hazardous Substances, and the SSC Spill Prevention
Control and Countermeasures Plan.

(End of clause)

3.  [ENVIRONMENTAL PLANNING]{.underline}

During the performance of this contract, the Contractor or
subcontractors may be required to design projects or perform projects
that will potentially impact the environment. To guide the Contractor in
what needs to be considered in project designs and planning, the
Contractor shall reference the SSC Environment Resources Document (ERD).
The development and submission to the NASA Environmental Office of the
Preliminary Environmental Survey found in the ERD is required if there
is any potential impact to the environment in the project. The NASA
Environmental Office will determine if the project will require
evaluation under the National Environmental Policy Act and what
environmental permits will be needed prior to proceeding with the
project.

(End of clause)

4.  [RESERVED]{.underline}

ATTACHMENT J-18-E

[]{#j18e .anchor}DRYDEN FLIGHT RESEARCH CENTER SPECIFIC CLAUSES

The following clauses apply only to SPOC effort performed at Dryden
Flight Research Center (DFRC):

1.  [SECURITY REGISTRATION AND IDENTIFICATION BADGES\--ON-SITE
    CONTRACTORS, EXCLUDING CONSTRUCTION (DFRC 52.204-90)]{.underline}

```{=html}
<!-- -->
```
a.  It is required that all persons engaged in work at Dryden Flight
    Research Center (DFRC) be registered and badged by the Security
    Office.

b.  It is the Contractor's responsibility that each of its employees or
    representatives wear the identification badge issued at all times
    they are within the boundaries of DFRC. Badges shall be worn in such
    a manner as to be clearly visible (on the left lapel of the coat or
    on the upper part of the outer garment).

c.  \(1\) The Contractor shall insure that all terminated employees or
    employees no longer connected with the work being performed under
    this contract are processed through the DFRC Security Check-out
    Procedures. Badges and vehicle passes/decals must be accounted for
    and returned. If a computer account has been established, the
    account must also be deactivated.

```{=html}
<!-- -->
```
(2) The Contractor shall be notified by the Government if a terminated
    employee has not been processed through the Security Check-out
    Procedures. The Contractor then has 30 days by which to process the
    terminated employee without penalty. After 30 days, a Bill of
    Collection will be issued by the Government in the amount of \$500
    for each terminated employee that has not been processed through the
    checkout procedures.

```{=html}
<!-- -->
```
d.  SUPPORT SERVICE CONTRACTS:

```{=html}
<!-- -->
```
(1) U.S. CITIZENS AND PERMANENT RESIDENT ALIENS. On the first day of
    work, check in at the NASA Reception Building (Bldg. 4825). A
    temporary badge will be issued and the employee will be directed to
    the work site. As soon as practical, bring the completed
    "Non-Government Employee Security Badging Packet," NASA Form 531, to
    the Security Office (Building 4825). Employees will need to submit a
    completed packet for each badge issued, including renewals.
    Fingerprints will be taken if necessary and a permanent badge,
    decal, etc., will be issued. All terminating employees must check
    out through the Badge Office.

(2) FOREIGN NATIONALS (PASSPORTS, VISAS, NON-IMMIGRANT ALIENS). A
    National Agency Check is a prerequisite for a foreign national,
    making it necessary that all paperwork be submitted to the Security
    Office, Code XAS, M/S D-4825, at least 60 days in advance of the
    anticipated entry date. The Security Office will provide guidance as
    to what paperwork and type of visa are required.

(3) RESERVE GATE PROCEDURE. In the event of a labor dispute the
    Government may restrict entrance and exit of the Contractor's
    employees and the Contractor's suppliers to a specified gate at
    DFRC, pursuant to Chapter 4 of NASA Handbook 5200.1 entitled
    "Industrial Labor Relations Manual." The Contractor agrees to have
    its employees rebadged and to direct them and its suppliers to
    utilize only the designated gate.

(End of clause)

2.  [SECURITY REGISTRATION AND IDENTIFICATION BADGES---ON-SITE
    CONTRACTORS, EXCLUDING CONSTRUCTION (DFRC 52.204-90) (FEB
    2001)]{.underline}

```{=html}
<!-- -->
```
a.  All persons engaged in work at Dryden Flight Research Center are
    required to be registered and badged by the Security Office, and to
    follow all security regulations and requirements.

b.  The Contractor is responsible for assuring that each employee or
    company representative wears his/her issued identification badge at
    all times while they are within the boundaries of Dryden Flight
    Research Center. Badges shall be worn above the waist in such a
    manner as to be clearly visible.

c.  The Contractor shall ensure that all employees who are terminated or
    who are no longer connected with the work being performed under this
    contract are processed out through the Security Office. Badges,
    keys, vehicle passes/decals, and other Government property must be
    accounted for and returned. If a computer account has been
    established, the account must be deactivated.

d.  Only U.S. Citizens and Permanent Resident Aliens will be badged by
    the security office. Foreign Nationals (non-immigrant aliens) WILL
    NOT be badged or permitted to perform on-site work on the project
    (other than to be escorted) until a National Agency Check has been
    completed.

e.  After badging, contractor and subcontractor employees will be
    permitted to enter the Center and to drive by direct route from that
    gate to the parking area assigned to the Contractor by the
    Contracting Officer.

f.  Employees of construction contractors shall turn in their badges to
    the Visitor Badging Office, Building 4825, when they complete
    working on-site.

(End of clause)

3.  [REPORTS OF WORK]{.underline}

```{=html}
<!-- -->
```
a.  Metrology Control Document. The Contractor shall prepare a metrology
    control document for each instrument calibrated/repaired. (DFRC Form
    760)

b.  NASA Mishap Report. The Contractor shall report any accident within
    2 hours after their occurrence to the COTR/CO and submit a NASA Form
    1627 within 24 hours of any mishap to the Safety Office.

(End of clause)

4.  [DELIVERY OF REPORTS]{.underline}

All reports of work shall be delivered in accordance with the Data
Requirements Descriptions (DRD) provided in Section J, Attachment No.
J-5. Unless otherwise specified, all reports shall be addressed to
NASA-Dryden Research Center, Edwards, CA 93523-0273, marked with the
contract number, to the attention of the listed recipients. A copy of
the transmittal letter for each report shall be forwarded to the
Contracting Officer.

(End of clause)

ATTACHMENT J-19

PROVISIONING MANAGEMENT PLAN

SPACE PROGRAM OPERATIONS CONTRACT

I.  PROVISIONING PROCEDURES

Statement of Work paragraphs of the contract subject to Program
Provisioning include: 1.4.1.2, Orbiter Logistics \[High Value Spares
(replacement parts with a unit cost of \$1M+)\], 1.4.1.5, Orbiter
Hardware Production and Support Tasks; 1.4.9, Flight Crew Equipment;
1.6.5.4, Flight Operations Development; 1.7.1, Special Studies and
Development Projects; 1.7.1.1, KSC Shuttle Development Activities;
1.7.1.2, KSC Construction of Facility Activities; 1.7.4, Program
Reimbursables; and 1.7.5, Solid Rocket Booster Development Activities.
The SOW paragraph of the contract subject to Transition Provisioning is
1.9, Program Transition. The SOW paragraph of the contract subject to
Constellation Provisioning is 1.10, Constellation Bridge Support.

II. CONTRACT IMPLEMENTATION

Implementation of Provisioning is defined in H.35. The clauses also
describe the annual Provisioning process. Costs associated with
Provisioning will be evaluated under the award fee provision of the
contract. The contractor is required to account for these costs so as to
ensure that no co-mingling of costs occurs between work under the basic
contract, work authorized under Program Provisioning, work authorized
under Transition Provisioning, and work authorized under Constellation
Provisioning.

III. INDIVIDUAL PROVISIONING AREA INFORMATION

Exhibits to this plan contain the following pertinent information
related to Provisioning:

-   Authorizing Statement of Work (Attachment J-1-A) paragraph

-   Identification of applicable Technical Management Representative
    (TMR) for the specific Provisioning program element.

-   The annual threshold amount (if any) for each area.

IV. PROVISIONING MANAGEMENT PROCEDURES

    The following are the overall procedures required for Provisioning
    establishment and management:

-   NASA and the contractor will, no later than 75 days prior to the
    beginning of the next GFY, partner the direct resources for the
    provisioned work to be initiated in the forthcoming GFY. The
    requirements for such work will be developed by the Government in
    concert with the contractor. The contractor and NASA will negotiate
    and definitize the provisioned work to be performed, and adjust the
    cost and fee for Program Provisioning, Transition Provisioning, and
    Constellation Provisioning in Clause B.2, before October 1^st^ of
    the forthcoming GFY.

-   The negotiation described above will result in an annual Program
    Provisioning Task List (PPTL), an annual Transition Provisioning
    Task List (TPTL), and an annual Constellation Provisioning Task List
    (CPTL) for each individual Exhibit, which shall be compiled into a
    Provisioning Task Book maintained by the contractor. The COTR and
    the TMR's have the flexibility, through the Contracting Officer, to
    modify, delete, reprioritize or otherwise change tasks, except as
    otherwise limited within this plan. The cognizant NASA Contracting
    Officer will issue contract direction to authorize any such changes
    deemed necessary or appropriate.

-   The Provisioning Task Book (PTB) will specify the negotiated tasks
    for each Exhibit, for each List. Within certain program elements, an
    estimate of below threshold changes expected in the coming year will
    be established in the annual List. The parties agree that no change
    made pursuant to an Exhibit(s) shall give rise to an equitable
    adjustment in the estimated cost and fee, delivery schedule, or any
    other contract provision, when said change does not exceed the
    specific threshold amounts reflected in each Exhibit. It is
    understood that activities authorized by the cognizant TMR shall not
    be artificially combined together to exceed the specified threshold
    nor shall they be artificially segregated to fall below the
    specified threshold. The parties recognize that several changes may
    be grouped together in a bilateral contract modification for
    definitization; however, the dollar value of each individual change
    will be controlling in determining whether or not an equitable
    adjustment is in order. For those tasks that occur during the fiscal
    year but do not exceed the threshold, the contractor shall support
    each task as authorized through technical direction by the cognizant
    TMR. The PTB and subsequent updates to it shall be made pursuant to
    the contract modification(s) executed by the parties which
    definitized the work and equitably adjusted the contract. The PTB
    shall be maintained by the contractor and made available to the
    Contracting Officer and the Contracting Officer's Technical
    Representative (COTR) via the United Space Alliance internal web
    page.

-   Individual Lists and related cost estimates shall be included in
    their appropriate Exhibits of the PTB for Program Provisioning,
    Transition Provisioning, and Constellation Provisioning. The PPTL,
    TPTL, CPTL, and PTB will be modified appropriately to reflect the
    issuance of supplemental agreements which definitize any Program,
    Transition, or Constellation Provisioning Change Orders (PCOs).

-   PPTL/TPTL/CPTL cost tracking shall be reflected in the Contractor's
    533 report at a summary level for each Exhibit. Lower level
    reporting for each Exhibit shall be in a format agreed to by the
    contractor and the Government and shall, at a minimum, provide
    visibility, by individual task, as to performance against the
    original task cost estimate as well as any modification made to the
    task to increase or decrease scope/cost. Reporting of performance
    shall be documented in the Monthly Incurred Cost (MIC) report.

-   The clause H.20, [SPECIAL PROVISION FOR CONTRACT
    CHANGES]{.underline}, does not apply to any change issued under
    Program Provisioning, Transition Provisioning, or Constellation
    Provisioning.

    **PROGRAM PROVISIONING TASK LIST**

######### Exhibit A-P, Orbiter

-   Authority: SOW Paragraphs 1.4.1.2, Orbiter Logistics; 1.4.1.5,
    Orbiter Hardware Production and Support Tasks; and 1.4.9, Flight
    Crew Equipment

-   Cognizant TMR for Orbiter

######### Exhibit B-P, Integrated Launch & Landing

-   Authority: SOW Paragraph 1.7.1.1, KSC Shuttle Development Activities
    and 1.7.1.2, KSC Construction of Facility Activities

-   Cognizant TMR for Launch Site Equipment

######### Exhibit C-P, Integration

-   Authority: SOW Paragraph 1.7.1, Special Studies and Development
    Projects

-   Cognizant TMRs for Integration and Space Shuttle Special Studies

######### Exhibit D-P, Program Reimbursables

-   Authority: SOW Paragraph 1.7.4, Program Reimbursables

-   Cognizant COTR

######### Exhibit E-P, SRB Program Provisioning

-   Authority: SOW Paragraph 1.7.5, Solid Rocket Booster Development
    Activities

-   Cognizant TMR for SRB Effort

######### Exhibit F-P, Flight Operations Development

-   Authority: SOW Paragraph 1.6.5.4, Flight Operations Development

-   Cognizant TMR for Flight Operations Development

######### Exhibit G-P, RESERVED

######### Exhibit H-P, RESERVED

######### Exhibit I-P, RESERVED

**Exhibit J-P, Program Provisioning Universal Pool**

-   Authority: SOW Paragraphs 1.4.1.2; 1.4.1.5; 1.4.9; 1.6.5.4; 1.7.1;
    1.7.1.1; 1.7.1.2; 1.7.3; 1.7.4; and 1.7.5

-   Cognizant TMRs: As identified under Exhibits A**-P** -- I**-P**

```{=html}
<!-- -->
```
-   Annual Program Provisioning Threshold:

    -   FY07 - \$1,000,000\*

> The Contractor shall perform Program provisioning changes in FY07 that
> are not specifically identifiable at the beginning of the fiscal year
> that are individually estimated to cost less than \$1M at price.
> Examples include: Orbiter Hardware changes and Program Integration
> (PI) Systems Design Analysis and Hardware tasks, not elsewhere
> authorized in PPTL. This pool may be used for other tasks with mutual
> agreement of the parties.
>
> \*The initial value of the pool is set is set at \$4M at USA price. In
> the event the value of the work authorized by the end of Government
> fiscal year 2007 is greater or less than that amount by more than
> \$1M, an adjustment in contract value will be made. This adjustment
> shall not include any added/deleted fee for the bandwidth itself; for
> amounts beyond the bandwidth, an adjustment shall be made in both cost
> and fee. The pool value will not include any value for the
> continuation of tasks started before FY 07, and the value of any
> authorized work for purposes of determining a contract value
> adjustment will be determined by the value shown on the authorizing
> document at the time of issuance.

######### 

-   
-   

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

######### **TRANSITION PROVISIONING TASK LIST** {#transition-provisioning-task-list .unnumbered}

**Exhibit A-T, Orbiter**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant TMR for Orbiter

**Exhibit B-T, Integrated Launch & Landing**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant TMR for Launch Site Equipment

**Exhibit C-T, Integration**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant TMRs for Integration and Space Shuttle Special Studies

**Exhibit D-T, Program Reimbursables**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant COTR

**Exhibit E-T, SRB Program Provisioning**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant TMR for SRB Effort

**Exhibit F-T, Flight Operations Development**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant TMR for Flight Operations Development

**Exhibit G-T, RESERVED**

**Exhibit H-T, Space Shuttle Strategic Sustainment**

-   Authority: SOW Paragraph 1.9, Program Transition

-   Cognizant COTR

**Exhibit I-T, RESERVED**

**Exhibit J-T, Transition Provisioning Universal Pool**

-   Authority: SOW Paragraph 1.9

-   Cognizant TMRs: As identified under Exhibits A**-T** -- I**-T**

```{=html}
<!-- -->
```
-   Annual Transition Provisioning Threshold:

    -   FY07 - \$1,000,000\*

> The Contractor shall perform Transition provisioning changes in FY07
> that are not specifically identifiable at the beginning of the fiscal
> year that are individually estimated to cost less than \$1M at price.
> Examples include: Detailed Transition Implementation Planning and
> Implementation tasks, not elsewhere authorized in TPTL.

\*The initial value of the pool is set is set at \$4M at USA price. In
the event the value of the work authorized by the end of Government
fiscal year 2007 is greater or less than that amount by more than \$1M,
an adjustment in contract value will be made. This adjustment shall not
include any added/deleted fee for the bandwidth itself; for amounts
beyond the bandwidth, an adjustment shall be made in both cost and fee.
The pool value will not include any value for the continuation of tasks
started before FY 07, and the value of any authorized work for purposes
of determining a contract value adjustment will be determined by the
value shown on the authorizing document at the time of issuance.

-   
-   

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

-   **CONSTELLATION PROVISIONING TASK LIST**

**Exhibit A-C, Orbiter**

-   Authority: SOW Paragraph 1.10, Constellation Bridge Support

-   Cognizant TMR for Orbiter

-   Annual Constellation Provisioning Threshold:

```{=html}
<!-- -->
```
-   FY 07 \$0

**Exhibit B-C, Integrated Launch & Landing**

-   Authority: SOW Paragraph 1.10, Constellation Bridge Support

-   Cognizant TMR for Launch Site Equipment

-   Annual Constellation Provisioning Threshold:

```{=html}
<!-- -->
```
-   **FY 07 \$1,000,000\***

> **The Contractor shall perform Constellation provisioning changes in
> FY07 that are not specifically identifiable at the beginning of the
> fiscal year that are individually estimated to cost less than \$1M at
> price. Examples include: ground systems operations, maintenance, and
> modification; vehicle processing, test, and recovery operations; and
> assembly and physical integration of Constellation test flight
> elements, not elsewhere identified in CPTL.**
>
> **\*The initial value of the pool is set is set at \$2.1M at USA
> price. In the event the value of the work authorized by the end of
> Government fiscal year 2007 is greater or less than that amount by
> more than \$1M, an adjustment in contract value will be made. This
> adjustment shall not include any added/deleted fee for the bandwidth
> itself; for amounts beyond the bandwidth, an adjustment shall be made
> in both cost and fee. The pool value will not include any value for
> the continuation of tasks started before FY 07, and the value of any
> authorized work for purposes of determining a contract value
> adjustment will be determined by the value shown on the authorizing
> document at the time of issuance.**

**Exhibit C-C, Integration**

-   Authority: SOW Paragraph 1.10, Constellation Bridge Support

-   Cognizant TMRs for Integration and Space Shuttle Special Studies

-   Annual Constellation Provisioning Threshold:

```{=html}
<!-- -->
```
-   FY 07 \$0

**Exhibit D-C, RESERVED**

**Exhibit E-C, SRB Program Provisioning**

-   Authority: SOW Paragraph 1.10, Constellation Bridge Support

-   Cognizant TMR for SRB Effort

-   Annual Constellation Provisioning Threshold:

```{=html}
<!-- -->
```
-   FY 07 \$0

**Exhibit F-C, Flight Operations Development**

-   Authority: SOW Paragraph 1.10, Constellation Bridge Support

-   Cognizant TMR for Flight Operations Development

-   Annual Constellation Provisioning Threshold:

-   **FY 07 \$1,000,000\***

> **The Contractor shall perform Constellation provisioning changes in
> FY07 that are not specifically identifiable at the beginning of the
> fiscal year that are individually estimated to cost less than \$1M at
> price. Examples include: concept development and trade analyses for
> flight operations trajectory planning, mission planning, development,
> integration and execution, not elsewhere identified in CPTL.**
>
> **\*The initial value of the pool is set is set at \$8.4M at USA
> price. In the event the value of the work authorized by the end of
> Government fiscal year 2007 is greater or less than that amount by
> more than \$1M, an adjustment in contract value will be made. This
> adjustment shall not include any added/deleted fee for the bandwidth
> itself; for amounts beyond the bandwidth, an adjustment shall be made
> in both cost and fee. The pool value will not include any value for
> the continuation of tasks started before FY 07, and the value of any
> authorized work for purposes of determining a contract value
> adjustment will be determined by the value shown on the authorizing
> document at the time of issuance.**

**Exhibit G-C, RESERVED**

**Exhibit H-C, Space Shuttle Strategic Sustainment**

-   Authority: SOW Paragraph 1.10, Constellation Bridge Support

-   Cognizant COTR

-   Annual Constellation Provisioning Threshold:

```{=html}
<!-- -->
```
-   FY 07 \$0

**Exhibit I-C, RESERVED**

ATTACHMENT J-20

RESERVED

ATTACHMENT J-21

FACILITIES AND ENVIRONMENTAL PROJECTS

  ------- -------- ------------------------------ ------------ ------------
  ITEM    CO/SA    TITLE                          CONTRACT\    TOTAL\
                                                  VALUE        FUNDING

  Basic            Roll through from NAS 9-20000  \$ TBD       \$ TBD
  ------- -------- ------------------------------ ------------ ------------

ATTACHMENT J-22

RESERVED

ATTACHMENT J-23

STANDARDS, FOOD, AND SPECIFICATIONS LIST

July 1989

FOOD STANDARDS AND SPECIFICATIONS

This exhibit contains the Food Processing Standards (FPS), the
Specification for Food (SD-F), and the Specification for Food Testing
(SD-T).

  --------------- -------------------------------------------------------
  FPS-149         Standard for Food Facility Preparation for Processing
                  Aerospace Food

  FPS-150         Standard for Food Facility Clean Room Operation

  FPS-153         Standard for the Interim Packaging of Aerospace Food

  FPS-155         Standard for the Burst Pressure Testing of Plastic
                  Laminate Food Packages

  FPS-156         Standard for Seal Strength Testing of Plastic Laminate
                  Food Packages

  FPS-157         Organoleptic Test Procedures for Flight Food

  FPS-158         Standard for Headspace Oxygen Analysis

  FPS-166         Standard for the Fabrication, Assembly, and Inspection
                  of the Shuttle Rehydratable Food Beverage/Package
                  Components

  FPS-209         Standard for the Fabrication and Assembly of Septum
                  Adapter Assemblies

  SD-T-0251       Microbiological Specification and Testing Procedure for
                  Foods Which Are Not Commercially Sterile

  SD-T-0252       Microbiological Specification and Testing Procedure for
                  Commercially Sterile Foods

  SD-T-0253       General Specification Procedure for Moisture
                  Determination in Food

  MIL-PRF-44073   Performance Specification -- Packaging of Food in
                  Flexible Pouches

  Production      Meat Entrees, Irradiated, Space Food Prototypes, U.S.
                  Army

  Guide No. 2     SBCCOM, 5 June, 2001
  --------------- -------------------------------------------------------

Food Manufacturing Specifications

  ----------- -----------------------------------------------------------
  SS-F-0018   Sliced Beef with BBQ Sauce

  SS-F-0019   Dried Beef

  SS-F-0020   Beef Pattie

  SS-F-0021   Beef Ravioli

  SS-F-0022   Beef Steak

  SS-F-0023   Beef Stroganoff with Noodles

  SS-F-0025   Breakfast Roll

  SS-F-0026   Brownies

  SS-F-0027   Candy Coated Chocolates

  SS-F-0028   Candy Coated Peanuts

  SS-F-0029   Bran Chex

  SS-F-0030   Cornflakes

  SS-F-0031   Granola

  SS-F-0032   Granola with Blueberries

  SS-F-0033   Granola with Raisins

  SS-F-0034   Grits with Butter

  SS-F-0035   Oatmeal with Brown Sugar

  SS-F-0036   Oatmeal with Raisins and Spice

  SS-F-0037   Rice Krispies

  SS-F-0038   Cheddar Cheese Spread

  SS-F-0039   Grilled Chicken

  SS-F-0040   Chicken Salad

  SS-F-0041   Sweet and Sour Chicken

  SS-F-0042   Teriyaki Chicken

  SS-F-0043   Spicy Chicken and Vegetables

  SS-F-0044   Cashew Chicken Curry

  SS-F-0045   Chicken Strips in Salsa

  SS-F-0046   Butter Cookies

  SS-F-0047   Shortbread Cookies

  SS-F-0048   Crackers

  SS-F-0049   Scrambled Eggs

  SS-F-0050   Mexican Scrambled Eggs

  SS-F-0051   Seasoned Scrambled Eggs

  SS-F-0052   Fettuccine

  SS-F-0053   Frankfurters

  SS-F-0054   Applesauce

  SS-F-0055   Dried Apricots

  SS-F-0056   Fruit Cocktail in Cans

  SS-F-0057   Peach Ambrosia

  SS-F-0058   Peaches in Cans

  SS-F-0059   Dried Peaches

  SS-F-0060   Pears in Cans

  SS-F-0061   Dried Pears

  SS-F-0062   Pineapple in Cans

  SS-F-0063   Strawberries

  SS-F-0064   Trail Mix

  SS-F-0065   Granola Bar

  SS-F-0066   Ham

  SS-F-0068   Apple Jelly

  SS-F-0069   Grape Jelly

  SS-F-0070   Macaroni and Cheese

  SS-F-0071   Noodles and Chicken

  SS-F-0072   Almonds

  SS-F-0073   Cashews

  SS-F-0074   Macadamia Nuts

  SS-F-0075   Peanuts

  SS-F-0076   Pasta Vegetable Parmesan

  SS-F-0077   Peanut Butter

  SS-F-0078   Potatoes au Gratin

  SS-F-0079   Banana Pudding

  SS-F-0080   Butterscotch Pudding

  SS-F-0081   Chocolate Pudding

  SS-F-0082   Tapioca Pudding

  SS-F-0083   Vanilla Pudding

  SS-F-0084   Rice with Butter

  SS-F-0085   Rice and Chicken

  SS-F-0086   Rice Pilaf

  SS-F-0087   Salmon

  SS-F-0088   Sausage Pattie

  SS-F-0089   Seafood Chowder

  SS-F-0090   Shrimp Cocktail

  SS-F-0091   Chicken Consommé

  SS-F-0092   Cream of Mushroom Soup

  SS-F-0093   Spaghetti with Meat Sauce

  SS-F-0094   Tuna

  SS-F-0095   Tuna Salad Spread

  SS-F-0097   Smoked Turkey

  SS-F-0098   Turkey Tetrazzini

  SS-F-0099   Asparagus

  SS-F-0100   Broccoli au Gratin

  SS-F-0101   Cauliflower with Cheese

  SS-F-0102   Corn

  SS-F-0103   Black Beans

  SS-F-0104   Green Beans and Mushrooms

  SS-F-0105   Italian Vegetables

  SS-F-0106   Mashed Potatoes

  SS-F-0107   Vegetable Risotto

  SS-F-0108   Creamed Spinach

  SS-F-0109   Tomatoes & Eggplant

  SS-F-0110   Apple Cider

  SS-F-0111   Cherry Drink with Artificial Sweetener

  SS-F-0112   Cocoa

  SS-F-0113   Coffee, Black

  SS-F-0114   Coffee with Artificial Sweetener

  SS-F-0115   Coffee with Cream

  SS-F-0116   Coffee with Cream and Artificial Sweetener

  SS-F-0117   Coffee with Cream and Sugar

  SS-F-0118   Coffee with Sugar

  SS-F-0119   Decaffeinated Coffee, Black

  SS-F-0120   Decaffeinated Coffee with Artificial Sweetener

  SS-F-0121   Decaffeinated Coffee with Cream and Sugar

  SS-F-0122   Decaffeinated Coffee with Sugar

  SS-F-0123   Decaffeinated Coffee with Cream and Artificial Sweetener

  SS-F-0124   Decaffeinated Coffee with Cream

  SS-F-0125   Kona Coffee, Black

  SS-F-0126   Kona Coffee with Artificial Sweetener

  SS-F-0127   Kona Coffee with Cream

  SS-F-0128   Kona Coffee with Sugar

  SS-F-0129   Kona Coffee with Cream and Artificial Sweetener

  SS-F-0130   Kona Coffee with Cream and Sugar

  SS-F-0131   Grape Drink

  SS-F-0132   Grape Drink with Artificial Sweetener

  SS-F-0133   Grapefruit Drink

  SS-F-0134   Chocolate Breakfast Drink

  SS-F-0135   Strawberry Breakfast Drink

  SS-F-0136   Vanilla Breakfast Drink

  SS-F-0137   Lemonade

  SS-F-0138   Lemonade with Artificial Sweetener

  SS-F-0139   Lemon-Lime Drink

  SS-F-0140   Orange Drink

  SS-F-0141   Orange Drink with Artificial Sweetener

  SS-F-0142   Orange-Grapefruit Drink

  SS-F-0143   Orange Juice

  SS-F-0144   Orange-Mango Drink

  SS-F-0145   Orange-Pineapple Drink

  SS-F-0147   Peach-Apricot Drink

  SS-F-0148   Pineapple Drink

  SS-F-0149   Strawberry Drink

  SS-F-0150   Tea

  SS-F-0151   Tea with Artificial Sweetener

  SS-F-0152   Tea with Cream

  SS-F-0153   Tea with Lemon

  SS-F-0154   Tea with Lemon and Artificial Sweetener

  SS-F-0155   Tea with Lemon and Sugar

  SS-F-0156   Tea with Sugar

  SS-F-0157   Tropical Punch

  SS-F-0158   Tropical Punch with Artificial Sweetener

  SS-F-0159   Condiments

  SS-F-0160   Chicken Teriyaki

  SS-F-0161   Spicy Broiled Lamb

  SS-F-0162   Beef Tips with Mushrooms

  SS-F-0163   Pasta with Herbs

  SS-F-0164   Lemon-Lime Ade

  SS-F-0165   Orange Ade

  SS-F-0166   Raspberry Peach Drink with Artificial Sweetener

  SS-F-0167   Candied Yams

  SS-F-0168   Southwestern Corn

  SS-F-0169   Lasagna with Meat

  SS-F-0170   Sweet & Sour Pork

  SS-F-0171   Vegetarian Vegetable Soup

  SS-F-0173   Fiesta Chicken

  SS-F-0174   Grilled Pork Chop

  SS-F-0175   Seafood Gumbo

  SS-F-0176   Tuna Noodle Casserole

  SS-F-0177   Barbecued Beef Brisket

  SS-F-0178   Beef Fajitas

  SS-F-0179   Teriyaki Beef Steak

  SS-F-0180   Breakfast Sausage Links

  SS-F-0185   Cheese Tortellini

  SS-F-0186   Chicken Noodle Soup

  SS-F-0187   Hot and Sour Soup

  SS-F-0188   Tomato Basil Soup

  SS-F-0191   Minestrone Soup

  SS-F-0192   Vegetarian Chili

  SS-F-0193   Beef Stew

  SS-F-0195   Crawfish Etouffee

  SS-F-0196   Fish Veracruz

  SS-F-0197   Peach Yogurt

  SS-F-0198   Raspberry Yogurt

  SS-F-0199   Plain Yogurt

  SS-F-0200   Chicken Fajitas

  SS-F-0201   Drinking Water Container

  SS-F-0203   Split Pea Soup

  SS-F-0204   Chicken with Black Beans

  SS-F-0205   Apples with Spice

  SS-F-0211   Beef Enchiladas

  SS-F-0212   Baked Tofu

  SS-F-0213   Carrot Coins

  SS-F-0214   Meatloaf

  SS-F-0215   Potato Soup

  SS-F-0216   Roasted Vegetables and Potatoes

  SS-F-0217   Bread Pudding

  SS-F-0218   Cherry Blueberry Cobbler

  SS-F-0219   Chicken with Peanut Sauce

  SS-F-0220   Curry Sauce with Vegetables

  SS-F-0221   Red Beans and Rice

  SS-F-0222   Squash Casserole

  SS-F-0223   Tofu with Hoisin Sauce

  SS-F-0224   Tofu with Hot Mustard Sauce

  SS-F-0225   Shrimp Cocktail (Processed In-House)

  SS-F-0226   Apricot Cobbler

  SS-F-0228   Chocolate Pudding Cake

  SS-F-0229   Cranapple Dessert

  SS-F-0234   Baked Beans

  SS-F-0235   Green Beans & Potatoes

  SS-F-0236   Mixed Vegetables

  SS-F-0237   Pasta with Pesto Sauce

  SS-F-0238   Mango-Peach Smoothie

  SS-F-0239   Green Tea

  SS-F-0240   Green Tea with Sugar

  SS-F-0241   Candy Coated Almonds

  SS-F-0242   Nut and Fruit Granola Bar

  SS-F-0243   Yogurt Covered Granola Bar

  SS-F-0244   Tea with Cream and Sugar

  SS-F-0245   Salmon in Pouches

  SS-F-0246   Tuna in Pouches

  SS-F-0247   Chicken w/ Corn & Black Beans

  SS-F-0248   Brown Rice

  SS-F-0249   Cheese Grits

  SS-F-0250   Citrus Fruit Salad

  SS-F-0251   Homestyle Potatoes

  SS-F-0252   Potato Medley

  SS-F-0253   Rhubarb Applesauce

  SS-F-0254   Sugar Snap Peas

  SS-F-0255   Tropical Fruit Salad

  SS-F-0256   Blueberry Raspberry Yogurt

  SS-F-0257   Chocolate Yogurt

  SS-F-0258   Mocha Yogurt

  SS-F-0259   Strawberry Yogurt

  SS-F-0260   Strawberry Banana Yogurt

  SS-F-0261   Chocolate Milk Drink
  ----------- -----------------------------------------------------------

ATTACHMENT J-24

RESERVED

ATTACHMENT J-25

RESERVED

ATTACHMENT J-26

RESERVED

ATTACHMENT J-27

RESERVED

ATTACHMENT J-28

IDIQ EFFORT

**J-28.1 [INDEFINITE DELIVERY/INDEFINITE QUANTITY (IDIQ) CLAUSES
(ATTACHMENT J-28)]{.underline}**

The purpose of this attachment is to provide a contract mechanism to
authorize work that is of a recurring nature and cannot be sufficiently
identified, predetermined, or quantified in advance, and is identified
as IDIQ work. The IDIQ work the Government currently anticipates is
identified in Paragraph J-28.7 of Attachment J-28 of contract
NNJ06VA01C, and all clauses contained in the contract apply to all tasks
performed under Attachment J-28 unless specifically identified
otherwise.

**J-28.2 [ORDERING (FAR 52.216-18) (OCT 1995)]{.underline}**

(a) Any supplies and services to be furnished under this contract shall
    be ordered by issuance of delivery orders or task orders by the
    individuals or activities designated in the Schedule. Such orders
    may be issued from October 1, 2006, through September 30, 2010.

(b) All delivery orders or task orders are subject to the terms and
    conditions of this contract. In the event of conflict between a
    delivery order or task order and this contract, the contract shall
    control.

(c) If mailed, a delivery order or task order is considered \"issued\"
    when the Government deposits the order in the mail. Orders may be
    issued orally, by facsimile, or by electronic commerce methods only
    if authorized in the Schedule.

**J-28.3 [ORDER LIMITATION (FAR 52.216-19) (OCT 1995)]{.underline}**

(a) *Minimum order.* When the Government requires supplies or services
    covered by this contract in an amount of less than \$1,000,000, the
    Government is not obligated to purchase, nor is the Contractor
    obligated to furnish, those supplies or services under the contract.

(b) *Maximum order.* The Contractor is not obligated to honor --

```{=html}
<!-- -->
```
(1) Any order for a single item in excess of \$10,000,000;

(2) Any order for a combination of items in excess of \$10,000,000; or

(3) A series of orders from the same ordering office within 5 days that
    together call for quantities exceeding the limitation in
    subparagraph (b)(1) or (2) of this section.

```{=html}
<!-- -->
```
(c) If this is a requirements contract (i.e., includes the Requirements
    clause at subsection 52.216-21 of the Federal Acquisition Regulation
    (FAR)), the Government is not required to order a part of any one
    requirement from the Contractor if that requirement exceeds the
    maximum-order limitations in paragraph (b) of this section.

(d) Notwithstanding paragraphs (b) and (c) of this section, the
    Contractor shall honor any order exceeding the maximum order
    limitations in paragraph (b), unless that order (or orders) is
    returned to the ordering office within 3 days after issuance, with
    written notice stating the Contractor\'s intent not to ship the item
    called for and the reasons. Upon receiving this notice, the
    Government may acquire the supplies or services from another source.

**J-28.4 [INDEFINITE QUANTITY (FAR 52.216-22) (OCT 1995)]{.underline}**

(a) This is an indefinite-quantity contract for the supplies or services
    specified and effective for the period stated, in the Schedule. The
    quantities of supplies and services specified in the Schedule are
    estimates only and are not purchased by this contract.

(b) Delivery or performance shall be made only as authorized by orders
    issued in accordance with the Ordering clause. The Contractor shall
    furnish to the Government, when and if ordered, the supplies or
    services specified in the Schedule up to and including the quantity
    designated in the Schedule as the \"maximum.\" The Government shall
    order at least the quantity of supplies or services designated in
    the Schedule as the \"minimum.\"

(c) Except for any limitations on quantities in the Order Limitations
    clause or in the Schedule, there is no limit on the number of orders
    that may be issued. The Government may issue orders requiring
    delivery to multiple destinations or performance at multiple
    locations.

(d) Any order issued during the effective period of this contract and
    not completed within that period shall be completed by the
    Contractor within the time specified in the order. The contract
    shall govern the Contractor\'s and Government\'s rights and
    obligations with respect to that order to the same extent as if the
    order were completed during the contract\'s effective period;
    *provided*, that the Contractor shall not be required to make any
    deliveries under this contract after September 30, 2010.

**J-28.5 [INDEFINITE DELIVERY/INDEFINTE QUANTITY (IDIQ)]{.underline}**

The minimum amount of combined delivery orders required for services
detailed in Attachment J-28 shall be \$1,000,000. The total value of
task orders issued by this clause shall not exceed \$200,000,000.

The total maximum contract value for Attachment J-28 is as follows:

Maximum Estimated Cost \$TBN

Maximum Available Award Fee [\$TBN]{.underline}

Total Maximum Value \$TBN

**J-28.6 [IDIQ RATE PROVISION]{.underline}**

The provisions of this clause apply only to the work performed under
Attachment J-28. The purpose of this clause is to set forth the direct,
indirect, and fee rates to be utilized in the subsequent negotiation and
cost establishment of IDIQ Task Orders in accordance with Task Ordering
Procedure. The contractor will utilize the direct, indirect and fee
rates established herein to determine the estimated costs for each IDIQ
Task Order.

The rates are set forth under Table B, [IDIQ Rates]{.underline}, of this
attachment. Direct and indirect rates established within this table
shall be subject to revision, either upward or downward, only upon the
issuance of a Forward Pricing Rate Agreement. Subcontractor direct and
indirect rates established within this table may be revised annually,
either upward or downward, within the first quarter of the calendar
year. Prime or subcontractor rates used to establish cost, once a task
order has been issued, are firm for the duration of the task and not
subject to adjustment. To effect such revisions, the rates table will be
updated via supplemental agreement, and said rates shall be effective
from the date of issuance of the supplemental agreement. Fee rates shall
not be subject to revision.

**J-28.7 [IDIQ STATEMENT OF WORK]{.underline}**

Any Task Order authorizing work under the IDIQ section of the contract
will be issued under the general scope of the contract. The IDIQ
mechanism is meant to enable the expeditious implementation of work
within the broad, general scope of the contract, for which specific
contract scope has not previously been authorized, for a limited period.
Such work may include effort that would typically be accomplished via
change to the Core or Provisioning Statement of Work.

Each Task Order issued shall be tracked in Table A, [IDIQ Task
Orders]{.underline}, found at the end of Attachment J-28, and a high
level statement of work summary for the Task Order shall be included
following the table.

**J-28.8 [METHOD OF PLACING TASK ORDERS]{.underline}**

(a) Only the Contracting Officer may issue Task Orders to the
    Contractor. The Contractor may incur costs under this contract in
    performance of Task Orders and Task Order modifications issued in
    accordance with this clause. No other costs are authorized unless
    otherwise specified in the contract or expressly authorized by the
    Contracting Officer.

(b) The contractor and Government shall jointly develop the Task Order
    scope of work. Once agreed upon, the Contracting Officer shall issue
    a Work Plan Request.

(c) The Contractor shall make every effort to respond to Work Plan
    Requests in the timeliest manner possible. The timelines established
    below are provided for reference purposes only. In the event the
    Contractor requires more time to generate and submit a Work Plan, a
    request for additional time shall be made to the Contracting
    Officer. The following milestone schedule identifies targets for
    completion of tasks necessary to facilitate timely processing of
    task order requirements. It is noted that these milestone dates are
    nominal and actual completion schedules will depend upon task
    difficulty, complexity, and the ability to agree on specific tasks
    necessary to accomplish the desired work content. The parties
    acknowledge that in some cases task order processing will require
    less time than is outlined below and in some cases may require more.

(d) The contractor will provide acknowledgement of the Work Plan Request
    within 2 business days of receipt.

(e) The Contractor and Government shall jointly develop and partner the
    requirements of the Work Plan within 18 business days (nominal flow)
    of receipt of the Work Plan Request.

(f) The Contractor shall submit a priced Work Plan to the Government
    within 23 business days of receipt of the Work Plan Request.

(g) The Work Plan from the Contractor shall include the technical
    approach, period of performance, cost information, and any other
    information required to determine the reasonableness of the
    Contractor\'s proposal.

(h) Within 5 business days of priced Work Plan receipt, the Contracting
    Officer shall either; (a) require clarification from the Contactor;
    or, (b) approve the work plan and make any desired or necessary
    changes to accommodate the Contractor\'s proposed staffing,
    deliverables, or costs.

(i) After review and any necessary discussions, the Contracting Officer
    may issue a Task Order to the Contractor containing, as a minimum,
    the following:

```{=html}
<!-- -->
```
(1) Date of the delivery order.

(2) Contract number and delivery order number.

(3) Task Description and assumptions

(4) Item/items ordered, including quantity, unit price, and amount of
    each.

(5) Total dollar amount authorized.

(6) Delivery/performance schedule, including start and end dates.

(7) Signature of the Contracting Officer.

```{=html}
<!-- -->
```
(j) Once the Task Order is issued, the Contractor may incur cost under
    this contract for the work authorized.

(k) If time constraints do not permit issuance of a fully defined Task
    Order in accordance with the procedures described in paragraphs (a)
    through (f), a Task Order, which includes a Not-to-Exceed Total
    Dollar authorized, may be issued. Under such circumstances, the
    parties agree to enter into good faith negotiations to establish a
    definitive value based on the principles described herein. If a task
    order is issued ***prior*** to CO acceptance of a Priced Work Plan,
    then the task order is an undefinitized contract action that must be
    reported appropriately.

(l) The Contracting Officer may amend Task Orders in the same manner in
    which they were issued.

(m) In the event of a conflict between the requirements of the Task
    Order and the Contractor's approved Work Plan, the Task Order shall
    prevail.

(n) Approved Task Orders are issued by the Contracting Officer and
    followed with a subsequent Supplemental Agreement, which will
    include the contract value change (Section B) as well as an update
    to Attachment J-8, Fee Plan, and this Attachment J-28 (paragraphs
    J-28.5 and Table A).

**J-28.9 [PLACEMENT OF TASK ORDERS AND SUBMISSION OF WORK
PLANS]{.underline}**

In addition to the material required in Attachment J-28.8, the
contractor shall submit the following information:

The Work Plan shall be based on the rates set forth in this Attachment
J-28.

Partnering will be conducted as necessary, and a Task Order value for
the specific work will be agreed upon. In the event the parties cannot
agree on a Task Order value (or any other term or condition of a Work
Plan), the Contracting Officer shall issue a Task Order, which includes
a Not-to-Exceed Total Dollar amount authorized. Under such
circumstances, the parties agree to enter into good faith negotiations
to establish a definitive value based on the principles described
herein.

The Contractor's Work Plan shall:

Specify a clear and concise plan of activities to be performed to
complete the work defined in the Work Plan Request.

Provide staffing requirements and proposed labor hours necessary to
complete the work.

Provide estimates for other direct costs, subcontract, material and
travel required to complete the work, with the basis of estimate for
such costs.

The negotiated/accepted Work Plan and its costs shall become the basis
of the Task Order. The Contractor shall manage the aggregate of skills
in accordance with the agreed to Work Plan.

Table A

[IDIQ Task Orders]{.underline}

+--------------+----------------------+----+--------+-----+----------+
| [Task        | [Period              | [  | [Esti  | [   | [Total   |
| Order]       | Covered]{.underline} | Re | mated] | Tot | Va       |
| {.underline} |                      | v] | {.unde | al] | lue]{.un |
|              |                      | {. | rline} | {.u | derline} |
| [Number]     |                      | un |        | nde |          |
| {.underline} |                      | de | [Cost] | rli | [Or      |
|              |                      | rl | {.unde | ne} | der]{.un |
|              |                      | in | rline} |     | derline} |
|              |                      | e} |        | [F  |          |
|              |                      |    |        | ee] |          |
|              |                      | [  |        | {.u |          |
|              |                      | No |        | nde |          |
|              |                      | .] |        | rli |          |
|              |                      | {. |        | ne} |          |
|              |                      | un |        |     |          |
|              |                      | de |        |     |          |
|              |                      | rl |        |     |          |
|              |                      | in |        |     |          |
|              |                      | e} |        |     |          |
+--------------+----------------------+----+--------+-----+----------+
| []{.mark}    |                      |    |        |     |          |
+--------------+----------------------+----+--------+-----+----------+

[]{.mark}

[Task Order SOW:]{.underline}

**Attachment J-28**

[]{.mark}

Table B

[IDIQ Rates]{.underline}

[WITHHELD FOIA EXEMPTION (b)(4)]{.underline}

ATTACHMENT J-29

PERSONAL IDENTITY VERIFICATION (PIV) CARD ISSUANCE PROCEDURES

**[PIV Card Issuance Procedures in accordance with]{.underline}** FAR
clause 52.204-9, Personal Identity Verification of Contractor Personnel

FIPS 201 Appendix A graphically displays the following procedure for the
issuance of a PIV credential.

![](media/image3.png){width="4.954861111111111in"
height="3.7270833333333333in"}

Figure A-1, FIPS 201, Appendix A

The following steps describe the procedures for the NASA Personal
Identity Verification Card Issuance (PCI) of a PIV credential:

**[Step 1]{.underline}**:

The Contractor's Corporate Security Officer (CSO), Program Manager (PM),
or Facility Security Officer (FSO) submits a formal letter that provides
a list of contract employees (applicant) names requesting access to the
NASA Contracting Officer's Technical Representative (COTR). In the case
of a foreign national applicant, approval through the NASA Foreign
National Management System (NFNMS) must be obtained for the visit or
assignment before any processing for a PIV credential can take place.
Further, if the foreign national is not under a contract where a COTR
has been officially designated, the foreign national will provide the
information directly to their visit/assignment host, and the host
sponsor will fulfill the duties of the COTR mentioned herein. In each
case, the letter shall provide notification of the contract or foreign
national employee's (hereafter the "applicant") full name (first, middle
and last), social security number (SSN) or NASA Foreign National
Management System Visitor Number if the foreign national does not have a
SSN, and date of birth. If the contract employee has a current
satisfactorily completed National Agency Check with Inquiries (NACI) or
an equivalent or higher degree of background investigation, the letter
shall indicate the type of investigation, the agency completing the
investigation, and date the investigation was completed. ~~Also, the
letter must specify the risk/sensitivity level associated with the
position in which each applicant will be working (NPR 1600.1, §4.5 is
germane)~~ Further, the letter shall also acknowledge that contract
employees may be denied access to NASA information or information
systems based on an unsatisfactory background
investigation/adjudication. .

After reviewing the letter for completeness ~~and concurring with the
risk/sensitivity levels~~, the COTR/host must forward the letter to the
Center Chief of Security (CCS). The CCS shall review the OPM databases
(e.g., DCII, PIP, et al.), and take appropriate steps to validate the
applicant's investigation status. Requirements for a NACI or other
investigation shall be initiated only if necessary.

Applicants who do not currently possess the required level of background
investigation shall be directed to the e-QIP web site to complete the
necessary background investigation forms online. The CCS shall provide
to the COTR/host information and instructions on how to access the e-QIP
for each contract or foreign national employee requiring access

**[Step 2]{.underline}**:

Upon acceptance of the letter/background information, the applicant will
be advised that in order to complete the investigative process, he or
she must appear in-person before the authorized PIV registrar and submit
two forms of identity source documents in original form. The identity
source documents must come from the list of acceptable documents
included in Form I-9, Employment Eligibility Verification, one which
must be a Federal[^1] or State issued picture identification.
Fingerprints will be taken at this time. The applicant must appear **no
later than** the entry on duty date.

When the applicant appears, the registrar will electronically scan the
submitted documents; any document that appears invalid will be rejected
by the registrar. The registrar will capture electronically both a
facial image and fingerprints of the applicant. The information
submitted by the applicant will be used to create or update the
applicant identity record in the Identity Management System (IDMS).

[**Step 3**:]{.underline}

Upon the applicant's completion of the investigative document, the CCS
reviews the information, and resolves discrepancies with the applicant
as necessary. When the applicant has appeared in person and completed
fingerprints, the package is electronically submitted to initiate the
NACI. The CCS includes a request for feedback on the NAC portion of the
NACI at the time the request is submitted.

**[Step 4]{.underline}**:

Prior to authorizing physical access of a contractor employee to a
federally-controlled facility or access to a Federal information system,
the CCS will ensure that a check has been performed with the National
Crime Information Center (NCIC) and Interstate Identification Index. In
the case of a foreign national, a national check of the Bureau of
Immigration and Customs Enforcement (BICE) database will be performed
for each applicant. If this process yields negative information, the CCS
will immediately notify the COTR/host of the determination regarding
access made by the CCS.

**[Step 5]{.underline}**:

Upon receipt of the completed NAC, the CCS will update IDMS from the NAC
portion of the NACI and indicate the result of the suitability
determination. If an unsatisfactory suitability determination is
rendered, the COTR will advise the contractor that the employee is being
denied physical access to all federally-controlled facilities and
Federal information systems.

Based on a favorable NAC and NCIC/III or BICE check, the CCS will
authorize the issuance of a PIV federal credential in the Physical
Access Control System (PACS) database. The CCS, based on information
provided by the COTR/host, will determine what physical access the
applicant should be granted once the PIV issues the credential.

**[Step 6]{.underline}**:

Using the information provided by the applicant during his or her
in-person appearance, the PIV card production facility creates and
instantiates the approved PIV card for the applicant with an activation
date commensurate with the applicant's start date.

**[Step 7]{.underline}**:

The applicant proceeds to the credential issuance facility to begin
processing for receipt of his/her federal credential.

The applicant provides to the credential issuing operator proof of
identity with documentation that meets the requirements of FIPS 201 (DHS
Employment Eligibility Verification (Form I-9) documents. These
documents **must** be the same documents submitted for registration.

The credential issuing operator will verify that the facial image, and
optionally reference finger print, matches the enrollment data used to
produce the card. Upon verification of identity, the operator will
locate the employee's record in the PACS database, and modify the record
to indicate the PIV card has been issued. The applicant will select a
PIN for use with his or her new PIV card. Although root data is
inaccessible to the operator, certain fields (hair color, eye color, et
al.) may be modified to more accurately record the employee's
information.

The applicant proceeds to a kiosk or other workstation to complete
activation of the PIV card using the initial PIN entered at card
issuance.

**[ALTERNATIVE FOR APPLICANTS WHO DO NOT HAVE A COMPLETED AND
ADJUDICATED NAC AT THE TIME OF ENTRANCE ON DUTY]{.underline}**

Steps 1 through 4 shall be accomplished for all applicants in accordance
with the process described above. If the applicant is unable to appear
in person until the time of entry on duty, or does not, for any other
reason, have a completed and adjudicated NAC portion of the NACI at the
time of entrance on duty, the following interim procedures shall apply.

1.  If the documents required to submit the NACI have not been completed
    prior to EOD, the applicant will be instructed to complete all
    remaining requirements for submission of the investigation request.
    This includes presentation of I-9 documents and completion of
    fingerprints, if not already accomplished. If the applicant fails to
    complete these activities as prescribed in NPR 1600.1 (Chapters 3 &
    4), it may be considered as failure to meet the conditions required
    for physical access to a federally-controlled facility or access to
    a Federal information system, and result in denial of such access.

2.  Based on favorable results of the NCIC, the applicant shall be
    issued a temporary NASA identification card for a period
    not-to-exceed six months. If at the end of the six month period the
    NAC results have not been returned, the agency will at that time
    make a determination if an additional extension will be granted for
    the temporary identification card.

3.  Upon return of the completed NAC, the process will continue from
    Step 5.

[^1]: A non-PIV government identification badge, including the NASA
    Photo Identification Badge, [MAY NOT BE USED]{.underline} for the
    original issuance of a PIV vetted credential