| Document/Purpose |
Identifies users and stakeholders and documents their needs/requirements for the IOR mission |
| Traceability (Upstream / Downstream) Documents | Upstream: Mission Context Downstream: Mission Requirements, CONOPS |
| Status | DRAFT |
| Baseline Version/Date | Current Version | Not yet established | v0.1 4 Mar 2026 |
| Last Updated | 7 Mar 2026 |
| Owner / Lead | @Sanjay Chadha |
| Contributors | |
| Reviewers | |
| Scope / Out-Of-Scope | Scope: List of users, stakeholders and their requirements. Out-of-Scope: Operational Context, System Requirements |
Table of Contents
Users / Stakeholders
Users
Users are individuals or organizations that directly interact with the IOR system during operations.
- Production Teams – Personnel responsible for manufacturing and assembling the IOR system components.
- QA Personnel – Personnel responsible for verification, validation, and testing of the IOR system.
- Deployment Teams – Teams responsible for preparing and deploying the system for launch and operational use.
- Mission Operations Teams – Teams responsible for planning, coordinating, and executing refueling missions.
- Operators – Personnel responsible for operating the IOR servicing system and monitoring refueling missions.
- IOR Mission Operators
- IOR Mission Planners
- Satellite Operator Coordination Teams
- Ground System Operators
- Maintainers – Personnel responsible for maintaining the servicing vehicle, depot infrastructure, and associated ground systems.
Stakeholders
Stakeholders are organizations or groups that have an interest in the success, safety, or operation of the IOR system.
- Owner / Operating Entity – Organization responsible for operating the IOR infrastructure and ensuring its economic viability.
- Developers – Organizations responsible for developing the hardware, software, and infrastructure that make up the IOR system.
- Technology Partners – Companies providing specialized technologies such as propulsion systems, sensors, docking mechanisms, autonomy systems, or navigation technologies.
- Clients / Satellite Operators – Organizations that own or operate spacecraft or constellations and require in-orbit refueling services.
- Launch Providers – Organizations responsible for launching servicing vehicles, depots, or propellant supply missions.
- Space Agencies / Institutional Stakeholders – Organizations such as NASA, ESA, CSA, and other governmental bodies with interest in standards, safety, and mission coordination.
External Players and Authorities
- Regulatory Bodies: ITU, UNOOSA
- National spectrum Authorities – FCC, ISED, OfCom, country specific
- Space traffic management
- US Space Command / 18th Space Defense Squadron (18 SDS)
- EU Space Surveillance and Tracking (EU SST)
- Space Surveillance Networks
- Commercial space situational awareness providers
- Space Safety and Debris Mitigation Authorities
- Inter-Agency Space Debris Coordination Committee (IADC)
- United Nations Committee on the Peaceful Uses of Outer Space (UNCOPUOS)
- NASA Orbital Debris Program Office (ODPO)
- European Space Agency Space Debris Office (ESA SD)
IOR Owner Requirements
Operations Capability Requirements
Performance Requirements
Propellant Requirements
Customer Requirements (LEO, GEO or ISS)
Operations Requirements
| Requirement ID | Summary | Linked Issues | Stakeholder Type |
| IOR-STKR-OPER-17 | The IOR System mission design and CONOPS shall apply Do No Harm principles including collision avoidance, contamination control, ESD, EMI/EMC, and orbital debris mitigation practices. | Customer | |
| IOR-STKR-OPER-18 | The IOR System shall support configurable CONOPS to accommodate client-specific requirements during RPOD, mated operations, and departure phases. | Customer | |
| IOR-STKR-OPER-19 | The solution shall provide a nominal CONOPS describing routine execution of refuelling missions. | Customer | |
| IOR-STKR-OPER-20 | The IOR System shall support sustained operations in Geostationary Earth Orbit (GEO) consistent with the defined mission design lifespan. | Customer |
Propellant Requirements
| Requirement ID | Summary | Linked Issues | Stakeholder Type |
| IOR-STKR-PROP-21 | The Customer requires the IOR system to store and deliver multiple defined classes of spacecraft propellants. | Customer | |
| IOR-STKR-PROP-22 | The Customer requires the IOR system to support transfer of electric propulsion propellants. | Customer | |
| IOR-STKR-PROP-23 | The Customer requires the IOR system to support transfer of storable chemical propellants within the hypergolic family. | Customer | |
| IOR-STKR-PROP-24 | The Customer requires the IOR system to provide a minimum transferable propellant capacity of 1000 kg per client spacecraft, which may be delivered through one or multiple Service Vehicle (SV) missions. | Customer | |
| IOR-STKR-PROP-25 | The Customer requires the IOR system to support a minimum single-transfer quantity of 10 kg per refueling event. | Customer | |
| IOR-STKR-PROP-27 | The Customer requires the IOR system to achieve a propellant transfer rate of not less than X kg per minute. | Customer |