Skip to content

2.3 Auto-IOS CONOPS

    Document/Purpose Defines the operational concept of the AUTO-IOS mission including mission context, actors, operational contexts, system actors, their interactions, and OPCON stages.
    Traceability (Upstream /Downstream) Documents Upstream: Mission Context, Stakeholder Requirements
    Downstream: Mission Requirements (note), System Requirements
    Status DRAFT
    Baseline Version/Date | Current Version Not yet established | v0.1
    Last Updated  
    Owner / Lead  Sanjay Chadha
    Contributors  
    Reviewers  
    Scope/Out-Of-Scope Scope: Operational Analysis (Mission Context, Operational Context), CONOPS stages
    Out-of-Scope: System Analysis, system design, system architecture

    Mission Context

     

    Orbit Regime: Auto-IOS is a unified, interoperable, and extensible system-of-systems framework that enables clients and service providers to autonomously discover, coordinate, and utilize in-orbit refuelling services.

    The Auto-IOS ecosystem enables independently operated systems to collaborate in fulfilling service requirements through standardized interfaces, service discovery, and autonomous coordination.

    Any participating system may act as both a client and a service provider. A service provider may, in turn, dynamically discover and engage other service providers to fulfil its own service obligations, enabling hierarchical and distributed service delivery.

    Operational Entities

    Key components in in the Auto-IOS CONOPS are:

      Definition
    Auto-IOS System The interoperable framework that enables registration, authentication, service discovery, and coordination between participants.
    Service Provider (SP) An independently operated system capable of offering one or more services. An SP may also act as a client when it requires services from other providers.
    Client A participating system that requests services to satisfy an operational need. A client may be an end-user spacecraft or another service provider.

     

    Auto-IOS_Mission Context.drawio.png

     

    Operational Interactions

    From To Interaction Details Nature
    Service Provider Auto-IOS Register Provide the details of the Service provider specifications. Information
    Auto-IOS Discover Discover the service providers which meet the discover criteria Information
    Auto-IOS Health Status Provide the Heath status, Telemetry, Errors Information
    Auto-IOS Operational Status Operational Status keeping Auto-IOS abreast of provider operational status  
    Client Auto-IOS Discover Discover the service providers which meet clients requirements for service Information
    Auto-IOS Operational Status Operational Status of the client keeping Auto-IOS abreast of client’s operational status  

     

    Auto-IOS Stages

    Other lifecycle stages like Development, Verification and End-of-life is on purpose omitted at this time.

    Stage 1: Auto-IOS Deployment & Commissioning

    In this stage the Auto-IOS a developed and verified under this initiative is installed..

    Stage 2A: Service Provider Registration

    All Service Provider have to be registered and be authenticated to provide services to the other service providers and clients. Service providers registers itself so it can be discovered to provide its services. A Service provider can be a client to a down stream service provider.

    1. Service Provider Deploy – Service Provider Deploys it services
    2. Service Provider Registers it service with Auto-IOS
    3. Auto-IOS authenticates the Service provider
    4. Auto-IOS verifies the service provider to make sure SP is behaving as expected
    5. Auto-IOS activates the service provider, thus making it service available to others.

    Stage 2B: Client Registration

    Each client has to register and be authenticated before it can request service from the Auto-IOS. Each client registers itself providing details of it specifications and potential requirements

    1. Client Deploy – Client Deploys it space crafts. Most client would be already existing contellations.
    2. Client registers itself with Auto-IOS
    3. Auto-IOS authenticates the client
    4. Auto-IOS verifies the service provider to make sure client is behaving as expected
    5. Auto-IOS activates the client, thus enabling it to request IOS services

    Stage 3: Service Provider Preparation

    Following registration, service providers may discover other providers whose capabilities are required to support their own service offerings.

    Providers may establish relationships in advance, either for a specific anticipated transaction or as a longer-term arrangement. Alternatively, relationships may be established dynamically during operations in response to a service request.

    A relationship may include capability compatibility, trust, interface compatibility, and applicable service terms.

    1. Service Provider Discovery– Discover service providers which are required but the service provider to deliver its services
    2. Establishes Relationship – Once suitable service providers are found, they establish a two way relationship

    Stage 4: Operations

    During operations, a client or service provider identifies a need for an in-orbit refuelling service. The participant uses Auto-IOS to discover compatible service providers and establish the necessary service arrangements.

    The selected provider and client coordinate and execute the service using the standardized interfaces defined by the IOS Systems Engineering Initiative. The outcome of the service is verified against the agreed service requirements.

    The operational sequence is:

    1. Detect – A client identifies a need for an in-orbit (refuelling) service.
    2. Discover – The client submits a service discovery request to Auto-IOS.
    3. Select – The client evaluates matching providers and selects a suitable provider.
    4. Coordinate – The client and provider establish service terms, confirm readiness, and commit to the service transaction.
    5. Execute – The client and provider perform the agreed service activities. 1.3 Concept of Operations (CONOPS)
    6. Verify – The parties confirm whether the service objectives and acceptance criteria have been met, and close or otherwise resolve the service transaction.

    Off-nominal operations

    The complete systems engineering must include Off-Nominal operations as shown below

    • No compatible provider is discovered.
    • A selected provider becomes unavailable before execution.
    • The client or provider loses communications.
    • The service is interrupted or only partially completed.
    • Verification fails or the outcome is uncertain.