Skip to content

1.9.6 In-Orbit Refueling (IOR) Architectural Initiative

What Is This Project The IOR Architectural Initiative is an eight-week systems engineering project created to deliver a structured architectural decomposition of an In-Orbit Refuelling (IOR) system. Phase I applies a disciplined systems engineering process to define mission context, capture… 

1.9.3 References

Normative References CONFERS: https://satelliteconfers.org/page/technical-committee-contributions CONFERS: Recommendations for Prepared In-Space (Re)Fueling Systems for Storable Propellants CONFERS: Recommendations for Best Practices, Functional Requirements, and Norms for In-space Servicing, Assembly, and Manufacturing (ISAM) Power and Data Interfaces NASA RPOD – https://www.nasa.gov/reference/jsc-rendezvous-prox-ops-docking-subsystems/ MERL –… 

1.9.2 Acronyms, Terms & Definitions

Acronyms AR&C – Autonomous Rendezvous and Capture. DSO – Dynamic Space Operations. ECEF – Earth-Centered Earth-Fixed. Used for ground locations. ECI – Earth Central Inertial – uses for orbits, spacecraft trajectory. GGNS – Guidance, Navigation and Control System. GN&C –… 

1.9 Appendix

Naming Convention OPCON Stages Examples OPC-LAUNCH OPC-ORBIT_INSERT OPC-STANDBY OPC-RENDEZVOUS OPC-PROXIMITY_OPS OPC-DOCKING OPC-PROP_TRANSFER OPC-UNDOCKING OPC-RETURN OPC-DISPOSAL Requirements IOR-<LEVEL>-<CATEGORY>-NNN LEVEL STKR = Stakeholder Requirement MISR = Mission Requirement SYSR = System Requirement DERR = Derived Requirement VERI = Verification Requirement HSWR –… 

1.8 Boundaries and Interfaces

  Document/Purpose  External and Internal Interfaces defined Traceability (Upstream /Downstream) Documents Upstream: Downstream: System Requirements Status DRAFT – Ready for Review Baseline Version/Date Current Version Not yet established | v0.1 04 Mar 2026 Last Updated  23 Mar 2026 Owner / Lead… 

1.7 Physical Architecture

Document/Purpose   Traceability (Upstream /Downstream) Documents Upstream: Downstream: Status pre-DRAFT WORK ON THIS SECTION HAS NOT STARTED. Baseline Version/Date | Current Version Not yet established | v0.1 04 Mar 2026 Last Updated  07 Mar 2026 Owner / Lead  Sanjay Chadha Contributors… 

1.6 Logical Architecture

Document/Purpose Traceability (Upstream /Downstream) Documents Upstream: 1.5 Functional Architecture and Activities Downstream: 1.7 Physical Architecture Status pre-DRAFT Baseline Version/Date | Current Version Not yet established | v0.1 04 Mar 2026 Last Updated  07 Mar 2026 Owner / Lead  Sanjay Chadha Contributors… 

1.5 Functional Architecture and Activities

  Document/Purpose Traceability (Upstream /Downstream) Documents Upstream: 1.3 Concept of Operations (CONOPS) Downstream: 1.4 System Requirements, 1.6 Logical Architecture Status pre-DRAFT Baseline Version/Date | Current Version Not yet established | v0.1 04 Mar 2026 Last Updated  22 Mar 2026 Owner /… 

1.4 System Requirements

Document/Purpose Documents the system requirements transformed from stakeholder needs, mission requirements, Traceability (Upstream /Downstream) Documents Upstream: Stakeholder Requirements, Mission Requirements, OpCons, Regulatory requirements, system constraints, Downstream: System Analysis, Logical Architecture Status pre-DRAFT WORK ON THIS SECTION HAS NOT STARTED. Baseline… 

1.3 Concept of Operations (CONOPS)

  Document/Purpose Defines the operational concept of the IOR mission including mission context, actors, operational contexts, system actors, their interactions, and OPCON stages. Reference: https://www.linkedin.com/pulse/mission-system-requirements-whats-difference-why-does-alan-fromberg-felkc/ Traceability (Upstream /Downstream) Documents Upstream: Mission Context, Stakeholder Requirements Downstream: Mission Requirements (note), System Requirements…