We have a tool that converts Honeywell Experion, Yokogawa CENTUM, and Foxboro DCS graphics to web-based displays — quickly and easily,
without rebuilding from scratch.

Live tag values and trend data from your historian (IP.21, AVEVA PI, or Honeywell PHD) are connected directly, so engineers can view
real-time process data and trends from any office browser on the intranet.

Multi-vendor DCS on the same plant?
All converted into one unified web view.

Demo:

Happy to answer questions.

 

Is this something you built yourself? Seems like there is a growing need for this

 

Yes, I built it myself.

Each site has slightly different graphic standards — colors, shapes, styles — so there's a one-time calibration step per site. Once set, it applies consistently to all graphics without further adjustment.

This makes large-scale conversion significantly more cost-effective compared to traditional per-graphic conversion work.

Can make demo if you're interested.

 

Nice work — the per-site calibration step makes a lot of sense. Graphic standards drift so much between plants that a one-size conversion was never going to hold up, so treating it as a calibration problem rather than a one-off mapping is the right call.
One thing I'd be curious about is how you're handling the real-time layer underneath the graphics. Pulling historian trends into a browser view is fairly well-trodden, but keeping a live mimic responsive with a lot of tags updating at once — without hammering the DCS interface or the OPC layer — is where these projects tend to get interesting. Are you polling on a fixed cycle, or pushing on change from a middle layer?
And the question I always end up asking with browser-based HMIs: does this stay read-only, or is there any path to writing back to the process? Read-only visualization is a much easier safety story, but the moment operators want setpoint changes from the browser, the whole conversation shifts to how you guarantee that write path. Curious where you've landed on that, since it tends to define who the tool is really for

 

Thanks for the thoughtful questions.

We pull data from the historian rather than directly from DCS or OPC — this avoids additional cybersecurity exposure and keeps the interface endpoints minimal. Update frequency is configurable per site.

Read-only is by design. Visualization only — no write path to the process. Safety and cybersecurity are the reason, and it keeps the tool clearly within office network boundaries.

The core problem we're solving is simpler: DCS graphics change frequently, and keeping an office-network view in sync is expensive with traditional approaches. We make that easy, fast, and low-cost.