PlantCode Studio 4 — Private Beta

Generate PLC & SCADA
projects automatically.

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.

PLC Generator
SCADA Generator
Phase Editor
DigitalTwin
PlantCode Studio dashboard: tools grouped by stage next to the S88 structure of an open project
// The Problem

Industrial automation engineering
is still largely manual.

Every project starts with the same routine. Hours of error-prone copy-paste work that should never be human work.

∞
Inconsistency across projects
Every engineer has their own style. Every project drifts from the standard. Maintenance becomes archaeology.
0
Automated testing for PLC logic
AOI behavior is verified manually, one signal at a time. Bugs hide until commissioning.
3×
Effort when requirements change
Add a field, rename a tag — propagate through PLC, SCADA, and documentation. Manually. Everywhere.
9
Integrated tools
1,800+
Automated tests
L5X
Native Rockwell output
S88
ISA-88 structure
YAML
Version-controlled source
TIA
Siemens pilot under way
// How It Works

One platform. Four stages.
Full stack.

From Excel taglist to a tested controller project, all from one launcher.

01 — Define
Import & Structure
Excel Taglist Import
Turn your taglist into one project file: S88 structure, CM instances and tag names.
CM Type Viewer
Browse the control module library and preview the rendered L5X for any AOI.
Tag Browser
Browse and pick tag expressions from a project.
02 — Configure
Wire Sequences
Phase Editor
Build ISA-88 phases and operations: steps, actions and transitions, generated as ladder.
S88 Type Editor
Define UDT templates for Process Cells, Units, Equipment Modules.
03 — Generate
Compile & Export
Project Manager
Generate the PLC controller, the SCADA files or both, as numbered builds.
Overlay Merge
Check externally written programs and merge them into the generated controller.
ACD Builder
Convert a generated L5X to .ACD through the Studio 5000 SDK.
TIA Import (pilot)
Import a generated Siemens build into TIA Portal through Openness.
04 — Test
Validate Before Commissioning
DigitalTwin
Run a process model and fault scenarios against a real or emulated Logix controller.
Co-Execution Harness
Library AOIs run against their reference ladder and are compared tag by tag, every scan, with no PLC.
// Key Features

Standardize your PLC architecture
across every project.

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.

Enforce Standards Across Projects
Define your naming conventions, CM library and tag structures once. Naming profiles validate imported taglists and derive CM types from tag codes, so every project follows the same standard.
ISA-88 Native
Built around the S88 hierarchy: Process Cell, Unit, Equipment Module, Control Module. Each S88 node becomes its own program, with phases and operations on top.
Rockwell L5X Output
One complete, numbered controller L5X that imports into Studio 5000 with zero errors: UDTs, AOIs, tags and ladder programs. Targets v35 and v36+, including the IEC mnemonic set.
Proven Library Logic
Each ported AOI runs in a software simulator against its reference ladder on the same inputs, compared tag by tag on every scan. No AOI ships until they match, and no PLC is needed.
SCADA Tags and Alarms
A FactoryTalk View ME tag database, alarms and trend and datalog helpers from the same project, or an alarm import for a FactoryTalk Alarms and Events server. Graphics stay in your SCADA editor.
Excel Import
Start from the spreadsheet you already have. An imported taglist becomes a complete project, without changing how you collect your equipment and tag data.
YAML as the Source of Truth
One readable project file and a version-controlled library, with no per-project database. Every change shows up as a clean diff in git.
As-Built Hardware Import
Export the controller from Studio 5000 and its real I/O tree is carried, byte for byte, into every generated project. Hardware configuration stays where it belongs.
Overlay Merge
Process logic written by hand or by AI merges into the generated controller, with one owner per routine. A published contract and a checker catch mismatches first. Rockwell targets.
// PlantCode Studio DigitalTwin

Test before you
touch the plant.

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.

Fault Injection Scenarios
Switch on stuck sensors, sensor failures, overshoots and contamination events while the logic runs, or override any instrument by hand.
Models You Can Edit
Define sensors, behaviour rules and fault scenarios in the built-in editor, picking sensors from your project's control modules. Models are saved as YAML with the project.
Available as Standalone
Launch the DigitalTwin from the Studio launcher or on its own. Use it for acceptance testing, operator training and regression testing logic changes.
PlantCode Studio DigitalTwin with its PLC connection, instruments table and fault scenarios
// PlantCode Studio DigitalTwin — Instruments and Fault Scenarios
// AI Pilot

Process logic,
drafted by AI.

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.

01 — Brief
Spec and contract
The agent works from the functional spec and the controller contract, which lists the programs, routines, UDT fields, CM instances and AOIs the generated controller exposes.
02 — Draft
Ladder overlays
It writes the process logic as ladder, with one L5X export per program, in the same form an engineer would export from Studio 5000.
03 — Check
Contract check
The overlay checker tests each export against the contract and reports mismatches before anything is merged.
04 — Verify
Merge and review
Overlay Merge builds one complete controller. It's then verified in Studio 5000, and engineers review the logic and behaviour choices.
Pilot

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.

// Targets

One library.
Vendor chosen at generation.

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.

PLC
Rockwell Studio 5000 v35 and v36+
Complete controller L5X, optionally converted to .ACD
Supported
PLC
Siemens TIA Portal V21, S7-1500
PLC data types, SCL function blocks, data blocks and ladder, imported through Openness
Pilot
PLC
Beckhoff TwinCAT
Follows the Siemens approach
Planned
SCADA
FactoryTalk View ME
HMI tag database, alarms, trend and datalog helpers per S88 unit
Supported
SCADA
FactoryTalk Alarms and Events
Alarm import for the alarm server of a View SE application
Supported
SCADA
Siemens WinCC
On the roadmap
Planned

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.

// Early Access

Ready to ship faster?

PlantCode Studio is currently in private beta. Built for automation engineers, by an automation engineer.

// Early access signup opening soon — plantcodestudio.eu