For PLC and controls engineers
FDSIQ structures the spec from your input.ScaffIQ compiles the PLC code and SCADA symbols from it.
Your confirmed tags, equipment and sequences become I/O, ladder logic and Ignition symbols. Nothing gets retyped into Excel, Studio 5000 or Ignition.
- Interlock rungs trace back to the tag pair they enforce
- Runs in your browser. Pay per project.
Already have an I/O list? Start with ScaffIQ scaffolding
| Tag | Description | Type |
|---|---|---|
| P_101 | Feed pump | Motor |
| XV_101 | Inlet valve | Valve |
| LT_101 | Tank level | Analog in |
Traced to tag pair XV_101
Overview
Define it once. Compile it everywhere.
Accurate · Efficient · Fast · Reduce rework
ScaffIQ compiles accurate I/O and tag declarations on its own. FDSIQ takes it further: capture the whole design once, get back the corporate .docx FDS your clients expect, plus the structured JSON every downstream product compiles from automatically.
FDS input (structured)
Equipment: CONV-014 Signal: Zone_3_Overrun Type: Digital Input Function: Overrun trip, zone 3 conveyor
ScaffIQ output
Tag: CONV014_ZN3_OVRN_DI AreaModel: /Line2/Conveyors/CONV-014 AlarmClass: Trip
The problem
Word documents drift. Tags get defined three times.
The I/O list lives in Excel. The sequence lives in Word. The interlock matrix is its own tab. None of them are linked. A tag renamed on page 12 is still the old name on page 47, and in the PLC program. Revision B overwrites Revision A, so there’s no immutable record of what was actually agreed.
Before
I/O list in Excel. Sequence in Word. Interlock matrix in a separate tab. Nothing linked, nothing validated.
After
Structured unified record. Tags defined once, referenced everywhere. Compiled straight into ScaffIQ.
Process
Five steps, compiled straight through, nothing gets re-keyed.
Define
Enter the design once, in a structured 10-step wizard. No free-text tag entry.
Compile
Locked revisions export to .docx and compile straight into ScaffIQ.
Validate
AI checks the data, not the prose. Broken references and logic gaps get flagged before export.
Deploy
Tags, I/O and sequence code land downstream with nothing re-typed and nothing drifting.
Build
Ignition Perspective symbol templates and page layouts generate automatically. The engineer wires them to live tags.
The IQ platform
One JSON schema compiles into four products.
FDSIQ produces the single source of truth. Everything downstream compiles from it.
Source of truth
FDSIQ
Structured 10-step wizard. Relational data model. AI validation engine.
Preview
Your FDS lives in Word. Your tags should live in a relational model.
View full page →
Standalone or from FDSIQ
ScaffIQ
I/O framework and tag declarations. Runs standalone, or compiled straight from FDSIQ's JSON schema.
Preview
Your IO list becomes a compiled PLC scaffold. Verified at every checkpoint.
View full page →
Compiled from FDSIQ
ScaffIQ Sequence Engine
PLC sequence code, compiled from the same JSON schema.
Preview
Real sequence logic, not just scaffolding. Every rung reviewed before it ships.
View full page →
Compiled from FDSIQ
ScaffIQ Perspective Engine
Reusable Ignition Perspective symbol templates and a ready-to-use overview page, generated from your FDS.
Preview
A ready-made symbol library for Ignition. Structure and layout, yours to wire up.
View full page →
Separate product
CurrentIQ
Turns an on-site electrical assessment into a polished, Standards-referenced report and client proposal in minutes.
Preview
Professional reports and proposals in minutes, not hours.
View full page →
Under the hood
Safety logic stays locked out of AI, by design.
AI never reads or writes safety_functions. It’s isolated at the infrastructure level, not just by convention.
schema.safety_functions access: locked ai_write: false ai_read: false editable_by: engineer_of_record revision: immutable