Skip to content
EngineeredIQ

EngineeredIQ

FDSIQ writes the spec.
ScaffIQ builds from it.

Define equipment, tags and sequence logic once in FDSIQ. ScaffIQ compiles the same data into the I/O framework, PLC sequence logic and SCADA screens, so none of it gets retyped by hand into Excel, Studio 5000 or Ignition.

Get startedSee how it works

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.

Get startedSee how it works

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.

Standalone or from FDSIQ

ScaffIQ

I/O framework and tag declarations. Runs standalone, or compiled straight from FDSIQ's JSON schema.

Compiled from FDSIQ

ScaffIQ Sequence Engine

PLC sequence code, compiled from the same JSON schema.

Compiled from FDSIQ

ScaffIQ Perspective Engine

Reusable Ignition Perspective symbol templates and a ready-to-use overview page, generated from your FDS.

Separate product

CurrentIQ

Turns an on-site electrical assessment into a polished, Standards-referenced report and client proposal in minutes.

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

Compile your next FDS instead of writing it.

Get started