<table style="width:100%;">
<colgroup>
<col style="width: 12%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 7%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 5%" />
<col style="width: 9%" />
<col style="width: 7%" />
<col style="width: 1%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 4%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3">National Aeronautics and<br />
Space Administration</td>
<td colspan="17"><blockquote>
<p><strong>Contract</strong></p>
</blockquote></td>
</tr>
<tr class="even">
<td colspan="4">1. DPAS</td>
<td colspan="5">2. PPC</td>
<td colspan="5">3. INITIATING OFFICE</td>
<td colspan="6">4. PAGE</td>
</tr>
<tr class="odd">
<td colspan="4">DO-C9</td>
<td colspan="5">DL</td>
<td colspan="5">OM/Program Integration Office</td>
<td colspan="4">1 OF</td>
<td>37</td>
<td></td>
</tr>
<tr class="even">
<td colspan="5">5. CONTRACT NUMBER</td>
<td colspan="4">6. EFFECTIVE DATE</td>
<td colspan="5">7. PROCUREMENT REQUEST NUMBER</td>
<td colspan="6">8. VENDOR CODE</td>
</tr>
<tr class="odd">
<td colspan="5">NAS 9-01060</td>
<td colspan="4">See Block 17b</td>
<td colspan="5">01080OA1</td>
<td colspan="6"></td>
</tr>
<tr class="even">
<td colspan="6">9. ISSUED BY:</td>
<td>CODE</td>
<td colspan="2">BG</td>
<td colspan="5">10. ADMINISTERED BY:</td>
<td colspan="3">CODE</td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="9">National Aeronautics and Space Administration</td>
<td colspan="11"></td>
</tr>
<tr class="even">
<td colspan="9"><p>Johnson Space Center</p>
<p>Attn: BG/Julia Trautman</p>
<p>2101 NASA Rd 1</p>
<p>Houston, TX 77058</p></td>
<td colspan="11"></td>
</tr>
<tr class="odd">
<td colspan="9"></td>
<td colspan="2">Administrator:</td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td colspan="6">11. PAYMENT WILL BE MADE BY:</td>
<td>CODE</td>
<td colspan="2">LF231</td>
<td colspan="5">12. SUBMIT INVOICES TO:</td>
<td colspan="2">CODE</td>
<td colspan="4">BG</td>
</tr>
<tr class="odd">
<td colspan="9"><p>NASA Johnson Space Center</p>
<p>LF231/Funding and Commercial Accounts</p>
<p>Houston, TX 77058</p></td>
<td colspan="11"><p>NASA Johnson Space Center</p>
<p>Attn: BG/Contracting Officer</p>
<p>Houston, TX 77058</p></td>
</tr>
<tr class="even">
<td colspan="20">13. ACCOUNTING AND APPROPRIATION DATA</td>
</tr>
<tr class="odd">
<td colspan="20">477-70-10-13-6A-OA-2513-OA11</td>
</tr>
<tr class="even">
<td colspan="9">14. CONTRACT TYPE</td>
<td colspan="11">15. INCREMENTAL FUNDING</td>
</tr>
<tr class="odd">
<td colspan="9">Firm Fixed Price - Labor-hour</td>
<td colspan="11">Yes</td>
</tr>
<tr class="even">
<td></td>
<td colspan="7">SECTION DESCRIPTION</td>
<td colspan="2">PAGE</td>
<td colspan="5">SECTION DESCRIPTION</td>
<td colspan="5">PAGE</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="7">CONTRACT COVER PAGE</td>
<td colspan="2">1</td>
<td colspan="5">REPORTS OF WORK</td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td><strong>TABLE OF</strong></td>
<td colspan="7">FULL TEXT CLAUSES</td>
<td colspan="2"></td>
<td colspan="5">ACCEPTANCE DATA PACKAGE</td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td><strong>CONTENTS</strong></td>
<td colspan="7">CLAUSES INCORPORATED BY REFERENCE</td>
<td colspan="2"></td>
<td colspan="5">STATEMENT OF WORK</td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="7">QUALITY AND RELIABILITY REQUIREMENTS</td>
<td colspan="2"></td>
<td colspan="5"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="7"></td>
<td colspan="2"></td>
<td colspan="5"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="20">16. ITEMS AWARDED UNDER THIS CONTRACT</td>
</tr>
<tr class="odd">
<td colspan="20">Provide Mobile Servicing System (MSS) Instrumentation,
Program, and Command List (IP&amp;CL) Standard-Input data, integration
of MSS software models into NASA simulators, MSS integrated test
support, MSS flight operations support deliverables, and special MSS
robotics studies.</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="18">17. NAME OF CONTRACTING OFFICER</td>
</tr>
<tr class="odd">
<td colspan="2"><p>UNITED</p>
<p>STATES OF</p></td>
<td colspan="18">N.L. Dawn Alexander</td>
</tr>
<tr class="even">
<td colspan="2">AMERICA</td>
<td colspan="11">17a. SIGNATURE</td>
<td colspan="7">17b. DATE</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="11"></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="20"></td>
</tr>
<tr class="odd">
<td colspan="20"><strong>CONTRACTOR - COMPLETE ALL ITEMS
BELOW</strong></td>
</tr>
<tr class="even">
<td colspan="8">CONTRACTOR NAME AND ADDRESS</td>
<td colspan="4">DISCOUNT TERMS</td>
<td colspan="8">TOTAL AMOUNT OF CONTRACT</td>
</tr>
<tr class="odd">
<td colspan="8">MacDonald Dettwiler Space Robotics Corporation</td>
<td colspan="4"></td>
<td colspan="8"></td>
</tr>
<tr class="even">
<td colspan="8">1300 Hercules Drive, Suite 210</td>
<td colspan="12">NAME AND TITLE OF SIGNER <em>(Type or print)</em></td>
</tr>
<tr class="odd">
<td colspan="8">Houston, TX 77058</td>
<td colspan="12">Paula Irwin, Contracts Manager</td>
</tr>
<tr class="even">
<td colspan="8">CONTRACT ADMINISTRATOR <em>(Name and telephone
number)</em></td>
<td colspan="6">SIGNATURE <em>(Of person authorized to sign)</em></td>
<td colspan="6">DATE</td>
</tr>
<tr class="odd">
<td colspan="8">Paula Irwin 905-790-4457</td>
<td colspan="6"></td>
<td colspan="6"></td>
</tr>
<tr class="even">
<td colspan="20"></td>
</tr>
</tbody>
</table>

NASA Form 1668 (Rev Dec 97) Previous Edition is Obsolete. (MS Word Jan
98)

**1. [CONSIDERATION AND PAYMENT]{.underline}**

**A.** Payment for services to be furnished shall be made in accordance
with the Federal Acquisition Regulation (FAR) clause 52.232-7, "Payments
Under Time-and Materials and Labor-Hour Contracts."

**B.** The hourly rate described in paragraph (a) of FAR Clause 52.232-7
shall be:

\(1\) For the five-month period (08/01/01 through 12/31/01)

[Labor Category]{.underline} [Rate]{.underline}

\_\_[H1 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$91.20
US\_\_]{.underline}

\_\_[H2 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$66.69
US]{.underline}\_\_

\_\_[H3 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$41.88
US]{.underline}\_\_

\_\_[J1 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$88.37
US]{.underline}\_\_

\_\_[J2 Engineer]{.underline}\_\_\_\_ \_\_\_\_\_\_ \_\_[\$64.24
US]{.underline}\_\_

\_\_[J3 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$48.61
US]{.underline}\_\_

\(2\) For the twelve-month period (01/01/02 through 12/31/02)

Labor Category Rate

\_\_[H1 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$93.93
US\_\_]{.underline}

\_\_[H2 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$68.69
US]{.underline}\_\_

\_\_[H3 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$43.13
US]{.underline}\_\_

\_\_[J1 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$91.02
US]{.underline}\_\_

\_\_[J2 Engineer]{.underline}\_\_\_\_ \_\_\_\_\_\_ \_\_[\$66.17
US]{.underline}\_\_

\_\_[J3 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$50.07
US]{.underline}\_\_

\(3\) For the twelve-month period (01/01/03 through 12/31/03)

Labor Category Rate

\_\_[H1 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$96.66
US\_\_]{.underline}

\_\_[H2 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$70.68
US]{.underline}\_\_

\_\_[H3 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$44.38
US]{.underline}\_\_

\_\_[J1 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$93.66
US]{.underline}\_\_

\_\_[J2 Engineer]{.underline}\_\_\_\_ \_\_\_\_\_\_ \_\_[\$68.09
US]{.underline}\_\_

\_\_[J3 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$51.52
US]{.underline}\_\_

\(4\) For the twelve-month period (01/01/04 through 12/31/04)

Labor Category Rate

\_\_[H1 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$99.56
US\_\_]{.underline}

\_\_[H2 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$72.80
US]{.underline}\_\_

\_\_[H3 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$45.71
US]{.underline}\_\_

\_\_[J1 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$96.38
US]{.underline}\_\_

\_\_[J2 Engineer]{.underline}\_\_\_\_ \_\_\_\_\_\_ \_\_[\$70.06
US]{.underline}\_\_

\_\_[J3 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$53.01
US]{.underline}\_\_

\(5\) For the seven-month period (01/01/05 through 07/31/05)

Labor Category Rate

\_\_[H1 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$102.64
US\_\_]{.underline}

\_\_[H2 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$ 75.06
US]{.underline}\_\_

\_\_[H3 Engineer]{.underline}\_\_\_\_\_\_\_\_\_\_ \_\_[\$ 47.13
US]{.underline}\_\_

\_\_[J1 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$ 98.31
US]{.underline}\_\_

\_\_[J2 Engineer]{.underline}\_\_\_\_ \_\_\_\_\_\_ \_\_[\$ 71.46
US]{.underline}\_\_

\_\_[J3 Engineer]{.underline} \_\_\_\_\_\_\_\_\_ \_\_[\$ 54.08
US]{.underline}\_\_

**C.** Travel, as directed by the Government, will be a direct cost to
the contract based on actual airfare and per diem rates per the most
current Official CONUS Per Diem Rates, located at
<http://www.dtic.mil/perdiem/pdrform.html>[.]{.underline}

A not-to-exceed amount of **[\$2,740.00 US]{.underline}** is allocated
for travel under this contract.

Invoices may be submitted upon completion of individual trips and shall
be prepared and submitted in accordance with paragraph 3, Submission of
Invoices. The invoices shall include copies of receipts for airfare,
lodging, car rental, and other expenses as required by the company
policy.

All trips will be limited as follows:

1.  Maximum allowable costs for lodging, meals and incidental expenses
    are limited to current

Government-established per diem rates.

2.  Maximum allowable cost for use of privately owned vehicles shall be
    restricted to the Federal

Travel Regulations.

3.  Allowable air travel expenses are limited to standard coach fare,
    whenever it does not conflict

with the ultimate purpose of the travel, and as much advance notice as
possible.

4.  Allowable automobile rental cost is limited to compact cars.

Per diem paid on travel days is ¾ per diem. The time actually spent in
travel is not considered.

**D.** The minimum value of services ordered and paid for under this
contract shall be \$100,000.

The Government is only obligated to order the minimum value under this
contract for the

basic period awarded.

**E.** The ceiling price of this contract is **[\$2,800,000
US]{.underline}**.

**F.** This is a firm fixed price - labor hour contract. The total value
of this contract shall be the total of the issued task orders.

**G. LIMITATION OF FUNDS (FIXED-PRICE CONTRACT) (NFS 1852.232-77)
(MARCH**

**1989)**

\(a\) The total funding amount that is presently available for payment
under this contract is **reflected**

**on the most recent task order**.

\(b\) The Contractor agrees to perform or have performed work on the
items specified in paragraph (a) of this clause up to the point at
which, if this contract is terminated pursuant to the Termination for
Convenience of the Government clause of this contract, the total amount
payable by the Government (including amounts payable for subcontracts
and settlement costs) pursuant to paragraphs (f) and (g) of that clause
would, in the exercise of reasonable judgment by the Contractor,
approximate the total amount at the time allotted to the contract. The
Contractor is not obligated to continue performance of the work beyond
that point. The Government is not obligated in any event to pay or
reimburse the Contractor more than the amount from time to time allotted
to the contract, anything to the contrary in the Termination for
Convenience of the Government clause notwithstanding.

\(c\) (1) It is contemplated that funds presently allotted to this
contract will cover the work to be performed through the period of
performance on the latest authorized **Task Order**.

\(2\) If funds allotted are considered by the Contractor to be
inadequate to cover the work to be performed until that date, or an
agreed date substituted for it, the Contractor shall notify the
Contracting Officer in writing when within the next 60 days the work
will reach a point at which, if the contract is terminated pursuant to
the Termination for Convenience of the Government clause of this
contract, the total amount payable by the Government (including amounts
payable for subcontracts and settlement costs) pursuant to paragraphs
(f) and (g) of that clause will approximate 75 percent of the total
amount then allotted to the contract.

\(3\) (i) The notice shall state the estimate when the point referred to
in paragraph (c)(2) of this clause will be reached and the estimated
amount of additional funds required to continue performance to the date
specified in paragraph (c)(1) of this clause, or an agreed date
substituted for it.

\(ii\) The Contractor shall, **30 days** in advance of the date
specified in paragraph (c)(1) of this clause, or an agreed date
substituted for it, advise the Contracting Officer in writing as to the
estimated amount of additional funds required for the timely performance
of the contract for a further period as may be specified in the contract
or otherwise agreed to by the parties.

\(4\) If, after the notification referred to in paragraph (c)(3)(ii) of
this clause, additional funds are not allotted by the date specified in
paragraph (c)(1) of this clause, or an agreed date substituted for it,
the Contracting Officer shall, upon the Contractor\'s written request,
terminate this contract on that date or on the date set forth in the
request, whichever is later, pursuant to the Termination for Convenience
of the Government clause.

\(d\) When additional funds are allotted from time to time for continued
performance of the work under this contract, the parties shall agree on
the applicable period of contract performance to be covered by these
funds. The provisions of paragraphs (b) and (c) of this clause shall
apply to these additional allotted funds and the substituted date
pertaining to them, and the contract shall be modified accordingly.

\(e\) If, solely by reason of the Government\'s failure to allot
additional funds in amounts sufficient for the timely performance of
this contract, the Contractor incurs additional costs or is delayed in
the performance of the work under this contract, and if additional funds
are allotted, an equitable adjustment shall be made in the price or
prices (including appropriate target, billing, and ceiling prices where
applicable) of the items to be delivered, or in the time of delivery, or
both.

\(f\) The Government may at any time before termination, and, with the
consent of the Contractor, after notice of termination, allot additional
funds for this contract.

\(g\) The provisions of this clause with respect to termination shall in
no way be deemed to limit the rights of the Government under the default
clause of this contract. The provisions of this Limitation of Funds
clause are limited to the work on and allotment of funds for the items
set forth in paragraph (a) of this clause. This clause shall become
inoperative upon the allotment of funds for the total price of said work
except for rights and obligations then existing under this clause.

\(h\) Nothing in this clause shall affect the right of the Government to
terminate this contract pursuant to the Termination for Convenience of
the Government clause of this contract.

(End of clause)

**2.** **[PERIOD OF PERFORMANCE]{.underline}**

The period of performance of this contract shall not exceed **July 31,
2005,** but is based on the date set by the **most recent task order**.

**3. [SUBMISSION OF INVOICES (JSC 52.232-90) (OCT 1993)]{.underline}**

Invoices shall be prepared and submitted in quadruplicate. Invoices
shall contain the following information as applicable: contract and
order number, description of services, hours, labor rates, and extended
totals. If travel costs are being invoiced, travel receipts shall be
submitted. Invoices shall be submitted to:

NASA Lyndon B. Johnson Space Center

Attn: BG/Contracting Officer

2101 NASA Road 1

Houston, TX 77058

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

**4.** **[PLACE OF PERFORMANCE]{.underline}**

The contractor shall perform the work under this contract at the Johnson
Space Center in Houston, TX, at the MDR facility in Brampton, Ontario,
Canada, and on travel to required destinations.

**5**. **[IDENTIFICATION OF EMPLOYEES (JSC 52.242-92)(MAY
1993)]{.underline}**

At all times while on Government property, the contractor,
subcontractors, their employees and agents shall wear badges which will
be issued by the NASA Contract and Pass Office, located in building No.
110. Badges will be issued only between the hours of 7:00 a.m. and 4:00
p.m., Monday through Friday. Each individual who wears a badge will be
required to sign personally for the badge. The contractor will be held
accountable for these badges, and immediately after completion of the
work, they shall be returned to the NASA Contract Badge and Pass Office.
Failure to turn in badges upon completion of work may result in final
payment being delayed.

**6. [(LIMITED) RELEASE OF CONTRACTOR CONFIDENTIAL BUSINESS INFORMATION
(CBI) (JSC 52.227-91) (FEB 2001) ]{.underline}**

\(a\) NASA may find it necessary to release information submitted by the
Contractor, either in response to this solicitation or pursuant to the
provisions of this contract, to individuals not employed by NASA.
Business information that would ordinarily be entitled to confidential
treatment may be included in the information released to these
individuals. Accordingly, by submission of this proposal, or signature
on this contract or other contracts, the Contractor hereby consents to a
limited release of its confidential business information (CBI).

\(b\) Possible circumstances where the Agency may release the
Contractor\'s CBI include, but are not limited to, the following:

\(1\) To other Agency contractors and subcontractors, and their
employees tasked with assisting the Agency in handling and processing
information and documents in the evaluation, the award or the
administration of Agency contracts, such as providing both pre-award and
post award audit support and specialized technical support to NASA\'s
technical evaluation panels;

\(2\) To NASA contractors and subcontractors, and their employees
engaged in information systems analysis, development, operation, and
maintenance, including performing data processing and management
functions for the Agency.

\(c\) NASA recognizes its obligation to protect the contractor from
competitive harm that could result from the release of such information
to a competitor. Except where otherwise provided by law, NASA will
permit the limited release of CBI under subparagraphs (1) or (2) only
pursuant to non-disclosure agreements signed by the assisting contractor
or subcontractor, and their individual employees who may require access
to the CBI to perform the assisting contract).

\(d\) NASA\'s responsibilities under the Freedom of Information Act are
not affected by this clause.

\(e\) The Contractor agrees to include this clause, including this
paragraph (e), in all subcontracts at all levels awarded pursuant to
this contract that require the furnishing of confidential business
information by the subcontractor.

(End of clause)

**7. [SECURITY/BADGING REQUIREMENTS FOR FOREIGN NATIONAL VISITORS AND
EMPLOYEES OF FOREIGN CONTRACTORS (JSC 52.204-91) (AUG 1999)
]{.underline}**

\(a\) An employee of a domestic Johnson Space Center (JSC) contractor or
its subcontractor who is not a U.S. citizen and does not have lawful
permanent resident status (no resident alien \"green\" card) may not be
admitted to the JSC site for purposes of performing work without special
arrangements. In addition, all employees of a foreign JSC contractor or
its subcontractors may not be admitted to the JSC site without special
arrangements. For employees as described above, advance notice must be
given to the JSC Security Office at least 3 weeks prior to the scheduled
need for access to the JSC site so that instructions on obtaining access
may be provided.

\(b\) The contractor\'s signature on all JSC badge request forms (i.e.,
JSC Forms 473A and 473B, as applicable), is certification that steps are
being taken to ensure that its contractor or subcontractor employees
will not be given access to export- controlled or classified information
for which they are not authorized. The contractor must designate at
least one individual and one alternate who have received training in
applicable security and export control matters. These individuals shall
serve as the contractor\'s representative(s) in certifying all JSC badge
request forms during normal duty hours in accordance with JSC security
and export control procedures. The names, telephone numbers, e-mail
addresses, and office addresses of these individuals shall be provided
to the contracting officer. Any changes in this information shall be
promptly forwarded to the contracting officer.

\(c\) The contractor agrees that it will not employ for the performance
of work onsite at the JSC any individuals who are not legally authorized
to work in the United States. If JSC Industrial Security Specialist or
the contracting officer has reason to believe that any employee of the
contractor may not be legally authorized to work in the United States,
the contractor may be required to furnish copies of Form I-9 (Employment
Eligibility Verification), U.S. Department of Labor Application for
Alien Employment Certification, and any other type of employment
authorization document.

\(d\) The contractor agrees to provide the information requested by the
JSC Security Office in order to comply with NASA policy directives and
guidelines related to foreign visits to NASA facilities so that (1) the
employee may be allowed access to JSC or other NASA Centers for
performance of this contract, (2) required investigations can be
conducted, and (3) for annual or revalidation reports required by NASA
Headquarters. All requested information must be submitted in a timely
manner in accordance with instructions provided by JSC or any other
Center to be visited.

(End of clause)

**8. [TASK ORDERING PROCEDURE (NFS 1852.216-80) (OCT
1996)]{.underline}**

\(a\) Only the Contracting Officer may issue task orders to the
Contractor, providing specific authorization or direction to perform
work within the scope of the contract and as specified in the schedule.
The Contractor may incur costs under this contract in performance of
task orders and task order modifications issued in accordance with this
clause. No other costs are authorized unless otherwise specified in the
contract or expressly authorized by the Contracting Officer.

\(b\) Prior to issuing a task order, the Contracting Officer shall
provide the Contractor with the following data:

\(1\) A functional description of the work identifying the objectives or
results desired from the contemplated task order.

\(2\) Proposed performance standards to be used as criteria for
determining whether the work requirements have been met.

\(3\) A request for a task plan from the Contractor to include the
technical approach, period of performance, appropriate cost information,
and any other information required to determine the reasonableness of
the Contractor\'s proposal.

\(c\) Within **[10]{.underline}** *working* days after receipt of the
Contracting Officer\'s request, the Contractor shall submit a task plan
conforming to the request.

\(d\) After review and any necessary discussions, the Contracting
Officer may issue a task order to the Contractor containing, as a
minimum, the following:

\(1\) Date of the order.

\(2\) Contract number and order number.

\(3\) Functional description of the work identifying the objectives or
results desired from the task order, including special instructions or
other information necessary for performance of the task.

\(4\) Performance standards, and where appropriate, quality assurance
standards.

\(5\) Maximum dollar amount authorized (cost and fee or price). This
includes allocation of award fee among award fee periods, if applicable.

\(6\) Any other resources (travel, materials, equipment, facilities,
etc.) authorized.

\(7\) Delivery/performance schedule including start and end dates.

\(8\) If contract funding is by individual task order, accounting and
appropriation data.

\(e\) The Contractor shall provide acknowledgment of receipt to the
Contracting Officer within **[5]{.underline}** *working* days after
receipt of the task order.

\(f\) If time constraints do not permit issuance of a fully defined task
order in accordance with the procedures described in paragraphs (a)
through (d), a task order which includes a ceiling price may be issued.

\(g\) The Contracting Officer may amend tasks in the same manner in
which they were issued.

\(h\) In the event of a conflict between the requirements of the task
order and the Contractor\'s approved task plan, the task order shall
prevail.

(End of clause)

**ALTERNATE I**

**(October 1996)**

\(i\) Contractor shall submit monthly task order progress reports. As a
minimum, the

reports shall contain the following information:

\(1\) Contract number, task order number, and date of the order.

\(2\) Task ceiling price.

\(3\) Cost and hours incurred to date for each issued task.

\(4\) Costs and hours estimated to complete each issued task.

\(5\) Significant issues/problems associated with a task.

\(6\) Cost summary of the status of all tasks issued under the contract.

**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 the/these
address(es):

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

b.  For all NASA FAR clauses --
    <http://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 11)
CLAUSES]{.underline}**

52.202-1 Definitions (May 2001)

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-15 Defense Priority and Allocation Requirement (Sept 1990)

52.215-2 Audit - Negotiation (Jun 1999)

52.215-10 Price Reduction for Defective Cost or Pricing Data (Oct 1997)

52.215-12 Subcontractor Cost or Pricing Data (Oct 1997)

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

52.215-17 Waiver of Facilities Capital Cost of Money (Oct 1997)

52.215-18 Reversion or Adjustment of Plans for Post Retirement Benefits
Other Than

> Pensions (Oct 1997)

52.215-19 Notification of Ownership Changes (Oct 1997)

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

Pricing Data-Modification (Oct 1997)

52.217-8 Option to Extend Services (Nov 1999) \[Insert "30 days"\]

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

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

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

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

52.222-3 Convict Labor (Aug 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-5 Pollution Prevention and Rights-to-Know Information (Apr 1998)

52.223-6 Drug-Free Workplace (May 2001)

52.223-10 Waste Reduction Program (Aug 2000)

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

52.227-1 Authorization and Consent (Jul 1995)

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

1852.227-14

52.227-16 Additional Data Requirements (June 1987)

52.229-4 Federal, State and Local Taxes (Noncompetitive Contract) (Jan
1991)

52.229-5 Taxes-Contracts Performed in U.S. Possessions and Puerto Rico
(Apr 1984)

52.232-7 Payments under Time --and-Materials and Labor Hour Contracts
(Mar 2000) -- Alternate II (Jan 1986)

52.232-8 Discounts for Prompt Payment (May 1997)

52.232-17 Interest (Jun 1996)

52.232-23 Assignment of Claims (Jan 1986)

52.232-25 Prompt Payment (May 2001) \[Insert 30^th^ day in subparagraph
(b)(1)\]

52.232-34 Payment by Electronic Funds Transfer-Other Than Central
Contractor Transfer (May 1999)

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

52.233-3 Protest after Award (Aug 1996)

52.237-2 Protection of Government Buildings, Equipment and Vegetation
(Apr 1984)

52.242-13 Bankruptcy (Jul 1995)

52.242-15 Stop-Work Order (Aug 1989)

52.243-3 Changes\--Time-and-Materials or Labor-Hours (Sept 2000)

52.244-2 Subcontracts (Aug 1998)

52.244-6 Subcontracts for Commercial Items (May 2001)

52.246-6 Inspection\--Time-and-Material and Labor-Hour (May 2001)

52.246-25 Limitation of Liability-Services (Feb 1997)

52.247-34 F.o.b. Destination (Nov 1991)

52.248-1 Value Engineering (Feb 2000)

52.249-2 Termination for Convenience of the Government (Fixed-Price)
(Sep 1996)

52.249-8 Default (Fixed-Price Supply and Service) (Apr 1984)

52.249-14 Excusable Delays (Apr 1984)

52.253-1 Computer Generated Forms (Jan 1991)

**B. [NASA/FAR SUPPLEMENT (48 CFR CHAPTER 18) CLAUSES]{.underline}**

1852.204-74 Central Contractor Registration (AUG 2000)

1852.204-76 Security Requirements for Unclassified Information
Technology Resources

> (Jul 2001)

1852.215-84 Ombudsman (Jun 2000) (Insert \"Debra L. Johnson at (281)
483-4157\" and "Before consulting with any ombudsman, interested parties
must try to resolve their concerns with the contract specialist or the
contracting officer.\")

1852.219-75 Small Business Subcontracting Reporting (May 1999)

1852.219-76 NASA 8 Percent Goal (Jul 1997)

1852.223-70 Safety and Health (May 2001)

1852.223-75 Major Breach of Safety or Security (May 2001)

1852.227-70 New Technology (November 1998)

1852.227-72 Designation Of New Technology Representative and Patent
Representative

(July 1997) (Insert "HA" and "NASA -- Johnson Space Center, 2101 NASA Rd
1,

Houston, TX 77058" for both the New Technology Representative and Patent

Representative.)

1852.228-75 Minimum Insurance Coverage (Oct 1988)

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

1852.237-70 Emergency Evacuation Procedures (Dec 1988)

1852.242-70 Technical Direction (Sep 1993) Replace reference to Section
C with "Statement

> of Work" in paragraph (a).

1852.242-72 Observance of Legal Holidays (Aug 1992)

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

1852.243-71 Shared Savings (March 1997)

1852.245 -71 Installation-Accountable Government Property (June 1998)

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

**[OFFERORS (JSC 52.209-90) (SEP 1988) -- As Amended]{.underline}**

This contract incorporates the Representations, Certifications, and
Other Statements of Offerors, as set forth in the contractor's proposal
dated **June 29, 2001** by reference, with the same force and effect as
if it were given in full text.

**11. [LIST OF INSTALLATION-ACCOUNTABLE PROPERTY AND SERVICES (NFS
1852.245-77)(JULY 1997)]{.underline}**

In accordance with the clause at 1852.245-71, Installation-Accountable
Government Property, the Contractor is authorized use of the types of
property and services listed below, to the extent they are available, in
the performance of this contract within the physical borders of the
installation which may include buildings and space owned or directly
leased by NASA in close proximity to the installation, if so designated
by the Contracting Officer.

\(a\) Office space, work area space, and utilities. Government
telephones are available for official purposes only; pay telephones are
available for contractor employees for unofficial calls.

\(b\) General- and special-purpose equipment, including office
furniture.

\(1\) Equipment to be made available is listed in Attachment 1*.* The
Government retains accountability for this property under the clause at
1852.245-71, Installation-Accountable Government Property, regardless of
its authorized location.

\(2\) If the Contractor acquires property, title to which vests in the
Government pursuant to other provisions of this contract, this property
also shall become accountable to the Government upon its entry into
Government records as required by the clause at 1852.245-71,
Installation-Accountable Government Property.

\(3\) The Contractor shall not bring to the installation for use under
this contract any property owned or leased by the Contractor, or other
property that the Contractor is accountable for under any other
Government contract, without the Contracting Officer\'s prior written
approval.

\(c\) Supplies from stores stock.

\(d\) Publications and blank forms stocked by the installation.

\(e\) Safety and fire protection for Contractor personnel and
facilities.

\(f\) Installation service facilities: Those provided within the office
such as electricity, water, heat etc.

\(g\) Medical treatment of a first-aid nature for Contractor personnel
injuries or illnesses sustained during on-site duty.

\(h\) Cafeteria privileges for Contractor employees during normal
operating hours.

\(i\) Building maintenance for facilities occupied by Contractor
personnel.

\(j\) Moving and hauling for office moves, movement of large equipment,
and delivery of supplies. Moving services shall be provided on-site, as
approved by the Contracting Officer.

\(k\) The user responsibilities of the Contractor are defined in
paragraph (a) of the clause at 1852.245-71, Installation-Accountable
Government Property.

(End of clause)

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

AVU Artificial Vision Unit

BDEALS Bilateral Data Exchange Agreements Lists

CCS Command and Control System

CEU Control Electronic Unit

CSA Canadian Space Agency

GUI PCS Graphical User Interface

IP&CL Instrumentation, Program & Command List

ISDT Integration Signal Data Team

ISS International Space Station

JCS Joint Control System

LCS LEE Control System

LEE Latching End Effector

MBF Mission Build Facility

MBS Mobile Base System

MEIT Multiple Element Integrated Test

MSS Mobile Servicing System

OCS Operations Control Software

PCS Portable Computer System

PIRN Preliminary/Proposed Interface Revision Notice

PUI Program Unique Identifier

RFOP Robotics Flight Operations Preparation

RPUI Requirements Program Unique Identifiers

RSSM Robotics Simulator Software Model

RWS Robotic Workstation

SACS SSRMS Arm Control Software

SES Shuttle Engineering Simulator

SGI Silicon Graphics SlmXX

SPDM Special Purpose Dexterous Manipulator

SSPS Software Standards and Procedures Specification

SSRMS Space Station Remote Manipulator System

SSTF Space Station Training Facility

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

The contractor shall provide deliverables and specified support for the
following tasks:

1\. Production of Space Station Instrumentation, Program, and Command
List (IP&CL) flight

data,

2\. Programming and engineering analysis support for insertion of
specific Space Station robotic

models into NASA simulator software,

3\. Planning, test support, and problem resolution of Space Station
robotics flight software

integrated tests and verification,

4\. Production of deliverables associated with Space Station robotics
flight operations, and

5\. Provision of engineering robotics expertise and ad hoc deliverables
specified by the contract

technical monitor within the constraints of specified level-of-effort
limits.

The above tasks must be accomplished in the environment of tight Space
Station schedules and of changing priorities associated with space
flight robotics. The contractor must possess detailed knowledge of the
hardware, software designs, and the data products associated with the
Space Station Remote Manipulator System (SSRMS), Mobile Base System
(MBS), the Special Purpose Dexterous Manipulator (SPDM), the Robotic
Workstation (RWS), the Artificial Vision Unit (AVU), the Command and
Control System (CCS), and the Portable Computer System (PCS). The
contractor must be able to meet NASA delivery schedules upon task
inception.

Priorities of specific work to be performed under all tasks and subtasks
of this contract will be determined by NASA. This control includes what
items are to be worked, authorization to proceed, specification of
deliverables, the setting of priorities, and the determination of
schedules. The dynamic nature of the work specified in this contract
requires that the contractor shall be able to change the level and skill
mix of staffing within three calendar weeks after NASA task change
direction. In general, the contractor shall respond to NASA direction
within three working days.

**13.1 INSTRUMENTATION, PROGRAM AND COMMAND LIST (IP&CL) TASK**

The object of this task is to provide to the NASA Mission Build Facility
the Instrumentation, Program and Command List (IP&CL) standard-input
data associated with the International Space Station (ISS) Mobile
Servicing System (MSS) robotics software. Included are data associated
with the flights that use the SSRMS, the MBS, the SPDM, the RWS, and the
AVU.

13.1.1 IP&CL TASK BACKGROUND

NASA established the MBF to manage the vast amounts of ISS systems'
data, payload data, and flight software for the large numbers of users
who require access to these data. The MBF prime responsibilities are:
collection, integration, and distribution of a controlled and baselined
set of ISS flight software, flight data, and associated ground data.
From the data perspective, the MBF provides a common data exchange
language and mechanism between and among the ISS/payload data sources
and their multi-purpose destinations supporting flight software
production, flight readiness, on-orbit operations, and ground support.

Defining each side of the MBF's common data exchanges are the
Standard-Input data files and Standard-Output data files. The IP&CL task
of this contract produces the Standard-Input files for MSS-associated
robotic elements. These files are then manipulated by the MBF and the
NASA Mission Operations Directorate, resulting in modified
Standard-Output data files. These modified output files compose the
integrated set of baselined ISS/payload data that is accessible by the
user community. Examples of the user community include the developers of
the Command and Control System (CCS), Portable Computer System (PCS) and
mission control software.

File definition, format, and delivery requirements for both the input
and output standard files are specified by the Integration Signal Data
Team (ISDT). The ISDT's vehicle for communicating these requirements is
the Space Station Software Standards and Procedures Specification (SSPS)
Document, D684-10056-01. The work of the IP&CL task of this contract is
to be performed in accordance with the most recent version of this SSPS.

13.1.2 IP&CL TASK DESCRIPTION

This task produces Space Station Standard-Input data files, specified as
IP&CL within the SSPS. Data for these files are developed via a two-step
process. Step A defines Part 1 data, which defines the existence of a
given signal or command, along with its functional characteristics. Step
B uses the Part 1 data as a baseline from which to define or refine
further signal and command data. In addition, Step B defines device,
bus, and conversion data along with groupings, instantiations, and
relationships all embodied within a set of relational files. The
conversion data, for example, includes all conversions required to take
the data from the Operations Control Software (OCS) units to the units
required for display on the PCS Graphical User Interface (GUI). It is
this set of IP&CL relational files that comprise the standard-input to
the MBF. The explicit format for these files is specified in the SSPS
Document.

The particular IP&CL data to be produced in this task is that associated
with the information that flows between the MSS Control Electronic Unit
(CEU) and the CCS. Both Parts 1 and 2 descriptions of this data are
contained in Space Station Program (SSP) Document 41175 Book 10.
MSS-related commands and signal (also called data ) parameters are
included for the RWS, SSRMS, MBS, SPDM, and AVU. The task covers the
information that flows in the twelve CCS 1553 "boxcars" associated with
Space Station Robotics. The task encompasses some initial data
requirements specifications, the development, pre-submittal validation,
and delivery of the MSS-related IP&CL standard-input data files and
follow-on error corrections.

Efforts under this task will be relatively continuous with the range of
deliverables specified in sections 13.1.3, 13.1.4, 14, and 15.

13.1.3 IP&CL SUBTASKS

The IP&CL subtasks included initial interface requirements development
support, MBF compatibility checking, Requirements Program Unique
Identifier (RPUI) traceability , Standard-In production, pre-MBF
validation, data submittal, contract reporting, and post-MBF delivery
support.

13.1.3.1 IP&CL INTERFACE DEVELOPMENT SUPPORT

Before IP&CL data can be produced and delivered, prerequisite tasks
often must be performed. The contractor shall, as needed, coordinate
data requirements with the software design and integration teams,
provide inputs to the SSP 41175 requirements process, assign RPUI's and
Program Unique Identifier (PUI) numbers, and support other program
processes judged to be necessary to accomplish the submittal of IP&CL.

13.1.3.2 IP&CL MBF COMPATIBILITY CHECKING

The MBF compatibility sub-task shall be accomplished by reviewing the
IP&CL definition and necessary delivery requirements in the SSPS to
ensure that these requirements accommodate all types of MSS IP&CL data.
Any function and/or deficiencies not supporting MSS items like unique
devices, conversion algorithms, etc., shall be recorded by the
contractor in the proper Space Station format and submitted to the
Integration Signal Data Team (ISDT) for SSPS Document baseline update.
Substantial SSPS changes may require additional negotiation and approval
time. Government approved changes from this sub-task will be used by MBF
developers to accommodate MSS data.

13.1.3.3 IP&CL RPUI TRACEABILITY

The RPUI traceability sub-task shall be accomplished by providing an
electronic spreadsheet defining traceability between 7-character Part 1
RPUI data and IP&CL 13-character Part 2 Primitive data.

The RPUI Traceability sub-task shall provide a preview as to how IP&CL
primitives map logically to their parent Part 1 RPUI data/commands. The
traceability allows early ISS program development support, as well as
visibility into the progress of the standard-input sub-task defined in
Section 13.1.1.

MSS Part 1 RPUI commands and interface data are documented in SSP
Document 41175, Book 10, Sections 3.2.1, 3.3.1, 3.3.2, 3.3.3, and 3.3.4.
SSPS Document, Section 3.3.1.2, defines five major categories of ISS
signals. For this RPUI traceability, only one category is required:
Software Primitives. The contractor shall create an RPUI traceability
table that logically maps all primitives in this category of IP&CL data
to their corresponding Part 1 RPUIs. The resultant RPUI traceability
table shall be delivered to NASA as an EXCEL spreadsheet.

Normally, the definition of SPUIs, Device PUIs and Bus PUIs will assume
that the origin of all data is above the lower unit software e.g., at
the Operations and Control Software (OCS) or the Workstation Host
Software (WHS) level. If appropriate, however, the PUIs may be defined
with lower origins.

13.1.3.4 IP&CL STANDARD-IN PRODUCTION

The Standard-Input sub-task shall be accomplished by providing to the
MBF all SSPS Document required standard-input IP&CL data and their
relational interdependencies as required in the SSPS Document. This data
shall be stage specific and be compatible with the most recent version
of SSP 41175 and its approved changes (called PIRNs). Standard-input
data under this sub-task shall be delivered in file format/media as
specified in the most recent version of the SSPS Document.

This standard-input sub-task shall provide all MSS software-related
standard-input files (usually up to eleven files) required by the MBF.

13.1.3.5 IP&CL PRE-MBF VAILIDATION

Prior to submitting the completed standard-input files to the MBF, the
Contractor shall perform a pre-submittal check of the standard-input
files in order to ensure proper format and legal values. This shall be
done by processing the proposed standard-input files through a
validation tool provided by the ISDT. The validation tool is described
in Section 15.

The ISDT validation tool ensures proper file/data content, format and
legal values. It does not check the relational integrity between files.
Standard-input files processed by the ISDT validation tool generate a
summary report. Only when completed standard-input files generate no
discrepancies in the summary report shall the Contractor deliver them as
specified in Section 13.1.3.6 to the MBF, along with a corresponding
summary report.

13.1.3.6 IP&CL DATA SUBMITTAL

When pre-MBF validation has been completed, the contractor shall deliver
the files electronically in SSPS format, simultaneously to the NASA
technical contract monitor and to the MBF. In addition, upon request,
the contractor shall deliver the entire database in Access or comparable
format to the NASA technical monitor.

13.1.3.7 IP&CL CONTRACT REPORTING

The Government must have visibility into the process and progress of the
IP&CL sub-tasks. The contractor shall provide the current master file
used to produce IP&CL submittals, SSP 41175 Book 10 requirements change
inputs, Standard-Input files, and output results from the ISDT
validation tool to the Government at any time during the contract period
of performance. The normal response time to provide such data shall be
three working days from the time of request.

13.1.3.8 IP&CL POST-MBF DELIVERY SUPPORT

The contractor shall ensure that data provided to the Government meets
the requirements in the SSPS Document. If errors are detected with the
data provided by the contractor, the contractor shall correct the data
expeditiously, revalidate using the validation tool, and resubmit the
changed data elements to the NASA technical monitor and the MBF.

The Contractor shall provide in a timely manner standard-input file
changes deemed necessary by the Government to support verification and
flight preparation activities.

13.1.4 IP&CL DELIVERY SCHEDULES

Schedules for the IP&CL data submittals shall be per the most recent
Standard -In dates as specified by the Avionics Software Control Board
and negotiated through its sub boards. Section 14 of this contract
contains the current requirements for deliveries. These schedules are
subject to modification with the restriction that any modifications that
are made are coordinated between NASA and the contractor and are
consistent with available contractor resources.

This task originally specifies explicit deliveries to support Flight 5A
through UF-4 and flights associated with safing enhancement software
deliveries. This includes flights associated with the SSRMS, the MBS,
and the SPDM. Additional flights may be added, consistent with available
resources, as the Space Station program evolves.

**13.2** **ROBOTICS SIMULATOR SOFTWARE MODEL (RSSM) TASK**

The object of this task is to provide systems expertise, engineering
analysis, and programming support for integration of the Canadian Space
Agency (CSA) supplied Mobile Servicing System (MSS) robotic models into
NASA simulation software used within JSC and other NASA engineering and
training facilities. These MSS models include the Space Station Remote
Manipulator System (SSRMS), Mobile Base System (MBS), the Special
Purpose Dexterous Manipulator (SPDM), and the Robotic Workstation (RWS).
The Trick Simulation Environment serves as the repository for these MSS
models. NASA JSC facilities requiring MSS models include the Space
Station Training Facility (SSTF), the Integrated Planning System (IPS),
the Shuttle Engineering Simulator (SES), the Multi-use Remote
Manipulator Development Facility (MRMDF), and the Neutral Buoyancy
Laboratory (NBL) underwater SSRMS. Facilities at other NASA sites
include the Contact Dynamics Simulation Laboratory (CDSL) at The
Marshall Space Flight Center (MFSC) in Alabama.

13.2.1 RSSM TASK BACKGROUND

Various simulations and simulators at NASA are used for engineering
analysis, procedures development, and crew training. These applications
must contain accurate representations of flight software as well as
system level hardware models. The fidelity of the models must be such
that objectives of the various simulators can be accomplished. In some
instances, security measures sanctioned by CSA are in place to preserve
the confidentiality of models.

Work under the RSSM task includes requirements development, integration
of both new and modified robotics models into simulation source code,
verification of the implementation, validation of the products, and
support of anomaly resolution. Previous efforts associated with this
task have involved updates to SSRMS models within the Trick-based MSS
simulations. New efforts will include the development and integration of
MBS, SPDM, and RWS models, thus improving the overall MSS capabilities
of the simulation.

13.2.2 RSSM TASK DESCIPTION

[]{.mark}

Under the RSSM task, the contractor shall perform the development of
Trick-based MSS simulations, including the integration of various
models, verification and testing of the models and validation of the
completed products for release to multiple JSC customers. In addition,
this task provides for support of anomaly resolution within the
engineering and training facilities. Finally, systems expertise and
engineering analysis support is required for operations involving the
MSS, e.g., SSRMS payload berthing.

Efforts under this task will be relatively continuous with the range of
deliverables specified in sections 13.2.3, 13.2.4, and 14.

[]{.mark}

13.2.3 RSSM SUBTASKS

The RSSM subtasks include integration of most recent versions of SSRMS
and

other robotic software into Trick, validation of Trick releases, Trick
anomaly resolution, simulation model Data Item Description (DID)
developments, and specified analysis support.

13.2.3.1 Model Insertion

This subtask involves the incorporation of the latest revisions of
models into NASA simulation software. For the SSRMS, the models are
described in SSRMS Simulation Data Package, SPAR-SS-R-1529, including
SSRMS Arm Control Software (SACS), Joint Control System (JCS), and
Latching End Effecter (LEE) Control System (LCS) to produce the Trick
MSS simulation releases. These capabilities shall be developed for
Silicon Graphics Inc. (SGI) workstations based on current Space Station
Training Facility (SSTF) requirements as well as on non-SGI platforms,
including such computers as SUN, Solaris PC, and Linux PC machines to
satisfy additional Trick MSS customer requirements. In addition, this
subtask covers the insertion of models into other NASA simulators such
as the CDSL.

13.2.3.2 Simulation release Validation

This subtask includes validation of the resulting Trick and other MSS
simulation releases. This validation shall be performed as outlined in
MSS Simulation Validation Plan Volume,

CSA-SS-PL-0007.

13.2.3.3 Anomaly Resolution

This subtask involves anomaly resolution after Trick or other MSS
simulation releases have been delivered to the various simulation
customers. The contractor shall analyze MSS-related problems and provide
resolution of such, including code fixes if needed.

13.2.3.4 MBS DID AND SIMULATION Development

The contractor shall develop a DID for NASA MBS model requirements and
provide this information via a Bi-lateral Data Exchange Agreement List
(BDEAL). After the MBS data package associated with the BDEAL has been
delivered by CSA, the contractor shall perform the majority of the
effort to design and develop the initial Trick or other program-based
MBS simulation.

13.2.3.5 SPDM DID AND SIMULATION Development

The contractor shall develop a DID for NASA SPDM model requirements and
provide this information via a BDEAL. After the SPDM data package
associated with the BDEAL has been delivered by CSA, the contractor
shall perform the majority of the effort to design and develop the
initial Trick or other program-based SPDM simulation.

13.2.3.6 RWS DID AND SIMULATION Development

The contractor shall develop a DID for NASA RWS model requirements and
provide this information via a BDEAL. After the RWS data package
associated with the BDEAL has been delivered by NASA, the contractor
shall perform the majority of the effort to design and develop initial
Trick or other program-based RWS simulation.

13.2.3.7 ANALYSIS SUPPORT

The contractor shall provide SSRMS expertise and analysis support to
tasks including, but not limited to, the berthing payloads to the ISS,
including problem initialization, installation method evaluation, and
investigation of FMA capabilities of the SSRMS.

13.2.4 RSSM DELIVERY SCHEDULES

Data deliverables and their schedules are found in Section 14,
Reports/Data Requirements.

**13.3 ROBOTICS INTEGRATED TEST SUPPORT (RITS) TASK**

This task provides planning, test support, and problem resolution of
Space Station robotics integrated tests and verification. This task
would conduct selected integrated tests.

13.3.1 RITS TASK BACKGROUND

MSS and other robotics Space Station elements are controlled and
monitored by a distributed software architecture. The software composing
this architecture has been, and is being, developed by multiple
companies, contracts, space agencies, and countries. As launch time
approaches, this software must be brought together in integrated
testing, often with much of the pertinent hardware. This integrated
testing, to date, has been performed in the MSS Avionics Integration
Facility (MAIF) at MDR in Brampton, Ontario, the Software Verification
Facility (SVF) and the ISS Integration Laboratory (ISIL) at JSC in
Houston, and the NASA facilities at MSFC and the Kennedy Space Center
(KSC).

The testing used various combinations of actual flight hardware,
flight-equivalent hardware, engineering-equivalent hardware, and
software simulation of missing hardware. In most instances, various
releases of flight software have been used. The purpose of the RITS task
is to support the ongoing and future versions of this integrated
testing.

13.3.2 RITS TASK DESCRIPTION.

Under the RITS task, the contractor will perform integrated Space
Station Robotics test planning, provide selected real-time systems
engineering test support, and integrated test problem resolution.
Initially, the robotics hardware will include the RWS, SSRMS, MBS, MT,
and the SPDM. Some of the tests covered include specific risk reduction
tests, Space Station Stage testing at JSC, various dry-run tests, and
Multi-Element Integrated Tests (MEIT) at KSC.

If deemed necessary by NASA, the RITS subtask 13.3.3.5, RITS Integrated
Test Hosting, will be activated. Subtask 13.3.3.5 is the hosting and
conduction of integrated hardware and software testing at one of the
Space Station integration facilities. The current best estimate of such
a test would be for the SPDM to be held at the MAIF.

Efforts under this task will be accomplished on an as-needed basis as
instructed by NASA, with the range of deliverables specified in sections
13.3.3, 13.3.4, and 14. The level of effort for this task will be
consistent with available resources. Initially the combined level of
effort of this task and Task 13.5, will be no greater than the
equivalent of 1.5 equivalent persons per year.

13.3.3 RITS SUBTASKS

The RITS subtasks include test planning, test preparation support,
real-time systems engineering test support, and test problem resolution
support. A test conduction subtask may be activated at a future date.

13.3.3.1 RITS TEST PLANNING

The contractor shall assist NASA in the strategic and tactical planning
of MSS-related integrated tests. This planning shall include, but not be
restricted to, high level layout of tests needed, high level test scope
and objectives, determination of which tests are to be run in which
facilities, resource requirements, and high and mid-level test
schedules.

13.3.3.2 RITS TEST PREPARATION

In this subtask the contractor shall, as specified by NASA, participate
in, and sometimes lead, work sessions and other meetings associated with
detailed test objectives and procedures, hardware and software
logistics, and the determination of personnel support.

13.3.3.3 RITS REAL-TIME SYSTEM ENGINEERING

In this subtask the contractor shall provide selected systems
integration real-time test support, as specified by NASA, for
MSS-related integrated tests. Two series of such tests planned in the
near-term are the MEIT II and MEIT II Regression tests. Each series of
tests includes dry runs at JSC and testing of the combined MBS hardware
and software at KSC.

13.3.3.4 RITS PROBLEM RESOLUTION SUPPORT

In this subtask the contractor shall provide post-test problem
resolution support, as specified by NASA, for MSS-related integrated
tests. This support may include the determination of problem root cause,
the relating of problems to occurrences in previous tests, and the
tracking of problems to closure with planned fixes.

13.3.3.5 RITS INTEGRATED TEST HOSTING

If activated, this subtask shall include, the preparation of test
procedures, the reconfiguration of the test facility to accommodate the
specific hardware needed (such as the SPDM, the CCS MDM, the PCS, etc.),
the required test facility hardware and software support during the
integrated test, conduction of the integrated test, and the recording of
resultant problems.

13.3.4 RITS DELIVERY SCHEDULES

Deliveries and their schedules are found in section 14.

**13.4 ROBOTICS FLIGHT OPERATIONS PREPARATION (RFOP) TASK**

The objective of this task is to provide technical support to the NASA
Space Station operations community associated with preparations for
ground flight support. Included are the development of robotics systems
description papers and subtasks associated with malfunction procedures
and integrated testing and the provision of training classes. The Space
Station robotics elements include the RWS, SSRMS, MBS, and SPDM.

13.4.1 RFOP TASK BACKGROUND

The Mission Operations Directorate (MOD) at the Johnson Space Center
(JSC) has the prime responsibility of providing ground support for Space
Station operations. Long before the actual mission, flight controllers
must be prepared for real-time support. This preparation includes
personal study of pertinent flight documents, attendance at training
sessions, and active participation in integrated simulations. The RFOD
task provides specific support to aid MOD in the preparation.

13.4.2 RFOP TASK DESCRIPTION

The RFOP task provides specific Space Station robotics expertise
required by NASA MOD. Contract personnel, knowledgeable in the detailed
design of the RWS, SSRMS, MBS, and SPDM, shall be required to write
and/or modify robotics system handbooks, handbook drawings, systems
briefs, and procedures. Robotics malfunction procedures documents must
be evaluated for accuracy and completeness. Detailed training classes,
specified by MOD, must be developed and presented. In addition,
contractor personnel shall follow hardware and software testing results
and system upgrades in order to ascertain their effects on real-time
flight operations and documentation.

Efforts under this task will be relatively continuous with the range of
deliverables specified in sections 13.4.3, 13.4.4, and 14. Level of
effort will be consistent with available resources. The RFOP task shall
provide one full-time engineer located at NASA MOD starting at task
inception. When appropriate, work may also be performed at the
contractor's home base by qualified system experts.

13.4.3 RFOP SUBTASKS

Subtasks include flight control documentation production, malfunction
procedure support, test results and system upgrade support, and training
development.

13.4.3.1 RFOP FLIGHT CONTROL DOCUMENT PRODUCTION

The contractor shall provide supporting effort to the development and
evaluation of RWS, SSRMS, MBS, and SPDM console documentation consisting
of system drawings, system briefs, and nominal operating procedures.
This effort shall ensure that the products are technically correct and
adequate to support real-time operations and issue resolution. Included
in this effort shall be support to the validation of the system
signatures encountered during nominal operations and the development of
data source integrity records.

13.4.3.2 RFOP malfunction procedures SUPPORT

Effort shall be allocated to the evaluation and development of RWS,
SSRMS, MBS, and SPDM malfunction procedures. This effort shall ensure
that the procedures are adequate for real-time on-orbit issues
resolution.

13.4.3.3 RFOP TEST RESULTS SUPPORT AND SYSTEM UPGRADE SUPPORT

The contractor shall keep informed on all RWS, SSRMS, MBS, and SPDM
hardware and software test results. Additionally, the contractor shall
follow planned system upgrades and enhancements. The object of this
subtask is to assess the impacts of these tests and upgrades on
real-time operations, identify any required changes to documentation and
training, and make any required alterations to the documentation and
training.

13.4.3.4 RFOP TRAINING DEVELOPMENT

In this subtask, the contractor shall develop and teach MSS-related
training classes whose topics are specified by MOD. The content of these
courses shall cover detailed technical topics related to the system
design or behavior of the RWS, SSRMS, MBS, and SPDM systems. Course
contents must be detailed enough to enable flight operations personnel
to support real-time flight operations.

13.4.4 RFOP DELIVERY SCHEDULES

The schedule for the completion of all system documentation and training
is driven by the Space Station program schedules and assembly sequence.
The RFOP subtasks shall be supported in priority effort as specified by
MOD.

**13.5 ROBOTICS EXPERTISE AND AD HOC DELIVERABLES (READH) TASK**

This task consists of robotics-related studies and other tasks defined
by NASA. The subjects and lengths of these studies will be varied,
depending upon NASA's needs. Subjects include various engineering
disciplines associated with MSS and other similar Station robotics.
Examples of past studies can be found in section 13.5.1.

13.5.1 READH TASK BACKGROUND

On occasions, NASA must have analyses performed related to MSS
equipment. Examples from the past include the production of an
electrical power time profile for the Russian-to-American Converter Unit
during its transfer from the Space Shuttle to the Service Module on the
Space Station, the production of RWS Failure Detection Isolation
Reports, and thermal analysis of various robotic structures. These tasks
were defined as the needs arose.

13.5.2 READH TASK DESCRIPTION.

Subtasks of this task will be defined ad hoc with specific end dates.
Efforts under this task will be accomplished on an as-needed basis, as
defined by NASA, with the range of deliverables specified in sections
13.5.3, 13.5.4, 14 and 15. Initially the combined level of effort of
this task, without Subtask 13.3.3.5, and Task 13.3 will be no greater
than the equivalent of 1.5 equivalent persons per year.

13.5.3 READH SUBTASKS

The scope of this work will consist of special studies.

13.5.4 READH DELIVERY SCHEDULES

Schedules of ordered deliverables will be defined as needed.

**14. REPORTS/DATA REQUIREMENTS (DRs)**

**IP&CL DR 1.1 SSPS Notice Validation**

Use: To ensure that MBF software can accept the correct MSS data type

> inputs

Content: Edits of SSPS D684-10056-01

Delivery: Approximately twice yearly, one week after NASA delivery of
SSPS candidate changes

NASA Approval: Yes

Distribution: ER3/R. E. Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic

SOW Reference: 13.1.3.2

**IP&CL DR 1.2 Traceability for SPDM Standard-Input Data**

Use: Provides a preview as to how IP&CL primitives logically map to

their parent Part 1 RPUI data/commands. This traceability allows

early ISS program development support, as well as visibility into

> the progress of the standard-input sub-task.

Content: A RPUI traceability table that logically maps all primitives in
this

category of IP&CL data to their corresponding Part 1 RPUIs.

Delivery: Basic bus 15 March 2001; engineering version 15 June 2001

First Submit: August 15, 2001

NASA approval: Yes

Distribution: ER3/R. E. Eckelkamp

> ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet)

**IP&CL DR 1.3 Flight Cycle Standard-Input Updates for MBS**

Use: Flight data submittal into the MBF for Flight 8A.

Content: Changes to ACCESS database content from last MBS delivery

Delivery: September 5, 2001

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.4 Delta Flight Cycle Standard-Input Updates for MBS**

Use: To delivery any necessary data changes into the MBF for Flight 8A.

Content: Changes to ACCESS database content from last 8A delivery

Delivery: December 5, 2001

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.5 Flight Cycle Complete MBS Standard-Input Database**

Use: 8A through UF-2 in-flight trouble shooting.

Content: Complete MBS 8A database

Delivery: February 15, 2002

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet)

SOW Reference: 13.1.3.6

**IP&CL DR 1.6 Basic Bus Standard-Input Data for 12A**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: September 5, 2001

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.7 Basic commands and Data Standard-Input Data for 12A**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: December 5, 2001

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.8 Engineering Cycle Standard-Input Data for 12A**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: March 5, 2002

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.9 Flight Cycle Standard-Input Data for 12A**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: June 5, 2002

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.10 Delta Flight Cycle Standard-Input Updates for 12A**

Use: To delivery any necessary data changes into the MBF for Flight 12A.

Content: Changes to ACCESS database content from last 12A delivery

Delivery: July 15, 2002

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

####### IP&CL DR 1.11 Flight Cycle Complete 12A Standard-Input Database

Use: 12A through 5R in-flight trouble shooting.

Content: Complete MBS 12A database

Delivery: September 15, 2002

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet)

SOW Reference: 13.1.3.6

**IP&CL DR 1.12 Basic Command and Data Standard-Input Data for SPDM**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: September 5, 2001

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.13 Engineering Cycle Standard-Input Data for SPDM**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: March 5, 2002

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.14 Flight Cycle Standard-Input Updates for SPDM**

Use: Flight data submittal into the MBF for Flight UF-4.

Content: Changes to ACCESS database content from last SPDM delivery

Delivery: December 5, 2002

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.15 Delta Flight Cycle Standard-Input Updates for SPDM**

Use: To delivery any necessary data changes into the MBF for Flight UF-4

Content: Changes to ACCESS database content from last SPDM delivery

Delivery: March 5, 2003

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.16 Flight Cycle Complete UF-4 Standard-Input Database**

Use: UF-4 and subsequent in-flight troubleshooting.

Content: Complete SPDM UF-4 database

Delivery: September 25, 2003

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet)

SOW Reference: 13.1.3.6

**IP&CL DR 1.17 Basic Command and Data Standard-Input Data for MSS
Upgrade**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: June 5, 2003

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.18 Engineering Cycle Standard-Input Data for MSS Upgrade**

Use: To allow MBF personnel to validate the

> inputs and build the established Standard-Out files.

Content: Defined by SSPS D684-10056-01 and subsequent Notices

Delivery: September 5, 2003

NASA Approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.19 Flight Cycle Standard-Input Updates for MSS Upgrade**

Use: Flight data submittal into the MBF for MSS upgrade flight

Content: Changes to ACCESS database content from MSS upgrade delivery

Delivery: December 5, 2003

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.20 Delta Flight Cycle Standard-Input Updates for MSS
Upgrade**

Use: To delivery any necessary data changes into the MBF for MSS upgrade
flight

Content: Changes to ACCESS database content from last MSS upgrade
delivery

Delivery: March 5, 2004

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet) and Hard Copy of Validation

Summary Report

SOW Reference: 13.1.3.4 and 13.1.3.6

**IP&CL DR 1.21 Flight Cycle Complete MSS Upgrade Standard-Input
Database**

Use: MSS upgrade in-flight troubleshooting.

Content: Complete MSS upgrade flight database

Delivery: September 25, 2003

NASA approval: Yes

Distribution: ER3/R.E.Eckelkamp

ER3/Dale Garrett

Program Repository

Program-authorized electronic library

Format: Electronic (EXCEL spreadsheet)

SOW Reference: 13.1.3.6

###### RSSM DR 2.1 Trick SPDM Model DID Development 

Use: To structure SPDM Trick Requirements

Content: SPDM simulation model DID

Deliveries: August 15, 2001

NASA Approval: Yes

Distribution: ER7/L. J. Quiocho

ER3/R. E. Eckelkamp

Format: documentation in DID format

SOW Reference: 13.2.3.1,13.2.3.5, and 13.2.3.6

###### RSSM DR 2.2 Trick Additional Flight Software Modules Inclusion 

Use: To increase fidelity of crew MSS training

Content : Trick code enhancement modules

Deliveries: when needed as specified by NASA

NASA Approval: Yes

Distribution: ER7/L. J. Quiocho

ER3/R. E. Eckelkamp

Format: source code modules and accompanying change documentation

SOW Reference: 13.2.3.1

**RSSM DR 2.3 Trick MSS Release Support**

Use: To enable accurate crew MSS training

Content: Programming of and integration support of Trick

Deliveries: When needed, as specified by NASA

NASA Approval: Yes

Distribution: ER7/L. J. Quiocho

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: source code

SOW Reference: 13.2.3.1, 13.2.3.4, 13.2.3.5, and 13.2.3.6

###### 

###### RSSM DR 2.4 Trick Validation Support 

Use: To validate Trick releases

Content: Per CSA-SS-PL-0007

Deliveries: Completion 1 to 3 months after integrated model have been
inserted as specified by NASA

NASA Approval: Yes

Distribution: ER7/L. J. Quiocho

ER3/R. E. Eckelkamp

Program Repository

Format: error correction, validation reports

SOW Reference: 13.2.3.2

###### 

###### RSSM DR 2.5 Trick Anomaly Resolution 

Use: To assist in Trick anomaly resolution within JSC training
facilities

Content: Per CSA-SS-PL-0007

Deliveries: Completion 1 to 3 months after integrated model have been
inserted as specified by NASA

NASA Approval: Yes

Distribution: ER7/L. J. Quiocho

ER3/R. E. Eckelkamp

Program Repository

Format: programming support

SOW Reference: 13.2.3.3

###### RSSM DR 2.6 Trick-based Analysis Support 

Use: To perform specific station robotic analyses using Trick

Content: As specified by NASA

Deliveries: Specific analyses and associated technical memos as
specified by NASA

NASA Approval: Yes

Distribution: ER7/L. J. Quiocho

ER3/R. E. Eckelkamp

Program Repository

Format: error correction, validation reports

SOW Reference: 13.2.3.7

**RITS DR 3.1 MEIT II Planning Support**

Use: To provide selected MEIT II planning and test preparation support,

Content: Task plans and planning meeting support

Deliveries: August 1 through October 15, 2001

NASA Approval: Yes

Distribution: OB/Shakeel Razvi

ER3/R. E. Eckelkamp

Format: electronic schedules and planning papers

SOW Reference: 13.3.3.1 and 10.3.3.2

**RITS DR 3.2 MEIT II Real-time Support**

Use: To provide selected MEIT II real time

> system engineering support.

Content: Real-time support tasks as defined by OM7.

Deliveries: During MEIT II dry run and KSC tests

NASA Approval: Yes

Distribution: OB/Shakeel Razvi

ER3/R. E. Eckelkamp

Format: as directed by OM7

SOW Reference: 13.3.3.3

**RITS DR 3.3 MEIT II Problem Resolution Support**

Use: To provide post MEIT problem resolution support

Content: Specific follow-ups of anomalies as specified by OM7.

Deliveries: As needed

NASA Approval: Yes

Distribution: OB/Shakeel Razvi

ER3/R. E. Eckelkamp

Format: electronic problem databases

SOW Reference: 13.3.3.4

####### RFOP DR 4.1 System Handbook Drawing Updates 

Use: To enable MOD and flight personnel to understand and control the
MSS-related hardware and software.

Content: Initial and updated handbook drawings and supporting text for
MSS-related equipment.

Deliveries: As needed by MOD

NASA Approval: Yes

Distribution: DX22/Angela Prince

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: Electronic and hard copies of drawings and text

SOW Reference: 13.4.3.1

####### RFOP DR 4.2 Malfunction Procedures Review 

Use: To enable MOD and flight personnel to perform near-real-time
reactions to MSS-related hardware and software malfunctions.

Content: Review and modification of MSS-related malfunction procedures
manuals.

Deliveries: As needed by MOD

NASA Approval: Yes

Distribution: DX22/Angela Prince

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: Electronic and hard copies of procedural manual updates.

SOW Reference: 13.4.3.2

####### 

####### 

####### 

####### 

####### 

####### 

####### 

####### 

####### RFOP DR 4.3 Integrated Testing Anomaly Support 

Use: To assist MOD and flight personnel in converting integrated test
results into informational summaries and operations notes

Content: Summaries of software and hardware anomalies and operational
notes

Deliveries: As needed by MOD

NASA Approval: Yes

Distribution: DX22/Angela Prince

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: EXCEL Electronic and hard copies of summaries, electronic and
hard copies of operational notes

SOW Reference: 13.4.3.3

####### RFOP DR 4.4 MSS-Related Training Classes 

Use: To enable MOD and flight personnel to gain understanding of
MSS-related hardware and software design, operations, and malfunctions

Content: Class sessions

Deliveries: Per MOD training schedules

NASA Approval: Yes

Distribution: DX22/Angela Prince

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: Electronic and hard copies of class material

SOW Reference: 13.4.3.4

######## RFOP DR 4.5 MOD Console Handbook System Briefs Updates 

Use: To enable MOD and flight personnel to understand and control the
MSS-related hardware and software.

Content: Review and identification of required updates to the console
handbook system briefs for MSS-related equipment.

Deliveries: As needed by MOD

NASA Approval: Yes

Distribution: DX22/Angela Prince

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: Electronic and hard copies of console handbook system brief
updates.

SOW Reference: 13.4.3.1

######### **RFOP DR 4.6 MOD Nominal Procedure Updates** 

Use: To enable MOD and flight personnel to understand and control MSS
related hardware and software.

Content: Review and identification of required updates to the MSS
nominal procedures.

Deliveries: As needed by MOD

NASA Approval: Yes

Distribution: DX22/Angela Prince

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: Electronic and hard copies of nominal procedure updates.

SOW Reference: 13.4.3.1

####### READH DR 5.1 Special Studies

Use: To provide specific technical studies associated with MSS elements

Content: Results and analysis reports as specified by OM7

Delivery: As needed by OM7

NASA approval: Yes

Distribution: OM7/Henry Orosco

ER3/R. E. Eckelkamp

Program Repository

Program-authorized electronic library

Format: Electronic and Hard Copy of results

SOW Reference 13.5.3

**15. [GOVERNMENT DELIVERABLES]{.underline}**

> This section describes the deliverables from the government to the
> contractor.

+--------+-------------------------+-----------------------------------+
| #####  | ##### Item              | ##### Time                        |
| Number |                         |                                   |
+--------+-------------------------+-----------------------------------+
| IP&CL  | SSPS Change notices     | When released by the ISDT         |
| 1      |                         |                                   |
+--------+-------------------------+-----------------------------------+
| IP&CL  | ISDT validation tool    | As available from the ISDT        |
| 2      | updates                 |                                   |
+--------+-------------------------+-----------------------------------+
| IP&CL  | SSP 41175 Book 10 PIRNs | As available from Boeing Conf.    |
| 3      |                         | Mgmt.                             |
+--------+-------------------------+-----------------------------------+