Turn "requirements + process notes + I/O table" into Siemens SCL code automatically — a 10× lever for electrical engineers.
About this page
This page describes the architecture and capabilities of the SCL Agent design. No real factory or customer process details, variable tables, or production code are shown. During MVP / V1 stages, every AI-generated SCL must be reviewed by a qualified electrical engineer before being deployed to a production PLC — a non-negotiable industrial-safety boundary.
What the agent takes off people's plates
Planning (Qwen2.5-72B) + code generation (DeepSeek-Coder-V2) + review (Qwen2.5-Coder-32B). Three models, each in its lane — beats any single-model attempt.
Language layer (SCL syntax + IEC 61131-3) / Template layer (motor, valve, PID, sequential, safety FBs) / Convention layer (variable prefixes, FB numbering, comments). The template layer is the moat.
Static syntax check (ANTLR4 + SCL grammar, milliseconds) → LLM logic review (refs / types / FB calls / interlocks) → auto-repair loop (5 rounds max, then escalate to human).
I/O tables are parsed deterministically into JSON (var_name / data_type / address / direction) before reaching the LLM. Anything code can do deterministically must not be left to the model.
Linux/Mac core + Windows Agent + Siemens Openness API. Always start with "export .scl + manual import" as a safety net; transactional rollback protects the TIA project; full auto-write to program blocks comes last.
MVP / V1 require mandatory engineer review. Phase gates (syntax / logic / first-pass rates) are hard requirements — no automation advance until they are met. Out-of-bound cases are fully logged to refine the template library.
Quantified before / after
Subjects and capability matrix
MVP
Syntax >90% · 1st-pass >60%
V1
Logic >85% · 1st-pass >75%
V2
Fine-tune + full auto-link
V3
Self-improving · quarterly delta
How the agent and human supervision collaborate
human
Engineer review
Flow