Industries / Industrial equipment and services / IoT and industrial automation
Controllers
Controllers are the computers that read the sensors and decide, many times a second, what motors, valves and machines do.
5
Milestones achieved, from 1959 to 2025.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1959
A computer closes the loop
At Texaco's Port Arthur refinery in Texas an RW-300 computer achieved "closed loop control" of a polymerization process, adjusting it from its own measurements without a person in between. The Computer History Museum says the system increased operating efficiency and reduced catalyst replacement costs.
Credit
Texaco and Ramo-Wooldridge
1962
Computers replace the controllers
In direct digital control a central computer takes over from the separate thermostats and pressure controllers on each loop. Monsanto's ethylene plant and ICI's soda ash plant first tried this in 1962, according to the Computer History Museum.
Credit
Monsanto; ICI
1969
The programmable controller
Answering GM's 1968 request, DEC delivered its PDP-14 in June 1969 and Modicon its 084 in November 1969, each to replace relay panels on a gear-grinding machine. The Modicon was programmed in a language that looked like the relay ladder diagrams electricians already used; the PDP-14's programs sat in read-only memory and had to be sent back to DEC to change, and DEC faded from the business about two years later. About 2,000 PLCs were installed by around 1972, Control Engineering reports.
LessonA new controller spreads when it works the way its users already work; in Emmett's words, "it needed to emulate what was already in place.".
Credit
Dick Morley and the Modicon team; DEC; Dave Emmett of GM Hydra-Matic, who wrote the request
1993
One set of languages
The IEC published IEC 61131-3, which defines a common set of programming languages for PLCs, on 22 March 1993. Its fourth edition came out on 22 May 2025.
Credit
IEC technical committee 65, subcommittee 65B
2025
An open control system runs
An ExxonMobil resin finishing plant in Baton Rouge, Louisiana became, in Chemical Engineering's words, "the first commercial process-manufacturing facility to be controlled by an open, standards-based process automation system," with more than 100 controllers and 1,000 input and output points built to the Open Process Automation Standard (O-PAS), so parts can come from different makers. In September 2026 the site engineer reported that routine maintenance on a Windows virtual machine briefly cost an operator control of a console, and that the first major upgrade brought intermittent loss of console control; the industrial PCs used cost about $1,800 each against about $10,000 for a traditional controller.
LessonOrdinary computers in place of controllers bring ordinary computers' maintenance problems into the control room.
Credit
ExxonMobil, with Yokogawa as system integrator and the Open Process Automation Forum
Watch for
Virtual PLCs on car lines
A virtual PLC is a controller that runs as software on an ordinary server instead of in its own box. Siemens says its S7-1500V F, certified by TÜV, is "the first fail-safe virtual controller on the market," and that Audi has started integrating virtual controllers on its car-body line at Böllinger Höfe in Neckarsulm, Germany. ARC Advisory Group wrote in 2026 that such pilot deployments "do not yet represent high-volume production" and put the practical limit at 12 virtual PLCs per server.
Achieved whenAudi or an outside party reports virtual PLCs running a high-volume line, with downtime figures.
Claimed by
Siemens and Audi, March 2025, repeated on Siemens' site in 2026
Open control spreads
At the ARC Forum in February 2026 ExxonMobil's Whit McConnell said the company was deploying a new open control system to a tank farm at its Baton Rouge Anchorage Chemical Terminal "with no issues," and that a project in India had started, with deployment expected in 2027.
Achieved whenan outside party reports these systems in operation, ideally after a part from one maker has been swapped for another's.
Claimed by
ExxonMobil, February 2026
Open
01
Move old programs, prove them
An AI pipeline that translates a PLC program from one maker's format to another's and then proves with a model checker, a program that explores every possible sequence of inputs, that the two versions give the same outputs, or else returns the input sequence where they differ.
The briefCredit · unclaimed02
Virtual PLCs per server
An outside load test that runs more and more virtual PLC instances on one server, each exchanging data with simulated input and output devices over PROFINET at a 1 ms cycle, with a logic analyzer timing their outputs, to find how many hold their cycle with no missed deadline.
The briefCredit · unclaimed
Open 01 · the brief
Move old programs, prove them
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An AI pipeline that translates a PLC program from one maker's format to another's and then proves with a model checker, a program that explores every possible sequence of inputs, that the two versions give the same outputs, or else returns the input sequence where they differ.
Why it is still open
Migration tools "often rely on static instruction mappings that require extensive manual correction," a May 2026 preprint from the University of Houston and Cornell University says. Its own AI pipeline translated one Rockwell shift-register program to Siemens with 396 of 437 elements (90.6%) correct, judged by a similarity score, not a proof. ABB researchers presented a behavioural equivalence check for PLC software upgrades in 2025, not for translations between makers.
Built with what exists
PLCverif, CERN's open-source verifier for PLC programs, which reads Siemens STEP 7 code; makers' export formats such as Rockwell's L5X files; OpenPLC, an open-source PLC runtime, to replay recorded inputs; AI coding agents to write translations and proof harnesses (see the Note "Proven in four weeks"). AI agents that help a few people write proofs about real code are what bring this within reach of a small team.
First step
Take one published sample program, translate it to Structured Text, and get PLCverif to prove that one input-output property holds in both versions.
Done looks like
Ten real programs of at least 500 rungs each, translated between two makers, each published with an equivalence proof or a counterexample, and at least eight proved equivalent without hand edits.
Open 02 · the brief
Virtual PLCs per server
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An outside load test that runs more and more virtual PLC instances on one server, each exchanging data with simulated input and output devices over PROFINET at a 1 ms cycle, with a logic analyzer timing their outputs, to find how many hold their cycle with no missed deadline.
Why it is still open
Published outside measurements cover one or two instances: an October 2025 workshop paper by Florian Hofer and Riccardo Venanzi ran two containerized virtual PLCs sharing one network port and reported jitter under 3 microseconds on tuned edge devices. ARC's limit of 12 per server is an analyst's figure, not a published test.
Built with what exists
CODESYS Virtual Control SL, the OpenPLC runtime and, with a licence, Siemens' S7-1500V; a server running a real-time Linux kernel; a logic analyzer; Wireshark to timestamp network frames.
First step
Run one OpenPLC instance in a container on a real-time Linux PC, toggle an output every cycle, and record its jitter with a logic analyzer for 24 hours.
Done looks like
For each product, the largest number of instances that ran for 72 hours at 1 ms with zero missed cycles, published with the timing histograms and test scripts.