About ControlCurve

ControlCurve publishes an independent, regularly revised maturity map for industrial control, automation and instrumentation, covering field instrumentation, field control devices, DCS/PLC/ESD/HMI control systems, and the industrial IT/OT and critical control information infrastructure that connects and protects them.

Why this exists

Engineering, operations and technology leaders in process and discrete industries are asked to place bets on emerging technology constantly — which field-network standard to specify on a new project, whether a virtualised DCS is ready for a control-critical loop, how urgently to invest in OT-specific cybersecurity architecture. Vendor marketing rarely distinguishes a technology that is genuinely production-ready from one still years from a defensible business case. ControlCurve exists to make that distinction explicit, sourced, and revisited on a fixed schedule rather than left to marketing cycles.

Editor

Eben Wassermann, founder and editor

Eben Wassermann founded ControlCurve and researches, writes and edits its analyses. He is responsible for every stage placement and time-horizon estimate on the site, and for corrections when the evidence changes. You can reach him through the contact page.

Methodology

Every technology tracked on this site gets two separate ratings: a stage on the ControlCurve, which compares the attention a technology receives with the results it has delivered, and an evidence level, which records how much deployment proof exists. Both are built from evidence a reader can check:

Shipped products and documented deployments, not roadmap announcements alone;
Standards-body milestones (IEC, IEEE, ISA, OPC Foundation, FieldComm Group, NIST and others);
End-user test results and case studies, which carry more weight than supplier claims;
Independent analyst and trade-press reporting, cross-checked where figures conflict.

Where a figure comes only from a supplier or its customers, the full analyses say so. Where published accounts disagree, we report the disagreement rather than pick the more flattering number.

What the five stages mean

Emerging Idea: A working concept and early demonstrations, but few or no production deployments. Evidence comes mainly from pilots, research and supplier roadmaps.
Over-Promise: More supplier and media attention than the deployed base justifies. Products exist and early adopters are live, but independent evidence of results is thin.
Reality Check: Early projects under-delivered or uptake has been slower than forecast. What remains is being re-scoped around the uses that work.
Industry Acceptance: Repeatable reference deployments and a reasonably understood business case. The open questions are about integration, cost and scale rather than whether the technology works.
Proven in Use: Mainstream: specified routinely, limits well known, supported by a broad supplier base.

How to read the map

The stage, the time-to-proven-use horizon and the evidence level are the parts of the map that reflect our research, and all three are stated explicitly so they can be checked against later evidence. The curve's vertical height is different in kind: it is a fixed reference shape, showing attention rising, falling back and recovering as results arrive, drawn once and mathematically smoothed through a set of keypoints, then sampled at each technology's horizontal position to place its marker. It is not a per-technology score, and it should not be read as ranking one technology "higher" or "lower" than another in importance, benefit or hype — only left-to-right position, the stated time horizon and the evidence level carry that meaning.

Evidence levels

The stage says how a technology's reputation compares with its results; it does not say how much proof exists. A technology can be heavily over-promised while already running in a few plants, or quietly proven while attracting little attention. The evidence level records the proof on its own five-step scale, loosely modelled on the public Technology Readiness Level idea (developed by NASA and standardised in ISO 16290) but measuring deployment in the field rather than engineering readiness:

E1Concept. Laboratory, prototype or supplier demonstrations only.
E2Field pilot. Pilots or trials at operating sites; no confirmed production use.
E3First production use. In production at one or a few named sites, usually with one supplier or integrator.
E4Multi-site references. Repeated production deployments by several owners, with more than one supplier.
E5Routine specification. Specified as normal practice, with a broad supplier base and international standards in place.

A level is raised only when public evidence for the higher level exists: a named site, a published test, a standard. Supplier claims of customer counts on their own do not move an entry up a level.

The AI & machine learning cross-section

AI and machine learning are deliberately not tracked as a fifth category. In practice, AI-driven mechanisms show up inside all four existing categories — edge-AI transmitters and soft sensors in field instrumentation, computer-vision inspection in field control devices, agentic process control and diagnostic copilots in control systems, federated learning and AI-driven anomaly detection in IT/OT/CCII — and siloing them into their own box would misrepresent how the technology is actually being deployed. Instead, every entry whose core mechanism is AI- or ML-driven carries a cross-cutting tag: it stays filed under its natural category, and is additionally surfaced on the homepage chart as a dashed accent ring around its marker, in its detail panel and directory card as an "AI/ML" tag, and can be isolated on its own with the AI & ML cross-section toggle above the chart. As of this edition, 17 of the 50 tracked technologies carry this tag.

Full analyses and short entries

The site has two kinds of technology page. Full analyses cover the entries closest to practical use, those with a current or near-term time to proven use. Each one explains how the technology works and where it does and does not pay, gives a dated evidence timeline, sets out why it sits at its stage and which adoption signals would move it, lists questions to ask before committing, and links every key fact to a public source. Short entries summarise the placement of the remaining technologies. They are kept for readers browsing the curve but are not yet offered to search engines, and they carry no advertising until they are expanded into full analyses.

Review cycle and corrections

The full set is reassessed at least twice a year, and individual entries are updated when material new evidence appears: a standard published, a product shipped, a deployment publicly disclosed. Each full analysis shows the date it was last updated. If you think a placement or a fact is wrong, tell us and include a source if you can; corrections that change a placement are recorded below.

Change log

October 2026 edition

Replaced the borrowed hype-cycle terminology with ControlCurve's own five stages (Emerging Idea, Over-Promise, Reality Check, Industry Acceptance, Proven in Use) and added an evidence level (E1 to E5) for every technology.
Published full, sourced analyses for eighteen technologies with a current or near-term time to proven use: thirteen on 15 October and five more (cloud SCADA, smart electric actuators, distributed fibre-optic sensing, Zero Trust for OT and LEO satellite connectivity) on 16 October.
Added a "Disagree with this placement?" box to every full analysis, so readers can challenge a stage or evidence level with a source.
Smart electric actuators and LEO satellite connectivity moved from evidence level E4 to E3: production use is real, but published multi-owner results are scarce, and supplier material alone does not raise a level.
IO-Link moved from the Industry Acceptance stage to the Proven in Use stage, reflecting about 71 million installed nodes and IEC standards for its wireless and safety extensions.
TSN with OPC UA FX moved from the Industry Acceptance stage to the Reality Check stage, with the time horizon changed from near-term to mid-term. The previous text overstated product availability: the industrial TSN profile was only published in June 2026, and controller-to-device OPC UA FX profiles are not yet specified.
Private 5G moved from the Industry Acceptance stage to the Reality Check stage. A previously quoted figure of around 2,000 industrial deployments could not be verified and has been removed.
Autonomous inspection robots and AI-driven APC moved earlier within the Industry Acceptance stage, because the public evidence is thinner than the previous text implied.
Removed an unverifiable reference to analyst reports, and corrected the reasoning on the agentic AI for process control entry, which contradicted its own placement.

September 2026 edition

First edition: 50 technologies across four categories.

Independence & disclosure

ControlCurve is editorially independent. This site displays advertising, including Google-served ads, which may be personalised in line with the Privacy Policy. Advertising placement does not influence which technologies are tracked or how they are staged. Where a specific vendor or product is named, it is cited as a public source or representative example, not as a paid placement, unless explicitly marked as sponsored content.

The general pattern of early enthusiasm, disappointment and gradual adoption has been described by many analysts, most famously in the hype-cycle concept popularised by Gartner, Inc. ControlCurve's stages, evidence levels and placements are its own, and ControlCurve is not affiliated with Gartner.