What is a PLC?
Technical definition
Programmable Logic Controller – the industrial control computer that reads sensors, executes control logic cyclically and deterministically, and drives actuators. The PLC is the workhorse at levels 1-2 of the automation hierarchy, usually programmed according to IEC 61131-3.
In brief
The PLC is where automation meets reality. How its program is structured and named determines whether the facility can be integrated, troubleshot and developed – for twenty years.
The Challenge
Every PLC program is a small world created by its programmer. Without a shared naming convention and program structure, the same pump gets different tag names in different cabinets, the logic becomes impossible to review and every integration with SCADA or MES requires detective work. When the original programmer leaves, the knowledge sits in the walls – literally. On top of that, ageing PLCs without security updates are a growing attack surface as OT networks get connected.
HubMind’s Methodology
We specify PLC deliveries as information deliveries: tag names according to the facility’s naming convention (preferably anchored in IEC 81346), structured program design according to IEC 61131, documented interfaces to higher-level systems and version-controlled code owned by you – not by the integrator.
In modern architectures we advocate exposing PLC data via OPC UA or MQTT with well-defined meaning – so the Engine can consume the data without custom couplings per cabinet.
Warnings & Pitfalls
The program as a black box: If you do not own the source code and documentation, you do not own your facility – vendor lock-in at the control level.
Tag chaos: Without a naming convention at the PLC layer, every higher-level system (SCADA, historian, analytics) becomes a translation exercise.
Connected without protection: PLCs were designed for isolated networks. Connecting them requires segmentation and security work according to IEC 62443.
💡Our Recommendation
Specify the naming convention: Tag structure and programming standard as an appendix in every automation procurement.
Own the code: Source code, documentation and licences are handed over and version-controlled with you.
Expose data via standards: OPC UA or MQTT with defined semantics – not raw registers.
Plan the lifecycle: Inventory the PLC fleet with age, patch status and spare part situation – before the breakdown.
FAQ
What is the difference between a PLC and a DUC? The same basic principle – the DUC is the building world’s variant, optimised for heating, ventilation and cooling. The PLC is industry’s generalist with higher demands on cycle time and determinism.
PLC or software-based control? Virtual PLCs and IEC 61499-based architectures are growing. But determinism, safety requirements and lifecycle must be evaluated per application – not per trend.
How often should PLC programs be reviewed? At every major change – and the fleet as a whole should be audited every three to five years for security, standards and documentation.
Do you know what runs in your PLCs – and who owns the code?
HubMind helps you specify control system deliveries with structure, standards and ownership – so automation remains your asset.