Inactive

The Space Force is a large and complex organization consisting of many functions with similar counterparts in the commercial sector. The Space Force wishes to explore innovative technology domains wit... The Space Force is a large and complex organization consisting of many functions with similar counterparts in the commercial sector. The Space Force wishes to explore innovative technology domains with demonstrated commercial value in the non-Defense sector, i.e., through existing products/solutions, in order to obtain Space Force applications, i.e. Dual-Purpose Technologies/Solutions. We recognize that it is impossible for the STTR program to specifically solicit every potentially relevant technological area, thus this topic is intended to be an open call for specific ideas and technologies to include concepts or technologies that are not currently solicited (i.e. the “unknown-unknown”). It is important that potential solutions have a high probability of keeping pace with technological change. Thus, they should be closely tied to commercial technologies and solutions supporting the solution’s development. Maturation to Capstone This topic is meant for non-Defense commercial solutions to innovatively adapt to meet DoD stakeholders’ needs in a short timeframe and at a low cost. Proposals will be peer reviewed based on the criteria below. Selections will represent best value to the Government considering the following factors, which are of equal importance: 1. Commercialization Potential – The offeror(s) should demonstrate broad commercialization potential for the prospective solution in both the Defense and commercial markets. The most effective solutions demonstrate this potential through clear and concise description of customer value or Return on Investment over the current alternative. Moreover, the best solutions are expected to generate varied interest of non-affiliated commercial, investment, and defense entities – financial or otherwise. 2. Relevance to the Defense market – The offeror(s) should demonstrate the relevance of their solution to the ‘Focus Area’ listed below. The offeror(s) may provide an indication of relevance by demonstrating knowledge of the current status of the solution’s prospective operational environment and stakeholders, as well as preliminary discussions with those stakeholders. 3. Technical/Team – The offeror(s) should demonstrate the technical merit for the proposed solution, as indicated by supporting, peer-reviewed advocacy (including but not limited to scientific articles or publications), and the depth/relevance of team member experience. Technical merit may also be measured by the offeror(s) ability to propose a solution that integrates all 3 strategic capabilities listed below. Price reasonableness and realism will be considered to the extent appropriate. In accordance with 15 USC 638(dd)(7), investment by venture capital, private equity firms, or hedge funds shall not be used as an award criterion. In summary, proposals for this topic should demonstrate a high probability of identifying a product-mission fit between a Space Force end user and the proposed solution through a non-Defense commercial solution’s adaptation. This is initiated through the proposal of R/R&D being applied to a mature non-Defense technical solution and a starting point to find a Space Force Customer. FOCUS AREA The objective of this Focus Area is to explore potential commercial products being developed in the emerging On-Orbit Servicing, Assembly, and Manufacturing (OSAM) market, to include Life Extension; Satellite Refueling; On-Orbit Inspection; Orbit Transfer; End of Life Servicing, for potential use in Active Debris Removal (ADR), reuse and recycling of materials to build the foundation for assembly and manufacturing in space. A typical OSAM mission can be broken down into the 3 phases outlined below. The alignment between a proposal and one or more of these phases can strengthen an application. Note, this does not change the requirement to demonstrate the Defense need, but may complement it. As applicable, the offeror should address the solution’s connection to one or multiple of these phases in the Technical Volume. This should include how the proposed solution will be demonstrated first via a Model Based Engineering Approach in software. Proposers are encouraged to explore Modular Open Source Architecture (MOSA) tools such as the Robot Operating System (ROS-2), Gazebo, NASA’s TRICK or cFS. Use of such open tools will speed integration and allow for broader adoption across multiple agencies. 1. On-Orbit Object Approach: Approach and rendezvous with the Resident Space Object (RSO), to include space debris, etc., using approach and Rendezvous Proximity Operations (RPO) algorithms a. Inspection, Sensing, Characterization and Planning for capture b. Rendezvous Proximity Operations (RPO) 2. On-Orbit Object Acquisition: Capture and Control the orbital object and/or perform Rendezvous Proximity Operations Docking (RPOD) a. Execute capture b. Update control algorithms with new dynamic system c. Safe operations should be considered throughout RSO acquisition 3. On-Orbit Object Service: Remediate the RSO by repairing, repositioning, refueling, de-orbiting, reusing or recycling, etc. a. End Of Life Servicing (EOLS) b. De-orbit Maneuver c. Destination Orbits d. Mission Extension e. Reuse/Recycling of objects/materials PHASE I: Validate the product-market fit between the proposed solution and the ‘Focus Area’ through a feasibility study that includes a software based Model Based Engineering approach that defines a clear and immediately actionable plan for demonstration of the solution on orbit. This feasibility study should: 1. Clearly identify the prime potential USSF end user(s) and Space Force customer/transition agent (note: the user and customer will likely be two different people) and articulate how they would implement your solution(s) (i.e., the one who is most likely to be an early adopter, first user, and initial transition partner). 2. Deeply explore the problem or benefit area(s) which are to be addressed by the solution(s) - specifically focusing on how this solution will impact the end user of the solution, especially in light of current alternatives. 3. Define clear and measurable objectives and key results for a potential trial of the proposed solution with the identified USSF end user(s). 4. Clearly identify any additional specific stakeholders beyond the USSF end user(s) who will be critical to the success of any potential trial. This includes, but is not limited to, program, contracting, or finance organizations as well as relevant certifying or validating entities 5. Describe how the solution would differ from the non-defense commercial offering (i.e. how would it be modified as compared to its commercial counterpart). 6. Describe the cost and feasibility of integration with current mission-specific products. 7. Describe if and how the demonstration can be used by other DoD or governmental customers. PHASE II: Develop, install, integrate or otherwise demonstrate a prototype system determined to be the most feasible solution during the Phase I feasibility study. This demonstration should focus specifically on: 1. Evaluating the proposed solution against the objectives and measurable key results as defined in the Phase I feasibility study. 2. Describing in detail how the solution differs from prospective non-defense commercial offerings in comparison to USSF counterparts and how it can be scaled for broader use. 3. A clear transition path for the proposed solution that takes into account input from all affected stakeholders, including but not limited to: end users, engineering, sustainment, contracting, finance, legal, and cyber security. 4. Specific details about how the solution can integrate with other current and potential future solutions. 5. How the solution can be sustainable (i.e. overall supportability) 6. Clearly identify other specific DoD or governmental customers who want to use the solution