Our friends from ORU BOAS project have reached a milestone that we're excited to share: the publication of a document defining the Design and Development requirements for any generic Orbit Replaceable Unit (ORU) or SatApp, transported in space by a dedicated Transporter.
What’s the purpose?
This deliverable establishes technical requirements for ORU/SatApps Providers from the perspective of a Transporter, ensuring seamless compatibility and integration.
Beyond technical specs
It also lays out essential programmatic elements – including schedule frameworks and preliminary deliverable lists – crucial for aligning development timelines with mission objectives.
Clarifying roles
In this context, the ORU/SatApps Customer refers specifically to the Transporter, not the final end-user of the payload, service or function once integrated into a space system, who will have his own technical and programmatic requirements.
What is an ORU Transporter?
Think of it as a space carrier, responsible for transferring an ORU/SatApps from its rocket injection point to its final destination. Examples include servicers (such as yours truly, EROSS) or logistics vehicles designed for on-orbit operations.
We thank our friends from ORU BOAS as this document is a fundamental step toward scalable, efficient and reliable in-space logistics – paving the way for future on-orbit servicing and assembly missions! Don’t hesitate to check it here
