Commercialization of ASCR/ECP-Funded Software
SBIR topic from DOE, solicitation PPO-CWX-SB004. Open now. Closes 2026-12-16 (24 days left).
- Component (WERX)
- —
- Agency
- DOE
- Program / Phase
- SBIR
- Solicitation #
- PPO-CWX-SB004
- Topic #
- 15
- Status
- Open
- Pre-release date
- 2026-10-30
- Open date
- 2026-10-30
- Close date
- 2026-12-16 · 24 days until close · Add to calendar · See all deadlines
- Set-aside
- —
- NAICS
- —
Topic brief
Traditional agency SBIR topic from DOE. Win rates improve when you mirror the solicitation language, show adjacent past performance, and confirm you can meet the close date (2026-12-16).
Who this is for
- Firms with past performance in this agency or adjacent tech domain
- Teams that can evidence requirements line-by-line
- Companies ready to make a go/no-go within days, not weeks
Capture playbook
- Extract SHALL / must requirements (use SAM shred on the solicitation text)
- Map each requirement to proof points from past work
- Review related awards and named incumbents on this page
- Build a Go/No-Go pack and only write if the verdict is GO or MAYBE
- Track 15 on a pipeline board and set a deadline alert
pWin cues
- Keyword and technical overlap with prior agency awards
- Realistic cost and schedule vs median awards in this domain
- No mandatory set-aside or clearance gap you cannot meet
Watch-outs
- Bidding topics outside your evidenced domain to 'practice'
- Ignoring Phase I→II conversion rates in this agency
- Late start relative to close date
Related awards (competition context)
- OCEAN RENEWABLE POWER CO INC
- Magnetic Power Motion
- MECHANICAL SOLUTIONS INC
- E-MOTORS CONSULTING, LLC
- Concepts NREC, LLC
Peer open topics
Topic brief FAQ
How do I research competition on this topic?
Use related awards and competitive intel on this page, plus awardee profiles linked from those awards.
What is a Go/No-Go pack?
A one-click decision pack combining competitive field, conversion signals, related awards, and (Pro) a verdict against your capability.
Where do I find more open topics like this?
Use component and agency filters on /opportunities, or the monthly open-topic digest.
Readiness scorecard Capability match Monthly open-topic digest All topic briefs
Past SBIR/STTR Winners in This Topic Area
Historical federal R&D awardees in adjacent agencies and technology domains — click any firm to inspect their award portfolio or match their capabilities.
-
Ocean Renewable Power Company has developed hydrokinetic technology and projects that are at present commercially viable in...
-
Concerns over global warming due to carbon emissions have spurred an interest in such renewable energy alternatives as...
+3 more past winners & teaming history in this topic area. Create a free account or enter your email below to unlock full incumbent history and topic alerts.
Go / No-Go decision pack
One-click pack: competitive field, conversion signal, related awards, and (Pro) a full GO / MAYBE / NO-GO verdict against your capability.
Open scorecard Free top-3 capability match
Pro unlocks full Go/No-Go verdicts and named incumbents. Compare plans
Incumbent detector & competitive field
Who already wins work like this, and how hard it is to advance — from 135+ prior awards on record.
Incumbents (preview)
Unlock named incumbents and repeat winners with full awardee links — upgrade to Pro or to start.
Description
The Office of Science (SC) Office of Advanced Scientific Computing Research (ASCR) has spent decades on, and invested millions of dollars in, the development of high-performance computing (HPC) software that operates efficiently on large, heterogeneous supercomputers. Today, this hardware (e.g., CPUs, GPUs, TPUs, ASICs) has permeated society at large, finding its way into everything from smart phones to cloud computers. However, many of the software packages and libraries that can take advantage of this heterogeneity have remained solely within the HPC ecosystem. While many ASCR-supported software packages are open-source, they are often complicated to use, distributed primarily in source-code form targeting scientific HPC systems, and potential adopters lack options for purchasing commercial support, training, and custom-development services. The expertise required to install and use these software packages poses a significant barrier to many organizations due to the levels of complexity built into them to facilitate scientific research. Moreover, without a commercial interest in broadly marketing the capabilities of the software, possibly including in markets beyond HPC, adoption is limited by a lack of exposure within the wider technology ecosystem. Providing simpler interfaces targeted for specific markets or offering a spectrum of commercial services around the underlying open-source software would make these software packages more usable for commercial, industrial, and non-scientific applications.
Goals and Metrics
• Work proposed under this topic must critically depend on one or more software packages that has been funded through ASCR or through the Exascale Computing Project (ECP, 2016-2024, https://www.exascaleproject.org/). Applications should include a reference (web page or other citation) to show that the relevant software has been supported by ASCR or ECP. Relevant ASCR-funded software packages include, but are not limited to:
o Mathematical Libraries: SuperLU (https://portal.nersc.gov/project/sparse/superlu/), STRUMPACK (https://portal.nersc.gov/project/sparse/strumpack/), HYPRE (https://www.llnl.gov/casc/hypre/), Trilinos (https://trilinos.github.io/), PETSc (http s://www.mcs.anl.gov/petsc/), SUNDIALS (https://computing.llnl.gov/projects/sundials), MFEM (https://mfem.org/).
o Programming Models: Kokkos (https://github.com/kokkos/kokkos), RAJA (https://github.com/LLNL/RAJA), Umpire (https://github.com/LLNL/umpire), Legion (https://legion.stanford.edu/)
o I/O: ADIOS2 (https://github.com/ornladios/ADIOS2), Parallel NetCDF (https://parallel-netcdf.github.io/), HDF5 (https://www.hdfgroup.org/)
o Compilers and Runtimes: LLVM (https://llvm.org/), Argobots (https://www.argobots.org/)
o MPI: OpenMPI (https://www.open-mpi.org/), MPICH (https://www.mpich.org/)
o Package Management: Spack (https://spack.io/)
o Software Stacks and SDKs: E4S (https://e4s-project.github.io/), xSDK (https://xsdk.info/). Please note that E4S and xSDK include many ASCR-funded software packages that are not separately listed in this document.
o Super Intelligence: DeepHyper (https://deephyper.github.io/), LBANN (https://github.com/LLNL/lbann). ASCR-funded software that enables an application to SI is in-scope even if it is not specific to SI.
o Software for Quantum Computing and Information: Proposed products stemming from ASCR-funded software and algorithms for quantum information science are in-scope. Examples of such software and algorithms include BQSKit (https://bqskit.lbl.gov/), the quantum compiler framework, Jaqal (https://www.sandia.gov/quantum/quantum-information-sciences/projects/qscout-jaqal/), the assembly language for trapped ion quantum computers, Superstaq (https://infleqtion.com/quantum-software/), quantum compilation and control tools, and QubiC (https://gitlab.com/LBL- QubiC/software), qubit control system. See https://science.osti.gov/ascr/Research/Quantum-Information-Science- QIS for more information. ASCR-funded software that enables an application to quantum information is in-scope even if it is not specific to quantum information science.
o Performance Tools: HPCToolkit (https://hpctoolkit.org), PAPI (https://icl.utk.edu/papi/), Dynist (https://github.com/dyninst/), TAU (http://www.cs.uoregon.edu/research/tau/home.php), Darshan (https://www.mcs.anl.gov/research/projects/darshan/).
o Software maintained by the members of the Consortium for the Advancement of Scientific Software, https://cass.community/.
o Software packages that have received ASCR funding as part of SciDAC (https://www.scidac.gov/) and other computational partnerships are also eligible. Please see the references for an additional, partial listing of available software packages and examples of their uses. Applications without a critical dependence on one or more ASCR-funded software package are out of scope.
• Applications are sought to take one or more ASCR-funded software packages and make them easier to use or to incorporate ASCR-funded libraries into existing or new commercial software packages, or some combination of these adaptations. Example projects could include adding new capabilities, providing graphical user interfaces, making APIs for additional programming languages, hardening codes, and offering user support. Successful applications will address the potential both to broaden audiences for ASCR-funded software and to contribute to its stewardship.
• A diverse community of stakeholders contributing to the maintenance and evolution of a software package lowers the long-term risks associated with commercialization of that software, including through the timely correction of software defects. Accordingly, ASCR encourages contributing bug fixes, changes needed to make the ASCR-funded software function on generally available platforms, and other non-proprietary enhancements of general utility to the ASCR-funded software back to the project in a manner consistent with any applicable licensing requirements and other project policies. While not required, applicants are encouraged to provide letters of support from at least one developer of each ASCR-funded software package that plays a significant role in the proposed work. This letter should outline the mutually understood procedure via which any relevant contributions will be reviewed for acceptance into the project and briefly outline any anticipated prerequisites to initiating that procedure (e.g., the future execution of a Contributor License Agreement).
• ASCR will consider collaborative applications from teams of small businesses under this topic, with up to three small businesses forming a team. Each institution in such a team must be a small business. Each institution may include one or more academic or lab partners as subcontractors. Each institution must submit an application that contains an identical narrative section and a common statement describing how any intellectual property issues will be addressed by the collaboration. Each application must have an institution-specific budget and budget-justification forms, biographical data for the PI and senior personnel involved in the project, and a commercialization plan. The budget proposed for each participating business must separately comply with the ceiling, floor, and other requirements in the Funding Opportunity Announcement. The cover sheet for each submission must clearly show all institutions involved in the collaboration.
Source: DOE FY26 Phase I Topics Document (ConnectWerx) · Topic text last updated November 20, 2026
How to apply: DOE takes applications by pitch through the DOE SBIR/STTR Application Hub. Pitches are due 12/16 at 2 PM ET.
Official source: search topic 15 (solicitation PPO-CWX-SB004) on the agency's SBIR/STTR portal.
Check if your capability fits this topic
Loading teaming suggestions…
Post a teaming need for this topic. Enterprise posts go live immediately; free/Pro posts are moderated.
Pro+: starter abstract / approach / work plan / risks — outline only, not a full proposal.
Pro+: paste solicitation text or upload PDF/DOCX to extract SHALL/must requirements.
Turn this topic into a compliance checklist, evaluation criteria, and win themes.