Skip to content

2.2 Auto-IOS: Mission and Stakeholder Requirements

    Document/Purpose Mission requirements, users and stakeholders needs and documents their needs/requirements to enable an autonomous IOS system.

    Reference: https://sebokwiki.org/wiki/Stakeholder_Needs_and_Requirements_(glossary)
    Traceability (Upstream /Downstream) Documents Upstream: Mission Context
    Downstream: Mission Requirements, CONOPS
    Status DRAFT
    Baseline Version/Date | Current Version Not yet established | v0.1
    Last Updated  
    Owner / Lead  Sanjay Chadha
    Contributors  Sanjay Chadha
    Reviewers  
    Scope/Out-Of-Scope Scope: List of users, stakeholders and their requirements.
    Out-of-Scope: Operational Context, System Requirements

    Stakeholders

    Auto-IOS builds upon and changes the architecture and ownership related to IOS: 1.2.1 User/Stakeholder Requirements

    There is one and only one Auto-IOS system deployed. This Auto-IOS system is run under this IOS Initiative as an open system.

    The stakeholders under this Auto-IOS are:

    1. The IOS-Initiative team – This is global all inclusive team formed of members. The structure and creation of this team is to be determined.
    2. IOS Component Providers – These companies provides components based on standards under this initiative but are not actively involved in providing a service. These providers are stakeholders in the IOS Ecosystem as IOS Service providers use their components to build their services. Example IOS component providers: Ground Segment, LiDAR, RPOD technology, Propellant Transfer Interface, Flight Dynamics System, GNC, Thrusters
    3. IOS Service Providers – Any vendor providing any service within the IOS ecosystem is an IOS Service Provider (IOS-SP). Propellant Suppliers, Orbital Storage Vendors, Resupply Vendors
    4. IOS-Client – Companies which consume the services provided by the IOS Service Providers. Example: SpaceX, US Space Force, ESA

    Users

    The IOS-Initiative team consists of employees of members companies who contribute to work required to manage this initiative

    1. Systems Engineers
    2. Developers
    3. QA Personnel
    4. Integration
    5. Client and Vendor Support
    6. Business Development
    7. Operations Team

    The IOS-Initiative Requirements

    These are requirements related to the Auto-IOS part of the system only.

    1. The Auto-IOS shall enable a client to identify and coordinate logistics services without requiring human intervention.
    2. One and only one Auto-IOS eco-system shall exist.
    3. Auto-IOS shall have continuous availability of the Auto-IOS capability delivered through redundancy and fault-tolerant operations.
    4. Auto-IOS shall have built-in security to prevent unauthorized access to its functionality.
    5. Auto-IOS system shall be able to support varied clients and service providers
    6. Auto-IOS system shall be able to support services across all orbital regimes
    7. Auto-IOS system shall be able to support services across and within country regulations and regimes
    8. Auto-IOS shall monitor the health of all its constituents and, where possible, assist in auto-recovery.
    9. Auto-IOS shall be self-healing and shall not have any single point of failure.
    10. Auto-IOS shall be upgradeable to support new service types, new service and client capabilities, new interfaces, and new requirements without requiring replacement of the system.