| Document/Purpose | |
| Traceability (Upstream /Downstream) Documents | Upstream: Downstream: |
| Status | pre-DRAFT |
| Baseline Version/Date | Current Version | Not yet established | v0.1 |
| Last Updated | |
| Owner / Lead | Sanjay Chadha |
| Contributors | |
| Reviewers | |
| Scope/Out-Of-Scope | Scope: Out-of-Scope: |
Auto-IOS (In-Orbit Servicing) Architecture
Interfaces
| INTF# | System 1 | System 2 | Description |
|---|---|---|---|
| 1 | Auto-IOS (AIOS) | IOS-Client- GS | Interface between Auto-IOR and Clients who want to use the service of Auto-IOR |
| 2 | Auto-IOS (AIOS) | IOS-SP-GS | IOS Service Provider interface with Auto-IOS |
| 3. | IOS-Client-Spacecraft | IOS-Client-GS | Proprietary |
| 4 | IOS-SP-Spacecraft | IOS-SP-G | Proprietary |
| 5 | IOS-Client-Spacecraft | IOS-SP-Spacecraft | 4 Modes of Client and Service Provider interfaces exist as documented here 1.11.0 Terminology and Definitions |
These interfaces are are outlined in diagram below:

Message Flow (for example OTV)
| Interface | Message | Remarks |
|---|---|---|
|
|
Client Registers with Auto-IOS |
|
|
Service Provider Registers with auto-IOS |
|
|
Client Sends request to Auto-IOS to discover service provider |
|
|
Service Provider Ground Segment sends information of Service Provider Spacecraft (e.g. OTV) |
|
|
Client Ground Segment sends information of Service Provider Spacecraft (e.g. OTV) |
|
|
Use the messages in IRD document Inter Spacecraft Interfaces |