Access Official Technical PDF

Share Summary:LinkedInEmail

Technology transition—the work of moving a promising concept toward operational use—depends on more than technical merit. It also requires early engagement with potential users, clear routes to adoption and timely decisions about whether development should continue. In 2019, the Department of the Navy (DoN) outlined changes to its Small Business Innovation Research and Small Business Technology Transfer (SBIR/STTR) programs intended to strengthen those connections and accelerate the path from proposal to deployment.

The changes were relevant beyond defense procurement. For industrial automation engineers, system integrators and operations leaders, the program offered a useful view of how structured innovation efforts can connect technology developers with organizations that understand operational needs. The central idea was to make it easier to surface useful technologies, evaluate them sooner and identify a potential home for successful work.

Technology transition starts with earlier decisions

The Navy’s traditional SBIR/STTR process centered on scheduled solicitations and defined topics. The 2019 plan retained three broad-area announcement solicitations each year for traditional topics, while adding the possibility of out-of-cycle solicitations with more general themes. Rather than assessing every proposal only against a narrowly specified problem, the Navy said it would also consider where a technology might be useful.

This shifted the conversation in two directions. A government organization could describe a specific need for industry to address, or a company could explain what its technology could do and invite the Navy to consider relevant applications. For industrial organizations, this illustrates the value of pairing problem-led innovation with an open channel for solutions that may not fit an initial requirements statement.

The proposal process was also set to become shorter. Instead of a 20-page technical proposal, applicants would submit a five-page proposal and a pitch deck. The Navy’s stated targets were to make Phase I selections within two weeks and put contracts in place within 30 days. These were intended process changes, not a guarantee that every project would achieve an operational result on that timeline.

More opportunities, with stronger expectations for progress

The Navy planned to widen the pool of early-stage awardees and accept more risk in trying new ideas. Its announced approach called for increasing the number of Phase I awardees per topic from two or three to 20, and the number of Phase I projects moving to Phase II from one or two to five or six.

A broader funnel can create more opportunities for small businesses, including those new to SBIR. But it does not remove the need for evidence of progress. The director’s message was explicit: companies that delivered what they promised could expect the process to move faster, while projects that failed to progress could be ended sooner. For technology developers, that makes clear milestones, credible technical plans and regular communication important parts of a transition strategy.

The intended destination was not a successful demonstration alone. The Navy emphasized finding a place for technologies in its programs of record and connecting promising work with acquisition pathways. That distinction matters to any technical decision-maker evaluating a pilot: a demonstration can show potential, but transition planning also needs to address who could adopt the technology and what decisions must follow.

Focused events connect developers with potential users

The Navy also reconsidered its Forum for SBIR/STTR Transition (Navy FST). Rather than relying on one large, general-purpose conference, the program planned to showcase Phase II technologies at focused events related to their subject areas. The intent was to put small businesses in front of government and industry decision-makers closer to the relevant technology.

Planned event formats included exhibitor booths, one-on-one meetings and Tech Talks. The program identified events such as the Naval Submarine League Annual Symposium, WEST and the AIAA AVIATION Forum as venues for its 2019–2020 cycle. The broader lesson for industrial technology suppliers is that outreach is more useful when it reaches people who understand the application area and may be positioned to evaluate or sponsor a next step.

A Virtual Transition Marketplace (VTM) offered another connection point. Participating companies could present materials such as technology descriptions and quad charts, helping potential Navy users identify relevant work before meeting the developers. In one reported example, a Navy maintenance organization found a company’s plasma gasification system through the marketplace and explored whether it could address waste-disposal needs at its base. The initial technology search was not limited to naval aviation, illustrating how a solution may attract interest from an adjacent operational group.

Demonstrations reveal the range of transition challenges

Two examples in the program material show why transition planning needs to account for the application as well as the technology. Windlift’s airborne power generation system was developed in response to a Marine Corps interest in reducing the weight and volume of renewable hybrid systems for tactical environments. The company described a trailer-mounted system and participated in a Marine Corps Systems Command demonstration. Discussions identified a potential Phase III transition target; the source described a Phase III award as expected, not completed.

SubUAS’s Naviator, an air-surface-subsurface vehicle, was developed in response to a Navy topic concerning explosive ordnance disposal and mine countermeasures. Its developers described an approach that could move between air and water, allowing the vehicle to gather information underwater and transmit data after surfacing. The company received Phase III contracts, while its broader development work included potential payloads and endurance challenges. The example underscores that transition can involve adapting a core technology to distinct user needs, not simply delivering a prototype.

Practical implications for industrial technology teams

The Navy’s 2019 reforms were a pilot effort, and the department acknowledged that SBIR could not solve every capability gap. Still, the approach highlights practical considerations for organizations developing or evaluating automation and other industrial technologies:

  • Engage users early. Connect the technical concept to a specific operational problem, while remaining open to applications beyond the initial use case.
  • Make progress visible. Define achievable development steps and show whether the work is meeting its commitments.
  • Plan for adoption. Identify potential sponsors, decision-makers and the organizational route from demonstration to implementation.
  • Choose relevant venues. Target forums where people familiar with the technology and its operating environment can assess it.

For plant managers, operations leaders and engineering teams, the takeaway is straightforward: promising technology needs a transition plan alongside its technical plan. Faster evaluations and broader access can help surface more ideas, but sustained progress depends on matching solutions to real needs and establishing a credible path to adoption. The Navy’s 2019 initiative treated those connections as part of technology development—not as work to begin only after a prototype is complete.

Access Official Technical PDF

About The Author