NASA SBIR 2008 Solicitation

FORM B - PROPOSAL SUMMARY


PROPOSAL NUMBER: 08-1 S4.04-9497
SUBTOPIC TITLE: Reusable Flight Software
PROPOSAL TITLE: Merging ORS Standards to Facilitate Rapid Development of Reusable Spacecraft Software

SMALL BUSINESS CONCERN (Firm Name, Mail Address, City/State/Zip, Phone)
Design_Net Engineering LLC
10311 W. Hampden Ave, Suite A-107
Lakewood, CO 80227 - 4314
(303) 462-0096

PRINCIPAL INVESTIGATOR/PROJECT MANAGER (Name, E-mail, Mail Address, City/State/Zip, Phone)
Dr. Ken Center
kcenter@design-group.com
10311 W. Hampden A ve, Suite A-107
Lakewood, CO 80227 - 4314
(303) 462-0096

Expected Technology Readiness Level (TRL) upon completion of contract: 4 to 5

TECHNICAL ABSTRACT (Limit 2000 characters, approximately 200 words)
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.

POTENTIAL NASA COMMERCIAL APPLICATIONS (Limit 1500 characters, approximately 150 words)
The standard Application Programming Interfaces and supporting tools developed through the course of this research have great utility to NASA for supporting the SBIRSat (e.g. Ames Research Center Small Satellite) program, which seeks more effective methods for constructing mission capability more rapidly and with lower cost. We would expect that the SBIRSat program is merely an opening for more widespread implementation of these standards, which could ultimately flow beyond the SBIRSat technology tracking into subsequent missions and eventually into larger programs.

POTENTIAL NON-NASA COMMERCIAL APPLICATIONS (Limit 1500 characters, approximately 150 words)
We already have significant heritage in the development of these software standards and tools for our military customers, AFRL and NRL. The utility of the offered software classes and supporting tools are unique to spacecraft development, but there are ample opportunities in the commercial space area for this work to be embraced and extended by the larger aerospace community. The Space Plug&Play Avionics (SPA) standards are likely to be accepted by the Operationally Responsive Space (ORS) program office, which will likely levy some portion of the standards on providers for the tactical mission series for which SPA was originally intended.

NASA's technology taxonomy has been developed by the SBIR-STTR program to disseminate awareness of proposed and awarded R/R&D in the agency. It is a listing of over 100 technologies, sorted into broad categories, of interest to NASA.

TECHNOLOGY TAXONOMY MAPPING
Computer System Architectures
On-Board Computing and Data Management


Form Generated on 11-24-08 11:56