How it works

Define it once, and everything downstream compiles from there.

This is the same five-stage sequence from the home page, expanded. Each stage below shows what actually happens to your data.

Walkthrough

FDSIQ, screen by screen

Real screenshots of the actual wizard, not a mockup, including a real AI Validation Engine catch and override. Press Play for an animated run-through, or step through it manually.

Walkthrough

ScaffIQ, screen by screen

Real screenshots of the actual wizard: importing an FDSIQ export, four checkpoints, the Sequence Engine liability gate, and Perspective Engine symbol assignment. Press Play for an animated run-through, or step through it manually.

Walkthrough

Sequence Engine, screen by screen

Real screenshots through to a real L5X download, plus the actual rung visualizer, live, rendered from a real 346-rung water-treatment plant project. Press Play for an animated run-through, or step through it manually.

Walkthrough

FDSIQ to ScaffIQ, end to end

A recorded walkthrough of a specification moving from FDSIQ through the JSON handoff into ScaffIQ compilation. Use the controls below the frame to step through it.

Define

Enter the FDS in a structured 10-step wizard. Tags, I/O and sequence logic are defined once, in Step 3, and referenced by dropdown in every step after. No free-text tag entry anywhere downstream.

Step 3: Tag Register
  CONV014_ZN3_OVRN_DI
  CONV014_ZN3_OVRN_AI

Referenced by dropdown in:
  Step 5 (Sequence)
  Step 7 (Interlocks)
  Step 9 (Alarms)

Compile

Locking a revision exports two artifacts at once. A client-ready .docx built on your corporate template, and the .json that becomes the compile target for everything downstream.

Revision: Rev A (locked)
Export:
  fds-acme-water.docx   client deliverable
  fds-acme-water.json   compile target

Validate

Before export, AI checks the data itself, not the prose. Broken references, missing interlocks and impossible timing get flagged. The safety_functions block is never read or written by AI. Locked at the infrastructure level.

Validation report
  passed: 214 tags resolved
  failed: CONV014_ZN3_OVRN_DI referenced in Step 7, undefined in Step 3
  locked: safety_functions untouched

Deploy

The locked JSON compiles directly into ScaffIQ's I/O framework and tag declarations, and into the Sequence Engine's PLC logic. Nothing gets re-typed between stages.

fds-acme-water.json
  -> ScaffIQ: I/O framework, tag declarations
  -> ScaffIQ Sequence Engine: PLC sequence code

Build

The same locked JSON also compiles into the Perspective Engine: a reusable Ignition Perspective symbol library and a ready-to-use Overview page, devices grouped by symbol type. Structure and layout only, the engineer wires every symbol to a live tag before use.

fds-acme-water.json
  -> ScaffIQ Perspective Engine: symbol library
                                 Overview page (grouped by type)

User Specs & Requirements

Qualified engineers only.

EngineeredIQ products are 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.