Turn your Excel taglist into a complete PLC project with SCADA tags and alarms, all from one version-controlled library. Then test it against a simulated process with the DigitalTwin. Built for Rockwell today, with a Siemens TIA Portal pilot under way.
Every project starts with the same routine. Hours of error-prone copy-paste work that should never be human work.
From Excel taglist to a tested controller project, all from one launcher.
The real value isn't just generating code — it's enforcing naming standards, CM libraries, S88 structures, tag consistency and HMI mapping across every project, automatically.
The DigitalTwin connects to a Logix controller or Studio 5000 Logix Emulate over EtherNet/IP. It reads the controller's outputs, runs a process model and writes back simulated sensor values, so your code runs against a live process before commissioning.
PlantCode Studio generates the program structure, CM calls and I/O mapping. Mode procedures, interlocks and sequences are project-specific and written separately. We're piloting a coding agent that drafts this logic as overlay programs.
Running on the rewrite of an existing production line, with around 1,000 rungs of process logic. A merged controller build verifies in Studio 5000 with no errors. The code hasn't been commissioned yet, so the pilot hasn't proven it on a running plant.
Logic is defined once as vendor-neutral library data and rendered per target. PLC and SCADA platforms are selected independently. Output is ladder by default.
Siemens pilot status. Not yet for production use. Data types and function blocks compile without errors in TIA Portal V20. The first full import on TIA Portal V21 is the next acceptance check.
What it doesn't do. PlantCode Studio generates files you import into your vendor's engineering tools. It doesn't replace Studio 5000 or TIA Portal, and it doesn't generate HMI graphics.
PlantCode Studio is currently in private beta. Built for automation engineers, by an automation engineer.