<table>
<colgroup>
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 13%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 4%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="19"><p>National Aeronautics and Space Administration</p>
<p>Lyndon B. Johnson Space Center</p>
<p>Houston, TX 77058</p></td>
<td colspan="33"><strong>ORDER FOR SUPPLIES OR SERVICES</strong></td>
<td colspan="3">Page <u>1</u> of</td>
<td colspan="7">28</td>
</tr>
<tr class="even">
<td colspan="15">1. PURCHASE ORDER NO.</td>
<td colspan="11">2. DATE OF ORDER</td>
<td colspan="36">NOTE: MARK ALL PACKAGES AND PAPERS WITH ORDER NO.</td>
</tr>
<tr class="odd">
<td colspan="15">322</td>
<td colspan="11">04/04/02</td>
<td colspan="36">Certified for National Defense under DPAS (15 CFR 700)
DO C9</td>
</tr>
<tr class="even">
<td colspan="26">3. ISSUING OFFICE</td>
<td colspan="13">4. SHIP TO:</td>
<td colspan="23">Transportation Officer, Building 421</td>
</tr>
<tr class="odd">
<td colspan="26">NASA Johnson Space Center, Houston, TX 77058</td>
<td colspan="12"></td>
<td colspan="24">NASA Johnson Space Center</td>
</tr>
<tr class="even">
<td colspan="8">Attn:</td>
<td colspan="18">Wayne C. Buckley</td>
<td colspan="12"></td>
<td colspan="24">Houston, TX 77058</td>
</tr>
<tr class="odd">
<td colspan="11">Org./Buyer:</td>
<td colspan="15">BN / M19</td>
<td colspan="12"></td>
<td colspan="24">Mark For: Accountable Property</td>
</tr>
<tr class="even">
<td colspan="7">Tel. No.:</td>
<td colspan="9">281-483-5568</td>
<td colspan="2">Fax:</td>
<td colspan="8">x37890</td>
<td colspan="12"></td>
<td colspan="8">Purchase Order No:</td>
<td colspan="16"></td>
</tr>
<tr class="odd">
<td colspan="16"><p>5. CONTRACTOR</p>
<p>Lockheed Martin Space Operations Company</p>
<p>Attn: Kathy J. Collins</p>
<p>595 Gemini</p>
<p>Houston, TX 77058</p></td>
<td>TIN:</td>
<td colspan="9"></td>
<td colspan="36"><ol start="6" type="1">
<li><p>DELIVER ON OR BEFORE:</p></li>
<li></li>
</ol></td>
</tr>
<tr class="even">
<td colspan="9">PHONE:</td>
<td colspan="17">281-853-3049</td>
<td colspan="15">F.O.B. POINT:</td>
<td colspan="21"></td>
</tr>
<tr class="odd">
<td colspan="26">7. CONFIRMING ORDER:</td>
<td colspan="36">8. BILLING ADDRESS:</td>
</tr>
<tr class="even">
<td colspan="10">FROM:</td>
<td colspan="13"></td>
<td colspan="3"></td>
<td colspan="36"><blockquote>
<p>NASA Johnson Space Center</p>
</blockquote></td>
</tr>
<tr class="odd">
<td colspan="10">TO:</td>
<td colspan="14"></td>
<td colspan="2"></td>
<td colspan="36">Attn: LF231/Funding &amp; Commercial Accounting
Section</td>
</tr>
<tr class="even">
<td colspan="10">DATE:</td>
<td colspan="12"></td>
<td colspan="4"></td>
<td colspan="36">Houston, TX 77058</td>
</tr>
<tr class="odd">
<td colspan="26"></td>
<td colspan="18">Purchase Order No.:</td>
<td colspan="15"></td>
<td colspan="3"></td>
</tr>
<tr class="even">
<td colspan="26"></td>
<td colspan="18"></td>
<td colspan="18"></td>
</tr>
<tr class="odd">
<td colspan="62">9. TYPE OF ORDER:</td>
</tr>
<tr class="even">
<td></td>
<td colspan="2"></td>
<td colspan="12">PURCHASE: REFERENCE</td>
<td colspan="11"></td>
<td colspan="3"></td>
<td colspan="2"></td>
<td colspan="31">DELIVERY: Except for the Terms and Conditions of
Purchase</td>
</tr>
<tr class="odd">
<td colspan="4"></td>
<td colspan="22"></td>
<td colspan="36">Order listed on the following page, this delivery order
is subject to</td>
</tr>
<tr class="even">
<td colspan="27">Please furnish the following on the terms and
conditions specified</td>
<td colspan="35">instructions contained on this form and is issued
subject to the</td>
</tr>
<tr class="odd">
<td colspan="27">on this order.</td>
<td colspan="20">terms and conditions of contract number:</td>
<td colspan="14"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="27"></td>
<td colspan="20"></td>
<td colspan="15"></td>
</tr>
<tr class="odd">
<td colspan="30">10. DISCOUNT TERMS:</td>
<td colspan="32">11.</td>
</tr>
<tr class="even">
<td colspan="30"></td>
<td colspan="6">BY</td>
<td colspan="12"><mark>Original signed by: Wayne Buckley</mark></td>
<td colspan="2"></td>
<td colspan="7">04/04/02</td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="30"></td>
<td colspan="6"></td>
<td colspan="12">CONTRACTING OFFICER</td>
<td></td>
<td colspan="9">DATE</td>
<td colspan="4"></td>
</tr>
<tr class="even">
<td colspan="62">12. SCHEDULE</td>
</tr>
<tr class="odd">
<td colspan="5">ITEM<br />
NO.</td>
<td colspan="31">DESCRIPTION</td>
<td colspan="6">QUANTITY<br />
ORDERED</td>
<td colspan="3">UNIT</td>
<td colspan="6">UNIT<br />
PRICE</td>
<td colspan="5">AMOUNT</td>
<td colspan="6">QUANTITY<br />
ACCEPTED</td>
</tr>
<tr class="even">
<td colspan="5"></td>
<td colspan="31"><p><strong>SORCE mission</strong></p>
<p><strong>CLIN 1 Pre-launch Services and</strong></p>
<p><strong>Launch &amp; Early Orbit Support</strong></p>
<p><strong>CLIN 2 Mission Operations - Base Period</strong></p>
<p><strong>CLIN 3 Mission Operations - Option 1</strong></p>
<p><strong>CLIN 4 Mission Operations - Option 2</strong></p>
<p><strong>CLIN 5 Mission Operations - Option 3</strong></p>
<p><strong>CLIN 6 Mission Operations - Option 4</strong></p>
<p><strong>SIRTF mission</strong></p>
<p><strong>CLIN 7 Pre-launch Services and</strong></p>
<p><strong>Launch &amp; Early Orbit Support</strong></p>
<p><strong>CLIN 8 Security Engineering Support</strong></p>
<p><strong>TOTAL</strong></p></td>
<td colspan="6"></td>
<td colspan="3"></td>
<td colspan="6"><p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p>
<p><strong>See Attached</strong></p></td>
<td colspan="5"><p><strong>$273,946</strong></p>
<p><strong>$ 5,962</strong></p>
<p><strong>$ 0</strong></p>
<p><strong>$ 0</strong></p>
<p><strong>$ 0</strong></p>
<p><strong>$ 0</strong></p>
<p><strong>$159,809</strong></p>
<p><strong>$ 57,500</strong></p>
<p><strong>$497,217</strong></p></td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="51">13. FOR JSC INTERNAL USE ONLY:</td>
<td colspan="11">14. Total</td>
</tr>
<tr class="even">
<td colspan="14">PURCHASE REQUEST NO.:</td>
<td colspan="8"></td>
<td colspan="3"></td>
<td colspan="9">COMP.</td>
<td colspan="3"></td>
<td colspan="3">PART.</td>
<td colspan="3">PPC:</td>
<td colspan="8"></td>
<td colspan="11"></td>
</tr>
<tr class="odd">
<td colspan="14">APPROPRIATION DATA:</td>
<td colspan="37"></td>
<td colspan="11"><p><strong>$ 11,459,262</strong></p>
<p id="section" class="heading"></p></td>
</tr>
<tr class="even">
<td colspan="14">ACCOUNTING CODE:</td>
<td colspan="37"></td>
<td colspan="11"></td>
</tr>
<tr class="odd">
<td colspan="14">REISSUE TO:</td>
<td colspan="37"></td>
<td colspan="11"></td>
</tr>
<tr class="even">
<td colspan="62">15. QUANTITIES IN “QUANTITY ACCEPTED” COLUMN HAVE
BEEN:</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="4"></td>
<td colspan="6">INSPECTED</td>
<td></td>
<td colspan="7">ACCEPTED</td>
<td></td>
<td colspan="41">RECEIVED</td>
</tr>
<tr class="even">
<td colspan="28">TO CONFORM TO THE CONTRACT.</td>
<td colspan="5">BY</td>
<td colspan="19"></td>
<td colspan="2"></td>
<td colspan="7"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="32">ACCEPTANCE WILL BE AT JSC UNLESS OTHERWISE NOTED.</td>
<td colspan="3"></td>
<td colspan="18">Authorized U.S. Government Representative</td>
<td></td>
<td colspan="6">Date</td>
<td colspan="2"></td>
</tr>
</tbody>
</table>

# SECTION A 

**Solicitation/contract form, JSC Form 1429**

**a.1 TABLE OF CONTENTS**

SECTION A ‑ Solicitation/contract form, JSC Form 1429

a.1 table of contents

SECTION B -- SUPPLIES OR SEVICES AND PRICE/COSTS

B.1 pricing

SECTION C -- statement of work

c.1 SORCE statement of work

C.2 SIRTF Statement of Work

SECTION D - RESERVED

SECTION E ‑ reserved

SECTION F ‑ DELIVERIES OR PERFORMANCE

F.1 COMPLETION OF WORK

F.2 reserved

F.3 performance requirements

SECTION G ‑ CONTRACT ADMINISTRATION DATA

G.1 SUBMISSION OF idiq invoices

SECTION H ‑ RESERVED

SECTION I -- RESERVED

SeCTION J-- Attachments

J.1 sorce Milestone Payment Schedule

J.1 sirtf Milestone Payment Schedule

# SECTION B

**SUPPLIES OR SEVICES AND PRICE/COSTS**

#### **b.1 pricing**

#### **clin 001 -- SORCE pre-launch sevices and launch & early orbit support**

#### Lockheed Martin, hereinafter referred to as Contractor, shall provide the SORCE Mission Pre-launch Services and Launch and Early Orbit Support specified in Section C1 of this Delivery Order. The Pre-launch Services and Launch and Early Orbit Support will be provided on a firm-fixed price basis. A proficiency metric of 0.991 is established for a maximum sixty (60) day Launch Early Orbit Support in accordance with delivery requirements consistent with prime contract NAS9-98100 and as further specified in paragraph F.3. Performance below this standard for a given month will result in a 10% reduction in the price associated with the maximum sixty (60) day SORCE Launch Early Orbit Support. However, Contractor shall not be penalized for loss of passes or data due to NISN communication errors, or Spacecraft related conflicts and errors, or Force Majeure. Force Majeure as it relates to this clause is defined as an unforeseeable or irresistible event that renders the obligation impossible to perform due to any cause beyond Contractor control and not occasioned by Contractor negligence or fault. Such causes shall be conclusively deemed to include, without limitation, (1) acts of God or of the public enemy, (2) acts of the Government in either its sovereign or contractual capacity, (3) fires, (4) floods, (5) epidemics, (6) quarantine restrictions, (7) strikes, (8) freight embargoes, and (9) unusually severe weather. Additionally, and as a means to provide incentive for the provider of services, performance above a proficiency level of .992 for the maximum sixty (60) day SORCE Launch Early Orbit Support will result in a 10% increase in the monthly payment. The following schedules display the firm-fixed price, with performance incentives as authorized under this Delivery Order. 

  --------------------------------------------------------- -------------
  Firm-Fixed Price Meeting Proficiency Standard .991        \$273,946

  Firm-Fixed Price Exceeding Proficiency Standard .992      \$301,341

  Firm-Fixed Price Below Proficiency Standard .991          \$246,552

  Amount Authorized                                         \$273,946
  --------------------------------------------------------- -------------

Payments shall be made in accordance with the milestones schedule
Attachment J.1.

#### **clin 002 --SORCE mission on-orbit operations - Base Period**

Contractor shall provide the SORCE Mission On-Orbit Operations specified
in Section C1 of this Delivery Order. SORCE Mission On-Orbit Operations
shall be provided on a firm-fixed price per pass basis per the following
schedule:

  --------------------------------------------------------- -------------
  Estimated Passes                                          11

  Price/pass                                                \$542

  Amount Authorized                                         \$5,962
  --------------------------------------------------------- -------------

Payments shall be on a monthly basis during the base period of the DO as
specified in paragraph F.1 completion of work.

#### **clin 003 -- sorce mission on-orbit operations -- option One (1)**

If this option period is awarded, Contractor shall provide the SORCE
Mission On-Orbit Operations specified in Section C1 of this Delivery
Order. SORCE Mission On-Orbit Operations shall be provided on a
firm-fixed price per pass basis per the following schedule:

  --------------------------------------------------------- -------------
  Estimated Passes                                          12

  Price/pass                                                \$542

  Amount Authorized                                         \$0
  --------------------------------------------------------- -------------

Payments shall be on a monthly basis during the base period of the DO as
specified in paragraph F.1 completion of work.

#### **clin 004 -- sorce mission on-orbit operations -- option Two (2)**

####  {#section-1}

If this option period is awarded, Contractor shall provide the SORCE
Mission On-Orbit Operations specified in Section C1 of this Delivery
Order. SORCE Mission On-Orbit Operations shall be provided on a
firm-fixed price per pass basis per the following schedule:

  --------------------------------------------------------- -------------
  Estimated Passes                                          12

  Price/pass                                                \$542

  Amount Authorized                                         \$0
  --------------------------------------------------------- -------------

Payments shall be on a monthly basis during the base period of the DO as
specified in paragraph F.1 completion of work.

####  {#section-2}

#### **clin 005 -- sorce mission on-orbit operations -- option Three (3)**

####  {#section-3}

If this option period is awarded, Contractor shall provide the SORCE
Mission On-Orbit Operations specified in Section C1 of this Delivery
Order. SORCE Mission On-Orbit Operations shall be provided on a
firm-fixed price per pass basis per the following schedule:

  --------------------------------------------------------- -------------
  Estimated Passes                                          12

  Price/pass                                                \$542

  Amount Authorized                                         \$0
  --------------------------------------------------------- -------------

Payments shall be on a monthly basis during the base period of the DO as
specified in paragraph F.1 completion of work.

####  {#section-4}

#### **clin 006 -- sorce mission on-orbit operations -- option Four (4)**

If this option period is awarded, Contractor shall provide the SORCE
Mission On-Orbit Operations specified in Section C1 of this Delivery
Order. SORCE Mission On-Orbit Operations shall be provided on a
firm-fixed price per pass basis per the following schedule:

  --------------------------------------------------------- -------------
  Estimated Passes                                          14

  Price/pass                                                \$542

  Amount Authorized                                         \$0
  --------------------------------------------------------- -------------

Payments shall be on a monthly basis during the base period of the DO as
specified in paragraph F.1 completion of work.

#  {#section-5}

#### **clin 007 -- sirtf pre-launch sevices and launch & early orbit support**

# Contractor shall provide the sirtf Mission Pre-launch Services and Launch and Early Orbit Support specified in Section C2 of this Delivery Order. The SIRTF Pre-launch Services and Launch and Early Orbit Support shall be provided on a firm-fixed price basis in the amount of \$159,809. 

**CLIN 008 --** **SITE** **SECURITY** **ENGINEERING SUPPORT**

Contractor shall provide engineering services in support of the
requirements presented in Section C.1 SORCE SOW paragraph 4.1.1, and
Section C.2 SIRTF SOW paragraph 2.0, associated with NASA Procedures and
Guidelines -- Security of Information Technology. Up to a maximum of 500
hours shall be provided as required under this Delivery Order and shall
be provided on a firm-fixed price per hour basis. Engineering Support
provided under this CLIN is for Satellite Applications Centre (SAC)
labor only. Any additional Contractor Labor required to ensure that all
interfaces and data processing equipment supporting the SORCE/SIRTF
missions conform to NPG 2810.1 shall require additional funding and
authorization from the Goddard Space Flight Center (GSFC) Contracting
Officer. [31]{.underline}

+-----------------+----------------+----------------+----------------+
| Engineering     | ##             | Total Hours    | Total Cost     |
| Support         | # Per Hour FFP |                |                |
+-----------------+----------------+----------------+----------------+
|                 | \$115.00       | 500            | \$57,500       |
+-----------------+----------------+----------------+----------------+

####   {#section-6}

# SECTION C

# statement of work

#  {#section-7}

# C.1 SORCE Statement of Work

# C.2 SIRTF Statement of Work

#   {#section-8}

# SECTION C.1

# SORCE statement of work

# 1.0 Introduction

CONTRACTOR shall provide ground station communications support for the
SORCE mission in accordance with the following requirements through an
IDIQ subcontract arrangement with Satellite Applications Centre (SAC).
Detailed technical requirements will be contained in the following
documents:

-   SORCE PSLA

-   SORCE Radio Frequency Interface Control Document. (RFICD)

-   SORCE Mission Operations Center (MOC) External Interfaces Control
    Document (MEICD)

Implementation of technical requirements contained in the above
documents shall require additional technical detail to be jointly
developed by CONTRACTOR and the SORCE Project. The requirements are
included in Section 4.0 of this Statement of Work (SOW).

# 2.0 SAC Background

SAC owns a commercial ground station that provides low cost
communications services supporting telemetry, tracking, and command
(TT&C) of LEO, MEO and GEO spacecraft. SAC schedules, maintains, and
operates their ground station to support their customers' TT&C
requirements. Customers interface to the SAC ground station via a
Diginet 64Kbps circuit that may be expanded up to 2Mbps, and pay for the
use of the ground station on a per pass basis.

# 3.0 SAC SORCE Support Overview

SAC shall provide nominal, backup, and contingency RF services for the
SORCE mission. The SAC station located in Pretoria/Hartebeesthoek, South
Africa shall provide nominal SORCE support.

SAC shall be responsible for ensuring ground station readiness in
support of the SORCE mission requirements as defined in the applicable
SORCE documentation. Section 4.0 details the tasks necessary to
successfully support the SORCE mission.

# 4.0 Tasks To Be Performed

The tasks to be performed under this SOW are comprised of the,
pre-launch, launch and early orbit post-launch phase and on-orbit
operations.

### **4.1** **Pre-launch**

###  {#section-9}

#### 4.1.1 Interface Definition

####  {#section-10}

This SOW covers only the SORCE-specific interfaces between SAC and the
SORCE Ground Segment. SAC shall be responsible for internal interface
management and control between all elements of the SAC ground station.
Insight into the implementation and status of SAC internal interfaces
shall be provided to the SORCE Ground Segment Manager and the NASA
Program Manager for review on an as-needed basis. In addition, all
interfaces and data processing equipment that support the SORCE mission
will conform to NPG 2810.1 for ADP and NASA/CSOC security standards. SAC
will assist CSOC in the development and implementation of all required
plans, tests, demonstrations, risk and mitigation analysis, reporting
and documentation associated with NPG 2810.1

#### 4.1.1.1 SORCE MOC External ICD

SAC shall provide inputs to the SORCE Mission Operations Center (MOC)
External ICD (MEICD) that will be developed by SORCE personnel. This ICD
shall define the details of all data and voice interfaces between the
MOC and SAC required for SORCE mission support, and specify any SAC or
MOC data processing requirements necessary to support those interfaces.
This ICD shall also specify SAC baseband command and telemetry
processing requirements related to the transfer of command and telemetry
data between the MOC and spacecraft.

#### 4.1.1.2 Radio Frequency ICD (RFICD)

SAC shall provide inputs to the SORCE Spacecraft to Ground Segment ICD
that will be developed by SORCE personnel. This document shall specify
the details of the interfaces between the SORCE spacecraft and the SAC
ground station. The focus of this document is on the characteristics of
the RF link between the spacecraft and the SAC ground station, including
CCSDS protocols, data format, and modulation/coding schemes.

#### 4.1.2 Testing

SAC shall support SORCE personnel in their performance of testing
necessary to verify SAC ground station compatibility and readiness for
the SORCE mission.

#### 4.1.2.1 SAC-to-MOC Testing

SAC shall support SORCE mission personnel in the definition and
execution of tests to verify all data interfaces between the SORCE MOC
and the SAC ground station. These interfaces shall be specified in the
MEICD. SAC-to-MOC testing shall include formal interface verification
during MOC systems testing and acceptance testing. SAC shall provide
inputs to and reviews of the Mission Readiness Test Plan (MRTP)
document, which defines the requirements, implementation, and schedule
for ground system readiness testing for the SORCE mission.

#### 4.1.2.2 SORCE RF Compatibility Testing 

> SAC shall provide standard RF compatibility test equipment to the
> SORCE mission. SAC shall support the development of the test plan and
> schedule that is developed by SORCE project personnel. SAC shall
> deliver a report of test results to the SORCE project.

#### 4.1.2.3 Mission End-to-End Testing

SAC shall support End-to-End data flow testing between the MOC and the
SAC ground station, as specified in the SORCE MRTP. Each test will be
billed as an actual cost per pass. For purpose of budgeting, a total of
10 tests are priced.

#### 4.1.3 Operations Planning

SAC shall support the development of a SORCE Network Operations Support
Plan (NOSP) that defines the operational procedures between SAC and the
SORCE Ground Segment. The plan, which will be developed by SORCE
personnel, shall include a description of the nominal, backup, and
contingency pass scheduling process, conflict resolution and SORCE
mission priority (vs. other missions supported by SAC), ground station
maintenance & operations, technical support (on and off-shift), and
points of contact.

SAC shall provide inputs to and fully support the development of the
SORCE Operations Concept and the SORCE Flight Operations Handbook. These
documents are developed by SORCE mission personnel and may include
operational procedures, details of the mission planning process, as well
as post-launch coordination processes and a description of the SORCE
mission operations organization.

SAC shall participate (by telecom) in scheduled Mission Operations
Working Group meetings to define operations requirements and support the
development of operations plans for SORCE.

Post-launch, SAC shall continue to support these meetings to review
operations status and revise operations procedures or methods as
required.

#### 4.1.4 Mission Simulation Support

SAC shall participate in up to two end-to-end SORCE mission rehearsals
and two launch rehearsals. This support shall include personnel,
facility, system support, and SAC ground station. Each test shall be
billed as an actual price per pass.

#### 4.1.5 Meetings, Reviews, Travel

SAC shall participate in project meetings and working groups necessary
to perform tasks described in this SOW. It is expected that much of the
meeting support will be accomplished through telecom. The Ground Network
Manager and the Customer Service Representatives will likewise
participate.

SAC shall support the following SORCE Project reviews via Telecom.

-   SORCE Ground Segment Critical Design Review

-   SORCE Launch Readiness Review

#### **4.2 Launch and Early-Orbit**

SAC shall support SORCE launch countdown operations with readiness
status reports as requested by the SORCE Ground Segment Manager.

In addition to the Routine Mission Support services described above, SAC
shall provide the following additional support during the first 48 hours
after launch:

-   24 hour manning of the SAC ground station.

-   Up to 22 contacts per day may be scheduled based on station
    availability.

    Details of the support requirements for launch & early orbit will be
    detailed in the SORCE Network Operations Support Plan. SAC shall
    support the development of this document with appropriate inputs and
    review.

The post-launch checkout of the SORCE spacecraft and payload will
proceed in five stages. The requirements for space-to-ground support
differ with each stage and will continue to evolve until the actual
launch of the spacecraft. SAC may provide the requested passes per day
during this mission phase with the remaining passes per day during
Launch & Early-Orbit operations being provided by NASA GN assets.

Stage 1 - Launch Day. This period covers solar array deployment and
initialization of the spacecraft. All contacts provided by a combination
of the SAC ground station or NASA GN with a maximum elevation above 10
degrees shall be scheduled. As a note, the NASA Space Network will also
be used to provide support between GN contacts, for the first 16 hours
after launch.

#### • Up to 22 passes via GN Support, averaging 10 minutes in duration

Stage 2 - from Launch +1 day to Launch + 7 days. This period covers the
commissioning of the spacecraft. Desired communications support is for
one uplink/downlink session of at least 8 minutes for every orbit. The
space-to-ground communications requirements for this stage can be met
using a combination of the SAC ground station, NASA GN, and Space
Network. For planning purposes, assume the following:

#### • Up to 11 passes per day via GN Support, averaging 10 minutes in duration

Stage 3 - from Launch + 8 days to Launch + 14 days. The period covers
the initial checkout of the spacecraft. Desired communications support
is for six uplink/downlink sessions of at least 8 minutes in duration
spaced relatively evenly throughout the day (i.e., every two orbits).
Here too the requirements can be met through a combination of SAC, NASA
GN, and Space Network. Assume the following for planning purposes:

#### • Up to 6 passes per day via GN Support, averaging 10 minutes in duration

Stage 4 - starting at Launch + 15 days and running for a period of from
two to five weeks. This will be a period of low activity while the
spacecraft outgases prior to activating the science instruments. Desired
communications support is for three uplink/downlink sessions of at least
8 minutes in duration within the period 6 am to 12 midnights, Mountain
Time (GMT minus 7). For planning purposes, assume:

#### • Up to 3 passes per day via GN Support, averaging 10 minutes in duration

Stage 5 - begins at the end of Stage 4 and runs for a period of 7 days.
Instrument initialization. Desire is for one contact per orbit, with
each contact a minimum of eight minutes in duration. Here too the
requirements can be met through a combination of SAC, NASA GN and Space
Network

#### • Up to 11 passes per day via GN Support, averaging 10 minutes in duration

Stage 6 - begins at the end of Stage 5 and runs for a period of 7 days.
Instrument checkout. Desired is for six contacts per day of eight
minutes or more in duration, spaced approximately four hours apart.

#### • Up to 6 passes per day via GN Support, averaging 10 minutes in duration

###  **4.3** **Normal Mission Operations**

After the 6-9 week launch and early-orbit phase is complete, the
spacecraft will transition to routine operations. Minimum required
downlink time per day would be 16 minutes, with 20 minutes of link time
per day desired. Passes will be preferentially scheduled during the
hours of 8 am to 12 midnights, Mountain Time (GMT minus 7). Only GN
Support resources will be used for routine on-orbit operations.

The SAC shall support the following generic scheduling rules:

1.  SAC shall provide one proficiency pass per month

2.  The antenna shall have a minimum G/T of 16dB/K and a minimum EIRP of
    80dBm.

3.  Each contact shall have a minimum of 8 minutes above a 10-degree
    horizon mask

4.  All contacts shall occur between 8am and 12 midnight Mountain time.

### 4.3.1 Routine Mission Support

The current SORCE launch date is November 30, 2002, with nominal mission
duration of 60 months. SAC shall provide RF communications support for
the entire on-orbit mission.

###  {#section-11}

### 4.3.1.1 Ground Station Maintenance & Operations

SAC shall operate and maintain the ground station used for SORCE mission
support for the duration of the SORCE mission.

SAC shall ensure that any ground station maintenance activities are
performed in a non-interference basis with routine SORCE mission
support. SAC shall provide a 24-hour technical support.

### 4.3.1.2 Pass Scheduling

Data Services shall be scheduled and coordinated between SAC Ground
Station and the Wallops Orbital Tracking Information System -- (WOTIS).
Note: CSOC plans to migrate the WOTIS function to a new Data Services
Management Center. This change will impact the operational interface due
to changes in IP addresses.

Services Operations shall be coordinated with WOTIS. Schedule conflicts
for the data services shall be resolved through WOTIS based on mission
priority guidelines provided by NASA and CSOC. Schedule confirmation
shall be provided by WOTIS to SAC prior to the provision of the Data
Services by SAC. The subcontractor shall accommodate all scheduling
requests.

Ground station status reports shall be provided by SAC both in real-time
(during a pass) and post pass to the WOTIS as well as the SORCE and
other space flight projects MOC.

Weekly activity reports shall be provided in accordance with current
procedures. Station discrepancy reports shall be provided to CSOC using
the CSOC-provided CDS Notifier System.

Station personnel shall also participate in regularly scheduled planning
and status meetings between NASA, CSOC, and other commercial service
providers.

4.3.1.3 Pass Support

SAC shall provide support on an as needed basis during the Normal
Mission Operations phase. The NASA site located in Wallops Island,
Virginia, and the University of Chile site located in Santiago, Chile
shall provide nominal SORCE support. The SAC ground station located in
Hartebeesthoek, South Africa, shall be utilized on a periodical basis to
maintain proficiency and be used as a contingency. For clarification,
the overall "GN Support" for the SORCE mission will come from a
combination of SAC, NASA Ground Network resources, and University of
Chile.

### **4.4 Uplink/Downlink Characterization**

Uplink: S-band, 16kHz subcarrier, 2000 bits per second,
Polarization=RHCP, Carrier modulation=PM (mod index 1.0), Subcarrier
modulation=BPSK, Baseband data format=NRZ-L, CCSDS telecommand format
with CCSDS randomization and COP-1 protocol.

Downlink: S-band, Baseband only, Information rate 3.0 Msymbols per
second, Carrier modulation=BPSK, Baseband data format=NRZ-M, CCSDS VCDUs
with Reed-Solomon (255, 223) coding, CCSDS randomization plus
convolutional (R=1/2, k=7) coding, for a total downlink rate of 1.5
Mbits/second.

The SN downlink has the same coding as above, however the symbol rate is
8 kbps, (4 kbps, information bits).

Real-time: There will be fourteen virtual channels. Two (VC-0 and 1)
will be for real-time data and must be forwarded directly to the MOC in
real time. The real-time link between SAC and GSFC shall be a minimum of
128 Kbps. The SORCE mission requires the capability to sort and extract
VCDUs (CCSDS Telemetry) from the downlink in real time. VC-0 & 1 shall
be real-time housekeeping data, VC-16 is the critical spacecraft bus
events from stored memory. VC-0 & 1 shall have the priority 1 (highest)
real-time to the Mission Operations Center (MOC). VC-16 shall be sent
priority 2 (medium) over the real-time link to the MOC. The CCSDS
processing system shall monitor and report any missing VCDUs during the
down-link to the MOC in real-time. This results in the MOC commanding
for a retransmit of the missing VCDUs.

Playback: Ten virtual channels (VC 14 through 23) will carry playback
data. Playback data may be buffered at the ground station and
transferred to the MOC post-pass. The other two virtual channels will
contain data only and may be discarded at the ground station. The
maximum amount of data to be dumped and recorded at the site is 90
Mbytes. The data is transferred to Goddard Space Flight Center (GSFC) in
Greenbelt, Maryland within 10 hours of receipt.

#### **4.5 Operations Coordination**

SAC shall interface with the SORCE Mission Operations Manager or his/her
designee at the MOC for day-to-day coordination required for routine
SORCE mission support.

SAC shall participate in periodic telecom or face-to-face meetings to
resolve operational or technical issues related to SORCE ground station
support post-launch.

SAC shall support the continued maintenance of SORCE operational
documentation for the duration of the SORCE mission.

All mission related correspondence between SAC and the SORCE project
will include the NASA Project Manager and CSOC Customer Service
Representative.

### 4.5.1 Roles and Responsibilities

The Ground Network (GN) Manager provides:

-   Coordination of SAC's site conformance to NPG 2810.1 security
    standards

-   Coordination of Compatibility testing with mission support
    requirement

-   Coordination to ensure SAC meets all requirements of CSOC-DRAFT- GN
    Management Plan

The Customer Service Representative (CSR) provides:

-   
-   

Coordination of mission support requirements with the SORCE program,
CSOC personnel and SAC

SAC provides:

-   Coordination in response to supported missions

-   Compliance to all activities detailed in the Task Order

-   Review and comments to CSOC-DRAFT- GN Management Plan

###  {#section-12}

### **4.6 Contingency Support**

SAC shall provide on-call support for SORCE mission and spacecraft
anomaly resolution and data quality problems. This support may include
manned support of the ground station, additional ground station contacts
(both pre-scheduled and emergency call-up) from SAC and other
operational support or technical investigations as requested by the
SORCE Mission Operations Manager.

# SECTION C.2

# sirtf statement of work 

#  {#section-13}

## **1.0 Introduction/Background**

CONTRACTOR shall provide spacecraft tracking and telemetry support for
the Space Infrared Telescope Facility (SIRTF) mission in accordance with
the following requirements through an IDIQ subcontract arrangement with
Satellite Applications Centre (SAC). The SIRTF follows a flight path
that does not rise over a Deep Space Network site until nearly 4 hours
after launch. The present launch date and time is January 9, 2003, at
approximately 1530 UTC from Cape Kennedy. The window of opportunity to
launch extends daily through March 11, 2003. There is one launch
opportunity each day occurring approximately 4 minutes earlier than the
launch time of the previous day.

The second engine cut off occurs approximately 700 seconds after launch.
The spacecraft receivers are powered on at launch and remain on
throughout the mission. The spacecraft transmitter is powered on by
stored sequence and will be timed to coincide with the initial
acquisition.

In the event of a serious anomaly following separation from the launch
vehicle, the SIRTF Observatory will enter what is known as safe mode. 
In safe mode, the Observatory\'s +Z axis (the normal to the solar
panels) is maintained within 1 degree of the sunline while the
Observatory rotates about this axis at a rate of one revolution every
two hours.  The Observatory continuously downlinks telemetry through its
Low Gain Antennas (LGAs) at a rate of 40 bps while it is rotating.  The
LGAs, which are boresighted along the +Y and -Y Observatory axes, each
have an effective Field-of-View (FOV) of 120 degrees (60-degree half
cone angle).  Therefore, during every 2-hour revolution the
SIRTF-to-Ground station vector will be contained within the LGA FOVs for
as much as 80 minutes (two communication periods of 40 minutes each,
with each period separated by 40 minutes where no communications are
possible).

#  {#section-14}

## **2.0 SIRTF Support Overview**

> SAC shall:

1\. Track and acquire the SIRTF spacecraft telemetry as soon as possible
after launch, with acquisition of signal no later than one-half hour
after launch. Tracking will continue until successful acquisition of
signal at the DSN Madrid Deep Space Communications Complex (MDSCC).
Nominal acquisition at MDSCC will be approximately 3 hours and 45
minutes after launch. Thus, the requirement is to track the spacecraft
for a minimum of 4 hours, or until MDSCC has a successful acquisition
and Hartebeesthoek has been released from support, whichever is longer,
but in no case will extend beyond 11hours unless specifically requested
and agreed upon by both parties. Staffing should be adequate to
accommodate all launch opportunities.

2.  Provide CCSDS telemetry frames to the Advanced Multi-mission
    Operations System (AMMOS) at Jet Propulsion Laboratory in Pasadena,
    California in real time. Record the data in case of a real-time
    communications outage, and for post-pass delivery to JPL. Deliver
    bits to AMMOS in the event that the frames do not Reed-Solomon
    decode. Details of SIRTF link parameters, telemetry format, and
    ephemeris follow.

3.  All interfaces and data processing equipment that support the SIRTF
    mission will conform to NPG 2810.1 for ADP and NASA/CSOC security
    standards. SAC will assist CSOC in the development and
    implementation of all required plans, tests, demonstrations, risk
    and mitigation analysis, reporting and documentation associated with
    NPG 2810.1

> Note: The requirement is for telemetry delivery to JPL only. There is
> no requirement for an uplink capability for either metric data or
> command purposes. Uplink (command) parameters are included below for
> completeness only.

3.  SIRTF Requirements

    1.  Telecommunications Link Parameters

> LGA, Gain 6.5 dBic transmit, 6.0 dBic receive
>
> Range from earth to a minimum altitude of 60,000 km
>
> (Rise at Madrid/DSN is slightly under 60,000 km about 3.5 hours after
> launch)
>
> Transmitter Power 13.8 watts, 4.7 dB of losses between the output of
> the SSPA and the transmit LGA

Note: Signal level at rise is expected to be 3-5 dB lower. At 6 degs
elevation the S/C is 103 degs off bore-site.

3.2 Uplink Parameters (For Information Purposes Only)

Frequency 7161.156636 MHz

Modulation PCM(NRZ-L)/PSK/PM

Subcarrier Frequency 16 KHz

Subcarrier Type Sinewave

> Coding BCH (Bose-Chaudhari- Hocquenghem)

Data rate 7.8125 bps

Modulation index 0.91 radians

####  Polarization RCP

3.3 Downlink Parameters

> Frequency 8413.641975 MHz
>
> Modulation PCM(NRZ-L)/BPSK/PM
>
> Subcarrier frequency 25 KHz
>
> Subcarrier Type Squarewave
>
> Coding Convolutional (7, 1/2)
>
> Reed-Solomon (255, 223) interleaving depth=5
>
> Data rates 2.2 Kbps
>
> 40 bps (emergency mode)
>
> Modulation index 1.39 radians (2.2 Kbps)
>
> 0.98 radians (40 bps)
>
> Polarization RCP

##  {#section-15}

3.4 Overall Telemetry Format

> SIRTF uses the downlink telemetry format specified in this section in
> all phases of its mission. This format conforms to the standard of the
> Consultative Committee for Space Data Systems (CCSDS) as specified in
> CCSDS Telemetry Channel Coding, CCSDS-101.0-B-2, and Packet Telemetry,
> CCSDS-102.0-B-2, with exceptions as noted.
>
> Variable length packets are placed within fixed length transfer
> frames. A transfer frame is the equivalent of a Virtual Channel Data
> Unit (VCDU). The transfer frames are Reed-Solomon encoded to form
> Reed-Solomon codeblocks. A Reed-Solomon codeblock is the equivalent of
> a Coded Virtual Channel Data Unit (CVCDU). A synchronization marker is
> prefixed to each codeblock forming the equivalent of a Channel Access
> Data Unit (CADU) and the entire bit stream is then convolutionally
> encoded into a symbol stream for modulation in the downlink RF signal.
>
> Transfer frames are Reed-Solomon encoded using the Berlekamp (dual
> basis) code with an interleave depth of 5. The code is shortened from
> the standard RS(255, 223) code to a RS(252, 220) code using 120 bits
> of virtual zero fill (not transmitted by the spacecraft) which are
> used by the decode process to fill out the codeblock to the standard.
> This results in a Reed-Solomon codeblock with a total length of 10080
> bits (8800 bits of transfer frame, and 1280 bits of Reed-Solomon check
> symbols).
>
> Each Reed-Solomon codeblock is prefixed with a synchronization marker.
> This 32-bit marker aids the receiving network in finding the frame
> boundaries. The specific bit pattern in hex is **1ACFFC1D**. The
> synchronization marker is not included in the Reed-Solomon encoding or
> decoding process. Figure 1 gives the format for a Reed-Solomon
> Codeblock.

![](media/image1.wmf){width="6.495138888888889in"
height="1.770138888888889in"}

###### *Figure 1 - Reed Solomon Codeblock Format*

The connection vectors for the convolutional code are as follows:

C1= 171 Octal (1111001 binary)

C2= Complement of 133 Octal (complement of 1011011 binary)

# SECTION D

**reserved**

#  {#section-16}

# SECTION E

**reserved**

# SECTION F

**deliveries and performance**

#### **F.1 COMPLETION OF WORK**

#### The period of performance for this delivery order is as follows: 

CLIN 001 SORCE Pre-launch Services and

####  Launch & Early Orbit Support ATP -- 01/31/03

CLIN 002 SORCE Mission Operations - Base Period 02/01/03 - 12/31/03

CLIN 003 SORCE Mission Operations - Option 1 1/1/04 - 12/31/04

CLIN 004 SORCE Mission Operations - Option 2 1/1/05 - 12/31/05

CLIN 005 SORCE Mission Operations - Option 3 1/1/06 - 12/31/06

CLIN 006 SORCE Mission Operations - Option 4 1/1/07- 2/29/08

CLIN 007 SIRTF Pre-launch Services and

####  Launch & Early Orbit Support ATP - 1/09/03 Launch Day

CLIN 008 SAC Security Engineering Support ATP - 1/09/03

#### **F.2 reserved**

#### **F.3 performance requirements**

Performance requirements are as specified in Ground Network data
Services Factory Service Agreement B.2.2.1.

# SECTION G

**CONTRACT ADMINISTRATION DATA**

#### **G.1 SUBMISSION OF IDIQ INVOICES**

Invoices shall be prepared and submitted in quadruplicate unless
otherwise specified. Invoices shall contain the following information as
applicable: contract and order number, description of supplies or
services, quantities, unit prices, and extended totals. Invoices shall
be submitted monthly to the following per specific requirements of the
Delivery Order.

NASA Johnson Space Center

Attn: BN/ Contracting Officer

2101 NASA Rd. 1

SECTION H

**RESERVED**

# SECTION I

**RESERVED**

#  {#section-17}

#   {#section-18 .unnumbered}

#  {#section-19}

# SECTION J

**attachments**

####  {#section-20}

**J.1 sorce Milestone Payment Schedule**

**J.2 sirtf Milestone Payment Schedule**

**attachment J.1**

**sorce Milestone Payment Schedule**

  --------------- ----------------------- --------------------- ----------- -----------
  **SORCE CLIN 1                                                            
  milestone                                                                 
  payment                                                                   
  schedule**                                                                

  **Milestone**   **Contractual           **Contractual Date**  **Payment   
                  Condition**                                   Amount**    

  P01             Completion of project   10 days After Receipt 20%         \$54,789
                  management plan for     of Order (ARO)                    
                  SORCE                                                     

  P02             Delivery of system      45 days ARO           15%         \$41.092
                  specification                                             
                  (excluding ATP)                                           

  P03             Completion of final     7 months ARO          15%         \$41,092
                  acceptance testing                                        

  P04             Completion of Mission   Launch -- 2 weeks     10%         \$27,395
                  Preparation and                                           
                  Qualification/Testing                                     

  P05             Completion of LEOP      Launch + 60 days      40%         \$109,578
                  Phase                                                     
  --------------- ----------------------- --------------------- ----------- -----------

**attachment J.2**

**sirtf Milestone Payment Schedule**

  --------------- ---------------------- --------------------- ----------- ----------
  **Sirtf CLIN**                                                           
  **7**                                                                    
  **milestone                                                              
  payment                                                                  
  schedule**                                                               

  **Milestone**   **Contractual          **Contractual Date**  **Payment   
                  Condition**                                  Amount**    

  P01             Completion of SIRTF    10 days After Receipt 20%         \$31,962
                  project management     of Order (ARO)                    
                  plan                                                     

  P02             Delivery of            45 days ARO           15%         \$23,971
                  specification                                            
                  (excluding ATP)                                          

  P05             Completion of final    7 months ARO          25%         \$39,952
                  acceptance testing                                       

  P06             Completion of Mission  Launch -- 2 months    20%         \$31,962
                  Preparation and                                          
                  Qualification                                            

  P07             Completion of Launch   Launch + 2 weeks      20%         \$31,962
                  support and provision                                    
                  of report                                                
  --------------- ---------------------- --------------------- ----------- ----------