Skip to content
Operational technology

SCADA & Industrial Automation

Control systems have to be right the first time and stay right for a decade. We engineer PLC and SCADA layers, remote telemetry for widely distributed assets, and the historian and reporting stack above them — then commission on site and support through the plant's life.

How it fits together

The shape of the work

IT/OT convergence without opening the plant floor

Process data climbs to the enterprise through a controlled conduit. Set-points come back down through the same reviewed path — never a flat network between a spreadsheet and a PLC.

Level 4 · EnterpriseERP · MES · reporting · cloud analyticsLevel 3 · SupervisorySCADA · HMI · historian · alarm managementLevel 2 · ControlPLCs · safety systems · control panelsLevel 0–1 · FieldSensors · actuators · drives · RTUsZONE & CONDUIT — firewalled, brokered, loggedprocess data ↑set-points ↓OT segment — no direct inbound access from the enterprise network.
What we deliver

Inside the SCADA & Industrial Automation practice

01

PLC & control panel engineering

Control philosophy, I/O schedules, panel design, PLC programming and factory acceptance testing before anything reaches site.

02

SCADA & HMI

Supervisory systems with high-performance HMI design, alarm rationalisation, role-based access and full audit trails.

03

Remote telemetry & RTUs

Cellular and radio-linked RTUs for pumping stations, substations, tank farms and other assets far from the control room.

04

OT security & IT/OT convergence

Zone-and-conduit segmentation, secure remote access and a data diode path from plant floor to enterprise reporting.

Tooling

What we build with

Representative — we choose per project, and we will tell you when the boring option is the right one.

  • Siemens TIA Portal
  • Allen-Bradley
  • Modbus / TCP
  • OPC UA
  • MQTT
  • Ignition
  • WinCC
  • IEC 61131-3
  • Historian / time-series
What you get

Every engagement includes

  • FAT and SAT documentation packs
  • Commissioning and operator training on site
  • Long-term spares and support agreements
In detail

What this actually involves

The level below the summary — for readers deciding whether we do this work or merely list it.

01

Before it reaches site

Most of the cost of a control system is incurred on site, and most of the risk is removed before you get there. We front-load the work into specification and factory testing, so commissioning is verification rather than discovery.

  • Control philosophy and cause-and-effect matrix agreed and signed
  • I/O schedule, loop list and interlock register as controlled documents
  • Panel general arrangement, wiring and termination drawings
  • Simulated FAT against the full I/O list with the customer present
  • Alarm rationalisation to ISA-18.2 before the HMI is drawn, not after operators complain
02

Commissioning

The part where a design meets a plant that is never quite as documented. It is a procedure with a paper trail, not a fortnight of goodwill.

  • Point-to-point loop checking with signed check sheets
  • Instrument calibration verified against certified references
  • Interlock and trip testing, proven by forcing the condition
  • Site acceptance testing against the same matrix used at FAT
  • Operator and maintenance training delivered on the running system
  • As-built drawings reissued — the drawings match the plant when we leave
03

Operations, after handover

A control system runs for a decade, and the interesting failures happen in year four. Day-two operation is engineered as deliberately as day one.

  • 24×7 monitoring with defined severity levels and escalation paths
  • Runbooks per failure mode, written before the failure
  • Incident response with post-incident review, blameless and recorded
  • Backup of PLC and SCADA configuration, with restores tested rather than assumed
  • Patching and change control through a reviewed window
  • Cyber-security monitoring on the OT segment, IEC 62443 zone model
04

Keeping it right for a decade

Drift is the quiet failure mode of instrumented plant. Readings stay plausible while slowly becoming wrong, and nobody notices until a batch is out of spec.

  • Scheduled instrument calibration against traceable references
  • Predictive maintenance from vibration, thermal and load telemetry
  • Spares holding and obsolescence tracking on controllers and I/O
  • Non-conformance and corrective-action handling with root-cause analysis
  • Full change history — who changed which rung, when, and why

The same control code, four times, with less and less pretend in it

Fidelity goes up left to right and so does the cost of being wrong. The point of the ladder is that a defect should be found in the cheapest column that can find it — which only works if the code is genuinely unmodified as it moves right.

SILSoftware in the loopPILProcessor in the loopHILHardware in the loopFIELDThe real thingThe control codeIdentical — not a port, not a rewrite, not “equivalent logic”Code runs onHost workstationThe target MCUThe target MCUThe target MCUPlant isA physics modelA physics modelReal I/O, modelled plantReal plantTiming isLogicalMeasured on targetReal-time, wiredReal-time, liveCost of a failureA re-runA re-runA rig, maybe a boardThe vehicle or the plantFAULT INJECTIONSensor dropout · link loss · actuator stuck · missed deadline — injected here, on purpose, in CINot here.A simulation you only run before a release is documentation. These suites run on every change, and a controlchange that leaves the envelope fails the build rather than the commissioning.
Worked toIEC 61131-3IEC 62443ISA-95ISA-18.2 alarmsOPC UAHow we hold to them

Have a project in SCADA & Industrial Automation?

Send the constraints. We will come back with an approach, a rough shape of the team and what it would take.