Engineering Compiler · Part of the IQ Platform

Your IO list compiles into a PLC scaffold
verified at every checkpoint.

ScaffIQ ingests IO lists, P&IDs and functional descriptions and compiles them into structured Rockwell L5X tag and AOI scaffolding, ready for Studio 5000. Three checkpoints stand between the parsed data and the compiled file. Sequence Engine can generate rung and sequence logic as a separate, optional, reviewed step.

Get Started → See How It Works
L5X / Studio 5000
Rockwell ControlLogix / CompactLogix now
Beckhoff, Schneider and Siemens coming soon
Runs standalone or from FDSIQ
scaffiq-compiler
Checkpoint 3 of 3
Confirmed loop
equipmentId: CONV014
detectedDeviceType: Motor DOL
selectedAoi: Motor_DOL_v2
Compiled output
<Tag Name="CONV014"
TagType="Base" DataType="Motor_DOL_v2"/>
<Tag Name="CONV014_RUN"
TagType="Alias" AliasFor="Local:3:I.Data.1"/>
214 tags · 38 AOI instances L5X ready
The problem

Scaffolding a PLC project by hand is slow and every shortcut is a liability.

Tag structures and AOI instances get built manually, from memory, against whatever IO list format showed up this time. Nothing checks the work before it reaches Studio 5000.

Five IO list formats, one deadline
Excel, CSV, a scanned PDF, a Word FDS. Every project starts with re-keying someone else's format into yours.
AOI mapping done from memory
Which AOI matches this device type is a judgment call made under time pressure, project after project, with no cross-reference to catch a mismatch.
No sign-off trail before code ships
Once a tag structure is built, there's usually no record of who approved the IO mapping before it was compiled into the controller.
How it works

Nothing compiles until three checkpoints clear it.

ScaffIQ parses your documents client-side, then routes the result through three sequential engineer sign-offs before anything is compiled.

IO Mapping Review
Every tag, address and description ScaffIQ identified from your IO list, P&ID and functional description, cross-referenced three ways: exact match, normalised and fuzzy. Confirm or correct before anything moves forward.
AOI Mapping Review
Signals are grouped into equipment loops and matched against your Add-On Instruction library. You confirm the AOI for each loop before a single tag is generated.
Output Review & Legal Gate
Task architecture is set, the engineer of record is named and safety content is flagged for explicit acknowledgement. Nothing compiles until this gate is passed.
What never leaves your machine
Document parsing is client-side
IO lists, P&IDs and FDS files are parsed entirely in your browser before any data is transmitted.
Only the abstracted payload is sent
What reaches the compiler is a structured, normalised description of confirmed loops, not your source documents.
No AI writes your logic
ScaffIQ's base scaffold compiles tag structures, AOI instances and routine placeholders only. Sequence Engine can generate real rung and sequence logic as a separate, optional step, deterministically, never by AI, always reviewed and signed off by the engineer of record before use. See real generated output →
What actually leaves your browser

Not an assertion. Here's the shape of it.

Your IO list, P&ID and FDS files are parsed by your browser's own JavaScript, never uploaded as files. Once you confirm a loop at Checkpoint 1 and 2, this is the entire, real shape of what gets sent, nothing else.

Your browser
IO list, P&ID, FDS files
parsed and never leave
→
Confirmed loops
Only what you signed off
at Checkpoints 1 & 2
→
ScaffIQ compiler
Compiles the L5X scaffold
{
  "confirmedLoops": [{
    "equipmentId": "CONV-014",
    "detectedDeviceType": "Motor DOL",
    "selectedAoi": { "name": "Motor_DOL_v2", "parameters": [ ... ] },
    "signalMappings": [{
      "signalTagName": "CONV014_RUN",
      "aoiParameterName": "Run",
      "signalType": "Digital Input",
      "hardwareAddress": "Local:3:I.Data.1"
    }]
  }]
}

This is the real request shape, not a mockup. Your original IO list, P&ID and FDS files, and everything you didn't confirm, are never part of it.

Beyond the scaffold

Two optional engines, each reviewed the same way.

Sequence Engine and Perspective Engine build on the same confirmed loop data from your three checkpoints. Both are additive: decline either one and your compiled L5X scaffold generates exactly as it always has.

ScaffIQ Sequence Engine
Real sequence logic, not just scaffolding
Sequence Engine goes beyond tag structures: state machine transitions, interlock conditions and alarm comparison rungs, generated directly from your confirmed I/O mapping and AOI selections. Open Studio 5000 to a project that already reflects how your process runs, with every rung ready for you to validate against your Functional Design Specification. It's a separate, optional step with its own review and sign-off, the base scaffold is unaffected either way.
ScaffIQ Perspective Engine
Ignition Perspective 8.3 Only
A ready-made symbol library for Ignition
Perspective Engine builds a complete library of reusable Perspective symbols for your devices, motors, pumps, valves, sensors and instruments, and places every confirmed device on a ready-to-use overview page, already labelled for your project. Built for Ignition Perspective 8.3, not earlier versions. Open Designer to symbols and layout already in place, ready for you to connect to live tags. It's a separate, optional step with its own review and sign-off: structure and layout only, live tag connections are yours to make.

Both engines follow the same pattern as ScaffIQ itself: you confirm, adjust or override what's proposed at every step. The sign-off stays yours.

The IO Platform

Runs standalone. Compiles faster from FDSIQ.

ScaffIQ takes a confirmed IO list directly, or a structured export from FDSIQ. Either way, the same three checkpoints apply.

FDSIQ
Structured FDS
JSON export
→
SCAFFIQ
3-checkpoint compiler
Tags · AOIs · L5X

Don't use FDSIQ? Upload your IO list, P&ID and FDS directly. ScaffIQ runs on its own.

Pricing

Priced per project. No subscription.

One flat price per project, whatever package you need.

ScaffIQ
$1,595
AUD per project
  • I/O framework and tag declarations
  • Runs on your own structured input
  • Full L5X export, ready for Studio 5000
Get started →
FDSIQ + ScaffIQ
$2,150
AUD per project
  • Everything in ScaffIQ
  • Structured 10-step FDS wizard
  • AI validation engine, locked revisions
Get started →
ScaffIQ + Sequence Engine
$4,620
AUD per project
  • Everything in ScaffIQ
  • ScaffIQ Sequence Engine included
  • No FDSIQ required
Get started →
The Works
$5,175
AUD per project
  • Everything in FDSIQ and ScaffIQ
  • ScaffIQ Sequence Engine included
  • Perspective Engine available, priced by device count
Get started →

Compare all packages and full FAQ →

User Specs & Requirements

What you need to run ScaffIQ.

Nothing to install. ScaffIQ runs entirely in the browser.

Modern browser
A current version of Chrome, Edge, Firefox or Safari. JavaScript and cookies must be enabled, both are required for sign-in and for the compiler itself.
Reliable internet connection
25 Mbps or faster recommended. Parsing, checkpoints and compilation are all live calls, there is no offline mode.
Studio 5000, for opening the output
ScaffIQ produces a real .L5X file. Opening, reviewing and downloading it into a live project needs Rockwell's own Studio 5000, ScaffIQ does not include a substitute.
A credit card with sufficient available funds
The project licence fires once, on your first compile. Held on file via Stripe, charged automatically, no manual invoice step.
A desktop or laptop screen
The checkpoint review screens, with their tag mappings and AOI tables, are built for a real screen. They are not optimised for a phone.
Qualified engineers only
ScaffIQ is built for qualified engineers (Controls, Process Control, Systems Integration, EI&C or Applications), not as a substitute for one. The Engineer of Record must review and authorise every generated output before it reaches a live system, accepting full professional responsibility for the result.

Compile your PLC scaffolding
instead of building it by hand.

Three checkpoints stand between your IO list and a compiled L5X file. All three run, every time.

Get Started →