Twelve disciplines. One control system.
The team that scopes your project is the team that delivers it. Each discipline below is described the way we work it, including where it starts and where it hands off to the next.
SCADA Systems
Supervisory control and data acquisition sits at the centre of most of our projects, because operations decisions get made there. We build SCADA systems around a real alarm philosophy, with priorities rationalised against consequence and response time. The architecture is designed so that a single failure does not take operator visibility with it.
Scope covers architecture design, redundancy planning (hot-standby servers, network path diversity), historian configuration and the reports operations managers read. We build mainly on Ignition for its licensing model and web-based deployment. Where a client's existing asset base points elsewhere, we use Siemens WinCC or Rockwell FactoryTalk View.
PLC Programming
PLC code is where design intent meets the real plant. We write structured, consistently named and commented logic in ladder, structured text or function block, chosen to suit the platform and the skills of the team who will maintain it.
Every program is version-controlled and factory tested against a written functional description before it goes to site. It ships with a change log your own engineers can follow six months later. We work across Rockwell ControlLogix and CompactLogix, Siemens S7-1200/1500, Beckhoff TwinCAT and CODESYS-based OEM controllers.
HMI Development
An HMI earns its keep at 2am during an alarm cascade, when an operator has to decide quickly. We design screens to ISA-101 principles: greyscale process graphics, colour reserved for abnormal conditions, and no more than three clicks between any two related screens.
Work includes screen hierarchy design, alarm banner and annunciation configuration, trend and historian screens, and operator sign-off testing before go-live. We build on Ignition Perspective and Vision, Siemens WinCC, Rockwell FactoryTalk View and Beckhoff TwinCAT HMI, matching the runtime already on site.
RTU Integration
Remote terminal units keep a control system connected to assets that lack the power reliability, network backhaul or physical access of a central plant. We specify and configure RTUs for solar-powered pump stations, unmanned substations and roadside monitoring points, where the next site visit may be weeks away.
This covers protocol selection (DNP3, Modbus TCP/RTU, IEC 60870-5-101/104), power budgets for battery and solar sites, local logic that holds a safe state when comms drop, and integration into the central SCADA historian. When a site reconnects, buffered data is merged without duplicate or stale values.
Telemetry Systems
Telemetry is the wide-area network underneath every distributed asset base: cellular, radio or fibre backhaul carrying data from sites that can be a hundred kilometres apart. We design these networks from site coverage testing and build in store-and-forward buffering, so a comms outage does not lose data.
Scope typically includes radio path surveys, cellular APN and failover configuration, telemetry gateway selection, and historian architecture sized to the actual tag count and polling rate.
OT Cybersecurity
OT networks fail differently to IT networks. An untested patch can stop a pump. We work to the IEC 62443 zone-and-conduit model: control networks segmented from corporate IT, trust boundaries defined between the safety, control and supervisory layers, and monitoring tuned to flag real anomalies without burying operators in false positives.
Work includes network architecture review, firewall and DMZ configuration between OT and IT, remote access hardening to replace flat VPNs into the control LAN, asset inventory and vulnerability assessment, and incident response planning for the specific control system.
MES Solutions
A manufacturing execution system is only useful if its data matches what happened on the line. We build MES layers that read directly from PLC and SCADA data: production counts, downtime reasons, batch genealogy, and OEE calculated from actual machine states.
Typical scope covers machine-level downtime and reason-code capture, batch and lot traceability for food, beverage and regulated manufacturing, and OEE dashboards. Operators help shape the data collection from the start, which is why they trust the numbers.
Cloud Integration
Cloud integration is where we are most conservative, because the isolation of the control network matters more than any dashboard. We build one-directional edge-to-cloud pipelines using historian replication, MQTT Sparkplug B publishing or scheduled batch export. A corporate BI tool or head-office dashboard can read plant data with no write path back into the control system.
Common outcomes include multi-site executive dashboards, long-term historian archiving to reduce on-prem storage, and links to enterprise asset management or ERP systems for maintenance and inventory workflows.
Electrical Design
Control system reliability starts with the electrical design under it: switchboard layout, load calculations and protection coordination that give the PLC hardware a stable, correctly rated environment. We design low-voltage switchboards and control panels to AS/NZS 61439 and site wiring to AS/NZS 3000. Drawings are issued in a form your electrical contractor can build from without a site visit to clarify intent.
Scope covers single-line diagrams, panel layout and thermal calculations, cable schedules, protection and coordination studies, and hazardous area classification where the site requires it.
Commissioning & Testing
Commissioning is where design assumptions meet a live plant, and it is the stage most often under-scoped. We run factory acceptance testing off-site against a written test plan before anything ships. Site acceptance testing follows in stages, with loop-by-loop verification and a cutover sequence planned around your maintenance windows.
Every commissioning plan includes a documented rollback procedure, a punch list tracked to closure, and formal operator sign-off before we consider the project complete.
Control System Documentation
Documentation is usually the first thing cut under schedule pressure and the first thing your team reaches for when something fails at 3am. We treat as-built drawings, I/O schedules, network diagrams and functional descriptions as deliverables with the same priority as the working system. They are updated at each project stage, so nothing has to be reconstructed at handover.
Standard deliverables include control philosophy documents, cause-and-effect matrices, I/O schedules cross-referenced to physical terminal numbers, network architecture diagrams, and a change log covering every modification made after go-live.
End-to-End Project Delivery
Most of the services above are delivered together on a single program, under one project engineer who is accountable from the first site audit to the final as-built drawing. This is a deliberate structure. It closes the handover gaps between electrical design, controls engineering and commissioning, which is where post-handover defects commonly start.
End-to-end delivery includes program scheduling around your operational constraints, subcontractor coordination where civil or mechanical trades are involved, budget tracking against the original scope, and one point of contact from start to finish.
Tell us which of these your current system is missing.
Most engagements start with a gap in one or two of the disciplines above. We can help you find it.