<table>
<colgroup>
<col style="width: 11%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 10%" />
<col style="width: 1%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 11%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 12%" />
<col style="width: 5%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td></td>
<td colspan="6"><p>National</p>
<p>Aeronautics and</p>
<p>Space</p>
<p>Administration</p></td>
<td colspan="10">Contract</td>
</tr>
<tr class="even">
<td colspan="4"><ol start="2" type="1">
<li><p>DPAS: <strong>DO-C9</strong></p></li>
</ol></td>
<td colspan="4"><ol start="2" type="1">
<li><p>PPC: <strong>BX</strong></p></li>
</ol></td>
<td colspan="5"><ol start="2" type="1">
<li><p>INITIATING OFFICE: <strong>OM</strong></p></li>
</ol>
<blockquote>
<p>Space Station Program Integration Office</p>
</blockquote></td>
<td colspan="4">4. PAGE <strong>1</strong> OF <strong>68</strong></td>
</tr>
<tr class="odd">
<td colspan="5"><p>5. CONTRACT NUMBER</p>
<p><strong>NAS9-00089</strong></p></td>
<td colspan="3"><p>6. EFFECTIVE DATE</p>
<p><strong>See Block 17b</strong></p></td>
<td colspan="5"><ol start="7" type="1">
<li><p>PROCUREMENT REQUEST NUMBER:</p></li>
</ol>
<blockquote>
<p><strong>01-081-OA1 (N)</strong></p>
</blockquote></td>
<td colspan="4">8. VENDOR CODE</td>
</tr>
<tr class="even">
<td colspan="6">9. ISSUED BY:</td>
<td colspan="2">CODE <strong>BG</strong></td>
<td colspan="7">10. ADMINISTERED BY: (If Other than Item 9)</td>
<td colspan="2">CODE</td>
</tr>
<tr class="odd">
<td colspan="6"><p><strong>NASA Johnson Space Center</strong></p>
<p><strong>Attn: BG/Julia Trautman</strong></p>
<p><strong>Houston, TX 77058</strong></p></td>
<td colspan="2"></td>
<td colspan="7"></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="8"></td>
<td colspan="7">Administrator:</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="6">11. PAYMENT WILL BE MADE BY:</td>
<td colspan="2">CODE <strong>LF231</strong></td>
<td colspan="7">12. SUBMIT INVOICES TO:</td>
<td colspan="2">CODE</td>
</tr>
<tr class="even">
<td colspan="8"><p><strong>NASA Johnson Space Center</strong></p>
<p><strong>Funding and Commercial Accounts</strong></p>
<p><strong>Mail Code: LF231</strong></p>
<p><strong>Houston, TX 77058</strong></p></td>
<td colspan="9"><p><strong>NASA Johnson Space Center</strong></p>
<p><strong>Attn: BG/Contracting Officer</strong></p>
<p><strong>Houston, TX 77058</strong></p></td>
</tr>
<tr class="odd">
<td colspan="11">13. ACCOUNTING AND APPROPRIATION DATA</td>
<td colspan="6"><p>14. CONTRACT TYPE</p>
<p><strong>Cost Plus Incentive Fee</strong></p></td>
</tr>
<tr class="even">
<td colspan="11"><strong>477-70-50-30-6A-OA2550-OA11</strong></td>
<td colspan="6"><p>15. INCREMENTAL FUNDING</p>
<h6 id="yes"> Yes</h6></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="7">SECTION DESCRIPTION</td>
<td>PAGE</td>
<td colspan="6">SECTION DESCRIPTION</td>
<td>PAGE</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="7">CONTRACT COVER PAGE</td>
<td><strong>1</strong></td>
<td colspan="6">SPECIFICATION/STATEMENT OF WORK</td>
<td><strong>12-19</strong></td>
</tr>
<tr class="odd">
<td colspan="2">TABLE OF</td>
<td colspan="7">FULL TEXT CLAUSES</td>
<td><strong>2-4</strong></td>
<td colspan="6">REPORTING AND SCHEDULE MILESTONES</td>
<td><strong>20</strong></td>
</tr>
<tr class="even">
<td colspan="2">CONTENTS</td>
<td colspan="7">CLAUSES INCORPORATED BY REFERENCE</td>
<td><strong>4-7</strong></td>
<td colspan="6">DELIVERABLE ITEMS DESCRIPTION</td>
<td><strong>21</strong></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="7">ACRONYM LIST</td>
<td><strong>8-9</strong></td>
<td colspan="6">DATA REQUIREMENTS</td>
<td><strong>22-67</strong></td>
</tr>
<tr class="even">
<td colspan="2"><mark></mark></td>
<td colspan="7">APPLICABLE DOCUMENTS</td>
<td><strong>10-11</strong></td>
<td colspan="6">QUALITY AND RELIABILITY REQUIREMENTS</td>
<td><strong>58-63</strong></td>
</tr>
<tr class="odd">
<td colspan="17"><p>16. ITEMS AWARDED UNDER THIS CONTRACT</p>
<p><strong>Common Attach System – Berthing Cues System for the
International Space Station</strong></p></td>
</tr>
<tr class="even">
<td colspan="17"></td>
</tr>
<tr class="odd">
<td colspan="3"><p>UNITED</p>
<p>STATES OF</p></td>
<td colspan="14"><ol start="17" type="1">
<li><p>NAME OF CONTRACTING OFFICER</p></li>
</ol>
<h6 id="james-p.-gips">James P. Gips </h6></td>
</tr>
<tr class="even">
<td colspan="3">AMERICA</td>
<td colspan="10">17a. SIGNATURE</td>
<td colspan="4">17b. DATE</td>
</tr>
<tr class="odd">
<td colspan="17"></td>
</tr>
<tr class="even">
<td colspan="17">CONTRACTOR - COMPLETE ALL ITEMS BELOW</td>
</tr>
<tr class="odd">
<td colspan="9">CONTRACTOR NAME AND ADDRESS</td>
<td colspan="3">DISCOUNT TERMS</td>
<td colspan="5"><p>TOTAL AMOUNT OF CONTRACT</p>
<p>$7,452,000</p></td>
</tr>
<tr class="even">
<td colspan="9"></td>
<td colspan="8">NAME AND TITLE OF SIGNER <em>(Type or print)</em></td>
</tr>
<tr class="odd">
<td colspan="9">CONTRACT ADMINISTRATOR (<em>Name and telephone
number)</em></td>
<td colspan="5">SIGNATURE <em>(Of person authorized to sign)</em></td>
<td colspan="3">DATE</td>
</tr>
<tr class="even">
<td colspan="17">NASA Form 1668 (Dec 97) (MS Word Jun 95)</td>
</tr>
</tbody>
</table>

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

The contractor shall provide a Common Attach System -- Berthing Cue
System for the International Space Station as defined in Paragraph 13,
[Specification/Statement of Work]{.underline}. The specific
deliverables, found in detail in Paragraph 14, [Project Reporting and
Scheduling Milestones]{.underline}, Paragraph 15, [Deliverable Item
Descriptions]{.underline}, and Paragraph 16, [Deliverable Items
List]{.underline}.

**2. [ESTIMATED COST AND INCENTIVE FEE (1852.216-84)(OCT
1996)]{.underline}**

The target cost of this contract is \$7,236,424 (US). The target fee of
this contract is \$578,911 (US). The total target cost and target fee as
contemplated by the Incentive Fee clause of this contract are
**\$7,815,335 (US)**.

The maximum fee is \$723,642 (US).

The minimum fee is \$217,093 (US).

The cost sharing for cost underruns is:

Government: 70 percent Contractor: 30 percent.

The cost sharing for cost overruns is:

Government: 70 percent Contractor: 30 percent.

**3. [COMPLETION OF CONTRACT]{.underline}**

All deliveries shall be completed by **September 30, 2003**.

**4. [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. 
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:

Not applicable

            (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.\
     (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:\
            (1)  One original Standard Form (SF) 1034, SF 1035, or
equivalent Contractor\'s attachment to:

Defense Contract Management Area Office-Canada

#### NASA Coordinator

275 Bank Street, Suite 200

Ottawa, Ontario, Canada K2P-2L6

            (2)  Three 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:\
                  (i)   Copy 1 NASA Contracting Officer\
                  (ii)  Copy 2 Auditor\
                  (iii) Copy 3 Contractor\
            (3)  The Contracting Officer may designate other recipients
as required.\
     (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 -- Johnson Space Center

> Attn: BG/Contracting Officer
>
> 2101 NASA Rd 1
>
> 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.

**5. [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 **\$6,097,575**. This allotment is for
all contract line items and covers the following estimated period of
performance:

April 16, 2001 through **November 30, 2002**.

\(b\) An additional amount of **\$508,425** is obligated under this
contract for payment of fee.

**6. [DUTY-FREE ENTRY OF SPACE ARTICLES (1852.225-8)]{.underline}**

All items listed in Contract NAS 9-00089 Paragraph 15 are to be accorded
duty-free entry.

**7. [INSPECTION AND ACCEPTANCE]{.underline}**

\(a\) Preliminary inspection of flight items required under this
contract will take place at the Contractor's facility by the Contracting
Officer or his duly authorized representative.

\(b\) Final inspection and acceptance will be performed at destination
by the Contracting Officer or his duly authorized representative. All
shipments, except Data Requirements reports which provide separate
delivery instructions, shall be shipped to the following address:

Ship to: Transportation Officer/JB7,

Building 421

####  NASA Johnson Space Center

2101 NASA Road 1

Houston, TX 77058-3696

Mark for: Accountable Property Officer

Mark with: Contract Number: NAS 9-00089

For reissue to: Henry Orosco OM 4South 4815C

(Name) (Mail Code) (Bldg.) (Rm.)

\(c\) All shipments/deliveries of hardware items shall be accompanied by
either a DD Form 250, "Material Inspection and Receiving Report", or a
DD Form 1149, "Requisition and Invoice/Shipping document", whichever is
appropriate.

8\. **[USE OF GOVERNMENT FACILITIES ON A RENT FREE BASIS]{.underline}**

The Government facilities and labor to operate these facilities
described in this paragraph 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 responsibility for any Government property damage
or loss.

Antenna Test Facility (Building 14) for EMI Evaluation Testing

Vibration Acoustics Test Facility (Building 49) Vibration Testing

Thermal Chamber Facility (Building 33) Thermal Vacuum Testing

**9. [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):

a.  For all Federal Acquisition Regulations (FAR) clauses -
    http://www.arnet.gov/far/;

```{=html}
<!-- -->
```
a.  For all NASA FAR clauses -
    hhtp://www.hq.nasa.gov/office/procurement/regs/nfstoc.htm

NOTICE: The following clauses are hereby incorporated by reference.

A. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) CLAUSES

52.202-1 Definitions (Oct 1995)

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 (Jul
1995)

52.203-7 Anti-Kickback Procedures (Jul 1995)

52.203-8 Cancellation, Rescission, and Recovery of Funds for Illegal or
Improper

> Activity (Jan 1997)

52.203-10 Price or Fee Adjustment for Illegal or Improper Activity (Jan
1997)

52.203-12 Limitation on Payments to Influence Certain Federal
Transactions (Jun 1997)

52.204-4 Printed or Copied Double-Sided on Recycled Paper (Aug 2000)

52.209-6 Protecting the Government\'s Interest When Subcontracting with
Contractors

> Debarred, Suspended, or Proposed for Debarment (Jul 1995)

52.211-5 Material Requirements (Aug 2000)

52.211-15 Defense Priority and Allocation Requirements (Sep 1990)

52.215-2 Audit and Records -- Negotiation (Jun 1999) -- Alternate I (Jan
1997)

52.215-11 Price Reduction for Defective cost or Pricing Data --
Modifications (Oct 1997)

52.215-13 Subcontractor Cost or Pricing Data -- Modifications (Oct 1997)

52.215-14 Integrity of Unit Prices (Oct 1997)

52.215-15 Pension Adjustments and Asset Reversions (Dec 1998)

52.215-18 Reversions or Adjustments of Plans for Postretirement Benefits
(PRB) Other Than Pensions (Oct 1997)

52.215-21 Requirements for Cost or Pricing Data or Information Other
Than Cost or

Pricing Data - Modifications (Oct 1997)

52.216-7 Allowable Cost and Payment (Mar 2000)

52.216-10 Incentive Fee (Mar 1997)

52.219-4 Notice of Price Evaluation Preference for HUBZone Small
Business Concerns

> (Jan 1999)

52.219-8 Utilization of Small Business Concerns (Oct 1999)

52.219-9 Small Business Subcontracting Plan (Oct 1999) -- Alternate II
(Jan 1999)

52.219-16 Liquidated Damages -- Subcontracting Plan (Jan 1999)

52.222-1 Notice to the Government of Labor Disputes (Feb 1997)

52.222-20 Walsh-Healey Public Contracts Act (Dec 1996)

52.222-21 Prohibition of Segregated Facilities (Feb 1999)

52.222-26 Equal Opportunity (Feb 1999)

52.222-35 Affirmative Action for Disabled Veterans and Veterans of the
Vietnam Era

(Apr 1998)

52.222-36 Affirmative Action for Workers with Disabilities (Jun 1998)

52.222-37 Employment Reports on Disabled Veterans and Veterans of the
Vietnam

> Era (Jan 1999)

52.223-6 Drug-Free Workplace (Jan 1997)

52.223-14 Toxic Chemical Release Reporting (Oct 1996)

52.225-13 Restrictions on Certain Foreign Purchases (Jul 2000)

52.227-1 Authorization and Consent (Jul 1995)

52.227-2 Notice and Assistance Regarding Patent and Copyright
Infringement (Aug 1996)

52.227-14 Rights in Data \-- General (Jun 1987) \-- As Modified by NASA
FAR Supplement

> 1852.227-14 Alternate II (Jun 1987) and Alternate III (June 1987)

52.228-7 Insurance -- liability to Third Persons (Mar 1996)

52.230-3 Disclosure and Consistency of Cost Accounting Practices (Apr
1998)

52.230-6 Administration of Cost Accounting standards (Nov 1999)

52.232-17 Interest (Jun 1996)

52.232-22 Limitation of Funds (Apr 1984)

52.232-23 Assignment of Claims (Jan 1986)

52.232-25 Prompt Payment (Jun 1997) \[Insert 17th day in subparagraph
(a)(1)(i)(A), (a)(1)(i)(B), and (a)(1)(ii)\]

52.232-33 Payment by Electronic Funds Transfer -- Central Contractor
Registration

> (May 1999)

52.233-1 Disputes (Dec 1998) \-- Alternate I (Dec 1991)

52.233-3 Protest After Award, Alternate 1 (Jun 1995)

52.242-1 Notice of Intent to Disallow Costs (Apr 1984)

52.242-3 Penalties for Unallowable Costs (Oct 1995)

52.242-4 Certification of final Indirect Costs (Jan 1997)

52.242-13 Bankruptcy (Jul 1995)

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

52.243-2 Changes -- Cost Reimbursement (Aug 1987), Alternate V (Apr
1984)

52.243-7 Notification of Changes (Apr 1984)

52.244-2 Subcontracts (Aug 1998) -- Alternate I (Aug 1998)

52.244-5 Competition in Subcontracting (Dec 1996)

52.244-6 Subcontracts for Commercial Items and Commercial Components
(Oct 1998)

52.245-5 Government Property (Cost Reimbursement, Time-and-Material, or

> Labor-Hour Contracts) (Jan 1986)

52.246-8 Inspection of Research and Development -- Cost-Reimbursement
(Apr 1984)

52.246-24 Limitation of Liability-High Value Items (Feb 1997

52.248-1 Value Engineering (Feb 2000)

52.249-6 Termination (Sep 1996)

52.249-14 Excusable Delays (Apr 1984)

52.252-6 Authorized Deviations in Clauses (Apr 1984) (Insert \"NASA FAR
Supplement

> (48 CFR Chapter 18)\" in paragraph (b))

52.253-1 Computer Generated Forms (Jan 1991)

[]{.mark}

B. NASA/FAR SUPPLEMENT (48 CFR CHAPTER 18) CLAUSES

[]{.mark}

1852.204-74 Central Contractor Registration (Aug 2000)

1852.204-76 Security Requirements For Unclassified
Technology Information Resources \
(July 2000)

1852.215-84 Ombudsman (Jun 2000) (Insert in subparagraph (b):

> \"Debra Johnson/BA
>
> 2101 NASA Rd 1
>
> Houston, TX 77058
>
> ph. (281) 483-4157
>
> debra.l.johnson1@jsc.nasa.gov\" and "Before consulting with any
> ombudsman, interested parties must try to resolve their concerns with
> the Contract Specialist or the Contracting Officer. DO NOT CALL THE
> OMBUDSMAN FOR SOLICITATION REQUESTS/INFORMATION.\")

1852.216-89 Assignment and Release Forms (Jul 1997)

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-70 Safety and Health (Jul 2000)

1852.223-75 Major Breach of Safety or Security (Jul 2000)

1852.227-70 New Technology (Nov 1998)

1852.227-85 Invention Reporting and Rights -- Foreign (Apr 1986)

1852.228-76 Cross-Waiver of Liability for Space Station (Jun 1994)

70. Center for Aerospace Information -- Final Scientific and Technical
    Reports

(Jul 2000)

1852.242-73 NASA Contractor Financial Management Reporting (Jul 1997)

1852.243-71 Shared Savings (Mar 1997)

1852.245-73 Financial Reporting of Property in the custody of
Contractors (Nov 1999)

1852.246-72 Material Inspection and Receiving Report (Jun 1995) \[Insert
"an original and 1

copy" in paragraph (a).\]

**10. [REPRESENTATIONS, CERTIFICATIONS, AND OTHER STATEMENTS
OF]{.underline}**

> **[OFFERORS OR QUOTERS INCORPORATED BY REFERENCE (JSC 52.209-90) (Sept
> 1988)]{.underline}**

This contract incorporates the Representations, Certifications, and
Other Statements of Offeror, as set forth in the contractor\'s proposal
dated [November 10, 2000]{.underline}, by reference, with the same force
and effect as if it were given in full text.

**11. [ACRONYM LIST]{.underline}**

ACAS Active Common Attach System

ADP Acceptance Data Package

AMS Alpha Magnetic Spectrometer

AR Acceptance Review

BCS Berthing Cue System

CAS Common Attach System

CCITT Consultative Committee on Telephony and Telegraphy

CDR Critical Design Review

CEI Contract End Item

CI Configuration Item

CIL Critical Items List

COTS Commercial-off-the-Shelf

COU Concept of Operations and Utilization

DCR Design Certification Review

DID Deliverable Item Description

DR Data Requirement

EMC Electromagnetic Compatibility

EMI Electromagnetic Interference

ERU Engineering Release Unit

ESP External Stowage Pallet

EVA Extravehicular Activity

EVR Extravehicular Robotics

EXP Express Pallet

FCA Functional Configuration Audit

FMEA Failure Modes and Effects Analysis

FQR Formal Qualification Review

FSE Flight Support Equipment

GFE Government Furnished Equipment

GSE Ground Support Equipment

GSRP Ground Safety Review Panel

ICD Interface Control Document

IP International Partner

IRD Interface Requirements Document

ISS International Space Station

ISSP International Space Station Program

IVA Intravehicular Activity

LSB Least Significant Bit

MBS Mobile Remote Servicer Base System

MCAS Mobile Base System Common Attach System

MIUL Materials Identification Usage Lists

MRMDF Multi-use Remote Manipulator Development Facility

MSB Most Significant Bit

MSS Mobile Servicing System

MT Mobile Transporter

MUA Materials Usage Agreements

ORU Orbital Replacement Unit

PALS Program Automated Library System

PCA Physical Configuration Audit

PCAS Passive Common Attachment System

PCS Portable Computer System

PDA Pre-delivery Acceptance

PDL Program Design Language

PDR Preliminary Design Review

PLB Payload Bay

PRACA Problem Reporting and Corrective Action

PRR Production Readiness Review

PVGF Power Video Grapple Fixture

RTL Ready-to-Latch

RWS Robotic Workstation

SDR System Design Review

SLP Spacelab Pallet

SOW Statement of Work

SRP Safety Review Panel

SRR System Requirements Review

SRMS Shuttle Remote Manipulator System

SSP Space Station Program

SSRMS Space Station Remote Manipulator System

SVF Software Verification Facility

TCS Thermal Conditioning System

TPR Team of Primary Responsibility

TRR Test Readiness Review

ULC Unpressurized Logistics Carrier

VMDB Vehicle Master Database

WBS Work Breakdown Structure

**12. [APPLICABLE DOCUMENTS]{.underline}**

+-----------------------+----------------------------------------------+
|                       |                                              |
+-----------------------+----------------------------------------------+
| SSP 30223             | Problem Reporting and Corrective Action      |
|                       | (PRACA) for the Space Station Program        |
+-----------------------+----------------------------------------------+
| SSP 30233             | Space Station Requirements for Materials and |
|                       | Processes                                    |
+-----------------------+----------------------------------------------+
| SSP 30234             | Failure Modes and Effects Analysis and       |
|                       | Critical Items List Requirements for Space   |
|                       | Station                                      |
+-----------------------+----------------------------------------------+
| SSP 30256             | Extravehicular Activity (EVA) Standard       |
|                       | Interface Control Document                   |
+-----------------------+----------------------------------------------+
| SSP 30309             | Safety Analysis and Risk Assessment          |
|                       | Requirements Document                        |
+-----------------------+----------------------------------------------+
| SSP 30312             | Electrical, Electronic, and                  |
|                       | Electromechanical (EEE) and Mechanical Parts |
|                       | Management and Implementation Plan for Space |
|                       | Station Program                              |
+-----------------------+----------------------------------------------+
| SSP 30558             | Fracture Control Requirements for Space      |
|                       | Station                                      |
+-----------------------+----------------------------------------------+
| SSP 30599             | Safety Review Process                        |
+-----------------------+----------------------------------------------+
| SSP 30695             | Acceptance Data Package Requirements         |
|                       | Specification                                |
+-----------------------+----------------------------------------------+
| SSP 41000             | Systems Specification for the International  |
|                       | Space Station                                |
+-----------------------+----------------------------------------------+
| SSP 41167             | Mobile Servicing System Segment              |
|                       | Specification for the International Space    |
|                       | Station Program                              |
+-----------------------+----------------------------------------------+
| SSP 41170             | Configuration Management Requirements        |
+-----------------------+----------------------------------------------+
| SSP 41171             | Preparation of Program-Unique Specifications |
+-----------------------+----------------------------------------------+
| SSP 41172             | Qualification and Acceptance Environmental   |
|                       | Test Requirements                            |
+-----------------------+----------------------------------------------+
| SSP 41173             | Space Station Quality Assurance Requirements |
+-----------------------+----------------------------------------------+
| SSP 42003             | Space Station Manned Base to Mobile          |
|                       | Servicing System Interface Control Document  |
+-----------------------+----------------------------------------------+
| SSP 42004             | Mobile Servicing System to User (Generic)    |
|                       | Interface Control Document                   |
+-----------------------+----------------------------------------------+
| SSP 50005             | International Space Station Flight           |
|                       |                                              |
|                       | Crew Integration Standard                    |
+-----------------------+----------------------------------------------+
| SSP 50021             | Safety Review Process                        |
+-----------------------+----------------------------------------------+
| SSP 50287             | Hardware/Software Acceptance Process and     |
|                       | Requirements                                 |
+-----------------------+----------------------------------------------+
|                       |                                              |
+-----------------------+----------------------------------------------+
| SSP 50123             | Configuration Management Handbook            |
+-----------------------+----------------------------------------------+
| SSP 50486             | #                                            |
|                       | ### Pre-Flight Imagery Requirements for NASA |
|                       |  Provided ISS Government Furnished Equipment |
+-----------------------+----------------------------------------------+
| SSP 57003             | Attach Payload Interface Requirements        |
|                       | Document                                     |
+-----------------------+----------------------------------------------+
| NASA Procedures and   | Procedures for Exchanging Parts, Materials,  |
| Guidelines (NPG)      | and Safety Problem Data Utilizing the        |
| 8735.1                | Government-Industry Data Exchange Program    |
|                       | and NASA Advisories                          |
| NPG 9501.2C           |                                              |
|                       | Procedures for Contractor Reporting of       |
| NSTS 07700, Volume    | Correlated Cost and Performance Data         |
| XIV                   |                                              |
|                       | Space Shuttle System Payload Accommodations  |
+-----------------------+----------------------------------------------+
| NASA-STD-6001         | Flammability, Odor, and Offgassing           |
|                       | Requirements and Test Procedures for         |
|                       | Materials in Environments that Support       |
|                       | Combustion                                   |
+-----------------------+----------------------------------------------+
| MSFC-HDBK-527/MAPTIS  | Materials Selection List for Space Hardware  |
|                       | Systems                                      |
| MIL-R-28002           |                                              |
|                       | Requirements for Raster Graphics             |
| JSC-28763             | Representation in Binary Format              |
|                       |                                              |
| DOD-D-1000            | Project Technical Requirements Specification |
|                       | for the Centerline Berthing Camera System    |
| DOD-STD-100           |                                              |
|                       | Drawings, Engineering and Associated Lists   |
|                       |                                              |
|                       | Engineering Drawing Practices                |
+-----------------------+----------------------------------------------+

\*NOTE: The most recent version of each of the applicable documents, at
the start date of this contract, shall be used.

**13. [SPECIFICATION/STATEMENT OF WORK]{.underline}**

## 13.1 [Introduction]{.underline} {#introduction .SOW-HDG2 .unnumbered}

## 13.1.1 Statement of Need {#statement-of-need .unnumbered}

The International Space Station Program (ISSP) has a need for the
development of a system to provide robotic operators with visual cues in
support of Common Attach System (CAS) berthing operations. Potential CAS
mounted payloads include pallets such as the Unpressurized Logistics
Carrier (ULC), Express Pallet (EXP) and full truss site payloads such as
the Alpha Magnetic Spectrometer (AMS). Current plans are for the ISS to
have seven CAS berthing locations. CAS mechanisms are to be installed on
the S3 (4 sites) and P3 (2 sites) truss elements and on the Mobile
Remote Servicer Base System (MBS) (1 site). Orbital stay times for CAS
mounted pallets and payloads will differ, and could be on the order of
months or years. However, the MBS will be used as a temporary berthing
location only, as payloads are transferred from the space shuttle
payload bay to an International Space Station (ISS) CAS location.

This contract provides only the avionics packages, targets, and
installation GSE as detailed in the following statement of work.

### 13.1.2 Concept Definition {#concept-definition .unnumbered}

The following concept definition in subsections 13.1.2.1, [Berthing Cues
System]{.underline}, and 13.1.2.2, [Operations]{.underline}, is offered
as background information and is not considered a requirement. Detailed
design activities, conducted as a part of this contract, will determine
the actual concept implementation.

### 13.1.2.1 Berthing Cues System  {#berthing-cues-system .unnumbered}

The design approach for CAS berthing cues utilizes a payload-mounted
camera with a boresight view of an ISS mounted visual target. This, in
conjunction with Robotic Workstation (RWS) video screen overlays,
provides the robotics operator with sufficient cues to safely and
accurately guide payloads to a ready-to-latch (RTL) state on the CAS.

The Berthing Cues System (BCS) consists of on-orbit based components,
including target(s), camera(s) and light(s), and is considered a
criticality 2 system. Specialized Ground Support Equipment (GSE)
supports installation, calibration, and verification activities for the
BCS. BCS targets are mounted on the active half of ISS CAS elements as
they are readied for launch and remain on-orbit. The camera(s) and
light(s) are combined with a power video grapple fixture (PVGF), which
is installed on pallets and payloads prior to launch. Once returned,
these BCS elements may be re-used on other payloads on later flights.

During on-orbit berthing operations, the BCS is linked to the ISS Mobile
Servicing System (MSS) through a PVGF mounted on the payload. The PVGF
provides power, video, and data connectivity between the BCS and the
MSS. The BCS provides power and data pass-through between the PVGF and
payload during berthing operations. Payloads have the capability to
receive power, monitor payload status, and issue payload commands
through this link during berthing operations. Once berthed, power to
support BCS long-term survival is provided by the payload.

### 13.1.2.2 Operations {#operations .unnumbered}

The BCS is used in conjunction with the Space Station Remote Manipulator
System (SSRMS) and Shuttle Remote Manipulator System (SRMS) to berth
pallets and payloads at ISS CAS berthing locations. In some cases, the
SSRMS is used to grapple the payload and remove it directly from the
shuttle payload bay (PLB). A joint operation may be performed in which
the payload is removed from the PLB by the SRMS, and then "handed off"
to the SSRMS.

Once removed from the PLB, the payload is translated to the target CAS
location and berthing operations commence. In some cases, this requires
that the payload first be berthed to the Mobile Base System (MBS) CAS
(MCAS) for translation on the Mobile Transporter (MT) to the desired CAS
location.

The BCS specific operational scenario is as follows:

1.  Utilizing the RWS and RWS Portable Computer System (PCS), the
    operator initiates power to MSS payload busses, thus activating the
    BCS camera package. This activates cameras, light, and support
    systems including power and video conditioning as well as thermal
    control systems.

2.  The operator selects an appropriate video overlay for the RWS.

3.  The operator utilizes the boresight camera view(s) of the berthing
    target (mounted on the active CAS (ACAS)) in conjunction with RWS
    video overlays in order to maneuver the payload into the RTL
    position at the CAS.

4.  Upon RTL indication, the capture latch mechanism is commanded to
    close using the PCS.

5.  The operator removes power from the MSS payload bus, thus shutting
    down BCS systems.

6.  Upon successful payload power-up, the payload provides power to the
    BCS in order to maintain operation of the BCS thermal conditioning
    systems (TCS).

## 13.1.3 Definition of Terms {#definition-of-terms .unnumbered}

Throughout this document the following definitions apply:

a)  The term "avionics package" refers to the hardware necessary to meet
    the operational need for one payload. Depending on the design
    implementation, this could mean one or more cameras, one or more
    lights, associated mounting hardware, cabling and wiring.

```{=html}
<!-- -->
```
a)  Similarly, the term \"target\" infers all of the hardware needed to
    provide target capability on one ACAS mechanism. This could imply
    one or more targets and associated mounting hardware.

b)  A single \"BCS kit\" is defined as one complete set of all the above
    components.

d\) The BCS uses the PAS coordinate system defined in section
3.1.3.1.2.1 Payload Attach System Coordinate System Origin Location, of
SSP 57003, Attached Payload Interface Requirements Document,
International Space Station Program, baseline revision, September 22,
1999. The following terms are defined using this coordinate system:

i.  Lateral refers to an offset in position in a plane that is parallel
    to the PAS X-Y plane. It is a positive quantity, and can occur in
    any direction.

ii. Wobble refers to the total angular deviation from a normal to the
    PAS X-Y plane. It is a positive quantity, and can occur in any
    direction from the normal. A normal to the PAS X-Y plane is
    considered to have a wobble of 0.

iii. Axial refers to an offset in position along a line that is parallel
     to the PAS Z axis.

iv. Roll is defined as a rotation about any line that is parallel to the
    PAS Z axis.

# 13.2 Design Requirements {#design-requirements .unnumbered}

##  {#section-1 .unnumbered}

## 13.2.1 Control {#control .unnumbered}

The sole means of BCS shall be through application of power from a
source external to the BCS and the removal of that power.

**13.2.2 Interchangeability**

a\) BCS targets shall be identical for use at all CAS sites.

b\) The contractor shall identify a common target and camera mounting
location at all CAS sites and for all payloads.

**13.2.3 Operator Envelope**

Starting at a pre-install position, 36 inches above the mated position,
and continuing through to the mated position, the BCS shall provide cues
that enable the SSRMS operator to discern alignment, between the active
and passive CAS interface mechanisms, within a corridor of the following
dimensions:

  ------------------------------------ ----------------------------------
  **Degree Of Freedom**                **Alignment Envelope**

  PAS X and Y directions               ±1.0 inch

  Roll                                 ±1.5 degrees

  Wobble                               1.5 degrees in any direction
  ------------------------------------ ----------------------------------

**13.2.4 Hardware Alignment Budget**

a\) The target alignment (target cues with respect to target mounting
interface) and avionics

> package alignment (camera views with respect to avionics package
> mounting interface) shall
>
> be set prior to delivery.

b\) The combined error between these components and interfaces shall be
within the following

> budget:
>
> (Wobble ≤ 0.25 degrees) and (Lateral/0.364 inches + \|Roll\|/0.8
> degrees ≤ 1),

c\) Verification of the above alignment shall address measurement
tolerances during fabrication,

> assembly and verifications, EVA replacement of the berthing cues, and
> the effects of on-orbit
>
> environments on position and attitude.

**13.2.5 Adjustability**

a\) The BCS avionics package shall provide a minimum alignment mechanism
adjustment capability of:

  -------------------------------- --------------------------------------
  **Degree Of Freedom**            **Adjustment Range**

  Lateral                          0.375 inches in any direction

  Roll                             ±1.5 degrees

  Wobble                           0.5 degrees in any direction
  -------------------------------- --------------------------------------

b\) The BCS target shall provide a minimum wobble alignment mechanism
adjustment capability of 0.5 degree in any direction.

**13.2.6 Power**

The following power requirements are applicable at the BCS avionics
package connector interface:

a\) The BCS shall be compatible with MSS power quality requirements
specified in SSP 42004, MSS to User (Generic) Interface Control Document
Part I, paragraph A3.2.1.5.1, Power Quality.

b\) During payload berth and unberth operations, the BCS shall utilize
no more than 30 watts.

c\) During payload berth and unberth operations, the BCS shall have the
capability to pass through at least 1800 watts of power to the payload.
The intent of this requirement is to permit payloads having peak power
consumption ratings between 0 and 1800 watts to operate without damaging
the BCS avionics package.

d\) BCS keep-alive power shall be no greater than 10 watts.

**13.2.7 Video**

The BCS shall be compatible with MSS video requirements specified in SSP
42004, MSS to User (Generic) Interface Control Document Part I,
paragraph A3.2.1.7, Synch Control and Video Interfaces.

**13.2.8 Target On-Orbit Servicing**

a\) The BCS target assembly shall be designed to be on-orbit serviceable
in accordance with SSP 50005 and SSP 30256.

b\) Viable solutions may include provisions for EVA replacement of all
or a portion of the target.

**13.2.9 Fault Tolerance**

The BCS avionics shall be at least single fault tolerant for operations.

**13.2.10 Operating Conditions**

a\) The BCS shall be capable of operating continuously for a minimum
period of 36 hours.

b\) The BCS shall perform the functions defined in this section under
the follow lighting conditions:

i\) with direct sunlight on any portion of the target,

ii\) with direct sunlight illuminating any portion of the camera, but
excluding the case where

the sun is directly within the camera field of view,

iii\) with direct sunlight on all of the target,

iv\) with direct sunlight on all of the camera, but excluding the case
where the sun is directly

within the camera field of view,

v\) in complete darkness.

**13.2.11 Electromagnetic Compatibility**

**13.2.11.1 Electromagnetic Design and Construction Standards**

The BCS shall conform to the design and construction requirements as
specified below:

a\) Wiring and cabling design external to the BCS shall be in accordance
with SSP 30242, Space Station Cable and Wiring Design Requirements.

b\) Bonding provisions for the BCS shall be in accordance with SSP
30245, Space Station Bonding Requirements.

c\) Grounding provisions for the BCS shall be in accordance with SSP
30240, Space Station Grounding Requirements.

d\) Electrostatic Discharge design requirements shall be in accordance
with SSP 30243, Space Station Requirements for Electromagnetic
Compatibility, Paragraph 3.2.10.

**13.2.11.2 Electromagnetic Emission and Susceptibility Requirements**

a\) The BCS shall be designed to meet the electromagnetic emission and
susceptibility requirements specified in SSP 30237, Space Station
Electromagnetic Emission and Susceptibility Requirements.

b\) The BCS shall not malfunction, or have unacceptable responses to
surges, ripples, voltages, and other electrical conditions that can
cause interference or susceptibility, when supplied with electrical
power as defined in paragraph 13.2.6, Power.

c\) EMI testing of the BCS shall be carried out per SSP 30238, Space
Station Electromagnetic Techniques.

**13.2.12 Ionizing Radiation Environment Compatibility**

**13.2.12.1 Radiation Dose Environment**

a\) Electrical/electronic components and equipment shall meet their
specified performance requirements when exposed to the radiation dose
environment as defined in Table 3.1.2-1, Table 3.1.2-2, and illustrated
in Figures 3.1.3-1 and 3.1.3-2 of SSP 30512.

b\) A radiation dose design margin of two shall be applied.

c\) The total dose environment defined in paragraph 1.2.1 is based on an
orbital lifetime of one year. The total dose environment for orbital
lifetimes other than one year shall be a linear extrapolation of the
given value.

**13.2.12.2 Single Event Effects Environment**

The BCS shall meet specified performance when exposed to the nominal
Single Event Effects environment defined in Table 3.2.1.4-1, and Figure
3.2.1.4-1 of SSP 30512.

**13.2.13 Service Lifetime**

a\) The BCS target shall perform the functions defined in this section
without servicing, for a period of 5 years from the date of acceptance.

b\) The BCS avionics package shall perform the functions defined in this
section for a period of 15 years from the date of acceptance, which can
be assumed to consist of five 3-year missions with five 36-hour periods
of berth/unberth operations per mission.

c\) Refurbishment may be used as a means of achieving the BCS avionics
package service life requirement specified in b) above. The maximum CAS
mounted payload orbital stay time is assumed to be 5 years. After the
orbital stay, the payload would be returned to the ground and the BCS
avionics package would be available for refurbishment.

# 13.3 Contract Tasks and Deliverables {#contract-tasks-and-deliverables .unnumbered}

This section describes the major contract tasks and deliverables that
are required in this contract.

## 13.3.1 Systems Analysis  {#systems-analysis .unnumbered}

a)  The contractor shall provide a structural analysis report (DR 17) to
    verify that the BCS meets performance specifications with the
    specified structural interface(s).

```{=html}
<!-- -->
```
a)  The contractor shall develop a thermal analysis report (DR 18) to
    verify that the BCS meets performance specifications with the
    specified thermal interface.

## 13.3.2 Safety and Reliability Analysis  {#safety-and-reliability-analysis .unnumbered}

a)  The contractor shall perform and document a failure modes and
    effects and critical items list analysis (DR 9) in accordance with
    SSP 30234, Failure Modes and Effects Analysis and Critical Items
    List Requirements for Space Station.

```{=html}
<!-- -->
```
a)  The contractor shall perform and document a safety analysis (DR 8)
    in accordance with SSP 30309, Safety Analysis and Risk Assessment
    Requirements Document and SSP 50021, Safety Requirements.

b)  The contractor shall perform and provide a limited life analysis.

## 13.3.3 New Documentation {#new-documentation .unnumbered}

a)  The contractor shall develop detailed system specifications for the
    BCS to include both ground and on-orbit components: ground support
    equipment, camera(s), light(s), cable harness(es) and target(s) as
    defined in DR 14.

```{=html}
<!-- -->
```
a)  The contractor shall develop and submit detailed engineering
    drawings compatible with ISS electronic databases including: Vehicle
    Master Database (VMDB) and Program Automated Library System (PALS)
    as defined in DR 3.

## 13.3.4 Traceability and Verification  {#traceability-and-verification .unnumbered}

a)  As defined by DR 20, Specification Traceability and Compliance
    Reports, the contractor shall provide reports documenting detailed
    traceability of all BCS requirements to ISS requirements.

```{=html}
<!-- -->
```
a)  As defined by DR 10, Verification Test Requirements Traceability,
    the contractor shall develop a Verification Plan Matrix documenting
    methods to be used in verification of BCS requirements.

b)  As defined by DR 12, Verification Test Reports, the contractor shall
    provide verification closure reports.

## 13.3.5 Qualification and Acceptance Testing {#qualification-and-acceptance-testing .unnumbered}

a)  The contractor shall develop a Qualification and Acceptance Test
    Plan meeting the requirements of SSP 41172, according to DR 31.

```{=html}
<!-- -->
```
a)  The contractor shall develop Qualification and Acceptance Test
    Procedures documenting the procedures required to meet BCS and ISS
    (per SSP 41172) test and verification requirements, according to DR
    11.

## 13.3.6 Closeout Photographs {#closeout-photographs .unnumbered}

The contractor shall develop and implement an imagery plan for closeout
photographs of BCS flight hardware meeting SSP 50486, Pre-Flight Imagery
Requirements for NASA GFE. The plan shall be developed according to DR
23.

### 13.3.7 Crew Evaluations {#crew-evaluations .unnumbered}

The contractor shall perform a crew evaluation of the cue design and
performance. NASA will identify and supply evaluation participants and
provide a crew consensus report.

## 13.3.8 Hardware Deliverables {#hardware-deliverables .unnumbered}

### 13.3.8.1 Flight Hardware Deliverables {#flight-hardware-deliverables .unnumbered}

The contractor shall provide deliverable items as defined in Section 15,
[BCS Deliverable Item Description (DID)]{.underline}.

### 13.3.8.2 GSE Deliverables {#gse-deliverables .unnumbered}

a)  The contractor shall provide one set of all unique tools and
    equipment necessary for turnaround processing at KSC, payload
    integration, and calibration, of the BCS. Equipment required for
    repair and refurbishment of BCS components will be provided through
    a separate sustaining engineering contract.

```{=html}
<!-- -->
```
a)  The contractor shall provide one set of ground handling, storage and
    shipping containers for each BCS avionics package. This includes
    engineering and flight units.

**13.3.8.3 Engineering Unit Deliverables**

The contractor shall provide 1 (one) Engineering Model BCS Avionics
Package for use in the Multi-use Remote Manipulator Development Facility
(MRMDF) (BCS-DID-3). The MRMDF Engineering Model Avionics Package
requires NTSC video output.

### 13.3.9 Procedures {#procedures .unnumbered}

a)  The contractor shall provide procedures to support turnaround
    testing, payload integration, calibration, and storage as defined in
    DR 24.

```{=html}
<!-- -->
```
a)  The contractor shall provide procedures to support on-orbit
    operation as defined in DR 25 and, according to SSP 30256,
    Extravehicular Activity (EVA) Standard Interface Control Document.

### 13.3.10 Training {#training .unnumbered}

a)  The contractor shall develop and provide training for flight crew
    instructors at Johnson Space Center, Houston, TX, in the design,
    performance, features, and use of the BCS. Training should be
    sufficiently comprehensive to permit continued BCS use after
    completion of this contract, as defined in DR 25.

b)  The contractor shall provide training of NASA ground processing
    personnel at the Kennedy Space Center (KSC) in the procedures for
    installation, calibration, alignment, and maintenance of BCS
    equipment. Training should be sufficiently comprehensive to permit
    continued BCS use after completion of this contract, as defined in
    DR 24.

**13.3.11 GIDEP and NASA Advisory Participation**

The contractor shall develop, document and implement a system that will
implement, control, manage, document, and report the efforts, results,
decisions, corrective actions, and track costs (for special problems)
necessary to comply with the participation in the GIDEP and NASA
Advisory reporting systems in accordance with DR 28.

The contractor shall review all GIDEP Alerts, GIDEP Safe-Alerts, GIDEP
Problem Advisories, GIDEP Agency Action Notices, and NASA Advisories to
determine if the problem(s) identified in any of these reports affect
any of the NASA products or operating facilities being produced,
procured, managed and maintained under this contract. For GIDEP Alerts,
GIDEP Safe-Alerts, GIDEP Problem Advisories, GIDEP Agency Action
Notices, and NASA Advisories that are determined to affect the program
products and facilities, the contractor shall take action to eliminate
or mitigate any negative effect to an acceptable level in accordance
with the documentation and reporting requirements of DR 28.

The contractor shall generate the appropriate failure experience data
report (GIDEP Alert, GIDEP Safe-Alert, GIDEP Problem Advisory or NASA
Advisory) in accordance with the requirements of GIDEP and NASA
documents referenced above whenever a problem, failed or nonconforming
item, or safety issue is identified or experienced during the activities
and tasks of complying with this contract when the incident has the
potential of affecting another NASA Program, Government Agency or
contract, or Industry Participant. Any required NASA Advisories are to
be released through the managing NASA Center's NASA Advisory release
system.

**13.3.12 Payload Integration Process and Facility Requirements**

The contractor shall provide engineering support for the development of
the KSC payload integration processes and facility requirements.

**14. PROJECT REPORTING AND SCHEDULE MILESTONES**

**14.1 ISSP Reviews**

a)  The contractor shall conduct ground and flight safety reviews
    according to SSP 30599, Safety Review Process.

```{=html}
<!-- -->
```
a)  The contractor shall conduct launch package and flight readiness
    reviews.

**14.2 Monthly Project Reviews**

a)  The contractor shall provide monthly progress reports as defined in
    DR5.

```{=html}
<!-- -->
```
a)  The contractor shall provide monthly integrated project schedule
    along with periodic updates reflecting current project status as
    defined in DR4.

**14.3 Project Review Schedule**

The contractor shall develop a schedule and conduct the following formal
design reviews in accordance with SSP 41170 and DR4:

Review [Date]{.underline}

a)  System Requirements Review (SRR) 11/29/01 (target)

    01/29/02 (avionics)

```{=html}
<!-- -->
```
a)  System Design Review (SDR) 12/20/01 (target)

    07/30/02 (avionics)

b)  Preliminary Design Review (PDR) included in SDR

c)  Critical Design Review (CDR) included in SDR

d)  Functional Configuration Audit (FCA) included in AR

e)  Physical Configuration Audit (PCA) included in AR

f)  Acceptance Review (AR) 02/28/02 (DID-2)

Acceptance Reviews for all remaining deliverables defined in Section 15,
[BCS Deliverable Item Description (DID)]{.underline}, shall be scheduled
a minimum of 1 week prior to the delivery date identified in the table.

**14.4 Project Schedule**

The contractor shall provide a schedule of key hardware milestones,
including requirements review, PDR, CDR, flight/qualification hardware
fabrication start, pre-delivery acceptance (PDA) test,
qualification/certification testing complete~~,~~ Acceptance Review,
flight/qualification hardware delivery, training hardware delivery, and
any critical path milestones.

# 15. BCS DELIVERABLE ITEM DESCRIPTION (DID) {#bcs-deliverable-item-description-did .unnumbered}

+-----------+----------+----------+----------+-----------------------+
| **DID     | **Del    | **Qu     | **       | ##                    |
| Number**  | iverable | antity** | Delivery | ###### Delivery Point |
|           | Item**   |          | Date**   |                       |
|           | **Re     |          |          |                       |
|           | quired** |          |          |                       |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-1 | Target   | 1 Set    | 03/01/02 | Kennedy Space Center  |
|           | Inst     |          |          | Transportation        |
|           | allation |          |          | Officer               |
|           | GSE      |          |          |                       |
|           |          |          |          | Kennedy Space Center, |
|           |          |          |          | FL 32899              |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS 9-00089 |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-2 | MBS      | 1 Target | 03/01/02 | The Boeing Company    |
|           | Target   |          |          |                       |
|           |          |          |          | PGOC Warehouse, Bldg. |
|           |          |          |          | M6-698                |
|           |          |          |          |                       |
|           |          |          |          | Kennedy Space Center, |
|           |          |          |          | FL 32899              |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS15-10000 |
|           |          |          |          |                       |
|           |          |          |          | Deliver to SSFP,      |
|           |          |          |          | Bldg. M7-360          |
|           |          |          |          |                       |
|           |          |          |          | Notify Kari Capatosto |
|           |          |          |          | 321-867-6612 or       |
|           |          |          |          | Marlene Wright        |
|           |          |          |          | 321-867-6807          |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-3 | Avionics | 1        | 05/30/03 | Johnson Space Center  |
|           | Package  |          |          | Transportation        |
|           | Eng      |          |          | Officer, Bldg 420     |
|           | ineering |          |          | 2101 NASA Rd 1        |
|           | Unit     |          |          | Houston, TX 77058     |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS 9-00089 |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-4 | Quali    | 1        | 09/30/03 | Johnson Space Center  |
|           | fication |          |          | Transportation        |
|           | Avionics |          |          | Officer, Bldg 420     |
|           | Package  |          |          | 2101 NASA Rd 1        |
|           |          |          |          | Houston, TX 77058     |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS 9-00089 |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-5 | Avionics | 1 Set    | 05/30/03 | Kennedy Space Center  |
|           | Inst     |          |          | Transportation        |
|           | allation |          |          | Officer               |
|           | GSE      |          |          |                       |
|           |          |          |          | Kennedy Space Center, |
|           |          |          |          | FL 32899              |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS 9-00089 |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-6 | P 3/4    | 2        | 05/28/02 | Ship to:              |
|           | Targets  | Targets  |          |                       |
|           |          |          |          | The Boeing Company    |
|           |          |          |          |                       |
|           |          |          |          | PGOC Warehouse, Bldg. |
|           |          |          |          | M6-698                |
|           |          |          |          |                       |
|           |          |          |          | Kennedy Space Center  |
|           |          |          |          | , FL 32899            |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS15-10000 |
|           |          |          |          |                       |
|           |          |          |          | Deliver to SSFP, Bldg |
|           |          |          |          | M7-360                |
|           |          |          |          |                       |
|           |          |          |          | Notify Kari Capatosto |
|           |          |          |          | 321-867-6612 or       |
|           |          |          |          | Marlene Wright        |
|           |          |          |          | 321-867-6807          |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-7 | S 3/4    | 4        | 07/12/02 | Ship to:              |
|           | Targets  | Targets  |          |                       |
|           |          |          |          | The Boeing Company    |
|           |          |          |          |                       |
|           |          |          |          | PGOC Warehouse, Bldg. |
|           |          |          |          | M6-698                |
|           |          |          |          |                       |
|           |          |          |          | Kennedy Space Center, |
|           |          |          |          | FL 32899              |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS15-10000 |
|           |          |          |          |                       |
|           |          |          |          | Deliver to SSFP, Bldg |
|           |          |          |          | M7-360                |
|           |          |          |          |                       |
|           |          |          |          | Notify Kari Capatosto |
|           |          |          |          | 321-867-6612 or       |
|           |          |          |          | Marlene Wright        |
|           |          |          |          | 321-867-6807          |
+-----------+----------+----------+----------+-----------------------+
| BCS-DID-8 | Avionics | 3        | 05/30/03 | Kennedy Space Center  |
|           | Packages |          |          | Transportation        |
|           |          |          |          | Officer               |
|           |          |          |          |                       |
|           |          |          |          | Kennedy Space Center, |
|           |          |          |          | FL 32899              |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS 9-00089 |
+-----------+----------+----------+----------+-----------------------+
| ~~BC      | ~~EVA    | ~~4~~    |          | **DID DELETED VIA     |
| S-DID-9~~ | Transfer |          |          | CONTRACT MOD 9**      |
|           | P        |          |          |                       |
|           | ackage~~ |          |          |                       |
+-----------+----------+----------+----------+-----------------------+
| B         | Avionics | 5        | 09/30/03 | Kennedy Space Center  |
| CS-DID-10 | Packages |          |          | Transportation        |
|           |          |          |          | Officer               |
|           |          |          |          |                       |
|           |          |          |          | Kennedy Space Center, |
|           |          |          |          | FL 32899              |
|           |          |          |          |                       |
|           |          |          |          | Mark for: NAS 9-00089 |
+-----------+----------+----------+----------+-----------------------+
| B         | Quali    | 1        | 05/30/03 | Lockheed Martin Space |
| CS-DID-11 | fication |          |          | Operations            |
|           | Target   |          |          |                       |
|           |          |          |          | 2400 NASA Road 1, C79 |
|           |          |          |          |                       |
|           |          |          |          | Houston, TX           |
|           |          |          |          | 77058-3799            |
+-----------+----------+----------+----------+-----------------------+
| B         | Spare FM | 1        | 09/30/02 | Lockheed Martin Space |
| CS-DID-12 | Target   |          |          | Operations            |
|           |          |          |          |                       |
|           |          |          |          | 2400 NASA Road 1, C79 |
|           |          |          |          |                       |
|           |          |          |          | Houston, TX           |
|           |          |          |          | 77058-3799            |
+-----------+----------+----------+----------+-----------------------+

#  16. BCS DATA REQUIREMENTS (DR) LIST {#bcs-data-requirements-dr-list .unnumbered}

  ------------------------------------------------------------------------
  **DR \#**  **DR Title**                                 **Data Type**
  ---------- -------------------------------------------- ----------------
                                                          

  1          Concept of Operations and Utilization (COU)  1

  2          Work Breakdown Structure (WBS) and WBS       1
             Dictionary                                   

  3          Engineering Drawings and Associated Lists    3

  4          Integrated Project Schedule                  2 and 3

  5          Progress Reports                             3

  6          Acceptance Data Package                      2

  7          Data Accession List                          3

  8          Hazard Reports and System Description        2

  9          Failure Modes and Effects Analysis (FMEA)    1 and 3
             and Critical Items List (CIL)                

  10         Verification Test Requirements Traceability  3

  11         Verification Test Procedures                 3

  12         Verification Test Reports                    3

  13         Documentation, Customer Analytical           3
             Integration Capability                       

  14         Development Specifications                   2

  15         Materials Identification Usage Lists (MIUL)  3

  16         Materials Usage Agreements (MUAs)            1 and 3

  17         Structural Loads Control Plan and Reports    1 and 3

  18         Integrated Thermal Control Plan and Reports  1 and 3

  19         Support Equipment Item Description           3

  20         Specification Traceability and Compliance    3
             Reports                                      

  21         Fracture Control Plan                        2

  22         BCS Launch Site Integration Plan             2

  23         Closeout Imagery                             2

  24         BCS Equipment Maintenance Manual             2

  25         BCS Operating Manual                         2

  26         Nonconformance Reports                       3

  27         Problem Reporting and Corrective Action      1
             (PRACA) Reports                              

  28         Government-Industry Data Exchange Program    1 and 3
             (GIDEP) and NASA Advisory Problem Data       
             Sharing and Utilization Program              
             Documentation and Reporting                  

  29         Quality Assurance Program Plan               2

  30         Financial Management Report (NASA Form 533M  3
             & 533Q)                                      

  31         Qualification and Acceptance Test Plan       2
  ------------------------------------------------------------------------

**[Data Type Definitions:]{.underline}**

Type 1 That information and documentation which requires NASA approval
prior to release. Approved type 1 information and documentation shall be
controlled, and deviations from or changes to the concepts, techniques,
and/or requirements stated therein shall require NASA approval prior to
implementation. All work under this contract covered by approved type 1
documents shall be performed in accordance with those approved
documents. The Contracting Officers Technical Representative will have
approval authority and will sign the data prior to its release.
Contractually binding documents will not be implemented nor revised
without contractual authorization.

Type 1 submissions shall be marked "TYPE 1 PRELIMINARY pending NASA
approval or Type I APPROVED BY NASA, as appropriate.\" Additional
special designations and deviations may be required on specific
submissions in accordance with configuration management requirements.

Type 2 That information and documentation for which NASA reserves a
time-limited right to disapprove, in whole or in part. Type 2 data shall
be submitted to JSC for review not less than 30 calendar days 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 received any comment prior to the
released target date, the document may be released for appropriate use.
Any NASA comment received shall be appropriately dispositioned before
the document is to be used. Type 2 data may be approved by NASA prior to
its submittal.

> Type 2 submissions shall be marked "TYPE 2 PRELIMINARY - RELEASE
> TARGET DATE, xx/xx/xx\" or \"TYPE 2 FINAL - NASA COMMENTS INCLUDED\"
> or "TYPE 2 FINAL DOCUMENT,\" where NASA comments were not receive

Type 3 That information and documentation which is provided to NASA for
surveillance, information, review, and/or management control. This
information does not require formal NASA review and approval.
Information in this category would include design solutions, status, and
cost/schedule reporting; analyses and test results, handbooks; and other
designated lists, reports, etc.

Type 3 submissions shall be marked \"TYPE 3 DOCUMENT - FOR INFORMATION,
SURVEILLANCE, REVIEW OR MANAGEMENT CONTROL\".

**DR1 [Concept of Operations and Utilization (COU)]{.underline}**

1\. Use: Support the development and evaluation of complimentary
on-orbit and ground system specifications.

2\. Scope: This DR establishes the content, format, maintenance, and
submittal requirements for the COU Document.

3\. Content: This COU incorporates NASA-developed concepts,
philosophies, and definition to describe the manner in which the BCS is
intended to be operated and utilized. The level of detail of these
descriptions shall be adequate to enable the development and evaluation
of complimentary on-orbit and ground system specification.

4\. Format: The COU shall be delivered in the Contractor's format.

5\. Data Type: 1

6\. Maintenance: The COU shall be maintained electronically.

7\. Frequency of Submission: Draft two weeks before major design reviews
with final release 120 days prior to hardware delivery.

8\. First Submission: Three days before SRR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

**DR2 [Work Breakdown Structure (WBS) and WBS Dictionary]{.underline}**

1\. Use: The WBS and the WBS Dictionary provide the framework for

> structuring the BCS Program (i.e. budgets, staffing and material
> estimates, work authorization documentation) and reporting contractor
> cost, schedule, and technical performance.

2\. Scope: The WBS and WBS Dictionary shall encompass all activities
required to achieve the BCS Program. The WBS shall be structured
consistent with the BCS SOW.

3\. Content: The WBS shall be developed down to the appropriate level
(nominally Level 4) to manage and control the BCS Program. The WBS
Dictionary shall define the activity and contents of each WBS element.

4\. Format: The WBS and WBS dictionary shall be delivered in the
Contractor's format consistent with MIL-STD-881, [Work Breakdown
Structure]{.underline}. The WBS shall be presented in a hierarchy of
increasing levels of detail.

5\. Maintenance: The WBS and WBS Dictionary shall be maintained
electronically.

6\. Remarks: The Contractor shall maintain the WBS and Dictionary
database.

7\. Frequency of Submission: Draft Structure at SRR, final Structure and
Dictionary two weeks before SDR; update as required.

8\. First Submission: Three days before SRR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

**DR3 [Engineering Drawings and Associated Lists]{.underline}**

1\. Use: Provide the design data used to manufacture, install, verify,

> operate, and maintain the products of this contract.

2\. Scope: This DR establishes the content, format, control, and
maintenance of drawings, schematics, and associated lists prepared by
the contractors and/or obtained from subcontractors/vendors for products
of this contract. Subcontractors/vendors responsible for minor
procurements or limited development items, which do not presently use
CAD systems, may be exempt from the electronic transmission and database
requirements herein.

3\. Content: Raster images: Raster images are to be Group 4 raster
images, prepared per MIL-R-28002 and applicable documents. The format
and quality verification requirements for Raster images of engineering
drawings and related documents shall be in conformance with MIL-R-28002,
section 6.2 (Ordering Data). Ordering data to be used for the
interchange of engineering drawing and associated document images are as
follows:

> a\. The basic requirements for interchange of raster image of
> engineering drawings and related documents shall be in accordance with
> Military Specification, Requirements for Raster Graphics
> Representation in Binary Format, MIL-R-28002.
>
> b\. The type of raster graphics being procured is Type 1 (untitled).
>
> c\. The delivery medium to be used shall be either by magnetic or
> electronic transmission, as determined by the Product Group and Tier 1
> Subcontractor organizations involved in the interchange.
>
> d\. Proper viewing orientation shall be based on a picture elements
> path direction of 0 degrees and a line progression direction of 270
> degrees, as defined in section 3.1.1.2, and shown in Figures 1 and 2
> of MIL-R-28002.
>
> e\. Raster image pixel element spacing shall be 200 dpi (dots per
> inch) minimum.
>
> f\. No overscanning is required beyond the drawing sizes listed in
> section 6.3.2; however, overscanning is encouraged to capture
> ancillary information that is placed outside the border, such as CAD
> file name or plot date.

g\. Bit ordering shall be MSB to LSB (most significant bit to least
significant bit).

> h\. Coding of background and foreground information. To the extent
> that a drawing represents lines on paper, the picture elements
> representing lines shall be coded as \"black\" and those picture
> elements representing the paper background shall be coded as "white\".
> This coding convention shall hold, regardless of the colors used for
> display on any particular device, and regardless of the coding as
> \"0\" or \"1\" on any particular system. In this way, white picture
> elements (paper) may be processed as background, and black picture
> elements (lines) may be processed as foreground.

NOTE: The preceding definition of the convention for coding background
and foreground has been provided because a choice of convention has not
been defined in MIL-R-28002 or Consultative Committee on Telephony and
Telegraphy (CCITT) Recommendation T.6. This convention is needed to
support processing of drawing images without human interpretation.

4\. Format: Delivery to NASA of drawings and associated lists will be
made electronically. All drawings, except for \"A\" size book form
drawings shall be delivered in a raster image format. \"A\" size book
form drawings may be delivered in an electronic format other than raster
image as mutually agreed to by the NASA and Contractor organizations
involved in the interchange. Associated lists shall be delivered either
in ASCII or Raster image format. The drawings shall be delivered in the
Contractor\'s format provided the following criteria are met:

> a\. Engineering flight drawings shall be in accordance with the intent
> of DOD-D-1000, Level 3 characteristics, and DOD-STD-100. For
> inseparable, integral items which require no intermediate maintenance
> activities upon installation and operation, specification of part
> marking and identification requirements in all applicable product
> drawings may be considered optional.
>
> b\. Drawings for Ground Support Equipment (GSE), Functionally
> Equivalent Units, and Facility Outfitting shall be in accordance with
> the intent of DOD-D-1000. The following requirements shall be met:
>
> Drawings will be provided to the lowest level of assembly subject to
> replacement during maintenance. Existing drawing or catalog data may
> be provided for items incorporated without alteration into GSE design.
>
> Processes shall be referenced to military specifications, described in
> the drawings, or when referenced to company standards, the standards
> shall be provided as part of the drawing package delivered per this
> DR.
>
> American National Standards Institute (ANSI) standards shall be used
> for dimensions and tolerance.
>
> Acceptance test requirements shall be identified for replaceable
> functional components.
>
> Cable diagrams for the GSE unit shall be provided. Connector reference
> numbers including commercial-off-the-shelf (COTS) receptacles shall be
> shown. COTS connectors shall be identified by the vendor\'s part
> number, cage code (if available) and manufacturer\'s name and address.
>
> c\. Drawings for Facility Outfitting SVF shall be in accordance with
> the intent of DOD-D-1000 (Level 1 classification) and DOD-STD-100.
>
> d\. All design activities shall use the methods designated in
> ASTM-E380 to convert dimensional units from one system (International
> System of Units (SI) or English) to another, where required for
> interfaces with International Partners.
>
> e\. All design activities shall use the U.S. convention on third-angle
> projection in depicting views on drawings.
>
> f\. Where design activity material or process specification numbers
> are called out, they shall be accompanied by the equivalent Government
> or industry specification numbers wherever a Government or industry
> specification is applicable.
>
> g\. Engineering parts list, bill of materials, and note format shall
> be consistent with DOD-STD-100 and delivered in ASCII format, Raster
> Image or Printerleaf with each drawing.
>
> h\. Electronic formats shall provide for magnetic, optical media, or
> electronic transmission exchanges between the Product Group and Prime
> Contractor computer systems.
>
> Delivery of drawings, and associated list files will be electronic.
> The file formats and structures of drawing delivery packages are
> defined in the attachment.
>
> Drawing deliveries may be in either Raster image format, Hewlett
> Packard Graphics Language (HPGL) plot files, or Printerleaf files.
>
> Other associated lists may be delivered as ASCII text files, HPGL plot
> files, Printerleaf files, or raster image format.

5\. Data Type: 3

6\. Maintenance: Changes and/or updating of drawings and list shall be
accomplished in accordance with the Contractor\'s engineering system and
the provisions of the cited applicable documents.

7\. Remarks: Released drawings and associated lists are available
real-time through the Drawing Database and made available for design
reviews as required by individual design review plans. Final drawings
shall be uploaded into the program-authorized electronic library.

8\. Frequency of Submission: Available for major design reviews

9\. First Submission: Avionics: Two weeks before SDR

Targets: Three days before SDR

10\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

11\. References:

\(a\) DOD-D-1000, Drawings, Engineering and Associated Lists

\(b\) DOD-STD-100, Engineering Drawing Practices

> \(c\) MIL-R-28002, Requirements for Raster Graphics Representation in
> Binary Format
>
> \(d\) ASTM-E380, Standard Practice for Use of the International System
> of Units (SI) (The Modernized Metric System)

# DR4 Integrated Project Schedule {#dr4-integrated-project-schedule .unnumbered}

1\. Use: The Integrated Project Schedule shall serve as the basis for
communication with NASA concerning BCS schedule and status.

2\. Scope: The Schedule shall integrate BCS activities with effected ISS
and payload major milestones.

3\. Content: The schedule shall encompass schedule planning
architecture, schedule content, and processes in accordance with SSP
41170.

4\. Format: The schedule shall be delivered in Contractor\'s format.

5\. Data Type: 2 (initial submittal)

3 (updates)

6\. Maintenance: The Integrated Project Schedule shall be maintained
electronically by the contractor.

7\. Frequency of Submission: Monthly

8\. First Submission: 15 days following contract award

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR5 Monthly Progress Reports {#dr5-monthly-progress-reports .unnumbered}

1\. Use: Monthly progress reports shall serve as the basis for
communication with NASA concerning BCS technical status.

2\. Scope: The report shall document progress and issues associated with
system development, production, certification and delivery.

3\. Format: The report shall be delivered in Contractor\'s format.

4\. Data Type: 3

5\. Maintenance: The report shall be maintained electronically by the
contractor.

6\. Frequency of Submission: Seven (7) working days after last day of
the month.

7\. First Submission: 15 days following contract award

8\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Program-authorized electronic library

\(b\) OM/Karl Zimmer

\(c\) BG/Contracting Officer (Notification of delivery only)

# DR6 Acceptance Data Package {#dr6-acceptance-data-package .unnumbered}

1\. Use: Provide using organization with minimum data required to
facilitate integration, operation, refurbishment, modification
activities, etc conducted by the organization receiving hardware custody
for the life of the hardware.

2\. Scope: The ADP is an accumulation of documentation that provides a
verified, complete, and current status of deliverable hardware and/or
software needed by the procuring/using organization to enable the
continuation of required activities.

3\. Content: The ADP contents shall be in accordance with SSP 30695.

4\. Format: The ADP shall be delivered in the Contractor's format in
accordance with SSP 30695.

5\. Data Type: 2

6\. Frequency of Submission: Required with each delivery of a BCS item
from a manufacturer/developer to a using site or deliveries between
using sites. Final ADP delivery to NASA will be reviewed and approved at
AR.

7\. First Submission: Submitted with initial shipment/transfer of item.

8\. Copies and Distribution: 1 original with delivered hardware

9\. References: SSP 30695, Acceptance Data Package Requirements
Specification

## DR7 [Data Accession List (DAL)]{.underline} {#dr7-data-accession-list-dal .Need-HDG-2 .unnumbered}

1\. Use: Provides a list of ERU internally released data, which may be
made available to NASA from the data repositories and/or supplemental
files of the Contractor.

2\. Scope: The DAL serves as a medium for identifying ERU internally
released data which have been generated by the Contractor and his
Subcontractors/Suppliers in compliance with the work effort described in
the Statement of Work.

3\. Content: The DAL shall contain all ERU internally released data.

4\. Format: The DAL shall be in Contractor format.

5\. Data Type: 3

6\. Maintenance: The DAL shall be maintained electronically.

7\. Remarks: Contractor shall prepare and maintain an accession list of
ERU internally released data generated by Contractor during the design,
development, testing, and management of Contractor equipment applicable
to the SOW.

8\. Frequency of Submission: New/added data provided monthly. Complete
listing at major design reviews.

9\. First Submission: Contract Definitization + 1 day

10\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

11\. References: SSP 30695, Acceptance Data Package Requirements
Specification

# DR8 Hazard Reports and System Description {#dr8-hazard-reports-and-system-description .unnumbered}

1\. Use: The ISS Safety Review Panel (SRP) will use the Hazard Reports
and System Description to assess the design and operation of ISS element
hardware configuration. The Ground Safety Review Panel (GSRP) will use
Hazard Reports and System Description to assess ISS cargo element/launch
packages and ground support equipment design and operations for
compliance.

2\. Scope: SM02 shall consist of Hazard Reports and System Descriptions
for all Contractor Provided Hardware and GSE. Additionally, SM02 shall
document integrated hazard analyses for the ISS Vehicle, as defined by
SSP 41000 and modified by Appendix C, except for Node 3.

3\. Content: Hazard Reports and System Descriptions shall be provided
that are commensurate with the level of maturity of the design in
accordance with SSP 30309.

4\. Hazard Report: Hazard Reports shall include the follow data fields:

> \(1\) Hazard Report Number
>
> \(2\) Hazard Title
>
> \(3\) Review Level
>
> \(4\) Revision Date
>
> \(5\) Scope
>
> \(6\) Hazard Description
>
> \(7\) Cause Summary
>
> \(8\) Program Stage
>
> \(9\) Interfaces
>
> \(10\) Status of Work
>
> \(11\) Remarks
>
> \(12\) Submittal Concurrence
>
> \(13\) Approval
>
> \(14\) Mission Phase
>
> \(15\) Severity Category
>
> \(16\) Likelihood of Occurrence
>
> \(17\) Controls
>
> \(18\) Method for Verification of Controls
>
> \(19\) Safety Requirements
>
> \(20\) Detection and Warning Method
>
> \(21\) Cause Remarks
>
> \(22\) CIL Reference
>
> \(23\) Point of Contact

For Phase I maturity, Hazard Reports shall reflect the preliminary
design and define hazards causes. Additionally, provide the preliminary
hazard controls and verification methods when available. For Phase II
maturity, the Hazard Reports shall be updated to reflect the critical
design and define the finalized hazard controls and verification
methods. For Phase II, the Hazard Reports shall be updated to reflect
the as-built contractor design and document completion of verification.

5\. System Description: The Contractor shall provide a description of
the launch and on-orbit configuration of the hardware and software in
accordance with SSP 30599, Safety Review Process. Functional diagrams
shall be submitted and supplemented with descriptions of interfaces and
operations.

6\. Format: These deliverables shall be in the Contractor\'s format.

7\. Data Type: 2

8\. Maintenance: This specification shall be maintained electronically.

9\. Remarks: The Hazard Report and System Description shall be prepared
in accordance with SSP 30599 in support of the safety review process.

10\. Frequency of Submission: Two weeks before each major design review
and with ADP

11\. First Submission: Avionics: Two weeks before PDR

Targets: Three days before PDR

12\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

\(c\) Executive Secretary, Safety Review Panel, NB5\*

\(d\) Chief, Flight Hardware Safety Engineering Branch, KSC, RT-

> SOE-1\*

\(e\) ISS Program independent safety review panel\*

\*Note: Submittal of the Hazard Report and System Description will be
based on associated needs of the Joint ISS and SSP SRP, and GSRP.

13\. References: (a) SSP 30309, Safety Analysis and Risk Assessment

> Requirements Document

\(b\) SSP 30599, Safety Review Process

# DR9 Failure Modes and Effects Analysis (FMEA) and Critical Items List (CIL) {#dr9-failure-modes-and-effects-analysis-fmea-and-critical-items-list-cil .unnumbered}

> 1\. Use: The FMEA serves as a source that documents the systematic
> evaluation by item failure mode analysis, the potential impact of each
> functional or hardware failure on mission success, personnel, and
> systems safety, system performance, maintenance, and maintainability
> requirements. Each potential failure is assessed in order that
> appropriate corrective action(s) may be taken to eliminate or control
> the high-risk items. The CIL documents the item\'s inability to meet
> program requirements.

2\. Scope: The FMEA/CIL shall be performed on program hardware to the
equipment level consistent with the identified on-orbit maintenance
level and ground support equipment as specified in SSP 30234.

3\. Content: The FMEA/CIL contents are specified by SSP 30234.

4\. Format: The data element format shall be specified in SSP 30234.

5\. Data Type: FMEA - 3; CIL - 1

6\. Maintenance: The worksheets shall be maintained electronically.

7\. Frequency of Submission: Two weeks before each major design review
and with ADPs

8\. First Submission: Avionics: Two weeks before PDR

Targets: Three days before PDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

10\. References: SSP 30234, Instructions For Preparation Of Failure
Modes And

> Effects Analysis And Critical Items List For Space Station

# DR10 Verification Test Requirements Traceability {#dr10-verification-test-requirements-traceability .unnumbered}

1\. Use: To ensure that all design and performance requirements are
addressed by the verification program and that all verification program
requirements are closed out.

2\. Scope: This DR provides requirements traceability for all
performance, design and verification requirements.

3\. Content: The traceability system shall include a record of
verification requirements derivation and the subsequent history of
where, by what process in the program, and when the requirements were
satisfied and certified closed.

4\. Format: Contractor format is acceptable.

5\. Data Type: 3

6\. Maintenance: Update as necessary to maintain currency and accuracy.

7\. Frequency of Submission: Two weeks before each major design review
and with ADPs

8\. First Submission: Avionics: Two weeks before PDR

Targets: Three days before PDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

# DR11 Verification Test Procedures {#dr11-verification-test-procedures .unnumbered}

1\. Use: To control tests and document results.

2\. Scope: This DR provides all procedures defining specific objectives,
event sequences, support requirements, configuration identification and
procedures for each test or series of tests.

3\. Content: Each procedure shall identify the verification test
requirements for the item from the related verification specification.
Individual specification requirements to be verified shall be referenced
in a manner that expedites procedure reviewing. As a minimum, the
following information will be included:

> a\. Nomenclature and identification of the test article or material.
> Identification of test configuration and any differences from
> delivered configuration.

b\. Identification of objectives and criteria established for test by
the applicable verification specification.

c\. Characteristics and design criteria to be inspected or tested,
including values with tolerances for acceptance or rejection.

d\. Description, in sequence, of steps and operations taken.

e\. Identification of computer software required.

f\. Identification of measuring, test and recording equipment to be
used, specifying range, accuracy and type.

g\. Certification that required computer test programs/support equipment
and software have been verified prior to use with delivered hardware.

h\. Any special instructions for operating data recording equipment or
other automated test equipment, as applicable.

i\. Layouts, schematics or diagrams showing identification, location and
interconnection of test articles and measuring equipment.

j\. Identification of hazardous situations or operations.

k\. Precautions and safety instructions to ensure safety of personnel
and prevent degradation of test articles and measuring equipment.

l\. Environmental and/or other conditions to be maintained with
tolerances.

m\. Constraints on inspection or testing.

o\. Specifications for facility, equipment maintenance, housekeeping,
certification inspection and safety and handling requirements before,
during and after the total verification activity.

p\. Calibration of equipment.

4\. Format: Contractor format is acceptable.

5\. Data Type: 3

6\. Maintenance: Update as necessary to maintain currency and accuracy.

7\. Frequency of Submission: One time for each qualification test or
qualification demonstration activity. One time for each unique
acceptance test or unique acceptance demonstration activity.

8\. First Submission: Thirty (30) days prior to start of each
qualification test or qualification demonstration activity. Also thirty
(30) days prior to start of each unique acceptance test or unique
acceptance test activity.

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

## DR12 [Verification Test Reports]{.underline} {#dr12-verification-test-reports .Need-HDG-2 .unnumbered}

1\. Use: To report the results of all verification assessments and tests
on deliverable items, including flight and GSE.

2\. Scope: This DR establishes the content, format, maintenance, and
submittal requirement for the verification report. This report will
include the qualification and acceptance assessment and test for results
components, subsystems and the systems verification activities.

3\. Content: Each requirement assessed shall be correlated with the
source of the requirement (i.e., the applicable requirement
specification), have the method of assessment identified, and be
supported by technical rationale. Each test report shall adequately
summarize the verification test results and shall be prepared in a
manner that relates each reported item to each requirement. As a
minimum, the following shall be included:

> a\. Name, part number, description, vendor, identification of next
> higher hardware level, and applicable verification phase.
> Identification of test configuration and any differences from the
> flight configuration.
>
> b\. Specific results of each procedure performance.
>
> c\. Performance data, plots, pictures (as appropriate) and location of
> raw data and calibration curves for copies upon request.
>
> d\. Copies of nonconformance failure report, failure analysis,
> waivers, and deviations.
>
> e\. Conclusions and recommendations relative to success of test,
> qualification status, use in higher level of later tests,
>
> f\. Disposition of test items and conditions or status of support
> equipment as affected by the verification (test).
>
> g\. Verification (test) log.

h\. Complete "as run" test procedure.

4\. Format: Contractor format is acceptable.

5\. Data Type: 3

6\. Maintenance: Update as necessary to maintain currency and accuracy.

7\. Frequency of Submission: One qualification activity report for each
CEI or group of similar CEIs and in FCA/PCA data package. One acceptance
activity report in the FCA/PCA data package for each CEI. Update if
required.

8\. First Submission: Thirty (30) days after completion of all
qualification activities and after completion of all acceptance
activities.

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR13 Documentation, Customer Analytical Integration Capability {#dr13-documentation-customer-analytical-integration-capability .unnumbered}

1\. Use: To provide NASA the capability to continue payloads analytical
integration after contract end date.

2\. Scope: Applies to all models and tools required for executing
engineering integration.

3\. Content: This DR requires the contractor to deliver to NASA all
contractor developed models, tools and documentation associated with the
development and implementation of the engineering integration function
and the PDL. All models and tools will be appropriately documented to
provide for future application, operation, and modification. The tools
and models delivered under this DR will be those required to accomplish
the following type of activity:

> a\. Structures/dynamics/microgravity/mass properties analysis.
>
> b\. Command and Data Handling/Communications and Tracking analysis.
>
> c\. Internal/External Thermal analysis.
>
> d\. Electrical/EMI/EMC analysis.

e\. Systems Engineering analysis.

4\. Format: Contractor format is acceptable.

5\. Data Type: 3

6\. Frequency of Submission: One time at completion of contract.

7\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR14 Development Specifications {#dr14-development-specifications .unnumbered}

1\. Use: Establish the design, performance, and verification
requirements for configuration items.

2\. Scope: This DR establishes the content, format, maintenance, and
submittal requirements for contractor CI specifications.

3\. Content: These documents shall contain the design, performance, and
verification requirements for the BCS.

4\. Format: The format for these specifications shall meet SSP 41171.
Existing specifications used on the ISS Program will not require
reformatting.

5\. Data Type: 2

6\. Maintenance: These specifications shall be maintained in accordance
with SSP 41171.

7\. Frequency of Submission: Two weeks before each major design review

8\. First Submission: Avionics: Two weeks before SDR

Targets: Three days before SDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

10\. References: SSP 41171, Preparation of Program-Unique Specifications

# DR15 Materials Identification Usage Lists (MIUL) {#dr15-materials-identification-usage-lists-miul .unnumbered}

1\. Use: Provide a complete identification of all materials usages in
configuration items excluding piece-part electronics.

2\. Scope: To provide a database of materials and processes that are
used in contractor-provided BCS hardware and denote where materials and
processes that do not meet the requirements of SSP 30233 have been
approved by MUAs.

3\. Content: The content shall be in accordance with the instructions in
paragraph 3.1.3 in SSP 30233.

4\. Format: The document shall be prepared in a format compatible with
the requirements of SSP 30233.

5\. Data Type: 3

6\. Maintenance: The Contractor shall maintain such files as necessary
for tracking, reporting status, and traceability of submittals for the
as-built and delivered MIULs.

7\. Frequency of Submission: Once; update as required.

8\. First Submission: As required with ADP

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Program-authorized electronic library

10\. References: (a) SSP 30233, Space Station Requirements for Materials
and

> Processes
>
> \(b\) NASA-STD-6001, Flammability, Odor, and Offgassing Requirements
> and Test Procedures for Materials in Environments that Support
> Combustion
>
> \(c\) MSFC-HDBK- 527/MAPTIS, Materials Selection List for
>
> Space Hardware Systems

# DR16 Materials Usage Agreements (MUAs) {#dr16-materials-usage-agreements-muas .unnumbered}

1\. Use: To identify for NASA and provide rationale and approval for use
of materials and processes that are exceptions to the requirements found
in SSP 30233 that are considered acceptable for use on the BCS.

2\. Scope: The agreements provide the rationale for the use of
contractor-provided materials and processes that are exceptions to the
requirements found in SSP 30233 and that are acceptable for use on the
BCS.

3\. Content: Category I MUAs shall use the form or approved equivalent
and instructions from page B-2 of SSP 30233. The form shall be dated and
submitted to the procuring activity with the appropriate signatures
entered. Detailed treatment of the material application, photographs,
sketches, drawings, test data, and rationale for usage acceptability
shall be submitted to the extent necessary for evaluation. Summary
reports of approved Category II MUAs shall be submitted in the
Contractor\'s format providing the issue and rationale for acceptance.

4\. Format: Category I MUAs shall meet the requirements of SSP 30233.
The MUAs shall be delivered in the Contractor\'s format.

5\. Data Type: Category I: Type 1

Category II: Type 3

> 5.1 Contractor shall submit to NASA for approval Category I MUAs per
> SSP 30233 for contractor materials or processes that do not meet SSP
> 30233 requirements and are a hazard to the safety of mission, crew, or
> vehicle.
>
> 5.2 Contractor shall submit to NASA a verification package in the form
> of a Category II MUA for verification of deliverable items in
> conformance with SSP 30233.
>
> 5.3 Summaries of Category II MUAs shall be submitted and Category III
> MUAs shall be tracked using the MIUL (DR15).

6\. Maintenance: The Contractor shall maintain files necessary for
tracking, reporting status, and traceability of submittals for both
Category I and II MUAs. Updates are required when design information is
revised to reflect that as-built hardware actual usage has changed.

7\. Frequency of Submission: Per event and within 180 days of that
event: design data packages for major design reviews, update as required
to reflect as-built materials usages, and acceptance packages for DD
Form 250.

8\. First Submission: As required per #1 above and SSP 30233

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

10\. References: (a) SSP 30233, Space Station Requirements for Materials
and

> Processes
>
> \(b\) NASA-STD-6001, Flammability, Odor, and Offgassing Requirements
> and Test Procedures for Materials in Environments that Support
> Combustion
>
> \(c\) MSFC-HDBK- 527/MAPTIS, Materials Selection List for
>
> Space Hardware Systems

# DR17 Structural Loads Control Plan and Reports {#dr17-structural-loads-control-plan-and-reports .unnumbered}

1\. Use: Control the processes used in structural design loads analysis,
control, and verification.

2\. Scope: The Structural Loads Control Plan shall establish the
criteria, approach, and control plan for BCS structural design loads.
The associated reports shall document the models, forcing functions,
methodology, and analysis results for the BCS on-orbit structural loads.

3\. Content:

\(a\) The plan shall include the following:

> \(1\) Analysis approach and criteria for the development of hardware
> structural design loads for ground handling and transportation,
> testing, launch, on-orbit assembly and flights, and descent.
>
> \(2\) Approach for verification of structural design loads from low
> frequency and high frequency acceleration, applied external forces,
> and thermal environments.
>
> \(3\) Description of the procedures for implementing the design loads
> and subsequent load changes onto contractor hardware.
>
> \(4\) Definition of Contractor responsibilities in the development of
> structural design loads, including the general task descriptions,
> input, and output requirements, and the interrelationships among the
> tasks.

\(b\) The reports shall cover the following:

> \(1\) On-orbit structural design loads for all BCS hardware, including
> their load source, cycle, and capability.
>
> \(2\) Comparison of the on-orbit structural design loads with the
> analysis results of each load cycle.

\(3\) On-orbit loads resulting from each analysis cycle.

> \(4\) Description of the analysis methodology and assumptions used in
> each load cycle.
>
> \(5\) Models used for the analysis, including model checkout results
> that validate the model for use in the analysis cycle.
>
> \(6\) Integrated on-orbit math models and forcing functions in
> sufficient detail to allow for loads and dynamics computations by
> independent analysts. Upon request by NASA, models and forcing
> functions of each BCS configuration item shall be included.

4\. Format: Deliverables shall be in the Contractor\'s format.

5\. Data Type: Plan - 1, Reports - 3

6\. Maintenance: The deliverables shall be maintained electronically.

7\. Frequency of Submission: Two weeks before major design reviews

8\. First Submission: Avionics: Two weeks before SDR

Targets: Three days before SDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR18 Integrated Thermal Control Plan and Reports {#dr18-integrated-thermal-control-plan-and-reports .unnumbered}

1\. Use: (a) Provide NASA with information defining the control,
criteria, and

> analysis approach and results for ISS thermal elements integration and
> Integrated Thermal Analysis, including U.S. and International Partners
> and participants.
>
> \(b\) Provide analytical models to ensure proper structure and
> content,
>
> and to aid in the evaluation of the Contractor\'s designs.

2\. Scope: The plan shall document the criteria, approach and plan for
BCS thermal control. The reports shall provide analysis results.

3\. Content: (a) The plan shall include:

> \(1\) Criteria and analysis approach for the development of BCS
>
> induced thermal environments and integrated thermal performance
> analysis
>
> \(2\) Planning for the verification of analysis models
>
> \(3\) Test philosophy and initial test plan to support the development
> of the components, assemblies, and integrated thermal elements.
>
> \(b\) The report shall:
>
> \(1\) Describe the analysis methodology and assumptions used.
>
> \(2\) Document the thermal models used for the analysis, including
> validation results.

4\. Format: The deliverables shall be in the Contractor\'s format.

5\. Data Type: Plan - 1, Reports - 3

6\. Maintenance: The plan shall be maintained electronically.

7\. Frequency of Submission: Plan - one time, update as required

> Reports - as described in the plan

8\. First Submission: Plan - Draft three days before SDR; Final 30 days
after SDR

Reports - As described in the Plan

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR19 Support Equipment Item Description (SEID) {#dr19-support-equipment-item-description-seid .unnumbered}

1\. Use: Document support equipment characteristics in advance of
delivery to the launch processing facility.

2\. Scope: Establish characteristic documentation for support equipment
delivered by the Contractor.

3\. Content: The SEID shall contain the following for each item to be
delivered:

\(a\) Short description of the configuration item

> \(b\) Short description of general function, including purpose,
> function, unique requirements, usage location, and safety category
>
> \(c\) Identification of end-items that are common for use in
> development facilities or at the launch site.
>
> \(d\) Identification of category of availability: GFE, Modified GFE,
> Commercial, Modified Commercial, or Manufacturing (new).

4\. Format: The SEID shall be delivered in the Contractor\'s format.

5\. Data Type: 3

6\. Maintenance: The SEID shall be maintained electronically.

7\. Frequency of Submission: Draft two weeks before each major design
review, with final release 120 days prior to hardware delivery

8\. First Submission: Avionics: Two weeks before SDR

Targets: Three days before SDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR20 Specification Traceability and Compliance Reports {#dr20-specification-traceability-and-compliance-reports .unnumbered}

1\. Use: Document BCS specifications traceability from parent
requirements to the last child requirement and the associated compliance
status.

2\. Scope: The Specification Traceability and Compliance Reports
document the requirements traceability flowdown and verification closure
for

(a) CAS Specification,

```{=html}
<!-- -->
```
(a) MBS Specification,

> \(c\) Attached Payload ICD

3\. Content: (a) The Specification Compliance Report shall contain the

following for the BCS specifications:

> \(1\) Specification numbers
>
> \(2\) Specification titles
>
> \(3\) Section 3 paragraph number and title
>
> \(4\) Requirement text
>
> \(5\) Requirement identification number
>
> \(6\) Section 4 paragraph number and text
>
> \(7\) Detailed verification objective number
>
> \(8\) Verification objective text
>
> \(9\) Verification activity title
>
> \(10\) Verification report number and title
>
> \(11\) Verification closure documentation
>
> \(12\) Requirements Status.
>
> \(b\) The Specification Traceability Report shall contain the
> following for the BCS specification:

(1) Parent external requirements,

```{=html}
<!-- -->
```
(1) Requirements with no parent requirements,

(2) Flowdown from requirements external to BCS to the lowest BCS child
    requirement.

4\. Format: The Specification Traceability and Compliance Reports shall
be delivered in the Contractor\'s format.

5\. Data Type: 3

6\. Maintenance: The reports shall be maintained electronically.

7\. Frequency of Submission: Two weeks before major design reviews.

8\. First Submission: Avionics: Two weeks before SDR

Targets: Three days before SDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

# DR21 Fracture Control Plan {#dr21-fracture-control-plan .unnumbered}

1\. Use: Define and document the Contractor\'s plans for fracture
control for BCS components.

2\. Scope: The plan shall describe the fracture control approach for
contractor-provided flight hardware that prevents structural failures
during fabrication, testing, handling, transportation, and operational
life.

3\. Content: The plan shall:

> \(a\) Describe the approach and activities for fracture control of
> applicable hardware as identified in SSP 30558.
>
> \(b\) Document the Contractor\'s fracture control criteria,
> procedures, and methods for nondestructive testing and flaw growth
> calculations.

\(c\) Describe how fracture-critical parts are identified and managed.

> \(d\) Identify the timing of fracture control activities involved in
> the design, fabrication, and testing of ISS hardware.

4\. Format: The plan shall be delivered in the Contractor\'s format.

5\. Data Type: 2

6\. Maintenance: The plan shall be maintained electronically.

7\. Frequency of Submission: Update as required

8\. First Submission: Avionics: Two weeks before PDR

Targets: Three days before PDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

10\. References: SSP 30558, Fracture Control Requirements for ISS

### DR22 [BCS Launch Site Integration Plan]{.underline} {#dr22-bcs-launch-site-integration-plan .unnumbered}

1\. Use: This DR will be utilized to plan and conduct BCS launch site
integration activities.

2\. Scope: All launch site BCS integration and test activities

3\. Content: The Contractor shall provide milestones, required test
support equipment and software, test locations, test documentation,
roles and responsibilities, test configurations, and configuration
management.

4\. Format: The plan shall be delivered in the Contractor\'s format.

5\. Data Type: 2

6\. Maintenance: The plan shall be updated as required.

7\. Frequency of Submission: Two weeks before major design reviews.

8\. First Submission: Avionics: Two weeks before SDR

Targets: Three days before SDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

Program-authorized electronic library

### DR23 [Closeout Imagery Plan]{.underline} {#dr23-closeout-imagery-plan .unnumbered}

1\. Use: Closeout images will constitute a visual historical record of
delivered items and will be utilized by the sustaining engineering
organization for the purpose of problem resolution, procedure
development, familiarization and training.

2\. Scope: The plan shall demonstrate adequate coordination with the
Imagery Working Group and coverage of appropriate views of delivered
flight hardware.

3\. Format: The plan shall be delivered in the Contractor's format.

4\. Data Type: 2

5\. Maintenance: The plan shall be maintained electronically.

6\. Frequency of Submission: At CDR

7\. First Submission: CDR

8\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

### DR24 [BCS Equipment Maintenance Manual]{.underline} {#dr24-bcs-equipment-maintenance-manual .unnumbered}

1\. Use: The Equipment Maintenance Manual will be utilized by the BCS
sustaining engineering organization to plan and conduct BCS maintenance
activities.

2\. Scope: Definition of BCS maintenance for the life of the equipment.

3\. Content: The manual should include, as the BCS design dictates,
refurbishment schedules and definition of procedures for long term
storage, troubleshooting, repair, handling and transportation,
installation and calibration.

4\. Format: The manual shall be delivered in the Contractor's format.

5\. Data Type: 2

6\. Maintenance: This plan shall be maintained electronically.

7\. Frequency of Submission: Draft three days before PDR, final 2 weeks
before first AR.

8\. First Submission: Avionics: Two weeks before PDR

Targets: Three days before PDR

9\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

\(b\) Program-authorized electronic library

### DR25 [BCS Operating Manual]{.underline} {#dr25-bcs-operating-manual .unnumbered}

1\. Use: The operating manual will be used as a reference by mission
planners for the development of on-orbit procedures.

2\. Scope: The operating manual shall describe setup, operation,
troubleshooting, teardown, stowage and servicing of all IVA and EVA
ORUs.

3\. Format: The manual shall be delivered in the Contractor's format.

4\. Data Type: 2

5\. Maintenance: The manual shall be maintained electronically.

6\. Frequency of Submission:

Avionics: Two weeks before PDR

Targets: Three days before PDR

7\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Review participants

> \(b\) Program-authorized electronic library

### DR26 [Nonconformance Reports]{.underline} {#dr26-nonconformance-reports .unnumbered}

1\. Use: Provide the necessary data to ensure a closed loop system for
control of nonconformances and ensure the proper identification,
reporting, disposition, corrective action, and recurrence control of
nonconformances. Nonconformance Reports for all nonconformances
dispositioned by the Material Review Board are needed to ensure
nonconformances are controlled in a consistent manner and assure that
all necessary data elements are documented.

2\. Content: Nonconformance recording will commence with initial receipt
of materials or articles for the procurement and continue through all
subsequent phases of the program. Records will include a unique and
traceable number, nomenclature and part number, lot number, serial
number, etc. of the nonconforming article or material, description of
required characteristics or design criteria and specific definition of
the nonconformance, initiator of the report and date report generated,
next assembly identification, type of activity being conducted when
nonconformance occurred, disposition, root cause analysis, corrective
action, recurrence control (if required), names of personnel who
participated in disposition and action, final closure indication and
date.

3\. Format: Individual detailed nonconformance records in contractor
format will be available upon request. Hard copy/electronic index report
with the following minimum elements: nonconformance number; nomenclature
and part number, lot/serial number, brief description of nonconformance;
date nonconformance report initiated; status; disposition; closure date.

4\. Data Type: 3

5\. Frequency of Submission: Index report submitted monthly. Individual
detailed nonconformance reports will be available upon request. Final
index report will be submitted with Acceptance Data Package.

6\. Copies and Distribution: 1 copy of monthly report index to NASA QA
Lead or designated representative.

> Final index report will be submitted with Acceptance Data Package.

### DR27 [Problem Reporting and Corrective Action (PRACA) Reports]{.underline} {#dr27-problem-reporting-and-corrective-action-praca-reports .unnumbered}

1\. Use: The PRACA System provides for the ability to access failure
history, allow for the identification of trends and statistics, and
provide for engineering data for corrective action and design
improvement.

2\. Content: The PRACA Reports shall be inclusive of the requirements in
SSP 30223.

3\. Format: ISS PRACA System is an on-line electronic database with
established formats for reporting, recording the dispositions and
electronic signature capabilities.

4\. Data Type: 1 (As required in SSP 30223)

5\. Frequency of Submission: As required in SSP 30223

6\. NASA Approval: Yes, in accordance with SSP 30233.

7\. Copies and Distribution: No distribution required. The PRACA System
provides capability of distribution.

### DR28 [Government-Industry Data Exchange Program (GIDEP) and NASA Advisory]{.underline}  {#dr28-government-industry-data-exchange-program-gidep-and-nasa-advisory .unnumbered}

###  [Problem Data Sharing and Utilization Program Documentation and Reporting]{.underline} {#problem-data-sharing-and-utilization-program-documentation-and-reporting .unnumbered}

1\. Use: This DRD provides the minimum information to be incorporated
into the contractor's and sub tier implementation procedure and
contractual data reporting requirements to comply with the program's
requirement to participate in GIDEP and NASA Advisory Problem Data
Sharing and Utilization Program. This includes:

-   Contractor's and Sub Tier Implementation Procedures

-   Preparation and submittal of GIDEP Documents

-   Preparation and submittal of NASA Advisories

-   Task Management, Control and Tracking Status

-   Milestone/Mission Support---Assessment/Impact Status Reports

-   Cost Data on Special Problems (involving criminal investigations)

2\. Content:

-   The contractor's and sub tier Implementation Procedures shall
    provide the details that will assure that the contractor understands
    and will implement these procedures that cover the scope, importance
    of task, management's responsibilities, technical expertise to
    identify and resolve any impacts, "special problem" information
    sensitivity, and documentation necessary to comply with GIDEP and
    NASA policies.

-   GIDEP documents are to comply with the operations manual requirement
    for the appropriate document being prepared and released.

-   NASA Advisories are to comply with contents as required to complete
    the JSC Form (JF) 1159 and to accurately report the problem and
    conditions.

-   Implementation documentation shall include an index of problem
    reports received and assessed for impact,
    hardware/systems/subcontractors subjected to the assessments, status
    of the impact assessments by problem report by
    hardware/system/subcontractor, corrective actions for problems with
    identified impacts including NASA program management's involvement
    and concurrence, and the required supporting documentation for all
    problems experienced on the program/project that meet the criteria
    for the release of a GIDEP Report or NASA Advisory and the released
    GIDEP Reports and NASA Advisories. This includes any other data
    required to comply with the applicable GIDEP and NASA documents.

-   Details of the required Milestone/Mission support efforts and
    reports with the associated roles and responsibilities.

-   Financial data to justify and substantiate any reported "Cost
    Impacts."

3\. Format: Electronic submittal is the preferred media for providing
access to or submittal of information and data under this DRD.

-   The contractor's format is acceptable for their Internal
    Implementation Procedures.

-   GIDEP documents are to be prepared on appropriate GIDEP form found
    in the GIDEP Operations Manual.

-   NASA Advisories are to be prepared on the JSC Advisory Form, JF1159.

-   The contractor's format is acceptable for providing the Task
    Management, Control, and Tracking Status as long as it includes all
    of the necessary information. An electronic database with access
    permission to appropriate NASA personnel is preferred.

-   Formats for these reports are to comply with the applicable
    Milestone/Mission event effort.

-   Cost data is to be provided as required by financial management
    reporting system and to the details required to support the criminal
    investigations.

4\. Scope: Generic problems reported by the GIDEP or NASA Advisory

> distribution networks shall be assessed to determine if there is an
> impact or potential impact to the program or program assets. Generic
> problems experienced by the program or by program assets shall be
> reported in the GIDEP or NASA Advisory network, as appropriate.
> Management documentation shall be adequate to assure that the subject
> problem data are received, properly distributed, thoroughly assessed
> for potential impact, identified impact issues are resolved or
> corrected with NASA program management concurrence, cost data for
> special problem issue is to be accumulated and reported and all of
> this information is to be captured and retained in a database.

5\. Maintenance:

-   As required to document the current implementation procedures and
    GIDEP and NASA Advisory policies.

-   As required to make sure that the released information is complete,
    factual, accurate and up-to-date.

-   As required to make sure that the released information is complete,
    factual, accurate and up-to-date.

-   As required to stay current and accurate, or as requested.

-   As required to substantiate submitted costs or to include additional
    costs as they are identified.

6\. Remarks: Special controls shall be implemented to comply with the
confidentiality of the problem reports involving criminal
investigations. The implementation procedures must address this special
need for the control of information with the restricted distribution as
well as the need to track and report the cost of the problem
investigation and resolution.

7\. Data Type: 1 and 3

8\. Initial Submission:

-   Contractor's and Sub Tier Implementation Procedures: 60 days after
    contract award

-   Release of GIDEP Documents: In compliance with GIDEP

> Operation Manual and Policy

-   Release of NASA Advisories: In accordance with NASA Policy

-   Problem Data Assessments: 30 days after receipt of the Problem

> Data

-   Milestone/Mission Support: As required to support the milestone

> or mission event

-   Cost Data: As required for special problems

> involving criminal investigations

9\. Reference: SOW 12.3.12 GIDEP and NASA Advisory

Participation

SO300-BT-PRO-010 GIDEP Operations Manual

SO300-BU-GYD-010 GIDEP Requirements Guide

NPG 8735.1 Procedures for Exchanging Parts,

> Materials, and Safety Problem Data Utilizing the Government-Industry
> Data Exchange Program and NASA Advisories

10\. Frequency of Submission: As required in NPG 8735.1

11\. Copies and Distribution: As required in NPG 8735.1, and

> Program-authorized electronic library

##### DR 29 [QUALITY ASSURANCE PROGRAM PLAN]{.underline}

1\. Use: Describe implementation of the Quality Assurance requirements
by the responsible organization. The quality plan will identify all
elements of the quality assurance organization, and describe the
objectives, implementing policies and procedures, and control systems
utilized throughout design, development, procurement, fabrication, and
delivery.

2\. Content: QA Plan will include as a minimum:

-   Procurement Control

-   Configuration/Change Control

-   Fabrication Control

-   Sampling Plans and Analysis

-   Assembly Integration and Test Control

-   Metrology Control

-   Handling, Storage, Preservation, Marking, Labeling, Packaging and
    Packing

-   Nonconformance Reporting and Processing and

-   Recording and retention of quality data

3\. Format: Hardcopy or electronic in contractor's format

4\. Data Type: 2

5\. Frequency of Submission: Draft submittal at PDR. Final submittal for
NASA approval 30 days after PDR.

6\. Copies and Distribution: 1 Copy with PDR data package.

> Final submittal 30 days after PDR to NASA ISS QA Lead for NASA
> approval.

##### DR 30 [FINANCIAL MANAGEMENT REPORT (NASA FORM 533M & 533Q)]{.underline}

The NASA Form 533 (NF533) reports provide data necessary for the
following:

1\. Projecting costs and hours to ensure that dollar and labor resources
realistically support

project and program schedules.

2\. Evaluating contractor's actual cost and fee data in relation to
negotiated contract value,

estimated costs, and budget forecast data.

3\. Planning, monitoring, and controlling project and program resources.

4\. Accruing cost in NASA's accounting system, providing program and
functional management information, and resulting in liabilities
reflected on the financial statements.

Cost is a financial measurement of resources used in accomplishing a
specified purpose, such as performing a service, carrying out an
activity, acquiring an asset, or completing a unit of work or a project.
NASA Contractor Financial Management Reporting, NASA Procedures and
Guidelines (NPG) 9501.2C or its most current revision, identifies the
cost reporting requirements for a contract.

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. Examples of accrual accounting for
common cost elements reported on the NF533 follow:

######### Cost Element

Labor Reported to NASA as hours are incurred.

Equipment & Materials Generally reported to NASA when received and
accepted by the (commercial-off-the-shelf) contractor.

Manufactured Equipment Defined as any equipment that is produced to
specific requirements that make it useless to anyone else without
rework. Cost should be reported to NASA as the equipment is being
manufactured. The straight-line method for estimating accrued costs or
the use of supplemental information obtained from the vendor are
acceptable methods used to calculate the cost accrual amount.

Leases Reported to NASA using a proration over the life of the lease.

Travel Reported to NASA as costs are incurred.

Subcontracts Actual and estimated costs reported by prime contractor
shall include subcontractors' incurred costs for the same accounting
period. Where subcontract costs are material, they should be separately
identified on NF533 reports. The prime contractor shall include in the
total cost of each subdivision of work the accrued cost (including fee,
if any) of related subcontractor effort. Subcontractors should,
therefore, be required to report cost to the prime contractor, using the
accrual method of accounting. If the G&A and fee reported by a
subcontractor are at the total subcontractor level, these costs must be
allocated to specific subdivisions of work. Data submitted by the
subcontractor should be structured similar to the prime contractor's
NF533 to enable the prime contractor to properly report to NASA. For
Firm-Fixed Price subcontracts with a contract value greater than
\$500,000, the prime contractor is required to document the methodology
used to generate the subcontractor costs reported and provide this
information to the Contracting Officer and Center Deputy Chief Financial
Officer (Finance).

Unfilled Orders Reported as the difference between the cumulative cost
incurred to date and the amounts obligated to suppliers and
subcontractors.

Fee Should be accrued as earned using a consistent and auditable method
to determine the amount. For example: an acceptable method would be to
use historical data to determine the amount to accrue each month. Fee
should be reported on the NF533 following the "Total Cost" line. Award
fee must be reported by the follow categories: Base Fee, Fee Earned,
Interim Fee, Provisional Fee, Potential Additional Fee, and Total Fee.
If any of the above fee categories does not pertain, they should not be
included in the NF533.

Prompt Payment Discounts Cumulative cost reported to NASA should be the
total incurred cost. The prompt payment discount amount taken should be
reported as a separate line item on the NF533 below the cumulative cost
amounts for the contract.

The NF533 reports are the official cost documents used at NASA for
cost-type, price redetermination, and fixed price incentive contracts.
The data contained in the reports must be auditable using Generally
Accepted Accounting Principles. Supplemental cost reports submitted in
addition to the NF533 must be reconcilable to the NF533.

The due dates for the NF533M and NF533Q reports are outlined on page 3-2
of the NPG 9501.2C. The following is a summary of the NF533 due date
requirements.

**[NF533 Report]{.underline} [Due Date]{.underline}**

NF533M Due not later than 10 working days following the close of the
contractor's

> monthly accounting period.

NF533Q Due not later than the 15^th^ day of the month preceding the
quarter being reported.

The due dates reflect the date the NF533 reports are received by
personnel on the distribution list, not the date the reports are
generated or mailed by the contractor. It is critical that the NF533
reports are submitted in a timely manner to ensure adequate time for
NASA to analyze and record the cost into the NASA accounting system.

Uncompensated overtime hours worked should be reported on NF533 reports
as a separate line item or in the footnotes.

For contracts which have multiple schedules, a summary NF533 is required
to provide a cumulative-from-inception cost for the contract, regardless
of schedule.

An 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 30 days after the incurrence of cost.

Column 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 columns 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 cost adjustments should be reported in columns 7a and 7c of
the NF533M and column 7a of the NF533Q with a footnote discussing the
reasons for and amounts of the adjustments.

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 contractor 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" contractor cost report, the contractor must submit a
revised NF533 report in the month the cost change is recognized.

Distribution (1 copy each): BG/Contracting Officer

LF6/Cost Accounting

> LO/Budget Analyst

OM/COTR

##### DR 31 [QUALIFICATION AND ACCEPTANCE TEST PLAN]{.underline}

1\. Use: To establish a test program for BCS development and
verification

2\. Content: Describes overall test philosophy, objectives and rationale
for the test. The plan shall contain as a minimum:

> 1\) A test matrix cross-referenced to the design and performance
> requirements listed in the verification matrix
>
> 2\) Test purpose and objectives
>
> 3\) Test methods including test facility, test support equipment
> (including instrumentation and data collection systems), assumptions,
> and constraints
>
> 4\) Test schedule

3\. Format: This DR may be delivered in Contractor\'s format.

4\. Data Type: 2

5\. Frequency of Submission: One time submission per test

6\. First Submission Date: 90 days after CDR

7\. Copies and Distribution: 1 copy distributed to each of the
following:

\(a\) Program repository

\(b\) Program-authorized electronic library

8\. Reference: SSP 41172, Qualification and Acceptance Environmental
Test Requirements