Cookies on this site

We'd like to use a few non-essential cookies.

We use strictly-necessary cookies to make this site work. With your permission we'd also like to use Google Analytics 4 to understand which pages are useful, and Crisp Chat so you can start a conversation with us. See our Cookie Policy for detail — you can change your choice at any time from the footer.

Controls & Automation · Service

HMI and SCADA development — operator interfaces that get used properly.

Panel HMI screens, plant-wide SCADA, alarm handling, historian and data-collection layers — designed around the people who actually use them.

HMI & SCADA designAlarm rationalisationData & historian

What we do

The service in plain English.

A good HMI is invisible when things are normal and unambiguous when things go wrong. A bad HMI trains the operators to disable alarms, ignore statuses and rely on tribal knowledge that leaves the site when the operator retires. Lutrom develops HMI and SCADA systems around the way the operators actually work — following the ISA-101 human-machine interface guidelines and the ISA-18.2 alarm-management principles where the site's operating model supports it. We design panel HMIs (touchscreens, thin-client stations, small operator panels) and plant-wide SCADA (multi-station supervisory systems with historian, dashboards and reporting) as part of a wider automation project, or as standalone upgrades of legacy systems that have accumulated a decade of ad-hoc changes and hundreds of nuisance alarms. Every HMI/SCADA project starts with a screen-design workshop with the actual operators — not just the engineering manager — and every finished screen is walked through with those operators before we consider it done. The result is an interface that gets used the way it was designed to be used, and an alarm list that operators trust.

What's included

Every job covers the following.

  • HMI screen design — operator workshops, ISA-101 layout principles, colour discipline
  • Alarm rationalisation — reducing alarm floods to a signal an operator can act on
  • SCADA design — multi-station supervisory systems with role-based access
  • Historian integration — event data, alarm data, process values, KPI dashboards
  • Trend and reporting layers — automatic shift reports, downtime analysis, batch reports
  • Access control — user roles, audit trails, electronic signatures where regulated
  • Legacy SCADA migration — porting screens, tags and history from old platforms
  • Data-collection layers — OPC UA / MQTT / SQL / REST integration for MES and ERP
  • Operator training — hands-on training sessions and printed SOPs delivered on hand-over

Who it's for

Common on these sites.

Our approach

Survey. Quote. Deliver. Sign off.

01

Understand the operator

We run a screen-design workshop with the people who actually use the current system. Every screen decision is grounded in an operator's real task, not a vendor's default template.

02

Alarm rationalisation

For upgrades and migrations, we rationalise the existing alarm list — critical vs. warning vs. information, deadband and delay tuned, redundant alarms removed. Fewer alarms, better response.

03

Develop & simulate

HMI/SCADA developed against a bench simulator or the live PLC in isolation, so operators can review screens against real data before go-live. Feedback baked in before hand-over.

04

Deploy & train

Deployed under a controlled cutover. Operators trained one shift at a time. Two-week hyper-care period after go-live where an engineer is available on request to tune anything that needs adjusting.

How we price this work

No surprise invoices.

HMI/SCADA work is priced against a written screen inventory and functional specification. Small single-panel HMIs are quoted fixed-price after a design workshop. Larger SCADA and historian projects are phased — a fixed-price design phase followed by a fixed-price implementation phase. Legacy migrations are quoted after a survey of the existing system, including a screen count, tag count and an alarm-list audit. Every quote itemises design, development, deployment, training and hyper-care so you can see exactly where the money goes.

Coverage

Where we deliver this service.

We deliver hmi and scada development — operator interfaces that get used properly across the North West of England — from our Northwich base. Same-day dispatch for callouts and scheduled visits for planned work.

Service FAQ

What clients ask before they call.

Which HMI / SCADA platforms do you work on?

We work on the mainstream industrial HMI and SCADA platforms. Tell us your existing platform and we'll confirm fit; where you're greenfield we'll recommend based on your site's existing installed base and your longer-term software strategy — not on our preferred vendor.

Can you rationalise alarms on an existing SCADA?

Yes — alarm rationalisation is one of the highest-value pieces of work we do on legacy SCADA systems. We assess the existing alarm list against ISA-18.2 principles, categorise, remove redundant alarms, tune thresholds and deadbands, and hand over a rationalised alarm database with the reasoning for each decision documented.

Do you migrate legacy SCADA systems?

Yes. Legacy migrations are usually driven by unsupported platforms, obsolete hardware or licensing changes. We audit the existing system, produce a migration plan, port the screens and tag database, and run the new SCADA in parallel with the old one during cutover so there's a fall-back if anything goes wrong.

Do you integrate with MES / ERP?

Yes. Standard interfaces (OPC UA, MQTT, SQL, REST) are straightforward. Legacy interfaces are possible but require a working test environment — we won't attempt an integration for the first time against a live production database.

What about electronic-signature / audit-trail requirements?

For regulated environments (pharma, life sciences, some food and beverage) we design HMI/SCADA with role-based access, electronic signatures and complete audit trails, aligned to the client's compliance framework. Where the site is subject to 21 CFR Part 11 or Annex 11 we design to those requirements and produce the documentation to support validation.

Can you train the operators?

Yes — every deployment includes hands-on training with each shift, printed SOPs, and a two-week hyper-care period after go-live where an engineer is available on request to tune anything that needs adjusting. Training the people who will use the system is not an optional extra.

Talk to us

Got a project, a survey or a compliance deadline?

Talk to a working engineer — not a call centre. Every enquiry gets a same-day human reply.

Related

Adjacent services you might also need

Made with Emergent