<table style="width:100%;">
<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: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 1%" />
<col style="width: 1%" />
<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: 1%" />
<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: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 0%" />
<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: 0%" />
<col style="width: 10%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 4%" />
<col style="width: 0%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="18"><p>National Aeronautics and Space Administration</p>
<p>Lyndon B. Johnson Space Center</p>
<p>Houston, TX 77058</p></td>
<td colspan="34"><strong>ORDER FOR SUPPLIES OR SERVICES</strong></td>
<td colspan="7">Page 1 of 36</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="15">1. PURCHASE ORDER NO.</td>
<td colspan="10">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">281</td>
<td colspan="10">12/21/01</td>
<td colspan="36">Certified for National Defense under DPAS (15 CFR 700)
DO C9</td>
</tr>
<tr class="even">
<td colspan="25">3. ISSUING OFFICE</td>
<td colspan="14">4. SHIP TO:</td>
<td colspan="22">Transportation Officer, Building 421</td>
</tr>
<tr class="odd">
<td colspan="25">NASA Johnson Space Center, Houston, TX 77058</td>
<td colspan="13"></td>
<td colspan="23"><p>NASA Johnson Space Center</p>
<p>Houston, TX 77058</p></td>
</tr>
<tr class="even">
<td colspan="8">Attn:</td>
<td colspan="17">Wayne Buckley</td>
<td colspan="13"></td>
<td colspan="23">Mark For: Accountable Property</td>
</tr>
<tr class="odd">
<td colspan="11">Org./Buyer:</td>
<td colspan="14">BN/59</td>
<td colspan="13"></td>
<td colspan="23"></td>
</tr>
<tr class="even">
<td colspan="7">Tel. No.:</td>
<td colspan="8">281-483-5588</td>
<td>Fax:</td>
<td colspan="9">281-483-7890</td>
<td colspan="13"></td>
<td colspan="8">Purchase Order No:</td>
<td colspan="15">281</td>
</tr>
<tr class="odd">
<td colspan="15">5. CONTRACTOR</td>
<td colspan="2">TIN:</td>
<td colspan="8"></td>
<td colspan="36"><ol start="6" type="1">
<li><p>DELIVER ON OR BEFORE:</p></li>
</ol></td>
</tr>
<tr class="even">
<td colspan="25"><p>Lockheed Martin Space Operations Company</p>
<p>Attn: Kathy Collins</p>
<p>595 Gemini Avenue</p>
<p>Houston, TX 77058</p></td>
<td colspan="36">01/01/2002 – 12/31/2002</td>
</tr>
<tr class="odd">
<td colspan="9">PHONE:</td>
<td colspan="16">281-853-3049</td>
<td colspan="16">F.O.B. POINT:</td>
<td colspan="20"></td>
</tr>
<tr class="even">
<td colspan="25">7. CONFIRMING ORDER:</td>
<td colspan="36">8. BILLING ADDRESS:</td>
</tr>
<tr class="odd">
<td colspan="10">FROM:</td>
<td colspan="12"></td>
<td colspan="3"></td>
<td colspan="36"><blockquote>
<p>NASA Johnson Space Center</p>
</blockquote></td>
</tr>
<tr class="even">
<td colspan="10">TO:</td>
<td colspan="13"></td>
<td colspan="2"></td>
<td colspan="36">Attn: LF231/Funding &amp; Commercial Accounting
Section</td>
</tr>
<tr class="odd">
<td colspan="10">DATE:</td>
<td colspan="11"></td>
<td colspan="4"></td>
<td colspan="36">Houston, TX 77058</td>
</tr>
<tr class="even">
<td colspan="25"></td>
<td colspan="20">Purchase Order No.:</td>
<td colspan="11"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="25"></td>
<td colspan="20"></td>
<td colspan="16"></td>
</tr>
<tr class="even">
<td colspan="61">9. TYPE OF ORDER:</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="2"></td>
<td colspan="12">PURCHASE: REFERENCE</td>
<td colspan="10"></td>
<td colspan="3"></td>
<td colspan="2">X</td>
<td colspan="31">DELIVERY: Except for the Terms and Conditions of
Purchase</td>
</tr>
<tr class="even">
<td colspan="4"></td>
<td colspan="21"></td>
<td colspan="36">Order listed on the following page, this delivery order
is subject to</td>
</tr>
<tr class="odd">
<td colspan="26">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="even">
<td colspan="26">on this order.</td>
<td colspan="22">terms and conditions of contract number:</td>
<td colspan="9"></td>
<td colspan="4"></td>
</tr>
<tr class="odd">
<td colspan="26"></td>
<td colspan="22"></td>
<td colspan="13"></td>
</tr>
<tr class="even">
<td colspan="29">10. DISCOUNT TERMS:</td>
<td colspan="32">11.</td>
</tr>
<tr class="odd">
<td colspan="29"></td>
<td colspan="6">BY</td>
<td colspan="14"><mark>Original signed by: Wayne buckle</mark></td>
<td colspan="2"><mark></mark></td>
<td colspan="8"><mark>12/21/2001</mark></td>
<td colspan="2"><mark></mark></td>
</tr>
<tr class="even">
<td colspan="29"></td>
<td colspan="6"></td>
<td colspan="14">CONTRACTING OFFICER</td>
<td></td>
<td colspan="5">DATE</td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="61">12. SCHEDULE</td>
</tr>
<tr class="even">
<td colspan="5">ITEM<br />
NO.</td>
<td colspan="27">DESCRIPTION</td>
<td colspan="8">QUANTITY<br />
ORDERED</td>
<td colspan="3">UNIT</td>
<td colspan="4">UNIT<br />
PRICE</td>
<td colspan="7">AMOUNT</td>
<td colspan="7">QUANTITY<br />
ACCEPTED</td>
</tr>
<tr class="odd">
<td colspan="5">1</td>
<td colspan="27"><strong>Southern Hemisphere Data Services</strong></td>
<td colspan="8">1</td>
<td colspan="3">Lot</td>
<td colspan="4"><strong>$654,368</strong></td>
<td colspan="7"><strong>$654,368</strong></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="47">13. FOR JSC INTERNAL USE ONLY:</td>
<td colspan="14">14. Total</td>
</tr>
<tr class="odd">
<td colspan="14">PURCHASE REQUEST NO.:</td>
<td colspan="7"></td>
<td colspan="3"></td>
<td colspan="9">COMP.</td>
<td colspan="3"></td>
<td colspan="4">PART.</td>
<td colspan="4">PPC:</td>
<td colspan="3"></td>
<td colspan="14"></td>
</tr>
<tr class="even">
<td colspan="14">APPROPRIATION DATA:</td>
<td colspan="33"></td>
<td colspan="14"><p><strong>$ 11,459,262</strong></p>
<p id="section" class="heading"></p></td>
</tr>
<tr class="odd">
<td colspan="14">ACCOUNTING CODE:</td>
<td colspan="33"></td>
<td colspan="14"></td>
</tr>
<tr class="even">
<td colspan="14">REISSUE TO:</td>
<td colspan="33"></td>
<td colspan="14"></td>
</tr>
<tr class="odd">
<td colspan="61">15. QUANTITIES IN “QUANTITY ACCEPTED” COLUMN HAVE
BEEN:</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="4"></td>
<td colspan="6">INSPECTED</td>
<td></td>
<td colspan="6">ACCEPTED</td>
<td></td>
<td colspan="41">RECEIVED</td>
</tr>
<tr class="odd">
<td colspan="27">TO CONFORM TO THE CONTRACT.</td>
<td colspan="4">BY</td>
<td colspan="21"></td>
<td></td>
<td colspan="6"></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="34">ACCEPTANCE WILL BE AT JSC UNLESS OTHERWISE NOTED.</td>
<td colspan="3"></td>
<td colspan="15">Authorized U.S. Government Representative</td>
<td></td>
<td colspan="5">Date</td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="42">JSC Form 1429 (Rev June 26, 2000) (MS Word August
1995)</td>
<td colspan="18"><strong>CONTRACTOR</strong></td>
<td></td>
</tr>
</tbody>
</table>

**Delivery Order Summary**

This Delivery Order (DO) is for the purpose of providing Santiago Ground
Station Communications support to the Southern Hemisphere for the period
January 1, 2002 through December 31, 2002. Santiago Ground Station
Communications support will be provided through a Directed Task Order
(DTO) to the University of Chile under CSOC IDIQ Contract GB57454B20.

The Santiago Ground site will be supporting NASA and NASA cooperative
missions such as ProSEDS, TDRS-I, TDRS-J, HESSI, and SORCE. This DO also
includes hours for data services to satisfy additional requirements as
they become apparent, engineering support services, WAN (128 kbps
communications) services, and Mission Unique Equipment (MUE) and
logistics.

# 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 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 -- Special Contract Requirements

H.1 logistics managment

SECTION I -- RESERVED

SeCTION J-- RESERVED

# SECTION B

**SUPPLIES OR SEVICES AND PRICE/COSTS**

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

####  {#section-1}

Contractor shall provide Santiago Ground Station Support Services
specified in Section C, Statement of Work (SOW) of this Delivery Order
(DO). Santiago Ground Station Support Services are provided through an
Indefinite Delivery, Indefinite Quantity (IDIQ) contract with the
Univesidad de Chile (U of C). In this scenario, a price per minute (PPM)
is defined for the mission support detailed in the Section C, Statement
of Work (SOW), which is estimated at 2 hours per day per quarter, or
182.5 hours of mission support per quarter or 43800 minutes per year, as
a minimum, during the period January 01, 2002 through December 31, 2002.
Additional support services beyond the two (2) hours shall be priced in
accordance with the established IDIQ rates with the U of C.

Also included in the Delivery Order (DO) are hours to purchase
additional data services to satisfy additional requirements as they
become apparent, engineering support services, WAN (128 kbps
communications) services, one ISDN (128kbps), 256kbps Internet, and
Mission Unique Equipment (MUE) and logistics. The price per hour (PPH)
scenario covers engineering support services not included in the PPM. It
is typical that the number of engineering support service hours is
approximately one (1) for every four (4) mission support hours.

Pricing is based on a price per minute (PPM) using established IDIQ
rates under U of C IDIQ contract GB57454B20. Additional support services
beyond the two (2) hours shall be priced in accordance with the
established IDIQ rates with the U of C. The firm-fixed price (Adjusted
for performance as outlined in paragraph B.2) is \$654,368. NASA will
reimburse Contractor in four (4) equal (quarterly) payments as follows:

  ------------------------------------------------ ----------------------
  March 15, 2002                                   \$163,592

  June 15, 2002                                    \$163,592

  September 15, 2002                               \$163,592

  December 15, 2002                                \$163,592

  **Total Amount Authorized**                      \$654,368
  ------------------------------------------------ ----------------------

**B.2 Performance Incentives and Penalties**

The performance metrics specified in the Section C, SOW paragraph 8.0,
shall be measured and evaluated on a monthly basis. The following
performance incentives and penalties shall apply:

  ----------------- ------------------- ----------------- -----------------------
  **Metric -- for   **Calculation**     **Performance     **Incentive/Penalty**
  all Antennae**                        Requirement**     

  Service           One minus (Minutes  0.992             10% above/below applied
  Availability &    scheduled minus                       to the monthly
  Proficiency       minutes                               remuneration
                    successfully                          
                    provided)/divided                     
                    by Minutes                            
                    scheduled                             
  ----------------- ------------------- ----------------- -----------------------

> Availability Calculation:
>
> 45 minutes scheduled. 45 minutes provided.
>
> 1-(45-45)/45 = 1.000
>
> In case of the following event, the pass shall not be included in the
> calculation of the monthly proficiency metrics. Hence, the Contractor
> shall not be penalized for losses of passes or due to:

-   NISN Communication errors

-   Force Majeure -- An unforeseeable or irresistible event that renders
    the obligation impossible to perform due to any cause beyond
    University of Chile's control and not occasioned by University of
    Chile's negligence or fault. Such causes shall be conclusively
    deemed to include, without limitation, war; warlike operation;
    insurrection; riot; fire; explosion; accident; material control
    regulations or orders; act of God; act of the public enemy; failure
    of or delay in transportation; inability to procure materials after
    due and timely diligence; epidemic; quarantine restriction; and
    labor trouble causing cessation, slowdown or interruption of work.

-   Spacecraft related conflicts and errors

-   Service unavailability resulting from commercial electrical power
    and communications outages, or any other reason non-attributable to
    the University of Chile, will not be taken into consideration for
    the calculation of the University of Chile service availability

# SECTION C

# statement of work

CONTRACTOR shall provide Data Services in accordance with the following
specification through an IDIQ subcontract arrangement with the
Universidad de Chile (U of C) hear after referred to as Santiago. This
Statement of Work (SOW) specifies the tasks to be performed and approach
to be used by Santiago in providing ground station communications
support to NASA.

#  {#section-2}

# 1.0 Background

> The University of Chile has provided TT&C services to NASA space
> missions since 1959, as the Chilean Cooperating Agency in the
> implementation of the Space Cooperation Agreement entered into by
> representation of both the Chilean International Affairs Office and
> the US Foreign Office.
>
> Up until 1989 the University operated the NASA Santiago STDN Station.
> From 1989 onwards, when the NASA property at the station was
> transferred to the University, it continued to provide TT&C services
> to NASA and also other space agencies, from its ground facility,
> located 38 km North of Santiago. In addition, the University has
> collaborated with the NASA Space Geodesy Program with GPS, SLR and
> VLBI measurements at the Santiago Station and GPS and SLR measurements
> at Eastern Island, where the GPS data collection has been
> uninterrupted.

## **2.0 Introduction**

> The Santiago Ground site will be supporting NASA and NASA-cooperative
> missions such as ProSEDS, TDRS-I, TDRS-J, HESSI, and SORCE through the
> CSOC Indefinite Delivery, Indefinite Quantity (IDIQ) contract. In this
> scenario, a price per minute (PPM) is defined for the mission support
> detailed in the SOW, which is estimated to be in the order of 2 hours
> per day per quarter, or 182.5 hours of mission support per quarter or
> 43800 minutes per year, as a minimum, during the period January 01,
> 2002 through December 31, 2002.
>
> Also included under the Directed Task Order (DTO) are hours to
> purchase additional data services to satisfy additional requirements
> as they become apparent, engineering support services, WAN (128 kbps
> communications) services, one ISDN (128kbps), 256kbps Internet, and
> Mission Unique Equipment (MUE) and logistics. The price per hour (PPH)
> scenario covers engineering support services not included in the PPM.
> It is typical that the number of engineering support service hours is
> approximately one (1) for every four (4) mission support hours.
>
> It is also understood that the missions in this scenario may change,
> be substituted for, or cancelled prior to the actual usage of the
> hours mentioned above. Also the operations staff shall be available 7
> days per week, 11 hours per day basis. The regular work hours of the
> operations staff run from 08:30 through 19:30 Local Time. This
> continued availability of both communications and shift staffing will
> continue to make possible the immediate response of the Santiago
> Station in case of call for spacecraft emergency support requirements
> This service for emergency support requires a call to the Station
> Operations 15 minutes ahead of actual desired support during regular
> work hours, and 3 hours in advance during other times.

## **3.0 Mission Data and Engineering Support Services**

> The data services consist of telemetry, tracking and command for
> launch and post-launch checkout phase. As a contingency TT&C station
> for on-orbit spacecraft (i.e. NOAA Wallops CDA backup), in addition to
> mission support services, Santiago supports storage of spacecraft
> health and safety maintenance data.
>
> Overall management and technical planning services for systems
> implementation are: programs reviews, systems engineering,
> mission/proficiency testing, tracking data handling and storage,
> operations coordination and scheduling, launch and early orbit
> support, science data, command and housekeeping data processing,
> documentation and security (NPG2810.1). Additional turnkey services
> include management, personnel, facilities, administration, reporting,
> communications, transportation, equipment, scheduling, overtime
> charges, testing, data accumulation/storage/delivery, implementation
> engineering/testing/training support, and non real time systems
> engineering.

# 4.0 Station Support Capabilities 

> The missions services shall be supported with the capabilities
> existing at the Santiago Station that are described in Table 1 below.
> These independent systems technically allow supporting three S-Band
> missions simultaneously if required. This availability is crucial to
> handle peak workloads and for resolving the priority conflicts that
> would arise otherwise.

+---------+-------+-------+-----+-----+----------+------+-----------+
| **CAPAB | **FR  | *     | **  | *   | **POLARI | **C  | **APPL    |
| ILITY** | EQ.** | *ANTE | EIR | *G/ | ZATION** | ONTR | ICATION** |
|         |       | NNA** | P** | T** |          | OL** |           |
|         | **M   |       |     |     |          |      |           |
|         | Hz.** | **T   | **( | **  |          | *    |           |
|         |       | YPE** | dBw | (dB |          | *MOD |           |
|         |       |       | )** | /ºK |          | ES** |           |
|         |       |       |     | )** |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| VHF     | 136 - | U     | \-  | -   | Lin X, Y | Ma   | Telemetry |
| RECEIVE | 138   | nique | \-- | 8.0 |          | nual |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | S    |           |
|         |       |       |     |     |          | lave |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| VHF     | 147 - | Yagi  | 56  | \-  | Lin X, Y | Ma   | Command   |
| T       | 150   | Array | (   | \-- |          | nual |           |
| RANSMIT |       |       | AM) |     | RHC, LHC |      |           |
|         |       |       |     |     |          | S    |           |
|         |       |       | 59  |     |          | lave |           |
|         |       |       | (   |     |          |      |           |
|         |       |       | PM) |     |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| L-BAND  | 1690  | 7     | \-  | 17  | RHC, LHC | Ma   | Telemetry |
|         | -1710 | Meter | \-- | .25 |          | nual |           |
| RECEIVE |       |       |     |     | RHC, LHC |      |           |
|         | 2     | Para  | \-  | \   |          | S    |           |
| S-BAND  | 200 - | bolic | \-- | >19 |          | lave |           |
| RCV     | 2300  |       |     |     |          |      |           |
|         |       |       |     |     |          | Pro  |           |
|         |       |       |     |     |          | gram |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2     | 7     | 52  | \-  | RHC, LHC | Ma   | Command   |
|         | 025 - | Meter | -58 | \-- |          | nual |           |
| T       | 2120  |       |     |     |          |      | Telemetry |
| RANSMIT |       | Para  |     |     |          | S    |           |
|         |       | bolic |     |     |          | lave | Tracking  |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  |       | \-  | 19  | RHC, LHC |      |           |
|         | -2300 |       | \-- |     |          |      |           |
| RECEIVE |       |       |     |     |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  | 9     | \-  | 2   | RHC, LHC | Ma   | Telemetry |
|         | -2300 | Meter | \-- | 3.0 |          | nual |           |
| RECEIVE |       |       |     |     | RHC, LHC |      | Command   |
|         | 2025  | Para  | 40  | \-  |          | S    |           |
| S-BAND  | -2120 | bolic | -85 | \-- |          | lave | Tracking  |
|         |       |       |     |     |          |      |           |
| T       |       |       |     |     |          | Pro  |           |
| RANSMIT |       |       |     |     |          | gram |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | A    |           |
|         |       |       |     |     |          | utot |           |
|         |       |       |     |     |          | rack |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  | 11    | \-  | \   | RHC, LHC | Ma   | Telemetry |
|         | -2350 | Meter | \-- | >25 |          | nual |           |
| RECEIVE |       |       |     |     |          |      |           |
|         |       | Para  |     |     |          | S    |           |
|         |       | bolic |     |     |          | lave |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | Pro  |           |
|         |       |       |     |     |          | gram |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  | 12    | \-  | \   | RHC, LHC | Ma   | Telemetry |
|         | -2300 | Meter | \-- | >26 |          | nual |           |
| RECEIVE |       |       |     |     |          |      |           |
|         |       |       |     |     |          | S    |           |
|         |       |       |     |     |          | lave |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | A    |           |
|         |       |       |     |     |          | utot |           |
|         |       |       |     |     |          | rack |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| X-BAND  | 8000  | Para  | \-  | 37  | RHC or   | Pro  |           |
|         | -8600 | bolic | \-- |     | LHC      | gram |           |
| RECEIVE |       |       |     |     |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+

> Note: The 7m and 12m systems can be configured to conduct ranging
> using a two-antenna set-up.

##### **Table 1**

##### **Summary of Transmit and Receive Capabilities**

## **5.0 Communications**

> Santiago shall keep the dedicated, point-to-point, 128 kbps, Intelsat
> Business System (IBS) type communications service between the tracking
> station facility -- located 38 km north of the city of Santiago -- and
> the GSFC. This is an existing communications service that has
> exhibited excellent availability. The local ground segment is
> connected via fiber optics from the station to the city of Santiago.

The existing service is normally configured for:

-   One 16 kbps voice channel

-   One 100 kbps telemetry and command data channel

> The data channel supports commands from the GSFC to the station,
> command echoes from the station to GSFC, acquisition data from GSFC to
> station and metric data from station to GSFC.
>
> Santiago shall flow data on the GSFC-AGO communication service using
> the 4800 bit-blocks NASA protocol; the radiometric data shall be
> provided in the NASA Universal Tracking Data Format (UTDF). The data
> provided by Santiago shall be IP encapsulated and de-encapsulated at
> the GSFC, using existing conversion devices.
>
> A 128 kbps ISDN BRI service will be leased as a backup to the above
> IBS system. This service will be transported via a radio link between
> the Station and the telecommunications service provider. A 256 kbps
> connection to the Internet will be available for the operations and
> administrative matters related to this Task Order.

**6.0 Scheduling, Work Hours and Resolution of Scheduling Conflicts.**

> Scheduling of the support to the Santiago Station shall be
> accomplished via e-mail to:
>
> <gago@ncc-comm.gsfc.nasa.gov>. During CY2002, scheduling of the ground
> station will be moved from the Wallops Scheduling Group to the White
> Sands Data Services and Management Center.
>
> The normal work hours of the Santiago station are shown in the
> following table:

+-------------+----------+------------------+-------------------------+
|             | ## Lo    | **UTC Normal     | **UTC Daylight Saving** |
|             | cal Time | Time**           |                         |
|             |          |                  | **2^nd^ Saturday        |
|             |          | **2^nd^ Saturday | October**               |
|             |          | March**          |                         |
|             |          |                  | **2^ne^ Saturday        |
|             |          | **2^nd^ Saturday | March**                 |
|             |          | October**        |                         |
+-------------+----------+------------------+-------------------------+
| **OFFICE    | 08:00 -- | 12:00 -- 22:00   | 11:00 -- 21:00          |
| HOURS**     | 18:00    |                  |                         |
|             |          |                  |                         |
| Mond        |          |                  |                         |
| ay-Thursday |          |                  |                         |
+-------------+----------+------------------+-------------------------+
| **SHIFT     | 08:00 -- | 12:00 -- 24:00   | 11:00 -- 23:00          |
| HOURS**     | 20:00    |                  |                         |
|             |          |                  |                         |
| Mo          |          |                  |                         |
| nday-Sunday |          |                  |                         |
+-------------+----------+------------------+-------------------------+
| **SUPPORT   | 08:30 -- | 12:30 -- 23:30   | 11:30 -- 22:30          |
| HOURS**     | 19:30    |                  |                         |
|             |          |                  |                         |
| Mo          |          |                  |                         |
| nday-Sunday |          |                  |                         |
+-------------+----------+------------------+-------------------------+

> Coordination of emergency support, or support outside the above hours,
> requires a minimum call of 15 minutes ahead of actual desired support
> during regular work hours, and 3 hours in advance during other times.
>
> The Santiago Station also provides LEOP and/or orbital support to
> space missions from other foreign organizations such as ESA, NASDA,
> ISAS, CNES, and others. The following general criteria will be applied
> in the resolution of scheduling conflicts:
>
> A. Priorities

-   Priority 1. Declared emergency of orbiting spacecraft.

-   Priority 2. Launch phase support and emergency needs of newly
    launched spacecraft.

-   Priority 3. Routine support for spacecraft in orbit.

-   Priority 4. Rehearsals, simulations and test activities.

> B. If technically feasible and if acceptable to the parties,
> simultaneous support will be provided.
>
> .
>
> C. The best efforts will be made by all parties during the priority
> coordination phase attempting the resolution of the problem.
>
> D. LEOP Support:
>
> For LEOP support, NASA/CSOC is required to specify the launch date,
> for which the first priority will be assigned, unless the University
> of Chile has previously committed that date for another support. In
> the event that the launch date is changed, the first priority will be
> maintained, unless the University had previously committed that date
> for supporting another mission.
>
> E. Routine Support.
>
> For routine support, upon receipt of the weekly schedule, the Station
> will notify NASA/CSOC, and the other party, of any potential support
> conflict, in an attempt to either reschedule the use of the preferred
> transmit and receive antennas, or the time of the activities, to avoid
> the conflict If the conflict cannot be resolved to the satisfaction of
> all parties, the Station will make the best possible decision on which
> activity to support and will immediately notify the parties.

**7.0 Reporting Requirements**

> Santiago shall also provide the mission-specific reports that may be
> established/required by the Project. Santiago shall provide the
> following reports specified in the respective NASA documents:
>
> Network Control Center and Spaceflight Tracking and Data Network
> Station Interface Procedures Document Number 532-SIP-NCC/STDN:

-   Station Equipment Status Report per Para 24.4

-   Operations Event Reporting

-   Pass Summary Report per Para 22.15

-   Tracking Operation Report per Para 22.16

-   Telemetry Summary Report per Para 22.18

-   Preliminary Monthly Report

> Spaceflight Tracking and Data Network Test and Simulation Support Plan
> document number 530-NOP-STDN/TS

-   Test Results Report per Para 6-17.

> (Also per 532-SIP-NCC/STDN Para 22.13)

**8.0 Performance Metrics**

> **8.1 Service Availability and Proficiency**
>
> The University of Chile shall provide availability and proficiency of
> services at not less than 0.992

2.  **Data Availability**

> The University of Chile shall provide not less than 0.992 of the
> scheduled data for each spacecraft per month. Command and spacecraft
> housekeeping data is transferred between the spacecraft and the NISN
> telecommunications interface without delay (real-time).

3.  **Mean time to Restore Services**

> The University of Chile shall provide the capability to have a mean
> time to restore service (MTTRS) of no more than 1.5 hours measured
> over a contiguous 10,000- hour interval.

# SECTION D

**reserved**

#  {#section-3}

# SECTION E

**reserved**

# SECTION F

**deliveries and performance**

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

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

January 1, 2002 through December 31, 2002

#### **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 quarterly to the following per specific requirements of the
Delivery Order.

NASA Johnson Space Center

Attn: BN/ Contracting Officer

2101 NASA Rd. 1

Houston, TX 77058

# SECTION H

**special contract requirements**

**H.1 Logistics Management**

Many of the systems existing at the Santiago station are not commercial
off-the-shelf items and were specially built in accordance with NASA
specifications. Some spare parts for these systems are available through
the NASA Logistics Depot only. Because these systems will still be
required to provide the support under Section C - Statement of Work,
limited logistical support from the NASA Logistics Depot is deemed
mandatory. This support is specific to operations and maintenance of the
Santiago Station to support the mission services identified within
Section C - Statement of Work. The items that will be provided through
CSOC are limited to \$80,000 per year, and are considered unique to the
Santiago Station, unavailable from common commercial manufactures and/or
no longer in production. Funding for these items exist in the completion
form contract and is not included in this DO

Some of the missions to be supported under this DO may require that
unique equipment be made available by NASA to the University to provide
TT&C support services. Mission unique equipment is not identified nor is
cost for mission unique equipment provided in this DO. Unique equipment
may include but not be limited to, command encoders, formatters, VLDS
recorders, test equipment and communications equipment.

Logistical support will be requested through the established, existing
mechanisms. It is understood that the CSOC cognizant Customer Service
Representative (CSR) will review and approve or disapprove the requests.

#   {#section-4}

#  {#section-5}

# SECTION I

**RESERVED**

#  {#section-6}

#   {#section-7 .unnumbered}

#  {#section-8}

# SECTION J

**RESERVED**

**Basis of Estimate**

This DO to provide ground station communications support to the southern
hemisphere is based on the following Directed Task Order CSOC4SAN-002
contemplated under the current IDIQ contract GB57454B20 with U of C.

**SANTIAGO**

**University of Chile**

**Ground Network Services**

**Table of Contents:**

Task Order and Award Template

Section A: Task Order Schedule and Pricing

Section B: Instructions, Terms and Conditions, Provisions and Special
Provisions

Section C: Statement of Work

<table style="width:100%;">
<colgroup>
<col style="width: 13%" />
<col style="width: 4%" />
<col style="width: 0%" />
<col style="width: 9%" />
<col style="width: 1%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 11%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="23"><h1 id="task-order-and-award">Task Order and
Award</h1></td>
</tr>
<tr class="even">
<td colspan="3"><p>Contract Number</p>
<p>GB57454B20</p></td>
<td colspan="6"><blockquote>
<p>Solicitation Number</p>
<p>N/A</p>
</blockquote></td>
<td colspan="9"><p>Task Order Type</p>
<p><u>_X</u> Directed (DTO)</p>
<p>Competitive (CTO)</p>
<p>__ Study (STO)</p>
<p>__ Engineering Services (ESTO)</p>
<p>__ Mission Unique (MUTO)</p></td>
<td colspan="3"><p>Date Issued</p>
<p>12-31-01</p></td>
<td colspan="2"><p>Task Order Number</p>
<p>CSOC4SAN-002</p></td>
</tr>
<tr class="odd">
<td colspan="23"><p>Issued By:</p>
<p>Lockheed Martin/CSOC</p>
<p>595 Gemini Dr.</p>
<p>Houston, TX 77058</p></td>
</tr>
<tr class="even">
<td colspan="23">Task Order Contract Implementation Plan</td>
</tr>
<tr class="odd">
<td colspan="23">Provide concurrence to the Task Order Statement Of Work
and sign the Task Order and Award form in <u>original and copies</u> to
place specified above.</td>
</tr>
<tr class="even">
<td colspan="2" rowspan="2">For Information Call:</td>
<td colspan="6" rowspan="2"><p>Name:</p>
<p>Jim Christiansen</p></td>
<td colspan="9">Telephone: (No Collect Calls)</td>
<td colspan="6" rowspan="2"><p>E-mail Address:</p>
<p>jm.christiansen@csoconline.com</p></td>
</tr>
<tr class="odd">
<td colspan="4"><p>Area Code</p>
<p>281</p></td>
<td colspan="3"><p>Number:</p>
<p>853</p></td>
<td colspan="2"><p>Ext:</p>
<p>3299</p></td>
</tr>
<tr class="even">
<td colspan="23">Table of Contents</td>
</tr>
<tr class="odd">
<td>Cover Form</td>
<td colspan="9">Task Order and Award Form</td>
<td colspan="3">Page 2</td>
<td colspan="3"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="even">
<td>Section A</td>
<td colspan="9">Schedule and Pricing</td>
<td colspan="3">Pages 3-4</td>
<td colspan="3"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="odd">
<td rowspan="2">Section B</td>
<td colspan="9" rowspan="2">Instructions, Terms and Conditions,
Provisions and Special Provisions</td>
<td colspan="3" rowspan="2">Pages 5-6</td>
<td colspan="3"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="odd">
<td>Section C</td>
<td colspan="9">Statement of Work</td>
<td colspan="3">Pages 7-12</td>
<td colspan="3"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="3"></td>
<td colspan="3"></td>
<td colspan="6"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="23">Offer (Must be fully completed by ID/IQ Preferred
Provider)</td>
</tr>
<tr class="even">
<td colspan="5">Discount for Prompt Payment</td>
<td colspan="9"><p>10 Calendar Days</p>
<p>%</p></td>
<td colspan="6"><p>20 Calendar Days</p>
<p>%</p></td>
<td colspan="3"><p>30 Calendar Days</p>
<p>%</p></td>
</tr>
<tr class="odd">
<td colspan="14">Name and Address of Offeror:</td>
<td colspan="9"><p>Name and Title of Person Authorized to Sign</p>
<p>(Type or Print)</p></td>
</tr>
<tr class="even">
<td colspan="14">Telephone Number</td>
<td colspan="9"></td>
</tr>
<tr class="odd">
<td>Area Code</td>
<td colspan="3">Number</td>
<td colspan="3">Ext.</td>
<td colspan="11" rowspan="2">Signature</td>
<td colspan="5" rowspan="2">Offer Date:</td>
</tr>
<tr class="even">
<td></td>
<td colspan="3"></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="23">AWARD</td>
</tr>
<tr class="even">
<td colspan="7">Accepted as to Items Listed</td>
<td colspan="7">Amount</td>
<td colspan="9">Accounting and Appropriation</td>
</tr>
<tr class="odd">
<td colspan="11">Submit Invoices to Address Shown Above</td>
<td colspan="12">Administered By:</td>
</tr>
<tr class="even">
<td colspan="6">PAYMENT WILL BE MADE BY:</td>
<td colspan="13">Name of Contracting Officer (Type or Print)</td>
<td colspan="4">Award Date:</td>
</tr>
<tr class="odd">
<td colspan="23">Award will be made on this Form, or by other authorize
official written notice.</td>
</tr>
</tbody>
</table>

> SECTION A
>
> Task Order Schedule/Pricing

1.  **Introduction**

> The Santiago Ground Station Support Services are estimated to be
> approximately 2 hours per day per quarter, or 182.5 hours of mission
> support per quarter. The University of Chile shall support all
> missions discussed in the Directed Task Order Section C, Statement of
> Work (SOW) and shall comply with the SOW of the IDIQ contract
> GB57454B20. The pricing method will also allow CSOC to purchase
> additional hours of data services to satisfy additional requirements
> and it is understood that the missions in this scenario may change, be
> substituted for, or cancelled prior to the actual usage of the hours
> mentioned above. Additional support services beyond the two (2) hours
> shall be priced in accordance with the established IDIQ rates.
>
> In this scenario the existing Santiago GSFC 128 kbps communication
> service shall be retained for the entire year, as the prime
> communications link, and one ISDN BRI (128kbps) will be available as a
> backup during this period. Also, the station will provide a 256kbps
> access to the Internet. The operations staff shall be available 7 days
> per week, 11 hours per day basis for immediate response of the
> Santiago station in case of call for spacecraft emergency support or
> unforeseen support requirements.

# Schedule

> The period of performance for the Santiago Ground Station (AGO)
> Directed Task Order CSOC4SAN-002, for tracking, telemetry and command
> (TT&C) services is from January 1, 2002 to December 31, 2002.

2.  **Pricing**

> The pricing methodology for the Directed Task Order shall be price per
> minute (PPM), based on the established IDIQ rates (Reference: IDIQ
> contract GB57454B20 J-16 Pricing Schedule, Page B-2). The hours shall
> be categorized and reflect the same rates established in the IDIQ for
> telemetry, tracking, and command (TT&C) in real-time, standard replay
> and FTP replay scenarios. The price per hour (PPH) scenario covers
> engineering support services not included in the PPM.

#  Payment Schedule 

> CSOC will reimburse University of Chile in four (4) equal (quarterly)
> payments as follows (Adjusted for performance as outlined in section A
> paragraph 5.0):

-   March 31, 2002 \$123,375.00

-   June 30, 2002 \$123,375.00

-   September 30, 2002 \$123,375.00

-   December 31, 2002 \$123,375.00

4.  **Performance Incentives and Penalties**

> The performance metrics specified in the Directed Task Order, SOW
> Section 11.0, Performance Metrics shall be measured and evaluated on a
> monthly basis by CSOC. The following performance incentives and
> penalties shall apply:

  ----------------- ------------------- ----------------- -----------------------
  **Metric -- for   **Calculation**     **Performance     **Incentive/Penalty**
  all Antennae**                        Requirement**     

  Service           One minus (Minutes  0.992             10% above/below applied
  Availability &    scheduled minus                       to the monthly
  Proficiency       minutes                               remuneration
                    successfully                          
                    provided)/divided                     
                    by Minutes                            
                    scheduled                             
  ----------------- ------------------- ----------------- -----------------------

> Availability Calculation:
>
> 45 minutes scheduled. 45 minutes provided.
>
> 1-(45-45)/45 = 1.000
>
> In case of the following event, the pass shall not be included in the
> calculation of the monthly proficiency metrics. Hence, the University
> of Chile shall not be penalized for losses of passes or due to:

-   NISN Communication errors

-   Force Majeure -- An unforeseeable or irresistible event that renders
    the obligation impossible to perform due to any cause beyond
    University of Chile's control and not occasioned by University of
    Chile's negligence or fault. Such causes shall be conclusively
    deemed to include, without limitation, war; warlike operation;
    insurrection; riot; fire; explosion; accident; material control
    regulations or orders; act of God; act of the public enemy; failure
    of or delay in transportation; inability to procure materials after
    due and timely diligence; epidemic; quarantine restriction; and
    labor trouble causing cessation, slowdown or interruption of work.

-   Spacecraft related conflicts and errors

-   Service unavailability resulting from commercial electrical power
    and communications outages, or any other reason non-attributable to
    the University of Chile, will not be taken into consideration for
    the calculation of the University of Chile service availability

    SECTION B

> **Instructions, Terms and Conditions, Provisions and Special
> Provisions**

# 1.0 Terms and Conditions

> Contract terms and conditions of Directed Task Order CSOC3SAN-002 are
> established and bi-laterally agreed upon by the services provider and
> Lockheed Martin, in the Indefinite Delivery, Indefinite Quantity
> (ID/IQ) subcontract GB57454B20.

#   {#section-9}

**2.0 Special Provisions**

1.  The service provider shall provide Data Services and Engineering
    Support only as authorized by Task Order(s). Only the CSOC
    Purchasing Representative or a CSOC Technical Representative
    (designated in writing by the CSOC Purchasing Representative) may
    issue Task Orders. The service provider may incur costs under this
    contract in performance of Task Orders and Task Order Modifications
    issued in accordance with this provision. No other costs are
    authorized unless otherwise specified in the contract or expressly
    authorized by the CSOC Purchasing Representative or designee.

2.  The service provider shall provide acknowledgment of receipt of the
    Task Order to the CSOC Purchasing Representative or designee within
    two (2) calendar days after receipt of the Task Order.

3.  The CSOC Purchasing Representative may amend Task Orders in the same
    manner in which they were issued.

4.  In the event of a conflict between the requirements of the Task
    Order and the service provider's approved Implementation Plan, the
    Task Order shall prevail.

> 5\. The Buyer's Prime Contract NAS9-98100 has a base period of
> performance that runs through 31 December 2003 followed by an option
> period from 01 January 2004 through 31 December 2008. Should NASA/SOMO
> not exercise this Option Period within the NASA Prime Contract
> NAS9-98100, the Buyer shall have the right to assign this subcontract,
> inclusive of any unused services and/or options, and any GFP to NASA
> or a successor contractor for performance of the services and prices
> stated and provided herein.
>
> Further, at the direction of the Government, the Buyer may be required
> to assign or transfer the administration of the Prime Contract or any
> portion thereof, including Subcontracts, from the Buyer to NASA or
> another Government agency, or to another party, at any time during the
> performance of the contract including any option period(s). If the
> provisions of this Subcontract need to be modified to fit the new
> arrangement, the parties agree to negotiate such changes in good faith
> (with each other and with the new contracting party).

**SECTION C**

###### Statement of Work/Specifications

# 1.0 Background

> The University of Chile has provided TT&C services to NASA space
> missions since 1959, as the Chilean Cooperating Agency in the
> implementation of the Space Cooperation Agreement entered into by
> representation of both the Chilean International Affairs Office and
> the US Foreign Office.
>
> Up until 1989 the University operated the NASA Santiago STDN Station.
> From 1989 onwards, when the NASA property at the station was
> transferred to the University, it continued to provide TT&C services
> to NASA and also other space agencies, from its ground facility,
> located 38 km North of Santiago. In addition, the University has
> collaborated with the NASA Space Geodesy Program with GPS, SLR and
> VLBI measurements at the Santiago Station and GPS and SLR measurements
> at Eastern Island, where the GPS data collection has been
> uninterrupted.

## **2.0 Introduction**

> The Santiago Ground site will be supporting NASA and NASA-cooperative
> missions such as ProSEDS, TDRS-I, TDRS-J, HESSI, and SORCE through the
> CSOC Indefinite Delivery, Indefinite Quantity (IDIQ) contract. In this
> scenario, a price per minute (PPM) is defined for the mission support
> detailed in the SOW, which is estimated to be in the order of 2 hours
> per day per quarter, or 182.5 hours of mission support per quarter or
> 43800 minutes per year, as a minimum, during the period January 01,
> 2002 through December 31, 2002.
>
> Also included under the Directed Task Order (DTO) are hours to
> purchase additional data services to satisfy additional requirements
> as they become apparent, engineering support services, WAN (128 kbps
> communications) services, one ISDN (128kbps), 256kbps Internet, and
> Mission Unique Equipment (MUE) and logistics. The price per hour (PPH)
> scenario covers engineering support services not included in the PPM.
> It is typical that the number of engineering support service hours is
> approximately one (1) for every four (4) mission support hours.
>
> It is also understood that the missions in this scenario may change,
> be substituted for, or cancelled prior to the actual usage of the
> hours mentioned above. Also the operations staff shall be available 7
> days per week, 11 hours per day basis. The regular work hours of the
> operations staff run from 08:30 through 19:30 Local Time. This
> continued availability of both communications and shift staffing will
> continue to make possible the immediate response of the Santiago
> Station in case of call for spacecraft emergency support requirements
> This service for emergency support requires a call to the Station
> Operations 15 minutes ahead of actual desired support during regular
> work hours, and 3 hours in advance during other times.

## **3.0 Mission Data and Engineering Support Services**

> The data services consist of telemetry, tracking and command for
> launch and post-launch checkout phase. As a contingency TT&C station
> for on-orbit spacecraft (i.e. NOAA Wallops CDA backup), in addition to
> mission support services, Santiago supports storage of spacecraft
> health and safety maintenance data.
>
> Overall management and technical planning services for systems
> implementation are: programs reviews, systems engineering,
> mission/proficiency testing, tracking data handling and storage,
> operations coordination and scheduling, launch and early orbit
> support, science data, command and housekeeping data processing,
> documentation and security (NPG2810.1). Additional turnkey services
> include management, personnel, facilities, administration, reporting,
> communications, transportation, equipment, scheduling, overtime
> charges, testing, data accumulation/storage/delivery, implementation
> engineering/testing/training support, and non real time systems
> engineering.

# 4.0 Station Support Capabilities 

> The missions services shall be supported with the capabilities
> existing at the Santiago Station that are described in Table 1 below.
> These independent systems technically allow supporting three S-Band
> missions simultaneously if required. This availability is crucial to
> handle peak workloads and for resolving the priority conflicts that
> would arise otherwise.

+---------+-------+-------+-----+-----+----------+------+-----------+
| **CAPAB | **FR  | *     | **  | *   | **POLARI | **C  | **APPL    |
| ILITY** | EQ.** | *ANTE | EIR | *G/ | ZATION** | ONTR | ICATION** |
|         |       | NNA** | P** | T** |          | OL** |           |
|         | **M   |       |     |     |          |      |           |
|         | Hz.** | **T   | **( | **  |          | *    |           |
|         |       | YPE** | dBw | (dB |          | *MOD |           |
|         |       |       | )** | /ºK |          | ES** |           |
|         |       |       |     | )** |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| VHF     | 136 - | U     | \-  | -   | Lin X, Y | Ma   | Telemetry |
| RECEIVE | 138   | nique | \-- | 8.0 |          | nual |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | S    |           |
|         |       |       |     |     |          | lave |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| VHF     | 147 - | Yagi  | 56  | \-  | Lin X, Y | Ma   | Command   |
| T       | 150   | Array | (   | \-- |          | nual |           |
| RANSMIT |       |       | AM) |     | RHC, LHC |      |           |
|         |       |       |     |     |          | S    |           |
|         |       |       | 59  |     |          | lave |           |
|         |       |       | (   |     |          |      |           |
|         |       |       | PM) |     |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| L-BAND  | 1690  | 7     | \-  | 17  | RHC, LHC | Ma   | Telemetry |
|         | -1710 | Meter | \-- | .25 |          | nual |           |
| RECEIVE |       |       |     |     | RHC, LHC |      |           |
|         | 2     | Para  | \-  | \   |          | S    |           |
| S-BAND  | 200 - | bolic | \-- | >19 |          | lave |           |
| RCV     | 2300  |       |     |     |          |      |           |
|         |       |       |     |     |          | Pro  |           |
|         |       |       |     |     |          | gram |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2     | 7     | 52  | \-  | RHC, LHC | Ma   | Command   |
|         | 025 - | Meter | -58 | \-- |          | nual |           |
| T       | 2120  |       |     |     |          |      | Telemetry |
| RANSMIT |       | Para  |     |     |          | S    |           |
|         |       | bolic |     |     |          | lave | Tracking  |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  |       | \-  | 19  | RHC, LHC |      |           |
|         | -2300 |       | \-- |     |          |      |           |
| RECEIVE |       |       |     |     |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  | 9     | \-  | 2   | RHC, LHC | Ma   | Telemetry |
|         | -2300 | Meter | \-- | 3.0 |          | nual |           |
| RECEIVE |       |       |     |     | RHC, LHC |      | Command   |
|         | 2025  | Para  | 40  | \-  |          | S    |           |
| S-BAND  | -2120 | bolic | -85 | \-- |          | lave | Tracking  |
|         |       |       |     |     |          |      |           |
| T       |       |       |     |     |          | Pro  |           |
| RANSMIT |       |       |     |     |          | gram |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | A    |           |
|         |       |       |     |     |          | utot |           |
|         |       |       |     |     |          | rack |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  | 11    | \-  | \   | RHC, LHC | Ma   | Telemetry |
|         | -2350 | Meter | \-- | >25 |          | nual |           |
| RECEIVE |       |       |     |     |          |      |           |
|         |       | Para  |     |     |          | S    |           |
|         |       | bolic |     |     |          | lave |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | Pro  |           |
|         |       |       |     |     |          | gram |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| S-BAND  | 2200  | 12    | \-  | \   | RHC, LHC | Ma   | Telemetry |
|         | -2300 | Meter | \-- | >26 |          | nual |           |
| RECEIVE |       |       |     |     |          |      |           |
|         |       |       |     |     |          | S    |           |
|         |       |       |     |     |          | lave |           |
|         |       |       |     |     |          |      |           |
|         |       |       |     |     |          | A    |           |
|         |       |       |     |     |          | utot |           |
|         |       |       |     |     |          | rack |           |
+---------+-------+-------+-----+-----+----------+------+-----------+
| X-BAND  | 8000  | Para  | \-  | 37  | RHC or   | Pro  |           |
|         | -8600 | bolic | \-- |     | LHC      | gram |           |
| RECEIVE |       |       |     |     |          |      |           |
+---------+-------+-------+-----+-----+----------+------+-----------+

> Note: The 7m and 12m systems can be configured to conduct ranging
> using a two-antenna set-up.

##### **Table 1**

##### **Summary of Transmit and Receive Capabilities**

## **5.0 Communications**

> Santiago shall keep the dedicated, point-to-point, 128 kbps, Intelsat
> Business System (IBS) type communications service between the tracking
> station facility -- located 38 km north of the city of Santiago -- and
> the GSFC. This is an existing communications service that has
> exhibited excellent availability. The local ground segment is
> connected via fiber optics from the station to the city of Santiago.

The existing service is normally configured for:

-   One 16 kbps voice channel

-   One 100 kbps telemetry and command data channel

> The data channel supports commands from the GSFC to the station,
> command echoes from the station to GSFC, acquisition data from GSFC to
> station and metric data from station to GSFC.
>
> Santiago shall flow data on the GSFC-AGO communication service using
> the 4800 bit-blocks NASA protocol; the radiometric data shall be
> provided in the NASA Universal Tracking Data Format (UTDF). The data
> provided by Santiago shall be IP encapsulated and de-encapsulated at
> the GSFC, using existing conversion devices.
>
> A 128 kbps ISDN BRI service will be leased as a backup to the above
> IBS system. This service will be transported via a radio link between
> the Station and the telecommunications service provider. A 256 kbps
> connection to the Internet will be available for the operations and
> administrative matters related to this Task Order.

**6.0 Scheduling, Work Hours and Resolution of Scheduling Conflicts.**

> Scheduling of the support to the Santiago Station shall be
> accomplished via e-mail to:
>
> <gago@ncc-comm.gsfc.nasa.gov>. During CY2002, scheduling of the ground
> station will be moved from the Wallops Scheduling Group to the White
> Sands Data Services and Management Center.
>
> The normal work hours of the Santiago station are shown in the
> following table:

+-------------+----------+------------------+-------------------------+
|             | ## Lo    | **UTC Normal     | **UTC Daylight Saving** |
|             | cal Time | Time**           |                         |
|             |          |                  | **2^nd^ Saturday        |
|             |          | **2^nd^ Saturday | October**               |
|             |          | March**          |                         |
|             |          |                  | **2^ne^ Saturday        |
|             |          | **2^nd^ Saturday | March**                 |
|             |          | October**        |                         |
+-------------+----------+------------------+-------------------------+
| **OFFICE    | 08:00 -- | 12:00 -- 22:00   | 11:00 -- 21:00          |
| HOURS**     | 18:00    |                  |                         |
|             |          |                  |                         |
| Mond        |          |                  |                         |
| ay-Thursday |          |                  |                         |
+-------------+----------+------------------+-------------------------+
| **SHIFT     | 08:00 -- | 12:00 -- 24:00   | 11:00 -- 23:00          |
| HOURS**     | 20:00    |                  |                         |
|             |          |                  |                         |
| Mo          |          |                  |                         |
| nday-Sunday |          |                  |                         |
+-------------+----------+------------------+-------------------------+
| **SUPPORT   | 08:30 -- | 12:30 -- 23:30   | 11:30 -- 22:30          |
| HOURS**     | 19:30    |                  |                         |
|             |          |                  |                         |
| Mo          |          |                  |                         |
| nday-Sunday |          |                  |                         |
+-------------+----------+------------------+-------------------------+

> Coordination of emergency support, or support outside the above hours,
> requires a minimum call of 15 minutes ahead of actual desired support
> during regular work hours, and 3 hours in advance during other times.
>
> The Santiago Station also provides LEOP and/or orbital support to
> space missions from other foreign organizations such as ESA, NASDA,
> ISAS, CNES, and others. The following general criteria will be applied
> in the resolution of scheduling conflicts:
>
> A. Priorities

-   Priority 1. Declared emergency of orbiting spacecraft.

-   Priority 2. Launch phase support and emergency needs of newly
    launched spacecraft.

-   Priority 3. Routine support for spacecraft in orbit.

-   Priority 4. Rehearsals, simulations and test activities.

> B. If technically feasible and if acceptable to the parties,
> simultaneous support will be provided.
>
> .
>
> C. The best efforts will be made by all parties during the priority
> coordination phase attempting the resolution of the problem.
>
> D. LEOP Support:
>
> For LEOP support, NASA/CSOC is required to specify the launch date,
> for which the first priority will be assigned, unless the University
> of Chile has previously committed that date for another support. In
> the event that the launch date is changed, the first priority will be
> maintained, unless the University had previously committed that date
> for supporting another mission.
>
> E. Routine Support.
>
> For routine support, upon receipt of the weekly schedule, the Station
> will notify NASA/CSOC, and the other party, of any potential support
> conflict, in an attempt to either reschedule the use of the preferred
> transmit and receive antennas, or the time of the activities, to avoid
> the conflict If the conflict cannot be resolved to the satisfaction of
> all parties, the Station will make the best possible decision on which
> activity to support and will immediately notify the parties.

**7.0 Reporting Requirements**

> Santiago shall also provide the mission-specific reports that may be
> established/required by the Project. Santiago shall provide the
> following reports specified in the respective NASA documents:
>
> Network Control Center and Spaceflight Tracking and Data Network
> Station Interface Procedures Document Number 532-SIP-NCC/STDN:

-   Station Equipment Status Report per Para 24.4

-   Operations Event Reporting

-   Pass Summary Report per Para 22.15

-   Tracking Operation Report per Para 22.16

-   Telemetry Summary Report per Para 22.18

-   Preliminary Monthly Report

> Spaceflight Tracking and Data Network Test and Simulation Support Plan
> document number 530-NOP-STDN/TS

-   Test Results Report per Para 6-17.

> (Also per 532-SIP-NCC/STDN Para 22.13)

**8.0 Logistics Management**

> Many of the systems existing at the Santiago station are not
> commercial off-the-shelf items and were specially built in accordance
> with NASA specifications. Some spare parts for these systems are
> available through the NASA Logistics Depot only. Because these systems
> will still be required to provide the support under the DTO SOW,
> limited logistical support from the CSOC is deemed mandatory. This
> support is specific to operations and maintenance of the Santiago
> Station to support the mission services identified within this SOW.
> The items that will be purchased through the CSOC are limited to
> \$80,000 per year, are considered to be unique to the Santiago
> Station, and unavailable from common commercial manufacturers and/or
> no longer in production.
>
> Some of the missions to be supported under this DTO may require that
> unique equipment be made available by CSOC to the University to
> provide TT&C support services. Unique equipment may include but not be
> limited to, command encoders, formatters, and VLDS recorders, test
> equipment and communications equipment.
>
> Logistical support will be requested through the established, existing
> mechanisms. It is understood that the CSR representative will review
> and approve or disapprove the requests.

**9.0 Mission Cancellation and Failure**

> The University of Chile acknowledges that NASA may unilaterally cancel
> missions and that this cancellation would preclude the need for the
> data service support.
>
> It is also understood that with regard to this contingency, CSOC may
> at its sole discretion, be entitled to; 1) terminate this Task Order
> in its entirety with a maximum financial liability to CSOC through the
> current calendar quarter in which the effort is terminated; 2) delay
> the remaining data service requirement; 3) terminate the remaining
> data service requirement in its entirety; 4) substitute another
> mission; or, 5) assign the remaining data services requirements to
> another contractor.
>
> In the event this provision conflicts with any other subcontract term
> and condition, the University of Chile and CSOC agree that this
> provision shall prevail over any other subcontract clause, term or
> condition.

**10.0 Government Pre-Launch Delay**

> After the effective award date of the DTO, the University of Chile
> acknowledges that the NASA may, unilaterally delay any mission
> detailed in the statement of work. Such a delay may impact the
> scheduled mission.
>
> In the event of such delay, CSOC shall be entitled to delay
> commencement of the data services performance period by a period equal
> to the number of calendar days the planned mission is delayed.
> Further, should a Pre-Launch Delay occur, the University of Chile
> agrees that no additional compensation shall be paid by the CSOC.

**10.1 Exceptions**

> The University of Chile acknowledges that CSOC reserves the right to
> replace one of the missions or the entire mission set~~s~~ with other
> missions that require like typical support services, provided that the
> replacement missions would occur during the period of performance
> described within this SOW.

11. **Performance Metrics**

    1.  **Service Availability and Proficiency**

> The University of Chile shall provide availability and proficiency of
> services at not less than 0.992.

2.  **Data Availability**

> The University of Chile shall provide not less than 0.992 of the
> scheduled data for each spacecraft per month. Command and spacecraft
> housekeeping data is transferred between the spacecraft and the NISN
> telecommunications interface without delay (real-time).

3.  **Mean time to Restore Services**

> The University of Chile shall provide the capability to have a mean
> time to restore service (MTTRS) of no more than 1.5 hours measured
> over a contiguous 10,000-hour interval.

This page Intentionally left blank

**DISCLOSURE/ADMINISTRATIVE INFORMATION**

**5.1** **Unsolicited Provisions That Lockheed Martin Technology
Services Group Initiates**

**5.1.1 Lockheed Martin Technology Services Group Affiliation**

> If awarded a Delivery Order as a result of this proposal, LOCKHEED
> MARTIN SERVICES, INC., (whose ultimate parent company is the LOCKHEED
> MARTIN CORPORATION) shall be permitted to use any ultimately wholly
> owned subsidiary, division, or business unit of the LOCKHEED MARTIN
> CORPORATION to perform the requirements of this contract. It is
> understood and agreed that the above mentioned performance shall not
> be considered as a subcontract, but as a transfer between divisions or
> subsidiaries of the SUBCONTRACTOR, and that the allowability of cost
> shall be determined in accordance with FAR 31.205-26(e). Any such
> subsidiary, division, or business unit performing under this contract
> shall be doing so on behalf of LOCKHEED MARTIN SERVICES, INC., who
> shall retain total responsibility hereunder.

**5.2 Disclosure**

**5.2.1 LM21 Disclosure**

> LM21 Operating Excellence is a Corporate-wide initiative to drive
> productivity, continuous improvement, and cost reduction throughout
> Lockheed Martin. The focus of LM21 is to drive process capability to
> world-class levels, deliver on customer value, achieve lean processes
> with Six Sigma capability, and to realize significant operating cost
> reductions. LM21 is the umbrella initiative for all of our
> productivity improvement efforts, including Lean, Six Sigma, EPI, SPI,
> Shared Services, Global Supply Chain Management, and B2B. The benefits
> from these efforts will be realized over time and the cost
> impacts/benefits are incorporated into proposals as they become known.

2.  **Realigning for Customer Focus**

> On September 27, 1999, the Lockheed Martin Corporation announced a
> number of actions to improve customer satisfaction and operational
> efficiency. These include the realignment of the five former sectors
> into four broad business areas. This realignment is expected to
> streamline and flatten the organization. In addition, the corporation
> announced the decision to explore divestiture of certain non-core
> business in Aerospace Electronics, Control Systems, and Environmental
> Management. Outstanding proposals will be updated when the financial
> impact of these actins has been quantified.

###  {#section-10}

**5.2.3 Internal Restructuring Project -- ALC**

> On January 24, 2001, the management of Lockheed Martin Services, Inc.
> (LMSI) announced its intent to establish an internal restructuring
> project that involves the migration of Lockheed Martin Aircraft and
> Logistics Center business segments onto the LMSI common systems and
> the consolidation of G&A activities. The first step involved the
> conversion of ALC employee benefits and moving the employees of the
> ALC Businesses (including Kelly Aircraft Center) to the Cherry Hill
> Benefits and Payroll System in January 2001. The next step will be to
> integrate business development, human resources, financial, and
> administrative systems that will enable a single G&A by January 2002.
> The internal restructuring project savings are estimated to yield
> total net savings in excess of \$40 Million. The project cost will be
> amortized over a five-year period beginning in 2001. Negotiated
> proposals will be updated when the financial impact of this action has
> been quantified at that level.

4.  **Acquisition of OAO Corporation**

> On October 26, 2001, Lockheed Martin Services, Inc. (LMSI) and OAO
> Corporation announced the signing of a definitive agreement under
> which LMSI will acquire the outstanding stock of OAO. LMSI will
> combine OAO with one of its product lines, Lockheed Martin Information
> Support Services, to create a new organization within the LMSI
> Segment. The new company is positioned for continued growth in the
> rapidly expanding federal information technology market. The
> transaction is subject to government approvals, including review under
> the Hart-Scott-Rodino Antitrust Improvements Act and satisfaction of
> other customary conditions. It is expected to close before the end of
> 2001. We are currently working on developing organization and
> accounting structures within the LMSI Segment that will occur in 2002
> and forward in anticipation of a December 2001 anti-trust review
> approval. We are also reviewing the potential impact of this
> acquisition on allocations from the Lockheed Martin Technology
> Services Business Area to the business segments. Negotiated proposals
> will be updated when the financial impact of this action has been
> quantified at that level.

2.  **Points of Contact**

**5.3.1 Cognizant Administrative Contracting Officer (ACO)**

#  Ms. Anna Marie Cuccio (856) 722-7468

#  DACODCMD-RVOB

DCMD Lockheed Martin -- Delaware Valley

##### 199 Borton Landing Road, Bldg. 127-133

> Moorestown, NJ 08057-3095

**5.3.2 Cognizant DCAA Auditor**

> Houston Branch Office
>
> Attn: Mr. Joseph Cook, Branch Mgr (713) 948-3300
>
> 8876 Gulf Freeway Suite 500
>
> Houston, TX 77017-6544
>
> Email address: <dcaa-fao3521@dcaa.mil>

**5.3.3 Lockheed Martin Point of Contact**

> Kathy J. Collins, LMSOC Contracts Manager, (281) 853-3049
>
> Donald W. Crosby, Sr. Contract Administrator, (281) 853-3378
>
> 595 Gemini Avenue
>
> Houston, TX 77258