What we mean by programming
Our programming practice covers everything that runs on the plant floor and one layer above it. PLC code that drives motors, valves and instruments. HMI screens operators actually want to use. SCADA that gives plant managers the visibility they need without wading through alarms. MES and SQL integration that turns it all into batch records, OEE and traceability.
We write code to be read — by the next engineer, by an auditor, by us in five years. Structured text where it belongs, ladder where it makes the line easier to maintain, and tag names that match the P and ID.
Capabilities and platforms
PLC
Structured, maintainable control code
- Rockwell ControlLogix, CompactLogix, Micro800
- Siemens S7-1200 and 1500, TIA Portal
- Schneider M340, M580, Modicon
- Mitsubishi Q, iQ-R, GX Works
HMI and SCADA
Operator-first screen design
- Rockwell FactoryTalk View SE and ME
- Inductive Automation Ignition
- Schneider Citect, Wonderware and AVEVA
- Siemens WinCC Unified, WinCC Pro
MES and SQL
Batch, traceability, OEE
- Custom MES on Ignition or Wonderware
- SQL Server, PostgreSQL, historian
- OPC-UA, MQTT, Sparkplug B
- ERP integration: SAP, Pronto, MYOB Advanced
Standards
What we align to by default
- ISA-88 batch and ISA-95 enterprise
- GAMP 5 for regulated industries
- OMAC PackML for packaging lines
- Your own standards on request
How an engagement runs
Functional design
An FDS written with you and signed off before a line of code. Tag list, sequences, alarms and modes locked early.
Build and simulate
Code written and tested in emulation. Sequences run end to end before we ship a single binary.
FAT
Customer-witnessed FAT against the FDS. Defects logged, fixed, retested. You sign before we travel.
Site and SAT
Loop checks, point to point, then SAT. Operator training and runbook handed over with the keys.
What changes for you
Plants run with less unplanned downtime, more visibility into what is actually happening on the line, and code the next engineer can pick up and extend without a rewrite. The longest-running systems we have built are still in active production years later — not because we maintained them, but because we wrote them to be read.
- One engineer of record from the functional design through to handover.
- Simulated before site so the shutdown is spent commissioning, not debugging.
- Documentation issued as-built — drawings, tag list, control philosophy and software backup.
- No lock-in. Source, licences and passwords go with the handover pack.
Common questions
Will you work on someone else's code?
Yes — most of our work is brownfield. We document what is there before changing anything, and we leave the structure cleaner than we found it.
Can you work to our internal coding standard?
Default. We write to your standard if you have one and to ours if you do not. Either way, the standard goes in the project pack.
What about long-term support after handover?
We offer rolling support agreements with named engineers and SLA-backed remote response. Nothing is locked behind us; everything you need to run it yourself goes with the handover pack.
Continue exploring services
All services
Industrial vision
Smart QA and inspection. Traceability, precision and product quality across manufacturing, food and beverage and packaging lines.
View service
Consultancy
Practical advice early, before the budget is locked. Concept-to-commissioning alignment, machine and process safety, documentation.
View service
Commissioning
On-site, remote and hybrid. Every device, control loop and safety system verified before handover, anywhere globally.
View serviceNeed PLC, HMI, SCADA
on your next project?
Tell us the platform, the plant and the shutdown window. We come back with an approach, not a brochure.