Platform for engineering
Your control system's knowledge,
unlocked for every engineer.
One upload turns a multi-gigabyte Emerson DeltaV™ FHX export into browsable, searchable, annotatable engineering data for the whole organization — entirely inside your own infrastructure.
The knowledge is already there. It's just locked in an export nobody can read.
A control system's configuration holds the answers half the plant needs every day — alarm limits, I/O channels, phase logic, what last quarter's project changed. But in practice it's readable only at the engineering workstation, by the few people with system access and the right tooling. Everyone else asks — and waits.
The distance from “we have an export” to “every engineer has the answer” is one upload.
For the whole organization
One export, everyone reads it
The engineering hours aren't saved in one heroic analysis — they're saved in the dozens of small lookups per week that today all queue on the automation team.
Electricians & instrument technicians
The full hardware topology — controllers, I/O cards, channels. Trace a signal from the marshalling cabinet to the control strategy, from a browser.
Process engineers
Phases, recipes, equipment logic and parameter values organized per plant unit — with the sequences drawn as clickable flow diagrams.
Automation engineers
Deep module detail, alarms, interlocks, where-used cross-references, global tag search — and far fewer interruptions, because everyone else serves themselves.
Validation & quality teams
As-built specification documents generated from the live configuration, version-to-version comparison, and an append-only audit trail for evidence.
System administrators
Controllers, operator workstations, network segments and the I/O subsystem — an always-current as-built inventory.
OEM vendors & contractors
One-click Excel specification packages to hand over — or a view-only login scoped to exactly what you've prepared.
Standout capabilities
Built like the plant depends on it
Your configuration never leaves your network
A dedicated single-tenant appliance inside your infrastructure — no shared cloud, no multi-tenant database, no telemetry phoning home. Offline-first by architecture, not by policy.
Built for regulated environments
Designed with pharma and petrochemical plants in mind: an append-only audit trail on every state change, and specification documents generated from the configuration itself — so the as-built paper matches the as-running system.
Logic you can actually read
Every phase's SFC and every recipe's PFC rendered as an interactive flow diagram — click any step or transition to read its exact logic, actions and conditions.
See exactly what changed
Upload the new export next to the old one: a changed / added / removed triage across the whole system, plus a structural, section-by-section diff for any single module.
Adapts to your site's conventions
Classification and parsing behavior are per-site configuration, not custom development. Onboarding an unfamiliar site means tuning a profile — not commissioning a software project.
The plant's memory
Notes and comments live on the data itself, flow into the exported documents, and survive configuration upgrades — with a full revision history on every note.
The interface speaks your engineers' language
Every menu, grid and detail page renders in the language each user picks — one click in the topbar, per person, with the language set growing alongside this website. What never gets translated is the configuration itself: tags, descriptions and parameter values stay exactly as they were engineered.
How it works
From export to answers in five steps
Upload
Drag the FHX file into the browser — chunked upload handles multi-gigabyte exports.
Parse
The appliance streams the export into structured, classified per-module data.
Explore & annotate
Grids, detail pages, hardware topology, search, where-used — plus notes from the people who know the plant.
Compare
Upload the next export alongside the previous one and review exactly what changed.
Export
Excel specification packages and any filtered grid view, ready to hand over.
Interfaces & integrations
What the platform holds doesn't stay locked inside
Offline-first by architecture — and still open on your terms. Three surfaces expose the same engineering data you read in the browser: each opt-in, each under your control, none of them live process values.
REST API
A versioned, read-only API over the specifications — every module, phase, recipe, hardware item and cross-version comparison you can see in the platform. Personal access tokens, strict version pinning, stable pagination, machine-readable errors — with interactive documentation and a guided check script served from the appliance itself.
MCP tools for AI assistants
The same service layer exposed as read-only tools over the Model Context Protocol. Connect the AI clients your organization already trusts and ask “which phases changed between the last two exports?” — answered from your own configuration, with citation links back into the platform. Same personal tokens, same role, no write path at all.
MQTT publish into your UNS
An optional egress service publishes the plant structure — area, process cell, unit, module — as retained topics on your own MQTT broker: a Unified Namespace seeded with the ISA-88 hierarchy straight from the FHX export, the skeleton UNS initiatives otherwise hand-build in spreadsheets. A payload profile controls the mapping down to per-attribute points and batch branches. It is the appliance's only outbound connection — and it ships disabled.
Deployment
A box on your site, or a dedicated virtual server
A box on your site
Preconfigured appliance hardware, delivered ready to run inside your network.
Or a dedicated virtual server
The same appliance as a virtual deployment — on infrastructure we provide, or on your own.
Either way, it's single-tenant by design: one customer, one appliance, one isolated dataset — with your identity provider, your SMTP relay for sign-in links, and invite-only access under your control.
Configuration data, not live process values.
FHX Forge works on the exported engineering database — the configuration as downloaded to the system. It doesn't connect to controllers and shows no live values; checking the live state remains, as it should, the automation engineer's job in the native system tools. FHX Forge's territory is everything around that: the engineering definition, readable by everyone — in the browser, over the API, or seeded into your UNS.
Test it on your own data
Prepare an export from your own plant — we'll walk you through FHX Forge live, or set it up against your export and let the results speak.
Request a demo