30.11.2012 Views

EDRS hosted payload AO - emits - Esa

EDRS hosted payload AO - emits - Esa

EDRS hosted payload AO - emits - Esa

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ESA UNCLASSIFIED – Releasable to the Public<br />

Announcement of Opportunity for <strong>hosted</strong> <strong>payload</strong> on board<br />

<strong>EDRS</strong> satellite<br />

Page 1/24<br />

TIA-TFS/2011-22271/FJ<br />

Date: 27/06/2011 Issue 1 Rev 0


ESA UNCLASSIFIED – Releasable to the Public<br />

Title Announcement of Opportunity for <strong>hosted</strong> <strong>payload</strong> on board <strong>EDRS</strong> satellite<br />

Issue 1 Revision 2<br />

Author TIA-TFS Date 11 August2011<br />

Reason for change Issue Revision Date<br />

Issue Revision<br />

Reason for change Date Pages Paragraph(s)<br />

- 2 -


ESA UNCLASSIFIED – Releasable to the Public<br />

Table of contents:<br />

1 ACRONYMS...............................................................................................................................................................4<br />

2 REFERENCE DOCUMENTATION ........................................................................................................................5<br />

3 BACKGROUND .........................................................................................................................................................5<br />

4 INTRODUCTION.......................................................................................................................................................5<br />

5 DESCRIPTION OF THE OPPORTUNITY.............................................................................................................6<br />

6 CONDITIONS FOR EMBARKATION ...................................................................................................................6<br />

6.1 TECHNICA L CONDITIONS .......................................................................................................................................6<br />

6.1.1 <strong>EDRS</strong>-C mission description............................................................................................................................6<br />

6. 1.2 On board resource allocation on board <strong>EDRS</strong>-C............................................................................................7<br />

6. 1.3 Operational constraints ...................................................................................................................................7<br />

6.2 SCHEDULE CONDITIONS...........................................................................................................................................8<br />

6.3 CONTRAC TUAL CONDITIONS ...................................................................................................................................8<br />

6.4 FI NANCIAL CONDITIONS..........................................................................................................................................9<br />

6.4.1 Embarkation fee...............................................................................................................................................9<br />

6.4.2 Provision of funding for the embarkation fee ................................................................................................10<br />

6.4.3 ESA possible contribution outside the <strong>AO</strong> hosting Mission Implementation Agreement...............................11<br />

7 SELECTION PROCEDURE AND EVALUATION CRITERIA.........................................................................11<br />

7.1 SE LECTION PROCEDURE ........................................................................................................................................11<br />

7.1.1 Step 1: Notice of Intent ..................................................................................................................................12<br />

7.1.2 Step 2: Clarification / Feasibility Assessment and Information Workshop ...................................................12<br />

7.1.3 Step 3: Proposal submission..........................................................................................................................13<br />

7.1.4 Step 4: Initial down-selection ........................................................................................................................13<br />

7.1.5 Step 5: Technical and Contractual dialogue .................................................................................................13<br />

7. 1.6 Step 6: Final proposal submission.................................................................................................................14<br />

7. 1.7 Step 7: Final selection ...................................................................................................................................14<br />

7.2 <strong>AO</strong> PROCESS SCHEDULE ........................................................................................................................................14<br />

7.3 EVALUA TION CRITERIA .........................................................................................................................................15<br />

7.3.1 Down-selection (Step 4)<br />

evaluation criteria ..................................................................................................15<br />

7.3.2<br />

7.3.3<br />

Final selection (Step 7) evaluation criteria ...................................................................................................15<br />

Summary of the process .................................................................................................................................16<br />

8 PROPOSAL GUIDELINES.....................................................................................................................................16<br />

8.1 GENERAL TENDER CONDITIONS.............................................................................................................................16<br />

8.2 PROPOSAL CONTENT .............................................................................................................................................17<br />

- 3 -


ESA UNCLASSIFIED – Releasable to the Public<br />

1 ACRONYMS<br />

AFT Abbreviated Function Test<br />

AIT Assembly Integration and Testing<br />

<strong>AO</strong> Announcement of Opportunity<br />

<strong>AO</strong>CS Attitude & Orbit Control Subsystem<br />

CA Coupled Analysis<br />

CDR Critical Design Review<br />

CFI Customer Furnished Item<br />

DP Data Pack<br />

DRB Delivery Review Board<br />

EESS Earth Exploration Satellite Services<br />

<strong>EDRS</strong> European Data Relay Satellite<br />

EGSE Electrical Ground Support Equipment<br />

EMC Electromagnetic Compatibility<br />

ESD Electrostatic discharge<br />

FMCR Flight Model Completion Review<br />

FFT Full Functional Test<br />

FOV Field Of View<br />

HP Hosted Payload<br />

ICD Interface Control Document<br />

IOT In Orbit Testing<br />

IRD Interface Requirement Document<br />

ISL Inter Satellite Link<br />

LCT Laser Communication Terminal<br />

LEO Low Earth Orbit<br />

LEOP Launch and Early Orbit Phase<br />

MAIT Manufacturing, Assembly, Integration and Test<br />

MIA Mission Implementation Agreement<br />

PDR Preliminary Design Review<br />

PPP Public Private Partnership<br />

PSR Pre Shipment Review<br />

Q&A Questions and Answers<br />

RFC Radio Frequency Compatibility<br />

S/C Spacecraft<br />

SFT System Functional Test<br />

SRR System Requirement Review<br />

HPTP HP Test Plan<br />

TIA Telecommunication and Integrated Application<br />

TM/TC Telecomm and and Telemetry<br />

TRB Test Review Board<br />

TRR Test Readiness Review<br />

- 4 -


ESA UNCLASSIFIED – Releasable to the Public<br />

2 REFERENCE DOCUMENTATION<br />

Ref Document Name Number Iss Date<br />

RD01 Call for Interest on in orbit validation for <strong>payload</strong><br />

<strong>hosted</strong> on-board Telecommunication satellites<br />

TIA/21624 15/03/2011<br />

RD02 Hosted Payload Interface Requirement Document <strong>EDRS</strong>-SAT-OHB-IRD- 01 30/06/2011<br />

for European Data Relay Satellite-C<br />

http://<strong>emits</strong>.esa.int/<strong>emits</strong>-doc/ESTEC/<strong>EDRS</strong>C-<br />

HostedPayloadInterfaceRequirement.pdf<br />

0001<br />

3 BACKGROUND<br />

The European Data Relay Satellite (<strong>EDRS</strong>) system programme was approved by the Joint<br />

Board on Communication Satellite Programmes (JCB) in January 2011 and is now entering<br />

its initial development (B/C/D/E) phase in a Public Private Partnership (PPP) between<br />

ESA and Industry. The “<strong>EDRS</strong>-C” element in the <strong>EDRS</strong> system refers to a geostationary<br />

satellite with some available resource on board to host additional <strong>payload</strong>(s).<br />

The Call for Interest issued by the Agency in March 2011 [RD01] has identified a large<br />

number of <strong>payload</strong>s potentially compatible technically and schedule-wise with <strong>EDRS</strong>-C.<br />

The consultation was however a non-committing and non-selective process aimed at<br />

gathering information on <strong>payload</strong> ideas. The information received was useful for<br />

identifying application domains, industrial and scientific Proponents and programmatic<br />

landscape (including <strong>payload</strong>s targeted to serve the needs of different ESA programmes),<br />

definition of mission and <strong>payload</strong> elements, maturity level and expected development<br />

schedule.<br />

The aim of the Announcement of Opportunity is the selection of the set of best matching<br />

<strong>payload</strong>s with the available resources in <strong>EDRS</strong>-C, compatible with the <strong>EDRS</strong> project<br />

requirements (schedule, risk, compatibility with <strong>EDRS</strong> mission) and providing full funding<br />

coverage with secured funding sources outside of the current <strong>EDRS</strong> financial subscriptions.<br />

4 INTRODUCTION<br />

This Announcement of Opportunity ultimately aims at generating additional funding for<br />

the <strong>EDRS</strong> program budget through an embarkation fee paid by the Hosted Payload (HP)<br />

provider(s).<br />

This document provides relevant information regarding the <strong>EDRS</strong> programme as well as<br />

conditions for <strong>payload</strong> embarkation. The selection process is described and content<br />

guidelines are also provided for the Proponents to produce their proposal.<br />

- 5 -


ESA UNCLASSIFIED – Releasable to the Public<br />

5 DESCRIPTION OF THE OPPORTUNITY<br />

The <strong>EDRS</strong> programme intends to ignite the emergence of a new type of Satellite Telecom<br />

services for future Earth Observation constellations by providing data relay function via a<br />

new Telecom Geostationary infrastructure. The PPP set up is such that the <strong>EDRS</strong>-C GEO<br />

satellite, as part of this infrastructure, will ultimately be owned and operated by the<br />

selected <strong>EDRS</strong> operator and service provider. This Announcement of Opportunity calls for<br />

Hosted Payload proposals to be embarked on a Geostationary satellite (<strong>EDRS</strong>-C) with the<br />

general concept of sharing the cost of satellite available resources and the launch. This<br />

allows lowering the cost for the <strong>EDRS</strong> programme whilst also providing access to space for<br />

a lower cost for the Hosted Payload Proponents.<br />

The fee applied for the embarkation of the HP is provided in section 6.4 with details of the<br />

activities included and excluded. In addition, the HP provider will also be responsible for<br />

the funding 0f the development of its <strong>payload</strong> and any other cost not covered by the<br />

embarkation fee.<br />

The overall on board resource available corresponds to an estimated Hosted Payload<br />

envelope of around 140 kg and 1.5kW power consumption with a launch planned in 2015.<br />

This envelope is indicative at this stage. This resource can be fully allocated to a single<br />

Hosted Payload or may be shared between several <strong>payload</strong>s. Although conceived to provide<br />

an in orbit validation opportunity, there is no specific restriction on the operational nature<br />

of the mission nor on the application domain, as long as compatible with the <strong>EDRS</strong>-C main<br />

mission on the technical and programmatic side (compatibility with <strong>EDRS</strong>-C <strong>payload</strong>(s),<br />

the platform capabilities, schedule). Those conditions are described in the following<br />

sections.<br />

6 CONDITIONS FOR EMBARKATION<br />

6.1 Technical conditions<br />

6.1.1 <strong>EDRS</strong>-C mission description<br />

The <strong>EDRS</strong> system will implement a full in orbit redundancy. The <strong>EDRS</strong>-C satellite is<br />

therefore one of a two in orbit node system and will be operated by the <strong>EDRS</strong> Operator.<br />

The satellite design is based on a small class (less than 400kg, 4kW <strong>payload</strong>) GEO platform<br />

using the OHB Small GEO product. From an orbital location at 3°East (to be confirmed),<br />

the satellite will carry a data relay <strong>payload</strong> with an optical Inter-Satellite Link (ISL) with<br />

the User LEO satellites and relaying the User data to the Ground through a European wide<br />

Ka band feeder downlink link coverage using the EESS band (26 GHz). Tasking services<br />

will also be provided allowing the User to re-programme its LEO satellites via <strong>EDRS</strong>-C<br />

satellite through the optical link to reach the LEO satellite. This function will require low<br />

rate transmissions from the ground and will be implemented using the <strong>EDRS</strong>-C satellite<br />

TM/TC capability. The optical ISL function is provided with the Laser Communication<br />

- 6 -


ESA UNCLASSIFIED – Releasable to the Public<br />

Terminal from TESAT using coherent detection technique at 1064 nm. Data rate of up to<br />

1.8 Gbps will be provided from the User LEO to ground via the <strong>EDRS</strong>-C satellite.<br />

The <strong>EDRS</strong>-C satellite will be operated from a dedicated satellite control centre. The <strong>EDRS</strong><br />

operator will operate several Feeder Link Ground Stations in Europe to receive the User<br />

LEO relayed data and distribute to the User premises through terrestrial means.<br />

Alternatively, the <strong>EDRS</strong> system operation also allows the User to receive their data directly<br />

from the <strong>EDRS</strong>-C satellite with an <strong>EDRS</strong> User Ground Station installed at their premises.<br />

The <strong>EDRS</strong>-C satellite will also carry a C-band <strong>payload</strong> provided by a commercial satellite<br />

operator in agreement with the <strong>EDRS</strong> Operator.<br />

A particular attention is drawn onto the operational compatibility of the Hosted Payload(s)<br />

with the optical ISL mission that can generate stringent operational requirements due to<br />

the pointing accuracy of the laser communication terminal.<br />

6.1.2 On board resource allocation on board <strong>EDRS</strong>-C<br />

A preliminary set of high level requirements have been defined to specify the envelope for<br />

the Hosted Payloads on board <strong>EDRS</strong>-C. The resources available are currently estimated at<br />

around 140 kg, 1.5kw power consumption. This envelope is indicative at this stage; these<br />

boundaries will be firmed up during the <strong>AO</strong> process. A more detailed set of requirements is<br />

provided in Appendix A in the form of an Interface Requirement Document. The<br />

Proponent is requested to include in his proposal the details of its own requirements as<br />

indicated in section 8. The compatibility of the candidate Hosted Payload with <strong>EDRS</strong>-C will<br />

be assessed on the basis of the information provided. The Proponent is therefore requested<br />

to provide as much information as possible.<br />

The Agency reserves the right to include Hosted Payloads provided internally and directly<br />

by other ESA directorate(s) and/or to confirm the allocation of some of the resource preallocated<br />

to the Italian Space Agency. Should this be the case the associated reduction of<br />

available resource will be communicated to the Proponents.<br />

6.1.3 Operational constraints<br />

Similarly to the physical accommodation constraints addressed in the previous section, the<br />

operational compatibility also needs to be assessed. The Appendix A provides a set of basic<br />

requirements and the Proponent is requested to include in his proposal the details of its<br />

own requirements with respect to the operation of <strong>payload</strong> (including the <strong>AO</strong>CS<br />

constraints, expected use of the TM/TC on-board and need for uplink/downlink<br />

capabilities, etc). The detail of the information requested is provided in section 8. The<br />

compatibility of the candidate Hosted Payload with <strong>EDRS</strong>-C will be assessed on the basis of<br />

the information provided. A basic principle of priority to the main <strong>EDRS</strong> mission is<br />

expected to be imposed over the Hosted Payload operations should such priority scheme be<br />

necessary.<br />

- 7 -


ESA UNCLASSIFIED – Releasable to the Public<br />

6.2 Schedule conditions<br />

The following table provides preliminary key milestones of the <strong>EDRS</strong>-C development<br />

phase.<br />

<strong>EDRS</strong>-C Satellite PDR (DP Delivery) 13.04.2012<br />

<strong>EDRS</strong>-C Satellite CDR (DP Delivery) 11.07.2013<br />

<strong>EDRS</strong>-C Platform TRB/DRB 10.10.2014<br />

<strong>EDRS</strong>-C Payload TRB/DRB 25.09.2014<br />

<strong>EDRS</strong>-C Satellite Test Readiness Review (TRR) 20.02.2015<br />

<strong>EDRS</strong>-C FMCR/PSR 23.09.2015<br />

<strong>EDRS</strong>-C Launch Readiness Review 03.11.2015<br />

<strong>EDRS</strong>-C Launch 04.11.2015<br />

<strong>EDRS</strong>-C In Orbit Acceptance 09.12.2015<br />

Table 1: <strong>EDRS</strong>-C Key milestone<br />

The delivery of the <strong>hosted</strong> <strong>payload</strong> to the satellite prime contractor will be optimised so as<br />

to minimise any impact to the overall <strong>EDRS</strong>-C spacecraft schedule. In their proposal,<br />

Proponents should identify the main schedule milestones for the HP (development,<br />

procurement and delivery) in absolute terms and in relation to the <strong>EDRS</strong>-C schedule with<br />

adequate justification.<br />

6.3 Contractual conditions<br />

This section outlines the main contractual requirements/conditions related to the Hosted<br />

Payload.<br />

The PPP between the Agency and the <strong>EDRS</strong> Operator provides the Agency with the right to<br />

integrate and launch suitable Hosted Payload(s) on board the <strong>EDRS</strong>-C satellite. The<br />

provisions of this PPP give rise to certain rights and obligations for both –ESA and <strong>EDRS</strong><br />

Operator- concerning the Hosted Payload whilst the operation and exploitation of the<br />

Hosted Payload shall be subject to a separate Agreement to be entered into between the HP<br />

Provider and the <strong>EDRS</strong> Operator.<br />

During the first phase of the <strong>AO</strong> process, the Proponent is requested to declare his<br />

acceptance of the main contractual principles related to the Hosted Payload, which are<br />

defined below.<br />

Following the down selection as detailed in chapter 7.1.4 of this document, the Agency will<br />

issue a draft Mission Implementation Agreement (MIA) providing more detailed<br />

contractual conditions regarding the undertakings of the Agency and the HP Provider to<br />

which the Proponent shall declare his acceptance with any reservations and/or deviations<br />

to be clearly indicated and duly justified (if any).<br />

- 8 -


ESA UNCLASSIFIED – Releasable to the Public<br />

Since the Hosted Payload will be a Customer Furnished Item (CFI) to be provided by the<br />

Proponent to the Agency, which will provide it to the <strong>EDRS</strong> Operator for integration and<br />

embarkation, acknowledgement and compliance with the following main contractual<br />

conditions is of utmost importance:<br />

• Ownership of the HP will remain with the HP Provider,<br />

• Intellectual Property Rights vested in the HP Provider will remain with the HP<br />

provider,<br />

• Access to Payload data, operation and exploitation of the HP will be subject to<br />

separate agreement between the HP Provider and the <strong>EDRS</strong> Operator,<br />

• ESA does not assume any responsibility for damage to or caused by the HP.<br />

• Loss of and damage to the HP occurring in the time period between having taken the<br />

HP into custody and lift-off of the launch vehicle that carries <strong>EDRS</strong>-C would be<br />

assumed by <strong>EDRS</strong> Operator. For insurance purposes, the HP Provider will be<br />

requested to identify the replacement value of the HP to the <strong>EDRS</strong> Operator.<br />

• Beyond that, liabilities for damage caused by or to the HP will remain with HP<br />

provider unless otherwise arranged in the separate agreement between the HP<br />

provider and the <strong>EDRS</strong> Operator,<br />

• In case the HP is delivered late, the HP provider undertakes to deliver a dummy<br />

<strong>payload</strong> at no cost,<br />

• Related frequency filing/licensing will be the responsibility of the HP Provider.<br />

• The HP Proponent shall identify any items subject to export control regulation (e.g.<br />

ITAR).<br />

6.4 Financial conditions<br />

6.4.1 Embarkation fee<br />

The Proponent is required to pay an embarkation fee including a contribution to the cost of<br />

Launch Services. Such fee is calculated as a pro-rata share of the Satellite resources utilised<br />

(mass in the first instance). An indicative formula for the calculation of the fee is:<br />

Fee (k€) = Hosted <strong>payload</strong> mass (kg) x 215 k€/kg<br />

In case the HP power consumption or dissipation proportion of the available resource is<br />

significantly higher than the mass proportion, the computation of the fee will need to be<br />

adjusted accordingly.<br />

The above embarkation fee may also be adjusted in relation with the integration activities<br />

complexity of the Hosted Payload on the Host satellite.<br />

In case the Proponent intends to also take up insurance, the Agency will support the<br />

Proponent in obtaining access to the <strong>EDRS</strong>-C main insurer (still to be selected) in order to<br />

obtain best insurance (financial) conditions.<br />

- 9 -


ESA UNCLASSIFIED – Releasable to the Public<br />

The embarkation fee includes:<br />

• Integration of the HP onto the host satellite (the details of the integration activities<br />

will need to be defined and agreed between the HP provider and the Satellite<br />

Manufacturer),<br />

• Support of the host satellite manufacturer for ground testing (command and control<br />

tasks), commanding and controlling of FFT . The evaluation of test data is under the<br />

responsibility of the HP provider with its own specific EGSE,<br />

• Launch,<br />

• LEOP,<br />

• Support of the host satellite manufacturer for IOT (command and control tasks),<br />

functional and performance tests are under the responsibility of the HP provider.<br />

The embarkation fee excludes any other cost, in particular:<br />

• Development/procurement cost of the HP <strong>payload</strong>,<br />

• Frequency filing cost and costs related to activities for coordination of the HP<br />

mission,<br />

• HP performance evaluation on ground and in orbit<br />

• Operational fee charged by <strong>EDRS</strong> Operator during the operating life of the HP. This<br />

fee will mainly depend on the Payload Telemetry and Telecommand requirements.<br />

It will be subject to separate agreement between the <strong>EDRS</strong> Operator and the HP<br />

supplier negotiated after down selection (Step 4) during the dialogue period (Step 5)<br />

through discussion with the <strong>EDRS</strong> Operator. The Agency will assist the Proponent in<br />

negotiations with the <strong>EDRS</strong> Operator for the provision of in-orbit operation fee.<br />

• Insurance<br />

• Any ground support equipment needed for Satellite AIT, Satellite IOT or at satellite<br />

operational center to process data.<br />

6.4.2 Provision of funding for the embarkation fee<br />

The embarkation fee shall be paid to ESA as a financial contribution to the <strong>EDRS</strong><br />

programme. Any source of funding, private or public, including ESA, can possibly<br />

contribute to the embarkation fee.<br />

Please note that in case the Proponent intends to have ESA partially or totally fund the<br />

embarkation fee it is important to address the request and seek the support from the<br />

relevant ESA programme/directorate and, when required, from the corresponding<br />

National Delegation.<br />

If the HP is a telecommunication <strong>payload</strong>, ESA will only potentially cover part or all<br />

embarkation fees that are duly supported by one or more National Delegations with their<br />

corresponding expressions of support as defined in 7.2 (financial proposal) included in the<br />

Proponent’s proposal.<br />

For non-telecommunication <strong>payload</strong>s, ESA can also contribute to the embarkation fee<br />

through funding provided by the programme(s)/directorate(s) that benefits from the<br />

<strong>payload</strong> (as a user, or for any other possible benefits). The ESA<br />

- 10 -


ESA UNCLASSIFIED – Releasable to the Public<br />

programme(s)/directorate(s) shall be identified by the HP Proponent early on in the<br />

process (Step 1) and the Proponent shall directly seek the required confirmation of interest<br />

and support.<br />

6.4.3 ESA possible contribution outside the <strong>AO</strong> hosting Mission<br />

Implementation Agreement<br />

If the proposed Hosted Payload contains innovative technology elements, ESA might under<br />

certain conditions (co)-fund the <strong>payload</strong> development non-recurring cost for the innovative<br />

technology elements. The level of the ESA funding depends on the degree of innovation of<br />

such technology elements. This potential contribution from ESA into the development of<br />

the Hosted Payload shall in any case be arranged separately from the Hosting Payload<br />

agreement subject of this <strong>AO</strong> (such as using ARTES 3-4 or ARTES 5.2), through separate<br />

contracts clearly indicated/suggested by the Proponent in its proposal.<br />

Proponents are invited to analyse the conditions for support and to assess their suitability.<br />

7 SELECTION PROCEDURE AND EVALUATION CRITERIA<br />

The selection through this <strong>AO</strong> will be performed against the criteria defined in section 7.3.<br />

Two stages are foreseen in the selection process:<br />

• a first down-selection in which only proposals providing an overall good marking<br />

(aggregate mark equal or higher than 60) are retained; the evaluation criteria are<br />

aimed at defining a ranking of the proposals with the aim of retaining the group of<br />

best matching proposals;<br />

• a final selection based on the assessment against the final set of evaluation criteria.<br />

A certain degree of interaction between the Proponents, the <strong>EDRS</strong> industrial team and ESA<br />

teams (from <strong>EDRS</strong> project or other application relevant ESA programmes) are expected in<br />

the early stages of the process to ascertain compatibility of the candidate <strong>payload</strong> with the<br />

<strong>EDRS</strong>-C main mission.<br />

7.1 Selection procedure<br />

The purpose of the section is to describe the process leading to a final selection, including a<br />

number of steps aimed at facilitating the interactions mentioned above. The steps are listed<br />

below and explained in detail in subsequent paragraphs.<br />

Step 1: Notice of Intent<br />

Step 2: Clarification, Feasibility Assessment and Information Workshop<br />

Step 3: Proposal submission<br />

Step 4: Initial down-selection<br />

Step 5: Technical and contractual dialogue<br />

Step 6: Final proposal submission<br />

Step 7: Final selection<br />

- 11 -


ESA UNCLASSIFIED – Releasable to the Public<br />

7.1.1 Step 1: Notice of Intent<br />

Following the issuing of this Announcement of Opportunity, interested parties are<br />

requested to submit a Notice of Intent providing a first set of information of the proposed<br />

<strong>payload</strong> and financial scheme (including identified funding sources).<br />

The information required at this stage is similar to that requested for the ESA Call for<br />

Interest issued in March 2011 but with special emphasis in two areas:<br />

1. Accommodation of the <strong>payload</strong> into <strong>EDRS</strong>-C satellite and assessment of<br />

compatibility with the <strong>EDRS</strong> mission. This task requires a first compliance<br />

assessment to the requirements of Appendix A and the delivery of detailed<br />

information on specific elements of the <strong>payload</strong> that might pose difficulties in their<br />

accommodation as well as operations (e.g. appendages, specific locations and/or<br />

orientations, bulky elements, moving parts, high dissipation, links and access to<br />

other S/C resources: on board data bus, on board memory, Ka-band link for <strong>payload</strong><br />

data dump on ground, …).<br />

Identification of funding sources, either private or public. Funding sources should cover all<br />

aspects related to the proposed mission, including <strong>payload</strong> development, <strong>payload</strong><br />

procurement and <strong>payload</strong> embarkation fees. In case ESA is expected to contribute to the<br />

funding of the embarkation fee, the ESA programme/directorate that would be the<br />

user/beneficiary of that <strong>payload</strong> shall be identified and a confirmation of support<br />

indicated.<br />

Appendix B defines the template for the Notice of Intent with required information that<br />

shall be submitted by e-mail to the address <strong>payload</strong>cfi@esa.int.<br />

Please note that further communications (provision of initial feedback,<br />

possibility of further questions, broadcast of general-interest Q&A, invitation<br />

to Information Workshop) will only be done with Proponents having<br />

submitted a Notice of Intent by the deadline defined in section 7.2.<br />

7.1.2 Step 2: Clarification / Feasibility Assessment and Information<br />

Workshop<br />

The decision on <strong>payload</strong>s to be embarked requires a full assessment of a number of aspects,<br />

on the basis of complete proposals. In particular, there will be 3 critical topics in the<br />

selection by ESA:<br />

o compatibility with the <strong>EDRS</strong> mission and project requirements (including <strong>payload</strong><br />

accommodation and schedule),<br />

o assessment of risk induced by the <strong>payload</strong><br />

o evidence of funding availability for the <strong>payload</strong> development, embarkation fee and<br />

operational fee.<br />

- 12 -


ESA UNCLASSIFIED – Releasable to the Public<br />

It is recognised that some interactions with the Proponents will be required (with ESA<br />

experts, ESA programme managers, the <strong>EDRS</strong> industrial and ESA project teams, National<br />

Delegations or Agencies for the different programmes and application domains). ESA,<br />

therefore, offers support to all Proponents with a confirmed interest (by means of the<br />

Notice of Intent defined in Step 1) in providing further clarifications aimed at determining<br />

the feasibility of the proposed <strong>payload</strong> (Step 2).<br />

The ultimate aim of this step is that sufficient information is available for the Proponent to<br />

prepare a full proposal compatible with technical, programmatic and financial<br />

requirements.<br />

Questions shall be addressed via e-mail to the address <strong>payload</strong>cfi@esa.int. Questions will<br />

be collected during the period and will be answered on an individual basis as soon as<br />

possible and latest by a Workshop planned the fourth week of August 2011 (25 th -26 th<br />

August, to be held at ESTEC, Noordwijk). The purpose of this workshop is to clarify as<br />

much as possible the selection process, conditions, and information required. Therefore,<br />

presentation sessions will be organised with general Q&A sessions as well as possibility of<br />

short slots for one-to-one Q&A on aspects specific to a Proponent proposal. The<br />

participation of ESA (technical, programmatic, contractual and legal representatives), the<br />

<strong>EDRS</strong> Operator and the <strong>EDRS</strong>-C satellite prime contractor is foreseen.<br />

7.1.3 Step 3: Proposal submission<br />

By the defined deadline (see calendar in section 7.2) full proposals will need to be<br />

submitted, with the content defined in section 8).<br />

7.1.4 Step 4: Initial down-selection<br />

The proposals received by the deadline will be evaluated against the criteria defined in<br />

section 7.3. The emphasis in this initial down-selection is to retain proposals that<br />

demonstrate their ability to meet the criteria. A particular attention will be given to<br />

credibility of the proposals on the financial and schedule aspects. Proposals that obtain an<br />

overall marking equal or higher than good (60) will be retained for the next steps.<br />

7.1.5 Step 5: Technical and Contractual dialogue<br />

Retained Proponents from Step 4 will then receive additional information,<br />

• on technical aspects (detailed accommodation requirements with issuing IRD<br />

version 1 with firmed up resource envelope, implementation and operational<br />

constraints, additional <strong>payload</strong>s being considered to form a set, etc)<br />

• on contractual and financial aspects:<br />

o between ESA and the Proponent regarding the HP embarkation (in the form<br />

of a draft Mission Implementation Agreement provided by ESA)<br />

o between the <strong>EDRS</strong> Operator and the Proponent with an initial set of<br />

operation fees and conditions provided by the <strong>EDRS</strong> Operator.<br />

- 13 -


ESA UNCLASSIFIED – Releasable to the Public<br />

The discussion will be established, both with ESA and with the <strong>EDRS</strong> industrial prime<br />

contractor on those technical, contractual and financial aspects.<br />

The financing commitments shall also be finalised during this step.<br />

7.1.6 Step 6: Final proposal submission<br />

At the end of the dialogue phase, a final version of the proposal will be submitted for final<br />

evaluation, including<br />

• an updated and more detailed technical content including the<br />

o HP ICD version 0,<br />

o HP Test Plan (AIT and IOT ) version 0,<br />

• compliance with the Mission Implementation Agreement,<br />

• final evidence of committed financing to cover all mission aspects (subscription<br />

letter, bank guarantee, etc).<br />

7.1.7 Step 7: Final selection<br />

The final selection will be made on the basis of the evaluation of the final proposals (step<br />

6). The same criteria used in the first down-selection, complemented with additional<br />

criteria as defined in section 7.3, will be used to rank the proposals. The final selection will<br />

also consider the best fit of the selected <strong>payload</strong>s set with the available <strong>EDRS</strong>-C resources<br />

(e.g. a set of <strong>payload</strong>s individually ranked lower might provide a best fit than a higher<br />

ranking individual <strong>payload</strong> than cannot be aggregated with other <strong>payload</strong>s).<br />

7.2 <strong>AO</strong> process schedule<br />

The schedule associated to the <strong>AO</strong> is defined in the following table:<br />

Step Event Date<br />

1 Notice of Intent As early as possible, latest by 1st September<br />

2 Clarification / feasibility assessment August 2011 based on submitted Notice of<br />

Intent<br />

+ Information Workshop<br />

22nd-23rd September 2011<br />

3 Proposal submission 7th October 2011<br />

4 Technical + Contractual dialogue October – November 2011<br />

5 Final proposal submission 15th December 2011<br />

6 Final selection December 2011/January 2012<br />

- 14 -<br />

2011<br />

Table 2: <strong>AO</strong> process schedule


ESA UNCLASSIFIED – Releasable to the Public<br />

7.3 Evaluation criteria<br />

This section identifies the evaluation criteria that will be used for both the down-selection<br />

(Step 4) and final selection (Step 7).<br />

7.3.1 Down-selection (Step 4) evaluation criteria<br />

For the down-selection, the following evaluation criteria will be used:<br />

• Compatibility with <strong>EDRS</strong>-C (technical + programmatic)<br />

• Risk assessment (technical + programmatic)<br />

• Evidence of funding coverage (public and/or private) of all mission elements<br />

(<strong>payload</strong>, embarkation, operations) on the basis of letters of support from funding<br />

sources<br />

• Level of compliance with contractual principles<br />

All criteria will have equal weight in the computation of the total marking.<br />

7.3.2 Final selection (Step 7) evaluation criteria<br />

For the final selection, the following evaluation criteria will be used:<br />

1. Criteria with high weighting factor (all equal to 20%):<br />

• Detailed compatibility with <strong>EDRS</strong>-C (technical + programmatic)<br />

• Detailed risk assessment (technical + programmatic)<br />

• Evidence of funding coverage (public and/or private) of all mission elements<br />

(<strong>payload</strong>, embarkation, operations) on the basis of committing steps from funding<br />

sources (subscription letter, bank guarantee, etc)<br />

• Compliance with the Mission Implementation Agreement<br />

2. Criteria with low weighting factor (all equal to 10%):<br />

• Benefits (innovation, scientific return, industrial strategic impact, etc)<br />

• Fill rate of <strong>EDRS</strong>-C available resources (individually or in a set of <strong>payload</strong>s)<br />

In its final assessment for the selecting/ranking of the Hosted Payload(s), the Agency will<br />

take into account the most effective and adequate utilisation of the <strong>EDRS</strong>-C satellite<br />

resource whilst maximising the financial contribution from the Proponent(s) for the<br />

embarkation fee.<br />

- 15 -


ESA UNCLASSIFIED – Releasable to the Public<br />

7.3.3 Summary of the process<br />

The following diagram summarises the planned process with main inputs from ESA and<br />

from the Proponents<br />

8 PROPOSAL GUIDELINES<br />

8.1 General tender conditions<br />

Figure 1: Announcement of Opportunity Process<br />

The proposal and all correspondence relating to it shall be in English.<br />

The proposal shall specifically state a period of validity of 4 months from the closing date<br />

for the receipt of tenders (for each of the two proposal submission Steps 3 and 6).<br />

Any document submitted in reply to the <strong>AO</strong> shall become the property of the Agency. It<br />

will use commercially sensitive or proprietary information solely for the purpose of the<br />

evaluation of proposal and the selection of the Hosted Payload Provider. ESA reserves the<br />

right to share information with <strong>EDRS</strong> Operator and <strong>EDRS</strong> Satellite manufacturer.<br />

Expenses incurred in the preparation and dispatch of the proposal will not be reimbursed.<br />

The <strong>AO</strong> does not bind the Agency in any way to place a contract.<br />

The Agency reserves the right to issue amendments to the <strong>AO</strong>.<br />

- 16 -


ESA UNCLASSIFIED – Releasable to the Public<br />

Prior to submitting the proposal, the Proponent is requested to complete and send a Notice<br />

of Intent form no later than the date indicated in the section 7.2. The template for this<br />

document is provided in Appendix B.<br />

8.2 Proposal content<br />

The Proponent shall include at least the following content (any additional relevant<br />

information deemed necessary by the Proponent may be included in its proposal)<br />

The final proposal (Step 6) is expected with a higher level of details than the first submitted<br />

proposal (Step 3).<br />

� Signed Cover Letter containing a summary of the Hosted Payload mission main<br />

features and objectives along with the company or consortium involved. Contact details<br />

for persons responsible for technical and contractual matters shall also be identified.<br />

� Technical proposal providing at least the following information<br />

� Mission description, objectives and benefits<br />

Any foreseen (co)-funding from ESA for the development of the HP shall be<br />

identified and justified.<br />

� Justification for the flight<br />

In case of an in-orbit validation case, the Proponent is invited to highlight<br />

the benefits of such an IOV (as opposed on ground demonstration when<br />

applicable for example).<br />

� Architecture and functional description including block diagram<br />

� Frequency plan and associated Radio Regulation constraints and status<br />

The Proponent is expected to be responsible for necessary Radio Regulation<br />

activities related to the Hosted Payload mission (including filing and<br />

coordination of the filing if applicable)<br />

� Detailed Technical budget including margins allocation:<br />

� Mass<br />

� Power consumption (average, peak, duty cycle),<br />

� Power dissipation,<br />

� TM/TC budget<br />

� Accommodation requirements:<br />

� Volumes<br />

� Preferred/mandatory locations/orientation on spacecraft<br />

� Visibility cone requirements<br />

� Need for deployment of antennas<br />

� Mechanical interfaces<br />

- 17 -


ESA UNCLASSIFIED – Releasable to the Public<br />

� Electrical interfaces<br />

• Power interface<br />

• Command interface and type of commanding (no. of commands incl. spares)<br />

• Telemetry interface and type of interface (no. of TLM incl. spares)<br />

• Data protocols interface and protocols<br />

� Access to other <strong>EDRS</strong>-C resources (e.g. attitude data …etc.)<br />

� Failure propagation free interfaces<br />

� Environment Requirements<br />

� Mechanical environment requirements<br />

� Shock compatibility<br />

� EMC-C and EMC-S environment requirements<br />

� EMC-RE and RS environment requirements<br />

� RFC environment requirements (RF power, frequency, in-band /out of band,<br />

modulation)<br />

� Thermal environment requirements<br />

� Orbit Radiations susceptibility<br />

� ESD<br />

� <strong>AO</strong>CS requirement<br />

� Ranging and position<br />

� Pointing requirements<br />

� Micro-vibration requirements<br />

� Operational requirement:<br />

� Operating lifetime<br />

� Utilisation profile and operational constraints<br />

� TM/TC ressource utilisation profile<br />

� Special Integration and Testing requirements<br />

� Mechanical<br />

� Thermal<br />

� Cleanliness<br />

• Class<br />

• Purging requirements , if any<br />

• Protection requirements, if any<br />

� Electrical<br />

� EMC/ESD tests<br />

� Safety (human safety like Laser light…)<br />

� IOT<br />

In the final proposal submission, the Proponent shall include an HP <strong>payload</strong><br />

ICD version 0<br />

- 18 -


ESA UNCLASSIFIED – Releasable to the Public<br />

� Implementation proposal providing at least the following information<br />

� Design and Development plan<br />

� Complete Qualification status for the <strong>payload</strong> sub-systems and equipment<br />

� Development plans for the <strong>payload</strong> sub-systems and equipment<br />

� Master schedule including margin allocation and its adequacy with the <strong>EDRS</strong>-C<br />

development schedule<br />

In the final proposal, a HP Test Plan version 0 covering both AIT and IOT<br />

shall be provided by the Proponent<br />

� Critical items list<br />

� Risk analysis<br />

� Management and contractual proposal<br />

� Industrial organisation (entities and their role)<br />

� Relevant Background information on the entities involved<br />

� Analysis of the preliminary contractual conditions (the Proponent is invited to<br />

indicate any critical contractual items they wish to discuss)<br />

In the final proposal, a Mission Implementation Agreement shall be reviewed<br />

by the Proponent (see Statement of concurrence section)<br />

� Financial proposal<br />

� Cost estimation for the development of the Hosted Payload and any other cost not<br />

covered by the HP Embarkation fee as defined in section 6.4.1<br />

� Proposed financial contribution for the HP embarkation fee defined in section 6.4.1<br />

� Proposed financial contribution for the HP operational fee<br />

� Financing scheme indicating for each of the above items<br />

� Identification of the funding sources<br />

� Apportionment between these various funding sources<br />

� Evidence of commitment from the funding sources (private and/or public)<br />

Letters of support are expected in the first proposal submission<br />

More committing documents are expected in the final proposal submissions<br />

(subscription letter, bank guarantee, etc)<br />

� Statement of concurrence<br />

� compliance with the <strong>EDRS</strong>-C Hosted Payload IRD (Appendix A)<br />

The Proponent shall provide the statement of compliance in a tabulated<br />

format. A Word version of the IRD file will be provided after reception of the<br />

Notice of Intent and the Hosted Payload Data Sheet from the Proponent.<br />

This compliance will be against IRD version 0 in the first proposal<br />

submission and against IRD version 1 in the final proposal submission<br />

� compliance with Mission Implementation Agreement (provided later see section<br />

7.1.5)<br />

Only required in the final proposal submission.<br />

- 19 -


ESA UNCLASSIFIED – Releasable to the Public<br />

APPENDIX A INTERFACE REQUIREMENT FOR THE HOSTED<br />

PAYLOADS ON BOARD <strong>EDRS</strong>-C<br />

Considering the early stage of the <strong>EDRS</strong>-C development it is not possible to provide a fully<br />

fledged IRD in the <strong>AO</strong> data package. The version of the IRD provided [RD02, attached in<br />

the link below] is therefore preliminary and provides only a certain level of details. A more<br />

complete version will be provided after down selection for more in depth technical<br />

iterations (Step 5).<br />

In addition to this document, and on the basis of received Notice Of Intent, the generic<br />

interface document related to the host platform will also be provided to the proponents at a<br />

later stage.<br />

http://<strong>emits</strong>.esa.int/<strong>emits</strong>-doc/ESTEC/<strong>EDRS</strong>C-HostedPayloadInterfaceRequirement.pdf<br />

- 20 -


ESA UNCLASSIFIED – Releasable to the Public<br />

APPENDIX B NOTICE OF INTENT FORM<br />

Name of the Proponent company:<br />

SUMMARY PAGE<br />

Contract manager name: Technical manager name:<br />

Mailing address: Mailing address:<br />

Tel.: Tel.:<br />

Fax: Fax<br />

E-mail: E-mail:<br />

Name of the proposed Hosted Payload:<br />

Brief description of the proposed Hosted Payload:<br />

Anticipated expected deviations wrt Appendix A, if any:<br />

- 21 -


ESA UNCLASSIFIED – Releasable to the Public<br />

HOSTED PAYLOAD DATA SHEET<br />

The following information shall be provided in the Notice of Intent.<br />

1. Proponent consortium<br />

This section shall identify the company or consortium of companies proposing the <strong>payload</strong>,<br />

defining the role of each company involved. The different countries involved in case public<br />

funding would be required shall be identified.<br />

2. Payload/mission description<br />

This section shall briefly describe the proposed <strong>payload</strong>. In case the <strong>payload</strong> will be part of<br />

a system/mission the overall system/mission shall be described.<br />

3. Payload elements<br />

This section shall describe the elements constituting the <strong>payload</strong>: equipment, antennas,<br />

other appendages.<br />

4. Telecommunication and regulatory aspects<br />

This section shall define any requirements associated to direct communication aspects<br />

from/to the proposed <strong>payload</strong> and associated regulatory aspects, if any.<br />

5. Estimated technical budgets and accommodation<br />

This section shall define the best estimate of the technical budgets (mass, power<br />

consumption –average, peak, duty cycle-, volume –for the different <strong>payload</strong> elements-,<br />

power dissipation, thermal constraints, telecommand/telemetry needs, memory,<br />

processing) and specific accommodation constraints (specific location, orientation,<br />

visibility needs).<br />

6. Operational constraints<br />

This section shall define operational requirements (ranging from TC/TM transmission to<br />

direct supervision of in-orbit performance parameters, continuous/intermittent operation,<br />

experiment duration, etc).<br />

This section shall also indicate any requirement relating to data access restriction (if any)<br />

- 22 -


ESA UNCLASSIFIED – Releasable to the Public<br />

7. Maturity level and pre-development needs<br />

This section shall identify the current maturity level of the proposed <strong>payload</strong> (TRL), any<br />

existing development plans (e.g. EQM already under way) and unplanned but necessary<br />

developments required to reach a PFM or FM stage, together with the associated schedule<br />

and estimated cost and funding needs.<br />

8. In case the <strong>payload</strong> if for In Orbit Validation purposes<br />

a. Validation objectives (in case the <strong>payload</strong> if for In Ortbit Validation purposes)<br />

This section shall define the objectives pursued with the validation in-orbit of the<br />

proposed concept (e.g. flight demonstration, in-orbit qualification, flight heritage<br />

build-up, new system/technological concept validation)<br />

b. Benefits of proposed IOV and associated beneficiaries<br />

This section shall define the benefits and strategic impact of carrying out the<br />

proposed IOV. Benefits can be direct (e.g. for the company proponent of an<br />

innovative equipment) or indirect (e.g. for satellite prime manufacturers, for<br />

satellite Operators or Service Providers). The beneficiaries shall be identified, as a<br />

generic class (e.g. Operators).<br />

9. Schedule aspects<br />

This section shall show preliminary schedule information demonstrating compatibility<br />

with schedule requirement defined in the section 6.2.<br />

10. Funding aspects<br />

This section shall define all funding-related aspects, including mention of contacts already<br />

established with ESA National Delegations and related expressions of interest, possibilities<br />

for co-funding development and/or cost from private sources (identifying in that case the<br />

source: e.g. own company funds, beneficiaries, customers/users/etc).<br />

ROM Cost estimate<br />

o Payload development:<br />

o Payload embarkation fees:<br />

o Payload operations:<br />

- 23 -


ESA UNCLASSIFIED – Releasable to the Public<br />

Funding sources (either private or public).<br />

o Payload development:<br />

o Payload embarkation fees:<br />

o Payload operations:<br />

In case ESA is expected to contribute to funding through separate contracts, the ESA<br />

programmes that would be the user/beneficiary of that <strong>payload</strong> and hence the<br />

contributor to the funding shall also be identified.<br />

- 24 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!