Service
SCADA and HMI development
A SCADA screen is read by someone who is tired, at the end of a shift, deciding whether to stop a line. It should answer that question in about a second. Most of the systems we are asked to fix answer it in about a minute.
We develop on FactoryTalk View SE and ME, Siemens WinCC across its editions, AVEVA Wonderware InTouch and System Platform, and Citect. On the operator-panel side that extends to PanelView, Comfort and Basic Panels, GOT2000, Magelis and the Omron NA and NB ranges.
Screens are built on a template so the second one costs less than the first and the fortieth still looks like the first. Colour carries meaning and nothing else: if red only ever means an alarm, an operator can scan a plant overview without reading a word.
What we build
- Plant overview, area and equipment-detail mimics, with animation tied to real state rather than decoration
- Alarm and event handling — rationalised, prioritised, with cause and operator action against each alarm
- Historical trending and datalogging, sized so the disk does not quietly fill up in month four
- Shift, batch, downtime and energy reports, scheduled and emailed
- Historian integration and OPC UA or native driver interfaces to third-party equipment
- User accounts, role-based access and audit trail where the process demands it
- Multilingual screen sets for mixed operator groups
- Redundant server pairs and failover, tested by actually pulling the plug
Alarm floods
The most common problem in an inherited SCADA system is not a missing feature. It is that every digital input became an alarm, so during a real upset the operator gets four hundred of them and ignores all four hundred. Alarm rationalisation is usually the highest-value day we can spend on an existing system.
Migration paths we handle
| From | To | What is actually involved |
|---|---|---|
| RSView32 | FactoryTalk View SE | Display set rebuilt; tag database and alarm model restructured. Not an import. |
| WinCC Flexible | WinCC Advanced / Unified (TIA Portal) | Screens and scripts rewritten. Budget for it as a rewrite from the start. |
| InTouch standalone | System Platform | Tags reorganised into a Galaxy object model — the point of the exercise, and the bulk of the work. |
| Citect legacy | AVEVA Plant SCADA | Cicode reviewed and ported; redundancy configuration re-proved, because it is usually wrong. |
Related work
A food manufacturing site in Coimbatore · 2025
Citect SCADA audit and redundancy rebuild on an effluent treatment plant
A redundant SCADA pair that had never actually failed over, found during a first AMC visit and rebuilt without taking the plant out of service.
A nutrition products manufacturer in Hosur · 2024
WinCC Flexible to TIA Portal migration across a packaging line
Eleven operator panels on end-of-life WinCC Flexible, rebuilt on a common template so the twelfth machine cost a fraction of the first.
A pharmaceutical facility in Chennai · 2024
Chiller plant integration and energy monitoring across a mixed-vendor facility
Four chillers from three vendors, plus cooling towers and AHUs, brought onto one head-end with metering placed to answer two specific questions.
Questions we get asked
Next step
Have a scada & hmi development enquiry?
Send the plant detail — platform, I/O count, what has gone wrong, and the window you can give us. An engineer picks it up.
An engineer responds within one business day.