While the machine is still being built

Millwright vs Revel

Revel commands hardware. Real-time telemetry plus RevelCode for the checks that have to hold while the machine moves: expected states, runtime limits, the abort. Millwright reads the machine and runs the work around it. It does not write to the DCS, and it raises no alarms of its own.

Keep Revel when: You need to command hardware, with abort logic living in the control layer.
Pick Millwright when: The controller is settled, and the hole is everything around it.

The Millwright workspace around a machine that already has a controller. — Millwright

A Revel console commanding an engine: live channels, limits and abort state. — Revel

The difference

What it does to the machine

Millwright: Reads it. Does not write to the DCS.
Revel: Commands it. Sequences, runtime checks, abort logic.

The job

Millwright: The workspace around a controller you already trust.
Revel: The software that develops, deploys, and commands the hardware.

Where it starts

Millwright: The historian, the EAM, and the procedures library you already have.
Revel: A stand whose control software is holding the hardware back.

When something is wrong

Millwright: Diag shows the points it read and stops to ask. Raises no alarms of its own.
Revel: RevelCode holds the check at runtime, so the abort is not a meeting.

The crew

Millwright: Operators, planners, contractors, and customers, scoped to the asset.
Revel: The people commanding the system Revel controls.

Where it runs

Millwright: Hosted, in your cloud, or on the plant floor next to the historian.
Revel: On the network with the hardware, including a closed network.

Feature comparison between Millwright and Revel
Feature	Millwright	Revel
What it does to the machine	Reads it. Does not write to the DCS.	Commands it. Sequences, runtime checks, abort logic.
The job	The workspace around a controller you already trust.	The software that develops, deploys, and commands the hardware.
Where it starts	The historian, the EAM, and the procedures library you already have.	A stand whose control software is holding the hardware back.
When something is wrong	Diag shows the points it read and stops to ask. Raises no alarms of its own.	RevelCode holds the check at runtime, so the abort is not a meeting.
The crew	Operators, planners, contractors, and customers, scoped to the asset.	The people commanding the system Revel controls.
Where it runs	Hosted, in your cloud, or on the plant floor next to the historian.	On the network with the hardware, including a closed network.

Revel as described on their public pages in October 2026. Corrections.

Where Revel wins

You need to command hardware, not only watch it.
Abort logic has to live in the control layer.
The stand has no controller you trust.

Where Millwright wins

The controller is trusted, and has to stay in charge.
No product here may write to the DCS.
The hole is the historian, the work, and the procedure.

How they fit together

Revel is extending this control layer into industrial sites (power, oil and gas, water), and that is a real product. The controller stays in charge either way. A site can run Revel on the machine and Millwright for the people around it.

Questions

Does Millwright control equipment?

No. It does not write to the DCS and does not replace the alarm management system. Write-back, where it exists, is per system and per field, and off until you turn it on.

Revel is moving into plants. Still a different product?

Yes. Commanding the process and running the work around it are different jobs, and a site can buy both.

Our operators already have a Revel console. What opens Millwright?

The console, when they command the system. Millwright, when the question leaves the console: which procedure, which ticket, what last week looked like, who outside this room may see it.

Other comparisons

See it running on your own plant.

We are onboarding a small number of operations teams. Three questions, and we will be in touch.