Access Official Technical PDF

Share Summary:LinkedInEmail

Patent eligibility for industrial automation can turn on how an invention is described in its claims—not simply on whether it uses computers, sensors or networked equipment. In decisions following the U.S. Supreme Court’s 2014 Alice ruling, courts repeatedly questioned claims framed as collecting, analyzing, organizing or displaying information when they relied on generic technology to perform those activities. Several cases involving industrially relevant systems illustrate the issues engineers, integrators and technology decision-makers should watch for.

What post-Alice eligibility decisions examined

The cases summarized through March 1, 2019 apply the patent-eligibility analysis associated with Alice. In the decisions described, courts asked whether claims were directed to an abstract idea and, if so, whether they included an inventive concept beyond implementing that idea with conventional components. A computer, server, database or sensor did not, by itself, resolve the question.

This distinction matters in automation because many systems gather signals, process them and present results. Those functions are central to monitoring and control, but broad claims that state the outcome without explaining a technical means of achieving it may be vulnerable. The decisions do not establish that data-oriented automation inventions are categorically ineligible. Rather, they show how the courts assessed the particular claims before them.

Patent eligibility for industrial automation: relevant cases

Power-grid monitoring and sensor data

In Electric Power Group, LLC v. Alstom S.A. (2016), the Federal Circuit considered claims for real-time performance monitoring of an electric power grid. It characterized the claimed activity as collecting information, analyzing it and displaying results. The court found the claims ineligible because they required only conventional, generic technology.

A similar concern arose in TDE Petroleum Data Solutions, Inc. v. AKM Enterprise, Inc. (2016), which involved sensor-data processing. The court described the claims as storing, gathering and analyzing data, and found that generic computer functions did not provide an inventive concept. These cases are pertinent to industrial monitoring applications: describing a useful data-processing objective is not necessarily the same as claiming a specific technical improvement in how the system performs it.

Inventory control and information processing

In Automated Tracking Solutions, LLC v. The Coca-Cola Co. (2018), the claims concerned inventory control. The Federal Circuit described them as collecting sensor data, analyzing it and determining results from that analysis. It concluded that generic computer components used to carry out those steps did not make the claims eligible.

The reasoning is a reminder to examine what the claim says about the system’s operation. Naming a sensor or an inventory application may identify the setting, but the cited decision focused on whether the claimed steps added more than the data-handling idea itself. For technical teams assessing an invention, the relevant question is whether the claims articulate a concrete technical approach, rather than only the desired information or business result.

Why claim detail and context matter

These rulings should not be read as a rule that automation software cannot be patented. The chart also records a different outcome in Data Engine Technologies LLC v. Google LLC (2018). The Federal Circuit held that claims for navigating three-dimensional electronic spreadsheets were not directed to an abstract idea, describing a specific navigation method that improved computer use. By contrast, claims about tracking spreadsheet changes were found ineligible as they recited generic steps for creating versions and identifying changes.

The comparison underscores the importance of reading claims as a whole. Two claim sets associated with the same general application can be treated differently when one describes a specific method and the other states familiar information-processing steps. For automation inventions, technical documentation and claim drafting should make the claimed method understandable: what is being processed, how the system processes it, and what the claims identify as the technical contribution.

Procedure can matter, too. In Berkheimer v. HP Inc. (2018), the Federal Circuit said that although eligibility is ultimately a question of law, underlying factual questions may arise. It remanded some claims because whether they provided an inventive concept presented a factual issue. The decision does not mean that every eligibility challenge requires a trial; the chart also describes cases resolved at the pleading stage. It does show that the factual basis for characterizing components or steps as conventional can be significant.

Practical implications for automation teams

Engineers and technical decision-makers evaluating potential patent filings can use these cases as prompts for discussion with patent counsel. Consider whether a proposed claim:

  • Describes a specific technical method, rather than only the goal of monitoring, analyzing or controlling a process.
  • Explains the role of sensors, computing components or data flows beyond naming generic equipment.
  • Identifies how the claimed approach differs from routine data collection, processing or presentation.
  • Is supported by technical documentation that clearly describes the claimed operation and any asserted improvement.

These are practical review questions, not guarantees of eligibility. The decisions summarized here concern particular claims and records, and the chart reflects cases available as of March 1, 2019.

Conclusion

Post-Alice decisions involving power grids, petroleum sensors and inventory systems show that industrial relevance alone does not settle patent eligibility. Claims focused on collecting, analyzing and displaying data with conventional technology faced challenges, while a specific computer-navigation method received a different result. For automation organizations, the practical lesson is to explain the technical method with precision and assess the claims—not just the application’s purpose—with qualified patent counsel.

Access Official Technical PDF

About The Author