Service · Web development

Custom HMI software development.

Custom Human-Machine Interface for operators on the factory floor, at the plant or in the field. Web-based or on industrial touchscreens, with live process data, alarms and recipe management, integrated with your PLCs via OPC UA, Modbus or MQTT.

Web-based HMIOPC UAMulti-vendor PLCBranded UX

What is an HMI, exactly.

An HMI (Human-Machine Interface) is the screen an operator uses to control a machine or installation. In practice, it is usually an industrial touchscreen of fifteen to twenty-one inches next to the line, but increasingly also a tablet the operator carries around or a browser page on a workstation in the control room.

Functionally, an HMI shows the current process variables (temperature, pressure, speed, fill level) plus buttons to start, stop or reset the machine. On top of that come prioritised alarms, trend charts covering the past hours or shifts, parameter adjustments, and recipe management for different production runs or product types. The HMI pulls that data in real time from the PLC (Programmable Logic Controller) that physically controls the machine, usually via OPC UA, sometimes via Modbus or a manufacturer-specific protocol.

In the Purdue reference model — the most widely used framework for industrial automation — the HMI sits at level 2: the operator interface at the machine. Level 1 is the PLC itself, level 3 is SCADA for supervisory monitoring across multiple machines or sites, level 3.5 is the MES for production execution, and level 4 is your ERP. The higher you go up this stack, the more business logic and the less real-time control. A well-built HMI knows its place in that stack: operating and visualising on the shop floor, and passing context on to the layers above.

We build custom HMI software when the standard packages from Siemens, Rockwell or Schneider are not the right fit — for example because you want a single interface across different PLC brands, because operators walk around with a tablet, or because the interface needs to integrate deeply with your MES and ERP. For the horizontal integrations with higher-level systems, we often set up API integrations between HMI, MES and ERP, so that production orders, quality records and machine events flow through automatically.

Three types of HMI software.

Depending on where the interface needs to run, how many machines and sites it spans, and how deeply it needs to integrate with your higher-level systems.

Compact project · fixed sprint budget

Single-machine HMI

An interface for a single machine or installation, running on an industrial touchscreen or a local browser. Live process data from the PLC, alarm handling, basic trends and operator login with role management. Suitable as a replacement for an outdated proprietary HMI or as the interface on a new line.

OPC UA clientReal-time trendsAlarm handlingTouchscreen-ready
Mid-sized project · fixed sprint budget

Web-based or mobile HMI

A browser-based HMI that operators can open on a tablet, phone or workstation. One codebase for multiple devices, push notifications for critical alarms, and role-based access to machine clusters. Operators walk around with a device instead of being tied to a single panel.

React / VueWebSocketPush notificationsInstallable PWA
Larger project · fixed sprint budget

Multi-vendor or multi-site HMI

One HMI platform across multiple PLC brands (Siemens, Rockwell, Beckhoff, Omron) or multiple production sites. A unified data layer via OPC UA and MQTT, an interface branded in your look and feel, and integrations with MES, ERP and historian. The bridge between the plant floor and the office environment.

Multi-PLC abstractionMES integrationHistorian integrationFDA / GMP-ready

What you get at the end.

A production-ready HMI platform, plus the documentation and integrations to manage and extend it yourself.

  • The HMI software itselfProduction and staging, running on an industrial-grade PC, an edge device or in your cloud — depending on what your network allows.
  • OPC UA, Modbus and MQTT integrationsConfigured for your specific PLC brands and types, with tag mapping and a watchdog for dropped connections.
  • Codebase and documentationFull source, build instructions, a deployment runbook and an architecture overview in which your OT and IT teams can find the reasoning behind the choices.
  • Operator and admin manualWritten for the people who work with it every day: how to add a recipe, how an alarm is acknowledged, how a new operator role is configured.
  • Maintenance contract (optional)Monitoring, security patches, PLC firmware updates that shift the tag names, and ongoing development. Fixed monthly price, four response-time tiers.

When custom HMI is the right choice.

We don't replace Siemens WinCC, Rockwell FactoryTalk or Schneider Vijeo for small, simple jobs — they do that well. It does make sense to consider a custom solution in these situations.

Multi-vendor

Different PLC brands on one screen

You have Siemens PLCs alongside Rockwell, or Beckhoff alongside Omron. A single-vendor HMI forces everything into its ecosystem. A custom HMI talks to all of them via OPC UA and gives the operator a single user interface.

Mobile-first

Operators walk around

The operator isn't tied to a single panel but walks the line with a tablet. A browser-based HMI fits tablet, phone and workstation without you having to manage three different interfaces.

Branded UX

Your brand, not Schneider's

For OEMs and machine builders: you sell the machine, but the standard HMI looks like the PLC supplier's. A custom HMI in your own industrial UX makes the machine recognisably yours.

Deep integration

Beyond the plant floor

The HMI needs to pull production orders from the ERP, write quality data back to the MES, and push maintenance signals to the CMMS. That kind of horizontal integration doesn't come as standard in vendor packages.

OPC UA, Modbus and the PLC landscape.

OPC UA (Open Platform Communications Unified Architecture) is the industry-standard protocol that has become the dominant way of talking to a PLC over the past ten years. It is vendor-independent: an OPC UA client talks to a Siemens PLC just as well as to a Rockwell or Beckhoff, provided the PLC publishes a UA server. For modern PLCs that is built in as standard; for legacy controllers we build a gateway that translates Modbus, Profinet or a manufacturer-specific protocol to OPC UA, so the HMI only has to speak one language.

We also work with MQTT for pub/sub scenarios, which is particularly useful if you monitor machines remotely, or if data needs to go not just to one HMI but to several consumers (HMI, MES, historian, dashboard) without each of them setting up its own connection to the PLC. For field-level integrations, Modbus TCP is still regularly needed, especially on older installations or small sensor modules where OPC UA is overkill.

The tech stack of a typical custom HMI looks like this: a web front end in React or Vue for the operator interface, a Node.js or Python back end that handles PLC communication and normalises data, a time-series database (InfluxDB or TimescaleDB) for historical trends, and WebSocket or Server-Sent Events for real-time push to the browser. For scenarios where machines also need to be accessible remotely, such as engineers carrying out maintenance on site, we often link the HMI to an IoT app that shows the same data on a phone or tablet, with push notifications for critical events.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Standard HMI packages and when they fit.

The Dutch and German plant-floor landscape is largely dominated by a handful of HMI packages: Siemens WinCC (often paired with a Siemens TIA Portal PLC), Rockwell FactoryTalk View (Allen-Bradley environments), Schneider Electric Vijeo Designer (Modicon and Magelis), Wonderware InTouch (now AVEVA), Inductive Automation Ignition (vendor-independent, web-based), and B&R and Beckhoff TwinCAT HMI. These packages are mature, well documented and in many cases the right choice.

We come into the picture where these packages have limitations: they are typically tightly bound to their own PLC ecosystem, their web clients are often licence-bound and not always truly mobile-friendly, and their look and feel is generic. For a single-vendor, single-machine HMI on an industrial touchscreen, the standard package is the right choice. For a multi-vendor, mobile or branded scenario, the extra investment in a custom solution often pays off against the licensing and flexibility limitations in the long run.

One specific example where custom wins: you are a machine builder selling installations to customers around the world, and you want the HMI on your machine to be recognisably yours, not the PLC supplier's. In that case we build a branded thin client or web HMI that carries your look and feel, while the PLC choice can vary per customer or per machine. The same applies to manufacturers with a mixed PLC floor who want to spare operators from switching between different vendor interfaces.

How an HMI project runs.

1

Introduction and walk-through

A conversation in which we learn which machines you have, which PLC brands they run on, what data needs to appear on screen and which compliance requirements apply. Ideally we walk the production floor with you to see the operator flow first-hand.

2

Tag inventory and wireframes

We take stock of the OPC UA, Modbus or MQTT tags the HMI needs, and sketch out the first screen flow with your operators and process engineers. By the end you have a scope, a plan and a clickable prototype.

3

Building in sprints

Every two weeks you get a working build that you can try out on a staging PLC or a PLC simulator. Operators test from the very first sprint — an HMI that looks good in the meeting can still turn out to be awkward on the shop floor.

4

Shop-floor rollout

A phased go-live on one line, then rollout to the rest. Operator training, a short video tutorial, and a runbook for your IT and OT teams. After that, ongoing maintenance for security updates and further development.

Frequently asked questions.

What clients usually want to know before we start on a custom HMI project.

What exactly is an HMI, and how does it differ from SCADA?
An HMI (Human-Machine Interface) is the operator interface at the machine itself — low in the Purdue model. SCADA sits a layer higher and is supervisory: multiple machines or sites in a single overview for process engineers and management. In practice the terms are often used interchangeably, but the rule of thumb is: HMI is for operating, SCADA is for monitoring a larger whole.
Do you replace Siemens WinCC or Rockwell FactoryTalk?
For small, standard jobs: no. Those packages are mature and well documented. We come into the picture when you want a single interface across different PLC brands, when you want web or mobile instead of a proprietary thick client, or when you need deep integration with MES, ERP or CMMS that the vendor packages don't offer out of the box.
What about an OPC UA integration between PLC and SCADA or HMI?
OPC UA is the modern industrial standard for PLC communication and is built into almost every new PLC. We build OPC UA clients into the HMI that talk directly to the PLC, or OPC UA servers that abstract legacy PLCs over Modbus or Profinet, so the HMI only needs to know one protocol. Where OPC UA isn't available, we use Modbus TCP, MQTT or a fieldbus gateway.
Can a web-based HMI handle the real-time requirements of a production line?
For monitoring and control at operator level: yes, comfortably. WebSocket or Server-Sent Events deliver tag updates within tens of milliseconds — plenty for visualisation, alarm acknowledgement and parameter settings. For hard real-time control (motion control, safety loops) the PLC itself remains responsible; the HMI orchestrates, the PLC executes.
What about FDA 21 CFR Part 11, GMP or ATEX?
For regulated industries we build in audit logging, electronic signatures and data integrity from the first sprint — not bolted on afterwards. ATEX applies at hardware level (the enclosure and certification of the panel itself), not to software, but we make sure the software runs on ATEX-certified panels. We supply validation documentation (URS, FS, DS, IQ/OQ) where needed.
What determines the cost of a custom HMI?
Mainly four things: how many different PLC brands and types we need to integrate, how many different screens and flows there are, whether integration with MES/ERP/CMMS is involved, and which compliance requirements apply. A single-machine HMI is a different project from a multi-site platform with FDA validation. After the discovery sprint we give you a well-founded estimate.
How long until we can go live?
A single-machine HMI with a limited tag set can be up and running on a staging PLC within a few sprints. A multi-vendor or multi-site platform is a project of several sprints, delivered in phases. We always work with interim demos on real hardware, so you never only find out at the end what has been built.

Talk to us about your HMI.

A no-obligation introductory call of half an hour. We listen to your machine park, your PLC landscape and the operator flow, and give you direction you can actually use. This is often followed by a short walk-through on the shop floor — nothing tells you as much as the real working environment.

Edit content