Theme: Local control with maintainable information
Quick definition
DUC, short for the Swedish term datorundercentral, is an industry term for a local programmable controller in building automation. It reads sensors, runs control and sequence logic, and drives valves, dampers, pumps and fans. The term describes a building role, not an international product class.
In context
A DUC works close to the physical process and normally continues local control if the supervisory BMS or network fails. It can expose objects, alarms, schedules and setpoints through BACnet or other protocols so operators gain a consolidated view.
For example: a ventilation unit
In an air-handling unit, the DUC measures temperature and pressure, starts fans in a safe sequence and controls a heating valve. If a sensor fails, local logic should select a safe mode and raise an alarm. The BMS presents the event but need not execute time-sensitive control.
DUC is not literally PLC
DUCs and PLCs are programmable controllers and may use similar hardware or programming principles. They are not identical terms. DUC primarily denotes a Nordic building-automation role with typical HVAC functions; PLC is a broad international industrial category. IEC 61131 addresses programmable controllers and languages, not the term DUC.
BACnet and interoperability
BACnet standardises objects and services for building automation. It can make a DUC easier to integrate, but understandable objects still need names, units, status and tested command priorities. BACnet/SC adds a modern secure IP transport; certificates, segmentation and authorisation still require governance.
Opportunity and limitations
Distributed local control provides resilience and can reduce dependency on central communications. Limitations arise when logic, tools or point lists are proprietary. An open protocol is insufficient when program backups, source code, credentials and change history are unavailable.
HubMind’s view
Specify the DUC as both controller and information delivery. Verify autonomous operation, failure modes, object model, time, alarms, backup and recovery. The next step is a witnessed communications-loss and restart test. Compare DUCs and PLCs where functions overlap, but do not let a simplified analogy replace actual requirements.
Related concepts
Sources and further reading
Scope and freshness
This page describes general Swedish use of DUC and uses BACnet and IEC 61131 for adjacent standards context. None of these sources defines DUC as literally identical to PLC. Reviewed 31 August 2026.