What is an FHX file?
An FHX file is the text-based export of an Emerson DeltaV™ control system’s
engineering configuration — the file the system’s export tooling creates when
engineers export a control strategy, a plant area, or the entire engineering
database. The name is simply the file extension, .fhx; Emerson’s own
documentation describes it as a control strategy file created by the export
configuration tooling.
What’s inside an FHX file
A full-system FHX file carries essentially everything the engineering database knows about the configured system, as structured, deeply nested text:
- control modules with their parameters, function blocks, and alarm configuration,
- the hardware topology — controllers, operator workstations, I/O cards and channels, and the device signal tags that tie field wiring to control logic,
- batch structure: units, equipment and phase logic, and recipe procedures,
- interlocks, trends and historization settings, diagnostics, and per-module revision information.
That is exactly the knowledge half the plant asks the automation team for every day: alarm limits, I/O assignments, what a phase actually does to which equipment, what last quarter’s modification project changed.
Where FHX files come from
FHX files are made at the engineering workstation, by the few people with system access and the right tooling. An export can be as narrow as a single module or as wide as the whole engineering database, and teams produce them routinely — as configuration backups, for migrations and integrator hand-overs, for change review, and as the raw material for specification documents. The FHX file is a snapshot of the engineering definition as downloaded to the system — configuration data, not online set values in the controllers, not live process values.
How big is an FHX file?
A single module exports to a file any text editor opens instantly. A plant-wide FHX file export is a different animal: it routinely runs to several gigabytes of nested text, with every module, parameter, alarm, and hardware reference of the site inside.
How do you open an FHX file?
Technically, any text editor can open a small one — it is text. But a multi-gigabyte export defeats editors, and scrolling nested blocks is not reading: the answers are in there, cross-referenced across thousands of modules, and no human finds them line by line.
In practice there are two ways to read one:
- The native tools — import the file back into a system at the engineering workstation. Exact and authoritative, but limited to the few people with system access.
- FHX Forge — upload the FHX file in a browser and get the whole configuration as browsable, searchable, annotatable engineering data: sortable tables per module family, hardware topology, phase and recipe logic as clickable flow diagrams, version-to-version comparison, and Excel specification documents ready to hand over. It runs as a dedicated appliance inside your own network, so the export never leaves your infrastructure.
One export, every engineer gets answers
The engineering hours are not saved in one heroic analysis — they are saved in the dozens of small lookups per week that otherwise all queue on the automation team. Request a demonstration and bring an FHX export from your own plant — we’ll walk you through it live, or set it up against your file and let the results speak.