Merging ORS Standards to Facilitate Rapid Development of Reusable Spacecraft Software, Phase I

DNet has been actively pursuing strategies for shortening the software development portion of the satellite development life-cycle for some time. We recognized upon analyzing the constituents of the traditional process that a disproportionate fraction of time is spent working with software that falls under one of two categories - developed from scratch to suit the needs of a new mission, or recycling "heritage code" that subsequently requires extensive rework to achieve compatibility with a new system. The development segment devoted to software may never be truly compressed to zero, but significant measures can be taken to streamline the process. Code reusability has the potential to offer tangible savings. DNet is leveraging AFRL and NRL data standards to develop Application Programming Interfaces (API) that allow code modules to be ported to new systems with no modification of the application-level code and minimal modification of the subservient layers that facilitate compatibility with lower-level system facilities and transport layers. This API will facilitate the creation of a satellite system from modular applications that can be combined in such a way as to provide support for a wide range of missions and be completely reusable as the physical composition of the satellite is changed.

This is a mature technology (TRL 7+) — the realistic path in is usually NASA's Technology Transfer Program: licensing an existing NASA patent, or a Space Act Agreement to use NASA facilities/expertise directly. NASA also runs a startup licensing program with no upfront fee for companies formed to commercialize a specific NASA technology.

None of these are guaranteed paths for this specific project — TechPort itself doesn't have an "apply" button. Reaching out to the contact(s) above with a specific question is usually the fastest way to find out what's actually open.