Theme: Control capability that remains understandable and maintainable
Quick definition
A PLC, or Programmable Logic Controller, is part of an international category of programmable controllers and associated peripherals intended to control machines and industrial processes. IEC 61131-1 identifies principal functional characteristics. A PLC reads inputs, executes logic and drives outputs, but timing and architecture still need application-specific requirements.
In context
PLC does not identify one vendor, programming language or Nordic building product. DUC is a regional term used in building automation and may describe similar control functions, but the categories are not synonyms. Intended use, characteristics, interfaces and support model determine the useful classification.
A concrete operating example
For example, on a packaging line a PLC reads photoelectric sensors and safety state, sequences conveyors and provides production status to supervisory systems. If connectivity to an analytics platform is lost, local control may still need to keep the process in its engineered safe operating state.
Program, information and interfaces
Logic is only one deliverable. Tag names, alarms, units, quality state, source code, build tools and interfaces determine whether a plant can be diagnosed and changed. IEC 61131-1 supplies general system context; detailed languages and project patterns belong to other parts and project requirements.
Opportunity and limitations
A well-structured PLC solution can provide robust local automation and intelligible data for SCADA and maintenance. It does not solve information ownership, network security or spare-parts strategy. NIST treats PLCs as OT whose changes must account for performance, reliability and physical safety.
Lifecycle questions before purchase
Who owns source code and libraries? Can a new engineer reproduce the running version? How are stops, communications loss and restart tested? Which spares and tools will be needed in ten years? These questions matter more than a generic claim of openness.
HubMind’s view
Specify a PLC as both a control system and an information delivery. Start with process consequence, safe states and ownership. Then define program structure, naming, interfaces and verification. Local control can remain stable while its information becomes useful above the controller.
Next step
Select one critical sequence and trace it from sensor to output, operator display and history. Check behaviour with an incorrect value, lost communications and a version change. Document accountability and acceptance criteria before choosing a platform.
Related concepts
Sources and further reading
Scope and freshness
PLCs under IEC 61131-1:2003 Edition 2 and as OT components in NIST SP 800-82 Rev. 3. No vendor or programming environment is prescribed. Reviewed 31 August 2026.