Access Official Technical PDF

Share Summary:LinkedInEmail

Patent eligibility is a distinct consideration for computer-implemented inventions, including technologies used in industrial automation. A claim may describe software or a process in detail and still raise a separate question: does the claimed subject matter qualify for patent protection under Section 101? In 2019 comments to the U.S. Patent and Trademark Office (USPTO), the High Tech Inventors Alliance (HTIA) argued that this eligibility analysis must not be confused with the disclosure requirements of Section 112.

That distinction is relevant when evaluating inventions involving control software, data processing, communications, and other computer-based functions. The comments addressed USPTO guidance rather than specific automation products, but their central message offers a useful framework: eligibility and disclosure answer different questions, and satisfying one does not automatically satisfy the other.

Patent eligibility asks what kinds of inventions can be protected

Section 101 defines the broad categories of subject matter that may be patented and excludes certain concepts, including abstract ideas, laws of nature, and natural phenomena. As HTIA explained, the purpose of this limit is not simply to assess whether an invention is new or described in detail. It is also to avoid granting exclusive rights over foundational ideas that others may need to use.

For computer-implemented claims, this creates an important distinction between claiming an abstract idea and claiming a technological application of one. The comments point to the contrast between an algorithm claimed by itself and a machine using an algorithm as part of a practical technological process. The concern is whether a claim would tie up the underlying idea broadly, rather than protect a specific technological implementation.

In an industrial setting, a claim involving software or data should therefore be assessed for what it actually contributes. Merely describing a business or organizational concept in computer terms may not establish eligibility. The analysis needs to consider whether the claimed subject matter is tied to a technical application, not just whether a computer appears in the claim.

Section 101 and Section 112 serve different roles

Section 112 addresses whether the patent application adequately describes and enables the invention it claims. In simplified terms, enablement concerns whether the disclosure teaches how to make and use the claimed invention across the claim’s scope. The written description requirement asks whether the application demonstrates that the inventor possessed what is claimed when the application was filed.

These requirements do not replace Section 101. HTIA used the example of a well-described activity that is not patentable subject matter: even if an application explains how to carry it out, that disclosure alone does not make the activity eligible. Applied to automation, a complete technical explanation of a software process cannot, by itself, resolve whether the claim is directed to eligible subject matter.

Keeping the standards separate helps applicants, examiners, and technical teams identify the right issue. A Section 101 concern is about the nature and scope of the claimed subject matter. A Section 112 concern is about the support and detail provided for the claim. A claim can raise either issue, both, or neither.

Why a computer in the claim may not be enough

HTIA supported the USPTO’s effort to organize Section 101 case law into categories of abstract ideas, while recommending clarifications. The comments said the categories should better capture not only mathematical concepts but also logic, data operations, data manipulation, and data itself. They also argued that the listed categories should be treated as examples rather than a complete list.

The submission also raised concerns about the guidance’s “practical application” analysis. HTIA recommended clarifying that ordinary meaning alone should not determine whether an abstract idea has been integrated into a practical application. It cautioned that adding generic computer components, arranged in a conventional way, should not automatically turn an abstract idea into an eligible invention.

For computer-implemented inventions, HTIA urged the USPTO to give greater emphasis to whether a claim improves the functioning of a computer or another area of technology. It described technological improvement as a particularly important indicator in relevant court decisions, while noting that it is not the only consideration. The practical implication for automation claim development is to identify the technical contribution precisely and explain how the claimed implementation relates to it, rather than relying on a computer or controller as a nominal element.

Disclosure should support the full scope of the claim

HTIA praised the USPTO’s Section 112 guidance for emphasizing that the full scope of a claim must be enabled. It recommended applying the same full-scope attention to written description: applicants should show possession of everything covered by the claim, not merely describe a narrower example.

This matters when claim language covers a range of implementations or functions. If a claim is broader than the disclosure, the application may not provide adequate support for that breadth. Technical and patent teams can reduce ambiguity by checking that key terms and claimed functions are grounded in the specification and that the disclosure supports the range of subject matter being sought.

The comments also addressed functional claiming under Section 112(f). They recommended that guidance explain how principles applied to means-plus-function claims generally also apply to step-plus-function claims. In method claims, examiners should look carefully for language that states a function without identifying the acts that perform it.

Practical steps for automation teams

These issues are best considered while the invention and its technical documentation are being developed. For teams working on computer-implemented automation inventions, useful review questions include:

  • What is the technical contribution? Identify the specific improvement or implementation, rather than describing only the desired result.
  • Does the claim rely on generic computing elements? Consider whether the claim explains a meaningful technical application beyond placing an abstract concept on a computer.
  • Does the specification support the claim’s full scope? Check that the disclosure describes and enables the range of implementations the claim covers.
  • Are functional limitations explained? For claims defined by a function, verify that the relevant acts or supporting structure are disclosed where required.

HTIA also encouraged examiners to use searches to identify claim terms that do not appear in the specification and to assess how guidance and training are applied over time. These recommendations underscore the importance of consistency: reliable examination depends both on clear standards and on careful application of those standards to the claim and disclosure.

Conclusion: treat eligibility and disclosure as separate reviews

For industrial automation inventions, patent eligibility and adequate disclosure are complementary but different tests. Section 101 asks whether the claimed subject matter falls within eligible technological territory; Section 112 asks whether the application sufficiently describes and enables what is claimed. A detailed specification cannot cure an eligibility problem, and an eligible concept still needs adequate support.

Separating these reviews can help engineering, operations, and intellectual property teams describe technical contributions more clearly and identify potential weaknesses earlier. The practical focus is to define the technological application, avoid relying on generic computer components as the sole point of distinction, and ensure the disclosure supports the complete scope of the claims.

Access Official Technical PDF

About The Author