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…
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…
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 /…
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…
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…
Document/Purpose Defines the operational environment of the IOR mission, identifies external actors, and describes how the system interacts with them. Reference: https://arcadia-method.org/operational-analysis.html Traceability (Upstream /Downstream) Documents Upstream: Business / Mission Analysis Downstream: Operational Analysis, OPCON Stages, Stakeholder Needs Status DRAFT…
Document/Purpose Defines the mission-level requirements the IOR system must satisfy to achieve the mission objectives. Reference: https://www.linkedin.com/pulse/mission-system-requirements-whats-difference-why-does-alan-fromberg-felkc/ Traceability (Upstream /Downstream) Documents Upstream: Stakeholder Requirements Downstream: CONOPS, System Requirements Status DRAFT Baseline Version/Date | Current Version Not yet established | v0.1 Last…
Document/Purpose Identifies users and stakeholders and documents their needs/requirements for the IOR mission Reference: 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…
1.2.1 Stakeholder (User/Owner/Customer) Requirements 1.2.2 Mission Requirements
WHY THIS IOR INITIATIVE This initiative enables companies to build their respective parts of an In-Orbit Refueling (IOR) ecosystem by providing system requirements, designs, system-level specifications, interfaces, QA frameworks, and guidelines. The objective is to ensure that independently developed…