Access Official Technical PDF

Share Summary:LinkedInEmail

Technology transition—the movement of research outputs toward use by operational organizations—is a central challenge in industrial automation as well as public-sector research. The U.S. Department of Homeland Security’s Science and Technology Directorate (DHS S&T) FY2020 Congressional Justification provides a detailed example of how an R&D organization connected its budget, technical activities and performance measures to that goal. The document is a historical budget plan, not a report on current funding, but its structure offers a useful way to examine the work required to move technology beyond development.

Technology transition begins with operational requirements

DHS S&T described its research and development mission as providing solutions for DHS components and first responders. Its stated approach balanced risk, cost, impact and time to delivery, with a focus on work linked to operational efficiency, effectiveness and safety. That framing matters to technical decision-makers: an innovation is not ready for adoption simply because it works in a development setting. It also needs to address a defined user need and be evaluated in terms of its intended operating context.

The Directorate’s organizational structure reflected several parts of this process. Research, Development and Innovation (RD&I) funded research and technical solutions. Acquisition and Operations Analysis supported requirements analysis, systems engineering, standards development, testing and evaluation, and technology transition. Laboratory Facilities supported laboratory operations and maintenance, while Mission Support provided corporate functions that enabled technical programs to operate.

For automation teams, this separation highlights a practical planning point: research, engineering, validation and deployment support are related activities, but they require different capabilities and resources. Treating them as connected stages can help teams identify what must happen between a prototype and an operational system.

Testing and systems engineering connect development to use

The budget describes Operations and Support funding as supporting systems engineering, standards, and test and evaluation so that technologies developed by S&T and procured by DHS components would work and be delivered on time and within budget. Acquisition and Operations Analysis, in particular, provided expert assistance across the Homeland Security Enterprise to improve the efficiency and effectiveness of operational capabilities through the transition, acquisition and deployment of technologies, information and procedures.

These functions are relevant wherever a technology must fit into established operations. Testing and evaluation can assess whether a solution meets its intended requirements; systems engineering can address how it works as part of a broader capability; and standards work can support consistent expectations. The budget does not prescribe a specific industrial automation process, but it makes clear that technical development was only one part of the transition pathway.

Milestones make progress visible

DHS S&T used program measures to monitor progress against plans. For RD&I, one management measure tracked the percentage of fiscal-year milestones met as set out in the budget execution plan. The document defined these milestones as technical or programmatic events, accomplishments or intermediate goals. Its FY2020 target was 75%; results for that year were listed as undetermined in the budget document.

A separate strategic measure tracked the percentage of Apex technologies or knowledge products transitioned to customers for planned improvements in the Homeland Security Enterprise. Apex projects were described as high-priority, cross-cutting efforts with innovation cycles of three to five years, from project inception through operational testing. The FY2020 target was 80%, while the result was not yet available in the document.

For engineering and operations leaders, the distinction between these measures is useful. Milestones indicate whether planned work is progressing; transition measures focus on whether outputs reach intended customers. Neither measure alone establishes the operational value of a technology, but together they illustrate why organizations may need to track both execution and handoff.

Funding timelines affect technical execution

The FY2020 request proposed $582.117 million for the Directorate, a decrease of about $1.2 million from the FY2019 President’s Budget. Within that total, the request included $303.163 million for Research and Development and $278.954 million for Operations and Support. The budget also described a new organizational approach, begun on October 1, 2018, intended to help S&T transition capabilities more rapidly and respond to emerging threats.

The document also explained why some activities required funding that remained available across multiple years. Acquisition and Operations Analysis supported activities such as testing, systems engineering and technology transition that could span fiscal years. Laboratory Facilities funding supported the operation and maintenance of aging, complex facilities, where some repair needs could be difficult to predict. The budget argued that shorter funding availability could constrain access to resources or create inefficiencies.

For organizations managing automation programs, the broader consideration is that technical schedules and financial schedules must align. Testing, facility needs and integration work may not fit neatly within a single annual planning cycle. The DHS budget illustrates how funding duration can be treated as part of program execution rather than as a separate administrative detail.

Applying the framework to automation programs

The DHS example suggests several questions for teams planning technology adoption:

  • Is the operational need clear? Connect development work to a defined user or process requirement.
  • Are validation and engineering resourced? Account for testing, systems engineering and standards alongside R&D.
  • Are progress and transition both tracked? Distinguish completion of planned milestones from delivery to intended users.
  • Does the schedule reflect resource availability? Consider whether testing, maintenance or transition activities extend across budget periods.

Conclusion

The FY2020 DHS S&T budget presents technology transition as an organizational and program-management challenge, not simply the final step after research. Its combination of R&D, systems engineering, testing, operational analysis, milestones and multi-year planning offers industrial automation decision-makers a useful framework for evaluating how innovations move toward use. The practical takeaway is to plan the path from requirement to validation and adoption from the outset, with appropriate responsibilities, measures and resources at each stage.

Access Official Technical PDF

About The Author