Qualified Research

Can Process-Control System Development Qualify as R&D?

Process-control system development may constitute qualified research when the work evaluates alternative control approaches to resolve a technical uncertainty about control performance. Deploying commercially available control systems in known applications generally is not qualified research.

A common question from manufacturers is whether process-control system development can qualify as research and development for the federal R&D tax credit under Section 41. The short answer is that process-control system development may constitute qualified research when the work evaluates alternative control approaches to resolve a technical uncertainty about control performance. Deploying commercially available control systems in known applications generally is not qualified research. This page explains the framework in general terms. It is educational and is not individualized advice. For the foundational framework, see our page on qualified research.

When Process-Control Development May Warrant Review

Process-control system development may warrant review when the work involves a genuine technical uncertainty and a process of experimentation. Under the four-part test, the work must be for a permitted purpose, be technological in nature (relying on engineering or computer science), be intended to eliminate uncertainty, and be conducted through a process of experimentation.

Common scenarios that may warrant review include:

  • Control algorithm development — evaluating alternative control algorithms to resolve uncertainty about whether a control system can achieve the required process stability or response.
  • Feedback loop development — testing alternative sensor configurations or feedback approaches to resolve uncertainty about whether a control system can maintain the required performance.
  • Multi-variable control — evaluating alternative control strategies to resolve uncertainty about whether a system can control multiple interacting variables.
  • New process control — testing alternative control approaches to resolve uncertainty about whether a new process can be controlled to the required performance.

Standard Deployment vs. Control Development

A central distinction is between deploying standard control systems and developing new control systems:

  • Standard deployment — purchasing and configuring a commercially available control system (e.g., a standard PLC with established programming) for a known application. There is no technical uncertainty about whether the system will work. This is deployment, not research.
  • Control development — developing a new control system or significantly modifying an existing one where there is a technical uncertainty about whether the system can achieve the required performance, and evaluating alternatives to resolve that uncertainty. This may warrant review.

Internal-Use Software Considerations

Where the control system includes software developed primarily for the taxpayer's internal use, the internal-use software rules under Section 41(d)(4)(E) and Treasury Regulation §1.41-4(c)(6) may apply. Software developed to enable a non-software business component (e.g., a manufacturing process) may warrant review under the excepted-software rules. The analysis is fact-specific.

Hypothetical Example

Consider a manufacturer that is developing a new process-control system for a new process with complex thermal dynamics and is uncertain whether any available control algorithm can maintain the required temperature stability. The company evaluates alternative control strategies (PID, model predictive control, adaptive control), tests each through simulation and physical trials, and systematically varies the approach to resolve the uncertainty. This systematic evaluation of alternatives may warrant review as qualified research.

By contrast, if the same manufacturer deploys a standard PLC with established programming for a known process, that is standard deployment, not research.

This example is illustrative only and does not state that the activity definitely qualifies.

Documentation That May Help

Records that can help support process-control development claims include control system design records identifying the uncertainty and alternative approaches, control-performance test results, simulation records, and records of how results informed control design decisions. For more, see our page on R&D tax credit documentation.

Key Takeaway

Process-control system development may constitute qualified research when the work evaluates alternative control approaches to resolve a technical uncertainty about control performance. Deploying commercially available control systems in known applications generally is not qualified research. Because the distinction is fact-specific, professional review is appropriate before claiming the credit.

Sources

  1. Treasury Regulation §1.41-4

    Cornell Law Institute (LII)

    Defines the process of experimentation and the internal-use-software rules in §1.41-4(c)(6).

  2. Internal Revenue Code §41

    Cornell Law Institute (LII)

    Section 41(d) defines qualified research; §41(d)(4)(E) addresses internal-use software.

  3. Instructions for Form 6765

    Internal Revenue Service

    Summarizes qualified research and excluded activities.

  4. Research Credit

    Internal Revenue Service

    IRS landing page for the Credit for Increasing Research Activities.

By R&D Ledger Editorial Team

Last reviewed: August 2026

Related educational pages

R&D Ledger

Organize your R&D documentation throughout the year.

Explore R&D Ledger