Problem Statement

Increased and Varied Need – As number of constellations and their size increases and their space activities increase, satellites will require refueling regularly and on a ad-hoc basis.

Need for Easy Refueling A easy to manage propellant refuel service is required to replenish these satellites.

Multivendors systems must work together – The IOS ecosystem consists of multiple components from multivendor in different

Support all satellite systems – Al VLEO, LEO, ME, GEO, CisLunar need to be supported.

Cost Effective – Refueling must be clearer a better and cheaper option than replacement.

Problem Statement: All this requires an IOS Ecosystem which delivers in-orbit refueling services which autonomously coordinate services between multiple service providers to provide refueling services to clients.

(Note: Although focus of this exercise is IOS services, the effort can be extended to include other On-Orbit services).

Mission Statement

The purpose of this sub-project is to enable the existing IOS Systems-Of-Systems to deliver a fully autonomous In-Orbit Refueling service where client systems can discover and receive service from the service providers.

Each service provider can be a client system which needs to discover and coordinate with other service provider to fulfil its service.

For example a Propellant Service provider uses the service of Orbital Warehouse acting as a propellant storage, a propellant warehouse in turn uses the service of a resupply vendor who delivers the propellant from the ground.

Mission Objectives (MO) for Autonomous IOS

These MO are built on top of MO outlined in section 1.1 Mission Business Analysis

Mission Objectives

These mission objectives build on top of MO outlined 1.1 Mission Business Analysis

Mission Objective-Auto-IOS-#

1. MO-AI-1 — Provider and Component Discovery
   Enable Auto-IOS to define, register, store, search, and identify service providers and system components based on multi-dimensional specifications, including propellant type, interface compatibility, RPOD compatibility, Keplerian orbital elements/orbital state, cost, availability/timing, geographic constraints, and regulatory restrictions.
2. MO-AI-2 — Service Registration
   Enable service providers to register their services and capabilities.
3. MO-AI-3 — Service Provider Discovery
   Enable service providers to discover other service providers required to fulfil their service commitments.
4. MO-AI-4 — Client Service Discovery
   Enable clients to discover service providers capable of fulfilling their service requirements.
5. MO-AI-5 — Predictive Health Monitoring
   Enable IOS systems to report health status and enable Auto-IOS to identify potential issues and recommend appropriate remedial actions.
6. MO-AI-6 — Extendible to other On-Orbit Services
   Auto-IOS ecosystem should be extendible to support other on-orbit services beyond refueling, including repair and maintenance services.

Assumptions

Organizations such as ESA and US Space force, value the benefit of such autonomous IOS and fund the initial R&D to enable formation of such ecosystem

Constraints

None at this time. To be added

System of Interest

Same as the IOS 1.1 Mission Business Analysis

External Systems

Same as the IOS 1.1 Mission Business Analysis

Mission Context

Refer to https://reliqai-team.atlassian.net/wiki/x/pYB1