Document:

Exhibit 10.6

 

	
  

  	
   

  	
  Contract
  INM-CO/03-3723

  November 2003

  

 

CONTRACT

 

FOR

 

LAUNCH
SERVICES

 

BETWEEN

 

SEA LAUNCH LIMITED PARTNERSHIP

Acting through its General
Partner

SEA LAUNCH
COMPANY, L.L.C.

 

AND

 

INMARSAT
LIMITED

 

Proprietary
& Confidential

 

TABLE OF CONTENTS

 

	
  ARTICLE
  1 — DEFINITIONS

  	
  3

  
	
  ARTICLE 2 —
  CONTRACTUAL DOCUMENTS

  	
  7

  
	
  ARTICLE
  3 — SERVICES TO BE PROVIDED BY SEA LAUNCH

  	
  7

  
	
  ARTICLE
  4 — CONTRACT PRICE

  	
  8

  
	
  ARTICLE 5 — PAYMENTS

  	
  8

  
	
  ARTICLE 6 — LAUNCH SCHEDULE

  	
  10

  
	
  ARTICLE 7 — LAUNCH
  POSTPONEMENTS

  	
  12

  
	
  ARTICLE 8 — EXCUSABLE
  DELAYS

  	
  13

  
	
  ARTICLE
  9 — OBLIGATIONS BEFORE AND AFTER LAUNCH

  	
  14

  
	
  ARTICLE
  10 — COMMUNICATION and COORDINATION BETWEEN SEA LAUNCH and Inmarsat

  	
  15

  
	
  ARTICLE 11 — PERMITS
  AND APPROVALS

  	
  16

  
	
  ARTICLE 12 — TITLE TO
  PROPERTY

  	
  16

  
	
  ARTICLE 13 —
  REPLACEMENT LAUNCH

  	
  16

  
	
  ARTICLE
  14 — TERMINATION

  	
  17

  
	
  ARTICLE 15 — RISK ALLOCATION

  	
  20

  
	
  ARTICLE 16 — PROPRIETARY
  DATA

  	
  24

  
	
  ARTICLE 17 —
  RIGHTS TO INVENTIONS AND DATA

  	
  26

  
	
  ARTICLE 18 — TECHNICAL
  CHANGES

  	
  26

  
	
  ARTICLE
  19 — ASSIGNMENT

  	
  27

  
	
  ARTICLE 20 —
  PUBLIC RELEASE OF INFORMATION

  	
  27

  
	
  ARTICLE 21 — DISPUTE
  SETTLEMENT

  	
  27

  
	
  ARTICLE 22 — APPLICABLE LAW

  	
  28

  
	
  ARTICLE
  23 — SEVERABILITY

  	
  28

  
	
  ARTICLE 24 — WAIVERS

  	
  28

  
	
  ARTICLE 25 —
  CONTRACT MODIFICATIONS

  	
  28

  
	
  ARTICLE 26 — ENTIRE
  AGREEMENT

  	
  28

  
	
   

  	
   

  
	
  ANNEX
  A

  	
   

  

 

1

 

CONTRACT
FOR LAUNCH SERVICES

 

This Contract is made and entered into by and
between Sea Launch Limited Partnership, an exempted limited partnership
organized under the laws of the Cayman Islands acting through its General
Partner, Sea Launch Company, L.L.C., a United States limited liability company
organized under the laws of the State of Delaware (“Sea Launch”) and having
offices in Long Beach, California; and Inmarsat Limited, a limited liability
company incorporated under the laws of England and Wales whose registered
office is at 99 City Road, London EC1Y 1AX, England, (“Inmarsat”).

 

2

 

ARTICLE 1 — DEFINITIONS

 

The terms used in the Contract shall have the
following definitions:

 

1.1           Assembly
and Command Ship or “ACS” means the ship, ““Commander”, which serves as
the facility for assembly, processing and checkout of the Launch Vehicle;
houses the Launch Control Center; acts as the base for tracking the initial
ascent of the Launch Vehicle; and, provides accommodations for marine and
launch crews.

 

1.2           Business
Day means any day other than the following:  a Saturday, Sunday, and any other day that is a Legal Bank
Holiday as defined in 1.25 below.

 

1.3           Contract means
this Contract as defined in Article 2, Contractual Documents.

 

1.4           Constructive
Total Failure means a Constructive Total Loss due to performance of
the Launch Vehicle.

 

1.5           Constructive
Total Loss shall have the meaning assigned to the term
“Constructive Total Loss” in Inmarsat’s policy of Launch and In-Orbit Insurance
in place at the time of Launch. 
Inmarsat shall provide a copy of such definition to Sea Launch promptly
after the issuance of such policy of Launch and In-Orbit Insurance.

 

1.6           Day or day
means a calendar day unless otherwise indicated.

 

1.7           Effective
Date means the date of last signature by an authorized representative of Sea
Launch or Inmarsat.

 

1.8           Home Port means the
payload processing area and surrounding facilities for the loading and unloading
of the Launch Vehicle and Spacecraft on the Assembly and Command Ship and the
Launch Platform.

 

1.9           Interface
Control Document or “ICD” means the document implementing the IRD
(defined below) that defines in detail the interface between Inmarsat provided
spacecraft and the launch vehicle needs and accommodations of the specific
mission.

 

1.10         Interface
Requirement Document or “IRD” means the document that defines the
requirements between the Inmarsat provided Spacecraft and the Launch Vehicle
needs and accommodations for the specific mission, version 2 issue 2 dated
February 2002 amended by an Inmarsat-4 technical note entitled “Programme Main
Technical Issues” dated January 31, 2003 and any other changes agreed between
the parties.

 

3

 

1.11         Launch means the
point in time when the electronic signal sent to command the opening of any
first stage propellant valves is received by the Launch Vehicle, as verified by
either the flow of propellant/oxidizer, or telemetry indicating that the signal
reached the propellant valve.  A Launch
is deemed not to have occurred in the event of a Terminated Ignition.

 

1.12         Launch and
In-Orbit Insurance means insurance covering the risks of Launch and the
risks of in-orbit failures with respect to partial loss, constructive total
loss and total loss of the Spacecraft.

 

1.13         Launch
Base means the Sea Launch marine launch platform from which the Launch will
take place, as well as the Assembly and Command ship from which Launch operations
will be directed and monitored.

 

1.14         Launch Day means the
calendar day within the Launch Slot established for the Launch pursuant to the
Contract.

 

1.15         Launch
Opportunity means the availability of a position in the Sea
Launch manifest for the Launch of the Spacecraft, and is based upon these
criteria: 1) adequate time to make the necessary preparations for the Launch;
and 2) existing binding commitments to other Sea Launch customers.

 

1.16         Launch
Period means a period of time of not less than ninety (90) days as established
in Article 6 during which the Launch will occur.

 

1.17         Launch
Platform or “LP” means the marine platform, “Odyssey”, from which the
Launch is conducted.

 

1.18         Launch
Schedule means the then current Launch Period or the then
current Launch Slot or Launch Day, if established.

 

1.19         Launch
Services means the services provided by Sea Launch as defined
in Article 3, Services To Be Provided by Sea Launch.

 

1.20         Launch
Site means the geographic location on the equator from which the Launch will
take place. Specifically, 0 degrees N latitude, 154 degrees W longitude.

 

1.21         Launch
Slot means a thirty (30) day period of time within the Launch Period during
which the Launch will occur.

 

1.22         Launch
Vehicle means the standard expendable 6000kg launch vehicle Zenit 3SL, utilized
by Sea Launch to perform the Launch of the Spacecraft, as described in Rev C of
the Sea Launch User’s Guide.

 

1.23         Launch
Vehicle Performance means:

 

4

 

1.23.1      The
environmental conditions experienced by the Spacecraft as measured and recorded
by Sea Launch via telemetry. Sea Launch uses the measurements to ascertain
compliance with the environments agreed to by the Parties in the Interface
Control Document (ICD).

 

1.23.2      If applicable,
the functional interface between the Launch Vehicle and the Spacecraft as
measured and recorded by Sea Launch via telemetry. Sea Launch uses such
measurements to ascertain compliance with the functional interface requirements
agreed to by the Parties in the Interface Control Document (ICD).

 

1.23.3      The
Spacecraft injection orbit parameters as measured and recorded by Sea Launch
via telemetry. Sea Launch uses the measurements to ascertain compliance with
the injection orbit parameters as agreed to by the Parties in the Interface
Control Document (ICD).

 

1.24         Launch
Window means a specific daily time period or periods within each of one or
more potential Launch Days during which the Launch can occur to meet mission
requirements.

 

1.25         Legal Bank
Holiday means any day on which national banks are authorized to be closed in
New York City, New York, USA and/or in the United Kingdom.

 

1.26         Licensed
Launch Activities means the launch of a launch vehicle as defined in
the Commercial Space Transportation Licensing Regulations or the applicable
license issued by the Associate Administrator for Commercial Space
Transportation and as carried out pursuant to such license, and shall include
all launch and pre-launch activities carried out pursuant to such license
wherever performed (whether in the U.S. or elsewhere).

 

1.27         Option
Launch means the ability of Inmarsat pursuant to Article 6.1.1 to order from
Sea Launch an additional Launch Service to be performed for a substantially
similar spacecraft under the same terms and conditions as the Launch Service
covered by this Contract

 

1.28         Partial
Failure means a Partial Loss due to performance of the Launch Vehicle.

 

1.29         Partial
Loss shall have the meaning assigned to the term “Partial Loss” in
Inmarsat’s policy of Launch and In-Orbit Insurance in place at the time of
Launch.  Inmarsat shall provide a copy
of such definition to Sea Launch promptly after the issuance of such policy of
Launch and In-Orbit Insurance.

 

1.30         Party or
Parties means Sea Launch or Inmarsat or both depending on the context.

 

1.31         Payload means the
Spacecraft supplied by Inmarsat to be launched on the Launch Vehicle.

 

5

 

1.32         Postlaunch
Services means the reports and range services as defined in the
Statement of Work that are to be provided by Sea Launch to Inmarsat after
Launch.

 

1.33         Related
Third Parties means any of the following parties, but in each case
only if such party is involved in Licensed Launch Activities:

 

1.33.1      Employees,
directors, officers or agents of Sea Launch or Inmarsat, including its or their
affiliates, parents or partner entities;

 

1.33.2      Customers
of Sea Launch and the employees of those customers;

 

1.33.3      Contractors
and subcontractors at any tier of Sea Launch or Inmarsat and the employees of
those contractors and subcontractors; and

 

1.33.4      Any party
with a financial interest in Sea Launch, Inmarsat, the Launch Vehicle, or the
Payload.

 

1.34         Spacecraft
Separation means the physical separation of the spacecraft from
the Launch Vehicle pursuant to the command activating the separation system
that releases the spacecraft.

 

1.35         Spacecraft means the
hardware supplied by Inmarsat for Launch by Sea Launch pursuant to the Contract
and which is compatible with the Launch Vehicle.

 

1.36         Successful
Launch Service means that from Launch to Spacecraft Separation the
Launch Vehicle performed in such a manner that did not result in a Constructive
Total Failure, a Total Failure or a Partial Failure.

 

1.37         Terminated
Ignition means following the time when the electronic signal
is sent to command the opening of any first stage propellant valves, the first
stage engines of the Launch Vehicle have been shut down for any reason before
the hold down mechanism is released and the pad is officially declared safe by
Sea Launch.

 

1.38         Third
Party means any individual or legal entity other than the Parties or Related
Third Parties.

 

1.39         Total
Failure means a Total Loss due to performance of the Launch Vehicle.

 

1.40         Total Loss shall
have the meaning assigned to the term “Total Loss” in Inmarsat’s policy of
Launch and In-Orbit Insurance in place at the time of Launch.  Inmarsat shall provide a copy of such
definition to Sea Launch promptly after the issuance of such policy of Launch
and In-Orbit Insurance.

 

6

 

ARTICLE 2 — CONTRACTUAL DOCUMENTS

 

2.1           This
Contract shall consist of the following documents:

 

2.1.1.       General
Provisions, Articles 1 through 26

 

2.1.2.       Statement
of Work and ICD

 

2.1.2.1.            Until such
time as the ICD is signed by Inmarsat, Sea Launch and EADS Astrium the IRD
shall be included as a Contract document. 
Once executed by the Parties the ICD shall replace the IRD.

 

2.1.3.       Sea Launch
Launch Procedures SLP-MP-02-TBD.

 

2.2           In the
event of conflict between the General Provisions and the Statement of Work the
General Provisions shall have precedence over the Statement of Work. During the
countdown to the actual launch SLP-MP-02-TBD shall have precedence over the
General Provisions and the Statement of Work.

 

ARTICLE 3 — SERVICES TO
BE PROVIDED BY SEA LAUNCH

 

3.1           Sea Launch
shall provide Launch Services for the Launch of the Inmarsat Spacecraft
provided by Inmarsat in accordance with the Statement of Work.  Except for Postlaunch Services as specified
herein, Launch Services provided under the Contract shall be deemed to have
been completed upon Launch.

 

3.2           The Launch
Service provided by Sea Launch under this Contract shall include one (1) round
trip transit of the Assembly and Command Ship and Launch Platform between Home
Port and the Launch Site. To the extent that Sea Launch requests or experiences
a postponement pursuant to Article 7, Launch Postponements of this Contract
after the departure of the ACS and the LP from Home Port, Sea Launch will bear
the additional costs between Home Port and the Launch Site. If after departure
of either vessel, Inmarsat requests a postponement that results in the vessels
return to Home Port, Inmarsat shall bear the actual additional costs, not to
exceed $6,000,000 per such Inmarsat requested postponement that occurs after
the departure of either vessel.  The
actual, additional costs shall be reasonable and auditable and shall be
reviewed with Inmarsat prior to submission of invoice.  The payment for such costs shall be payable
by Inmarsat thirty days after submission of an invoice.

 

7

 

ARTICLE 4 — CONTRACT PRICE

 

4.1           The Contract price is
as follows:

 

One Firm launch of an
Inmarsat-4/EADS Astrium Spacecraft                                                                                                                                                                    ****

 

Option for a second, ****

****                                                                                                                                                                                                                                                                                                                                                                                                                                                                      ****

 

4.2           Taxes

 

The Launch Services prices set forth above
include all taxes, duties and other levies imposed on any Sea Launch furnished
service or materials by the U. S. Government and/or any political subdivisions
thereof; but exclude any taxes, duties, or other levies that may be imposed on
any Inmarsat-furnished Spacecraft, support equipment, or material used in the
transportation of Inmarsat-furnished Spacecraft or support equipment.  Any taxes, duties, or other levies imposed
on any Inmarsat-furnished Spacecraft, support equipment, or material used in
the transportation of Inmarsat-furnished Spacecraft or support equipment that
become the obligation of Sea Launch to pay, will be reimbursed by Inmarsat to
Sea Launch within thirty (30) days of the receipt of Sea Launch’s request for
payment

 

4.3           All
prices, payments and other figures of a financial nature are quoted in U.S.
dollars. All payments made under this contract shall be in U.S. dollars.

 

ARTICLE 5 — PAYMENTS

 

5.1           Inmarsat shall pay
the Contract Price in U.S. dollars as follows:

 

(i)            Inmarsat
will make an initial payment of **** save as otherwise provided in this
Contract and ****.  Upon exercise by
Inmarsat of its option for a launch of a second **** spacecraft, and
immediately upon presentation of an invoice from Sea Launch, Inmarsat shall
make an initial payment of ****. 
Thereafter, the payment terms of Article 5.1 (ii) below shall apply for
such Option Launch.

 

(ii)           Inmarsat
shall make the balance of the payments of the Contract Price for the Launch in
**** payments, beginning **** days prior to the first day of the Launch Period
as specified in Article 6, where “L” means the first day of the Launch Period,
Launch Slot, or Launch Day as applicable, and in accordance with the following
payment schedule:

 

8

 

	
  Event/Date

  	
   

  	
  Payment

  	
   

  
	
  L**** Days

  	
   

  	
   

  	
  ****

  	
   

  
	
  Launch **** days

  	
   

  	
   

  	
  ****

  	
   

  

****

 

5.2           Sea Launch
shall submit invoices to Inmarsat thirty (30) days in advance of the scheduled
due date.  If the due date falls on a
Saturday, Sunday, or Legal Bank Holiday, payment is due on the following
Business Day.

 

5.3           Payment
shall be made by electronic bank transfer, free of charge to Sea Launch, in the
amount specified in the invoice and pursuant to the instructions contained in
the invoice.  Payment shall be deemed to
have been made when credit for the payable amount has been established in the
payee’s designated bank account.

 

5.4           In the
event payment has not been received by Sea Launch by the due date, or has been
received in part only, Inmarsat shall pay Sea Launch interest on any unpaid
amount based on the interest rate charged by Citibank of New York City to its
preferred Customer’s (the prime rate) plus ****.  All payments then due and owing must be made prior to the
departure of the Launch Platform from Home Port.

 

5.5.          In the
event Inmarsat requests a postponement or postponements pursuant to paragraph
7.1 of Article 7, Launch Postponements, including any postponements due to excusable
delay, for every **** months of postponement requested by Inmarsat from the
originally contracted for nominal **** Launch Period unless **** is selected by
Inmarsat as the applicable Launch Period, Inmarsat shall pay Sea Launch the sum
of **** and each **** payment for each requested **** month postponement
period(s) shall accordingly reduce the payment due to Sea Launch at **** days
by the corresponding amount.  Payment of
the required **** for each **** months of postponement shall be due and payable
within thirty (30) days of the date of receipt of invoice from Sea Launch.

 

5.6           In the
event that one Party has not paid the second Party any amount that is due and
payable to the second Party under this Contract, such second Party shall have
the right to **** such amount against any payment(s) due and payable or to
become due and payable to the first Party, provided, however, any amount being
disputed under Article 21 of this Contract shall not be considered due and
payable until the dispute is finally resolved. In the event an undisputed
payment has not been received by the due date, or has been received in part
only, the Party owing the money shall pay the receiving Party interest on any
unpaid amount based on the interest rate charged by Citibank of New York City
to its preferred Customer’s (the prime rate) plus ****.

 

9

 

5.7           No payment
made under this Contract shall relieve Sea Launch of any of its obligations
under this Contract.

 

ARTICLE 6 — LAUNCH SCHEDULE

 

6.1           The Launch
of the Spacecraft shall take place during the following Launch Period(s):

 

	
  Launch

  	
   

  	
  Launch Period

  
	
   

  	
   

  	
   

  
	
  Inmarsat-4/EADS
  Astrium F-1

  	
   

  	
  Oct
  1, 2004 – Dec 31, 2004

  
	
   

  	
   

  	
   

  
	
  Inmarsat-4/EADS
  Astrium F-2

  	
   

  	
  Jan
  1, 2005 – Mar 31, 2005

  
	
   

  	
   

  	
   

  
	
  Option
  Launch Inmarsat-4/EADS Astrium F-3

  	
   

  	
  Jul
  1, 2005 – Sep 30, 2005

  

 

Nominally F-2 shall be the applicable Launch
Period, however, Inmarsat shall notify Sea Launch in writing no later than
April 1, 2004 which of the above Launch Periods Inmarsat intends to utilize for
the Launch of the Spacecraft.

 

6.1.1        In order
to preserve the Launch Period for the Option Launch, Inmarsat shall exercise
its option, in writing, within thirty (30) days of the launch of
Inmarsat-4/EADS Astrium F-1.  Sea Launch
shall be free to re-allocate launch vehicle hardware for the Option Launch,
once assigned pursuant to the Statement of Work, upon expiration of this
option.

 

6.1.2        Inmarsat
shall also have the right to exercise an option for the launch of
Inmarsat-4/EADS Astrium F-3 at any time till the end of December 2006 at the
price specified herein for F-3 and upon the same terms and conditions of this
Conract for the Launch Services.

 

6.2           Sea Launch
shall submit a proposed Launch Slot to Inmarsat within 30 days of Inmarsat’s
notifcation of the selection of the Launch Period for either F-1 or F-2, and
for F-3, after exercise of Option Launch. .

 

6.3           Sea Launch
shall submit a proposed Launch Day to Inmarsat at least ninety (90) days prior
to the first day of the Launch Slot. The Launch Day shall be determined by
mutual agreement of the Parties at least seventy-five (75) days prior to the
first day of the Launch Slot based on the availability of Launch Opportunities.
Upon commitment to a Launch Day, Inmarsat agrees to deliver the satellite to
Sea Launch’s Home Port no later than 45-days prior to the Launch Day.

 

6.4           The Launch
Window shall be determined by mutual agreement of the Parties no later than
forty-five (45) days prior to the Launch Day based on the availability of
Launch Opportunities.

 

10

 

6.5           The
following rules shall govern the establishment of Launch Schedule priorities
between Sea Launch, Inmarsat, and third party customers of Sea Launch,
excluding any commitments or obligations by Sea Launch prior to the effective
date of this Agreement:

 

(i)            In the
event of a Sea Launch postponement, for any reason, the launching order remains
in effect as of the date of Sea Launch’s postponement, excluding the following:

 

a.     Scientific
missions, which are time sensitive in nature, shall not be postponed;

 

b.     Reflight
or Replacement launches due to previous launch failures shall be initially
scheduled on a priority basis.  After
the initial scheduling procedure, a Reflight or Replacement launch shall
maintain its position in the launching order and shall be treated as a standard
Launch Service for any subsequent Sea Launch postponement.

 

(ii)           In the
event of a scheduling conflict during the initial scheduling of a Launch Period
or Launch Slot due to overlapping Launch Slots between two or more customers,
the Sea Launch customer with the earlier Contract effectivity date (i.e.
contract award date or option exercise date) shall have precedence.

 

(iii)          In the
event of a scheduling conflict during the scheduling of a Launch Period or
Launch Slot due to a postponement or delivery of the Spacecraft to Home Port
after the date specified in Article 6.3 by Inmarsat or due to a postponement by
any other Sea Launch customer, the Sea Launch customer (i.e. Inmarsat or third
party customer) initially scheduled for the Launch Period or Launch Slot shall
have precedence.

 

6.6           Inmarsat
shall notify Sea Launch ten (10) days prior to delivery of the spacecraft to
either Home Port or to a local airport. Except for delays that are Excusable
Delays as defined in Article 8, Excusable Delays, if Inmarsat fails to deliver
the Spacecraft within the period specified in paragraph 6.3 of this Article and
in accordance with the notification required in this paragraph, Sea Launch may,
depending on manifest constraints, treat the late delivery of the Spacecraft or
the inability to export the Spacecraft within the same timeframe as a
postponement by Inmarsat in accordance with Article 7, Launch Postponements .

 

11

 

ARTICLE 7 — LAUNCH
POSTPONEMENTS

 

7.1           Postponements
requested by Inmarsat

 

7.1.1        Prior to
the departure of the Launch Platform from Home Port to the launch site,
Inmarsat may request a change to the Launch Schedule for any reason by
providing written notice of any desired change. Inmarsat must request a change
as soon as Inmarsat has reason to believe that Inmarsat will not be able to
maintain the current Launch Schedule. At the time of the request for a change,
Inmarsat will propose a new Launch Schedule that Inmarsat is ready and able to
maintain. Within thirty (30) days of the receipt of the written request for a
Launch Schedule change, Sea Launch will either inform Inmarsat that a Launch
Opportunity is available as requested or will propose an alternative Launch
Schedule as close as possible to the Launch Schedule requested by Inmarsat. If
an alternative Launch Schedule is proposed by Sea Launch, Inmarsat will within
thirty (30) days respond by either accepting the alternative Launch Schedule
proposed by Sea Launch or by proposing another Launch Schedule. This process
shall continue until the Parties come to agreement on the Launch Schedule.

 

7.1.2        If after
departure of either vessel from Home Port, Inmarsat requests a postponement
that results in a delay of the Launch which requires the vessels to return to
Home Port, Inmarsat shall bear the actual additional costs, not to exceed ****
per such Inmarsat requested postponement which occurs after the departure of
either vessel. The actual additional costs shall be reasonable, auditable and
reviewed with Inmarsat prior to submission of invoice.

 

7.1.3        In the
event, that a single postponement or cumulative postponements by Inmarsat
exceed eighteen (18) months for a Launch, the exclusive right and remedy of Sea
Launch shall be either renegotiation of the Contract, including price and
terms, or termination in accordance with Paragraph 14.2 of Article 14,
Termination.

 

7.2           Postponements
requested by Sea Launch

 

7.2.1        Sea Launch
may request a change to the Launch Schedule in the event that a Launch
Opportunity does not exist within the current Launch Schedule. Sea Launch will
provide written notice of any desired change as soon as Sea Launch knows that a
Launch Opportunity will not be available. Sea Launch will propose a new Launch
Schedule at the time of the request for a change. Within thirty (30) days of
the receipt of the written request for a Launch Schedule change, Inmarsat will
either accept the alternative Launch Schedule proposed by Sea Launch or will
propose another Launch Schedule.

 

12

 

7.2.2        Postponements
by Sea Launch under this Article shall not exceed a total of nine (9) months
for any Launch. In the event that a single postponement or cumulative
postponements exceed nine (9) months for a Launch, the exclusive right and
remedy of Inmarsat shall be either renegotiation of the Contract, including
price and terms, or termination in accordance with Paragraph 14.1 of Article
14, Termination.

 

7.3           The length
of a postponement under this Article is measured from the first day of the then
current Launch Schedule to the first day of the Launch Schedule proposed in
conjunction with the initial request for a change. Days during which an excusable
delay exists as defined in Article 8, Excusable Delays, and which affect the
Launch Schedule of the postponed launch, are not included in determining the
length of a postponement under this Article.

 

ARTICLE 8 — EXCUSABLE DELAYS

 

8.1           Neither
Sea Launch nor Inmarsat shall be liable to the other in the event of a delay in
the performance of its obligation or commitments, and the date on which those
obligations are to be fulfilled shall be extended for a period of time equal to
that caused by the delay, when the delay is considered to be an excusable
delay, that is due to causes beyond the control of Sea Launch or Inmarsat as
the case may be, and not due to their fault or negligence in reasonably
anticipating and avoiding such delays. 
Sea Launch and Inmarsat shall use its reasonable efforts to reduce the
schedule impacts of such delays. Such excusable delays also include the
excusable delays of subcontractors when the item(s) or service(s) provided by
the subcontractor cannot be reasonably obtained from other sources.  Such excusable delays shall include, but not
be limited to: acts of God; fires; interruptions of essential services such as
electricity, natural gas, fuels and water; adverse weather or launch safety
conditions that do not permit Launch, any condition which jeopardizes the
safety of the employees of Sea Launch or Inmarsat or their subcontractors; acts
(including delay or failure to act) of any governmental authority (de jure or
de facto, but not export controls except as specified in Article 11, Permits
and Approvals), embargoes, strikes or labor stoppages (except those that affect
only the workforce of Sea Launch or its sub-contractors); wars; riots;
revolutions, terrorism, and hijacking

 

8.2           The
inability of Sea Launch to perform due to any export control restrictions or
delays caused by or arising from assignment of this Contract in whole or in
part by Inmarsat pursuant to Article 19, Assignment shall be an excusable delay
event.

 

13

 

ARTICLE 9 — OBLIGATIONS
BEFORE AND AFTER LAUNCH

 

9.1           Sea Launch
shall provide to Inmarsat and Inmarsat shall provide to Sea Launch the data,
hardware and services identified in the Statement of Work according to the
schedules provided therein.  The data,
hardware and services will be received in a condition suitable for their
intended use as defined by the requirements of the Statement of Work.  In the event that the data, hardware or
services are not received according to their schedule or requirements, and the
non-availability will affect the Launch Schedule, the following procedure shall
apply:

 

(i)        The Party
receiving or failing to receive the data, hardware or services shall promptly
notify the other Party including a statement of the discrepancy and recommended
solutions.  The Party receiving the
notification shall provide written direction to the other Party on how to
proceed, considering the recommendations of the other Party, within seven (7)
days of the receipt of notice.

 

(ii)       The Party
receiving or failing to receive the data, hardware or services shall use its
best efforts to continue its obligations under the Contract without affecting
the Launch Schedule.  If, however, this
is not possible despite the best efforts of the receiving Party, and the Launch
Schedule is affected as a result of the failure of one Party to deliver the
data, hardware or services in accordance with the schedule or requirements of
the Statement of Work, then a Launch postponement shall be declared by the
receiving Party and such delay shall be considered a delay under the
appropriate provisions of Article 7, Launch Postponements by the Party
providing or failing to provide the data, hardware or services.

 

9.2           The
Parties recognize that Sea Launch has no ability to alter the performance or in
any way correct any defect in the Launch Vehicle after Launch.  An agreement by Inmarsat to conduct the
Launch, given at the final launch readiness review, shall constitute a waiver
by Inmarsat of any claim that the Launch Vehicle or Launch Services do not meet
the requirements of the Statement of Work, or that the Launch Vehicle or Launch
Services are not otherwise suitable for their intended purpose.  Except for Postlaunch Services, the sole
liability or obligation of Sea Launch for performance subsequent to Launch is
to provide a replacement launch in accordance with Article 13, Replacement
Launch.

 

14

 

ARTICLE 10 — COMMUNICATION and COORDINATION BETWEEN SEA LAUNCH and
INMARSAT

 

10.1         All
notices and communications between the Parties relating to financial,
contractual or administrative matters of the Contract that are required or
permitted under the Contract, in order to be given effect, shall be in writing
and shall be addressed as listed below.

 

	
  All Notices to Sea Launch:

  	
   

  	
  Sea Launch Company, L.L.C.

  
	
   

  	
   

  	
  One World Trade Center

  
	
   

  	
   

  	
  Suite 950

  
	
   

  	
   

  	
  Long Beach, California 90831-0950

  
	
   

  	
   

  	
  Attention:

  	
  Cynthia M. Childs

  
	
   

  	
   

  	
   

  	
  Director, Project Development

  
	
   

  	
   

  	
   

  	
  Phone: (562) 
  499-4714

  
	
   

  	
   

  	
   

  	
  Fax: (562) 
  499-4755

  
	
   

  	
   

  	
   

  	
  Email:cynthia.childs@sea-launch.com

  
	
   

  	
   

  	
   

  	
   

  
	
  Notices to Inmarsat:

  	
   

  	
  Inmarsat Limited

  
	
   

  	
   

  	
  99
  City Road,

  
	
   

  	
   

  	
  London,
  EC1Y 1AX

  
	
   

  	
   

  	
  England

  
	
   

  	
   

  	
  Attention:

  	
  Tommy
  Smith

  
	
   

  	
   

  	
   

  	
  Senior
  Contracts Manager

  
	
   

  	
   

  	
   

  	
  Phone:
  +44 (0) 20 7728 1278

  
	
   

  	
   

  	
   

  	
  Fax:
  +44 (0) 20 7728 1612

  
	
   

  	
   

  	
   

  	
  Switchboard:
  +44 (0) 20 7728 1000

  
	
   

  	
   

  	
   

  	
  Email:
  tommy_smith@inmarsat.com

  

 

10.2         Sea Launch and Inmarsat each shall designate a Mission
Manager no later than one (1) month after the effective date of the
Contract.  The task of each of the
Mission Managers shall be to supervise and coordinate the respective
responsibilities of the Parties. 
Neither Mission Manager is authorized to direct work contrary to the
requirements of the Contract or to make modifications to the Contract.  Each Party may replace its Mission Manager
provided the other Party has received notification in writing of such action.

 

10.3         All documentation, notices, reports and correspondence
required pursuant to the Contract shall be submitted and maintained in the
English language.  All communication at the
Home Port and Launch Base between the Parties and with Related Third Parties
and between the personnel of the Parties or Related Third Parties shall be in
English.  The Parties shall mutually
agree upon standards for transliteration and translation of non-English
information.

 

15

 

ARTICLE 11 — PERMITS AND
APPROVALS

 

11.1         Each Party is responsible for obtaining in a timely
manner, all necessary licenses, permits, approvals, and authorizations to
perform its respective obligations under the Contract.  Each Party agrees to timely assist and
support the other Party to the extent practicable, in obtaining such licenses,
permits, approvals, and authorizations. 
Any failure to obtain or maintain such licenses, permits, approvals, and
authorizations shall be treated as follows:

 

(i)            If
such failure is attributable to lack of due diligence by Sea Launch, Article 14
..1.1 shall apply;

 

(ii)           If each Party has
affirmatively acted with due diligence, and its failure to obtain or maintain
the necessary governmental authorizations is attributable to causes beyond the
Party’s reasonable control and is not the result of any act or omission on the
part of such Party, Article 8.1 shall apply.

 

ARTICLE
12 — TITLE TO PROPERTY

 

12.1         Inmarsat understands and agrees that at no time does
Inmarsat obtain title to or any ownership of or any other legal or equitable
right or interest in or to any part of any Launch Vehicle, or in any other
property of Sea Launch including without limitation hardware used or furnished
by Sea Launch in providing Launch Services under this Contract.  Such property of Sea Launch shall be
considered between the Parties to be the property of Sea Launch.

 

12.2         Sea Launch understands and agrees that at no time does
Sea Launch obtain title to or any ownership of or any other legal or equitable
right or interest in or to any property of Inmarsat or any part thereof
including without limitation hardware used or furnished in performing the
obligations of Inmarsat hereunder.  Such
property of Inmarsat shall be considered between the Parties to be the property
of Inmarsat.

 

ARTICLE
13 — REPLACEMENT LAUNCH

 

13.1         Inmarsat may request a replacement launch in the event
of a Total Failure or Constructive Total Failure.

 

13.2         The request for a replacement launch must be in
writing and received by Sea Launch no later than ninety (90) days after the
determination of a Total Failure or Constructive Total Failure.  The request shall indicate the Launch Period
desired for the replacement launch.

 

13.3         Sea Launch shall inform Inmarsat, after receipt of the
request, if a Launch Opportunity exists in the requested Launch Period.  If a Launch Opportunity does

 

16

 

not
exist in the requested Launch Period, the Parties will negotiate in good faith
to reach a mutually acceptable Launch Period.

 

13.4         Any agreement reached by the Parties on a replacement
launch shall be in writing.  The
replacement launch shall be provided in accordance with the terms and
conditions of the Contract.

 

13.5         The configuration and mission requirements of the
Spacecraft selected by Inmarsat for the replacement launch shall be
sufficiently similar to avoid any need for mission analysis or for Launch
Vehicle or interface changes.

 

13.6         Inmarsat shall pay Sea Launch the same price for the
replacement launch as paid for the Launch declared a Total Failure or
Constructive Total Failure, subject to escalation at a rate of **** per year calculated from the first day of the Launch
Period established at the time of Contract award to the first day of the Launch
Period agreed upon by the Parties in accordance with Paragraph 13.3.

 

13.7         Inmarsat shall make payment for the replacement launch
in accordance with the payment schedule set forth in Article 5, Payments.  Inmarsat shall make the initial payment at
the time of the written agreement establishing the Launch Period of the
replacement launch in accordance with Paragraph 13.3.  The initial payment shall include all past due sums.

 

13.8         The remedies set forth in this Article 13 shall
constitute the sole and exclusive remedies of Inmarsat for Total Failure or
Constructive Total Failure.

 

ARTICLE 14 — TERMINATION

 

14.1         Termination by Inmarsat

 

14.1.1      Prior to Launch Inmarsat shall have the right to
terminate this Contract in whole or in part, for default, and shall be entitled
to a refund of ****
within thirty (30) days of the date of such termination, in the event that:

(i)            Sea Launch is in breach of a material term or
condition of this Contract;

(ii)           Sea Launch has failed to comply with the following
event milestones:

a.     The Launch Vehicle hardware shall be delivered to the
Sea Launch Home Port no later than ****
days;

b.     The Payload accommodation unit shall be delivered to
the Sea Launch Home Port no later than **** days;

c.     The monthly flight designs shall be completed by five
months prior to the beginning of the then current Launch Period.

 

17

 

d.     The allocation of the Inmarsat specific flight
hardware shall be accomplished by execution of this Contract plus ****;

e.     The Sea Launch hardware necessary to perform the
interface tests specified in Article 2.3.3 of the Statement of Work shall be
delivered to EADS Astrium in Toulouse, France no later than ****.

f.      Obtain a TAA by Effective Date of contract plus **** months.

(iii)          Sea Launch launch postponements exceed **** months;

a.     Inmarsat shall terminate within **** days of the expiration of the **** month period of postponement or it will have waived
its right to terminate under this provision unless the Inmarsat Launch is
further postponed by Sea Launch.

(iv)          The launch immediately preceding the scheduled
Inmarsat Launch is a failure; or Inmarsat chooses not to terminate and
thereafter Sea Launch is not able to perform its return to flight mission
within **** months of the date of the failure;

(v)           The second flight of the 6000kg configuration of the
Sea Launch Zenit-3SL launch vehicle is a failure.

 

14.1.2      Prior to the exercise of any postponement rights
pursuant to Article 7, Launch Postponements, Inmarsat shall have the right to
terminate the Contract in whole or in part, for convenience, in which event Sea
Launch shall be entitled to retain, as a termination charge and not as a penalty,
the amount specified in the following table as of the date of the termination:

 

	
  Date of Customer Termination

  	
   

  	
  Termination
  Liability as a

  percentage of the applicable

  Launch Services Price

  
	
  Effective
  Date of Contract through Launch Minus **** days

  	
   

  	
  **** at Effective Date of contract until **** days

  
	
  Launch
  Minus **** days through Launch

  	
   

  	
  **** at ****
  days through Launch

  

 

14.1.3      Following the exercise of any postponement right(s) to
which Inmarsat may be entitled pursuant to Article 7, Launch Postponements for
the nominal F-2 Launch Period, unless F-1 has been selected by Inmarsat as the
applicable Launch Period, the right of Inmarsat to terminate the Contract for
convenience and the available remedies, are limited to the following:

 

18

 

	
  Date of Customer Termination

  following Postponement

  	
   

  	
  Termination
  Liability

  
	
  For
  any postponement of the Launch Period of **** months:

  	
   

  	
  **** 

  
	
  For
  a postponement of the Launch Period of up to **** months:

  	
   

  	
  **** 

  
	
  For
  any postponement of the Launch Period of up to ****:

  	
   

  	
  **** 

  
	
  For
  any postponement of the Launch Date that exceeds **** 

  	
   

  	
  Sea Launch shall be entitled to
  renegotiation the Contract, including price and terms, or terminate the
  Contract in accordance with Paragraph 14.2.3 of Article 14, Termination.

  

 

14.1.4      The exclusive rights and remedies of Inmarsat
subsequent to Launch are limited to a replacement launch in accordance with
Article 13, Replacement Launch.

 

14.2         Termination by Sea Launch

 

14.2.1      The rights of Sea Launch to terminate the Contract or
any Launch under the Contract, and the available remedies, are limited to the
following:

 

(i)            Sea Launch may terminate the Contract in the event
that Inmarsat fails to comply with the payment obligations specified in Article
5, Payments.  In no event shall the
effective date of termination by Sea Launch under this Paragraph be earlier
than sixty (60) days after the due date of any payment not made. In the case of
a multi-launch agreement, only the Launch for which payments are delinquent may
be terminated under this Paragraph. In the event of such termination, Sea
Launch shall retain, as a termination charge, all payments due under Article 5,
Payments, for the Launch terminated, as of the effective date of termination;

 

(ii)           If Sea Launch elects to terminate for excessive
postponement under Article 7, Launch Postponements, Sea Launch will retain all
payments made by Inmarsat for the Launch terminated. In the case of a
multi-launch agreement,

 

19

 

only
the Launch postponed may be terminated under this Paragraph. The right of Sea
Launch to terminate under this Paragraph is conditioned upon receipt of a
written notification of a Launch postponement or cumulative postponements
exceeding eighteen (18) months.  Sea
Launch must terminate within sixty (60) days of the expiration of the eighteen
(18) month period of postponement or must waive its right to terminate under
this Paragraph unless further delayed by Inmarsat.

 

14.2.2      If Sea Launch brings any claim for material breach
prior to Launch other than for a Launch Schedule postponement, the exclusive
remedy of Sea Launch shall be termination of the Contract and retention of up
to the total of all payments made for every Launch subject to termination.

 

14.3         Any termination for default or breach under this
Article must be preceded by thirty (30) days written notification that
specifies the default or breach and the intent to terminate in the event that
the default or breach is not or cannot be cured within thirty (30) days of such
notice.

 

14.4         Both Inmarsat and Sea Launch agree that the payments
specified in this Article represent fair compensation for either Party, and
shall constitute the exclusive rights and remedies available to the Parties in
the event of termination by either Party.

 

ARTICLE
15 — RISK ALLOCATION

 

The
Parties expressly acknowledge and agree that the liabilities of Sea Launch
and/or of Inmarsat, resulting from the non execution or late execution of the
services provided by Sea Launch, and of the technical commitments of Inmarsat,
are strictly limited to the provisions of this Contract, excluding any other
liabilities or claims.

 

15.1         Warranty

 

15.1.1      Warranty Disclaimer. 
Sea Launch makes no warranty, express or implied, with respect to the
Launch or any services provided to or on behalf of Inmarsat. Nothing in this
Contract shall be construed as an express or an implied warranty. Inmarsat
acknowledges that it has read and understands this article and the exclusion of
all warranties has been bargained for in this Contract.

 

15.1.2      Limitation of Liability. In no event shall either
Party be liable under or in connection with this Contract under any legal or
equitable theory, including negligence, for direct, indirect, special,
consequential, or incidental damages, or indemnities, except as expressly
provided in this Contract.

 

20

 

Consistent
with this limitation of liability, each Party shall ensure that its insurer(s)
waive all rights of subrogation against the other Party.

 

15.2         Licensed Launch Activities

 

15.2.1      Third Party Liability Insurance (Licensed Launch
Activities)

 

15.2.1.1   Sea Launch shall obtain and maintain in effect a
policy of liability insurance that protects Inmarsat and its Related Third
Parties against claims by a Third Party for bodily injury or property damage
resulting from Licensed Launch Activities performed under this Contract. Such
insurance shall be in the amounts of US $100,000,000, before Launch and US
$300,000,000 after Launch, or such other amounts determined by the AST.

 

15.2.1.2   Such insurance shall remain in effect from
commencement of Licensed Launch Activities until one year after Launch.

 

15.2.1.3   The Third Party liability insurance obtained pursuant
to this Article shall not cover loss of or damage to the Spacecraft even if the
claim is brought by a Third Party or Related Third Party.

 

15.2.2      Indemnification by the United States Government
(Licensed Launch Activities).

 

15.2.2.1   Subject to the conditions of the Commercial Space
Launch Act (49 U.S.C. §§ 70101-70121), the United States Government shall pay
claims by a Third Party against Sea Launch, Inmarsat or their Related Third
Parties for bodily injury or property damage resulting from Licensed Launch
Activities, but only to the extent that the aggregate of such claims arising
out of any particular Launch is (i) in excess of the amount of insurance
required by the AST under paragraph 15.2.1.1 above and (ii) not in excess of
$1,500,000,000 (plus any additional sums necessary to reflect inflation
occurring after January 1, 1989).

 

15.2.2.2   Upon expiration of the insurance policy prescribed
under paragraph 15.2.1.1 above, the United States Government shall, subject to
the conditions of the Commercial Space Launch Act, provide for payment of
claims by a Third Party against Sea Launch, Inmarsat or their Related Third
Parties for bodily injury or property damage resulting from Licensed Launch
Activities from the first dollar of loss up to $1,500,000,000 (plus any
additional sums necessary to reflect inflation occurring after January 1,
1989).

 

15.2.2.3   Sea Launch makes no representation nor provides any
warranty that payment of claims by the United States Government will be made
pursuant to the Commercial Space Launch Act or otherwise.

 

21

 

The
sole obligation of Sea Launch is to make a good faith best effort to obtain
such payment from the United States Government.

 

15.2.2      Reciprocal Waiver and Release of Claims (Licensed
Launch Activities).

 

15.2.2.1   Each Party agrees to execute and submit to the AST, at
least forty (40) days prior to commencement of Licensed Launch Activities under
this Contract, the Agreement for Waiver of Claims and Assumption of Responsibility
incorporated into this Contract as Attachment 1.  Such Agreement is binding upon Inmarsat, Sea Launch and the U.S.
Government only with respect to Licensed Launch Activities performed under this
Contract.

 

15.2.2.2   Each Party shall implement the reciprocal waiver of
claims provisions provided in paragraph 15.2.2.1 with its Related Third Parties
(other than employees, officers or directors) requiring them to waive and
release all claims of liability they may have against the other Party and its Related
Third Parties.

 

15.3         Activities other than Licensed Launch Activities

 

15.3.1      Third Party Liability (other than Licensed Launch
Activities) Each Party agrees to indemnify, defend and hold harmless the other
Party from and against any and all claims of a Third Party (other than claims
by employees, officers or directors of a Party or of its Related Third Parties)
for personal injury or property damage to the extent that it is caused by the
indemnifying Party or its Related Third Parties while performing activities
related to this Contract other than Licensed Launch Activities.  Each Party shall maintain insurance with
limits sufficient to cover the aforementioned indemnification obligation and
ensure that its insurer(s) waive all rights of subrogation against the other
Party.

 

15.3.2      Reciprocal Waiver and Release of Claims (other than
Licensed Launch Activities)

 

15.3.2.1   Each Party agrees to a reciprocal waiver of claims
pursuant to which each Party agrees to be responsible for and to absorb the
financial and any other consequences of any property damage or loss it sustains
or any personal injury to, death of, or property damage or loss sustained by
its own employees arising out of or relating to any activities carried out
under this Contract other than Licensed Launch Activities. Neither Party will
make any claim or institute any arbitration or judicial proceedings against the
other Party or its Related Third Parties for such damage, loss, injury or
death. This waiver will not be applicable to the extent that the damage, loss,
injury or death sustained by a Party or its employees is caused by the
intentional misconduct of the other Party or its Related Third Parties.

 

22

 

15.3.2.2   Each Party further agrees to require its Related Third
Parties (other than employees, officers or directors) to be responsible for and
to make no claims against the other Party or its Related Third Parties for any
property damage or loss they sustained or for any personal injury to, death of,
or property damage or loss sustained by their own employees arising our of or
relating to any activities carried out under this Contract other than Licensed
Launch Activities.  The waiver required
by this paragraph 15.3.2.2 will not be applicable to the extent that the
damage, loss, injury or death sustained by a Related Third Party is caused by
the intentional misconduct of the other Party or its Related Third Parties.

 

15.3.2.3   If any of a Party’s Related Third Parties makes a
claim or institutes any arbitration or judicial proceeding (other than claims
for gross negligence or intentional misconduct which are not subject to this
waiver) against the other Party or its Related Third Parties for damage, loss,
injury or death as identified in paragraph .15.3.2.2, the first Party shall
indemnify, hold harmless and defend the other Party and its Related Third
Parties from and against any liability on account of such damage, loss, injury
or death, and shall pay all expenses and satisfy all awards and judgments which
may be incurred by or rendered against said indemnitee(s).  The Party seeking such indemnification shall
comply with the provisions of Article 15.6.

 

15.4         Spacecraft

 

Inmarsat
assumes the risk of any actual or constructive loss of or damage to the
Spacecraft prior to, during, and after Launch, including any loss or damage
resulting from the non-availability of or inability to use the Spacecraft
following Launch.  Inmarsat shall
indemnify, defend, and hold harmless Sea Launch and its Related Third Parties
against all claims and actions based in whole or in part on loss or damage to
the Spacecraft, including loss or damage resulting from the non-availability of
or inability to use the Spacecraft. 
This assumption of risk and indemnification shall not apply (i) to the
extent that the loss or damage is caused by the intentional misconduct of Sea
Launch or its Related third Parties. 
Inmarsat shall ensure that its insurers waive all rights of subrogation
against the Sea Launch and its Related Third Parties.

 

15.5         Indemnification- Intellectual Property Infringement

 

15.5.1      Sea Launch agrees to defend, hold harmless and
indemnify Inmarsat and its Related Third parties from and against any
liabilities, costs, risks, losses, damages, or injury, or any consequences
thereof, resulting from an infringement or claim for infringement of the patent
right or any other intellectual property right of a third party or a Related
Third Party of Sea Launch which may arise from the provisions of the services
under this Contract by Sea Launch.

 

23

 

15.5.2      Inmarsat agrees to defend, hold harmless and indemnify
Sea Launch and its Related Third parties from and against any liabilities,
costs, risks, losses, damages, or injury, or any consequences thereof,
resulting from an infringement or claim for infringement of the patent right or
any other intellectual property rights of a third party or a Related Third
Party of Inmarsat which may arise from the design and manufacture of the
Spacecraft

 

15.6         Notice and Cooperation

 

Each
Party agrees to cooperate with the other Party in obtaining relevant reports
and other information in connection with the presentation by either Party of
any claim under insurance required by this article.  A Party seeking indemnification under this Article shall (i)
promptly advise the indemnitor of any damage or injury incurred, or the filing
of any suit or any written or oral claim against it; (ii) provide the
indemnitor with copies of all relevant documentation; and (iii) cooperate with
the indemnitor and its insurers in every reasonable manner in defending against
such claim. A Party seeking indemnification shall not make any admission, nor
shall it reach a compromise or settlement, without the prior written approval
of the indemnitor.

 

15.7         Evidence of Insurance

 

Sea
Launch shall provide Inmarsat with evidence of third party liability insurance
within L-thirty (30) days.

 

ARTICLE
16 — PROPRIETARY DATA

 

16.1         The Parties recognize that technical information may
be disclosed by one Party to the other Party in the course of performance under
the Contract and that the disclosing Party may desire to protect such
information against unrestricted use or disclosure to others.  To provide protection for such information,
each Party agrees to respect such information and, to the extent it includes
proprietary data, to handle such information as provided for in this Article.

 

16.2         For the purpose of this Contract, the term
“proprietary data” means each Party’s proprietary, secret, or confidential
information, data, processes, and physical materials, including information
originated by, or available only from the disclosing Party and information
originating with a Third Party or Related Third Party with respect to which the
disclosing Party has limited disclosure rights, and which the disclosing Party
desires to protect against unrestricted disclosure to others, provided that
such information, data, processes, and physical materials are marked
“proprietary data” or with an equivalent legend or, if disclosed orally, is
identified as proprietary at the time of disclosure and then summarized in a
written document marked as “proprietary data” that is supplied to the receiving
Party within ten (10) days of initial disclosure.

 

24

 

16.3         Except as permitted herein and in paragraph 16.4
below, a Party receiving proprietary data shall take all reasonable precautions
to prevent publication or disclosure of proprietary data to others, and shall
use such data only for the purpose of performance under the Contract.  Except as permitted herein and in paragraph
16.4 below, any other use of such proprietary data shall be made only upon
prior written consent of the disclosing Party. 
Each Party agrees to protect the other Party’s proprietary data with the
same degree of care as it protects its own proprietary data (but in no event
less than a reasonable degree of care), and to restrict disclosures of such
proprietary data to those persons, entities (i.e. insurance underwriters) and
subcontractors having a need to know the data provided any such person, entity
or subcontractor must first agree in writing to treat any such proprietary data
as confidential.

 

16.4         The aforementioned restrictions on the use and
disclosure of proprietary data shall not apply if the proprietary data:

 

(i)            Is in the public domain at the time of receipt or
comes into public domain thereafter through no act of the receiving Party that
is inconsistent with the aforementioned restrictions;

 

(ii)           Known to the receiving Party prior to disclosure by
the disclosing Party;

 

(iii)          Disclosed with the prior written approval of the
disclosing Party;

 

(iv)          Independently developed by the receiving Party; or

 

(v)           Lawfully disclosed to the receiving Party by a Third
Party under conditions permitting such disclosure;

 

(vi)          Is required by applicable law, regulation or
governmental order to be disclosed (but in such case only to the extent so
required to be disclosed).

 

16.5         Upon termination or upon completion of performance
under the Contract, and upon the request of one Party, the other Party shall
return all proprietary data (including any copies thereof) received from that
Party, or provide written certification that such proprietary data has been
destroyed, except that either Party may retain a legal file copy.

 

16.6         Neither Party assumes any liability to the other Party
for damages arising from the use of or reliance upon any information disclosed
pursuant to this Article 16, except as provided elsewhere herein.

 

16.7         Information exchanged under this Contract may be
subject to U.S. and U.K. export control laws and regulations, such as the U.S.
International Traffic in Arms Regulations (ITAR) or the Export Administration
Regulation (EAR). The disclosing Party shall clearly mark any such information
exchanged with an appropriate legend indicating the relevant restrictions or
applicable laws and regulations.  The
receiving Party agrees that information subject to such export control laws and
regulations shall not be disclosed or transferred to a Third Party or Related
Third

 

25

 

Party
without first obtaining written approval from the disclosing party and
complying with all applicable U.S. export control laws and regulations. Such
approval shall not be unreasonably withheld.

 

16.8         Information exchanged under this Contract may be
subject to Russian and/or Ukrainian export control laws and regulations. The
disclosing Party shall clearly mark any such information exchanged with an
appropriate legend indicating the relevant restrictions or applicable laws and
regulations. The receiving Party agrees that information subject to such export
control laws and regulations shall not be disclosed or transferred to a Third
Party or a Related Third Party without first obtaining written approval from
the disclosing Party and complying with all applicable export control laws and
regulations. Such approval shall not be unreasonably withheld.

 

ARTICLE 17 — RIGHTS TO INVENTIONS AND DATA

 

Sea
Launch and Inmarsat agree that neither Party shall by entry into the Contract
or by performance of the Contract, acquire any rights to or under the other
Party’s patents, proprietary data, or other intellectual property or technical
information, unless the grant of any such right is expressly provided for in a
separate written agreement duly executed by the granting Party.

 

ARTICLE
18 — TECHNICAL CHANGES

 

18.1         Inmarsat may, by a written notice, request technical
(e.g., Launch Vehicle interface, environmental requirements) changes within the
general scope of this Contract.  If any
such change causes an increase or decrease in the cost of, or the time required
for the performance of any part of the work under this Contract, an equitable
adjustment, to be negotiated in good faith between the Parties, shall be made
in the price, delivery schedule, Launch Date, or other terms affected by the
requested change, and the Contract shall be modified in writing accordingly.  Any claim by Sea Launch for an adjustment
must be made in writing within thirty (30) days of the receipt of any such
notice.  Nothing in this Article 18
shall excuse Sea Launch from proceeding without delay to perform this Contract
as so changed.

 

18.2         Sea Launch shall have the right to recommend changes
within the general scope of this Contract. 
Sea Launch shall submit any such change to Inmarsat in writing and
Inmarsat shall accept or reject such change in its sole discretion.  Inmarsat shall respond to any such change
proposed by Sea Launch promptly but in no event later than forty-five (45) days
after the date on which Sea Launch submitted the proposed change.  Sea Launch shall not proceed with any change
under this Paragraph until an amendment to this Contract is executed by both
Parties authorizing the change and making the corresponding adjustments to the
work and/or the terms of this Contract necessitated by the change.

 

26

 

18.3         Launch Service(s) postponements by Inmarsat or Sea
Launch shall be resolved in accordance with Article 7, Launch Postponements, of
this Contract.

 

18.4         In the event Sea Launch changes the launch vehicle
interfaces or environmental requirements subsequent to execution of this
Contract, Sea Launch shall indemnify Inmarsat for its reasonable costs
associated with the design, test and schedule impact required to be made on any
of the Inmarsat-4 spacecraft to accommodate such Sea Launch changes.

 

ARTICLE
19 — ASSIGNMENT

 

19.1         The Parties agree not to assign their respective
rights or obligations under the Contract without the prior written consent of
the other Party.

 

Notwithstanding
the above, Inmarsat shall have the right to assign this Contract to any company
within the Inmarsat Group, e.g., subsidiaries of any tier of the holding
Company. Inmarsat shall have the right to novate this Contract for Launch
Services within the Inmarsat Group, subject to the consent of Sea Launch which
consent shall not be unreasonably withheld or delayed.

 

ARTICLE 20 — PUBLIC RELEASE OF INFORMATION

 

20.1         Except as required by law or regulation, no news
release, public announcement, or advertising material concerned with this
Contract shall be issued by either Party without prior written consent of the
other Party.  Such consent shall not be
unreasonably withheld. All releases shall be coordinated between both Parties.

 

20.2         Subject to redaction of proprietary terms and
information, including but not limited to pricing and payment provisions,
Inmarsat shall be entitled to disclose parts of the Contract to the extent
necessary to comply with any listing authorities’ requirements, should Inmarsat
seek a listing. Subject to prior execution of nondisclosure agreements,
Inmarsat shall be entitled to disclose all or parts of the Contract to private
equity or debt financing partners.

 

ARTICLE 21 — DISPUTE SETTLEMENT

 

The
Parties shall endeavour to reach an amicable settlement of any dispute or
controversy resulting from, or arising in connection with, the performance of
this Contract.  In the event a
settlement cannot be reached in a timely manner by the Sea Launch and Inmarsat
Mission Managers, the dispute or controversy shall be referred to the
respective Presidents of Sea Launch and Inmarsat, who shall use their best
efforts to reach a settlement acceptable to both Parties.  If such a settlement cannot be reached the
dispute or controversy shall be submitted to arbitration under the London Court
of Arbitration, London England, by three arbitrators appointed pursuant to the
governing rules.  The

 

27

 

arbitration
shall be conducted in English.  The
arbitration award shall be final and binding, and the execution thereof may be
entered in any court having competent jurisdiction.

 

ARTICLE 22 — APPLICABLE LAW

 

The
Contract and any matter arising under the Contract, regardless of whether such
matter is addressed in the Contract, shall be governed by the laws of England
excluding its choice of law rules.

 

ARTICLE
23 — SEVERABILITY

 

In
the event any of the provisions of the Contract shall, for any reason
whatsoever, be held to be invalid or unenforceable, the remaining provisions
shall not be affected.

 

ARTICLE
24 — WAIVERS

 

No
waiver of any of the provisions of the Contract shall be binding on either
Party unless evidenced by a written notice signed by the Party to be
bound.  Failure of either Party to
insist upon performance of any of the terms or conditions herein or to exercise
any right or privilege shall not constitute a waiver.  A waiver by either Party of a breach of any provision of this
Contract does not constitute a waiver of any succeeding breach of the same or
any other provision, nor shall it constitute a waiver of the provision itself.

 

ARTICLE 25 — CONTRACT MODIFICATIONS

 

The
Contract shall be modified only upon mutual consent and such modification shall
be made in writing and shall be signed by both Parties.

 

ARTICLE
26 — ENTIRE AGREEMENT

 

The
Contractual documents referred to in Article 2, Contractual Documents, comprise
the entire understanding between the Parties with respect to the subject matter
of the Contract and shall supersede all prior and contemporaneous discussions
between the Parties.  Neither Party
shall be bound by any conditions, warranties, definitions, statements, or documents
previous to the Contract unless the Contract makes express reference thereto.

 

28

 

IN
WITNESS WHEREOF, the Parties hereto have executed the Contract as of the day
and year stated:

 

 

	
  Inmarsat
  Limited

  	
  Sea
  Launch Limited Partnership acting

  through its General Partner,

  Sea Launch Company, L.L.C.

  
	
   

  	
   

  
	
   

  	
   

  
	
  By:

  	
  /s/ LEA TRAINI

  	
   

  	
  By:

  	
  /s/ JAN T. SKOLMLI

  	
   

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Title:

  	
  Director, Procurement and
  Contracts

  	
   

  	
  Title:

  	
  Vice President, Risk Management

  	
   

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Date:

  	
  16 December 2003

  	
   

  	
  Date:

  	
  16 December 2003

  	
   

  

 

29

 

	
  

  	
   

  	
  Contract INM-CO/03-3723

  November 2003

  

 

 

ANNEX A

 

 

STATEMENT OF WORK

 

 

for

 

 

LAUNCH SERVICES

 

 

	
  Proprietary
  & Confidential

  	
   

  	
   

  

 

 

TABLE OF CONTENTS

 

	
  ABBREVIATIONS AND ACRONYMS

  	
   

  	
  3

  
	
  SCOPE

  	
   

  	
   

  	
  4

  
	
   

  	
  Reference
  Documents

  	
   

  	
   

  	
  4

  
	
   

  	
  1.1

  	
   

  	
  Documentation,
  Reports, Meetings and Reviews

  	
  5

  
	
   

  	
   

  	
  1.1.1

  	
   

  	
  Documentation

  	
  5

  
	
   

  	
   

  	
  1.1.2

  	
   

  	
  Reports

  	
  6

  
	
   

  	
   

  	
  1.1.3

  	
   

  	
  Schedules

  	
  6

  
	
   

  	
   

  	
  1.1.4

  	
   

  	
  Meetings and Reviews

  	
  6

  
	
   

  	
  1.2

  	
   

  	
  Quality

  	
  7

  
	
   

  	
  1.3

  	
   

  	
  Safety

  	
  7

  
	
  2.

  	
   

  	
  LAUNCH VEHICLE

  	
  8

  
	
   

  	
  2.1

  	
   

  	
  Launch Vehicle
  Hardware

  	
  8

  
	
   

  	
  2.2

  	
   

  	
  Launch System
  Performance

  	
  8

  
	
   

  	
   

  	
  2.2.1

  	
   

  	
  Launch
  Vehicle Performance

  	
  9

  
	
   

  	
   

  	
  2.2.2

  	
   

  	
  Mission Optimization

  	
  9

  
	
   

  	
  2.3

  	
   

  	
  Spacecraft
  to Launch Vehicle Interfaces

  	
  10

  
	
   

  	
   

  	
  2.3.1

  	
   

  	
  Mechanical
  Interfaces

  	
  10

  
	
   

  	
   

  	
  2.3.2

  	
   

  	
  Electrical
  Interfaces

  	
  10

  
	
   

  	
   

  	
  2.3.3

  	
   

  	
  Spacecraft/Spacecraft
  adapter interface test support

  	
  11

  
	
   

  	
  2.4

  	
   

  	
  Spacecraft
  Separation Conditions

  	
  11

  
	
   

  	
  2.5

  	
   

  	
  Environmental
  Requirements

  	
  11

  
	
   

  	
  2.6

  	
   

  	
  Customer
  Logo on Payload Fairing

  	
  11

  
	
  3.

  	
   

  	
  MISSION
  ANALYSIS

  	
  11

  
	
  4.

  	
   

  	
  LAUNCH SERVICES AND FACILITIES

  	
  12

  
	
   

  	
  4.1

  	
   

  	
  Sea Launch
  Home Port, Long Beach, California

  	
  13

  
	
   

  	
   

  	
  4.1.1

  	
   

  	
  Home Port
  Facilities

  	
  13

  
	
   

  	
   

  	
  4.1.2

  	
   

  	
  Home Port Services

  	
  13

  
	
   

  	
  4.2

  	
   

  	
  Assembly
  and Command Ship (ACS)

  	
  13

  
	
   

  	
   

  	
  4.2.1

  	
   

  	
  Assembly
  Command Ship Facilities

  	
  13

  
	
   

  	
   

  	
  4.2.2

  	
   

  	
  Assembly
  Command Ship Services

  	
  13

  
	
   

  	
  4.3

  	
   

  	
  Launch Platform (LP)

  	
  14

  
	
   

  	
   

  	
  4.3.1

  	
   

  	
  Launch
  Platform Facilities

  	
  14

  
	
   

  	
   

  	
  4.3.2

  	
   

  	
  Launch Platform
  Services

  	
  14

  
	
   

  	
  4.4

  	
   

  	
  Communications

  	
  14

  
	
   

  	
  4.5

  	
   

  	
  Launch Services

  	
  14

  
	
   

  	
  4.6

  	
   

  	
  Range Services

  	
  15

  
	
  5.

  	
   

  	
  POST
  LAUNCH SERVICES

  	
  15

  
	
  6.

  	
   

  	
  SEA LAUNCH RESPONSIBILITIES

  	
  15

  
	
  7.

  	
   

  	
  INMARSAT RESPONSIBILITIES

  	
  16

  
								

 

A-1

 

LIST OF TABLES

 

	
  Table
  1.1.4-1.  Sea Launch Meetings and
  Reviews

  	
  7

  
	
  Table
  3-1.  Sea Launch Mission Analysis
  Tasks

  	
  12

  
	
  Table
  6.1.  Sea Launch Deliverables

  	
  16

  
	
  Table
  7.1.  Inmarsat Deliverables

  	
  18

  

 

A-2

 

ABBREVIATIONS
AND ACRONYMS

 

ACS                        Assembly and Command Ship

 

CCAM                   Contamination and Collision Avoidance
Maneuver

 

CDR                        Critical Design Review

 

CLA                        Coupled Loads Analysis

 

DTM                      Displaced Transformation Matrix

 

EMC                       Electromagnetic Compatibility

 

EMI                        Electromagnetic Interference

 

GMM                     Geometric Math Model

 

HAR                       Hardware Acceptance Review

 

HP                           Home Port, Long Beach, CA

 

ICD                         Interface Control Document

 

ILV                          Integrated Launch Vehicle

 

LLC                         Limited Liability Company

 

LP                           Launch Platform

 

LV                           Launch Vehicle

 

L-                            Launch Minus

 

PLA                        Payload Accommodations

 

PLF                         Payload Fairing

 

PPF                         Payload Processing Facility at Sea Launch
Home Port, Long Beach, CA

 

SC                           Spacecraft

 

SOW                      Statement of Work

 

TAA                       Technical Assistance Agreement

 

A-3

 

SCOPE

 

This
Statement of Work (SOW) encompasses the launch services to be supplied by Sea
Launch Limited Partnership acting through its general partner, Sea Launch
Company, LLC (Sea Launch) to Inmarsat for the INMARSAT 4 Mission utilizing the
Astrium Eurostar 3000 spacecraft (SC).

 

Sea
Launch shall perform the tasks and provide the equipment and facilities
specified in this SOW to provide launch services for the INMARSAT 4
spacecraft.  Launch Services shall be
provided using the Sea Launch launch vehicle (LV), the Zenit-3SL.  The mission shall be conducted from Sea
Launch’s Assembly and Command Ship (ACS) and Launch Platform (LP) in the
equatorial region (0 DEG. N. Latitude) of the Pacific Ocean.

 

This
Statement of Work includes the following areas:

 

1.     Program Management

2.     Launch Vehicle

3.     Mission Analysis

4.     Launch Services and Facilities

5.     Post Flight Reporting

6.     Sea Launch Responsibilities

7.     Inmarsat Responsibilities

 

Unless
specified otherwise, times are presented in months prior to launch, ‘L-x’.

 

REFERENCE DOCUMENTS

 

Parts
of the following documents are incorporated into this Exhibit to the extent
that they are specifically referenced herein. 
Where a conflict exists, the Statement of Work takes precedence.

1)     D688-10009-1, Sea Launch User’s Guide, Revision C, February 2003

2)     D688-10024-1, Sea Launch Safety Regulations Manual, Rev. New, 16
July 1998

3)     HPD-40105 Sea
Launch Facilities Accommodations Handbook, Rev New, 15
October 2001

4)     INMARSAT 4 Interface Requirements Document
(IRD), document number TBD

5)     INMARSAT 4 Interface Control Document (ICD),
document number TBD, released following the execution of the ICD by all
parties.

6)     Appendix 1, Inmarsat-4 Program Main Technical Issues, dated 31 January,
2003

 

A-4

 

6)     1.             PROGRAM MANAGEMENT

 

Sea
Launch shall supply the Program Management necessary to cover all aspects of
the Contract for Launch Services. Program Management tasks shall include the
following:

•      LV hardware production and schedule

•      Document generation, control and delivery

•      Meetings, reviews and telecons

•      Mission analysis

•      Applicable Home Port activities including joint operations (Sea Launch
shall support, but not provide direct management of, autonomous SC activities)

•      All launch site activities

•      Post launch reports

•      Safety provisions

•      Quality provisions

•      Customer events related to viewing the launchTechnical Assistance
Agreement (TAA)

 

Sea
Launch shall assign a dedicated Sea Launch Mission Manager no later than one
month after contract signature.  All Sea
Launch deliverable documentation shall be transmitted through the Sea Launch
Mission Manager to the INMARSAT 4 Mission manager.  The Sea Launch Mission Manager shall be responsible for all
INMARSAT 4 Mission functions related to the execution of the Contract for the
INMARSAT 4 Launch Service.

 

Inmarsat
shall assign a dedicated INMARSAT 4 Mission Manager no later than one month
after contract award.  All Inmarsat
deliverable documentation shall be transmitted through the INMARSAT 4 Mission
Manager (and/or designated INMARSAT 4 representative) to the Sea Launch Mission
Manager.  The INMARSAT 4 Mission Manager
shall be responsible for all INMARSAT 4 Mission functions related to the
execution of the Contract for Launch Services.

 

1.1          DOCUMENTATION, REPORTS,
MEETINGS AND REVIEWS

 

1.1.1       Documentation

 

Sea
Launch shall prepare all documentation required to provide the launch service,
as specified in Section 6, Table 6-1. 
Sea Launch shall maintain a configuration control system for the mission
unique documentation.  Inmarsat shall
provide timely inputs to Sea Launch to support development of documentation, as
specified in Section 7, Table 7-1.

 

Sea
Launch shall maintain configuration control of mission specific signed
documentation subject to the agreement of both parties.  Formal change proposals shall be submitted
to Inmarsat for review and approval. 
Contract modifications may be required for changes that exceed the scope
of the launch services contract.

 

The
Sea Launch Mission Manager and the INMARSAT 4 Mission Manager shall agree that
a minimum of five (5) Hard copies and one (1) electronic copy of required
documentation shall be provided by each party.

 

Interface Control Documentation: Sea Launch shall develop a SC to LV
Interface Control Document (ICD) based on timely inputs from Inmarsat. Once
signed by both Sea Launch and

 

A-5

 

Inmarsat,
the ICD shall become the contractual document defining the technical
requirements for launch services, superseding the technical integration
requirements of this Statement of Work. Sea Launch and Inmarsat shall each
verify their respective requirements as defined in the ICD.  All verification shall be completed prior to
launch.

 

Procedures:
All Sea Launch operations are conducted in accordance with Sea Launch approved,
released procedures that are maintained under configuration control.  All combined procedures that address joint
operations between the SC and the Sea Launch System are reviewed and agreed to
with the INMARSAT 4 Mission Manager prior to commencement of operations.  All SC hazardous and on-site procedures
shall be under Inmarsat configuration control and will be provided to Sea
Launch for review per Section 7, Table 7-1.

 

1.1.2       Reports

 

Sea
Launch shall provide to Inmarsat the reports specified in Section 6, Table
6-1, Items 10-14.  A preliminary
delivery schedule for these reports is provided in Table 6-1. Sea Launch
and Inmarsat shall mutually agree upon a final delivery schedule after
contract award.

 

1.1.3       Schedules

 

Sea
Launch shall maintain mission integration schedules that cover all aspects of
program management for the launch services. 
Sea Launch shall provide the schedules to Inmarsat on a quarterly basis.

 

Sea
Launch and Inmarsat shall develop and mutually agree to a mission-specific
milestone and documentation schedule within 30 days of Contract signature
by both parties.  This milestone
schedule shall provide all major technical milestones necessary for
successful completion of the Contract for Launch Services.  This milestone schedule shall be based
upon on Table 6-1 and Table 7-1.  The
mission integration schedule shall be presented at applicable reviews.

 

1.1.4       Meetings and Reviews

 

Sea
Launch and Inmarsat agree to conduct meetings/reviews as often as necessary to
allow timely execution of all activities to support the Mission.  These shall include, but not be limited to
the meetings/reviews identified in Table 1.1.4-1.  Approximate timing of the meeting/review is shown, with the final
timing to be agreed to between Sea Launch and Inmarsat.

 

Inmarsat
is invited to all meetings listed in Table 1.1.4-1.  The Sea Launch Mission Manager and the INMARSAT 4 Mission Manager
shall agree upon specific meeting location, agendas, logistics and
participation in advance, on a case-by-case basis.

 

Sea
Launch and Inmarsat shall have access to the Sea Launch and Inmarsat facilities
to attend meetings and reviews as defined above.

 

Inmarsat
is invited to witness activities related to the launch vehicle hardware
assigned to the INMARSAT 4 mission at Sea Launch Home Port and the launch
site.  The Sea Launch Mission Manager
shall advise the INMARSAT 4 Mission Manager as to the schedule and
location of the various reviews and activities. Participation at launch vehicle
hardware reviews is subject to the

 

A-6

 

provision
of applicable Technical Assistance Agreements. 
The number of attendees to view activities at the launch site may be
limited by available accommodations on the ACS.

 

Sea
Launch and Inmarsat shall obtain necessary approvals for their respective
personnel to attend the meetings and/or reviews.

 

To
track all actions identified during applicable meetings and reviews, Sea Launch
shall create and maintain an Action Item list. 
The Action Item list shall be presented at applicable reviews.  Sea Launch shall also provide a draft version
of the meeting minutes signed by both Sea Launch and Inmarsat at the completion
of the meeting.  Final documentation
from the meeting will be prepared and provided expediently.

 

Table 1.1.4-1.  Sea Launch Meetings and Reviews

 

	
  Item

  	
   

  	
  Purpose

  	
   

  	
  Schedule

  
	
  Kickoff
  Meeting

  	
   

  	
  Development
  of the contracted data requirements list and commitments, mission integration
  timelines and meeting and review schedules, formats and ground rules.

  	
   

  	
  Contract
  signature + 10 working days

  
	
  CDR

  	
   

  	
  Review
  the results of analyses and design activities

  	
   

  	
  L-6
  months

  
	
  Ground
  Operations Working Group Meetings

  	
   

  	
  Held
  at Home Port to evaluate operations requirements for SC, GSE, and personnel
  requirements for launch operations. The first meeting shall include
  finalization of the ICD.

  	
   

  	
  First
  meeting at Contract signature + 2 months Second meeting at L-4 months

  
	
  Readiness
  Reviews

  	
   

  	
  To
  ensure that all parties are ready to continue to the next phase of operation.

  	
   

  	
  L-2
  months to Launch

  

 

1.2          QUALITY

 

Sea
Launch shall maintain a mission success and quality assurance program for the
processes, procedures, and documentation in place at the Sea Launch’s
facilities and operations to ensure effective mission success and quality
assurance for the INMARSAT 4 mission.

 

Sea
Launch shall also present the design and qualification status of all new (not
previously flown) flight hardware whether mission unique or generic.  Appropriate reviews (CDR and HAR) shall be
held as defined in Table 1.1.4.

 

1.3          SAFETY

 

To
ensure safety related to the INMARSAT 4 mission, Sea Launch shall submit both
Sea Launch and Inmarsat safety data to the appropriate regulatory agencies, as
defined in the Sea Launch Safety Regulations
Manual.  Inmarsat shall
provide the safety inputs defined in Section 7, Table 7-1. Sea Launch
shall deliver the safety deliverables defined in Section 6, Table 6-1.

 

A-7

 

2.             LAUNCH VEHICLE

 

Sea
Launch shall supply all the LV hardware, software and consumables necessary to
provide the Launch Service.  This shall
include the design, manufacture, and qualification of all standard and mission-unique
hardware and software defined herein (Paragraph 2.1).

 

2.1          LAUNCH VEHICLE HARDWARE

 

Sea
Launch shall provide a 6000 Kg performance capable Zenit-3SL Launch Vehicle,
which consists of the Zenit-2S booster, the Block DM-SL upper stage, and
Payload Accommodations (PLA).  The PLA
consists of the spacecraft adapter (SCA), payload structure, interface skirt,
standard 4-meter payload fairing, flight avionics and instrumentation.

 

Sea
Launch will allocate hardware to the Inmarsat missions based on the existing
manifest within 2 months of the signing of the Launch Service Agreement.  Sea Launch shall provide a top-level
manufacturing schedule with major milestones including:

•      Block DM-SL manufacturing completion, integrated system testing, and
acceptance

•      Zenit-2S manufacturing completion, integrated system testing, and
acceptance

•      Payload Accommodation (fairing, interface skirt) assembly completion,
mission unique installations and testing, and acceptance

•      Delivery schedules for the Block DM-SL and Zenit-2S to Home Port

•      Delivery of the PLA to Home Port;

•      Delivery of mission unique flight tasks to Home Port

 

The
schedules will be updated based on completions of quarterly reviews with Sea
Launch subcontractors.  Sea Launch will
invite Inmarsat representatives to participate (subject to Technical Assistance
Agreements with our subcontractors) in the Hardware Acceptance Reviews at the
factories.  Sea Launch shall present a
summary called the Customer Hardware Acceptance Reviews to Inmarsat at Home
Port at approximately L-60 days.

 

Once
launch vehicle hardware is allocated to the Inmarsat mission, such hardware
shall not be re-allocated without Inmarsat’s prior written permission.

 

2.2          LAUNCH SYSTEM PERFORMANCE

 

2.2.1       Launch Vehicle Performance

 

The
launch vehicle shall provide an optimized geosynchronous transfer orbit to
maximize spacecraft on-orbit lifetime.

 

2.2.2       Mission Optimization

 

Sea
Launch shall optimize, within the constraints of the LV, the mission design
consistent with Paragraphs 2.2.1 above. 
The orbital parameters shall be optimized for the final design mass
(defined in Table 7-1, Item 3) and operational characteristics of the SC
(defined in Table 7-1,

 

A-8

 

Items
4 and 36).  Performance curves of the
Launch Vehicle shall be provided to Inmarsat to support this optimization.

 

For
each month for the 12 consecutive months, Sea Launch will design a launch
vehicle ascent trajectory that meets the customer’s orbital requirements. The
Zenit-2S portion of flight (first two stages) will at a maximum have two
trajectories, one for a northern launch azimuth and one for a southern launch
azimuth.  The Block DM-SL portion of
flight (third stage) will be unique for each month in order to satifsy the
argument of perigee requirement.

 

Vehicle
flight task development will begin at L-5 months.  Depending on the results of prior analyses, work will begin on
one or two Zenit-2S flight tasks plus three or four Block DM-SL flight tasks.  These flight tasks will cover the launch
slot plus subsequent months in order to ensure that all flight tasks will be
ready in the case of a launch delay.  As
the launch slot narrows or shifts, work on flight tasks that no longer apply
will be terminated, and possibly work on new flight tasks will begin.  Such modifications will be coordinated with
the customer.

 

The
maximum number of mission designs will be 12. The number of Block DM-SL flight
tasks is anticipated to be smaller, although that number could also be 12 if
delays in launch occurred right before the SC is supposed to arrive at Home
Port. Only 1 or 2 Zenit-2S flight tasks would be required. If the launch were
to slide outside the contractual launch period and the contract were extended,
Sea Launch will continue to produce additional mission designs and flight tasks
as necessary to protect the launch date.

 

2.2.2        Sea Launch will adopt a Block DM-SL two-burn injection strategy.  The Zenit-3SL lift-off shall be governed by
the requirement to achieve an inertial Right Ascension of the Ascending Node
(RAAN), which will be selected by Inmarsat.

 

It
shall be possible to vary the timing of the second Block DM-SL burn in order to
achieve a transfer orbit apse-line at a specified orientation to the Earth-Sun
line, in order to satisfy all satellite-related constraints.  This means that for launch throughout the
year, the argument of perigee of the transfer orbit can be in the range of 0
degree to 360 degrees.

 

In
order to achieve optimum lifetime conditions for the satellite for launch
throughout the year, Sea Launch shall allow for at least 12 different start
times for the second Block DM-SL burn.

 

The
integrated launch vehicle shall be capable of the performance into transfer
orbit indicated in the table below:

 

A-9

 

	
  Perigee
  Ht.

  (Km)

  	
   

  	
  Argument
  of Perigee Range

  (deg)

  	
   

  	
  Satellite
  Mass (Kg)

  
	
  218

  	
   

  	
  0 to 360

  	
   

  	
  5997

  
	
  250

  	
   

  	
  0 to 360

  	
   

  	
  5975

  
	
  300

  	
   

  	
  0 to 360

  	
   

  	
  5936

  
	
  350

  	
   

  	
  0 to 360

  	
   

  	
  5895

  
	
  400

  	
   

  	
  0 to 360

  	
   

  	
  5856

  

 

For
all of the above, the apogee height shall be 35786 Km, and the inclination
shall be 3.0 degrees.

 

Sea
Launch shall show mission feasibility, through detailed mission analyses, for
the full range of orbits that can arise with the above-defined launch strategy.

 

2.3          SPACECRAFT TO LAUNCH VEHICLE
INTERFACES

 

The
SC to LV interfaces are as specified in the herein-referenced sections of the Sea Launch User’s Guide and the Inmarsat -4 IRD,
reference document number 4. 
Once signed, the INMARSAT 4 to Sea Launch System ICD shall supersede the
interfaces defined here.

 

2.3.1       Mechanical Interfaces

 

The
Spacecraft shall be mated to the upper stage via a Saab Ericsson Space 1194VS
adapter and separation system.  The
adapter and the SC shall be encapsulated in the payload fairing prior to mating
with the Zenit-3SL.  The SC to LV
mechanical interfaces shall be compatible with the mechanical interfaces
specified in the Sea Launch User’s Guide,
Section 7.1 and the Inmarsat -4 IRD,
reference document number 4

 

2.3.2       Electrical Interfaces

 

Sea
Launch provided electrical interfaces shall include umbilical wiring, SC
telemetry and command links including RF re-radiation system and hardwire links
and in flight interfaces.  Inmarsat
shall provide separation connectors for the mission. Electrical interfaces
shall be as specified in the Sea Launch
User’s Guide, Section 7.2 and Sea
Launch Facilities Accommodations Handbook, Section 6 and the Inmarsat -4 IRD, reference document number 4.

 

 The launch vehicle adapter standard
configuration accommodates two SAE=AS81703-style connectors (37 pins or 61
pins). Inmarsat through Astrium shall supply both halves and provide the mating
half to Sea Launch for installation on the adapter.

 

Sea
Launch shall provide spacecraft umbilical charging capability of 70A maximum
total (35A per connector) up until L-8 hours and 20A maximum total after L-8
hours.

 

A-10

 

Sea
Launch shall provide an interface skirt umbilical path during transit to the
launch site.  The T-0 umbilical path is
not available during transit to the launch site.

 

Sea
Launch shall provide a re-radiation system for SC telemetry and command that
supports a frequency range of 3-18 GHz. Frequencies required outside this range
may be negotiated.

 

2.3.3       Spacecraft/Spacecraft
adapter interface test support

 

SC
to SCA interface tests are performed to verify proper fit and clearances of the
Sea Launch provided SCA and separation system with the SC, and to provide a
flight-representative separation shock environment for purposes of spacecraft
environmental verification.  Sea Launch,
with support from Inmarsat as specified in Section 6, shall perform one
matchmate test and one separation shock test between a Sea Launch provided SCA
and INMARSAT 4 spacecraft for each first-of-kind spacecraft bus type.  This test shall be performed at Astrium’s
factory.  For the matchmate test, both
the SCA and spacecraft shall be flight hardware.  Matchmate/separation tests on subsequent spacecraft of a
previously tested bus type may be negotiated, if requested by Inmarsat.  A “touch and go” between the SCA and SC will
also be conducted at Home Port shortly after SC arrival at Home Port, as agreed
to by Sea Launch and Inmarsat.

 

2.4          SPACECRAFT SEPARATION
CONDITIONS

 

Preliminary
injection accuracy, attitude accuracy, and minimum relative separation velocity
of the Block DM-SL at the time of SC separation shall be as specified in the Sea Launch User’s Guide, Section 3.5
and the the Inmarsat -4 IRD, reference document 4.  The final separation conditions shall be as specified in the ICD.

 

2.5          ENVIRONMENTAL REQUIREMENTS

 

Sea
Launch shall ensure that during transportation, handling, and from launch
through SC separation, the SC is not exposed to environments exceeding those
defined in the Sea Launch User’s Guide
Section 5, and Appendix 1.

 

2.6          CUSTOMER LOGO ON PAYLOAD
FAIRING

 

Inmarsat
shall have a cylindrical section of the payload fairing available for
logos.  Size, colors and locations of
logos are subject to approval by Sea Launch Management and Systems Engineering.

 

3.             MISSION ANALYSIS

 

Sea
Launch shall perform the following analyses for the INMARSAT 4 Mission to
ensure compatibility between the INMARSAT 4 SC/GSE and the Sea Launch System.
Inmarsat provided inputs to integration analysis are defined in Section 7.  A preliminary delivery schedule for
analysis results is defined in Table 6-1.

 

A-11

 

Table 3-1. Sea Launch Mission
Analysis Tasks

 

	
  Analysis

  	
   

  	
  Content

  
	
  Mission
  Design

  	
   

  	
  Trajectory,
  in-flight maneuvers, post separation, contamination and collision avoidance,
  injection accuracy, flight performance reviews, and Orbit Characteristics and
  Dispersions

  
	
  SC
  Acoustic Environment

  	
   

  	
  Predicted
  acoustic environment for a specific mission, considering the SC configuration
  and any unique PLU design

  
	
  Payload
  Fairing Separation

  	
   

  	
  Predicted
  clearance between the separated Payload Fairing halves and critical SC
  locations, confirmation that there is no re-contact between the separated
  halves and the integrated launch vehicle

  
	
  SC
  Separation

  	
   

  	
  Predicted
  SC and upper stage dynamics (spin/tumble rates and relative velocity) as well
  as relative clearance during the separation event

  
	
  Critical
  clearance analysis (dynamic)

  	
   

  	
  Minimum
  clearance between SC and PLU for CLA, PLF separation, encapsulations, and SC
  separation

  
	
  Coupled
  loads analysis

  	
   

  	
  SC
  loads for all critical flight events

  
	
  SC
  shock

  	
   

  	
  Predicted
  shock environment experienced by the SC resulting from SC separation and all
  other ILV events

  
	
  SC
  vibration

  	
   

  	
  Predicted
  vibration at the SC interface occurring during ILV liftoff and flight

  
	
  SC
  – PLA clearance analysis (static, for encapsulation)

  	
   

  	
  SC
  to PLA clearance during encapsulation, static clearance for horizontal and
  vertical states

  
	
  Thermal
  and Pressure

  	
   

  	
  Payload
  processing facility environmental control system (ECS), Transportation phase
  payload unit ECS, Pre-launch ECS, Flight thermal analysis (ascent phase-pre
  –fairing jettison, ascent phase post fairing jettison and flight), Payload
  compartment pressure venting analysis

  
	
  Contamination

  	
   

  	
  Generic
  Contamination Analysis Report, generic Contamination Control Plan, mission
  unique CCAM Plume Impingement Analysis, if required – a mission unique
  contamination analysis and/or contamination control plan, if required

  
	
  Avionics
  and Electrical Assessment

  	
   

  	
  On-pad
  RF link assessment of SC telemetry & command functions, EMC assessment
  for SC/PLU emissions and susceptibility

  
	
  Operations

  	
   

  	
  SC/GSE
  ground ops assessment, final planning of operations, facilities, GSE,
  personnel

  

 

4.             LAUNCH SERVICES AND
FACILITIES

 

Sea
Launch shall provide Inmarsat with pre-launch and launch-site facilities and
support services necessary for the processing, assembly, installation,
transportation, fueling, and launch of commercial SC.

 

A-12

 

4.1          SEA LAUNCH HOME PORT, LONG
BEACH, CALIFORNIA

 

4.1.1       Home Port Facilities

 

Sea
Launch shall provide facilities at the Home Port for SC processing, SC fueling,
and encapsulation into the payload fairing. 
Details of Sea Launch Payload Processing Facilities (PPF) and customer
office and storage areas are documented in the Sea
Launch Facilities Accommodations Handbook, Section 3.  Mission unique facility configurations shall
supersede the Sea Launch Facilities
Accommodations Handbook, and shall be specified in the ICD.

 

4.1.2       Home Port Services

 

Sea
Launch shall assist Inmarsat with arranging for transportation of the SC in its
shipping container and GSE from local airports to the Home Port.

 

Sea
Launch shall perform one fit check for each SC to verify the compatibility of
the mechanical and electrical interfaces between the SC and the SCA.  This fit check is accomplished at the Sea
Launch Payload Processing Facility at Home Port and does not include firing of
the separation system.

 

Sea
Launch shall provide SC environmental control during all phases of SC
processing, per the Sea Launch Facilities
Accommodations Handbook, Section 3.2.

 

Sea
Launch shall provide equipment as defined in the Sea Launch Facilities Accommodations Handbook,
Section 3.2.23 and 3.11.

 

Sea
Launch shall provide security services for INMARSAT 4 SC, SC GSE, and personnel
as defined in the Sea Launch Facilities
Accommodations Handbook, Section 3.8.

 

Sea
Launch shall provide miscellaneous services defined in the Sea Launch Facilities Accommodations Handbook,
Section 3.14.

 

4.2          ASSEMBLY AND COMMAND SHIP
(ACS)

 

4.2.1       Assembly Command Ship
Facilities

 

Sea
Launch shall provide facilities aboard the ACS for the mechanical and
electrical integration of the encapsulated SC with the Zenit 3SL prior to transfer
to the Launch Platform.  The ACS shall
provide provisions for INMARSAT 4 launch support, living accommodations,
customer office area and storage as defined in the Sea Launch Facilities
Accommodations Handbook, Section 4. 
Mission unique facility configurations shall be specified in the ICD.

 

4.2.2       Assembly Command Ship
Services

 

Sea
Launch shall provide meal, recreation, and medical services as defined in the Sea Launch Facilities Accommodations Handbook,
Section 4.5.

 

Sea
Launch shall provide security for INMARSAT 4 SC GSE and personnel as defined in
the Sea Launch Facilities Accommodations
Handbook, Section 4.6.

 

A-13

 

Sea
Launch shall provide miscellaneous services defined in the Sea Launch Facilities Accommodations Handbook,
Section 4.10.

 

Sea
Launch shall provide communication services as defined in the Sea Launch Facilities Accommodations Handbook,
Section 7.2.

 

4.3          LAUNCH PLATFORM (LP)

 

4.3.1       Launch Platform Facilities

 

Sea
Launch shall provide facilities on-board the Launch Platform (LP) for Inmarsat
4 GSE and SC monitoring, storage area, office area, and living accommodations
as defined in the Sea Launch Facilities
Accommodations Handbook, Section 5.  Mission unique facility configurations shall be specified in the
ICD.

 

4.3.2       Launch Platform Services

 

Sea
Launch shall provide meal, recreation, and medical services as defined in the Sea Launch Facilities Accommodations Handbook,
Section 5.4.

 

Sea
Launch shall provide security services for INMARSAT 4 SC, SC GSE and personnel
as defined in the Sea Launch Facilities
Accommodations Handbook, Section 5.5.

 

Sea
Launch shall provide communication services as defined in the Sea Launch Facilities Accommodations Handbook,
Section 7.2.

 

Sea
Launch shall provide SC environmental control during all phases of SC transit
and launch operations, as defined in Section 2.5 of this exhibit.

 

4.4          COMMUNICATIONS

 

Sea
Launch shall provide communications links for Inmarsat personnel between the
ACS, LP, Home Port, and external sites during SC Home Port processing and
mission operations as defined in the Sea
Launch Facilities Accommodations Handbook, Sections 7.1 and
7.2.  Communications between the ACS and
land facilities shall consist of telephones and internet connections.

 

Sea
Launch shall provide spacecraft communications, which link Inmarsat personnel
with the SC, as defined in the Sea Launch
Facilities Accommodations Handbook, Section 7.3.

 

4.5          LAUNCH SERVICES

 

The
following services are provided:

•      Sea Launch shall encapsulate the INMARSAT 4 SC in the launch vehicle
payload fairing in the PPF. Sea Launch shall transfer the encapsulated SC from
the PPF to the ACS.

•      Sea Launch shall integrate the encapsulated SC with the LV.

•      Sea Launch shall perform testing of the Integrated Launch Vehicle
(ILV).

•      Sea Launch shall transfer the ILV from the ACS to the LP.

 

A-14

 

•      Sea Launch shall transport the ACS and LP from Home Port to the launch
site and return to Home Port for the purpose of conducting the Launch.

•      Sea Launch shall conduct the launch of the SC during the launch window
specified in the ICD.

•      Sea Launch shall coordinate special services such as launch events, VIP
charter services to the launch site, and third party communications. Sea Launch
and Inmarsat shall agree upon specific requirements, logistics, participation,
and costs in advance, on a case-by-case basis.

 

4.6          RANGE SERVICES

 

Sea
Launch shall provide all necessary range telemetry assets and provide tracking
of the launch vehicle from launch through SC separation, via telemetry data
(real time or recorded).

 

Sea
Launch shall provide all necessary telemetry assets to verify LV functions and
conditions from Launch to SC separation. 
Telemetry (either real time or recorded) shall be provided during
powered flight and for discrete events.

 

5.             POST LAUNCH SERVICES

 

Sea
Launch shall provide the following post-launch services, according to the
schedule provided in Section 6:

•      Post-launch tracking and reporting, including SC post-separation
orbital parameters, to be delivered to Inmarsat at the launch site.

•      Post-launch Report.

 

6.             SEA LAUNCH RESPONSIBILITIES

 

In
addition to other obligations of Sea Launch as set forth in this SOW, Sea
Launch shall perform the tasks and provide the equipment and data specified
below at the approximate times indicated. 
Sea Launch and Inmarsat shall develop a program schedule that shall
contain calendar dates for the accomplishment of the scheduled tasks.

 

A-15

 

Table 6.1.  Sea Launch Deliverables

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Due
  Date*

  
	
  1.
  ICD

  	
   

  	
  Precisely
  defines the SC mission requirements and interfaces with the Launch Vehicle

  	
   

  	
  L-9.5
  months

  
	
  2.
  SC Campaign Document

  	
   

  	
  Provides
  detailed implementation of the customer requirements into the operations and
  facilities.

  	
   

  	
  L-2
  months

  
	
  3.
  Launch Description Document

  	
   

  	
  Provides
  management definition for the activities to be performed by the Sea Launch
  Company for the preparation and launch of the Zenit-3SL integrated launch
  vehicle.  The document contains
  mission requirements, conditions and constraints

  	
   

  	
  L-2
  weeks

  
	
  4.
  Master Countdown Procedure

  	
   

  	
  Controls
  and defines the launch preparation process. 
  Coordinates the activities of the Sea Launch partners and the customer
  to achieve a launch capability during the appointed launch window.  Defines the communications architecture
  and protocol to be used by all parties during launch operations.  Provides formal steps for safing and
  securing the launch vehicle and payload in the event of a launch abort after
  ILV erection.

  	
   

  	
  L-2
  weeks

  
	
  5.
  Launch Commit Criteria

  	
   

  	
  Defines
  the Sea Launch program commit process and criteria for deployment from Home
  Port to the Launch Site and for Launch Countdown operations.  It identifies operational limitations and
  constraints for the Sea Launch program.

  	
   

  	
  L-2
  weeks

  
	
  6.
  Verification Task Sheets

  	
   

  	
  Describe
  each requirement in the spacecraft ICD and how it was verified.

  	
   

  	
  L-2
  months

  
	
  7.
  Generic Contamination Plan

  	
   

  	
  Establishes
  a plan, requirements and responsibilities for contamination control during
  operations at the Sea Launch Home Port, and while onboard the Assembly and
  Command Ship and Launch Platform.

  	
   

  	
  L-10
  months

  
	
  8.
  Sea Launch Safety Regulations Manual

  	
   

  	
  The
  Sea Launch Safety Regulations Manual, D688-10024-1, provides the details for
  the spacecraft safety integration process as defined in Chapter 3 and Chapter
  4 of the document.  Spacecraft system
  design requirements are provided in Chapter 3 and operations planning and
  performance requirements are provided in Chapter 4.

  	
   

  	
  L-10
  months

  
	
  9.
  Process Safety Management Plan

  	
   

  	
  Addresses
  the regulatory safety requirements of California for the ability of the Sea
  Launch Home Port facility and operating personnel to accommodate the safe
  handling and transfer of customer propulsion system propellants.  The spacecraft propellants mononmethyl
  hydrazine and nitrogen tetroxide are included in a class of acutely hazardous
  materials requiring stringent hazard analysis and management.  The primary purpose of this plan is to
  address the safety of operating personnel.

  	
   

  	
  L-10
  months

  
	
  10.
  Risk Management Plan

  	
   

  	
  This
  document identifies the most credible hazard scenario for release of
  spacecraft propellants into the environment as a result of propellant related
  operations.  The primary purpose of
  this plan is to document the potential hazard to the surrounding community of
  Long Beach, CA as the result of the identified hazardous material release.

  	
   

  	
  L-10
  months

  
	
  11.
  EMC Control Plan

  	
   

  	
  Describes
  the EMC requirements, program controls, analyses, tests and specifications to
  be used for EMC assurance, as well as the engineering design, integration and
  test methods used to achieve and demonstrate system electromagnetic
  compatibility.

  	
   

  	
  L-10
  months

  

 

A-16

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Due
  Date*

  
	
  12.
  Design Review Package (CDR)

  	
   

  	
  Presents
  the results of the analyses and design work performed during the mission
  integration.  Also includes SC
  interface, operational and facility requirements and SL compliance status.

  	
   

  	
  L-6
  months

  
	
  13.
  Thermal Analysis Report

  	
   

  	
  Facility
  Environmental Control System (ECS) Analysis Report, Transportation phase PLU
  ECS Report, Prelaunch ECS Analysis Report

  	
   

  	
  L-6
  months

  
	
  14.
  Electromagnetic Compatibility Analysis

  	
   

  	
  Provides
  EMC analysis of SC compatibility with all aspects of the SL system.

  	
   

  	
  L-6
  months

  
	
  15.
  Venting Report

  	
   

  	
  Provides
  analysis results and confirms SL compatibility with the requirements in the
  ICD

  	
   

  	
  L-6
  months

  
	
  16.
  Coupled Loads Analysis Report

  	
   

  	
  Includes
  SC interface accelerations and section loads in addition to the
  accelerations and loads for the supplied SC acceleration transformation
  matrix and the supplied SC load transformation matrix.

  	
   

  	
  L-6
  months

  
	
  17.
  RF Link Analysis

  	
   

  	
  Analysis
  of spacecraft RF communications link on the launch pad.

  	
   

  	
  L-6
  months

  
	
  18.
  Fairing Separation Analysis

  	
   

  	
  Analyis
  of fairing dynamics during separation to ensure adequate clearances exist.

  	
   

  	
  L-6
  months

  
	
  19.
  Dynamic Clearance Analysis

  	
   

  	
  Analyis
  of expected spacecraft and fairing deflections during launch to ensure
  adequate clearances exist.

  	
   

  	
  L-6
  months

  
	
  20.
  Static Clearance Analysis

  	
   

  	
  Analyis
  of expected spacecraft and fairing deflections during
  processing/encapsulation to ensure adequate clearances exist.

  	
   

  	
  L-6
  months

  
	
  21.
  Acoustics, Vibration, and Shock Analysis

  	
   

  	
  Analysis
  of expected spacecraft acoustic, vibration, and shock environments.

  	
   

  	
  L-6
  months

  
	
  22.
  SC Separation Report

  	
   

  	
  Provides
  analysis results and confirms SL compatibility with the requirements in the
  ICD

  	
   

  	
  L-6
  months

  
	
  23.
  SC Injection orbit and attitude

  	
   

  	
  Provides
  SC separation data, including flight elements, state vector, orbital
  elements, attitude and attitude rates about the SC axes. SL will endeavour to
  provide preliminary data within 20 minutes

  	
   

  	
  Separation
  + 50 minutes

  
	
  24.
  Post Launch Report

  	
   

  	
  Contains
  analysis of prelaunch, launch, and flight data during the mission, including
  the actual environments seen by the SC as compared to values agreed to in the
  ICD.

  	
   

  	
  L+60
  days

  

 

*Dates
are considered preliminary until a final agreement is reached at the Kick-Off
Meeting

 

A-17

 

7.             INMARSAT RESPONSIBILITIES

 

In
addition to other obligations of Inmarsat as set forth in this Statement of
Work, Inmarsat shall perform the tasks and provide the equipment and data
specified below in Table 7.1 at the times indicated (Sea Launch and INMARSAT 4
Mission Managers will mutually agree to mission specific schedules).  Sea Launch and Inmarsat shall develop a
program schedule that shall contain calendar dates for the accomplishment
of the scheduled tasks.

 

Table 7.1.  Inmarsat Deliverables

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  1)
  Completed user questionnaire

  	
   

  	
  Questionnaire
  from the Sea Launch User’s Guide Preliminary information on spacecraft physical
  characteristics, flight design, electrical and mechanical interfaces,
  environments, ground processing requirements, and safety requirements

  	
   

  	
  N/A

  	
   

  	
  EDC

  
	
  2)
  Interface Requirements Document

  	
   

  	
  Red-lined
  Sea Launch ICD from a previous mission or Customer’s own Interface
  Requirements Document

  	
   

  	
  N/A

  	
   

  	
  EDC

  
	
  3)
  Spacecraft master schedule

  	
   

  	
  Top-level
  program schedule that shows key program milestones including contract
  go-ahead, critical design review, acoustic test, sine vib test, thermal vac
  test, spacecraft preship review, spacecraft ship, launch

  	
   

  	
  at
  EDC

  	
   

  	
  SC
  dellivery – 2 weeks

  
	
  4a)
  Mission Trajectory

  	
   

  	
  Spacecraft
  injection orbit

  

  SC mass to be used for mission design

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  4b)
  Flight Mechanics

  	
   

  	
  In-flight
  attitude constraints

  

  Spacecraft nominal separation parameters

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  5)
  Launch window

  	
   

  	
  Launch
  time and RAAN constraints

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  6)
  Spacecraft mass properties status reports

  	
   

  	
  Spacecraft
  mass

  

  Three-axis center of gravity

  

  Three-axis moment of inertia about center of gravity

  

  Three-axis product of inertia about center of gravity

  

  Mass properties uncertainty ranges

  	
   

  	
  L-10
  months

  	
   

  	
  L-4
  months, followed by as-weighed data at SC delivery + 5 days

  
	
  7)
  Spacecraft clearance CAD model

  	
   

  	
  Three-dimensional
  geometric math model of spacecraft external surfaces in STEP format

  	
   

  	
  L-10

  	
   

  	
  L-8
  months

  

 

A-18

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  8)
  Spacecraft thermal math model

  	
   

  	
  Atmospheric
  (pre-launch and ascent phases) and flight telemetry versions

  

  Timelines of events and sequences

  

  Dissipation and charging profiles for powered spacecraft components

  

  Definition of acceptable limits and ranges

  

  Maximum aero heating/free molecular heating constraints

  

  Solar exposure constraints (attitudes, durations)

  

  Thermal/timeline constraints and requirements on flight operations

  

  Preferences and restrictions on vehicle orientation, maneuvers, or attitudes

  

  Typical formats-SINDA-G/SINDA85

  	
   

  	
  N/A

  	
   

  	
  L-10 months

  
	
  9) Spacecraft external surfaces geometric
  math model

  	
   

  	
  Thermo-optical properties of external
  surfaces

  

  Map of GMM surfaces and corresponding thermal model nodes

  

  Typical formats-TRASYS, NEVADA, OPERA

  	
   

  	
  N/A

  	
   

  	
  L-10 months

  
	
  10) Spacecraft umbilical definition

  	
   

  	
  Connector part numbers (both halves)

  

  Umbilical pin-out and signal nomenclature

  

  Wiring shield arrangements

  

  Resistance and capacitance allocations

  	
   

  	
  N/A

  	
   

  	
  L-10 months

  
	
  11) Spacecraft in-flight command and
  telemetry requirements

  	
   

  	
  Base band signal characteristics

  

  Discrete command requirements

  

  Accelerometer interfaces

  

  Any special instrumentation requirements

  	
   

  	
  N/A

  	
   

  	
  L-10 months

  
	
  12) Agreement on safety data submittals
  format and schedule

  	
   

  	
  Format and review process to be implemented
  by the spacecraft customer and Sea Launch

  

  Schedule for processing and accepting the safety data

  	
   

  	
  N/A

  	
   

  	
  L-10 months

  
	
  13) Matchmate pyro-shock test option
  requirement definition

  	
   

  	
  Identify need to perform test

  

  Location of test

  	
   

  	
  N/A

  	
   

  	
  L-10 months

  

 

A-19

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  14)
  Phase I & II Customer prelaunch safety package

  	
   

  	
  Description
  of safety-significant spacecraft and support systems (Phase I)

  

  Hazard analysis identifying spacecraft system hazards (Phase I)

  

  Hazard controls to be implemented (Phase II)

  

  Phase II includes customer identification of previous mission hazardous
  procedures to be used for S/C Customer

  

  Phase II includes notification by customer of which changes to operations
  affect safety

  

  Exhaust products from spacecraft processing or system operation

  	
   

  	
  L-10
  months (Phase I, SC product-line Generic)

  	
   

  	
  SC
  delivery – 6 months (Phase II, S/C Customer specific)

  
	
  15)
  Spacecraft clocking definition

  	
   

  	
  Identification
  of restrictions on spacecraft orientation during horizontal processing

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  16)
  Access hatch location defined

  	
   

  	
  Quantity
  and location of lower access hatches

  	
   

  	
  L-10
  months

  	
   

  	
  L-8
  months (limited to aft end of barrel section)

  
	
  17)
  Spacecraft electrical ground support equipment definition

  	
   

  	
  Electrical
  power requirements

  

  Dimensions and mass

  

  Desired locations

  	
   

  	
  L-10
  months

  	
   

  	
  L-6
  months

  
	
  18)
  Spacecraft operations plan

  	
   

  	
  Spacecraft
  operations flow and timeline for the Home Port

  	
   

  	
  L-10
  Months

  	
   

  	
  L-6
  months

  
	
  19)
  Wiring/ cabling requirements and signal characteristics

  	
   

  	
  Electrical
  wiring diagrams and schematics for electrical equipment that interfaces with
  or through the launch vehicle (accelerometers only)

  

  Types of connectors, cables, wires, shields, bonding, and grounding

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  20)
  Spacecraft solar exposure constraints

  	
   

  	
  Solar
  exposure constraints

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  21)
  Spacecraft electromagnetic compatibility data

  	
   

  	
  Conducted
  and radiated emissions and susceptibility of the spacecraft system

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  22)
  Non-standard spacecraft facilities requirements

  	
   

  	
  Power,
  communications, and others

  	
   

  	
  N/A

  	
   

  	
  L-10
  months, with implementation details at L-6 months

  

 

A-20

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  23)
  Spacecraft radio frequency system characteristics

  	
   

  	
  Characteristics
  of SC T&C system, to include frequency, radio frequency power of
  transmitters, bandwidth, modulation, sensitivity of receivers, antenna
  polarization, antenna gain, and SC T&C antenna pattern (or power levels
  at selected bore sight angles)

  

  Spacecraft re-radiation requirements

  

  Radio frequency circuit losses for transmit and receive

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  24)
  Logo defined

  	
   

  	
  Desired
  logo of spacecraft customer delivered in electronic media (IGES, AI, or any
  PRO-E compatible format)

  	
   

  	
  N/A

  	
   

  	
  L10
  months

  
	
  25)
  Explosive policies/ procedures for matchmate test site

  	
   

  	
  Plans,
  procedures, and policies that govern explosive device transportation,
  storage, use, and disposal at the test site

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  26)
  Spacecraft thermal requirements

  	
   

  	
  Facility
  requirements

  

  General ambient environments

  

  Dedicated provisions (e.g., cooling air, purges)

  

  Pre-launch thermal soak requirements

  

  Maximum airflow velocities

  

  Thermal interface requirements

  

  Minimum/maximum interface attach point temperatures

  

  Heat flow across interface

  

  External environment requirements

  

  Minimum/maximum radiation sink temperature requirements

  

  Maximum aero-heating/free molecular heating constraints

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  27)
  Spacecraft environmental assessment data

  	
   

  	
  Unique
  design components or operations

  

  Radioactive materials

  

  Propellants and pressurized gases or liquids

  

  Reactive or toxic chemicals

  

  Structural materials

  

  Exhaust products from spacecraft processing or system operation

  

  Potential environmental effects from use or release of these items

  	
   

  	
  N/A

  	
   

  	
  L-10
  months

  
	
  28)
  Spacecraft breakup data list

  	
   

  	
  Identification
  of all spacecraft parts that can survive re-entry

  

  Data to include quantities, dimensions, and mass in metric units, material of
  the re-entered parts, and illustrations showing the location of the parts on
  the spacecraft

  	
   

  	
  N/A

  	
   

  	
  L-9
  months

  

 

A-21

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  29)
  Fluid/ propellant systems characteristics

  	
   

  	
  Inventory
  of fluid/propellant types, mass, and densities

  

  Three-axis center of gravity for fluids in each tank with fluid types
  specified

  

  Tank capacities

  

  Parameters of maximum loadable mass

  

  Ullage

  	
   

  	
  N/A

  	
   

  	
  L-9
  months

  
	
  30)
  Dynamic load model

  	
   

  	
  Craig-Bampton
  dynamic model of the spacecraft

  

  Model description and units

  

  Acceleration transformation matrix

  

  Loads transformation matrix

  

  Spacecraft modal damping and rigid body mass properties

  	
   

  	
  N/A

  	
   

  	
  L-8
  months

  
	
  31)
  Spacecraft volumetric properties

  	
   

  	
  Displaced
  volume

  	
   

  	
  N/A

  	
   

  	
  L-8
  months

  
	
  32)
  Spacecraft pressure requirements

  	
   

  	
  Maximum
  allowable residual pressure in fairing at jettison

  

  Maximum allowable rate of pressure decay in fairing

  	
   

  	
  N/A

  	
   

  	
  L-8
  months

  
	
  33)
  Spacecraft passage airflow characteristics

  	
   

  	
  Airflow
  characteristics between spacecraft internal cavities

  	
   

  	
  N/A

  	
   

  	
  L-8
  months

  
	
  34)
  Spacecraft contamination requirements

  	
   

  	
  Facility
  requirements

  

  Spacecraft surface molecular contamination requirements at launch and at
  spacecraft/upper stage separation

  

  Spacecraft surface particulate contamination requirements at launch and at
  spacecraft/upper stage separation

  

  Spacecraft debris requirements

  

  Location of contamination-sensitive surfaces

  

  Thermo-optical properties of contamination-sensitive surfaces

  

  Planned access to spacecraft after encapsulation

  

  Bagging and covering procedures during ground processing

  	
   

  	
  N/A

  	
   

  	
  L-8
  months if non-standard contamination requirements

  
	
  35)
  Measured data on radio frequency systems emissions

  	
   

  	
  Actual
  measured radio frequency characteristics of the spacecraft radio frequency
  transmitters, receivers, antennas, and related components

  	
   

  	
  L-8
  months

  	
   

  	
  L-6
  months

  
	
  36)
  Radio frequency systems on/off timeline

  	
   

  	
  On/off
  times of the radio frequency systems, including any autonomous testing,
  checkout, and actual countdown

  	
   

  	
  L-8
  months

  	
   

  	
  L-2
  months

  

 

A-22

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  37)
  Spacecraft hazardous procedures

  	
   

  	
  Final
  mission specific hazardous procedures to be used in payload processing
  facility, assembly and command ship, or launch platform

  	
   

  	
  L-8
  months

  	
   

  	
  SC
  delivery – 2 weeks

  
	
  38)
  Explosive license/ permit for matchmate test site

  	
   

  	
  Evidence
  of GovernmenL-issued license authorizing receipt and storage of explosive
  devices

  	
   

  	
  N/A

  	
   

  	
  L-7
  months

  
	
  39)
  Launch commit criteria

  	
   

  	
  Identification
  of launch go/no-go criteria for spacecraft

  	
   

  	
  L-6
  months

  	
   

  	
  L-2
  months

  
	
  40)
  Process safety management document

  	
   

  	
  Updates
  to baseline document containing descriptions of hazard analyses, controls
  implemented, hazard communication, employee training, and change management
  processes

  	
   

  	
  L-6
  months

  	
   

  	
  SC
  delivery – 2 weeks

  
	
  41)
  Results of qual testing (dynamic sine, static loads testing, or both)

  	
   

  	
  Sine
  vibration and static loads testing results

  	
   

  	
  N/A

  	
   

  	
  L-4
  months

  
	
  42)
  Spacecraft propellant tank and system certification package for Department of
  Transportation

  	
   

  	
  Data
  containing design factors employed in spacecraft propellant tanks and systems

  

  Tests conducted to verify tank manufacture and design integrity

  

  Acceptance test verification for the specific tanks used in the spacecraft

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 30 days

  
	
  43)
  Competent authority explosives classification approval for spacecraft
  transport

  	
   

  	
  Evidence
  of approval of spacecraft explosives for transportation of the spacecraft as
  issued by the Government transportation authority of the spacecraft
  manufacturer or owner responsible for spacecraft shipment to Sea Launch (new
  or continuing)

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 30 days

  
	
  44)
  Phase III Customer prelaunch safety package

  	
   

  	
  Updates
  to Phase II Package

  

  Verification of hazard control implementations

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 2 weeks

  
	
  45)
  Safety-critical equipment certification

  	
   

  	
  For
  the following types of equipment, list part #, location/type of
  certification:

  

  Propulsion system loading

  

  Spacecraft handling

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 7 days

  
	
  46)
  Personnel qualifications and certifications package

  	
   

  	
  Personnel
  operating safety-critical equipment or performing hazardous operations at Sea
  Launch facilities

  

  Package will show training completed, medical or other evaluations performed,
  certificates issued, and expiration dates for all certifications

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 7 days

  

 

A-23

 

	
  Item

  	
   

  	
  Typical
  contents

  	
   

  	
  Preliminary*

  	
   

  	
  Final*

  
	
  47)
  Hazardous materials inventory package

  	
   

  	
  List
  of hazardous materials to be brought to Sea Launch facilities, including
  quantities and methods of disposal

  

  Material safety data sheets for all hazardous materials brought to Sea Launch
  facilities

  

  Unique storage, handling, and personnel protection requirements involved with
  any of the hazardous materials

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 7 days

  
	
  48)
  Spacecraft interface control document verification package

  	
   

  	
  All
  reports that demonstrate completion of verification of requirements on the
  spacecraft customer in the mission-unique spacecraft/Sea Launch interface
  control document

  	
   

  	
  L-3
  months (status)

  	
   

  	
  L-1
  month

  
	
  49)
  Post-separation data

  	
   

  	
  Post
  separation spacecraft attitude and position data

  	
   

  	
  N/A

  	
   

  	
  L+5
  days

  
	
  50)
  Risk Management Plan Certification

  	
   

  	
  S/C
  Customer certification of compliance with SL Risk Management Plan

  	
   

  	
  N/A

  	
   

  	
  SC
  delivery – 2 weeks

  

 

*Dates
are considered preliminary until a final agreement is reached at the Kick-Off
Meeting

 

A-24

 

ANNEX A, APPENDIX 1

 

STATEMENT OF WORK

 

 

for

 

LAUNCH SERVICES

 

 

 

Inmarsat-4 program
main technical issues

 

You will find enclosed a summary
of the main technical topics for the INMARSAT-4 program, to be addressed during
the working meeting scheduled on the 11th and 12th of February.

 

Basically,
all requirements indicated in the document “INMARSAT 4/Sea Launch interface
requirement” reference INM4.SP.00002.S.MMS issue 2 revision 2 dated Feb. 2002
are still applicable.

 

The
main changes or updates are described in the following chapters.

 

The chapters concerning the
launch operations requirements will be updated later during further discussions
concerning launch campaign, most of the INTELSAT-X requirements may be
applicable (TBC by ASTRIUM).

 

1 INMARSAT-4
anticipated waivers to SL user’s guide

 

1.1   Acoustic environment:

 

The preliminary acoustic test plan that is planned for INMARSAT-4 is
described on figure 1.

 

Only a minor deviation of 0.1 db is requested in the 250 Hz octave band
Vs User’s guide requirements.

 

This should be acceptable since Sea Launch has already technically
approved a larger waiver in these frequency bands (See Boeing fax reference
JWE-02-016 dated 07 march 2002).

 

Since margins are large Vs measured flight limit levels, Sea Launch is
requested to confirm that the acoustic flight limit levels that will be
indicated in the ICD will be lower or equal to the Inmarsat flight limit levels
(acceptance) indicated on figure 1. In particular no additional margin will be
requested regarding fill factor effect or local acoustic protection removal
effect (very local area, that may be limited to the TMA thrusters).

 

1.2   Shock environment:

 

The
shock environment specified by Sea Launch when using the 1194VS low shock
separation system is described on figure 2.

 

The
Eurostar 3000 platforms have been qualified Vs the environment described on
Figure 3. Whatever the flight events, the maximum flight level shock at the
spacecraft separation plane shall not exceed that shown on Figure2. This
figures applies at a level of 12.5 cm above the separation plane, on the
satellite side. It is to be noted that this spectrum represents loads imparted
by clampband separation (i.e. mainly driven by radial shock inputs).

 

A
minimum margin of 3 dB has been considered for equipment qualification on top
of the environment generated by this shock environment.

 

Summary
of the methodology used for Eurostar 3000 qualification to shocks:

 

A
clampband release has been performed on the Eurostar 3000 STM. The separation
system used for this test was a classical 1194 SAAB separation system (about 30
kN band tension) equivalent to the Sea Launch standard SCA 1194 spacecraft
adaptor.

 

The
induced shock environment has been measured at most equipment locations.

 

The
qualification specifications for the equipment and subsystems have been derived
from the above measurements, using a minimum margin of 3 dB for qualification.

 

1

 

It
is considered that this approach is conservative Vs the needs for a flight on
Sea Launch for the following reasons:

 

•      The standard SCA 1194 separation system has
been used for qualification that should cover the shock levels induced by the
low shock separation system used for INMARSAT with the SCA 1194VS.

 

•      The shock attenuation into the flight models
should be higher for spacecraft flight models than for the STM due to the
presence of electrical harness, heat pipes and real equipment hardware. It
should generate more damping than the blank panels (no heat pipes nor
electrical harnesses) equipped with mass dummies that were mounted on the STM.

 

The shock qualification is thus basically achieved on ground at
subsystem level. The separation shocks tests that will be performed on the
INMARSAT flight models at system level will be used to confirm that the shock
attenuation is equal or lower than the STM and as an acceptance at system
level.

 

This should be basically the same waiver that was requested for
Intelsat-X (that was using the standard SCA1194 adaptor).

 

Sea Launch is requested to confirm that this approach is acceptable and
that the qualification to shock for launching on Sea Launch is acceptable even
the User’s guide shock specification shown on Figure 1 is not demonstrated.

 

Sea Launch is also requested to provide the qualification status of the
SCA1194VS adaptor as far as the measured shock levels induced by the low shock
separation system.

 

2. Main
technical topics and S/C requirements

 

2.1 S/C mass characteristics

 

The Centre of
gravity
coordinates are referenced in the S/C coordinate system, the origin being the
geometrical centre of the separation plane.

 

	
   

  	
   

  	
   

  	
   

  	
  CG
  Coordinates (m)

  	
   

  
	
   

  	
   

  	
  Mass (kg)

  	
   

  	
  Xs

  	
   

  	
  Ys

  	
   

  	
  Zs

  	
   

  
	
  SPACECRAFT

  	
   

  	
  6025

  	
   

  	
  0.018

  	
   

  	
  0.001

  	
   

  	
  1.909

  	
   

  
	
  Tolerances

  	
   

  	
  +/- 50

  	
   

  	
  (Xs2+Ys2)1/2 < 0.025

  	
   

  	
  +/- 0.025

  	
   

  

 

The moments of
inertia are
referenced in the S/C coordinate system where the origin is at the centre of
gravity of the S/C.

The products of
inertia are
calculated by the following equation: Pxy=+¿xydm

 

	
   

  	
   

  	
  Moment of
  inertia (kg.m2)

  	
   

  	
  Product of
  inertia (kg.m2)

  	
   

  
	
   

  	
   

  	
  Ixx

  	
   

  	
  Iyy

  	
   

  	
  Izz

  	
   

  	
  Pxy

  	
   

  	
  Pyz

  	
   

  	
  Pzx

  	
   

  
	
  SPACECRAFT

  	
   

  	
  14963

  	
   

  	
  14711

  	
   

  	
  5982

  	
   

  	
  152.8

  	
   

  	
  -11.2

  	
   

  	
  34.6

  	
   

  
	
  TOLERANCES

  	
   

  	
  +/- 5%

  	
   

  	
  +/- 30

  	
   

  	
  +/- 50

  	
   

  

 

For information the mass of 6025 kg corresponds to the full chemical
tanks configuration.

 

The +/- 50 kg tolerance value on the S/C mass corresponds to
uncertainties on the dry mass typical at this stage of the program.

 

2

 

The above characteristics will be updated in the coming weeks but are
close and conservative w.r.t. the upcoming values, and are good bases for the
preliminary analyses.

 

2.2 Orbital parameters at separation

 

The elements of the transfer orbit at injection shall be as follows
based on a separated mass of 6066 kg.

 

Any lighter mass of the SC shall be used to improve the orbital
parameters in order to minimise the Delta V required on the SC.

 

	
  Ha

  	
   

  	
  altitude of apogee (at apogee)

  	
   

  	
  35786 km

  
	
  Hp

  	
   

  	
  altitude at perigee (at perigee)

  	
   

  	
  200 km or higher

  
	
  I

  	
   

  	
  inclination

  	
   

  	
  between 0 and 3deg depending on the launch date

  
	
  o

  	
   

  	
  argument of perigee

  	
   

  	
  between -10o&+10o and between 170o&190o depending on the
  launch date

  
	
  o

  	
   

  	
  right ascension of ascending node

  	
   

  	
  free for optimisation

  

 

The argument of perigee will be optimised to achieve the INMARSAT
mission requirements. Sea Launch is requested to provide the performance losses
associated to the argument of perigee variation (in case of one or two burns
strategy).

 

The argument of perigee value will be associated with the launch window
for all days of the years in the range indicated above.

 

2.3 Separation mode and attitude pointing at separation

 

Separation at a spin rate of 2.5o/s (+/- 0.6o/s) about the satellite Z
axis. The transverse rates shall be not greater than 0.6 o/s at 3o.

 

The spacecraft attitude shall be such that the satellite Z-axis is
normal to the satellite-sun line and in the orbit plane. The spin axis pointing
error shall be less than 2.5o.

 

2.4 Umbilical connectors

 

The pin allocation for both umbilical connectors is described in Annex
1.

 

The references of 61 pins umbilical connectors to be procured at
Deutsch by Sea Launch on the LV side are the following:

 

•      “025 8210 61 ARIANE” on -Y SC side

•      “025 8214 61 ARIANE” on +Y SC side

 

3

 

2.5 Thermal constraints

 

The
thermal limitations are described in the IRD refered above.

 

Main
constraints are:

 

SC
LVA ring temperature has to remain above +5oC (LV uncertainties and margins
included)

 

Batteries
temperature must be limited to +25oC at the highest. In order to protect
batteries from overshoot the charge will be stop at 22oC (take into account
chemical phenomenon in the cells and thermal inertia).

 

The
3o overshoot on batteries temperature has been verified during charging tests
on INMARSAT batteries.

 

The
thermal analysis must thus demonstrate batteries temperature below 22oC since
overshoot cannot be simulated).

 

The
SC thermal model is available at ASTRIUM in a format acceptable by Sea Launch
(THERMICA, accordingly to J. Ellinthorpe).

 

Dedicated
ventilation is needed for battery charging onto the launcher up to a period as
close as possible from the launch (D-1?). The description of the access point
onto the SC as far as ventilation requirement has been provided to sea Launch
last early 2002 and is recalled on Figure4. We need one ventilation pipe per
battery, the other ventilation hole is used to vent the air directly into the
clean room or fairing cavity (no pipe is needed for outlet). Access to the four
holes in the batteries MLI through the fairing is needed since we need to close
the four ventilation holes prior flight.

 

2.6 Spacecraft CLA model

 

The
final Spacecraft CLA model to be used for LV analyses will be available week 6.

 

This
model is the final FEM model to be used for sine tests preparation.

 

The
Format (NASTRAN output 4) and size is acceptable by Sea Launch (accordingly to
J. Ellinthorpe).

 

2.7 SC CAD model

 

The
SC CAD model to be used for fairing accommodation should be available by mid
February (TBC by ASTRIUM).

 

The
IGES format is acceptable by Sea Launch (accordingly to J. Ellinthorpe).

 

The
most critical area (TMA and deployable reflector) should be slightly les
critical than in the preliminary model received by Sea Launch (TBC by ASTRIUM).

 

The
volume below the separation plane specific to INMARSAT is described on Figure5.

 

2.8 S/C radio compatibility

 

S/C
susceptibility to radiations is described on Figure 6.

 

S/Cradiated
emissions are described on figure 7.

 

4

 

2.9 ICD preparation

 

The
INMARSAT-4 / Sea Launch ICD has to be prepared based on the IRD referenced
above, including the updates enclosed in this document.

 

It
should be quicker to redline the INTELSAT-10 ICD, by incorporating the
INMARSAT-4 specific requirements.

 

Most
of the launch campaign requirements applicable to INTELSAT should be applicable
to INMARSAT, see IRD for specificities. This will be redlined with ASTRIUM
during the preliminary launch campaign preparation meeting (to be performed
soon in Long Beach).

 

Best
regards

 

5

 

FIGURE 1

INMARSAT-4 proposed levels for PFM&FMs
acoustic tests

 

	
  Octave

  Band

  (Hz)

  	
   

  	
  Sea Launch
  FLL

  User’s Guide

  Rev.B 07/2000

  (dB–Ref. 20 mPa)

  	
   

  	
  INM4
  Flight Limit

  Level

  (Agreed LMAO

  levels)

  (dB–Ref. 20 mPa)

  	
   

  	
  INM4
  Protoflight limit

  level

  (INM4 FLL+3dB)

  (dB–Ref. 20 mPa)

  	
   

  	
  Test
  tolerances

  (dB–Ref. 20 mPa)

  
	
  31.5

  	
   

  	
  124.5

  	
   

  	
  129.0

  	
   

  	
  132.0

  	
   

  	
  -2/+4

  
	
  63.0

  	
   

  	
  130.1

  	
   

  	
  134.0

  	
   

  	
  137.0

  	
   

  	
  -1/+3

  
	
  125.0

  	
   

  	
  134.8

  	
   

  	
  136.0

  	
   

  	
  139.0

  	
   

  	
  -1/+3

  
	
  250.0

  	
   

  	
  138.1

  	
   

  	
  138.0

  	
   

  	
  141.0

  	
   

  	
  -1/+3

  
	
  500.0

  	
   

  	
  134.1

  	
   

  	
  135.0

  	
   

  	
  138.0

  	
   

  	
  -1/+3

  
	
  1000.0

  	
   

  	
  127.8

  	
   

  	
  129.0

  	
   

  	
  132.0

  	
   

  	
  -1/+3

  
	
  2000.0

  	
   

  	
  123.8

  	
   

  	
  125.0

  	
   

  	
  128.0

  	
   

  	
  -1/+3

  
	
  4000.0

  	
   

  	
  120.3

  	
   

  	
  121.0

  	
   

  	
  124.0

  	
   

  	
  -4/+4

  
	
  8000.0

  	
   

  	
  116.3

  	
   

  	
  117.9

  	
   

  	
  120.9

  	
   

  	
  -4/+4

  
	
  OASPL

  	
   

  	
  141.6

  	
   

  	
  142.6

  	
   

  	
  145.6

  	
   

  	
  -1/+3

  

 

6

 

FIGURE 2

 

FIGURE 3

 

7

 

FIGURE 4

 

Coordinates
of the center of the two batteries ventilation holes (per battery pack).

 

These
coordinates are given with reference to the S/C coordinate system origin
located at the center of the S/C separation plane (X, Y, Z) :

 

	
  A= 1042.425 , -857.5 , -145.75

  	
   

  	
  B= 1042.425 , 857.5 , -145.75

  

 

 

	
  D= -1042.425, -857.5, -145.75

  	
   

  	
  C= -1042.425, 857.5, -145.75

  

 

8

 

FIGURE 5

Volume below the separation plane

 

9

 

 

10

 

FIGURE6

 

INMARSAT-4
susceptibility to radiations

 

 

	
  Frequency (MHz)

  	
   

  	
  E_Field
  (dBmV/m)

  	
   

  
	
  0.0001

  	
   

  	
  120

  	
   

  
	
  1000

  	
   

  	
  120

  	
   

  
	
  1000

  	
   

  	
  148

  	
   

  
	
  6338.5

  	
   

  	
  148

  	
   

  
	
  6338.5

  	
   

  	
  80

  	
   

  
	
  6340.5

  	
   

  	
  80

  	
   

  
	
  6340.5

  	
   

  	
  148

  	
   

  
	
  30000

  	
   

  	
  148

  	
   

  

 

The
susceptibility level is at equipment surface. To evaluate the effect of the
launcher radiated field on the L/V onto S/C TC receivers, the launcher
radiation level at S/C separation plane region must be attenuated by 33 dB to
account for the presence of S/C structures and MLI and the location of the TC
receivers inside the S/C.

 

11

 

FIGURE 7

 

INMARSAT-4
radiated emissions (TM emitters OFF)

 

 

	
  F (MHz)

  	
   

  	
  E-Field

  (dBmV/m)

  	
   

  	
  F (MHz)

  	
   

  	
  E-Field

  (dBmV/m)

  	
   

  
	
  1

  	
   

  	
  29.4

  	
   

  	
  200.00

  	
   

  	
  40.7

  	
   

  
	
  2.00

  	
   

  	
  29.4

  	
   

  	
  200.00

  	
   

  	
  37

  	
   

  
	
  2.00

  	
   

  	
  30.5

  	
   

  	
  300.00

  	
   

  	
  37

  	
   

  
	
  3.00

  	
   

  	
  30.5

  	
   

  	
  300.00

  	
   

  	
  32.5

  	
   

  
	
  3.00

  	
   

  	
  27.5

  	
   

  	
  400.00

  	
   

  	
  32.5

  	
   

  
	
  5.00

  	
   

  	
  27.5

  	
   

  	
  400.00

  	
   

  	
  30.7

  	
   

  
	
  5.00

  	
   

  	
  28.3

  	
   

  	
  500.00

  	
   

  	
  30.7

  	
   

  
	
  6.00

  	
   

  	
  28.3

  	
   

  	
  500.00

  	
   

  	
  30.8

  	
   

  
	
  6.00

  	
   

  	
  32.7

  	
   

  	
  600.00

  	
   

  	
  30.8

  	
   

  
	
  7.00

  	
   

  	
  32.7

  	
   

  	
  600.00

  	
   

  	
  32.4

  	
   

  
	
  7.00

  	
   

  	
  39.3

  	
   

  	
  700.00

  	
   

  	
  32.4

  	
   

  
	
  8.00

  	
   

  	
  39.3

  	
   

  	
  700.00

  	
   

  	
  30

  	
   

  
	
  8.00

  	
   

  	
  41.3

  	
   

  	
  800.00

  	
   

  	
  30

  	
   

  
	
  9.00

  	
   

  	
  41.3

  	
   

  	
  800.00

  	
   

  	
  27.7

  	
   

  
	
  9.00

  	
   

  	
  47.2

  	
   

  	
  1000.00

  	
   

  	
  27.7

  	
   

  
	
  10.00

  	
   

  	
  47.2

  	
   

  	
  1000.00

  	
   

  	
  27.6

  	
   

  
	
  10.00

  	
   

  	
  59

  	
   

  	
  1500.00

  	
   

  	
  27.6

  	
   

  
	
  20.00

  	
   

  	
  59

  	
   

  	
  1500.00

  	
   

  	
  26.1

  	
   

  
	
  20.00

  	
   

  	
  48.1

  	
   

  	
  1575.00

  	
   

  	
  26.1

  	
   

  
	
  30.00

  	
   

  	
  48.1

  	
   

  	
  1575.00

  	
   

  	
  10.4

  	
   

  
	
  30.00

  	
   

  	
  33.9

  	
   

  	
  1660.50

  	
   

  	
  10.4

  	
   

  
	
  40.00

  	
   

  	
  33.9

  	
   

  	
  1660.50

  	
   

  	
  26.7

  	
   

  
	
  40.00

  	
   

  	
  34.8

  	
   

  	
  1930.00

  	
   

  	
  26.7

  	
   

  
	
  60.00

  	
   

  	
  34.8

  	
   

  	
  1930.00

  	
   

  	
  15.4

  	
   

  
	
  60.00

  	
   

  	
  33.5

  	
   

  	
  2690.00

  	
   

  	
  15.4

  	
   

  
	
  80.00

  	
   

  	
  33.5

  	
   

  	
  2690.00

  	
   

  	
  26.1

  	
   

  
	
  80.00

  	
   

  	
  43.3

  	
   

  	
  5850.00

  	
   

  	
  26.1

  	
   

  
	
  100.00

  	
   

  	
  43.3

  	
   

  	
  5850.00

  	
   

  	
  29.1

  	
   

  
	
  100.00

  	
   

  	
  43.8

  	
   

  	
  6500.00

  	
   

  	
  29.1

  	
   

  
	
  150.00

  	
   

  	
  43.8

  	
   

  	
  6500.00

  	
   

  	
  26.1

  	
   

  
	
  150.00

  	
   

  	
  40.7

  	
   

  	
  47000.00

  	
   

  	
  26.1

  	
   

  

 

S/C
attenuation through the MLI and walls is included (20 dB).

The
S/C telemetry is OFF in these figures.

These
levels apply at the S/C separation plane.

 

12

 

ANNEX 1 : 61 LINKS CONFIGURATION : UMBILICAL CONNECTORS PIN ALLOCATION
(1/2)

 

Connecteur P1 (-Y)

 

	
  Pin

  Nb

  	
   

  	
  Function

  	
   

  	
  Max

  Volt

  (V)

  	
   

  	
  Mx

  Current

  (Amp)

  	
   

  	
  Specific
  Requirement

  	
   

  	
  P(ower)

  or

  S(ignal)

  
	
  1

  	
   

  	
  SCUA TCaux DATA RTN

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 6, shielded

  	
   

  	
  S

  
	
  2

  	
   

  	
  SCUA TCaux PRESENCE RTN

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 7, shielded

  	
   

  	
  S

  
	
  3

  	
   

  	
  SCUA TCaux CLOCK RTN

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 10, shielded

  	
   

  	
  S

  
	
  4

  	
   

  	
  spare

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
  S

  
	
  5

  	
   

  	
  spare

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
  S

  
	
  6

  	
   

  	
  SCUA TCaux DATA

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 1, shielded

  	
   

  	
  S

  
	
  7

  	
   

  	
  SCUA TCaux PRESENCE

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 2, shielded

  	
   

  	
  S

  
	
  8

  	
   

  	
  LAUNCHER -Y STRAP

  	
   

  	
  —

  	
   

  	
  —

  	
   

  	
  Strapped to 9 in spacecraft (launcher use)

  	
   

  	
  S

  
	
  9

  	
   

  	
  LAUNCHER -Y STRAP RTN

  	
   

  	
  —

  	
   

  	
  —

  	
   

  	
  Strapped to 8 in spacecraft (launcher use)

  	
   

  	
  S

  
	
  10

  	
   

  	
  SCUA TCaux CLOCK

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 3, shielded

  	
   

  	
  S

  
	
  11

  	
   

  	
  SCUA AUXILIARY TM

  	
   

  	
  1,75

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 24, shielded

  	
   

  	
  S

  
	
  12

  	
   

  	
  SCUA RX DATA COMP

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 26, shielded

  	
   

  	
  S

  
	
  13

  	
   

  	
  LV INHIBITION

  	
   

  	
  5

  	
   

  	
  <0.005

  	
   

  	
  Strapped to 28 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  14

  	
   

  	
  SHIELDING

  	
   

  	
  —

  	
   

  	
  —

  	
   

  	
  Shield

  	
   

  	
  S

  
	
  15

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 18

  	
   

  	
  P

  
	
  16

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 19

  	
   

  	
  P

  
	
  17

  	
   

  	
  BAT1 RELAY CD RTN

  	
   

  	
  0V

  	
   

  	
  <3.5

  	
   

  	
  Twisted with 35 and 58

  	
   

  	
  P

  
	
  18

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 15

  	
   

  	
  P

  
	
  19

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 16

  	
   

  	
  P

  
	
  20

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 33

  	
   

  	
  P

  
	
  21

  	
   

  	
  SEP - Y DETECTION

  	
   

  	
  5

  	
   

  	
  0,001

  	
   

  	
  Strapped to 22 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  22

  	
   

  	
  SEP -Y DETECTION RTN

  	
   

  	
  0V

  	
   

  	
  0,001

  	
   

  	
  Strapped to 21 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  23

  	
   

  	
  SCUA TCaux TONE EXECUTE

  	
   

  	
  5

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 43, shielded

  	
   

  	
  S

  
	
  24

  	
   

  	
  SCUA AUXILIARY TM RTN

  	
   

  	
  0V

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 11, shielded

  	
   

  	
  S

  
	
  25

  	
   

  	
  SCUA AUXILIARY TM DWELL

  	
   

  	
  1,25

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 44, shielded

  	
   

  	
  S

  
	
  26

  	
   

  	
  SCUA RX DATA TRUE

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 12, shielded

  	
   

  	
  S

  
	
  27

  	
   

  	
  BAT1 RELAY ST

  	
   

  	
  5

  	
   

  	
  0,001

  	
   

  	
  Twisted with 47

  	
   

  	
  S

  
	
  28

  	
   

  	
  LV INHIBITION return

  	
   

  	
  5

  	
   

  	
  <0.005

  	
   

  	
  Strapped to 13 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  29

  	
   

  	
  SCUA AUXILIARY TM

  	
   

  	
  1,75

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 30, shielded

  	
   

  	
  S

  
	
  30

  	
   

  	
  SCUA AUXILIARY TM RTN

  	
   

  	
  0V

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 29, shielded

  	
   

  	
  S

  
	
  31

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 36

  	
   

  	
  P

  
	
  32

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 37

  	
   

  	
  P

  
	
  33

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 20

  	
   

  	
  P

  
	
  34

  	
   

  	
  Bus 2 voltage (NC in 1 PSR conf)

  	
   

  	
  5

  	
   

  	
  <0.0025

  	
   

  	
  Shielded,

  	
   

  	
  S

  

 

13

 

	
  35

  	
   

  	
  BAT1 RELAY OFF CD

  	
   

  	
  28

  	
   

  	
  <3.5

  	
   

  	
  Twisted with 17 and 58

  	
   

  	
  P

  
	
  36

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 31

  	
   

  	
  P

  
	
  37

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 32

  	
   

  	
  P

  
	
  38

  	
   

  	
  BUS1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 52

  	
   

  	
  P

  
	
  39

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 56

  	
   

  	
  P

  
	
  40

  	
   

  	
  BAT1 VOLTAGE

  	
   

  	
  50

  	
   

  	
  <0.05

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  41

  	
   

  	
  PSRA 0V MEASURE

  	
   

  	
  0V

  	
   

  	
  <0.05

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  42

  	
   

  	
  BUS1 VOLTAGE

  	
   

  	
  5

  	
   

  	
  <0.0025

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  43

  	
   

  	
  SCUA TCaux TONE EXECUTE RTN

  	
   

  	
  5

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 23, shielded

  	
   

  	
  S

  
	
  44

  	
   

  	
  SCUA AUXILIARY TM DWELL RTN

  	
   

  	
  0V

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 25, shielded

  	
   

  	
  S

  
	
  45

  	
   

  	
  SCUA TX DATA TRUE

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 46, shielded

  	
   

  	
  S

  
	
  46

  	
   

  	
  SCUA TX DATA COMP

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 45, shielded

  	
   

  	
  S

  
	
  47

  	
   

  	
  BAT1 RELAY ST RTN

  	
   

  	
  0V

  	
   

  	
  0,001

  	
   

  	
  Twisted with 27

  	
   

  	
  S

  
	
  48

  	
   

  	
  BAT1 TEMPERATURE

  	
   

  	
  5

  	
   

  	
  0,0005

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  49

  	
   

  	
  BAT1 CURRENT (+)

  	
   

  	
  5

  	
   

  	
  <0.0025

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  50

  	
   

  	
  BUS1 CURRENT

  	
   

  	
  5

  	
   

  	
  <0.0025

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  51

  	
   

  	
  BAT1 BDRs INPUT VOLTAGE

  	
   

  	
  50

  	
   

  	
  <0.05

  	
   

  	
  Shielded

  	
   

  	
  S

  
	
  52

  	
   

  	
  BUS SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 38

  	
   

  	
  P

  
	
  53

  	
   

  	
  BUS SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 61

  	
   

  	
  P

  
	
  54

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 59

  	
   

  	
  P

  
	
  55

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 60

  	
   

  	
  P

  
	
  56

  	
   

  	
  BDR1 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 39

  	
   

  	
  P

  
	
  57

  	
   

  	
  XENON TEMPERATURE

  	
   

  	
  5

  	
   

  	
  0,0005

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  58

  	
   

  	
  BAT1 RELAY ON CD

  	
   

  	
  28

  	
   

  	
  <3.5

  	
   

  	
  Twisted with 17 and 35

  	
   

  	
  P

  
	
  59

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 54

  	
   

  	
  P

  
	
  60

  	
   

  	
  BDR1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 55

  	
   

  	
  P

  
	
  61

  	
   

  	
  BUS1 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 53

  	
   

  	
  P

  

 

(*)
Only for NIH2 Battery. Otherwise pins not wired

 

14

 

ANNEX 1 : 61 LINKS CONFIGURATION : UMBILICAL CONNECTORS PIN ALLOCATION
(2/2)

 

Connecteur P2 (+Y)

 

	 
	
  Pin

  Nb

  	
   

  	
  Function

  	
   

  	
  Max

  Volt

  (V)

  	
   

  	
  Mx

  Current

  (Amp)

  	
   

  	
  Specific
  Requirement

  	
   

  	
  P(ower)

  or

  S(ignal)

  	 

	
  1

  	
   

  	
  SCUB TCaux DATA RTN

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 6, shielded

  	
   

  	
  S

  
	
  2

  	
   

  	
  SCUB TCaux PRESENCE RTN

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 7, shielded

  	
   

  	
  S

  
	
  3

  	
   

  	
  SCUB TCaux CLOCK RTN

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 10, shielded

  	
   

  	
  S

  
	
  4

  	
   

  	
  spare

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
  S

  
	
  5

  	
   

  	
  spare

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
  S

  
	
  6

  	
   

  	
  SCUB TCaux DATA

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 1, shielded

  	
   

  	
  S

  
	
  7

  	
   

  	
  SCUB TCaux PRESENCE

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 2, shielded

  	
   

  	
  S

  
	
  8

  	
   

  	
  LAUNCHER +Y STRAP

  	
   

  	
  —

  	
   

  	
  —

  	
   

  	
  Strapped to 9 in spacecraft (launcher use)

  	
   

  	
  S

  
	
  9

  	
   

  	
  LAUNCHER +Y STRAP RTN

  	
   

  	
  —

  	
   

  	
  —

  	
   

  	
  Strapped to 8 in spacecraft (launcher use)

  	
   

  	
  S

  
	
  10

  	
   

  	
  SCUB TCaux CLOCK

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 3, shielded

  	
   

  	
  S

  
	
  11

  	
   

  	
  SCUB AUXILIARY TM

  	
   

  	
  1,75

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 24, shielded

  	
   

  	
  S

  
	
  12

  	
   

  	
  SCUB RX DATA COMP

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 26, shielded

  	
   

  	
  S

  
	
  13

  	
   

  	
  LV INHIBITION

  	
   

  	
  5

  	
   

  	
  <0.005

  	
   

  	
  Strapped to 28 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  14

  	
   

  	
  SHIELDING

  	
   

  	
  —

  	
   

  	
  —

  	
   

  	
  Shield

  	
   

  	
  S

  
	
  15

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 18

  	
   

  	
  P

  
	
  16

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 19

  	
   

  	
  P

  
	
  17

  	
   

  	
  BAT2 RELAY CD RTN

  	
   

  	
  0V

  	
   

  	
  <3.5

  	
   

  	
  Twisted with 35 and 58

  	
   

  	
  P

  
	
  18

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 15

  	
   

  	
  P

  
	
  19

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 16

  	
   

  	
  P

  
	
  20

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 33

  	
   

  	
  P

  
	
  21

  	
   

  	
  SEP + Y DETECTION

  	
   

  	
  5

  	
   

  	
  0,001

  	
   

  	
  Strapped to 22 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  22

  	
   

  	
  SEP +Y DETECTION RTN

  	
   

  	
  0V

  	
   

  	
  0,001

  	
   

  	
  Strapped to 21 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  23

  	
   

  	
  SCUB TC TONE EXECUTE

  	
   

  	
  5

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 43, shielded

  	
   

  	
  S

  
	
  24

  	
   

  	
  SCUB AUXILIARY TM RTN

  	
   

  	
  0V

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 11, shielded

  	
   

  	
  S

  
	
  25

  	
   

  	
  SCUB AUXILIARY TM DWELL

  	
   

  	
  1,25

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 44, shielded

  	
   

  	
  S

  
	
  26

  	
   

  	
  SCUB RX DATA TRUE

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 12, shielded

  	
   

  	
  S

  
	
  27

  	
   

  	
  BAT2 RELAY ST

  	
   

  	
  5

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 47

  	
   

  	
  S

  
	
  28

  	
   

  	
  LV INHIBITION return

  	
   

  	
  5

  	
   

  	
  <0.005

  	
   

  	
  Strapped to 13 in launcher adaptor (S/C use)

  	
   

  	
  S

  
	
  29

  	
   

  	
  SCUB AUXILIARY TM

  	
   

  	
  1,75

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 30, shielded

  	
   

  	
  S

  
	
  30

  	
   

  	
  SCUB AUXILIARY TM RTN

  	
   

  	
  0V

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 29, shielded

  	
   

  	
  S

  
	
  31

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 36

  	
   

  	
  P

  
	
  32

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 37

  	
   

  	
  P

  
	
  33

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 20

  	
   

  	
  P

  
	
  34

  	
   

  	
  XENON / HELIUM TEMPERATURE RTN

  	
   

  	
  0V

  	
   

  	
  0,0005

  	
   

  	
  Shielded,

  	
   

  	
  S

  
																	

 

15

 

	
  35

  	
   

  	
  BAT2 RELAY OFF CD

  	
   

  	
  28

  	
   

  	
  <3.5

  	
   

  	
  Twisted with 17 and 58

  	
   

  	
  P

  
	
  36

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 31

  	
   

  	
  P

  
	
  37

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 32

  	
   

  	
  P

  
	
  38

  	
   

  	
  BUS1 SUPPLY or Bus 2 supply in 2 PSR conf

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 52

  	
   

  	
  P

  
	
  39

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 56

  	
   

  	
  P

  
	
  40

  	
   

  	
  BAT2 VOLTAGE

  	
   

  	
  50

  	
   

  	
  <0.05

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  41

  	
   

  	
  PSRA 0V MEAS or PSRB 0V measure in 2 PSR conf

  	
   

  	
  0V

  	
   

  	
  <0.05

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  42

  	
   

  	
  Bus2 current or NC in 1 pSR conf

  	
   

  	
  0V

  	
   

  	
  <0.005

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  43

  	
   

  	
  SCUB TC TONE EXECUTE RTN

  	
   

  	
  5

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 23, shielded

  	
   

  	
  S

  
	
  44

  	
   

  	
  SCUB AUXILIARY TM DWELL RTN

  	
   

  	
  0V

  	
   

  	
  <0.01

  	
   

  	
  Twisted with 25, shielded

  	
   

  	
  S

  
	
  45

  	
   

  	
  SCUB TX DATA TRUE

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 46, shielded

  	
   

  	
  S

  
	
  46

  	
   

  	
  SCUB TX DATA COMP

  	
   

  	
  5

  	
   

  	
  <0.05

  	
   

  	
  Twisted with 45, shielded

  	
   

  	
  S

  
	
  47

  	
   

  	
  BAT2 RELAY ST RTN

  	
   

  	
  0V

  	
   

  	
  <0.001

  	
   

  	
  Twisted with 27

  	
   

  	
  S

  
	
  48

  	
   

  	
  BAT2 TEMPERATURE

  	
   

  	
  5

  	
   

  	
  0,0005

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  49

  	
   

  	
  BAT2 CURRENT (+)

  	
   

  	
  5

  	
   

  	
  <0.0025

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  50

  	
   

  	
  BATTERY TEMP RTN

  	
   

  	
  0V

  	
   

  	
  <0.001

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  51

  	
   

  	
  BAT2 BDRs INPUT VOLTAGE

  	
   

  	
  50

  	
   

  	
  <0.05

  	
   

  	
  Shielded

  	
   

  	
  S

  
	
  52

  	
   

  	
  BUS SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 38

  	
   

  	
  P

  
	
  53

  	
   

  	
  BUS SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 61

  	
   

  	
  P

  
	
  54

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 59

  	
   

  	
  P

  
	
  55

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 60

  	
   

  	
  P

  
	
  56

  	
   

  	
  BDR2 SUPPLY RTN

  	
   

  	
  0V

  	
   

  	
  <5

  	
   

  	
  Twisted with 39

  	
   

  	
  P

  
	
  57

  	
   

  	
  HELIUM TEMPERATURE

  	
   

  	
  5

  	
   

  	
  0,0005

  	
   

  	
  Shielded,

  	
   

  	
  S

  
	
  58

  	
   

  	
  BAT2 RELAY ON CD

  	
   

  	
  28

  	
   

  	
  <3.5

  	
   

  	
  Twisted with 17 and 35

  	
   

  	
  P

  
	
  59

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 54

  	
   

  	
  P

  
	
  60

  	
   

  	
  BDR2 SUPPLY

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 55

  	
   

  	
  P

  
	
  61

  	
   

  	
  BUS1 SUPPLY or Bus2 supply in 2 PSR conf

  	
   

  	
  50

  	
   

  	
  <5

  	
   

  	
  Twisted with 53

  	
   

  	
  P

  

 

(*)
Only for NIH2 Battery. Otherwise pins not wired

 

16Exhibit 10.7

 

	
  

  	
   

  	
  Contract No. INM-CO/01-2876/HC

  

 

 

INMARSAT
LIMITED

99 City Road, London EC1Y 1AX, England

 

 

Contract No.
INM –CO/01-2876/HC

 

 

for

 

Broadband
Global Area Network (BGAN) Radio Access Network (RAN)

 

 

with

 

 

THRANE
& THRANE A/S

Lundtoftegårdsvej 93D, DK-2800 Lyngby, Denmark

 

 

Proprietary &
Confidential

 

 

INMARSAT
CONTRACT

TERMS AND
CONDITIONS

Table of
Contents

 

	
  Article

  	
   

  	
  Title

  	
   

  
	
  Preamble

  	
   

  	
   

  	
   

  
	
  1

  	
   

  	
  Scope of Work

  	
   

  
	
  2

  	
   

  	
  Delivery
  by Contractor

  	
   

  
	
  3

  	
   

  	
  Performance
  Schedule

  	
   

  
	
  4

  	
   

  	
  Price

  	
   

  
	
  5

  	
   

  	
  Final Acceptance

  	
   

  
	
  6

  	
   

  	
  Taxes and
  Duties

  	
   

  
	
  7

  	
   

  	
  Payment Terms

  	
   

  
	
  8

  	
   

  	
  Contractor
  Deliverables, Title and Assumptions of Risk

  	
   

  
	
  9

  	
   

  	
  Warranty
  as to Quality

  	
   

  
	
  10

  	
   

  	
  Access to Work in
  Progress and Data

  	
   

  
	
  11

  	
   

  	
  Inmarsat’s
  Rights in Technical Data and Inventions

  	
   

  
	
  12

  	
   

  	
  Patents For
  Foreground Inventions

  	
   

  
	
  13

  	
   

  	
  Intellectual
  Property Right Indemnity

  	
   

  
	
  14

  	
   

  	
  Loss and Damage,
  Indemnity

  	
   

  
	
  15

  	
   

  	
  Inmarsat-Furnished
  Property and Facilities

  	
   

  
	
  16

  	
   

  	
  Inmarsat-Furnished
  Documents, Examination

  	
   

  
	
  17

  	
   

  	
  Confidentiality

  	
   

  
	
  18

  	
   

  	
  Public Release of
  Information

  	
   

  
	
  19

  	
   

  	
  Termination

  	
   

  
	
  20

  	
   

  	
  Termination for Convenience

  	
   

  
	
  21

  	
   

  	
  Incentives and Remedies
  for Early and Late Delivery

  	
   

  
	
  22

  	
   

  	
  Remedies
  for Unsatisfactory Service and Support

  	
   

  
	
  23

  	
   

  	
  Consequences of Force
  Majeure

  	
   

  
	
  24

  	
   

  	
  Governmental Authorizations

  	
   

  
	
  25

  	
   

  	
  Applicable Law

  	
   

  
	
  26

  	
   

  	
  Arbitration

  	
   

  
	
  27

  	
   

  	
  Changes

  	
   

  
	
  28

  	
   

  	
  Key Personnel

  	
   

  
	
  29

  	
   

  	
  Key
  Sub-Contractors

  	
   

  
	
  30

  	
   

  	
  Technical
  Data Deposit

  	
   

  
	
  31

  	
   

  	
  Assignment
  of Contract

  	
   

  
	
  32

  	
   

  	
  Responsible
  Officers

  	
   

  
	
  33

  	
   

  	
  Communications

  	
   

  
	
  34

  	
   

  	
  Time Limits

  	
   

  
	
  35

  	
   

  	
  Order
  of Precedence

  	
   

  
	
  36

  	
   

  	
  Waiver

  	
   

  
	
  37

  	
   

  	
  Options

  	
   

  
	
  38

  	
   

  	
  Warranty
  Support and Maintenance Support

  	
   

  
	
  39

  	
   

  	
  Spares

  	
   

  
	
  40

  	
   

  	
  Entire
  Agreement

  	
   

  
	
   

  	
   

  	
  Signature

  	
   

  

 

	
  Annexes:

  	
   

  	
   

  	
   

  
	
  A

  	
   

  	
  Statement of
  Work (SOW)

  	
   

  
	
  B

  	
   

  	
  System Requirements
  Specification (SRS)

  	
   

  
	
  C

  	
   

  	
  Air
  Interface Specifications

  	
   

  
	
  D

  	
   

  	
  Price Breakdown and Payment Plan

  	
   

  
	
  E

  	
   

  	
  Warranty and Maintenance Plan

  	
   

  
	
  F

  	
   

  	
  Key Personnel

  	
   

  
	
  G

  	
   

  	
  Key Sub-Contractors

  	
   

  
	
  H

  	
   

  	
  Contractor Background

  	
   

  

 

 

Preamble 

 

This
is a Contract between Thrane & Thrane A/S (hereinafter referred to as the
“Contractor”), a company organized and existing under the laws of Denmark, with
its registered office at Lundtoftegårdsvej 93D, DK-2800 Lyngby, Denmark, and
Inmarsat Ltd, whose registered office is at 99 City Road, London EC1Y 1AX,
England (hereinafter referred to as “Inmarsat”)

 

The
effective date of this Contract (EDC) is 1 July 2001

 

Article 1:                                           Scope of Work

 

A.                                   The Contractor shall deliver to Inmarsat a Radio Access
Network (RAN) in accordance with all the requirements of this
Contract, including Annex A and B hereto, entitled Statement of Work (SOW) and System
Requirements Specification (SRS), the terms and conditions of this
Contract, and as directed by Inmarsat’s Responsible Officer, Helga Cantrell,
hereinafter referred to as “the Work”.

 

B.                                     Annex A and B hereto, entitled Statement of
Work and SRS set out the technical requirements and the functional
specifications to be met by the Contractor and the deliverables to be supplied
hereunder.  The total firm fixed price
referred to as “the Price” under Article 4 hereto, entitled Price
is for the Work to be provided hereunder and is inclusive of all applicable
taxes and duties in accordance with Article 6 hereto, entitled Taxes and
Duties.

 

Article 2:                                           Delivery by Contractor

 

A.                                   The items to be delivered by the Contractor
pursuant to this Contract shall be as described in Annex A and B hereto,
entitled Statement
of Work and SRS.

 

B.                                     The Radio Network Sub-system (RNS) delivery
locations shall be either as indicated in Annex A hereto, entitled Statement of
Work, or as finally determined by Inmarsat.  Notice of the final selection of delivery
locations shall be provided to the Contractor no later than six (6) months from
EDC.  All deliverable items shall be
delivered in accordance with Article 3 hereto, entitled Performance
Schedule in accordance with Annex A and B hereto, entitled Statement of
Work and SRS.

 

Article 3:                                           Performance
Schedule

 

The
Work, as defined in Article 1 hereto, entitled Scope of Work and as set out
in Annex A and B hereto, entitled Statement of Work  and SRS, shall be performed
in accordance with the schedule detailed in Annex A and B herein, entitled
Statement
of Work and SRS.  Final Acceptance
of the RAN in accordance with Article 5 hereto, entitled Final
Acceptance shall be completed no later than thirty (30) months after EDC.

 

Article 4:                                           Price

 

A.                                   The firm fixed price for the Work as defined in
Annex A and B herein, entitled Statement of Work and  SRS shall be **** and shall
be all inclusive and shall hereinafter be referred to as “the Price”.

 

B.                                     The prices for the Options under this contract
are detailed in Article 37 hereto, entitled Options.

 

Article 5:                                           Final Acceptance

 

A.                                   All deliverable items specified in
Paragraph A of Article 2 hereof, entitled Delivery by Contractor, and
the Contractor’s entitlement to the Price specified in Article 4 hereof,
entitled Price,
shall be subject to Final Acceptance of such items by Inmarsat.

 

B.                                     Inmarsat shall notify the Contractor of its
acceptance or rejection of project milestones prior to Final Acceptance and of
Final Acceptance of the Work within thirty (30) days after delivery or, if
applicable, upon completion of post-delivery acceptance of project milestones
prior to

 

1

 

Final
Acceptance.  Final Acceptance shall be
in accordance with the procedures specified in Annex A and B hereto, entitled Statement of
Work and SRS.

 

C.                                     The Contractor’s right to retain any payments
made pursuant to Article 7 hereof, entitled Payment Terms, shall be
conditional upon Final Acceptance of the Work in accordance with the procedures
and requirements referred to in Paragraph B of this Article.  If any part of the Work is not accepted
Paragraph B of Article 9 hereto, entitled Warranty as to Quality and
Article 21 hereof, entitled Incentives and  Remedies for Early and Late Delivery shall
apply.  Payments prior to Final
Acceptance of the Work in its entirety shall not be construed as acceptance of
any part of the Work and shall only be made against the completion of project
milestones specified in Annex D hereto, entitled Price Breakdown and Payment Plan.

 

Article 6:                                           Taxes and Duties

 

A.                                   With the
exception of UK value added tax, if applicable, the Contractor shall be
responsible for, and shall hold Inmarsat harmless from, all taxes, duties, and
similar liabilities which may arise under any present or future national,
federal, state, or local laws, and which become due by reason of the
performance of the Work under this Contract or any subcontract hereunder, and
shall comply with any requirements of such laws as may be necessary to
effectuate this Contract.

 

B.                                     The Price stated in Article 4 hereto,
entitled Price
is inclusive of all customs duties, VAT and sales and other taxes arising up to
the point of delivery to Inmarsat, which shall be identified on the invoice at
the applicable rates.

 

C.                                     Inmarsat shall be responsible for all taxes,
duties and similar liabilities that may become due by reason of the supply of
any Inmarsat equipment or other property to the Contractor.  The Contractor shall provide all reasonable
assistance to Inmarsat in connection with the importation of the Inmarsat
equipment as required, to ensure that the duration of customs clearance for any
Inmarsat equipment will not exceed seven working days from arrival of such
equipment at the port of entry.

 

D.                                    The Contractor shall be responsible for paying any withholding taxes
due on any payments made in connection with this Contract by Inmarsat and shall
indemnify Inmarsat from any liability for such withholding taxes.

 

E.                                      Where the Contractor pays remedies to Inmarsat (or its successor to
this Contract) under Articles 19, entitled Termination and Article 21, entitled Incentives
and Remedies for Early and Late Delivery (excluding interest
payments) or where Inmarsat withholds payment or where the Contractor provides
Unavailability Credits under this Contract, in accordance with Article 22,
entitled Remedies
for Unsatisfactory Service and Support, such remedies, withholdings
or payments will be treated as a reduction in the Price as described in
Article 4 hereto, entitled Price for which the Contractor will issue a
credit note.  The credit note shall
separately identify any credit for taxes and duties. If there are insufficient
sums under the Contract against which to issue a credit note the Contractor
shall pay the outstanding sums to Inmarsat.

 

Article 7:                                           Payment Terms

 

A.                                   The Price referred to in Article 4 hereof,
entitled Price,
shall be paid by Inmarsat in accordance with Annex D hereto, entitled Price
Breakdown and  Payment Plan, and with the terms of this
Contract.

 

B.                                     With respect to each amount specified in
Annex D hereto entitled Price Breakdown and  Payment Plan, the Contractor
shall submit an invoice to Inmarsat when the corresponding milestone event has
been successfully completed in accordance with Annex A and B hereto entitled Statement of
Work and SRS.  Each invoice
shall contain or be accompanied by a written certification from the Contractor
that the milestone event has been successfully completed.

 

C.                                     Inmarsat shall pay each amount within thirty
(30) days after Inmarsat receives the invoice and certification, provided,
however, that if Inmarsat concludes that the requirements for such milestone
event have not been fulfilled, the applicable payment shall not be made until

 

2

 

within
thirty (30) days after Inmarsat has determined that the requirements for such
milestone event have been fulfilled.

 

D.                                    All invoices shall be submitted in the original
and one (1) copy.  Any value added tax
or other applicable duties shall be separately identified.

 

E.                                      In the case of late payment of any amount
payable by Inmarsat under this Contract, the exclusive remedy for the
Contractor shall be action to compel payment with interest on the amount
outstanding at a rate of the current three (3) month US Dollar London
Inter-Bank Offer Rate (LIBOR) per annum calculated on a daily basis.  Such interest charge shall be computed
commencing on the first day following the payment due date.

 

Article 8:                                           Contractor Deliverables, Title and Assumption of Risk

 

A.                                   Title to all deliverable items specified in
Paragraph A of Article 2 hereof, entitled Delivery by Contractor, shall
pass to Inmarsat upon Final Acceptance thereof by Inmarsat pursuant to
Article 5 hereof, entitled Final Acceptance.  The Contractor warrants to Inmarsat that it has and will deliver
good title to all such deliverable items, free from any claim, lien, pledge,
mortgage, security interest, or other encumbrances, including, but not by way
of limitation, those arising out of the performance of the Work.

 

B.                                     With respect to each such deliverable item, the
risk of loss or damage shall be borne by the Contractor up to the time of
delivery into Inmarsat’s custody pursuant to Article 2 hereof, entitled Delivery by
Contractor.  After such
delivery, Inmarsat shall bear the risk of loss or damage. Notwithstanding the
foregoing any loss or damages to such deliverables, caused by the Contractor,
shall be subject to Article 14 hereto, entitled Loss and Damage, Indemnity.

 

C.                                     Notwithstanding the passing of title or
documents and reports, Inmarsat’s rights to use the information contained
therein shall be subject to Article 11 hereof, entitled Inmarsat’s
Rights in Technical Data and Inventions.

 

Article 9:                                           Warranty as to Quality

 

A.                                   Notwithstanding any prior inspection or
acceptance by Inmarsat, the Contractor warrants that:

 

1.                                       All deliverable equipment specified in
Paragraph A of Article 2 hereof, entitled Delivery by Contractor, shall
be new and free from any defects in materials, workmanship and design;

 

2.                                       All services shall be performed in a skillful
and workmanlike manner consistent with the best practices of the industry; and

 

3.                                       Deliverable items, including hardware,
software, services and documentation shall conform to the requirements
specified in this Contract, including Annex A and B hereto, entitled Statement of
Work and SRS.

 

B.                                     In the event of defective or non-conforming
Work, whether equipment, services, software, reports or otherwise, Inmarsat
shall notify the Contractor that the Work is non-conforming.  Such notice may be given after delivery, in
accordance with Article 5 hereof, entitled Final Acceptance, or prior to
delivery, at any time during the performance of this Contract.  In either case, the notice shall identify
those particulars in which the Work fails to conform. Inmarsat shall have the
following remedies:

 

1.                                       Inmarsat may require the Contractor to correct
or replace the defective or non-conforming Work at the Contractor’s
expense.  The decision whether the
non-conforming Work is to be corrected or replaced shall be at Inmarsat’s
option, but shall require consultation with the Contractor.  If the Contractor does not correct or
replace the Work within a reasonable period after notification from Inmarsat,
or if the Contractor fails to do so effectively, Inmarsat may have the
correction or replacement done by a third party, in which case the Contractor
shall reimburse Inmarsat for all costs reasonably incurred by Inmarsat.

 

3

 

2.                                       Inmarsat may elect not to have the defective or
non-conforming Work corrected or replaced, in which case the parties shall in
good faith negotiate an equitable reduction in the Price and, to the extent
Inmarsat has already made payments in excess of the reduced price, the
Contractor shall promptly refund that amount.

 

3.                                       Inmarsat may elect to reject any part of the
Work that is non-conforming, in which case the Contractor shall reimburse
Inmarsat for all amounts previously paid for such Work with interest at the
rate as set out in Article 7 hereof, entitled Payment Terms, calculated
from the day following the date of each payment by Inmarsat until the date of
reimbursement, and shall also be liable for any increased costs reasonably
incurred by Inmarsat in procuring alternative goods and/or services.

 

C.                                     With respect to each deliverable item or
service, these warranties and support shall run for a period of two (2) years
on all hardware, software and documentation delivered from the date of Final
Acceptance by Inmarsat pursuant to Article 5 hereof, entitled Final
Acceptance. With respect to any latent defect not discoverable upon
acceptance testing or use within the warranty period, such warranty period
shall run from the time of discovery of such latent defect.

 

D.            Any
corrections or replacements made pursuant to this Article shall be subject
to Article 8 hereof, entitled Contractor Deliverables, Title and Assumption of Risk.  With respect to any component that is
corrected or replaced, the warranty period specified in this Article shall
be suspended from the date of notification of the defect by Inmarsat and shall
recommence upon the date of satisfactory completion of the correction or
replacement for the un-expired portion of the warranty period.  Where such correction or replacement renders
other Work non-functional, the warranty period shall be similarly extended for
such Work.

 

E.                                      The rights and remedies of Inmarsat provided in
this Article shall be in addition to, and without prejudice to, or
forfeiture of, any other rights and remedies Inmarsat may have under this
Contract or at law or equity.

 

F.                                      The Contractor
warrants that neither the performance nor functionality of the Work are or will
be affected by Date Changes.  For the
purposes of this Paragraph, the term “Date Changes” means that all date based
functionality and/or operations must behave consistently with dates and any
representation of dates must not cause any interruption or degradation in
functionality and/or operation.  In
particular, all equipment, software and products must calculate, manipulate and
present dates correctly for the purposes for which they were created.  This warranty is a separate, independent and
continuing warranty and is not limited in time.

 

Article 10:                                    Access to Work in Progress and
Data

 

A.                                   As used in this Article, the term
“Sub-Contractors” refers to those Sub-Contractors within the scope of
Article 29 hereof, entitled Key Sub-Contractors.  To the extent necessary to implement this
Article, the Contractor shall pass the provisions hereof through into all such
Key Sub-Contracts and suppliers of critical path items.

 

B.                                     The Contractor shall provide for design and
progress review meetings with Inmarsat, and submit reports and documentation,
in accordance with Annex A and B hereto, entitled Statement of Work and SRS.

 

C.                                     Inmarsat shall have the right, at all reasonable
times during the performance of this Contract, to monitor the Work in progress
at the plants of the Contractor and its Key Sub-Contractors.

 

D.                                    All documentation and data relating to the
performance of this Contract shall, upon Inmarsat’s request and at Inmarsat’s
election, be made available for inspection and copying at the plants of the
Contractor and its Sub-Contractors, or copies shall be delivered to
Inmarsat.  This obligation shall apply
during the period of performance of the Contract.  With respect to any such documentation and data that is not
deliverable pursuant to Article 2 hereof, entitled Delivery by Contractor,
Inmarsat shall reimburse the reasonable costs of copying and delivery.  Thereafter, to the extent that such
documentation and data is of a type normally retained by the Contractor and its
Key Sub-Contractors, it shall continue to be

 

4

 

available
for such purposes for a period of two (2) years from the date of expiry or
earlier termination of this Contract.

 

E.             Subject
to reasonable arrangements to ensure the confidential treatment of proprietary
information, the same rights of access granted to Inmarsat in this
Article shall be granted to any technical consultants working for Inmarsat
in connection with this Contract or any projects related to the Work to be
performed under this Contract.

 

Article 11:                                    Inmarsat’s Rights In
Technical Data and Inventions

 

A.                                   Definitions

 

1.                                       “Contractor Background”
means any data, Know-how, Invention, or Intellectual Property Right owned by or
otherwise in the possession of the Contractor at the effective date of this
Contract, other than Foreground, used in performing any Work under this
Contract and which is required for the design, development, manufacture, use or
maintenance of any product delivered under this Contract.  Contractor Background is specifically
identified under Annex H to this Contract.

 

2.                                       “Inmarsat Background” means any data, Know-how, Invention, or
Intellectual Property Right owned by or otherwise in the possession of Inmarsat
at the effective date of this Contract, other than Foreground, disclosed to the
Contractor for its use in performing any Work under this Contract and provided
to the Contractor as part of Annex A and B hereto, entitled Statement of
Work and SRS or any other Annexes hereto.

 

3.                                       “this Contract” includes, where the context so admits or requires,
any Sub-Contract.

 

4.                                       “Designee” means a natural person or other entity that is designated
by Inmarsat.

 

5.                                       “Foreground” means any
data, Know-how, Invention or Intellectual Property Right generated in
performing any Work under this Contract, including without limitation any
technical information as may be specifically identified as Foreground in the
Final Report or any interim report.

 

6.                                       “Intellectual Property
Right” means all ideas, Inventions, patents, or applications therefore,
unregistered designs, registered design rights and applications therefore,
copyright, topography rights, all identifiable Know-how, experience, data and
all other technical or commercial information whether in human or machine
readable form and whether stored electronically or otherwise.

 

7.                                       “Invention” means any
invention, discovery, improvement or innovation of more than a trifling or
obvious nature, whether or not patentable, which is used to design, manufacture
or use any item, carry out any process of manufacture or to perform any other
Work under this Contract.

 

8.                                       “Know-how” means
technical information, data, Invention or experience, whether patentable or not
including, but not limited to, all design or manufacturing techniques,
operating instructions, machinery designs, raw material or products
specifications, drawings, blue prints and any other technical and commercial
information relating to research, design, development, manufacture, assembly,
use or sale.

 

9.                                       “Sub-Contract” and
“Sub-Contractor” mean respectively any sub-contract entered into by the
Contractor pursuant to this Contract and any other party to such sub-contract;

 

B.                                     Notification of and disclosure of Foreground to Inmarsat

 

1.                                       Upon completion of the
Work to be performed under this Contract or upon termination of this Contract
(if earlier) and also upon the written request of Inmarsat, the Contractor
shall notify Inmarsat of any and all items of Foreground not listed in a prior
report or certify that there are no such unreported items of Foreground.  Notification shall be in the form of a
report which contains a list setting forth the nature of each item of
Foreground, the system, subsystem, process or part thereof to which each listed
item relates and the source of each such item.

 

5

 

2.                                       Inmarsat may at any time
and from time to time request the Contractor by written notice to disclose to
it any or all of the Foreground and the Contractor shall disclose to Inmarsat
full details of the Foreground requested, sufficiently complete to convey a
clear understanding of the nature, purposes, operation and, to the extent known
to the Contractor, the technical characteristics of the Foreground.

 

3.                                       Inmarsat, without payment
of additional compensation to the Contractor, may disclose to any Designee any
item of Foreground disclosed to it hereunder.

 

C.                                     Use and Practice of Foreground by Inmarsat and others

 

1.                                       The Contractor hereby
grants Inmarsat the irrevocable, non-exclusive, royalty-free right to use the
Foreground throughout the world together with the right to grant sub-licences
of the Foreground to any Designee.

 

2.                                       The right to grant sub-licences under this Contract is subject to
the following conditions: -

 

(a)                                  any such sub-licence shall be non-exclusive and shall be limited and
subject to the rights and obligations granted hereunder;

 

(b)                                 no sub-licence shall include the right for the sub-licensee to grant
further sub-licences.

 

D.                                    Use and Practice of Background 

 

1.                                       The Statement of Work and SRS and any other Annexes shall include
all Inmarsat Background, which is to be made available to the Contractor.  The Inmarsat Background shall remain the
property of Inmarsat and the Contractor shall not make any representation or do
any act to indicate that it has any right title to or interest in the Inmarsat
Background.

 

2.                                       Inmarsat hereby grants to
the Contractor a non-exclusive, royalty free licence to use the Inmarsat
Background for the purposes of carrying out the Work in relation to this
Contract.  The Contractor agrees that it
will not use the Inmarsat Background for any purpose other than the performance
of its obligations under this Contract.

 

3.                                       The Contractor shall
disclose to Inmarsat on the EDC all Contractor Background to be used by the
Contractor, or any Sub-Contractor, in connection with the Work under this
Contract and thereafter shall not include additional Background without Inmarsat’s
written consent.  See Annex H hereto.

 

4.                                       The Contractor hereby
grants to Inmarsat and any Designee of Inmarsat a non-exclusive, royalty free
licence to use the Contractor Background for the purposes of exploiting, using,
repairing or maintaining the Work delivered under this Contract including any
Foreground.

 

5.                                       At the written request of
Inmarsat, the Contractor shall grant licenses under this Article 11.D. to
any Designee of Inmarsat.

 

E.                                      Copyright in Reports

 

1.                                       The Contractor hereby
assigns to Inmarsat copyright and all its present and future right, title and
interest throughout the world and all other rights of a like nature in all
reports deliverable under this Contract and all modifications and amendments
thereto, absolutely for the full term during which such rights and any renewals
or extensions may subsist.

 

2.                                       No Background shall be
included in any Final Report without the written approval of Inmarsat.  Background shall be provided in a separate
annex to the Final Report.

 

F.                                      Copyright in software

 

Where and to the extent
that any item delivered under this Contract consists of or includes software,
the Contractor hereby grants to Inmarsat the right under the Copyright in the
said software to use the said software and to make such copies of it as are
reasonably necessary for any use, including back-up, up-grades and archive
purposes.

 

6

 

G.                                     Availability of Know-how 

 

Notwithstanding any other
provision of this Article 11 under which limitations or conditions may be
imposed on Inmarsat or any other person or entity authorised by the Contractor
to use Know-how:

 

1.                                       The right to use any
Know-how shall become unconditional and unlimited immediately upon such item
having come into the public domain;

 

2.                                       If the relevant Know-how
becomes lawfully available to Inmarsat or any other entity authorised to use it
under this Article 11 on other terms, Inmarsat or such other person or
persons or entity may, at its sole discretion, use the relevant Know-how on
such other terms notwithstanding that such terms are more favourable to
Inmarsat or such other person or entity than the terms contained in this
Article 11.

 

H.                                    Marking Know-how

 

1.                                       All Foreground that is
disclosed under this Article 11 shall be marked by the Contractor with the
following notice:

 

“This
document/item is supplied pursuant to a Contract between Inmarsat and dated
                             
[and a Sub-Contract thereunder
between                                  and
                                                  ].  This document/item contains Foreground as
defined in that Contract which may be used only in the manner specified in that
Contract, unless such Foreground is or lawfully comes into the public domain or
is or lawfully becomes available to the user on other terms.”

 

The words in square
brackets shall be deleted if not appropriate.

 

2.                                       All Contractor Background
supplied under this Article 11 shall be marked by the Contractor with the
following notice:

 

“This
document/item is supplied pursuant to a Contract between Inmarsat and dated
                             [and a Sub-Contract thereunder
between                                      and
                                  ].  This document/item contains Contractor
Background as defined in that Contract which may be used only in the manner
specified in that Contract, unless such Contractor Background is or lawfully
comes into the public domain or is or lawfully becomes available to the user on
other terms.”

 

The words in square
brackets shall be deleted if not appropriate.

 

3.               Inmarsat and any other
person or entity to whom any Know-how is disclosed under this Contract shall be
entitled at any time to modify, remove, obliterate or ignore any legend or
equivalent marking which appears on any item of Know-how which is not expressly
authorised by this Article 12 provided that a written notice is first sent
to the Contractor advising the Contractor of such proposed action and the
Contractor fails, within twenty-one (21) days of receiving such notice,
satisfactorily to justify to Inmarsat the retention of such legend or
marking.  Any failure to mark Contractor
Background shall entitle Inmarsat to treat the same as if it were Foreground.

 

I.                                         Sub-Contracts

 

1.                                       In any Sub-Contract which may involve a
material amount of study, research or development the Contractor shall, unless
otherwise authorized or directed by Inmarsat in writing, include provisions
relating to Know-how which shall ensure that Inmarsat is not disadvantaged as a
result of such Sub-Contract and which shall not adversely affect the rights of
Inmarsat to use, or to exercise the Option in respect of any Foreground as
provided for under this Article 11. 
Without prejudice to the generality of the foregoing, the Contractor
undertakes not to enter into any Sub-Contract that may involve the generation
of Foreground without first obtaining from the relevant Sub-Contractor a
contractual undertaking that all Intellectual Property Rights in any such
Foreground will vest in the Contractor and an obligation to assign the same to
the Contractor, to the extent that such rights are assignable, and an
irrevocable and unconditional waiver of all other such rights.  As between Inmarsat and the Contractor, the
responsibility for and cost of obtaining all such assignments and waivers shall
be borne by the Contractor.

 

7

 

2.                                       If a Sub-Contractor refuses to accept any
provision pursuant to Article 11 the Contractor shall promptly submit a
written report to Inmarsat setting out the Sub-Contractor’s reasons for refusal
and shall not proceed with the Sub-Contract without Inmarsat’s written consent.

 

J.                                        Further Assurance

 

Notwithstanding
termination of this Contract for any reason, the Contractor shall do and execute
and shall procure that its employees and any Sub-Contractor and its employees
engaged in the performance of the Works do and execute all and any documents
and do all such things as Inmarsat may require to give effect to the provisions
of this Article 11.

 

K.                                    Warranty of Authority

 

The Contractor
warrants that it has or will obtain full power and authority to carry out the
provisions of this Article 11 from all persons and other entities who
perform any Work under this Contract or any Sub-Contract.

 

Article 12:                                    Patents For Foreground
Inventions

 

A.                                   Secrecy of Foreground Inventions

 

1.                                       The Contractor shall take all necessary steps
to preserve the secrecy of all Foreground Inventions and shall use its best
endeavors not to publish, put into commercial use, offer for sale or otherwise
perform acts which would adversely affect the patentability of any Foreground
Invention in any country before an application is filed pursuant to this
Article 12.

 

2.                                       If any publication, commercial use, offer for
sale or other act is made in error, the Contractor shall immediately notify
Inmarsat of all relevant details and circumstances and take all available steps
to minimize the adverse effects.

 

B.                                     Filing Of Patent Application

 

1.                                       The Contractor shall have the right to file, at
his own expense, patent applications in respect of Foreground Inventions
throughout the world.

 

2.                                       The Contractor shall give prompt written notice
to Inmarsat of each application filed and each patent granted pursuant to an
application, those countries in which it intends to file an application for a
patent or, if appropriate, which asserts that the Contractor does not intend to
file any patent application. 
Furthermore, the Contractor shall provide Inmarsat with a copy of each
application and the full specification with respect to each application within
forty-five (45) days of filing and, at Inmarsat’s written request, shall keep
Inmarsat advised of the progress of each application and provide Inmarsat with
a copy of each patent granted pursuant to an application.

 

3.                                       Inmarsat
shall identify any additional countries in which it would like a patent
application to be filed.  Within sixty
(60) days of receiving Inmarsat’s request, the Contractor shall, confirm
whether it intends to file a patent application in those countries.

 

4.                                       For each
country in respect of which the Contractor either fails to file an application
or gives notice to Inmarsat that it does not intend to file an application, the
Contractor shall, at the written request of Inmarsat, transfer to Inmarsat the
entire right, title and interest in the Foreground Invention in each such
country.  Any such transfer shall
include the right for Inmarsat, at its sole discretion, to use the Foreground
Invention as its confidential property and to apply for and obtain patent
protection provided that the Contractor may reserve to itself an irrevocable,
non-exclusive, royalty-free licence to use the Foreground Invention (with the
right to grant sub-licenses) in the relevant country.

 

5.                                       Should the
Contractor or any other person or entity deriving rights from the Contractor
(excluding licensees under this Contract) elect to abandon an application or a
granted patent, the Contractor shall so notify Inmarsat in writing not less
than sixty (60) days before any such application or Patent is allowed to lapse
or any positive act of abandonment is taken. 
At the written request of Inmarsat the Contractor shall promptly
transfer to Inmarsat the entire right, title and interest in each such
application or patent

 

8

 

and, pending such transfer, shall take all necessary
action (including without limitation the payment of fees) to maintain such
application or patent.  On the transfer
of an application or patent pursuant to this Article 12 the Contractor may
reserve to itself an irrevocable, non-exclusive, royalty-free licence to use
the Foreground Invention which is the subject of the application or the patent
in the relevant country (with the right to grant sub-licenses).

 

6.                                       All the
costs of filing and prosecuting any application and maintaining any patent
obtained pursuant to an application shall be borne by the Contractor save that
Inmarsat shall bear all such costs in respect of any patent application filed
or patent obtained by Inmarsat pursuant to this Article 12 and any
application or patent assigned to Inmarsat pursuant to this Article 12.

 

7.                                       The Contractor shall keep Inmarsat advised of
the progress of each application and provide Inmarsat with a copy of each
patent granted pursuant to an application.

 

8.                                       On grant of any patent the Contractor shall
grant to Inmarsat an irrevocable, non-exclusive,
royalty-free right to use the patent throughout the world together with the
right to grant sub-licences of the patent to any Designee.

 

C.                                     Examination of Records Relating to Foreground
Inventions

 

1.                                       At any time between the effective date of this
Contract and the expiry of thirty-sixth (36) months after final payment is made
under Article 7 hereof, entitled Payment Terms, or (if earlier) the date
this Contract terminates, the Contractor shall:

 

(a)                                  permit Inmarsat to examine any books, records,
documents and other data and materials in the possession or control of the
Contractor that Inmarsat shall reasonably deem likely to be directly pertinent
to the discovery or identification of a Foreground Invention or to the
compliance by the Contractor of its obligations under this Contract; and

 

(b)                                 at the written request of Inmarsat, promptly
execute and supply Inmarsat with an irrevocable power of attorney to inspect
and make copies of each Patent application in relation to any Foreground
Invention filed by or on behalf of the Contractor.

 

2.                                       Where Inmarsat has exercised transfer rights, the Contractor shall
assign to Inmarsat all rights in any Foreground Invention the same shall apply
to Foreground that the Contractor has failed to notify to Inmarsat under
Articles 11 and/or 12.  Pending a written assignment to Inmarsat of any
such forfeited rights the Contractor shall hold the Foreground Invention and
all rights in it, including any patents or patent applications, on trust for
Inmarsat and as soon as practicable the Contractor shall transfer to Inmarsat
all such rights in the Foreground Invention.

 

3.                                       The rights accruing to Inmarsat under this
Article 12 shall be in addition and without prejudice to any other rights
that Inmarsat may have in relation to unreported Foreground Inventions.

 

Article 13                                        Intellectual Property Right
Indemnity

 

A.                                   For the purposes of this Article 13:

 

1.                                       “Indemnitee” means Inmarsat, any
Designee, any subsequent owner or lessee of any item to be delivered under this
Contract and any officer, employee or agent of any such entities.

 

2.                                       The terms defined in Article 11 hereto,
entitled Inmarsat’s
Rights in Technical Data and Inventions, shall have the same meaning
when used in this Article 13.

 

B.                                     This Article 13 shall apply with respect
to all claims that the Intellectual Property Right of a third party is
infringed by:

 

1.                                       the manufacture, sale, lease or use of any item
to be delivered pursuant to this Contract; or

 

A.                                   the use of any item to provide a service to be
delivered pursuant to this Contract; or

 

9

 

B.                                     the use of any Foreground generated under this
Contract.

 

C.                                     The Contractor undertakes to defend, at its own
expense, any claim against any Indemnitee and to pay any royalties and other
costs associated with the settlement of such claim and any damages and costs
awarded as a result of any legal proceedings based on such claim. This
obligation shall be contingent upon the Indemnitee giving the Contractor prompt
notice of such claim, all necessary authority to defend or settle the claim on
its behalf and, at the request and sole cost of the Contractor, reasonable cooperation
and assistance and such relevant information as is available to it.

 

D.                                    In this Paragraph D, “enjoinment” means
any legal restraint or prohibition, whether by court order, under a negotiated
settlement or otherwise, and “enjoined” shall be understood accordingly.  If, as a result of any claim to which this
Article 13 applies, the manufacture or delivery of any item or service to
be delivered or otherwise provided pursuant to this Contract is enjoined, or the
sale, lease or use of any item delivered under this Contract is enjoined after
delivery or the use of any Know-how or Invention is enjoined at any time, the
Contractor agrees to do the following in the order stated:

 

C.                                     To use its best endeavours to negotiate a
licence or other agreement with the claimant to resolve the alleged
Intellectual Property Right infringement; and

 

D.                                    where applicable and subject to the technical
approval of Inmarsat and any other Indemnitee directly affected by the
enjoinment, to modify the item or substitute a suitable item so that the
modified or substituted item is not subject to the enjoinment.

 

If
neither of the foregoing alternatives is suitably accomplished by the
Contractor, the Contractor shall be liable to Inmarsat and any other Indemnitee
for any damages and costs suffered as the result of any such enjoinment as
aforesaid.

 

E.                                      The Contractor agrees that the provisions of
this Article 13 shall apply to any item modified pursuant to this
Article 13.

 

Article 14:                                    Loss and Damage, Indemnity

 

A.                                   For the purposes of this Article, the term “Indemnitees” shall
include (1) Inmarsat (2) any subsequent owner or lessee of any item to be
delivered hereunder; and (3) the officers, employees, agents or subsidiaries of
any of them.

 

B.                                     This Article 14 shall apply with respect to any loss of or
damage to property, or personal injury or death, caused by an act or omission
of the Contractor, or its Sub-Contractors, or the employees or agents of any of
them, in the performance of the Work under this Contract.

 

C.                                     In the case of loss or damage suffered by an Indemnitee, the
Contractor shall provide indemnification for all direct damages suffered.   Contractor specifically excepts
indemnification for indirect, consequential or special damages, including loss
of profit or business.

 

D.                                    In the case of loss or damage suffered by third parties, including
employees of the Contractor or its Sub-Contractors, the Contractor shall, at
its own expense, defend any claims brought against any of said indemnitees, and
shall pay all damages and costs associated with settlements or awards in
connection therewith.  This obligation
shall be contingent upon the indemnitees giving the Contractor prompt notice of
such claims, appropriate authority to defend the claims on their behalf, and,
at the request of the Contractor, reasonable cooperation and assistance and
such relevant information as is available to them.

 

Article 15:                                    Inmarsat-Furnished
Property and Facilities

 

A.                                   With respect to all equipment or other property furnished to the
Contractor by Inmarsat pursuant to Annex A and B hereto, entitled Statement of
Work and SRS, the following terms and conditions shall apply:

 

1.                                       The Contractor shall exercise due care to
ensure that such property is suitable for the purpose intended in connection
with the performance of the Work under this Contract.  If the Contractor is not so satisfied, it shall give Inmarsat
written notice to that effect as soon as possible.  In the case of deficiencies that should be

 

10

 

reasonably
discoverable upon receipt and examination, such notice must be given within
fifteen (15) days after receiving the property.

 

2.                                       The Contractor shall ensure that such property
is used solely in the performance of this Contract.

 

3.                                       Title to such property shall at all times
remain with Inmarsat, and the Contractor shall ensure that no claim, lien,
pledge, mortgage, security interest, or other encumbrance attaches to such
property as a result of any act or omission of the Contractor or its
Sub-Contractors.

 

4.                                       The Contractor shall return such property to
Inmarsat if so requested by Inmarsat, or when it is no longer required in
connection with the performance of any Work under this Contract, or in the
event of termination of this Contract. 
The costs associated with returning the property shall be borne by the
Contractor.

 

5.                                       The Contractor shall bear the risk of loss of
or damage to such property from the time that it arrives on the premises of the
Contractor or any of its Sub-Contractors and for so long as it remains in their
custody.  When the property is returned
to Inmarsat pursuant to Paragraph A (4) of this Article, the risk of loss
or damage while in transit shall be borne by the Contractor.

 

6.                                       Responsibility for any taxes or duties
associated with the delivery, use, or return of such property shall be in
accordance with Article 6 hereof, entitled Taxes and Duties.

 

B.                                     With respect to any facilities provided by Inmarsat or any of its
other contractors pursuant to Annex A and B hereto, entitled Statement of
Work and SRS, whether for installation of the items to be delivered
by the Contractor under this Contract or for any other purpose, the Contractor
shall exercise due care to ensure that such facilities are suitable for the
purpose intended.  If the Contractor is
not so satisfied, it shall give Inmarsat notice to that effect as soon as
possible.  In the case of deficiencies
that should be reasonably discovered upon examination, such notice must be
given within fifteen (15) days after the Contractor is afforded an opportunity
to examine the facilities.

 

Article 16:                                    Inmarsat-Furnished
Documents, Examination

 

A.                                   This Article shall apply to any documents that Inmarsat is
required to provide to the Contractor pursuant to this Contract.

 

B.                                     The Contractor shall exercise due care to ensure that such documents
are sufficient for the performance of this Contract, and that they contain no
manifest errors or anomalies.  This
Article shall not apply to any errors or omissions in the documents that
would not be reasonably discoverable by the Contractor exercising due care.

 

C.                                     With respect to documents furnished to the Contractor by Inmarsat,
the Contractor shall be presumed to be satisfied that they are sufficient, that
they contain no manifest errors or anomalies, and that they are timely, unless
the Contractor gives Inmarsat notice that it is not so satisfied within fifteen
(15) days after the Contractor receives such documents.  On a case-by-case basis, the Contractor may
request a longer period to examine the documents, but such request must be made
within the said fifteen (15) day period, and Inmarsat shall not be required to
grant such an extension if, in Inmarsat’s judgement, the Contract performance
schedule would be adversely affected thereby.

 

D.                                    In addition to the obligations of this Article 16, if the
Contractor concludes, at any time during the performance of this Contract, that
there are inaccuracies or inconsistencies in any documentation supplied by
Inmarsat or that it is not complete or sufficient to enable the Contractor to
perform the Work, the Contractor shall immediately refer the matter to Inmarsat
for resolution before proceeding with any Work affected by such deficiencies.

 

E.                                      If Inmarsat does not receive timely notice that the Contractor is
not satisfied pursuant to this Article 16, or if the Contractor proceeds
with any Work in contravention of this Article 16, the Contractor shall be
neither relieved of its obligation to perform the Work as intended nor entitled
to any increase in the Price or extension of the delivery schedule by
reason thereof.

 

11

 

Article 17:                                    Confidentiality

 

A.                                   Each party shall during the full term of this Contract and
thereafter, keep secret and confidential all Know-how or other business,
technical or commercial information, in connection with this Contract disclosed
to it by the other party or otherwise belonging to the other party (and shall
procure that any employees, sub-licensees or sub-contractors are similarly
bound) and shall not disclose the same to any person save to the extent
necessary to perform its obligations in accordance with the terms of this
Contract.  All such information shall be
identified as confidential at the time it is so supplied.

 

B.                                     Even if information is identified as
confidential, disclosure to Inmarsat’s Designees shall be permitted.  Any disclosure by Inmarsat to Designees
shall be subject to reasonable safeguards to protect the confidentiality of
such information.

 

C.                                     Article 11 hereto, entitled Inmarsat’s
Rights in Technical Data and Inventions, and Article 12 hereof,
entitled Patents
for Foreground Inventions, shall take precedence over the provisions
of this Article to the extent that there is any inconsistency.

 

D.                                    The foregoing provisions of this Article shall not apply to
know-how and information which:

 

1.                                       is or becomes public knowledge without breach of this Contract;

 

2.                                       is already known to the receiving party at the time of its
disclosure by the disclosing party and was not otherwise acquired by the
receiving party from the disclosing party under any obligations of confidence;

 

3.                                       is independently developed by the Contractor or Inmarsat which fact
can be shown by competent evidence;

 

4.                                       Inmarsat or the Contractor is compelled by legal process or
government regulation or order to disclose, provided that the disclosing party
is given prompt notice of any proposed release of information under this
sub-clause and that the disclosing party be given ample opportunity to engage
in legal action to resist and/or restrict any such disclosure.

 

E.                                      The provisions of this Article shall remain in force for a
period of five (5) years from the date of receipt by the party concerned of
such Know-how and information notwithstanding earlier termination of this
Contract.

 

Article 18:                                    Public Release of Information

 

A.                                   The Contractor shall obtain the written
approval of Inmarsat concerning the content and timing of news releases,
articles, brochures, advertisements, prepared speeches, and other information
releases to be made by the Contractor or any of its Sub-Contractors concerning
this Contract or the Work performed or to be performed hereunder.  Inmarsat shall be given a reasonable time to
review the proposed text prior to the date scheduled for its release.

 

B.                                     To the extent required to do so by law, the
Contractor shall have the right to release information concerning this
Contract.  Inmarsat shall have the right
to review and approve the content of such release.

 

Article 19:                                    Termination

 

A.                                   Inmarsat shall have the right to terminate this Contract, without
prejudice to any of its other rights and remedies, forthwith by notice in
writing to the Contractor in the event that:

 

1.                                       the Contractor shall default in due performance or observance of any
of its material obligations on its part to be performed or observed hereunder
and (in the case of a remediable breach) fails to remedy such breach within
thirty (30) days of being requested by written notice to do so and in that
event the remedies set out in Article 21 hereto, entitled Incentives
and  Remedies for Early and Late Delivery shall apply; or

 

2.                                       the Contractor passes a resolution or a court of competent
jurisdiction makes an order that the Contractor be wound up otherwise than for
the purpose of bona fide reconstruction or amalgamation, or a receiver, manager
or administrator on behalf of a creditor is appointed in respect of the
Contractor’s business or any part

 

12

 

thereof, or if
circumstances arise which entitle a court of competent jurisdiction or a
creditor to appoint a receiver, manager or administrator or which entitle the
court otherwise than for the purpose of bona fide reconstruction or
amalgamation to make a winding up order, or the Contractor is unable to pay its
debts within the meaning of section 123 of the Insolvency Act 1986 or
under any other laws domestic or foreign, relating to bankruptcy, insolvency,
reorganisation, winding up or adjustment of debts. In that event the remedies
set out in Article 21 hereto, entitled Incentives and  Remedies for
Early and Late Delivery shall apply.

 

B.                                     For any other breach, including, but not limited to anticipatory
breach, repudiation, inability to perform, or lack of due diligence, which if
remediable is not so remedied within thirty (30) days of a notice from Inmarsat
requiring such remedy, Inmarsat may terminate the Contract, either in whole or
as to any severable portion, and in that event the remedies set out in
Article 21 hereto, entitled Incentives and  Remedies for Early and Late Delivery shall
apply.

 

C.                                     Where Inmarsat after undue delay by the
Contractor notifies the Contractor that time is of the essence of the Contract
and the Contractor shall not have performed any of its obligations stated in
such notice by any reasonable date stated in the notice, Inmarsat may terminate
the Contract in accordance with Article 21 hereto,
entitled Incentives
and  Remedies for Early and Late Delivery.

 

D.                                    If the Contractor fails to comply with the notification requirements
due upon completion of the Contract Work pursuant to Article 11 hereof,
entitled Inmarsat’s
Rights in Technical Data and Inventions, Inmarsat may, until such
notification is provided, withhold payment of the Final Acceptance payment
milestone specified in Annex D hereto, entitled Price Breakdown and  Payment Plan.

 

E.                                      In the event that any alleged breach of this Contract leads to
arbitration proceedings pursuant to Article 26 hereof, entitled Arbitration,
Inmarsat shall be entitled to exercise the remedies in Article 9 hereof,
entitled Warranty
as to Quality, and in this Article pending the outcome of such
proceedings.  If Inmarsat gives notice
of discharge and it is subsequently determined that the Contractor was not in
breach, the rights and obligations of the parties shall be the same as if
Inmarsat had terminated for convenience pursuant to Article 20 hereof,
entitled Termination
for Convenience, unless the parties mutually agree to reinstate the
Contract.

 

Article 20:                                    Termination for Convenience

 

A.                                   Inmarsat may terminate this Contract, in whole or in part, for
Inmarsat’s convenience, at any time prior to completion.

 

B.                                     In the event of such termination by Inmarsat, the termination
charges shall be determined by good faith negotiations between Inmarsat and the
Contractor or, if agreement cannot be reached Article 27 hereof, entitled Arbitration,
shall apply.  In making such
determination, the following principles shall be applied:

 

1.                                       The total termination charges shall not exceed
the sum of:

 

(a)                                  Direct costs (including overhead recovery on
such costs, but excluding any profit element)) reasonably incurred by the
Contractor in connection with the performance of the Work prior to termination,
other than those costs referred to in Paragraph B (1)(c) of this Article.  Such costs shall be determined in accordance
with the Contractor’s standard accounting practices and, if requested by
Inmarsat, shall be verified by the Contractor’s independent auditors at the
Contractor’s expense.  Inmarsat may also
elect to have such costs verified by Inmarsat’s independent auditors at
Inmarsat’s expense.

 

(b)                                 A profit element representing ten percent (10%)
of the costs in Paragraph B (1)(a) above.

 

(c)                                  Reasonable costs incurred by the Contractor in
settlement with Sub-Contractors and suppliers as a result of Inmarsat’s
termination.  With

 

13

 

respect
to any proposed settlement involving an amount in excess of ten (10%) percent
of the value of any such sub-contract, the Contractor shall advise Inmarsat,
and shall not enter into any binding settlement until Inmarsat has approved the
proposal, or until thirty (30) days have elapsed from the date when such advice
was furnished to Inmarsat, whichever is sooner.

 

2.                                       In no event shall the termination charges
exceed the unpaid balance of the Price. 
In the case of termination in part, the termination charges shall not
exceed that unpaid balance of the severable portion of the Price applicable to
the part of the Work that is terminated.

 

C.                                     Unless otherwise agreed, Inmarsat shall be entitled to take
possession of all Work completed or in progress prior to termination under this
Article 20, except for Work associated with any executory portion of the
Contract that is not terminated.

 

D.                                    The termination charges determined pursuant to this
Article shall be reduced by the following:

 

1.                                       Any amounts previously paid by Inmarsat to the
Contractor with respect to the performance of the Work prior to
termination.  To the extent such amounts
previously paid by Inmarsat exceed the termination charges due, the Contractor
shall refund the difference to Inmarsat.

 

2.                                       Amounts representing the resale, reuse, or
salvage value to the Contractor, or to its Sub-Contractors and suppliers, of
items that Inmarsat has not taken possession of pursuant to Paragraph C of
this Article.

 

Article 21:                                    Incentives and Remedies for Early and Late Delivery

 

Without
prejudice to any other remedies available to Inmarsat, with respect to late
delivery in breach of the schedule requirements in Article 3 hereof,
entitled Performance
Schedule, and as defined in Annex A and B hereto, entitled Statement of
Work and SRS. The following procedures incentives and remedies shall
apply to the Factory Acceptance Test (FAT) and Final Acceptance contractual
milestones as follows:

 

Factory
Acceptance Test (FAT) Milestone:

 

1.                                       In case Factory Acceptance (FAT) is delayed, the Contractor shall be
liable for liquidated damages in the amount of **** per day for each day of
delay of FAT in accordance with Article 5 hereof entitled Final
Acceptance.  Such liquidated
damages shall accrue up to a total amount of ****

 

2.                                       The liquidated damages set out in (1) above shall accrue up to and
including the date of successful FAT or termination by Inmarsat pursuant to
Article 19 hereto, entitled Termination.  During the period when liquidated damages are accruing, the
Contractor shall not be liable for any other damages with respect to such
delay, except as explicitly stated to the contrary.

 

Final Acceptance Milestone:

 

1.                                       Incentives shall be triggered by an early Final Acceptance date before EDC+30
months, in accordance with Article 5 hereto, entitled Final
Acceptance.  Incentives for early Final
Acceptance shall be as follows:  ****
per day for every day the final Acceptance in accordance with Article 5
hereto, entitled Final Acceptance is earlier than EDC+30 months, up to and
including three (3) weeks before EDC+30 months.  If Final Acceptance is earlier than the above-mentioned three (3)
weeks, the Incentives shall be **** of the total Contract Value, less the
Incentives
already accrued spread linearly over the remaining period of up to EDC+ four
(4) months, calculated on a daily basis.

 

2.                                       Lidquidated
Damages shall be triggered by delay to the
scheduled Final Acceptance Date EDC+30 months in accordance with Article 5
hereof, entitled

 

14

 

Final Acceptance.  There shall be no
differentiation as to which part of the Work caused the delay to the Work and
the Liquidated
Damages shall be as follows: 
**** per day from the first day of delay up to and including three
weeks.  Thereafter the Liquidated
Damages shall be **** of the total Contract Value less the Liquidated
Damages already accrued spread linearly over the remaining period of
up to EDC+ four (4) months, calculated on a daily basis.

 

3.                                       The liquidated damages set out in (2) above shall accrue up to and
including the date of successful Final Acceptance or termination by Inmarsat
pursuant to Article 19 hereto, entitled Termination.  During the period when liquidated damages
are accruing, the Contractor shall not be liable for any other damages with
respect to such delay, except as explicitly stated to the contrary.

 

4.                                       Both parties acknowledge that the liquidated damages specified in
this Article are a genuine pre-estimate of the loss likely to be suffered
by Inmarsat and that the figures therein are reasonable.

 

5.                                       The liquidated damages specified in this Article may be
recovered by Inmarsat, at its sole discretion, either:

(a)                                  as a sum of money invoiced by Inmarsat and payable by the
Contractor; or

(b)                                 as a credit against any sum of money owed by Inmarsat to the
Contractor or which may subsequently become due to the Contractor.

 

6.                                       If the Contractor fails to promptly complete the Work by the due
date(s), or does not progress the Work such that the same will be completed by
the due date(s), Inmarsat may terminate the Contract, either in whole or any
severable portion thereof.  Inmarsat
shall give the Contractor notice of intention to invoke these remedies thirty
(30) days before giving formal notice of discharge.  In the event Contractor is unable to remedy the situation within
the said thirty (30) days, the following remedies shall apply:

 

(a)                                  Inmarsat may, in its sole discretion, take over
all or part of the Work affected by the termination, and proceed with the same
to completion, by contract or otherwise. 
For this purpose, Inmarsat may take possession of, and utilize in
completing the Work, such materials, equipment, and information and data as may
be necessary therefore. The Contractor shall reimburse Inmarsat for any
increased costs reasonably incurred in completing the Work.

 

(b)                                 With respect to any part of the Work affected
by the termination that Inmarsat does not elect to take over and complete, the
Contractor shall reimburse Inmarsat for all amounts previously paid for such
Work, and shall also be liable for any increased costs reasonably incurred by
Inmarsat in procuring alternative goods and/or services. The reimbursements
shall be inclusive of interest calculated at a rate of the current three (3)
month US Dollar London Inter-Bank Offer Rate (LIBOR) per annum, calculated on a
daily basis.  Such interest charge shall
be computed commencing on the first day following the payment due date for the
increased costs reasonably incurred by Inmarsat in procuring alternative goods
and/or services and for the previously paid amounts from the date when such
payments were received by the Contractor.

 

Article 22                                        Remedies for Unsatisfactory Service and Support

 

A.                                   For the purpose of this Article, periods of
unsatisfactory service of the BGAN RAN shall be referred to as Unavailability
and shall mean failure to meet the requirements of this Contract, in particular
failure to meet the availability requirements specified in Annex A and B
hereto, entitled Statement of Work and SRS, except for the following:

 

1.                                       Planned down-time, such as for preventative
maintenance, in accordance with Annex A and B hereto, entitled Statement of
Work and SRS.

 

15

 

B.                                     The remedies under this Paragraph shall apply
for each set of RNS equipment delivered hereunder if the minimum availability
requirements of **** during the first year of operations and ****% during each subsequent year of operations for
each RNS, as specified in Annex A and B hereto, entitled Statement of Work and SRS,
are not satisfied and shall be as follows:

 

1.                                       Unavailability Remedies: For each **** that the cumulative period of unavailability
of each RNS in any calendar month of operation drops below ****% (with the
exception of the first year where the availability requirement is ****%) and is caused by
the Contractor’s failure to meet its responsibilities under this Contract,
Inmarsat shall be entitled to retain or recover **** as Unavailability Remedies. The cumulative
period of unavailability shall not include planned outages and agreed
acceptance periods. The total amount of Unavailability Remedies per month per
RNS shall not exceed **** for availability down to ****%.

 

Inmarsat
shall be entitled to reduce the payment due to Contractor under the Payment Plan
in accordance with Annex D hereto at the end of each Warranty Year by the total
cumulative amount of Unavailability Remedies.

 

2.                                       Chronic Unsatisfactory Performance:  The
equipment and/or support shall be deemed to have chronic unsatisfactory performance if,
in any period of twelve (12) months, the availability of any RNS provided by
the Contractor drops at any time below ****%, or availability is below ****% for three
consecutive months (except for the first year where the threshold shall be ****%), not including
planned outages.  Regardless of outages,
in case the equipment and/or warranty and support is deemed to be non-compliant
with the functional requirements of Annex A and B hereto, entitled Statement of
Work and SRS the performance shall be deemed to be a non-compliant
performance.

 

C.                                     The following remedies shall apply in the event
of any RNS showing chronic unsatisfactory performance or
non-compliant performance with the functional requirements  of
Annex A and B hereto, entitled Statement of Work and SRS, in addition to
any other remedies available at law or under this Contract:

 

1.                                       In the event Contractor’s equipment and/or support
are chronically unsatisfactory or non-compliant, Inmarsat shall be entitled to
unavailability remedies not to exceed **** of the total annual warranty or maintenance
payment.

 

2.                                       Termination
for default, in which case the Contractor shall pay the increased costs
actually incurred by Inmarsat in procuring replacement RAN systems, not to
exceed the Contract value.

 

3.                                       Notification
to the Contractor that Inmarsat wishes to continue receiving the service, in
which case the parties shall negotiate in good faith to establish lower
performance standards, and new lower charges. In the event Inmarsat determines
at any time that such lower grade of service is not adequate to meet Inmarsat’s
revised operational requirements, Inmarsat may invoke the remedy in (1) above.

 

D.                                    The following evidentiary and procedural
provision shall govern the determination of whether the performance of the
equipment has been unsatisfactory:

 

1.                                       Inmarsat measurements, computations and
analyses shall be the basis for determining whether and for what period of time
the performance of the equipment has been unsatisfactory, and the Contractor
shall be given access to such data. Should the Contractor disagree with such
determination and have evidence to the contrary, Inmarsat shall consider such
evidence. In the event that disagreement persists, such disagreement shall be
resolved in accordance with Article 26 hereof, entitled Arbitration.

 

2.                                       Inmarsat shall notify the Contractor in writing of Inmarsat’s
determination that the performances have been unsatisfactory as soon as
possible after receipt by Inmarsat of the data that are necessary for such
determination.

 

3.                                       Any use by Inmarsat of unsatisfactory equipment comprising the Work
shall be without prejudice to, or forfeiture of, any rights and remedies of
Inmarsat under this Contract, including, but not limited to, Inmarsat’s
entitlement to Unavailability Credits pursuant to Paragraph B of this Article.

 

16

 

E.                                      Remedies Following Warranty Period:   It is expressly agreed between the parties
that the Unavailability Remedies shall be available to Inmarsat during the two
(2) year Warranty period as well as the Maintenance Period following expiration
of Warranty for up to eight (8) additional years.

 

Article 23:                                    Consequences of Force Majeure

 

A.                                   The purpose of this Article is to establish the consequences of
force majeure events preventing either party from complying with any of its
obligations under this Contract.

 

B.                                     As used in this Article, the term “force majeure” refers to events
extrinsic to this Contract that are beyond the reasonable control of, and not
attributable to negligence or other fault of, the party relying on such events
to excuse its failure to perform.  The term
does not include strikes or other events caused by labour disputes, unless such
strikes or other events are part of national or regional disputes.

 

C.                                     The Contractor shall not be excused from performance due to any
failure to perform by its Sub-Contractors or suppliers unless their failure to
perform is due to force majeure.

 

D.                                    Any party whose ability to perform is affected by a force majeure
event shall take all reasonable steps to mitigate the impact of such event.

 

E.                                      If the effect of a force majeure event is temporary, subject to
Paragraph F of this Article, the party so affected shall not be
responsible for any consequent delay, and the relevant schedule or time
period shall be extended accordingly, if and only if notice of the event is
given to the other party within seven (7) days after the event has
occurred.  At the time of the initial
notice of the occurrence of the event, or as soon as possible thereafter, the
party affected shall inform the other party of the extent of the delay expected
as a result of the event.

 

F.                                      In the case of one or more force majeure events having a temporary
effect on the ability of the Contractor to comply with the schedule in
Article 3 hereof, entitled Performance Schedule and if the effect
is, or will be, to delay the said schedule by more than six (6) months, or
in the case of force majeure events permanently preventing the Contractor from
complying with said schedule, Inmarsat may declare this Contract to be
terminated, in whole or in part.  With
respect to any part of the Contract that is so terminated, the financial
obligations hereunder of either party shall be determined by negotiations
between the parties or, if agreement cannot be reached, pursuant to
Article 26 hereof, entitled Arbitration.  The object of such determination shall be to equally apportion
between the parties the financial consequences of the termination of the
Contract in whole or in part, taking into account the impact of such
termination on each party, including any insurance proceeds.

 

Article 24:                                    Governmental
Authorizations

 

A.                                   The Contractor shall be responsible for obtaining all governmental
authorisations necessary for the performance of the Work hereunder. For this
purpose the Work shall include without limitation the delivery of all items,
documents and data which are deliverable pursuant to any provision of this
Contract, the conduct of tests and design and progress reviews in accordance
with the requirements of this Contract and the provision of all required
services. Certification by the Contractor to Inmarsat of the receipt of such
governmental authorisations is a condition subsequent.  If such receipt is not certified to Inmarsat
within ninety (90) days after the effective date of this Contract,
Inmarsat may rescind this Contract.  In
the event of such decision, Inmarsat shall have no financial or other
obligation to the Contractor relative to this Contract, and any amounts
previously paid by Inmarsat to the Contractor shall be refunded with interest
at the rate as set out in Article 7 hereof, entitled Payment Terms. Such interest
charges shall be computed commencing from the date when the Contractor received
the refundable payments.

 

B.                                     If the Contractor does not certify receipt of all necessary
governmental authorisations within the time limit specified in Paragraph A
of this Article 24, and if Inmarsat nevertheless elects not to rescind the
Contract but instead to allow the Contractor to proceed with the Work pending
receipt of such authorisations, any subsequent failure of the Contractor to
obtain such authorisations shall be treated as follows:

 

17

 

1.                                       If such failure is attributable to lack of due
diligence by the Contractor Article 19 hereof, entitled Termination,
shall apply.

 

2.                                       If the Contractor has acted with due diligence,
has notified Inmarsat in accordance with the provisions of this Contract and
its failure to obtain the necessary governmental authorizations is attributable
to causes beyond the Contractor’s reasonable control, Article 23 hereof,
entitled Consequences
of Force Majeure, shall apply.

 

C.                                     Without prejudice to Paragraph A of this Article 24:

 

1.                                       the exercise by Inmarsat or its technical
consultants of any rights under Article 10 hereof, entitled Access to
Work in Progress and Data; and

 

2.                                       the exercise by Inmarsat or its Designees of
any rights under Article 11 hereof, entitled Inmarsat’s Rights in Technical Data and
Inventions;

 

shall be
subject to applicable domestic laws relating to the export of the subject
technology.  The Contractor shall upon
request exercise due diligence to obtain any such licence as may be necessary
for the exercise of any such rights.

 

Article 25:                                    Applicable Law

 

This
Contract shall be governed by and interpreted according to the laws of England.

 

Article 26:                                    Arbitration

 

A.                                   Any dispute that arises between the Contractor and Inmarsat in
connection with this Contract, which is not settled within thirty (30) days
from the date that either party notifies the other that such a dispute exists,
or within such longer period as may be mutually agreed upon, shall be resolved
by arbitration under the Rules of the London Court of International Arbitration
in effect on the date that the arbitration was initiated.

 

B.                                     A sole arbitrator shall be appointed by the Court, unless either
party requests a three (3) member tribunal, or unless the Court determines in
view of all the circumstances of the case that a three (3) member tribunal is
appropriate.

 

C.                                     The place of arbitration shall be London, England.

 

D.                                    Responsibility for paying the costs of the arbitration, including
the costs incurred by the parties themselves in preparing and presenting their
cases, shall be apportioned by the tribunal.

 

E.                                      The award shall state the reasons upon which it is based.

 

F.                                      The award shall be final and binding on the parties as from the date
it is made.

 

G.                                     Judgement upon the award rendered may be entered in any court having
jurisdiction, or application may be made to such court for a judicial
acceptance of the award and an order of enforcement, as the case may be.

 

H.                                    The parties recognise that the subject matter of this Contract is
unique, and that damages may not be adequate under some circumstances.  For these reasons, the parties agree that
the tribunal shall be empowered to decree specific performance.

 

Article 27:                                    Changes

 

A.                                   At any time during the period of this Contract, Inmarsat may request
changes in the Work, so long as such changes are within the general scope of
the Contract.  The Contractor may also
propose changes for consideration by Inmarsat.

 

B.                                     A change request from Inmarsat must be identified as such, must be
made or confirmed in writing, and must be signed by the responsible officer
identified in Article 32 hereof, entitled Responsible Officers.  If any other conduct by the responsible
officer or any other representative of Inmarsat is construed by the Contractor
as possibly constituting a change request or an interpretation of the Contract
requirements inconsistent with the Contractor’s

 

18

 

understanding
of those requirements, the Contractor shall promptly notify Inmarsat and
request clarification.

 

C.                                     Within fifteen (15) days after receiving a change request from
Inmarsat, the Contractor shall submit to Inmarsat a contract change notice in a
format to be provided by Inmarsat and in accordance with the requirements of
this Article 27.  On a case-by-case
basis, the Contractor may request a longer period to prepare the contract
change notice, but any request for such a longer period shall be made by the
Contractor within seven (7) days after the Contractor receives the change
request.  Inmarsat shall not
unreasonably withhold its consent to a request for such a longer period, taking
into account the nature of the change request, but Inmarsat may also take into
account the impact of such an extension on the performance schedule.

 

D.                                    Whether submitted in response to a change request initiated by
Inmarsat, or initiated by the Contractor, the contract change notice shall
itemise, in a format to be approved by Inmarsat, any impact that the change
would have on the technical requirements, price, performance schedule, or other
terms and conditions of this Contract. 
Where appropriate, the contract change notice shall also suggest any
revised language for the Contract, including any of its Annexes that would be
necessary to implement the change.

 

E.                                      Any claim by the Contractor for adjustment of the technical
requirements, price, performance schedule, or other terms and conditions of
this Contract, attributable to a change, shall be deemed waived unless asserted
in the contract change notice.

 

F.                                      If the cost of any materials that would be made obsolete as a result
of a change is included in the Contractor’s claim for adjustment:

 

1.                                       To the extent that such materials have resale,
reuse, or salvage value to the Contractor or its Sub-Contractors or suppliers,
Inmarsat shall be entitled to a credit.

 

2.                                       If such materials have no such resale, reuse,
or salvage value, Inmarsat shall have the right to prescribe their manner of
disposition.

 

G.                                     After Inmarsat receives a sufficiently detailed contract change
notice, and after any negotiations with respect to the adjustments claimed by
the Contractor, the following outcomes are possible:

 

1.                                       Inmarsat may decide not to proceed with
implementation of the change.

 

2.                                       Inmarsat may decide to implement the change, in
which case:

 

(a)                                  If the parties have reached agreement about the
adjustments to be made in the Contract, the Contractor shall proceed with
implementation as agreed.

 

(b)                                 If the parties are unable to reach such an
agreement, the provisions of Article 26 hereof, entitled Arbitration,
shall apply.

 

(c)                                  Pending any negotiations and/or arbitration,
Inmarsat may direct the Contractor to proceed with implementation of the
change, subject to any adjustments subsequently agreed or awarded.

 

H.                                    Inmarsat may also direct the Contractor to proceed with
implementation of a change prior to preparation of a complete contract change
notice, subject to any adjustments subsequently agreed or awarded.

 

I.                                         Inmarsat’s right to direct the Contractor to proceed with the
implementation of a change pursuant to Paragraph G (2)(c) or H of this
Article 27 shall be subject to the Contractor’s ability to do so, taking
into account the resources, facilities, supplies, and services available to it,
and may also be subject to a stipulated financial limit.

 

Article 28:                                    Key
Personnel

 

A.                                   The Contractor agrees that those individuals identified in Annex F
hereto, entitled Key Personnel, are necessary for the successful completion of
the Work to be performed under this Contract.

 

19

 

B.                                     Such Key Personnel shall not be removed from the performance of the
Work under this Contract unless replaced with personnel of substantially equal
qualifications and ability.  Inmarsat
shall have the right to review the
qualifications of any proposed replacements and, if for
good and sufficient reasons Inmarsat deems such personnel to be unsuitable,
Inmarsat may require the Contractor to offer alternative candidates.

 

C.                                     Notwithstanding its role in approving key personnel and their
replacements, Inmarsat shall have no supervisory control over their Work, and
nothing in this Article shall relieve the Contractor of any of its
obligations under this Contract, or of its responsibility for any acts or
omissions of its personnel.

 

Article 29:                                    Key Sub-Contractors

 

A.                                   The Contractor agrees that those Sub-Contractors identified in
Annex G hereto, entitled Key Sub-Contractors, are necessary for the
successful completion of the Work to be performed under this Contract.

 

B.                                     The Contractor hereby agrees to use its best efforts to enter into
subcontracts with these Key Sub-Contractors. 
If, for any reason, the Contractor is unable to enter into subcontracts
with any of these Key Sub-Contractors, or such subcontracts are entered into
and are subsequently terminated, the Contractor shall replace such Key
Sub-Contractors with Sub-Contractors of substantially equal qualifications and
ability acceptable to Inmarsat.

 

C.                                     The Contractor shall enter into no other subcontracts having a value
in excess of United States Dollars *** (US$****) without the prior
express approval of Inmarsat.

 

D.                                   Nothing in this Article shall relieve the Contractor of its
responsibility for the performance, in accordance with this Contract, of the
subcontracted Work.

 

Article 30:                                    Technical Data Deposit

 

A.                                   The Contractor agrees that, no later than at
the Final
Acceptance Date as defined in Article 5 herein, entitled Final
Acceptance, it shall deliver to Inmarsat one complete copy of all
software, including without limitation, source code, source software and
supporting software documentation.  The
Contractor shall also deliver to Inmarsat all design documentation, design
drawings and notes, manufacturing production and process information.

 

B.                                     The software, including but not limited to
documentation, design and manufacturing information, referred to in Paragraph A
of this Article 30 shall be updated at least once annually or at differing
intervals upon Inmarsat’s request.

 

C.                                     The software, including but not limited to
documentation, design and manufacturing information, referred to in Paragraph A
of this Article 30 shall include off the shelf third party software which
is included as part of the RAN to the extent that the Contractor has the right
to include it.

 

D.                                    In the event of the Contractor’s default or
Inmarsat’s termination of this Contract as determined in accordance with this
Contract or in the event of the Contractor’s insolvency or in any other
circumstances where the Contractor is unwilling or unable to manufacture,
maintain or support on reasonable terms and conditions the RAN, their
improvements and modifications, then Inmarsat shall be entitled (without prejudice
to any other rights hereunder) to non-exclusive, unrestricted, full,
royalty-free, and worldwide use of the source code, source software and
supporting software, design documentation, design drawings and notes,
manufacturing production and process information.

 

Article 31:                                    Assignment of Contract

 

A.                                   The Contractor shall not assign or delegate, either in whole or in
part, this Contract or any of the Contractor’s rights, duties, or obligations
hereunder to any person or entity without the prior express approval of
Inmarsat, which shall be at Inmarsat’s sole discretion.

 

B.                                     Notwithstanding any conditions under which Inmarsat may grant such
approval, the Contractor shall remain a guarantor to Inmarsat of the
performance of the assigned or delegated duties and obligations in accordance
with this Contract and all applicable laws.

 

20

 

C.                                     Inmarsat shall be entitled to assign or novate this Contract, or any
part thereof, and/or any rights or obligations or any deliverable items
hereunder to a third party or third parties subject only to such third party or
parties having, in the reasonable opinion of the Contractor, sufficient
financial resources to meet its payment obligations hereunder.  Such right may be exercisable on more than
one occasion.  For the avoidance of
doubt, should Inmarsat assign or novate the Contract or any part thereof as
aforesaid to a third party or parties, such third party or parties shall have
all rights under this Contract necessary to use, maintain, modify, repair of
otherwise enjoy the benefit of any deliverable item including but not limited
to the right to exercise any option hereunder. 
Insofar as any such option is stated with an indivisible price then such
option shall be apportioned between those exercising the same.

 

D.                                    The Contractor hereby acknowledges that Inmarsat may wish to
exercise the rights provided for in Article 31 C, among other things, so
as to transfer the Work to a third party or parties either in whole or in divisible
parts.  In such event, both parties
agree to act in good faith to minimise any adverse consequences on the
Work.  Inmarsat shall, if necessary,
assist any such third party or parties with necessary technical resource should
such transfer take place prior to delivery of the Work.  Insofar as any additional rights are
required under the Contract to achieve or implement such transfer then the
Contractor agrees to negotiate in good faith the grant of such rights on reasonable
terms and conditions.

 

Article 32:                                    Responsible Officers

 

The
responsible officers of the parties may be changed from time to time by notice
to the other party.  Until further
notice, the responsible officer for Inmarsat shall be Helga Cantrell – Senior
Contracts Manager, and for the Contractor, ****.

 

Article 33:                                    Communications

 

A.                                   All notices, reports, invoices and other correspondence to be
provided to Inmarsat or the Contractor pursuant to this Contract shall be sent
for the attention of the responsible officers referred to in Paragraph A
of Article 32 hereof, entitled Responsible Officers, at the following
addresses:

 

	
  INMARSAT:

  	
   

  	
  CONTRACTOR:

  
	
   

  	
   

  	
   

  
	
  Inmarsat
  Ltd

  	
   

  	
  Thrane
  & Thrane A/S

  
	
  99
  City Road

  	
   

  	
  Lundtoftegårdsvej
  93D

  
	
  London
  EC1Y 1AX

  	
   

  	
  DK-2900
  Lyngby

  
	
  England

  	
   

  	
  Denmark

  

 

B.                                     All communications pertinent to this Contract shall be made or
confirmed in writing, including telegram, telex, facsimile or electronic mail.

 

C.                                     All documentation and communications required under this Contract
shall be in the English language.

 

Article 34:                                    Time Limits

 

Any
time limits to which this Contract binds the Contractor or Inmarsat shall be
counted in calendar days from the day following that of the event marking the
start of the time limit, and shall end on the last day of the period laid down.  When the last day of a time limit is a
Saturday or Sunday, or a legal holiday in the country in which the particular
contractual performance is required, such time limit shall be extended to the
first Working day following.

 

Article 35:                                    Order of Precedence

 

Should
any conflict arise between any Annex hereto and the terms and conditions of
this Contract, the terms and conditions of this Contract shall take precedence.

 

Article 36:                                    Waiver

 

No relaxation
forbearance delay or indulgence by either party in enforcing any of the terms
and conditions of this Contract or the granting of time by either party to the
other shall prejudice affect or

 

21

 

restrict the
rights and powers of the said party nor shall any waiver by either party of any
breach hereof operate as a waiver of or in relation to any subsequent or any
continuing breach hereof.

 

Article 37:                                    Options

 

Inmarsat
shall have the following options available for exercise:

 

A.                                   Annually renewable maintenance support for a
period of up to eight (8) years in accordance with Annex A and B hereto,
entitled Statement
of Work and SRS.  The fixed
baseline price for each year of maintenance support following the first two (2)
years of Warranty shall be $**** subject to an annual increase in line
with inflation, but not to exceed 5%, and shall be payable in advance in
quarterly instalments, as set out in Annex D hereto entitled Price
Breakdown and Payment Plan.

 

B.                                     The option for Inmarsat to purchase additional
RNSs shall be subject to the firm fixed price per additional RNS for $****
excluding TT&C equipment and $**** including TT&C equipment. The
delivery time for each additional RNS shall not exceed ten (10) months from the
date the option is exercised.  This
option shall be available to Inmarsat from EDC until thirty-six (36) months
from Final Acceptance.

 

C.                                     The firm fixed price for additional channel
unit sub-systems shall be $**** per channel unit board consisting of
eight (8) channels and $**** for each channel unit subrack comprised of
one (1) subrack, two (2) GigaLAN Switches, and eight (8) Channel Boards for a
total of 64 channels.   The delivery
time for additional channel units shall not exceed six (6) months from the date
the option is exercised.  This option
shall be available to Inmarsat throughout the lifetime of the contract.

 

D.                                    The firm fixed price for
each set of additional Transportable Test Tools, consisting of one (1) UT
simulator and two (2) CN RTB simulators shall be $****. The delivery
time for additional Transportable Test Tools shall not exceed six (6) months
from the date the option is exercised.  This option shall be available to Inmarsat from EDC until thirty-six
(36) months from Final Acceptance.

 

E.                                      The man/day rates for BGAN system integration support over and above
the scope of work as defined in Article 1 hereto, entitled Scope of
Work shall be $****. 
This option shall be available to Inmarsat throughout the lifetime of
the contract.

 

F.                                      The firm fixed price for repeat training course over and above the
scope of work as defined in Article 1 hereto, entitled Scope of
Work shall be $**** per week .  Inmarsat shall give the Contractor at least three (3) months
notice of its intent to exercise this option. 
This option shall be available to Inmarsat from EDC until thirty-six
(36) months from Final Acceptance.

 

G.                                     The firm fixed price for ten (10) years of
engineering support to be provided by Contract during the BGAN integration and
testing phase shall be $****. 
Inmarsat shall give the Contractor at least three (3) months notice of
the time when such support will be required. 
This option shall be available to Inmarsat from EDC until thirty-six
(36) months from Final Acceptance.

 

H.                                    The firm fixed price for redundant AFC Pilot
Generators shall be $**** per site.  This option shall be available to Inmarsat from EDC until
thirty-six (36) months from Final Acceptance.

 

I.                                         The ROM price for a 16.4 metre antenna is $****
per antenna, over and above the price for a 13 metre antenna, which is firm
fixed at $****.  Inmarsat shall confirm
whether it wishes to proceed with this option no later than mid
October 2001.

 

J.                                        The cost reduction for deletion from the
baseline deliverable of one (1) CN Network Gateway is TBD — to be confirmed no
later than KOR.

 

K.                                    The cost reduction for deletion from the
baseline deliverables of one (1) or more RFS, is based on the recurring price
set out in Annex D hereto, entitled Price Breakdown and Payment Plan - to be
confirmed no later than KOR.

 

L.                                      The ROM price for
an independent Man Machine Interface (MMI) at the GRM is $****.  Inmarsat shall confirm whether it wishes to
proceed with this option no later than KOR.

 

22

 

Article 38                                        Warranty Support and Maintenance Support

 

A.                                   The warranty and maintenance support shall be
in accordance with Article 9 hereto, entitled Warranty as to Quality,
Article 39 hereto, entitled Spares, and Section 10 of Annex A
hereto, entitled Statement of Work.

 

B.                                     Upon expiry of the two (2) year warranty period
referred to in Article 9 hereof, entitled Warranty as to Quality, the
Contractor shall at Inmarsat’s option provide further maintenance and support
as set out in Annex A hereto, entitled Statement of Work, in Annex D hereto,
entitled Price
Breakdown and Payment Plan, and Annex E hereto, entitled Warranty and
Maintenance Plan.  Inmarsat
shall exercise its option for annual maintenance and support at least three (3)
months prior to expiration of the two year warranty period.  Maintenance shall be annually renewable at
the sole option of Inmarsat.  Such
option to renew shall be notified to Contractor at least three (3) months prior
to the expiration date of each annual maintenance period.

 

C.                                     The baseline annual maintenance price is $****
subject to annual increases in line with the formula provided under Annex D,
entitled Price
Breakdown and Payment Plan.

 

Article 39                                        Spares

 

The
Contractor shall guarantee the availability for a minimum of ten (10) years
from the date of Final Acceptance of all necessary spare parts, or in the event
of obsolescence provide similar equipment which meets the specifications of the
Contract, for the deliverable equipment as specified in Annex A hereto,
entitled Statement
of Work.

 

Article 40:                                    Entire Agreement

 

This
Contract constitutes the entire agreement between the parties with respect to
the subject matter hereof, and supersedes all prior or contemporaneous
correspondence, representations, proposals, negotiations, understandings, or
agreements of the parties, whether oral or written.  The parties also hereby acknowledge that there are no collateral
contracts between them with respect to the subject matter hereof. This Contract may be signed in counterparts and each original
counterpart shall be deemed binding on each party collectively and individually.   A person who is not a party to this Contract has no rights under the
Contracts (Rights of Third parties) Act 1999 to enforce any term of this
Contract but this does not affect any right or remedy of a third party which
exists or is available apart from that Act or any right of a party to this
Contract to enforce any term of this Contract for and on behalf of such third
party where applicable.

 

IN WITNESS
WHEREOF, the parties
hereto have signed this Contract in duplicate.

 

 

	
  THRANE AND THRANE A/S

  	
  INMARSAT LIMITED

  
	
   

  	
   

  
	
   

  	
   

  
	
  ****

  	
  BY: 

  	
  /s/ Michael
  Storey

  	
   

  
	
   

  	
   

  
	
  ****

  	
  Typed Name:

  	
  Michael
  Storey

  	
   

  
	
   

  	
   

  
	
  ****

  	
  Title: 

  	
  President
  & CEO

  	
   

  
	
   

  	
   

  
	
  ****

  	
  Date: 

  	
  August 1,
  2001

  	
   

  
							

 

23

 

	
  

  	
   

  	
  Contract INM-CO/01-2876/HC

   

  Broadband Global Area Network

   

  Radio Access Network (RAN)

  Annex A - Statement of Work

  

 

ANNEX A

 

STATEMENT OF WORK

 

A-1

 

INM-CO/01-2876/HC

 

ANNEX A

 

BGAN RADIO ACCESS NETWORK

 

STATEMENT OF WORK

 

 

TABLE OF CONTENTS

 

	
  1.

  	
  INTRODUCTION

  	
   

  
	
   

  	
   

  	
   

  
	
  1.1

  	
  PURPOSE AND SCOPE

  	
   

  
	
  1.2

  	
  DOCUMENT
  HIERARCHY

  	
   

  
	
  1.3

  	
  DEFINITION
  METHODOLOGY

  	
   

  
	
   

  	
   

  	
   

  
	
  2.

  	
  OVERALL FRAMEWORK

  	
   

  
	
   

  	
   

  	
   

  
	
  3.

  	
  TABLE 2:MILESTONE SCHEDULECONTRACTOR
  RESPONSIBILITIES

  	
   

  
	
   

  	
   

  	
   

  
	
  4.

  	
  INMARSAT RESPONSIBILITIES

  	
   

  
	
   

  	
   

  	
   

  
	
  5.

  	
  PROJECT AND
  SCHEDULE CONTROL

  	
   

  
	
   

  	
   

  	
   

  
	
  5.1

  	
  PROJECT PLANNING AND
  CONTROL

  	
   

  
	
  5.2

  	
  REVIEW MEETINGS

  	
   

  
	
  5.3

  	
  PROJECT
  SCHEDULING

  	
   

  
	
  5.4

  	
  PROJECT TEAM

  	
   

  
	
  5.5

  	
  LOCATION
  OF THE WORK

  	
   

  
	
  5.6

  	
  INMARSAT RIGHT OF ACCESS

  	
   

  
	
   

  	
   

  	
   

  
	
  6.

  	
  QUALITY AND
  CONFIGURATION CONTROL

  	
   

  
	
   

  	
   

  	
   

  
	
  6.1

  	
  QUALITY
  ASSURANCE

  	
   

  
	
  6.2

  	
  QUALITY CONTROL

  	
   

  
	
  6.3

  	
  RELIABILITY

  	
   

  
	
  6.4

  	
  CONFIGURATION MANAGEMENT

  	
   

  
	
   

  	
   

  	
   

  
	
  7.

  	
  TEST
  AND INTEGRATION

  	
   

  
	
   

  	
   

  	
   

  
	
  7.1

  	
  GENERAL TEST REQUIREMENTS

  	
   

  
	
  7.2

  	
  DESIGN
  PROVING/PROTOTYPE TESTING

  	
   

  
	
  7.3

  	
  UNIT TESTING

  	
   

  
	
  7.4

  	
  INTEGRATION TESTING

  	
   

  
	
  7.5

  	
  BGAN
  SERVICE DEMONSTRATION AND SYSTEM INTEGATION

  	
   

  
	
  7.6

  	
  FACTORY AND SITE
  ACCEPTANCE TESTING

  	
   

  
	
   

  	
   

  	
   

  
	
  8.

  	
  DELIVERY AND INSTALLATION

  	
   

  
	
   

  	
   

  	
   

  
	
  8.1

  	
  RAN
  SITE SURVEYS

  	
   

  
	
  8.2

  	
  EQUIPMENT DELIVERY
  PREPARATION

  	
   

  
	
  8.3

  	
  EQUIPMENT
  TRANSPORTATION AND SHIPMENT

  	
   

  
	
  8.4

  	
  SITE INSTALLATION AND
  INTEGRATION

  	
   

  
	
   

  	
   

  	
   

  
	
  9.

  	
  TRAINING

  	
   

  
	
   

  	
   

  	
   

  
	
  9.1.

  	
  GENERAL REQUIREMENTS

  	
   

  
	
  9.2.

  	
  OPERATOR TRAINING
  REQUIREMENTS

  	
   

  
	
  9.3.

  	
  ENGINEERING TRAINING
  REQUIREMENTS

  	
   

  
	
   

  	
   

  	
   

  
	
  10.

  	
  WARRANTY AND MAINTENANCE

  	
   

  

 

A-3

 

	
  10.1

  	
  GENERAL
  REQUIREMENTS

  	
   

  
	
  10.2

  	
  WARRANTY AND SUPPORT
  REQUIREMENTS

  	
   

  
	
  10.3

  	
  SUPPORT DURING
  WARRANTY AND MAINTENANCE

  	
   

  
	
  10.4

  	
  WARRANTY AND
  MAINTENANCE PROCEDURES

  	
   

  
	
  10.5.

  	
  TELEPHONE
  ON-CALL TECHNICAL WARRANTY AND MAINTENANCE SUPPORT

  	
   

  
	
  10.6.

  	
  FAULT
  REPORTING

  	
   

  
	
  10.7.

  	
  ON-SITE
  ATTENDANCE

  	
   

  
	
  10.8.

  	
  PROBLEM
  RESOLUTION

  	
   

  
	
  10.9.

  	
  STATUS
  REPORTING

  	
   

  
	
  10.10

  	
  WARRANTY AND
  MAINTENANCE CHANGE CONTROL

  	
   

  
	
  10.11

  	
  RELEASE
  CONTROL

  	
   

  
	
  10.12.

  	
  SUPPORT
  ACTIVITIES

  	
   

  
	
   

  	
   

  	
   

  
	
  11.

  	
  DELIVERABLE DOCUMENTATION

  	
   

  
	
   

  	
   

  	
   

  
	
  12.

  	
  APPLICABLE STANDARDS

  	
   

  
	
   

  	
   

  	
   

  
	
  12.1.

  	
  SITE
  REQUIREMENTS

  	
   

  
	
  12.3

  	
  ENVIRONMENTAL CONDITIONS

  	
   

  
	
  12.4

  	
  HEALTH
  AND SAFETY

  	
   

  
	
   

  	
   

  	
   

  
	
  13.

  	
  TEST
  FACILITIES

  	
   

  
	
   

  	
   

  	
   

  
	
  13.1.

  	
  REFERENCE TEST BED (RTB)

  	
   

  
	
  13.2.

  	
  TRANSPORTABLE TEST TOOLS

  	
   

  
	
   

  	
   

  	
   

  
	
  14.

  	
  SYSTEM INTEGRATION EFFORT

  	
   

  
	
   

  	
   

  	
   

  
	
  14.1

  	
  BGAN DEVELOPMENT
  COORDINATION FORUM

  	
   

  
	
  14.2

  	
  ACCESS TO REFERENCE TEST
  BED

  	
   

  
	
  14.3

  	
  SYSTEM INTEGRATION SUPPORT

  	
   

  
	
   

  	
   

  	
   

  
	
  APPENDIX A -
  ABBREVIATIONS

  	
   

  
	
   

  	
   

  	
   

  
	
  APPENDIX B

  	
   

  

 

A-4

 

1.                                      INTRODUCTION

 

1.1                               Purpose and Scope

 

This Statement
of Work (SOW)
defines the work to be performed by the Contractor for the Inmarsat Broadband
Global Area Network (BGAN) Radio Access Network (RAN).

 

The technical
and operational requirements for the RAN are given in the RAN System
Requirements Specification (SRS) document.

 

The System
Overview Document (SOD) is an information document outlines
the overall scope of the BGAN system, of which the RAN is a part.

 

1.2                               Document Hierarchy

 

This Statement
of Work concerns the design, development, implementation and test of the user,
ground and business equipment required to deliver BGAN services.

 

The contract
documentation has been structured as per Table 1 below, containing either
mandatory or guidance information as identified.

 

	
  Document

  	
   

  	
  Type

  	
   

  	
  Content
  Summary

  
	
  Statement of Work (SOW)

  	
   

  	
  Mandatory

  	
   

  	
  Outlines how the work is to be organised, managed and controlled.

  
	
  System Requirements Specifications (SRS)

  	
   

  	
  Mandatory

  	
   

  	
  Identifies the technical and operational requirements for the work.

  
	
  System Overview Document (SOD)

  	
   

  	
  Guidance

  	
   

  	
  Outlines the overall scope of the BGAN system development, of which
  this contract is a part.

  

 

Table 1: RAN Documentation

1.3                               Definition Methodology

 

The meaning of
the following terms is appropriate throughout this SOW and its subsidiary
documents:

 

Shall                                                                   Represents a mandatory requirement that must be implemented in full
by the Contractor or Inmarsat as noted.

Should                                                         Represents a desirable requirement whose implementation (in full or
in part) is considered advantageous to the service.

 

A-5

 

Text that does
not contain either shall
or should is to be
considered as background information, provided to explain further the rational
behind the overall Programme and requirements placed.

 

2.                                      OVERALL FRAMEWORK

 

1.               The Contractor shall be fully responsible for all tasks
related to the design, development, fabrication, integration, testing, and
delivery of the RAN.  The RAN consists
of a number of Radio Network Subsystems (RNS) compatible with ETSI UMTS Release
4 specifications, installed at designated Satellite Access Station (SAS) site
locations.

2.               The Contractor shall be responsible for all programme
management tasks including formal reporting to Inmarsat on Programme status.

3.               The Contractor shall plan for the work being conducted in
accordance with the contractual milestones and associated
schedule identified in Table 2 below.

4.               Inmarsat approval shall be required for successful completion
of all contractual milestones defined in Table 2 below.

5.               The Contractor shall support Inmarsat in the
standardisation of the selected Air Interface specification, as the Satellite
Component of IMT-2000/UMTS by the International Telecommunications Union (ITU),
the European Telecommunications Standards Institute (ETSI) and the American
National Standards Institute (ANSI).

6.               Final acceptance of the work shall be based on the completion of all
contractual requirements.

7.               The Contractor shall enter the warranty period and
subsequent maintenance arrangements upon completion of the Final Acceptance.

8.               Inmarsat will chair a Change Control Board (CCB) consisting of
representatives of all contracted BGAN equipment manufacturers (AMN, UT, BSS
etc) which will be responsible for agreement of any changes to the baseline Air
Interface definition for the programme.  
The draft guidelines for the conduct of the CCB are given in Appendix B.

 

A-6

 

	
  No.

  	
   

  	
  Milestone
  Activity

  	
   

  	
  Required
  Completion Date

  
	
  1)

  	
   

  	
  Kick-off
  Review (KOR)

  	
   

  	
  ****

  
	
  2)

  	
   

  	
  Preliminary
  Design Review (PDR)

  	
   

  	
  ****

  
	
  3)

  	
   

  	
  Final Design
  Review (FDR)

  	
   

  	
  ****

  
	
  4)

  	
   

  	
  Radio
  Frequency Subsystem (RFS) Delivery

  	
   

  	
  ****

  
	
  5)

  	
   

  	
  RAN
  Reference Test Bed (RTB) Ready

  	
   

  	
  ****

  
	
  6)

  	
   

  	
  Site
  Readiness Review (SRR)

  	
   

  	
  ****

  
	
  7)

  	
   

  	
  RAN RTB
  Delivery

  	
   

  	
  ****

  
	
  8)

  	
   

  	
  Factory
  Acceptance Test Review (FATR)

  	
   

  	
  ****

  
	
  9)

  	
   

  	
  Site
  Acceptance Test Review (SATR) for Site 1

  	
   

  	
  ****

  
	
  10)

  	
   

  	
  Final
  Acceptance

  	
   

  	
  ****

  

 

3.                                      Table 2: Milestone
Schedule / CONTRACTOR
RESPONSIBILITIES

 

This
Section defines the equipment and services to be provided under this
Contract.

 

4.               The Contractor shall deliver, install and commission the Radio
Access Network (RAN) equipment to the three (3) sites designated by Inmarsat.

5.               The Contractor shall develop or procure test procedures
and equipment for the purpose of Factory Acceptance Tests (FAT).

6.               The Contractor shall ensure proper integration and
inter-working with other BGAN subsystems, in accordance with the agreed
Interface Control Documents (ICD), for the purpose of Site Acceptance Tests
(SAT).

7.               The Contractor shall provide all equipment (including
cabling, installation materials, but excluding site facilities, external
connections and consumable etc.), executable software, firmware and associated
documentation necessary to build, install, configure, operate and maintain the
RAN.

8.               The Contractor shall deliver to Inmarsat all application
software, standard third party COTS software, data definitions, databases and
necessary data required for the satisfactory operation and maintenance of all
site and test equipment delivered under this contract.

9.               The Contractor shall be responsible for producing site
layout plans in liaison with Inmarsat (and the site operator) showing where the
equipment is to be installed, cable runs, power layout, earthing points, etc.
(cf. Site Installation Document).

10.         The Contractor shall
provide option pricing for the production and delivery of additional RNS to
additional designated sites.

 

A-7

 

11.         The Contractor shall participate in the ICD Change Control
Board (as defined in Appendix B) and the BGAN Development Coordination Forum
(as defined in section 14.1).

12.         The Contractor shall deliver a descoped Reference Test Bed
(RTB) (RAN on the Bench) to Inmarsat by January 2003 for UT compatibility
testing

 

4.              Inmarsat responsibilities

 

Inmarsat shall
be responsible for providing the following:

 

a)                                      Provisioning of the site facilities including the building (antenna
foundation, temporary antenna erection crane and RF shelter) and associated
infrastructure facilities (e.g. air conditioning, mains AC and DC power, UPS, temporary
storage, site access, cable ways etc.) and COTS test equipment in readiness for
equipment installation.

b)                                     Obtaining all necessary local operating licences for test sites
including radiated tests.

c)                                      If a designated site is not operated by Inmarsat then Inmarsat will
be responsible for obtaining proper authorisation, access and co-operation for
the Contractor to fulfil their contractual obligations and for ensuring that
Contractor equipment is safe-guarded at the site.

d)                                     Suitable office facilities and amenities to Contractor staff at the
nominated site plus Inmarsat HQ, including reasonable use of
telecommunications, etc

e)                                      Chairmanship and administration of the Air Interface Change Control
Board, which will be responsible for controlling changes to the baseline AI
specification.

f)                                        Leading the efforts to establish the selected Air Interface as the
standard for the Satellite Component of UMTS/IMT-2000 by the International
Telecommunications Union (ITU), the European Telecommunications Standards Institute
(ETSI) and the American National Standards Institute (ANSI).

g)                                     Providing draft Interface Control Documents (ICD) for all external
interfaces to the RAN.

h)                                     Ensuring the availability of other BGAN subsystems at their
respective on-site locations, by EDC + 24 months, to enable the Contractor to
perform the RAN Site Acceptance Tests.

i)                                         Ensuring the availability of the BGAN Core Network Reference Test
Bed by EDC + 9 months, for the purpose of interworking testing with the RAN
under development.

j)                                         Providing a baseline Air Interface (AI) definition by KOR, and a
finalised AI definition by PDR. 
Inmarsat would be responsible for validation of correctness and
performance of the AI specification.

k)                                      Providing access to a prototype version of the Payload Control
System (PCS) by EDC + 12 months, for integration testing with the RAN under
development

 

A-8

 

To support these activities then:

 

1.                                       The Contractor shall provide a final SAS Facilities
Requirement Specification not later than the Preliminary Design Review (PDR).

2.                                       The Contractor shall be given formal and sufficient access
to the SAS site at installation and test time on condition that the Contractor:

 

1.4         Notifies
Inmarsat formally of the intent to visit at least two weeks before the actual
day.

1.5         Undertakes
to adhere to all site procedures and regulations in place at the site (e.g.
safety, security, on-site working hours, etc.).

 

1.                                       The Contractor shall provide final details (by PDR) of the
equipment (i.e. floor sizing, etc.) requirements and facilities required at the
Inmarsat NOC/BOC to enable installation at the site.

2.                                       The Contractor shall provide the necessary information to
Inmarsat in order to obtain local licences.

 

5.              Project and
schedule control

 

5.1                               Project Planning and Control

 

1.               Contractor (and subcontractor) management and development processes shall adhere
to Contractor ISO-9001 (or equivalent) processes. Inmarsat shall have the right
to audit the contractor management and development practices applied to this
contract.

2.               The Contractor shall develop and maintain a Project
Management Plan (PMP) - based on the draft version submitted as part of the
proposal.

3.               The PMP shall outline the various project
activities to be performed together with the control procedures that are to be
applied and project schedule (see Section 5.3).

4.               The PMP shall describe the proposed management team
structure together with the overall responsibilities (including any key
subcontractors).

5.               The PMP shall describe how the Contractor will
manage and provide visibility of all work undertaken by any key subcontractors.

6.               The Contractor shall maintain a Risk Management Plan.

7.               The Project Management Plan and Risk Management Plan shall be
formally issued within one month of contract commencement.

8.               The contractor shall report status and provide Inmarsat
with any subsequent updates to the Project Management Plan and Risk Management
Plan in accordance with the contract requirements.

9.               Thereafter, the Contractor shall maintain the plans in line with the
work being performed.

10.         The Contractor shall maintain
all project documentation related to project planning and provide all
deliverables in electronic form.

 

A-9

 

5.2                               Review Meetings

 

5.2.1                     Milestone Review Meetings

 

1.               The Contractor shall agree the actual time of each project
milestone review meeting with Inmarsat at least one month before the meeting.

2.               The Contractor shall provide an agenda for each project
milestone review at least 5 working days before the meeting to which Inmarsat
may add items to discuss.

3.               The Contractor shall plan and conduct as a minimum the
project review meetings defined in Table 3

4.               The Contractor shall agree to support additional intermediate
progress reviews during the design and implementation, if requested to do so by
Inmarsat with at least three weeks notice.

5.               The Contractor shall be responsible for assembling the
relevant documentation and presentational material for all project reviews.

6.               The Contractor shall submit the documentation to be
reviewed at the meeting in accordance with the document delivery
schedule within this SOW.

7.               Inmarsat intends to use Review Item Discrepancy (RID)
forms for feeding back comments with respect to the documentation being
reviewed. The Contractor shall incorporate the RID mechanism into
the project milestone review process.

8.               The Contractor shall be responsible for documenting the
review proceedings and monitoring the actions placed.

9.               The minutes shall be produced within five working days
of the meeting.

10.         Inmarsat’s concurrence shall be sought for the minutes of formal
meetings

11.         Actions placed shall be tracked via a formally documented
procedure.

12.         The Contractor shall implement an internal design review
process on all hardware, firmware and software design activities as per
standard engineering practice.

13.         The Contractor shall conduct process compliance audits to
confirm that design processes are followed.

14.         The Contractor shall provide Inmarsat the right to call
for additional technical milestone review meetings with reasonable advanced
notice at either Inmarsat or the Contractor site if it is felt there is a need
to resolve issues expediously.

 

A-10

 

	
  No.

  	
   

  	
  Review
  Meeting

  	
   

  	
  Purpose

  	
   

  	
  Inputs

  	
   

  	
  Duration

  (Days)

  	
   

  	
  Location

  
	
   

  	
   

  	
  KICK-OFF
  MEETING (KOR)

  	
   

  	
  This review shall include:

   

  a)
  communication lines and contact points for financial, contractual and
  technical matters;

   

  b)
  Management plan(s) review;

   

  c)
  Short-term work plan review;

  d)
  Accommodation of Inmarsat staff at site premises;

  e) First
  review of the baseline Air Interface (AI).

  	
   

  	
  •     Project
  Management Plan (PMP);

  •                  Risk Management Plan (RMP);

  •                  Quality Assurance Plan (QAP);

  •                  Configuration Management Plan (CMP);

  	
   

  	
  2

  	
   

  	
  Contractor
  Premises

  
	
  2.

  	
   

  	
  PRELIMINARY
  DESIGN REVIEW (PDR)

  	
   

  	
  This review shall include:

  a) Review of
  the System Requirements Allocation and System Functional Specification. The
  Contractor is required to demonstrate that the contractually agreed
  requirements have been partitioned into a thorough and consistent system
  definition;

  b) Review of
  the traceability mapping between the contractually agreed requirements and
  the system functional specifications and the further allocation to SAS subsystems;

  c)
  Identification of the external interfaces and review of preliminary interface
  control documents;

  d) Review
  the network analysis and sizing that has been

  	
   

  	
  •                  System Requirements Allocation;

  •     System
  Operations Concept;

  •                  System Functional Specification - including traceability matrix;

  •                  Overall System Test Plan;

  •                  External Interface Control Document

  •                  Training Plan;

  •                  Facility Requirement Specification;

  •                  Common Air Interface

  •                  System Design Document;

  	
   

  	
  5

  	
   

  	
  Contractor
  Premises

  

 

A-11

 

	
   

  	
   

  	
   

  	
   

  	
  performed to
  dimension the RAN - this will be incorporated in the system functional
  specifications;

  e) Review
  the overall System Test Plan. This will outline the various test stages to be
  conducted together with a schedule of development;

  f) Review of
  radio equipment and operations training requirements.

  g) Review of
  SAS and NOC infrastructure requirements.

  h) Review of
  the BGAN Air Interface.

  The primary
  review material will be the documents delivered as review inputs. Inmarsat is
  expected to read and provide written comments for discussion at the meeting.
  This review material will be supplemented with summary presentation slides.

  	
   

  	
  •                  Requirements Allocation;

  •                  System Architecture Document;

  •     Operations
  Concept;

  	
   

  	
   

  	
   

  	
   

  
	
  3.

  	
   

  	
  FINAL DESIGN REVIEW (FDR)

  	
   

  	
  This review shall include:

  a) Review of
  the updated system documents from the PDR for completeness and consistency
  with requirements;

  b) Review of
  the System Design Document end-to-end performance model showing predicted
  performance of user applications;

  c) Review of
  RAN segment design to subsystem level and

  	
   

  	
  •                  System Requirements Allocation;

  •                  System Operations Concepts;

  •                  System Design Document;

  •                  System Functional Specification (including traceability matrix);

  •                  Requirements Allocation;

  	
   

  	
  5

  	
   

  	
  Contractor
  Premises

  

 

A-12

 

	
   

  	
   

  	
   

  	
   

  	
  including
  operations concepts and MMI interfaces;

  d) Review of
  RAN resource management algorithms and results of associated performance
  models.

  e) Review of
  the RAN test plans.

  f) Finalisation
  of training plan

  g) Finalisation
  of RAN Facilities Requirements.

  h) Finalise
  the Common Air Interface for implementation

  k) Review of
  status of action items from the PDR.

  The primary
  review material will be the documents delivered as review inputs. Inmarsat is
  expected to read and provide written comments for discussion at the
  meeting.  This review material will be
  supplemented with summary presentation slides.

  	
   

  	
  •                  System Architecture Document (including traceability matrix to the
  SFS);

  •                  System Test Plan;

  •                  Acceptance Test Plan;

  •                  Factory Acceptance Test (FAT) Plan;

  •                  Site Acceptance Test (SAT) Plan;

  •                  Facility Requirement Specification;

  •                  Training Plan;

  •                  BGAN Air Interface ;

  •                  Operations Concepts;

  •                  MMI Design Document

  •                  Recommended Spares List;

  	
   

  	
   

  	
   

  	
   

  
	
  4.

  	
   

  	
  SITE READINESS REVIEW (SRR)

  	
   

  	
  This review shall review
  the readiness of the SAS site to accept delivery and installation of the
  Contractor SAS equipment.

  	
   

  	
  •                  Facilities Requirement Specification;

  	
   

  	
  2

  	
   

  	
  SAS site

  

 

A-13

 

	
  5.

  	
   

  	
  FACTORY ACCEPTANCE TEST REVIEW (FAT)

  	
   

  	
  This review shall
  include:

  a) Review of
  all outstanding issues with FAT Plan and FAT Procedures;

  b) Review of
  the FAT Readiness Report;

  c) Review of
  the Configuration Report;

  	
   

  	
  •                  FAT Plan;

  •                  FAT Procedures;

  •                  FAT Readiness Report;

  •                  FAT Configuration Report;

  	
   

  	
  2

  	
   

  	
  Contractor
  Site (Factory)

  
	
  6.

  	
   

  	
  FIRST SITE ACCEPTANCE TEST REVIEW (SAT)

  	
   

  	
  This review shall
  pertain to the first SAS site and include:

  a) Review of
  any outstanding issues with SAT Plan and SAT procedures;

  b) Review of
  SAT Readiness Report;

  c) Review of
  SAT Configuration Report;

  	
   

  	
  •                  SAT Plan;

  •                  SAT Procedures;

  •                  SAT Readiness Report;

  •                  SAT Configuration Report;

  •                  Installation and Maintenance Manuals;

  	
   

  	
  2

  	
   

  	
  SAS site #1

  
	
  7.

  	
   

  	
  FINAL SITE ACCEPTANCE TEST REVIEW

  	
   

  	
  This review shall
  pertain to all subsequent SAS sites and include:

  a) Review of
  the completion of Site Acceptance Tests for all contracted SAS sites.

  b) Review of
  any outstanding issues related to all previous milestones

  	
   

  	
  •                  As above

  	
   

  	
  3

  	
   

  	
  Contractor
  Site (Factory)

  

 

Table 3: Milestone Reviews

 

A-14

 

5.2.2                     Progress Reporting

 

1.                                       The Contractor shall supply a progress report to Inmarsat
by the end of the first week of each month, and in time for the monthly
progress review meeting covering:

1.4                      Work performed during the reporting period;

1.5                      Milestones met and/or achieved;

1.6                      Progress against the schedule (see Section 4.4). Any
slippage is to be identified together with remedial action;

1.7                      Dependencies;

1.8                      Problems experienced;

1.9                      Activities planned for the next period;

1.10                Risk Log status;

 

2.                                       The format of the progress report shall be agreed with Inmarsat
at the Project Kick-off Review meeting.

3.                                       Inmarsat shall have the right to request the
Contractor to provide direct key subcontractor progress reports.

4.                                       The Contractor shall conduct a monthly progress meetings
with representatives of Inmarsat (either at Contractor’s premises or,
alternatively, by telephone/video conference) where the following shall be
discussed :

 

4.4                                 Current active tasks;

4.5                                 Technical and schedule aspects;

4.6                                 Status and progress;

4.7                                 Technical, contractual and managerial issues;

4.8                                 Risks and contingency measures (in the form of a Risk Log);

4.9                                 Current and potential problems;

 

5.                                       The Contractor shall minute the meeting proceedings
capturing the key decisions and all actions taken.

6.                                       The minutes shall be agreed with Inmarsat.

7.                                       The minutes shall be produced within five working days
of the meeting.

8.                                       Inmarsat reserves the right to call for additional meetings.

 

5.2.3                     Extraordinary Management Meetings

 

1.               At any point in the Programme, either Inmarsat or the Contractor shall have
the right to call an Extra Ordinary Senior Management meeting, should a major
issue arise.

2.               Each meeting shall require at least ten working days
notification.

 

5.3                                        Project Scheduling

 

3.               The Contractor shall maintain a detailed activity
schedule of all tasks to be undertaken for this contract.

4.               This schedule shall be maintained with a unique reference
number in order that it can be regularly updated as work progresses.

 

A-15

 

5.               The schedule shall reflect the following overall
breakdown levels:

3.1.                              Level 1:
Project decomposed into phases;

3.2.                              Level 2:
Phases decomposed into work packages;

3.3.                              Level 3:
Work packages decomposed into tasks;

6.               All levels shall be maintained within the one
consistent schedule in order to ensure consistency between the levels.

 

7.               The Contractor shall define a suitable Work Breakdown
Structure (WBS) and produce work package descriptions (WPD)
for each level 2 activity.

8.               The Contractor’s WBS shall clearly identify the following key
activities:

•                  System Design

•                  Segment Design

•                  Subsystem Design

•                  Implementation

•                  Factory Acceptance
Test

•                  Site Acceptance Test

9.               The WBS shall be used to plan and organise the
work.

10.         The WBS shall cover all project activities from
contract commencement to the end of the warranty period.

11.         The WBS and initial set of WPDs included in the draft PMP shall be
agreed at the Project Kick-off review.

12.         Thereafter, the Contractor shall progressively expand the WBS and
raised further WPs, as required for management and reporting purposes.

13.         The Contractor should not commence a level 2 task if the
associated WPD has not been raised.

14.         The schedule shall clearly identify the scope of
design/development/test work that has been assigned to any key
sub-contractor(s).

15.         Inmarsat shall have the right to audit the work of the
key sub-contractors at the place where the work is being conducted.

16.         The programme schedule shall be developed and maintained using
Microsoft Project.  The following views
shall be presented (as a minimum):

 

.1.            Bar Chart (Gantt) View - for basic completion status;

.2.            Network Activity View - for critical path analysis;

 

1.               The Contractor shall include a schedule showing work
completed in the monthly progress report.

2.               The Contractor shall also provide Inmarsat with an
electronic copy of the Monthly Report including the schedule.

 

5.4                               Project Team

 

3.               The Contractor shall assign a suitably qualified programme
manager for the duration of this contract, specifically charged with the
responsibility for all aspects of the Contract.

4.               The Programme Manager shall serve as the interface with Inmarsat
for the duration of the Contract and at least until the end of the warranty
period.

 

A-16

 

5.               The Contractor shall support open lines of communications
to respective representatives from each party with respect to technical
matters.

 

5.5                                        Location of the Work

 

1.               The Contractor shall provide office accommodation at the
main site that work in being conducted during the development and
implementation phase.

2.               This accommodation shall provide space for at least two Inmarsat
resident staff plus up to six temporary visiting staff.

3.               Office accommodation shall include reasonable use of facilities
including international telephone/facsimile lines, desktop PCs with Internet
connection, etc.

 

5.6                               Inmarsat Right of Access

 

Inmarsat will
appoint a number of project co-ordinators who will work to monitor and
facilitate where necessary the activities being undertaken on this contract.

 

4.               The Contractor shall allow the Inmarsat project
co-ordinators access to the main work site, given reasonable notice.

5.               Visits to other work sites shall be supported at an agreed date and
with specified objectives.

 

It should be
noted that the on-site representative(s) will not be authorised to agree
requirement or contract changes without going through the formal change
process, specified in the Contract.

 

6.              Quality and
configuration control

 

6.1                               Quality Assurance

 

6.               The Contractor shall hold a currently valid ISO9001 (or
suitable equivalent) accreditation to cover both the design, manufacture and
software development activities.

7.               The Contractor shall control and manage the Programme in
accordance with ISO 9001 (or equivalent) standards.

8.               A Quality Assurance Plan (QAP) shall be issued to Inmarsat at the Kick-Off
review for comment, based on the draft QAP submitted in the Proposal.

9.               Any subsequent changes to the QAP following formal issue shall require
Inmarsat approval.

10.         In the case of software development, a formal software quality management
process that is compliant with ISO 9001 (or equivalent) shall be employed.

11.         The Contractor shall nominate a team member to be fully
responsible for overall QA on this project.

12.         This nominated team member shall have suitable experience and training
with respect to ISO9001 (or equivalent) and its application to a large
programme.

 

A-17

 

13.         The QAP shall at all times reflect the actual
practices being applied on the Project.

14.         The software elements of the project shall be developed in
accordance with the Contractor ISO 9001 (or equivalent).

15.         The software engineering approach and standards shall be defined in
the Software Management Plan (SMP).

16.         The Contractor shall submit as part of the QAP, an audit
schedule outlining the audits (minimum of three) to be conducted
throughout various points of each sub-programme.

17.         The Contractor shall document each scheduled audit in the
form of an Audit Report.

18.         The Audit Report shall be made available to Inmarsat on
request.

 

14.         Inmarsat reserves the right to audit Contractor work at any point in
the Project, provided that at least two weeks notice is given to the Contractor
Programme Manager.

 

15.         The Contractor shall be fully responsible for the quality
achieved and controls applied by any sub-contractor parties used.

 

16.         The ISO9001 (or suitable equivalent) quality conditions are to be
flowed down to each sub-contractor involving design, development and/or testing
activities.

 

17.         The Contractor shall provide a quarterly Quality Assurance
Progress Statement to Inmarsat outlining the quality activities undertaken
during the reporting period.

18.         The Contractor shall have in place a Non-Conformance
Control mechanism.

19.         The Contractor shall have a mechanism for tracking
corrective actions at all project phases.

20.         Inmarsat shall have authority to approve or reject
all non-conforming items (waivers or deviations to the contract requirements)
prior to acceptance testing or as part of an Acceptance Test Review.

21.         A suitable tracking mechanism shall be used to map the Inmarsat
requirements to the Contractor definition, design and subsequent testing
documentation.

22.         This tracking mechanism shall be presented at the Project Kick-off
review.

 

6.2                               Quality Control

 

1.                           Quality
controls to be applied during the manufacturing process shall be clearly stated in
the Quality Assurance Plan or alternate document.

2.                           The levels
of inspection from initial goods-inwards to final inspection and test shall be
stated at the outset.

3.                           All
inspection and quality records shall be archived by the Contractor as per
Contractor’s ISO 9001 (or equivalent) process, and be available for Inmarsat
audit at the Contractor facility on a non-interfering basis if requested.

 

A-18

 

6.3                               Reliability

 

1.                                       The Contractor shall produce a Reliability (Parts Count)
Prediction (to be included in the relevant System Documentation) for all
new/modified elements of the RAN using an Industry recognised technique (e.g.
Bellcore).  This may incorporate
reliability figures of existing parts/equipment based on experienced service.

2.                                       The reliability analysis shall determine both the MTBF and MTTR
times down to sub-system level. Vendor information may be used where available
for existing equipment otherwise budgetary predictions may be employed.

3.                                       Availability analysis and Reliability Prediction shall be
used to demonstrate confidence that the RAN subsystems availability and outage
performance criteria can be met.

4.                                       The Contractor shall keep a record of each equipment
failure (hardware, software, firmware) incident that occurs from the
commencement of the Factory Acceptance Testing Phase (see Section 7.5.2)
until System Acceptance.

5.                                       The records should be held in a database which can
provide information for the whole system or for individual elements, according
to severity and status.

 

6.4                               Configuration Management

 

19.         The Contractor shall produce an overall Configuration
Management Plan (CMP) outlining the controls that will be applied to:

 

1.1.                              Documentation
Configuration and Change Management;

1.2.                              Requirements
Management;

1.3.                              Software
Development, Version and Release Control;

1.4.                              Firmware
Development, Version and Release Control;

8.5                                 Hardware
Development and Manufacture;

 

2.                                       The CMP shall be finalised by the project kick-off
review.

3.                                       The CMP (and any subsequent updates) shall require Inmarsat
approval.

4.                                       The Contractor shall nominate a team member to be
responsible for overall configuration management throughout the project.

5.                                       Adherence to the CMP shall be maintained throughout the project.

6.                                       Configuration management to be applied to sub-contractor work (if
used) shall
be identified.

7.                                       Configuration records for Contractor developed and delivered software
and equipment shall be made available to Inmarsat on request. Configuration
records for design and assembly of COTS products and standard switching
products may be unavailable.

 

A-19

 

7.                                      TEST and INTEGRATION

 

Each
element of the RAN is to be functionally tested before being integrated with
other elements. Thereafter, integration should be progressive, as interfaces
are verified between the equipment that makes up RAN. When sufficient elements
have been integrated then acceptance testing can commence. The actual details
of testing are to be defined in the RAN Subsystem Test Plan to be provided at
the preliminary design review. However, Inmarsat will be looking to ensure that
the overall test programme proposed addressed the following types of testing:

 

1.                          Prototype/Early Design
Proving Testing: To ensure critical new areas in
the design are tested for feasibility. Requirements for this testing are
discussed in Section 7.2.

2.                          Unit/Module Testing:  Involves functionality
testing of a specific hardware, firmware or software unit typically with inputs
generated from a test harness. 
Requirements for this testing are discussed in Section 7.3.

3.                          Subsystem Integration
Testing: 
Involves checking interfaces between the respective SAS components and
checking the functionality that extends across sub-systems. Typically such
testing involves the use of a test bed or suitable simulator in which elements
of the system are progressively integrated. Requirements for this testing are
discussed in Section 7.4 and 7.5.

4.                          FAT/SAT Acceptance Testing: This represents an iteration of testing levels that collectively
provide verification of the RAN equipment against the overall requirements.
Testing will encompass in-house factory acceptance testing of the SAS
equipment, on-site acceptance testing of the SAS and ground segment acceptance
testing between the SAS (via the regional satellite) and other sites in the
architecture (e.g. regional AOC, regional GS, etc.). Requirements for this
testing are discussed in Section 7.6.

 

7.1                                                  General Test Requirements

 

Unless
specified otherwise, the Contractor is expected to provide all test beds,
equipment and measuring instruments required to complete the appropriate level
of factory testing. For site acceptance Inmarsat will provide any necessary
COTS equipment (e.g. spectrum analysers).

 

1.                                       The Contractor shall produce and maintain test plans, test
designs and test procedures and test reports for all test levels covering
hardware, firmware and software as required by his ISO 9001 standards (or
equivalent).

2.                                       By PDR, the Contractor shall deliver a complete and comprehensive
RAN Test Plan defining the test approach to be adopted, acceptance test mapping
(i.e. Verification Requirements Traceability Matrix - VCRM) and associated test
document structure to demonstrate

 

A-20

 

coverage of all contracted requirements as required by
his ISO 9001 standards.

3.                                       The Contractor shall develop a comprehensive set of test
procedures for each acceptance test activity. For switching system standard
products, existing product test results or product conformance statements may
be provided in lieu of new tests to demonstrate network element requirement
conformance.

4.                                       Test procedures developed for the acceptance phase shall require
Inmarsat approval.

5.                                       The test procedures shall comprise tests, inspections, analyses
and demonstrations, which demonstrate that the system is able to deliver
contract end-to-end functionality.

6.                                       Test procedures shall be presented to Inmarsat before the
actual testing is conducted.

7.                                       Inmarsat shall have the right to approve or request
reasonable amendments to the acceptance test plans and procedures.

8.                                       All acceptance test results shall be documented in the form of test
reports.

9.                                       The test report shall present the:

 

9.1              Test results (i.e.
pass/fail),

9.2              Conductor of the test,

9.3              Comments made regarding
the test run,

9.4              Reason for any failures;

 

10                                    The
Contractor shall provide to Inmarsat all acceptance test plans,
procedures and test reports.

11.                                 The
Contractor shall provide all instruments, tools, facilities, manpower and
services necessary to conduct the acceptance tests other than stated Inmarsat
requirements (see Section 4.5).

12.                                 All
Acceptance Tests shall be witnessed and acknowledged by both Inmarsat and the
Contractor representatives. Inmarsat at its sole discretion may waive its right
to witness given tests.

13.                                 Any
agreed Inmarsat residents shall have access to the primary factory
integration lab and may observe integration testing while it is in progress.
Inmarsat will also have access to observe over-air integration testing that
will be conducted prior to the formal acceptance testing.

14.                                 All
acceptance test results shall be subject to Inmarsat acceptance in
accordance with the approved test plans and procedures.

 

7.2                                                  Design Proving/Prototype
Testing

 

1.                                       The Contractor shall undertake any necessary design
proving and prototyping of all development areas.

2.                                       Any design proving and prototyping activities shall be highlighted to
Inmarsat by the PDR.

 

A-21

 

3.                                       Results of design proving/prototyping shall be retained and
discussed with Inmarsat at the respective review meetings

 

7.3                               Unit Testing

 

1.                                       The Contractor shall perform unit level hardware and
software testing throughout the development process as required by Contractor
ISO 9001 (or equivalent) process.

2.                                       Evidence of hardware testing shall be made available to Inmarsat, on
request.

3.                                       Evidence of software unit testing shall be made available to
Inmarsat, on request.

 

7.4                               Integration Testing

 

1.                                       The Contractor shall perform integration hardware and
software testing throughout the development process as required by Contractor
ISO 9001 (or equivalent) process.

2.                                       Evidence of hardware and software unit testing shall be made available to
Inmarsat, on request.

 

7.5                               BGAN
Service Demonstration and System Integation

 

1.                                       The Contractor shall submit data regarding simulations
and/or prototype implementations in the Functional Specification Document by
Preliminary Design Review (PDR).

2.                                       The Contractor shall demonstrate to Inmarsat the
establishment of the physical layer communications path using the Reference
Test Bed (RTB) in accordance with the AI before the Final Design Review (FDR)

3.                                       The Contractor shall demonstrate to Inmarsat the
establishment and data transfer through the packet data communication path
using the RTB, in accordance with the AI, before the Factory Acceptance Test
review (FAT).

4.                                       The Contractor shall demonstrate the interworking of the
RAN with prototype UT and CN equipment via participating in Inmarsat organised
integration test campaigns; requiring the Contractor to perform tests both
in-laboratory and over satellite.

 

7.6                               Factory
and Site Acceptance Testing

 

Acceptance
testing is to be performed to demonstrate compliance with all contract
requirements through a combination of factory, site and end-to-end system
tests, inspections and analyses, provision of unit performance or environmental
test results, and provision of standard product test results or conformance
statements for switching system vendor standard products or other
commercial-off-the-shelf products.

 

Inmarsat
representatives will be involved in witnessing all or some of this testing and
ultimately for approving if the RAN meets the contractual requirements.

 

A-22

 

1.               Configuration and test documentation shall be created such that it
will be possible to re-run previously completed acceptance tests.

2.               Problems noted during acceptance tests shall be classified into one
of three categories.

 

Category 1 : Representing one of the following conditions:

•                                          System crash;

•                                          Loss of critical function, severe performance degradation or
instability of the segment/system inoperable for revenue service;

•                                          Failure to detect, report and/or recover from a failure that renders
any part of the system inoperable for revenue service.

•                                          Greater than 10 minutes unplanned sustained loss of operator
management visibility and control.

Category 2 : representing one of the following conditions:

•                                          The problem relates to a contract requirement and is not critical to
any system function.

•                                          The problem is not directly related to the tests.

•                                          The problem occurs rarely and can quickly be recovered by operator
intervention.

Category 3 : representing one of the following conditions:

•                                          The problem is not reproducible.

•                                          The problem can be fixed without system modification.

•                                          The problem is not related to and does not affect a system
requirement.

•                                          The problem can be resolved by an operational or procedural change
unless the problem relates to a function that is primarily involved with
operational or procedural changes.

•                                          The problem is cosmetic in nature and does not impact functionally.

•                                          The problem is in the test procedure and not in the system under
test.

3.                                       Category 1 problems not corrected shall prevent Inmarsat
acceptance of the equipment or acceptance of the relevant testing phase.

4.                                       Category 2 problems may not prevent Inmarsat acceptance of the
equipment or of the relevant testing phase. The Contractor shall develop a list of
category items. A schedule and priority for fixing category 2 items will
need to be presented to Inmarsat. Any proposed deferral of a category 2 problem
to the warranty period shall require the approval of Inmarsat and
form part of pot delivery testing.

5.                                       Those Category 3 problems pertaining to fitness for purpose
requirements compliance or inaccuracies in delivered operator procedures shall
require correction during the agreed warranty period. The Contractor shall
develop a list of category items. A schedule and priority

 

A-23

 

for
fixing category 3 items during warranty will need to be presented to Inmarsat
and form part of post delivery testing.

6.                                       Each list provided for each problem category is not exhaustive and shall
be finalised in the System Test Plan.

 

7.6.1                     Acceptance Criteria

 

The
Contractor shall agree to the following acceptance criteria being
applied:

 

1.                                       All contractual requirements shall be met.

2.                                       The Contractor shall have conducted the necessary Test
Readiness Review with Inmarsat prior to each acceptance test activity, to
review the status of completed qualification testing (e.g. dry run results).

3.                                       Inmarsat review of the integration tests shall not delay FAT provided
that the Contractor supplies these results in accordance with the agreed
schedule.

4.                                       Completion of FAT with no category 1 problems and agreement on the
list of category 2 problems together with an agreed resolution schedule shall be
a prerequisite to commencement of Site Acceptance Testing (SAT).

5.                                       Completion of SAT with no category 1 problems and agreement on the
list of category 2 and 3 problems together with an agreed resolution
schedule shall be a prerequisite to Final Acceptance.

6.                                       Each test stage shall be dependent on the successful
delivery of the relevant system release, associated operational documents and
installation procedures as defined in the corresponding Acceptance Test Plan.

7.                                       If final acceptance is successful on the condition that any
outstanding problems (category 2 and 3) are to be corrected, then the
Contractor shall perform Post-Delivery Testing to confirm the outstanding
problems are corrected.

8.                                       Inmarsat shall have the right to witness
Post-Delivery Test and/or review the test results.

 

7.6.2                     Factory Acceptance Tests (FAT)

 

1.                                       The Contractor shall produce a FAT Plan outlining the
tests for those requirements to be accepted in the factory.

2.                                       The FAT shall be used to test the interface to the
external systems (eg. UT, CN, BSS, etc.) using simulated interfaces.

3.                                       The FAT plan shall require review and approval by
Inmarsat.

4.                                       The Contractor shall perform the FAT for each set of RAN
equipment.

5.                                       The FAT shall be deemed acceptable if the results
achieved satisfy the agreed acceptance criteria (cf section 7.6.1).

 

A-24

 

6.                                       The FAT shall be performed using representative configurations
sufficient for the test objective.

7.                                       The FAT shall demonstrate compliance with
requirements allocated to this acceptance test phase.

8.                                       The FAT shall include the relevant verification of
the following types of contract requirement, as allocated to this acceptance
test phase:

 

8.1.                              Failure
detection, reporting and recovery requirements.

8.2.                              Performance
requirements.

8.3                                 Stability/soak
test where the RAN equipment is to operate for a period of 48 hours without any
application or processor failures. The Contractor is required to provide
load generation and network simulation capability required to establish the
soak conditions. 

8.4                                 Environmental
testing. Here, test results or commercial-off-the-shelf product specifications shall be
provided to demonstrate compliance with contract environmental requirements.

8.5.                              Congestion
handling requirements;

8.6.                              Redundancy
requirements;

8.7                                 Interface
recovery requirements;

8.8                                 The
Factory acceptance test readiness review shall be conducted with Inmarsat 5 days
prior to commencement of the formal witnessed test.

 

9.                                       The FAT shall be witnessed by Inmarsat
representatives.

10.                                 Inmarsat
shall
nominate one member within the witnessing party to have final responsibility
for determining whether the tested system has completed FAT in accordance with
the criteria defined by this SOW.

11.                                 The
Inmarsat representative shall have the authority to either instruct
that a test be repeated or fail the FAT in the case of excessive failures.

12.                                 The
Contractor shall deliver a Test Report for each FAT to Inmarsat within
three weeks of the completion of the FAT.

 

7.6.3                     Site Acceptance Testing (SAT)

 

Each
SAT will show compliance with those requirements allocated to this test phase.
Each requirement to be demonstrated or tested is to be allocated to one test
phase for acceptance.

 

1.                                       Each SAT shall include relevant verification of:

 

1.1.                              Deliverable equipment quantities including spares.

 

1.2.                              Hardware checkout of the installation;

 

1.3.                              Standalone check-out tests;

 

1.4.                              Connectivity tests with other deliverable equipment at the site.

 

A-25

 

2.                                       The Contractor shall produce each SAT Plan for Inmarsat
review and approval.

3.                                       Inmarsat shall witness each SAT.

4.                                       The Contractor shall produce an SAT Test Report at the end
of each SAT.

5.                                       Each SAT Test Report shall include a Site Transfer Document
outlining all items delivered and installed at the site.

6.                                       Each SAT shall be conducted by the Contractor.

7.                                       The SAT readiness report shall be provided to Inmarsat at least 5
days prior to the formal witnessing of the tests.

8.                                       Each SAT shall be witnessed by Inmarsat
representatives.

9.                                       Inmarsat shall nominate one member within the
witnessing party to have final responsibility for determining whether the
tested system has completed SAT in accordance with the criteria defined by this
SOW.

10.                                 The
Inmarsat representative shall have the authority to either instruct
that a test be repeated or fail the SAT in the case of excessive failures.

11.                                 The
SAT shall
be deemed acceptable if the results satisfy the agreed acceptance criteria (cf
section 7.6.1).

 

8.              DELIVERY and INSTALLATION

 

8.1                               RAN Site Surveys

 

1.                                       The Contractor shall conduct a survey of the RAN sites
where the equipment is to be installed.

2.                                       The Contractor shall produce Site Survey Report for each
visit within two weeks of the site visit.

3.                                       Each Site Survey Report shall identify important installation
issues (for which the Contractor is responsible) including, but not limited to:

 

3.1                                 Installation
Plan (i.e. dates and duration);

3.2                                 Need
for co-operation of site staff during installation;

3.3                                 Identification
of on-site test equipment required and/or available;

3.4                                 Impact
on other systems at same site (if applicable).

 

4.                                       The Contractor shall produce a Site Installation Document
(SID).

5.                                       The SID shall be submitted to Inmarsat at least two
weeks before start of any equipment installation.

6.                                       The SID shall identify important installation
issues (for which the Contractor is responsible) including, but not limited to,
the following:

 

6.1                                 Physical
layout and sizing of equipment;

6.2                                 Racking;

6.3                                 Power
requirements;

 

A-26

 

6.4                                 Cooling
requirements;

6.5                                 Communications
interfaces;

6.6                                 Cabling
and connector types;

 

7.                                       Each Site Survey Report and Site Installation Document shall
be approved and signed-off by the Contractor, the Site Contractor and Inmarsat.

 

8.2                               Equipment Delivery
Preparation

 

3.                                       The Contractor shall prepare a Shipment Plan for each
separate shipment of the RAN site equipment.

4.                                       Each Shipment Plan shall be submitted for Inmarsat approval 4
weeks prior to the proposed date for commencing delivery.

5.                                       No equipment shall be shipped unless the Contractor has
received prior Inmarsat approval of the associated Shipment Plan.  Inmarsat will approve the Plan within 10
working days of submission by the Contractor

6.                                       Written notice of shipment shall be given to Inmarsat at least 15
working days prior to shipment of the equipment, indicating port of arrival and
other necessary details.

7.                                       If the site is not owned or operated by Inmarsat, the Contractor shall
also give the same notice to the identified Site Operator .

8.                                       Customs clearance shall be the responsibility of the
Contractor.

9.                                       Inmarsat shall only accept delivery of the equipment
after receipt of the associated Equipment Transfer Documentation.

 

8.3                               Equipment
Transportation and Shipment

 

10.                                 The Contractor shall be responsible for the safe
transportation and delivery of all equipment, materials, tools, etc., to each
designated site.

11.                                 All transported equipment shall be suitably protected to ensure safe
delivery to site.

12.                                 The Contractor shall submit plans for Inmarsat’s
notification that provides the following information for Contractor
transportation obligations:

 

3.1                                 Equipment
being transported;

3.2                                 Transportation
company name;

3.3                                 Mode
of transportation (road, air, sea, etc.);

3.4                                 Level
of packaging protection;

3.5                                 Transportation
timetable.

3.6                                 Incoterms
proposed to be used for shipment.

 

8.4                               Site Installation and
Integration

 

13.                                 Installation of RAN equipment and integration with all the
associated communications links to the rest of the network shall be the Contractor’s
responsibility.

 

A-27

 

14.                                 The Contractor shall provide the necessary personnel and
all relevant installation procedures, instructions, drawings, etc., as required
to achieve the overall technical and operational performance requirements
according to schedule.

15.                                 Inmarsat shall have the right to monitor the work of
the Contractor on site, or to appoint third parties to do so.

 

9.                                      TRAINING

 

The
Contractor is required to provide suitable awareness and operational training
to Inmarsat (encompassing the RAN site operator) prior to service launch. The
training will be centred on the system architecture, operational
responsibilities, problem handling and overall network/resource procedures.

 

1.                                       The Contractor shall train Inmarsat HQ and site staff in
the administration, configuration and operation of all RAN equipment.

2.                                       This training shall take the form of the following course
types:

 

2.1                                 Operator Training Course: Designed to
address the operation, administration and maintenance procedures to be
undertaken at the site – see Section 9.2.

2.2                                 Engineering Course: Designed to
communicate the architectural and engineering aspects behind each major SAS
sub-system – see Section 9.3.

 

9.1                               General Requirements

 

16.                                 The
operational training shall be to a level that will enable
relevant operators to carry out scheduled preventative / restoration /
contingency maintenance and front-line tasks.

17.                                 The
Contractor shall develop suitable documentation and presentational
material needed for all training (i.e. training manual as opposed to basic
slide presentations).

18.                                 Inmarsat
shall
review and approve the training course structure before each course is held.

19.                                 The
location of training shall be:

 

4.1                                 Operator
Training: At the SAS site and repeated at Inmarsat Headquarters, London, as
long as no equipment beyond the agreed contractual deliverable equipment is
required for this course.

4.2                                 Engineering
Course: At the Inmarsat Headquarters in London, as long as no equipment beyond
the agreed contractual deliverable equipment is required for this course.

 

5.                                       The Contractor shall agree to undertake repeat courses, as
instructed by Inmarsat during the warranty period as defined by the contract.

 

A-28

 

6.                                       Inmarsat shall be granted permission by the
Contractor to copy, video, re-produce and/or reuse training material, as
required provided that they are for Inmarsat purposes.

7.                                       Each course shall be suitably structured to allow
(self) refresher training to be undertaken on a unit-by-unit basis.

 

9.2                               Operator Training Requirements

 

This course will cover the
operation of the RAN equipment but will need to be provided to both the site
and Inmarsat HQ staff. In the case of the Inmarsat HQ staff, training is
required to exercise all remote operations functions.

 

1.                                       The Contractor shall provide both presentational and
‘hands-on’ training for site operations staff.

2.                                       This training shall address:

 

2.1                                 Capabilities
and configuration of each sub-system and network elements;

2.2                                 OAM
capabilities of each sub-system;

2.3                                 Routine
operational and maintenance procedures;

2.4                                 Contractor
maintenance support including hardware / software / firmware updates;

2.5                                 Application
of the operational documentation;

2.6                                 Rehearsal
of critical operational procedures including contingency procedures;

2.7                                 Maintenance/support
procedures;

 

3.                                       This training shall suitably reference the relevant
operator manuals, guides and handbooks provided.

4.                                       The training shall be suitably structured such that
staff who attend are thereafter capable of dealing with day-to-day operation
and maintenance of the equipment.

5.                                       Each course shall support up to 10 attendees with a
minimum of 4.

6.                                       The Contractor shall be responsible for providing and
shipping all items needed for the course.

7.                                       The course should include a hands-on and theoretical
test to be taken by each attendee.

8.                                       Two training courses of this type shall be provided.

9.                                       One course shall be held prior to the commencement of
the SAT.

10.                                 The
minimum duration of this course shall be five days.

 

9.3                               Engineering Training
Requirements

 

1.                                       The Contractor shall provide presentational training for
Inmarsat engineering staff.

2.                                       This training shall address:

 

A-29

 

2.1                                 Overall
RAN architecture;

2.2                                 Detailed
design of each sub-system;

2.3                                 Detailed
configuration capabilities of each sub-system;

2.4                                 Detailed
understanding of sub-system fault and error codes;

2.5                                 Application
of the engineering and reference documentation;

2.6                                 Detailed
understanding of the air interface protocols and their operation.

2.7                                 Detailed
understanding of the network switching protocols and their operation.

 

3.                                       The training shall be suitably structured such that
engineering staff who attend are thereafter capable of providing on-call
engineering support to operations to deal with abnormal conditions.

4.                                       The course shall support up to 10 attendees with a
minimum of 4.

5.                                       The Contractor shall be responsible for providing and
shipping all items needed for the course.

6.                                       One training course of this type shall be provided.

7.                                       The minimum duration of this course shall be four days.

 

10.                               WARRANTY and MAINTENANCE

 

The
Contractor is required to provide warranty and support for the delivered
RAN.  The Contractor shall
provide additional maintenance after warranty subject to an annual renewable
maintenance contract being authorised and for a period of up to five years
following the warranty period.

 

10.1                        General Requirements

 

20.         Warranty
and maintenance arrangements to be put in place by the Contractor shall be
sufficient to meet and maintain the RAN contract availability requirement.

 

21.         The
Contractor shall provide a minimum of two years of warranty and support
from Final Acceptance on all hardware, firmware, software and documentation
delivered for the RAN.

 

22.         The Contractor
shall commit
to being prepared to continue to support the RAN for a minimum period of eight
(8) years following warranty completion.

 

23.         The
Contractor shall produce a Sparing Plan identifying sparing, spare part
renewal rates and on-site support policies.

 

24.         The Contractor shall highlight in the Warranty and
Maintenance Plan any third party manufacturer contracts that are advised with
third party hardware and/or software.

 

25.         The Contractor shall ensure that Inmarsat can enter into
such third party contracts should Inmarsat decide to do so.

 

A-30

 

26.         The Contractor shall produce a Warranty and Maintenance
Plan to take effect from the commencement of warranty covering the delivered
equipment and identifying the procedures to be followed in the event of
equipment/system problems.

 

10.2                        Warranty and Support
Requirements

 

27.         The
Contractor shall provide two-year warranty and support on all hardware,
software, firmware and documentation supplied under this contract.

 

28.         The
warranty period shall commence following Final Acceptance .

 

29.         Defects
discovered during the warranty period shall be corrected promptly by the
Contractor at no cost to Inmarsat, except that Inmarsat will be responsible for
shipment of goods to the factory if required.

 

30.         An
annual review of system performance shall be performed with the Contractor
during the warranty period.

 

31.         Each
Warranty Review shall assess the equipment delivered with respect to the
number and types of problems reported, problem completion times and adherence
to contractual conditions.

 

32.         The second review shall also be used by Inmarsat to decide
whether to proceed into an annually renewable maintenance contract with the
Contractor.

 

33.         The Contractor shall perform enhancements to the RAN
during the warranty period, if requested to do so by Inmarsat and in accordance
with the agreed upon change procedure.

 

10.3                        Support during Warranty and Maintenance

 

10.3.1                                      Provisioning of Spares

 

34.         The Contractor shall produce an equipment sparing plan
bearing in mind the:

1.1                                 System
availability requirements;

1.2                                 Need
to achieve the availability requirements for a minimum period of two years from
service launch.

1.3                                 System
mean time to repair targets (namely four hours). This dictates what types of
spares need to be stored at the site (i.e. due to long lead times) or that can
be procured as and when needed.

35.         The Contractor shall undertake to finalise the Sparing
List by the Final Design Review (see Section 4.2.2), clearly identifying
those items which are not COTS equipment.

36.         The Contractor shall provide suitable spares for the RAN
equipment as determined to be necessary to met the system availability
requirements and as indicated in the sparing plan.

 

A-31

 

37.         Spares not deliverable within one week at the site shall
be identified by no later than the Final Design Review.

38.         The Contractor shall be responsible for ensuring that
suitable spares are available for the duration of the warranty and maximum
maintenance period. In the case of obsolete items then suitable replacements
may be used.

 

10.3.2                                      Warranty and Maintenance
Plan

 

39.         The Warranty and Maintenance Plan shall outline the support
proposed during both the warranty and maintenance periods.

 

40.         The Warranty and Maintenance Plan shall outline the procedures
to be developed, particularly in respect to the handling of problems and
Inmarsat specific requirements.

 

41.         The Contractor shall guarantee spares will be available
for a minimum period of ten (10) years from Final Acceptance (with the
exception of third party COTS products) and switching system products –
Inmarsat will be given notice for last time buy within six months notice.

 

42.         The Warranty and Maintenance Plan shall indicate

 

4.1                      The number of personnel required;

 

4.2                      The job functions provided;

 

4.3                      The percentage time dedicated to maintenance per team member;

 

4.4                      Training approach that is to be implemented to ensure trouble-free
continuity of expert support.

 

4.5                      Provision for direct operational support in the event of emergency;

 

4.6                      Hardware repair facilities to be provided;

 

4.7                      Software repair facilities to be provided;

 

4.8                      The use of the RTB facility to support the warranty and maintenance.

 

5.               Not more than 30 elapsed days should be allowed for a hardware repair or
replacement that is returned to the manufacturer/vendor.

 

6.               Priority 1 (P1) problems (see Section 10.4.1)  shall receive immediate attention and
pre-empt other activities, with a goal to repair all such problems within two
working days from the time of the problem being reported.

 

7.               The Warranty and Maintenance Plan shall explain how problems
that arise during warranty will be handled.

 

43.         The Contractor shall define an escalation procedure for
problems not corrected within a stated time.

 

9.               The Warranty and Maintenance Plan shall specify the time to
visit RAN site during the warranty in the event that a problem requires on-site
attention.

 

A-32

 

8.6                               Warranty and Maintenance
Procedures

 

1.                                       The Contractor shall establish and maintain suitable
maintenance procedures, effective throughout the warranty and subsequent
maintenance periods.

2.                                       The maintenance procedures shall take into account the level of
service criteria defined in this sub-section.

 

10.4.1                                      Warranty and Maintenance
Support And Fault Reporting

 

Problems
encountered in the RAN shall be classified into either:

 

1.1.                              Priority
1 Problems (P1)

Whereby the
RAN is suffering from a reduction in capacity, reliability or service quality.

 

1.2.                              Priority
2 Problems (P2)

These are
non-critical problems that do not fall into the P1 category. In this situation,
no traffic is lost.

 

10.5                        Telephone On-Call
Technical Warranty and Maintenance Support

 

1.                                       The Contractor shall provide on-call technical and
operational support.

2.                                       This on-call support shall include:

 

2.1.                              Diagnostic assistance;

2.2.                              Clarification of alarms and advice on hardware and system
management;

2.3.                              Assistance with the interpretation of hardware and system problems;

2.4.                              Technical advice;

2.5.                              Status reporting on outstanding problems;

2.6.                              Progress reporting on P1 problems not resolved within two working
days of notification;

 

3.                                       Immediate telephone warranty and maintenance support and Contractor
remote site access shall be available during normal working
hours (defined as 08:30am to 05:00pm local Contractor time Monday to Friday,
except public holidays).

4.                                       Telephone contact shall be available outside normal working
hours (i.e. evenings, weekends and holidays) to a support engineer (i.e.
reachable via a mobile telephone, etc.).

5.                                       In the case of out-of-hours support then access via a remote dial-up
line shall
be available within one-hour of contact being made.

6.                                       Detailed call handling procedures shall be provided to the SAS
site operators and maintained as necessary by the Contractor.

 

10.6.                     Fault Reporting

 

1.                                       Contact should be made with the Contractor Customer
Support Office (CSO) via a written RAN Query (RANQ).

 

A-33

 

2.                                       For P1 problems then telephone support shall be available as defined
in Section 10.5.

3.                                       P1 problems should be reported via a RANQ to the CSO,
in addition to the on-line telephone support.

4.                                       In case of a software problem then a Software Fault Report (SFR)
number should
be assigned by the CSO.

5.                                       The RANQ should contain the following information:

5.1.                              Site code;

5.2.                              Contact name;

5.3.                              Contact telephone and facsimile number;

5.4.                              Type of fault (hardware, software or other);

5.5.                              Brief description of the fault or problem;

6.                                       In the event of a hardware failure then the following additional
information should be provided on a Hardware Fault Report (HFR):

6.1.                              Part number of the faulty equipment;

6.2.                              Serial number of the faulty equipment;

6.3.                              Description of the faulty equipment;

7.                                       A complete account of the fault should be faxed on a System Problem Report
(SPR) form to the Contractor’s Maintenance Support Function.

8.                                       In the event of a hardware fault then the faulty hardware item should be
returned to the Contractor nominated repair facility.

 

10.7.                     On-site Attendance

 

1.                                       In the event that a Contractor engineer is required to visit an RAN
site during warranty/maintenance then a mutually agreeable time notification
period shall
be agreed.

2.                                       On-site attendance shall be required in cases of emergency and
when the site operator staff has not been able to resolve the problem using the
Contractor supplied procedures.

3.                                       Inmarsat and the Contractor shall agree the necessity of an on-site
attendance on a case-by-case basis.

 

10.8.                     Problem Resolution

 

10.8.1                                      P1 Resolution

 

1.                                       A qualified response shall be supplied by telephone to the
relevant RAN site operator within thirty (30) minutes of the initial call being
placed at the CSO.

2.                                       For each P1 problem, the Contractor shall provide a work-around
solution to restore site availability.

3.                                       System availability shall be restored in the shortest possible
time and full service restored no later than twenty-four (24) hours from the
reported incident. The one exception to this is for third party software
problems that are outside of the control of the Contractor.

 

A-34

 

4.                                       For each P1 problem then the Contractor shall conduct an investigation
to determine the cause of the problem.

5.                                       The results of this investigation shall be provided as soon as
possible and not later then at the end of the next working day from the initial
notification.

6.                                       For P1 software problems in Contractor-developed software then the
Contractor shall provide a “patch” within two (2) working days of the
initial notification. A “patch” is an interim software fix that does not go
through a complete coding and regression testing cycle.

7.                                       Each patch shall be subject to Inmarsat review before
release. Inmarsat will identity an accessible after-hours contact for this
purpose.

8.                                       The “patch” should be such that effort is required from
the site operator during the loading process is minimised (i.e. patch
downloading and initialisation is automated).

9.                                       The Contractor shall supply a formal software release
containing the formal resolution of the P1 problem in Contractor-developed
software within three (3) months of the notification.

 

10.8.2                                      P2 Resolution

 

1.                                       Unless otherwise agreed, these problems in Contractor-developed
software shall
be fixed within the next routine software maintenance release.

2.                                       “Patch” solutions shall only be delivered ahead of the next
formal release if expressly agreed with Inmarsat.

 

10.8.3                                      Regression Testing

 

1.                                       A regression test procedure shall be exercised by the Contractor for
each new software release.

 

10.9.                     Status Reporting

 

1.                                       Closure of problem reports shall require an examination of the
symptoms to determine if the fault is hardware or software related or both.

2.                                       The closure report shall detail the cause(s) of the problem,
affected software subsystems, proposed solution and resolution schedule.

3.                                       The test procedures and implementation strategy for each resolution shall
be evaluated and agreed in co-operation with Inmarsat.

4.                                       The Contractor shall hold a monthly maintenance review to
monitor and report progress being made on reported problems and against
resolutions. Inmarsat reserve the right to participate in a review meeting, as
felt necessary.

5.                                       The Contractor shall provide a monthly maintenance report
to Inmarsat reporting the status of all outstanding reported problems.

6.                                       The monthly report shall include a characterisation of the
particular status of each outstanding P1 problem as well as a detailed problem
resolution plan.

 

A-35

 

10.10                 Warranty
and Maintenance Change Control

 

10.10.1       Document Updates

 

This sub-section concerns the
co-ordination of document changes to hardware and system manuals to ensure that
they remain in line with the versions implemented in the field.

1.                                       Revisions shall be applied, as required, to the
following documents before a software or hardware release is installed:

1.1.                              Operators manuals;

1.2.                              Procedures manuals;

1.3.                              Maintenance Manuals;

2.                                       The Contractor shall provide a list of outstanding
reported system problems with each release.

3.                                       This list should be supplied in a Problem Status
Notice (PSN) to the SAS site every 3 months or when a software/hardware upgrade
occurs

4.                                       The PSN should include:

4.1.                              A procedure for avoiding or coping with the problem;

4.2.                              A forecast of the release number and date when the solution is
expected.

 

10.10.2.                            Software and Hardware Updates

 

1.                                       Each software and hardware update should be accompanied by a
Release Bulletin (RB).

2.                                       Each RB should divide into:

2.1.                              A Problem Status Notice (PSN);

2.2.                              Update Status Bulletin (USB) that includes:

2.2.1.                     Identification of changes included in the release;

2.2.2.                     Identification of known problems that are thereby resolved;

2.2.3.                     Instructions on how the release is to be installed and integrated;

2.2.4.                     Documentation replacement pages, as required;

2.2.5.                     Tests to be completed by the site staff;

2.2.6.                     Details on the factory system configuration that the release was
tested against.

 

10.10.3                               Consolidated Software Releases

 

1.                                       The Contractor shall undertake to provide periodic
consolidated software releases for Contractor-developed software.

2.                                       There shall be at least one consolidation release per annum. This
excludes any releases delivered to rectify problems.

 

A-36

 

10.10.3.1.
Requirements of Software Releases

 

1.                                       It shall be possible to introduce a consolidated software release
during a SAS maintenance window. Redundant equipment within the delivered SAS
is to be employed to eliminate or minimise downtime.

2.                                       Each consolidated software release shall be compatible with the
existing software and operating system environment.

3.                                       Inmarsat shall retain the right to witness any
software consolidation compatibility test before it is transferred to the
target site.

 

10.10.3.2.
System and Configuration Build

 

1.                                       The Contractor shall maintain a system test environment
(referred to as the SAS Reference Test bed) suitably representative of the
configuration used at the operational SAS (see Section 13).

2.                                       The Contractor shall ensure that the test equipment, test
software and databases are configured to be representative of the site
installation.

 

10.11                 Release Control

 

1.                                       The Contractor should coherently group software changes
into staged, planned releases.

2.                                       Release control shall ensure that Contractor software
released from the development environment is adequately specified in terms of
documentation, testing and quality.

3.                                       The release control procedure used by the Contractor shall address:

3.1.                              Configuration
management: Management of the resources used to
control acceptance of new/changed software into the application libraries. Such
configuration management needs to permit regression back to any previous build
release. It should be possible to determine the modification state of a
particular software component in any new release. This principle similarly
applies to hardware changes.

3.2.                              Document
Management: Generation of release notes and
document updates for the configuration controlled items.

3.3.                              Testing: Ensuring that new/changed functions are individually tested then
regression tested within the complete release using a representative test
environment.

3.4.                              Production: Generation of release media or hardware components for site
installation.

3.5.                              Installation
instructions: Producing appropriate and documented
installation guidelines to the host sites which will, in case of unforeseen
problems, allow the staff, in a reasonable time scale, to regress to the
previous release.

3.6.                              Certification: Ensuring that the site configurations are compatible with the new
software or hardware release, in terms of

 

A-37

 

configuration
item compatibility and operating system parameters.

4.                                       The type of a release shall be mutually agreed between the
Contractor and nominated Inmarsat representative(s).

5.                                       The type of release shall be categorised as:

5.1.                              Routine: Where installation procedures are provided with the release. In
this event, each release represents a localised, low risk change rectifying a
well defined problem.

5.2.                              With
telephone assistance: Where the problem(s) is well
defined but configuration at the factory cannot ensure complete confidence in
the reliability of the release when transferred into the target operating
environment. This assistance is extended to all P1 fixes.

5.3.                              With
on-site assistance: This will not routinely be
necessary for problem resolution, but will be provided when both the Contractor
and Inmarsat agrees that on-site support is required

6.                                       Before any software release then the Contractor shall have completed all
required testing of the software.

7.                                       Release testing shall include one or more of:

7.1.                              Baseline unit tests;

7.2.                              Specific tests for the individual changes;

7.3.                              Regression testing;

8.                                       Master archives of the software, documentation and the release notes
shall
be maintained and updated at the Contractor’s maintenance facility.

 

10.12.              Support Activities

 

10.12.1                               Field Activity

1.                                       A representative(s) from the Contractor Maintenance team shall visit
the SAS once a year (during the warranty period) to review the operation and
the service provided.

2.                                       Outstanding site problems shall be investigated during these visits.

3.                                       During these visits then operational procedure updates, the use of
software routines and any further utilities shall be demonstrated to site
operator staff.

4.                                       Inmarsat shall be provided with an agenda for this
visit, two weeks before the actual visit date.

 

11.                               DELIVERABLE DOCUMENTATION

1.                                       The Contractor shall deliver to Inmarsat all programme
management documentation listed in Table 4, in accordance with the specified
schedule.

2.                                       The Contractor shall deliver to Inmarsat all technical
documentation listed in Table 5, in accordance with the specified schedule.

 

A-38

 

3.                                       The Contractor shall  establish
a secure communications link to Inmarsat for the electronic exchange of documents
and e-mail.

4.                                       Delivery of documentation (draft versions) shall comprise:

4.1.                              At least two hard copies of each report;

4.2.                              An electronic version of each file, delivered via e-mail, floppy or
CD ROM, as appropriate.

5.                                       Delivery of documentation (final versions) shall comprise:

5.1.                              At least four hard copies of each report;

5.2.                              An electronic version of each file, delivered via e-mail, floppy or
CD ROM, as appropriate.

6.                                       Unless otherwise agreed, all documentation shall be delivered to
Inmarsat, London.

7.                                       At the end of the project, the Contractor shall prepare and deliver a
CD ROM containing the final version of each deliverable document.

8.                                       All deliverable documents shall be written in English.

9.                                       The Contractor shall agree in advance with Inmarsat the word
processing package to be used (i.e. Microsoft Word).

10.                                 All documentation should be delivered in a browser viewable
format (i.e. PDF or HTML).

11.                                 The documentation standard and control procedure shall be
referenced in the QAP and approved by Inmarsat before use.

12.                                 All documentation in Tables 4, 5 shall be retained under
formal document configuration control.

 

A-39

 

	
  No

  	
   

  	
  Contractor

  Document

  	
   

  	
  Comments

  	
   

  	
  Delivery
  Schedule

  
	
  Draft
  1

  	
   

  	
  Draft
  2

  	
   

  	
  Final

  
	
  1.

  	
   

  	
  Programme
  Management Plan (PMP)

  	
   

  	
  Incorporates
  Overall Project Schedule (may be separated for each development)

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  2.

  	
   

  	
  Risk
  Management Plan (RMP)

  	
   

  	
  Incorporates
  overall risk management procedures (may be separated for each development)

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  3.

  	
   

  	
  Configuration
  Management Plan (CMP)

  	
   

  	
  Incorporates
  the overall configuration control procedures (may be separated for each
  development).

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  4.

  	
   

  	
  Quality
  Assurance Plan (QAP)

  	
   

  	
  Incorporates
  the overall quality assurance procedures (may be separated for each
  development). Contains process descriptions of the Hardware Development Plan
  and Software Development Plan

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  5.

  	
   

  	
  Training
  Plan

  	
   

  	
  Covers both
  engineering and operational training (may be separated for each development).

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  6.

  	
   

  	
  Warranty and
  Maintenance Plan

  	
   

  	
  Maintenance
  plan for the equipment and network

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  7.

  	
   

  	
  Monthly
  Progress Report

  	
   

  	
  Statement of
  project progress.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  8

  	
   

  	
  Milestone
  Review Meeting Minutes

  	
   

  	
  Records the
  points raised at the review meeting

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  9.

  	
   

  	
  System Test
  Plan

  	
   

  	
  Details the
  overall test approach for RAN, acceptance test plans and the requirements
  mapping to the acceptance test plans.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  

 

Table 4: Programme
Management Documents

 

A-40

 

	
  No

  	
   

  	
  Contractor

  Document

  	
   

  	
  Comments

  	
   

  	
  Delivery
  Schedule

  
	
  Draft
  1

  	
   

  	
  Draft
  2

  	
   

  	
  Final

  
	
  1.

  	
   

  	
  Functional
  Specification

  	
   

  	
  Functional
  specification

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  2.

  	
   

  	
  Requirements
  Allocation

  	
   

  	
  Allocation
  of requirements to RAN subsystems

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  3.

  	
   

  	
  External
  Interface Control Documents (ICD)

  	
   

  	
  Interface
  definition between the RAN and all other BGAN subsystems

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  4.

  	
   

  	
  Facilities
  Requirement Specification(s)

  	
   

  	
  Outlines the infrastructure required for delivery of
  equipment into the site. Decomposed into:

  

  a) Radio Facilities Requirements

  

  b) Base Station Facilities Requirements

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  5.

  	
   

  	
  Segment
  Design Document

  	
   

  	
  Segment
  design document - decomposition into subsystems, subsystem high level design.
  I

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  6.

  	
   

  	
  MMI Design
  Document

  	
   

  	
  Man-machine
  Interface (MMI) for the RAN operations

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  

 

A-41

 

	
  7.

  	
   

  	
  Operational
  Concepts

  	
   

  	
  Operational
  concepts

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  8

  	
   

  	
  Factory
  Acceptance Test Plan

  	
   

  	
  Factory
  acceptance test plan.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  9.

  	
   

  	
  Site
  Acceptance Test Plan

  	
   

  	
  Site
  acceptance test plan.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  10.

  	
   

  	
  Factory
  Acceptance Test Procedures

  	
   

  	
  Factory
  acceptance test procedures.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  11.

  	
   

  	
  Site
  Acceptance Test Procedures

  	
   

  	
  Site
  acceptance test procedures

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  12.

  	
   

  	
  Operator
  Training Manual

  	
   

  	
  Manual to be
  used for operator training for the delivered equipment.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  13.

  	
   

  	
  FAT
  Configuration Report

  	
   

  	
  FAT
  configuration report

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  14.

  	
   

  	
  SAT
  Configuration Report

  	
   

  	
  SAT
  configuration report

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  15.

  	
   

  	
  FAT
  Readiness Report

  	
   

  	
  SAS FAT
  Readiness Report

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  16.

  	
   

  	
  SAT
  Readiness Report

  	
   

  	
  SAS SAT
  Readiness Report.

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  17.

  	
   

  	
  FAT Test
  Report

  	
   

  	
  Results of
  the FAT testing

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  

 

A-42

 

	
  18.

  	
   

  	
  SAT Test
  Report (including site transfer document)

  	
   

  	
  Results of
  the SAT testing

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  19.

  	
   

  	
  Operations
  Manual(s)

  	
   

  	
  Operating
  and user instructions for the RAN equipment

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  20.

  	
   

  	
  Site Survey
  Report

  	
   

  	
  Results of
  Contractor review of the SAS facility

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  21.

  	
   

  	
  Shipment
  Plan

  	
   

  	
  Details of
  when and how the equipment is to be shipped and accepted at the site

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  22.

  	
   

  	
  Site
  Readiness Review Report

  	
   

  	
  Site
  Readiness Review Report

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  23.

  	
   

  	
  Site
  Installation Document

  	
   

  	
  Installation
  Plan

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  24.

  	
   

  	
  Annual
  Warranty Report

  	
   

  	
  Summary of
  warranty activities and services provided over the last 12 month period

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  
	
  25.

  	
   

  	
  Recommended
  Spares List

  	
   

  	
  Definition
  of the sparing plan proposed for the equipment

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  ****

  

 

Table 5: Deliverable Technical Documentation

 

A-43

 

12.                               APPLICABLE STANDARDS

 

Inmarsat is
responsible for the provisioning of the RAN building site infrastructure and
required facilities such as power and air conditioning.

1.                                       The Contractor shall undertake to deliver at EDC+3 months
a preliminary draft of equipment detail, a second draft at PDR and a final
Facilities Requirement Specification by FDR, outlining all the site
requirements to enable equipment installation.

2.                                       The Facilities Requirement Specification shall include a
schedule of when facilities will be required and when access to the site
is needed.

3.                                       The Facilities Requirement Specification shall address what is
required in terms of:

3.1.                              Power supply;

3.2.                              Environmental conditions (temperature, humidity, etc.);

3.3.                              Floor space;

3.4.                              Security and access control;

3.5.                              Estimated number of operational staff;

3.6.                              Qualifications of operational staff;

3.7.                              Civil engineering (e.g. building, antenna structure and load
bearing, etc.);

3.8.                              Mechanical structures.

 

12.1.                     Site Requirements

 

Selection of
the RAN sites has not yet been made. This selection will be identified by PDR.
The NOC is located at the Inmarsat Headquarters site in London, England.

1.                                       The Contractor shall indicate how national requirements
for site equipment and installation (e.g. cabling, voltages, etc.) is to be met
once the site location has been confirmed by Inmarsat.

2.                                       All equipment (racks, shelves, cards, cables, etc.), shall
be labelled to enable easy identification.

3.                                       Such labelling shall not be of a temporary nature.

4.                                       All labelling shall be written in the English language.

5.                                       The Contractor should enter equipment inventory details in
the Site Configuration Report .

6.                                       Equipment shall be provided with suitable termination
points for all cabling to facilitate installation, interconnection and
subsequent maintenance.

7.                                       Contractor identified cabling required but that which is not part of
the equipment to be installed will  be provided as under floor cabling with
suitable termination points being provided.

8.                                       Wiring and cabling used within the equipment shall be of adequate size and
rating so as to prevent mechanical or electrical damage by any reasonable
factors, including the carrying out of routine maintenance work.

9.                                       The Contractor-supplied commercial off-the-shelf (COTS) equipment shall
have as a minimum the applicable CE mark; all Contractor developed equipment
shall have the CE mark and additionally be compliant to UL and FCC requirements
for that class of equipment. Precautions include:

9.1.                              Induced voltages due to lightning discharge;

9.2.                              AC mains borne interference;

9.3.                              Induced voltages due to adjacent RF equipment.

 

A-44

 

10.                                 The Contractor shall accept responsibility for compliance
with local regulations for suppression of radio interference, and for
elimination of any co-site interference emanating from the Contractor’s
equipment.

11.                                 The Contractor shall provide adequate protection against
any equipment susceptibility to potential electromagnetic contamination.

 

12.2                        Environmental Conditions

 

The equipment shall
meet their technical requirements over the following range of environmental
conditions:

	
  Temperature

  	
   

  	
  10o
  to 35o C ambient

  
	
  Relative
  Humidity

  	
   

  	
  10 to 80%
  bounded by an absolute humidity of 20g/m3 on the high side and
  bounded by 1.5 g/ m3 on the low side

  

 

12.3                        Health and Safety

 

The Contractor
shall deliver
equipment that fully complies with the safety requirements associated with its
CE mark.

 

13.                               TEST FACILITIES

 

13.1.                     Reference Test Bed (RTB)

 

The purpose of
the RTB (maintained at the Contractor facility) is to enable the Contractor to
suitably verify, test and debug the RAN during development. Thereafter, the RTB
will be used for maintenance once in operation and for co-ordinating and
testing upgrades including new software, new enhancements etc and also for
trouble shooting.

1.                                       During the development and test stage the Contractor shall be
responsible for all in-lab equipment required to verify the AI and the RAN.

2.                                       The Contractor shall design, develop and build an
in-factory representative Reference Test Bed (RTB) sufficiently sized (both
hardware and software) to assist with RAN development, system performance/load
testing, AI verification and maintenance investigations.

3.                                       The Contractor shall use the RTB for in-house system
testing, warranty and maintenance support.

4.                                       The Contractor shall support the RTB throughout the
development, testing and warranty period.

5.                                       The Contractor and Inmarsat shall agree upon a delivery mechanism
between the Contractor facility and SAS site for the transfer of software
upgrades, files, etc.

6.                                       The RTB shall be able to connect with the
operational network, when authorised via Inmarsat and on provision of a
suitable communications line.

 

The RTB shall
provide a test harness capability for all external interfaces to the RAN.  The technical requirements for the RTB are
given in the System Requirements Specification (SRS).

 

13.2.                     Transportable Test Tools

 

The
Contractor shall develop and produce two (2) sets of transportable test
tools (TTT).

 

A-45

 

The
purpose of the TTT is to enable the Contractor to test the RAN by emulating all
external interfaces, including the Air Interface, the Core Network Interface,
the Business Support System (BSS) Interface and the Network Management System
Interface.  This tool set shall have
appropriate interfaces at baseband, IF as well as RF, in order to enable
testing the Air Interface at both IF and over-satellite.

The
technical requirements for the TTT are given in the System Requirements
Specification (SRS).

 

14.                               SYSTEM INTEGRATION EFFORT

 

14.1                        BGAN Development
Coordination Forum

 

Inmarsat
will chair a BGAN Development Coordination Forum (DCF) for the coordination of
technical and operational issues related to the BGAN system development.  All contractors and suppliers related to the
BGAN system development are required to participate in these DCF meetings.

The
scope of the SEC meetings is to encompass :

a)              resolution of technical and operational issues related to the
development of the BGAN system

b)             coordination of inter-working and integration testing between
different BGAN subsystems;

c)              identification and resolution of issues related to gaining type
approval and certification of BGAN user terminal equipment for different
markets;

d)             identification and resolution of technical issues related to gaining
licensing and market access for the BGAN system operation and service
provision.

1.               The Contractor shall
participate in the DCF meetings to be established by Inmarsat.

2.               The Contractor shall
participate proactively in identifying and resolving technical and operational
issues related to the development of the BGAN system.

 

14.2                        Access to Reference Test Bed

 

The
Contractor shall make available the Reference Test Bed (RTB) for
interworking and integration tests by other BGAN subsystem suppliers, as
nominated by Inmarsat.  Inmarsat will
ensure that the other BGAN subsystem suppliers provide reasonable notice for
the Contractor to schedule access to the RTB facilities.

 

14.3                        System Integration Support

 

The
Contractor shall support overall system integration testing activity as
directed by Inmarsat.  These tests shall
be conducted after SAT testing for the SAS site.  This excludes all integration and test activities conducted by
the Contractor prior to the SAT milestone, and as such shall be within the
scope of the contracted work.

The
Contractor shall make available skilled personnel capable of supporting
the integration test campaign, for a minimum of 10 man-years at agreed time and
materials charge rates.  The Contractor shall
invoice Inmarsat on a monthly basis in arrears for the actual level of support
provided.  All system integration
activities supported by the Contractor shall require prior approval by the
responsible Inmarsat project manager.

 

A-46

 

	
  Appendix A - Abbreviations

  
	
  ADD

  	
   

  	
  Architectural
  Design Document

  
	
  ADR

  	
   

  	
  Architectural
  Design Review

  
	
  AI

  	
   

  	
  Air
  Interface

  
	
  AOC

  	
   

  	
  Advanced
  Operations Centre

  
	
  API

  	
   

  	
  Applications
  Programming Interface

  
	
  ATR

  	
   

  	
  Alpha Test
  Review

  
	
  BCC

  	
   

  	
  NOC Backup
  Control Centre

  
	
  BGAN

  	
   

  	
  Broadband
  Global Area Network

  
	
  BOC

  	
   

  	
  Business
  Operations Centre

  
	
  BSS

  	
   

  	
  Business
  Support System

  
	
  BTR

  	
   

  	
  Beta Test
  Review

  
	
  CAI

  	
   

  	
  Common Air
  Interface

  
	
  CMP

  	
   

  	
  Configuration
  Management Plan

  
	
  CSO

  	
   

  	
  Customer
  Support Office

  
	
  CU

  	
   

  	
  Communications
  Unit

  
	
  DCN

  	
   

  	
  Data
  Communications Network

  
	
  DR

  	
   

  	
  Development
  Review

  
	
  EDC

  	
   

  	
  Effective
  Date of Contract

  
	
  ESA

  	
   

  	
  European
  Space Agency

  
	
  FAT

  	
   

  	
  Factory
  Acceptance Test

  
	
  FATR

  	
   

  	
  FAT Review

  
	
  FDR

  	
   

  	
  Final Design
  Review

  
	
  FFP

  	
   

  	
  Firm Fixed
  Price

  
	
  FTR

  	
   

  	
  Factory Test
  Review

  
	
  GEO

  	
   

  	
  Geostationary
  Earth Orbit

  
	
  GGSN

  	
   

  	
  Gateway GPRS
  Support Node

  
	
  GPRS

  	
   

  	
  General
  Packet Radio Service

  
	
  GS

  	
   

  	
  Ground
  Station

  
	
  HFR

  	
   

  	
  Hardware
  Fault Report

  
	
  HLR

  	
   

  	
  Home
  Location Register

  
	
  HMP

  	
   

  	
  Hardware Management
  Plan

  
	
  ICD

  	
   

  	
  Interface
  Control Document

  
	
  IF

  	
   

  	
  Intermediate
  Frequency

  
	
  ITP

  	
   

  	
  Integration
  Test Plan

  
	
  KOR

  	
   

  	
  Kick-off
  Review

  
	
  MTBF

  	
   

  	
  Mean Time
  Between Failures

  
	
  MT

  	
   

  	
  Mobile
  Terminal

  
	
  MTTR

  	
   

  	
  Mean Time to
  Repair

  
	
  N/A

  	
   

  	
  Not
  Applicable

  
	
  NE

  	
   

  	
  Network
  Element

  
	
  NOC

  	
   

  	
  Network
  Operations Centre

  
	
  NFO

  	
   

  	
  Network
  Facilities Operator

  
	
  ORR

  	
   

  	
  Operations
  Readiness Review

  
	
  OTR

  	
   

  	
  Operations
  Test Report

  
	
  PBSC

  	
   

  	
  Packet Base
  Station Controller

  
	
  PBTS

  	
   

  	
  Packet Base
  Transceiver Site

  

 

A-47

 

	
  PDD

  	
   

  	
  Prototype
  Design Document

  
	
  PDR

  	
   

  	
  Preliminary
  Design Review

  
	
  PLMN

  	
   

  	
  Plain Land
  Mobile Network

  
	
  PMC

  	
   

  	
  Personal
  Multimedia Communications

  
	
  PMP

  	
   

  	
  Programme
  Management Plan

  
	
  PSN

  	
   

  	
  Problem
  Status Notice

  
	
  QAP

  	
   

  	
  Quality
  Assurance Plan

  
	
  QoS

  	
   

  	
  Quality of
  Service

  
	
  RANQ

  	
   

  	
  RAN Query

  
	
  RF

  	
   

  	
  Radio
  Frequency

  
	
  RFP

  	
   

  	
  Request for
  Proposal

  
	
  RMP

  	
   

  	
  Risk
  Management Plan

  
	
  RID

  	
   

  	
  Review Item
  Discrepancy

  
	
  RN

  	
   

  	
  Release Note

  
	
  RTF

  	
   

  	
  Reference
  Test Facility

  
	
  SAS

  	
   

  	
  Satellite
  Access Station

  
	
  SAT

  	
   

  	
  Site
  Acceptance Test

  
	
  SATR

  	
   

  	
  SAT Review

  
	
  SDD

  	
   

  	
  System Design
  Document

  
	
  SFR

  	
   

  	
  Software
  Fault Report

  
	
  SFS

  	
   

  	
  System
  Functional Specification

  
	
  SGSN

  	
   

  	
  Serving GPRS
  Support Node

  
	
  SID

  	
   

  	
  SAS
  Installation Document

  
	
  SMP

  	
   

  	
  Software
  Management Plan

  
	
  SOT

  	
   

  	
  System
  Operational Testing

  
	
  SOW

  	
   

  	
  Statement of
  Work

  
	
  SPR

  	
   

  	
  System
  Problem Report

  
	
  SP

  	
   

  	
  Service
  Provider

  
	
  STP

  	
   

  	
  System Test
  Plan

  
	
  TBC

  	
   

  	
  To Be
  Confirmed

  
	
  TBD

  	
   

  	
  To Be
  Determined

  
	
  TE

  	
   

  	
  Terminal
  Equipment

  
	
  USB

  	
   

  	
  Universal
  Serial Bus (1)

  
	
  USB

  	
   

  	
  Update
  Status Notice (2)

  
	
  UT

  	
   

  	
  User
  Terminal

  
	
  VLR

  	
   

  	
  Visitor
  Location Register

  
	
  WBS

  	
   

  	
  Work
  Breakdown Structure

  
	
  WPD

  	
   

  	
  Work Package
  Description

  

 

A-48

 

Appendix B

ICD CHANGE CONTROL BOARD

BASIC GUIDELINES

DRAFT

 

1.               Membership of the ICD
CCB shall be open to the suppliers of all major subsystems of the BGAN system.

2.               Inmarsat shall chair
the CCB.  All other members of the CCB
shall have equal status.

3.               The CCB shall be
responsible for maintaining all BGAN Interface Control Documents (ICDs),
including the BGAN Air Interface (AI) definition.

4.               Any member of the CCB
may propose changes to any ICD, with appropriate supporting information and
justification.

5.               The CCB shall decide
whether a given change is substantive or editorial.

6.               Editorial changes shall
be to clarify ambiguities and remove errors in the ICD definition.  Substantive changes shall be to provide
enhanced performance/ functionality in the ICD definition.

7.               All members shall adopt
all editorial changes, without the need for amendment of their respective
development contracts.

8.               All members shall adopt
substantive changes up to their respective contractual PDR milestones, provided
there is no consequential impact on the contracted scope of work, without
amendment of their respective contracts

9.               All members shall adopt
substantive changes up to their respective contractual FDR milestones, provided
there is no consequential impact on the contracted scope of work.

10.         All members shall make best
efforts to adopt substantive changes at any time, in the interest ensuring a
properly functional BGAN system.

11.         Decisions of the CCB shall
generally be taken by consensus.  In
case of lack of consensus, the Chairperson shall decide on the basis of
congruence with Inmarsat BGAN programme goals.

 

A-49

 

ANNEX B

 

 

SYSTEM REQUIREMENTS
SPECIFICATION (SRS)

 

 

[***]

 

 

ANNEX C

 

 

[***]

 

 

 

ANNEX D

 

PRICE
BREAKDOWN AND PAYMENT PLAN

PRICE BREAKDOWN (in US Dollars)

 

A.                                    BREAKDOWN
OF BASELINE PRICES

 

	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
   

  	
   

  	
   

  	
   

  
	
  B.                                    BREAKDOWN OF OPTION PRICES

  	
   

  	
   

  	
   

  
	
   

  	
   

  	
   

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
   

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  
	
  *****

  	
   

  	
  *****

  	
   

  

 

C.                                    VARIABLE PRICES

 

1.                                       Shipping and Travel Costs

Shipping and Travel Costs for the four representative sites (Raisting,
Singapore, Goonhilly and UAE) total $**** and are included in the
FFP.   Following Inmarsat’s final
selection of RAN sites, the prices may be adjusted in accordance with the
actual costs of shipping the RAN equipment to those alternative sites and
Contractor’s actual travel costs.   
Contractor and Inmarsat shall agree on the appropriate Change Notice to
Annex D to the Contract to incorporate the final prices.

 

2.                                       Annual Maintenance Costs

The annual baseline price of $**** shall be adjusted in accordance with
additional Work and/or RAN Equipment that will be added to the baseline by the
time the maintenance period commences, plus the price escalation of TBD% - NTE
5%.  The annual baseline price does not
include maintenance of Contractor’s manufactured equipment.  Inmarsat has the option to have such
hardware maintenance performed for a firm fixed annual price or to have
equipment repaired on a case by case fixed price basis.  Contractor shall provide prices for both
options at least three months prior to expiration of the warranty period.

 

 

A.                                    PAYMENT
PLAN

 

Baseline
Contract

 

The Firm Fixed Price of
**** shall be payable by Inmarsat following Contractor’s completion of the
following contractual milestones:

 

	
  Month

  EDC+

  	
   

  	
  Milestone

  Number

  	
   

  	
  Milestone

  Description

  	
   

  	
  Milestone

  Payment

  in %

  	
   

  	
  Milestone

  Payment in

  USD

  	
   

  
	
  1

  	
   

  	
  1

  	
   

  	
  Kick-Off
  Review

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  6

  	
   

  	
  2

  	
   

  	
  Preliminary
  Design Review

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  12

  	
   

  	
  3

  	
   

  	
  Final Design
  Review

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  13

  	
   

  	
  4

  	
   

  	
  Delivery of
  RFT

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  24

  	
   

  	
  5

  	
   

  	
  Factory
  Acceptance Test

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  27

  	
   

  	
  6

  	
   

  	
  Site 1
  Acceptance

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  30

  	
   

  	
  7

  	
   

  	
  Final
  Acceptance

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  42

  	
   

  	
  8

  	
   

  	
  End of
  Warranty Year 1

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  
	
  54

  	
   

  	
  9

  	
   

  	
  End of
  Warranty Year 2

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  

 

B.                                    PAYMENT
PLAN

 

Options

 

A payment plan for Inmarsat’s options under this Contract shall be
agreed between the parties at the time the options are confirmed and shall be
incorporated in the appropriate amendment(s) to Contact.

 

C.                                    PAYMENT PLAN

 

Maintenance

 

The annual maintenance price for the baseline RAN, following expiration
of the two year Warranty Period is $****.  This price is subject to a yearly increase
based on the annual rate of inflation in Denmark; however, the increase shall
not exceed **** per year.

 

Payment shall be made by Inmarsat in equal quarterly instalments of **** + annual percentage of inflation,
payable at the beginning of each quarter of maintenance.

 

 

ANNEX E

 

 

WARRANTY
AND MAINTENANCE PLAN

 

 

The Contractor’s Final Warranty and Maintenance Plan in conformance with
the requirements of Annex A and B, SOW and SRS, shall be available at
FAT.

 

 

ANNEX F

 

 

CONTRACTOR
KEY PERSONNEL

 

 

	
  Name

  	
   

  	
  Title

  	
   

  	
  %
  on Project

  
	
   

  	
   

  	
   

  	
   

  	
   

  
	
  ****

  	
   

  	
  System Sales Manager

  	
   

  	
  30

  
	
  ****

  	
   

  	
  Systems R&D Manger

  	
   

  	
  75

  
	
  ****

  	
   

  	
  RAN Programme Manager

  	
   

  	
  100

  
	
  ****

  	
   

  	
  System Design/Test and Integration Manager

  	
   

  	
  100

  
	
  ****

  	
   

  	
  Sub-Contractor Manager

  	
   

  	
  100

  
	
  ****

  	
   

  	
  Manager Systems Engineering

  	
   

  	
  100

  
	
  ****

  	
   

  	
  Project Manager, Channel Unit Design

  	
   

  	
  100

  
	
  ****

  	
   

  	
  Project Manager, Host System Design

  	
   

  	
  100

  
	
  ****

  	
   

  	
  SW Team Leader

  	
   

  	
  100

  
	
  ****

  	
   

  	
  HW Team Leader and System Design

  	
   

  	
  100

  
	
  ****

  	
   

  	
  Quality Assurance Manager

  	
   

  	
  25

  
	
  ****

  	
   

  	
  CN Interface / UMTS Expert

  	
   

  	
  100

  
	
  TBD

  	
   

  	
  Mathematician

  	
   

  	
  100

  

 

 

ANNEX G

 

 

KEY
SUBCONTRACTORS

 

 

	
  Company
  Name

  	
   

  	
  Address

  
	
   

  	
   

  	
   

  
	
  SED
  SYSTEMS, INC.

  	
   

  	
  18
  Innovation Boulevard, PO Box 1464

  
	
   

  	
   

  	
  Saskatoon,
  Saskatchewan, Canada S7K 3P7

  
	
   

  	
   

  	
   

  
	
  Key
  Personnel:

  	
   

  	
   

  
	
   

  	
   

  	
   

  
	
  Overall Contract Management:

  	
   

  	
   

  
	
  Brent McConnell

  	
   

  	
  VP, Operations

  
	
  Patrick Thera

  	
   

  	
  Program Manager

  
	
  Gary Beeton

  	
   

  	
  QA Coordinator

  
	
   

  	
   

  	
   

  
	
  GRM:

  	
   

  	
   

  
	
  Dan Baril

  	
   

  	
  Project Manager

  
	
  Mike Gale

  	
   

  	
  Lead Systems Engineer

  
	
  Russ Palmer

  	
   

  	
  Lead Software Engineer

  
	
   

  	
   

  	
   

  
	
  RFS:

  	
   

  	
   

  
	
  Sandra Frattinger

  	
   

  	
  Project Manager

  
	
  Howard Grant

  	
   

  	
  Engineering Consultant

  
	
  Dave Fenske

  	
   

  	
  Lead Systems Engineer

  
	
  Brent Clark

  	
   

  	
  PCE/MCS Lead Software Engineer

  
	
  Ron Nunweiler

  	
   

  	
  Installation Supervisor

  
	
   

  	
   

  	
   

  
	
  LOGICA UK LIMITED

  	
   

  	
  75 Hampstead Road

  
	
   

  	
   

  	
  London
  NW1 2PL, England

  
	
   

  	
   

  	
   

  
	
  Key
  Personnel:

  	
   

  	
   

  
	
  Steve Smart

  	
   

  	
  Business Manager

  
	
  Hugh Deighton

  	
   

  	
  RAN Project Manager

  
	
  Lawrie Vince

  	
   

  	
  Quality Support

  
	
  Michael Carrigan

  	
   

  	
  Technical Consultant

  
	
  Nick Green

  	
   

  	
  System Architect

  
	
  Martin Potter

  	
   

  	
  Development Manager

  
	
  Keith Smith

  	
   

  	
  Test & Integration Manager

  
	
   

  	
   

  	
   

  
	
  WIRELESS
  INTELLIGENT SYSTEMS, LTD.

  	
   

  	
  Baltic
  Street West

  
	
   

  	
   

  	
  London ,
  England

  
	
   

  	
   

  	
   

  
	
  Key
  Personnel:

  	
   

  	
   

  
	
  Panagiotis Fines

  	
   

  	
  Project Management

  
	
  Katerina Christofylaki

  	
   

  	
  Contracts Manager

  
	
  Fatin Said

  	
   

  	
  Technical Consultant, Turbo Coding

  
	
  Mike Lind Rank

  	
   

  	
  DSP Engineer

  
	
  Soren Kilsgaard

  	
   

  	
  Digital HQ Design and Implementation

  
	
  Michael Dohler

  	
   

  	
  Channel Modelling and Testing

  

 

 

ANNEX H

 

 

CONTRACTOR
BACKGROUND DISCLOSURE

 

Contractor
identifies the following Background in respect of Article 11 hereto:

 

A.                                    THRANE & THRANE BACKGROUND

 

•                  Channel Unit Operating System

•                  Alarm and Event System

•                  Host Control System (SCS)
(Star-up, Close-down and Switch-over functions)

•                  Rack Design

•                  Sub-rack Design

 

B.                                    LOGICA BACKGROUND

 

•                  LD-TeleCUSP-SCCPPR-0014 (Telecusp
CCP Provider Low Level Design Specification), Version 1.1 dated 16
November 1999.

 

C.                                    SED SYSTEMS BACKGROUND

 

•                  M&C Software

•                  Geographical Positioning Software

•                  GRM Framework Software

 

•                  Third Party Background

•                  Vertex/RSI Antenna Design

 

 

	
  

  	
  Contract
  Change Notice

  

 

	
  PROJECT  

  	
  Inmarsat B-GAN RAN

  	
   

  	
  CCN NO. 011

  	
   

  	
  DATE

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  CONTRACT  

  	
  INM-CO/01-2876/HC

  	
   

  	
   

  	
   

  	
  20 January 2003

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  (1) TITLE OF CHANGE

  	
  Updates to Contract Terms and Conditions

  	
   

  	
   

  	
   

  
	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Under this CN011, the parties amend certain contract terms and
  conditions as described in the attachment hereto.  Specifically, the CN encompasses the change from a one phase
  delivery of the RAN to a two phase delivery, changes in the payment milestone
  to include the additional 120 Man Months of effort incurred by Contractor in
  connection with delivery schedule of the SDM, and addition of Appendix I
  to Annex A of the Contract entitled Statement of Work which describes in more
  detail the RAN on the Bench deliverable to Inmarsat.

  	
   

  	
  (3) RECOMMENDED INTRODUCTION POINT 20/12/2002

  
	
   

  	
   

  	
  (4) DRAWINGS AND SPECS. AFFECTED

  
	
   

  	
   

  	
   

  
	
  (7) REASON FOR CHANGE

  	
  Updating Contract

  	
   

  	
   

  
	
   

  	
   

  	
   

  	
   

  
	
  (8) RELATED FACTORS

  	
   

  	
   

  
	
   

  	
   

  	
   

  
	
  FACTOR

  	
  Y

  	
  N

  	
  FACTOR

  	
  Y

  	
  N

  	
  FACTOR

  	
  Y

  	
  N

  
	
  Performance

  	
   

  	
   

  	
  Testing

  	
   

  	
   

  	
  Other factors

  	
   

  	
   

  
	
  Reliability

  	
   

  	
   

  	
  Materials and processes

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Interface

  	
   

  	
   

  	
  Spare parts

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Weight

  	
   

  	
   

  	
  Agency furnished equipment

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Dimensions

  	
   

  	
   

  	
  Packaging

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Electrical parameters

  	
   

  	
   

  	
  Publications

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  (9) ESTIMATED INFLUENCES ON CONTRACT
  PROVISIONS

  	
   

  	
   

  
	
   

  	
   

  	
   

  
	
  1. TOTAL PRICE INFLUENCE

  	
   

  	
   

  
	
   

  	
   

  	
   

  
	
  TOTAL HOURS

  	
  LABOUR COSTS

  	
  MATERIALS

  	
  TAXES

  	
  OTHER COSTS

  	
  TOTAL COSTS

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  Not specified

  	
  Not specified

  	
  Not specified

  	
  Not included

  	
   

  	
  USD ****

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  2. SCHEDULE INFLUENCE None

  	
   

  	
   

  
	
   

  	
   

  	
   

  
	
  CONTRACTOR’S SIGNATURES

  	
   

  	
  INITIATOR

  Both Parties

  DATE:  20-01-032

  
	
  PROJECT MANAGER

  	
   

  	
   

  
	
  ****

  	
  DATE: DD-MM-YY

  	
   

  
	
  CONTRACT MANAGER

  	
   

  	
   

  
	
  ****

  	
  DATE:  DD-MM-YY

  	
   

  
																					

 

	
  Confidential
  & Proprietary

  	
   

  

 

 

	
  DATE OF REJECTION

  	
   

  	
  DATE OF APPROVAL

  	
   

  	
  INTRODUCTION POINT

  
	
  CUSTOMER’S SIGNATURES

  	
   

  	
   

  
	
  PROGRAMME MANAGER

  	
   

  	
   

  	
  DATE:

  
	
  CONTRACTS MANAGER

  	
   

  	
   

  	
  DATE:

  
						

 

 

Article 1                                               Scope of Work

 

The scope of work current as of December 2002, is reflected in the
Statement of Work Issue 2.1 and the updated System
Requirements Specification Issue 3.1.

 

Article 2                                               Delivery by
Contractor

 

Paragraph B of Article 2 is hereby amended to read as follows:

 

The Radio Network Sub-system (RFS) delivery locations shall be Burum in
the Netherlands and Fucino in Italy. 
All deliverable items shall be delivered in accordance with
Article 3 hereto, entitled Performance Schedule, in accordance with the
Statement of Work and SRS Volume 3.1.

 

A new Paragraph C is added as follows:

 

The RAN on the Bench (ROB) which is developed by Contractor concurrently
with the Reference Test Bed (RTB) but shall be delivered to Inmarsat, shall be
ready for delivery to Inmarsat no later than mid-May 2003.  The ROB shall have as a minimum the
functionality set out in the ROB Technical Specification attached as Appendix I
to the Statement of Work, Annex A.

 

Article 3                                               Performance Schedule

 

The parties have agreed to change the originally agreed delivery
schedule from one phase delivery with Final Acceptance to take place no
later than 30 months from EDC, to a two-phased delivery encompassing the
following revised delivery milestone dates:

 

	
  Delivery of RFT

  	
  ****

  
	
  Final Design Review

  	
  ****

  
	
  Delivery of RAN on the Bench (ROB)

  	
  ****

  
	
  Factory Acceptance (FAT) 1 for Baseline 1

  	
  ****

  
	
  Site Acceptance (SAT) 1 at Burum for Baseline 1

  	
  ****

  
	
  Factory Acceptance (FAT) 2 for Baseline 2

  	
  ****

  
	
  Site Acceptance (SAT) 2 at Burum for both RFSs

  	
  ****

  
	
  Site Acceptance (SAT) 2 at Fucino for both RFSs

  	
  ****

  
	
  Final Acceptance of Baselines 1 and 2

  	
  ****

  

 

Article 4                                               Price

 

Paragraph A of Article 4 is amended to read as follows:

 

The firm fixed price for the Work as defined in Annex A and B herein,
entitled Statement of Work and SRS, is $****
at EDC.  The firm fixed price shall be
subject to Change Notices subsequently entered into between the parties which
result in a change of the total value of the contract from the initial firm
fixed price.

 

3

 

New Paragraph C

 

C.                                     For avoidance of doubt, the **** of the Total Contract Value
available to Inmarsat for Liquidated Damages under Article 21 “Final
Acceptance Milestone” - sub-paragraph 2, shall be assessed against the then
current total value of the Contract.

 

New Paragraph D

 

D.                                    Inmarsat and Contractor have agreed to a
payment covering the total of 120 Man Months of effort required by Contractor
to accommodate increased resourcing due to delay of the SDM and re-phasing of
the programme into two distinct delivery phases.  The total payable is $****
which is payable in accordance with the distribution of additional resources as
a percentage add-on payment to the revised milestone payments shown under the
amended Annex D, entitled Price Breakdown and Payment Plan

 

Article 21                                        Incentives and
Remedies for Early and Late Delivery

 

Due to the parties change to a two phase delivery of the RAN,
Article 21 is hereby amended to reflect the revised schedule:

 

The Delivery Milestones under this Article 21 have been modified as
follows:

 

Milestone 1 - Factory Acceptance Test (FAT1) for Baseline 1

In case FAT 1 is delayed, the Contractor shall be liable for liquidated
damages in the amount of ****
per day for each day of delay of FAT 1 in accordance with Article 5 of the
Contract entitled Final Acceptance.  Such liquidated damages shall accrue up to a
total amount of United States Dollars ****.

 

The liquidated damages set out in 1. above shall accrue up to and
including the date of successful FAT1 or termination by Inmarsat pursuant to
Article 19 of the Contract entitled Termination.  During the period when liquidated damages are accruing, the
Contractor shall not be liable for any other damages with respect to such
delay, except as explicitly stated to the contrary.

 

Milestone 2 - Site Acceptance (SAT) 2 at Burum 

In case SAT 2 acceptance at Burum is delayed, the Contractor shall be
liable for liquidated damages in the amount of United States Dollars **** per day for each day of delay of
SAT 1 in accordance with Article 5 of the Contract entitled Final Acceptance.  Such liquidated damages shall accrue up to a total amount of
United States Dollars ****.

 

The liquidated damages set out in 1. above shall accrue up to and
including the date of successful SAT 2 or termination by Inmarsat pursuant to
Article 19

 

4

 

of the Contract entitled Termination. 
During the period when liquidated damages are accruing, the Contractor
shall not be liable for any other damages with respect to such delay, except as
explicitly stated to the contrary.

 

Final Acceptance Milestone

 

Paragraph 1 “Incentives” is hereby deleted as this is no longer relevant
due to the schedule change.

 

Paragraph 2 is modified to a Final Acceptance Date of EDC+40 months
(July 1, 2001 to October 31, 2004).

 

For avoidance of doubt, the parties confirm that the total Liquidated
Damages amount of **** of the
Contract Value shall include any sums paid by Contractor in connection with LD
Milestones 1 (FAT1) and 2 (SAT-2).

 

Annex A                                                 Statement of
Work

 

Sub-paragraph 1.2 of Article 10, entitled Warranty and Maintenance
shall be deleted and replaced with the following text:

 

10.1.2          The Contractor shall provide a
minimum of two years warranty and support commencing from the following start
dates:

 

a.                                               For the RFS and Antenna
equipment, the warranty start date shall be EDC plus 30 months, or 1
January 2004.

 

b.                                              For the RNS equipment, excluding
equipment identified under a. above delivered to the Burum SAS, the warranty
start date shall be SAT-1 at Burum.

 

c.                                               For the RNS equipment, excluding
equipment identified under a. above, delivered to Fucino SAS, the warranty
period shall commence from delivery of such RNS equipment to Fucino provided,
however, that the warranty start date for such RNS equipment under this
sub-paragraph c. is no earlier than EDC plus 30 months or SAT-1 at Burum,
whichever is the later.

 

d.                                              For all software delivered by
Contractor under sub-paragraphs b. and c. above, the warranty period shall
commence SAT-1 at Burum.

 

5

 

Annex C                                                 Air Interface
Specifications

 

****

 

Annex D                Price
Breakdown and Payment Plan

 

Payment Plan – Baseline Contract

 

The Baseline Payment Plan is hereby revised to reflect the change to a
two phase delivery of the system and inclusion of 120 Man Months of additional
effort by Contractor.  Milestones 1 - 4
covering **** of the baseline
contract price remain as originally stated, but a new Milestone 5 has been
added to reflect the RAN on the Bench (ROB) deliverable.  Thus, the following shall be the new payment
milestones for the baseline contract:

 

	
  Milestone

  	
   

  	
  Dates

  	
   

  	
  %

  	
   

  	
  Total
  Amount

  	
   

  	
  Plus
  Man

  Months

  	
   

  	
  Total
  Including

  120 Man Months

  	
   

  
	
  FDR

  	
   

  	
  11/02

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  0

  	
   

  	
  ****

  	
   

  
	
  Delivery or RFT

  	
   

  	
  11/02

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  0

  	
   

  	
  ****

  	
   

  
	
  Delivery of ROB

  	
   

  	
  05/03

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  0

  	
   

  	
  ****

  	
   

  
	
  FAT 1

  	
   

  	
  09/03

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  25

  	
   

  	
  ****

  	
   

  
	
  SAT 1

  	
   

  	
  01/04

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  35

  	
   

  	
  ****

  	
   

  
	
  FAT 2

  	
   

  	
  06/04

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  10

  	
   

  	
  ****

  	
   

  
	
  SAT 2 (Burum)

  	
   

  	
  08/04

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  10

  	
   

  	
  ****

  	
   

  
	
  SAT 2 (Fucino)

  	
   

  	
  09/04

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  40

  	
   

  	
  ****

  	
   

  
	
  Final Acceptance

  	
   

  	
  10/04

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  0

  	
   

  	
  ****

  	
   

  
	
  Warranty Year 1

  	
   

  	
  10/05

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  0

  	
   

  	
  ****

  	
   

  
	
  Warranty Year 2

  	
   

  	
  10/06

  	
   

  	
  ****

  	
   

  	
  ****

  	
   

  	
  0

  	
   

  	
  ****

  	
   

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  	
  ****

  	
   

  	
   

  	
   

  	
  ****

  	
   

  

 

The remaining baseline contract payments therefore total $****.

 

6

 

Annex F                                                   Key Personnel

 

The following is a revised list of key personnel.

 

	
  Name

  	
   

  	
  Title

  	
   

  	
  %
  on Project

  	
   

  
	
   

  	
   

  	
   

  	
   

  	
   

  	
   

  
	
  ****

  	
   

  	
  System Manager

  	
   

  	
  30

  	
   

  
	
  ****

  	
   

  	
  System R&D Manger

  	
   

  	
  75

  	
   

  
	
  ****

  	
   

  	
  RAN R&D Product Manager

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  RAN Programme Manager

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  RAN Project Manager

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  System Design Team Leader

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Sub-Contractor Manager

  	
   

  	
  50

  	
   

  
	
  ****

  	
   

  	
  System Engineering

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Team Leader, Host System Design

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Channel Unit SW Team Leader

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Channel Unit HW Team Leader and System
  Design

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Test Team Leader

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  UT Simulator Team Leader

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Quality Assurance Manager

  	
   

  	
  10

  	
   

  
	
  ****

  	
   

  	
  CNGW Team Leader

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  DSP Team Leader

  	
   

  	
  100

  	
   

  
	
  ****

  	
   

  	
  Development Engineer, RRM

  	
   

  	
  100

  	
   

  

 

 

Annex G                                                 Key
Sub-Contractors

 

Annex G is amended by deleting sub-contractor’s Logica UK Limited and
Wireless Intelligent Systems, Inc.

 

For Logica UK Limited, the following is substituted for Core Network
Interface Development Work:

 

Hughes Software Systems Ltd. (HSS)

Electronic City, Plot No. 31

Sector 18, Gurgaon 122015

Haryana (India)

 

Hughes Software Systems Ltd. Key Personnel

 

	
  N. Mohan

  	
  Engineering Manager

  
	
  Poonam Pandita

  	
  Configuration Manager

  
	
  V. Sivasankaran

  	
  System Engineer

  
	
  Prabhat Sahoo

  	
  Manager CN Development

  
	
  Rajinder Kumar

  	
  Manager Integration & Tetsing

  

 

7

 

Annex H                                                 Contractor
Background Disclosure

 

Logica Background is deleted.

 

HSS Background is substituted as follows:

 

	
  S. No

  	
   

  	
  RNC
  Protocols

  	
   

  	
  Compliance

  
	
  1.

  	
   

  	
  SSCOP

  	
   

  	
  ITU-T Q.2110

  
	
  2.

  	
   

  	
  Q2630.1

  	
   

  	
  ITU-T Q.2630.1

  
	
  3.

  	
   

  	
  Q2630.2

  	
   

  	
  ITU-T Q.2630.2

  
	
  4.

  	
   

  	
  SCCP

  	
   

  	
  Q.711 - Q.714, 1996, ETS 300 009 1996, T1.112 1996, GR 246

  
	
  5.

  	
   

  	
  DMTP3-B

  	
   

  	
  ITU-T Q. 2210, 1996

  
	
  6.

  	
   

  	
  GTP-U for RNC

  	
   

  	
  3G TS 29.060 v4.1.0 (2001-06)

  
	
  7.

  	
   

  	
  SSCF-NNI

  	
   

  	
  ITU-T Q.2140

  
	
  8.

  	
   

  	
  RANAP

  	
   

  	
  Intermediate Release- 3GPP TS 25.413 R99
  December 2001 version

  
Final
  Release will support R4 Compliance March 2002 version or later.

  
	
  9.

  	
   

  	
  Q.2150.1

  	
   

  	
  ITU-T Q.2150.1

  
	
  10.

  	
   

  	
  IPoA

  	
   

  	
  RFC 2684

  
	
  11.

  	
   

  	
  PDCP

  	
   

  	
  Intermediate Release ? 3GPP TS 25.323 v3.3.0

  

  Final Release will support R4 Compliance March 2002 version or later.

  

 

8

 

Appendix I to Annex A

****

 

 

9

Source: [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00067-of-00352.parquet"}, [{"source": "alea-institute/alea-institute/kl3m-data-edgar-agreements/train-00067-of-00352.parquet"}]]