Multimission Flight Support 2015

Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)

OVERVIEW
Multi Mission Flight Support (MMFS) shall be provided in the time period from 1.1.2015 to 31.12.2015 and optionally from 1.1.2015 until 31.12.2016 for all Low Earth Orbit (LEO) satellites being operated at German Space Operations Center (GSOC), Oberpfaffenhofen (Germany). The Multi Mission Flight Support team shall operate the command position in the control room of the LEO missions and support all scheduledn passes for spacecraft in orbit or simulated passes in preparation, test and validation phase.
Depending on the phase of the involved LEO missions four different types of support are requested:
1. Support during preparation, test and validation of the Mission Operation System
2. Operations support for satellite missions during the Launch and Early Orbit-Phase (LEOP) and Commissioning Phase (CP)
3. Routine operations of satellite missions
4. Multi Mission on-call support for contingency cases of one of the satellites in orbit
The following missions shall be supported:
— Grace (two satellites Grace 1 and Grace 2)
— TerraSAR-X/TanDEM-X mission (two satellites TSX and TDX)
— Firebird mission (two satellites TET-1 and BIROS)
— PAZ (1 satellite)
— Eu:CROPIS (1 satellite)
For Grace 1, Grace 2, TSX, TDX, TET-1 routine operations support is requested. The launch of BIROS is currently scheduled for the second quarter of 2015. Consequently, it is assumed that for BIROS the first three support types (see list above) are needed within the time frame of the current tender offer.
Eu:CROPIS launch is foreseen for the third quarter of 2016. Therefore it is assumed that support of type 1-3 is requested for this mission for the period in question.
According to current PAZ schedule the launch is foreseen for third quarter 2014. GSOC's PAZ project support is restricted to Lauch and Early Orbit Phase (LEOP). In principle MMFS support of type 1 and 2 would be necessary, type 3 support is not needed at all. If PAZ is launched as scheduled, all support periods lay outside of the time period covered by this invitation to tender. However, in case of a launch delay the support times may shift to 2015 or even later. Type 4 support (on-call) shall be provided as a single service for all missions in orbit with contractually agreed type 3 support.
The invitation to tender contains baseline and optional parts. Optional work packages have been chosen in the following cases:
— Support in 2016
— Support of type 1 and 2 as listed above
— Support for BIROS since operational concept is still evolving
— On-Call offer
TYPE 1 SUPPORT
MMFS Support in the preparation, test and validation phase comprises:
— Participations in simulations and rehearsals
— Participations in trainings
— Preparation of MMFS documentation for operations after launch
The volume of the requested support depends on the simulation concept of the supported missions. For the spacecraft BIROS and Eu: CROPIS the training concept is yet not consolidated. Therefore the volume of support shall be offered in a scalable way. Regulations concerning support volume and minimum purchase volume will follow. Information about statement of work and the corresponding mission specific requirements extensions will follow as well.
TYPE 2 SUPPORT
Type 2 support consists of the operations of the command position in the control room during LEOP and CP phase of the supported mission. The volume of the required service shall be scalable to the LEOP and CP operations concepts of the missions. Regulations concerning volume and minimum purchase volume will follow. Information about statement of work and the corresponding mission specific requirements extensions will follow as well.
TYPE 3 SUPPORT
Type 3 support consists of the operations of the command position in the control room during routine phase. The requested support comprises:
— Activities before, during and after passes scheduled for the LEO missions
— Offline activities not directly linked to passes
— Participation in routine missions meetings
A detailed statement of work (generic requirements for all missions) and the corresponding mission specific requirements extensions will follow.
The routine MMFS support shall be able to support the routine passes of the LEO missions. For sun-synchronous LEO missions the passes are each day at similar time of day. For non sun-synchronous LEO missions the passes are shifting in time. In general support times of LEO mission may overlap in time. Details of the pass patterns of GSOC LEO missions will follow.
This request does neither specify the detailed schedule of the MMFS routine support nor the total amount of support hours per day. It is with the freedom of the provider to offer a suitable team concept.
The team concept shall be optimally balanced between the following goals:
— Stable and safe operations concept
— Minimization of low activity phases during routine operations support
— Flexibility
The following boundary conditions need to be respected:
— At any time at least one MMFS Operator shall be present at site
— A hand over concept from one operator to the next shall be available
— All scheduled passes of the mission shall be supported
— The team schedule shall be adapted to the scheduled passes
— The duration of a support around a 10 min. pass is estimated including pre-pass and post-pass activities to the duration of an orbit (90 min.). During the 90 min. period the operator supporting the pass shall be at site and be ready to take over operational tasks. The support does not necessarily be centered in time around the pass. However, the operator shall be at console at least 20 min. before the pass.
TYPE 4 SUPPORT
On-call support shall be offered as a single service for all routine missions. The on-call support shall be activated in case of a spacecraft contingency. In this case additional passes might need to be supported. The intention of the on-call support is to cope with the increased operator support in contingency situation. Therefore, the effect on other LEO missions shall be minimized. The statement of work will follow. Timeless requirements will follow as well.

Deadline
Die Frist für den Eingang der Angebote war 2014-07-14. Die Ausschreibung wurde veröffentlicht am 2014-06-05.

Wer?

Wie?

Wo?

Geschichte der Beschaffung
Datum Dokument
2014-06-05 Auftragsbekanntmachung
2014-07-08 Ergänzende Angaben