ÒÁÈËÖ±²¥

The key aim of the study is to establish the feasibility of a refuelling mission. The end of study will be marked by a formal review of the study outcomes.ÌýÌý

The Contract Recipient shall perform a number of key tasks during the study, as outlined below. In the Contract Recipient’s Response to this call for proposals, they should elaborate and critique these tasks, identifying any additional suitable activities (with justification), presenting Work Package Descriptions (WPDs) and a Work Breakdown Structure (WBS) demonstrating a comprehensive and organised management approach.Ìý

Task 1 - high level requirementsÌý

The justification for a refuelling mission needs to be based on firm requirements. This task is intended to capture these requirements in a High-Level Requirements Document.ÌýÌý

±õ²Ô±è³Ü³ÙÌý

All applicable documents (eg, the Call Guidance Document)Ìý

Task descriptionÌý

Create a hierarchical set of high level requirements that address:Ìý

• user requirements that will need to be met by a refuelling service provider in order to justify designing satellites that are capable of being refuelled in orbit. These can be actual user requirements or inferred requirements that the Contract Recipient recognises will need to be met
• mission requirements that meet the user requirements and any constraints that the Contract Recipient considers relevant. Include safety requirements, eg for the handling of fuel throughout the mission lifecycle including rendezvous, docking, transfer and undocking. Include requirements to minimise waste and to avoid producing additional debris
• initial space segment requirements that include high level requirements for the design, manufacture and test of the refuelling spacecraft
• initial ground segment requirements that address how the refuelling spacecraft will be monitored and controlled, and the interactions with the ground segment of the satellite to be refuelled. Address both ground segment hardware and software requirements.

°¿³Ü³Ù±è³Ü³ÙÌý

High level requirements document (HLRD)

• including traceability of lower level requirements to higher level requirements through use of a requirements numbering system
• addressing options where appropriate eg relating to the refuelling interface

Task 2 - concept of operationsÌý(CONOPS)

This task is intended to provide an overview of the way a proposed refuelling mission would be executed to refuel an ADR satellite plus a third party satellite in Low Earth Orbit.Ìý

±õ²Ô±è³Ü³ÙÌý

• all applicable documents (eg the Call Guidance Document)Ìý
• specification of the baseline UK ADR missionÌý
• high-level requirements from Task 1Ìý

Task descriptionÌý

Operations scenariosÌý

• outline operational scenarios, sequences and timeline for all mission phasesÌý
• address the approach, docking and transfer of fuel to the target spacecraftÌýÌý
• address orbit plane/height change issues (LEO only)Ìý
• describe nominal and contingency operationsÌý

Communications conceptÌý

• establish communication architecture for uplink and downlink, to achieve commandability and observability in nominal and degraded operations to include consideration of key technical parametersÌý
• define communications scenarios for all mission phasesÌý
• propose the frequency band to be used in line with International Telecommunication Union (ITU) Radio RegulationsÌý
• consider use of intersatellite comms with ADRÌý

Ground segment definitionÌý

• produce a preliminary design of the Ground Segment in accordance with the operational concept and the requirements flowed-down from Task 1

°¿³Ü³Ù±è³Ü³ÙÌý

• Concept of Operations (CONOPS) ReportÌý

Task 3 - Baseline Satellite DesignÌý

This task is intended to provide a technical overview of the proposed refuelling spacecraft.Ìý

±õ²Ô±è³Ü³ÙÌý

• all applicable documents (eg the Call Guidance Document)Ìý
• high-level requirements from Task 1Ìý
• CONOPS from Task 2Ìý

Task descriptionÌý

• produce a preliminary design of the satellite in accordance with the requirements flowed down from Task 1, down to subsystem level. Address any trade-offs that have led to the baseline design, state the TRL levels of subsystems etcÌý
• address the design of the refuelling subsystem hardware and softwareÌý
• address the design of the navigation hardware and softwareÌý
• produce a risk assessment highlighting the top 10 technical risks to the satellite design

°¿³Ü³Ù±è³Ü³Ù²õÌý

• Baseline Satellite Design Report (BSDR)Ìý

Task 4 - future mission planning and deliveryÌý

The UK Space Agency is keen to explore all avenues of mission delivery and how such a refuelling mission may be delivered outside of the traditional Phase B,C, D, E institutional model. Participants are invited to explore non-traditional approaches to mission delivery and how such approaches could be used whilst still giving the UK Space Agency confidence in committing public finance and enabling a good understanding of the factors that may affect the schedule and cost of the project.Ìý

Input

• all applicable documents (eg the Call Guidance Document)Ìý
• high-level requirements from Task 1Ìý
• CONOPS from Task 2Ìý
• basic Satellite Design from Task 3Ìý

Task descriptionÌý

Produce a delivery plan which gives confidence to the UK Space Agency which includes:Ìý

• an overview of the project team and the project management approach
• an analysis of the level of definition of the technologies selected for the baseline satellite design. Identify long lead items, the source of supply (UK/Non-UK, etc) and any ITAR/EAR and other export control issues
• an overview of the Manufacture, Assembly, Integration and Test (MAIT) approach
• an overview of the Product Assurance (PA) approach
• external interfaces and dependencies, and their potential impact on the cost and schedule
• the Risk Management approach; identify the top 10 cost and schedule risks
• an overview of any validation to be performed in orbit and supporting on-ground activitiesÌý

Define the mission schedule (one or more Gannt Charts in MS Project or compatible format) including clear identification of the critical path and key delivery milestones for all project phases. Include a summary bar chart in the Development Plan.

Provide an itemized ROM cost, in MS Excel format, for the activities from the start of Phase B to the launch and commissioning of the spacecraft. Include a summary of the costs in the Development Plan document.

Provide an itemised estimate ROM cost, in MS Excel format, of the annual operations cost once the satellite has been commissioned. Include a summary of the costs in the Development Plan.Ìý

°¿³Ü³Ù±è³Ü³Ù²õÌý

• development and delivery planÌý
• project Gantt Chart(s)Ìý
• ROM Cost Estimates which cover whole life mission costsÌý

Task 5 - the business caseÌý

The business case is crucial to the decision to build a spacecraft to refuel a target spacecraft. The cost to the user must be less than the cost of replacing a spent satellite with an identical replacement.ÌýÌý

±õ²Ô±è³Ü³ÙÌý

• all applicable documents (eg the Call Guidance Document)Ìý
• high-level requirements from Task 1Ìý
• CONOPS from Task 2Ìý
• basic satellite design from Task 3Ìý
• development and delivery plan from Task 4Ìý

Task DescriptionÌý

Propose options for an economic infrastructure to refuel satellites, including:Ìý

• market analysisÌý
• consideration of ground-based versus ‘gas station in space’ approachesÌý
• pricing policy eg price per servicing mission, multiple serving deals etc
• discussion of how many serving missions are needed per year to make them economic for both the users and the providerÌý
• assess the number and type of spacecraft that may adopt a refuelling approach and how they might be incentivised to make this commitmentÌý
• produce a risk assessment highlighting the top 10 business risksÌý
• demonstrate the benefits to the UK economyÌý

°¿³Ü³Ù±è³Ü³Ù²õÌý

• business case for Satellite Refuelling Missions in Low Earth Orbit

Task 6 - project managementÌý

This task relates to the management of the study.Ìý

±õ²Ô±è³Ü³ÙÌý

• all applicable documents (eg the Call Guidance Document)Ìý

Task DescriptionÌý

Produce a Project Management Plan (PMP) to manage the studyÌýÌý

Provide regular reports on each of the tasks:Ìý

• monthly progress reports, with reports sent on the last Tuesday of every month and prepared following the ‘monthly written report template’ outlined by the UK Space Agency
• organise a Mid Term Review (MTR) and Final Review (FR); take minutes, record actions etc

°¿³Ü³Ù±è³Ü³Ù²õÌý

• project management planÌý
• monthly reportsÌý
• meeting minutesÌý

Workflow and TimelineÌý

The project will be completed by 31 August 2024. The project will be punctuated by a series of project milestone meetings. Ahead of these meetings, the teams will be required to provide the relevant outputs and deliverables to the UK Space Agency panel for review. The main milestones for the project are to include the following:Ìý

• project kick-off: the Contract Recipient shall outline their plans for the study, recapping their proposal, highlighting any concerns/discussion points and stating any assumptions they have made
• project mid-term review (MTR): the mid-term review will allow for a review on the progress of the study highlighting progress in the development of the requirements baseline, the concept of operations and the baseline spacecraft design definition.Ìý
• final review (FR): planned for the end of the study, this review will provide updates on the requirements baseline, the concept of operations and the baseline spacecraft design definition but will focus on the future mission planning and delivery, and the business case for a refuelling mission.Ìý

The indicative timeline for the project is as follows:

• high level requirements: starting months 0, ending month 3
• concept of operations: starting month 1, ending month 6-7
• baseline satellite design: starting month 1, ending month 6-7
• future planning and delivery: starting month 4, ending month 7-8
• the business case: starting month 1, ending month 7-8
• KO meeting: month 0
• MTR meeting: month 4
• FR meeting: month 7-8

The mid-term review is expected to occur approximately half-way through the study (approximately 4 months after project kick-off). The final review will take place at the end of the study, ideally no later than 8 months after project kick-off.Ìý

¶Ù±ð±ô¾±±¹±ð°ù²¹²ú±ô±ð²õÌý

Table 1 defines the deliverables required in the study and allocates them to project milestones.ÌýAll deliverables shall be delivered 5 working days ahead of the milestone dates to allow for review. The only exceptions to this are the summary presentations for the KO, MTR, and FR – Contract Recipients should provide them at least 24 hours ahead of the corresponding review meeting.Ìý

Applicants are invited to consider and propose additional deliverables and milestones needed to progress their project.Ìý

Table 1: expected deliverablesÌý

Task	Deliverable name	KO	MTR	FR	Notes
6	KO presentation	Issue 1	Ìý	Ìý	Ìý
6	Project management plan	Issue 1	Ìý	Ìý	Ìý
1	High level requirements document	Ìý	Issue 1	Issue 2	Ìý
2	Concept of operations	Ìý	Issue 1	Issue 2	Ìý
3	Baseline satellite design	Ìý	Issue 1	Issue 2	Ìý
4	Development and delivery plan	Ìý	Ìý	Issue 1	Ìý
4	Development and delivery Gantt chart(s)	Ìý	Ìý	Issue 1	Ìý
4	ROM cost for development and delivery	Ìý	Ìý	Issue 1	Ìý
5	The business case	Ìý	Ìý	Issue 1	Ìý
6	Project management plan	Issue 1	Ìý	Ìý	Ìý
6	KO presentations and minutes	Issue 1	Ìý	Ìý	Ìý
6	MTR presentations and minutes	Ìý	Issue 1	Ìý	Ìý
6	FR presentations and minutes	Ìý	Ìý	Issue 1	Ìý
6	Monthly progress reports	Ìý	Ìý	Ìý	Ìý