Product
One data model compiles into four products.
FDSIQ captures the design once. ScaffIQ, the Sequence Engine and the Perspective Engine compile straight from it, or run on their own. Nothing gets re-keyed between stages.
The platform
Five products, one JSON schema.
Jump straight into a product, or keep reading for how each one compiles from the same structured data below.
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 →
FDSIQ
Structured 10-step wizard. Tags defined once, referenced by dropdown everywhere after. AI validates the data, not the prose, and flags broken references before export.
FDSIQ
input: structured wizard (10 steps)
validation: AI, data-level only
safety_functions: locked, ai_write=false
export: .docx (client deliverable)
.json (compile target)ScaffIQ
Compiles I/O and tag declarations, either from FDSIQ's structured output or entered directly. Runs standalone.
ScaffIQ
input: FDSIQ output, or entered directly
output: I/O framework
tag declarationsScaffIQ Sequence Engine
Compiles PLC sequence code from the same structured schema. No hand-written logic to re-key.
ScaffIQ Sequence Engine input: structured schema output: PLC sequence code
ScaffIQ Perspective Engine
Reusable Ignition Perspective symbol templates and a ready-to-use overview page, compiled from the same structured schema. Structure and layout only, live tag connections are yours to make.
Overview
Motors
Pumps
Valves
Instruments
Comparison
What actually changes
| Measure | EngineeredIQ | Manual process | Generic alternative |
|---|---|---|---|
| Tag definition | Once, referenced everywhere | Re-entered in Excel, Word and the PLC program | Partial reuse, still hand-mapped |
| Time per FDS | Structured entry, compiled output | 40 to 60 billable hours lost to drift and rework | Faster drafting, no compiled output |
| Revisions | Locked and immutable | Overwritten, no audit trail | Version history, not immutable by design |
| Safety section | Isolated at the infrastructure level | Lives in the same document as everything else | Not typically separated |
User Specs & Requirements
What you need to run any IQ product.
Nothing to install. Every product runs entirely in the browser, whether you're using FDSIQ, ScaffIQ, Sequence Engine or Perspective Engine.
Modern browser
A current version of Chrome, Edge, Firefox or Safari. JavaScript and cookies must be enabled.
Reliable internet connection
25 Mbps or faster recommended. Every save, validation and compile is a live call, there is no offline mode.
Software to open your output
Word or another .docx viewer for FDSIQ, Studio 5000 for ScaffIQ and Sequence Engine, Ignition Designer for Perspective Engine.
A credit card with sufficient available funds
Held on file via Stripe, charged automatically at your first locked revision or compile. No manual invoice step.
A desktop or laptop screen
The structured wizards and checkpoint review screens are built for a real screen, not optimised for a phone.
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.