DUC

« Back to Glossary Index

What is a DUC?

Technical definition

Datorundercentral (Swedish term, roughly “outstation controller”) – building automation’s local control unit regulating heating, ventilation, cooling and other technical systems in a building. The DUC is the building world’s equivalent of industry’s PLC.

In brief

The DUC controls the indoor climate – and its programming and tagging determine whether the building’s data can be used for energy optimisation and analytics.

The Challenge

A property portfolio accumulates outstations from different generations, brands and contractors – each with its own tagging and programming style. When supervisory systems (BMS/SCADA) try to assemble the whole, you discover the same function has a different name in every building. Energy optimisation and AI analytics then stall at pilot stage: the data exists, but its meaning is unknown.

HubMind’s Methodology

We specify outstation deliveries against the property owner’s naming convention – not the contractor’s habit. Tags, alarm classes and function texts are defined in the procurement, and the delivery is approved only when the structure is verified. Open protocols such as BACnet or Modbus are a minimum requirement to avoid lock-in.

That way every new outstation becomes part of the Map: portfolio data can be aggregated, compared and optimised – building by building, in the same language.

Warnings & Pitfalls

The contractor’s standard becomes yours: Without your own naming convention in the tender documents, you inherit a new dialect per project.

Proprietary tools: If the outstation can only be programmed with the supplier’s locked tools and licences, you do not own your own facility.

Forgotten on the network: Outstations are connected control systems and must be part of OT security work – segmentation, inventory and lifecycle plan.

💡Our Recommendation

Your own naming convention in every procurement: Tagging and alarm classes are the client’s requirement, not the contractor’s choice.

Require open protocols: BACnet/Modbus and exportable configuration.

Verify at delivery: The structure is reviewed before final inspection – not after.

Inventory the fleet: Brand, age, protocols and access – the basis for both security and reinvestment.

FAQ

What is the difference between a DUC and a PLC? The same basic principle – the PLC is industry’s generalist with tougher cycle-time demands; the DUC is optimised for a building’s control loops and operator views.

Do all outstations need replacing to standardise? No. Start with a naming convention for new projects and refurbishments; older units are handled via data mapping until phased out.


HubMind’s related pages:

Building Automation, BMS and BACnet

PLC and Naming convention

Do your buildings speak the same language?

HubMind helps property owners specify building controls with naming conventions and open protocols – for a portfolio that can be optimised.

« Back to Glossary Index
Contact us