Skip to content

2.5 ISOS4I & Auto-IOS – Extending ISO4I

    ISOS4I:  Components & Governing Bodies

    4 Components

    1. Servicing component (SC) – Delivers Services
    2. HOST component (HC) – Warehouse for fuel, satApps, platform for IOD/V
    3. Logistic component (LC): – Transport services like OTV for fuel, satApps. Launcher to Host
    4. satApps component (AC) – Modular components

    2 Governing Bodies

    • CSA – Industry led
    • PMAG – Pilot Mission Advisory Group
      • Commission
      • Member states

    ISOS4I 2:  Spacecraft Service Interfaces (SSI)

    1. Universal Service Interface (USI) – active includes mechanical, power and data
    1. Docking Interface – active
    1. Removal Interface – passive element to remove the owner
    1. Refuelling Interface – active

    Recommendation

    • Docking and refuelling same for SC, HC and LC
    • HC should allow the support of multiple EU-based USI solutions (such as SIROM, HOTDOCK, iSSI)

    ISOS4I 3:  Communication (including with GS)

    Communication architecture

    • Coordinated by CSA
    • Communication intra-component: HC, SC, LC and AC.
    • HC, SC, and LC communication with ground segment.

    ISOS4I Challenge– Managing Variations

    ISOS4I brings together four components: SC, HC, LC and satApps. With multiple variations.

    As ISOS Ecosystem evolves:

    1. Multiple vendors provide different interface solutions (BRIDGE, iFEX, iSSI, ASSIST).
    2. Each component may have different versions, configurations and capabilities.
    3. Service providers from outside the ISOS4I projects need to participate
    4. New providers and services enter the ecosystem, some are removed

    Components need to identify compatible service providers across these variations

    IOS Ecosystem is dynamic and diverse

    Global IOS Architecture

    Auto-IOS: Dynamic Discovery & Coordination

    Dynamic and Autonomous Ecosystem

    • Enables SC, HC, LC and satApps to discover and access services across the ecosystem.
    • Identifies suitable service providers based on component capabilities, interface compatibility and service requirements.

    Extensible Global Ecosystem

    • Supports the addition of new providers, services and capabilities.
    • Extends ISOS4I interoperability to international providers and initiatives.

    Autonomous Coordination

    • Coordinates service requests between clients and providers through Auto-Seed.
    • Enables service delivery across independently developed systems.

    What does it take to Integrate

    Easy to integrate API. Review details here.

    Benefits to Integrate Now

    1. Uniformity across all ISOS4I projects.
    2. All six ISOS4I projects can be demonstrated as one integrated project.
    3. Ability to add or remove components dynamically.
    4. Easy integration if incorporated into the architecture now.
    5. Avoid rework, redevelopment and re-verification