A district heating network delivers hot water to a whole town, but each building needs a controlled, metered connection to that network sized for its own demand. The heat substation is that connection point. Sitting in the basement or plant room of a building, it transfers heat from the network into the building's own heating and hot-water systems, meters what is used, and regulates temperature and flow locally. This page defines the heat substation, contrasts the common indirect arrangement using a plate heat exchanger with the direct alternative, describes its primary and secondary circuits and its controller and heat meter, and explains which data points a SCADA platform polls to supervise a fleet of substations remotely.
Heat Substation in one line: A heat substation is the building-level unit that connects a property to a district heating network, transferring heat from the network into the building's heating and hot-water circuits and metering the energy used. In the common indirect type a plate heat exchanger separates the network water, the primary circuit, from the building's own water, the secondary circuit, while a direct substation connects the two hydraulically. A local controller regulates the secondary temperature and flow, and a heat meter records consumption, with these values available to a SCADA platform for remote monitoring and control.
The job of a heat substation is to take heat from the shared district network and hand it to one building in a controlled way. The most common arrangement is the indirect substation, built around a plate heat exchanger. In this design the network water flows through one side of the exchanger and the building's own water flows through the other, and heat passes across the plates between them without the two waters ever mixing. This hydraulic separation is the key feature of the indirect type: the building runs its own closed loop of water at its own pressure, protected from the pressure and any contaminants of the wider network, while still drawing heat from it.
The direct substation, by contrast, connects the network water straight into the building's circuits without a heat exchanger, so the same water that circulates in the district network flows through the building's radiators. This is simpler and can be efficient, but it exposes the building to the network's pressure and water quality and couples the two hydraulically, so it is used where the network conditions suit it. The indirect approach is generally preferred in modern networks precisely because the separation makes the building independent of network pressure and lets the network operate at conditions the building's own equipment could not tolerate directly.
In either case the substation defines two circuits that meet at it. The primary circuit is the district network side, the hot water arriving from the plant and returning to it, and in an indirect substation this side passes through the primary of the heat exchanger. The secondary circuit is the building side, the water that actually circulates through the building's radiators, underfloor heating, or hot-water preparation. The whole purpose of the substation is to transfer heat from primary to secondary and to control the secondary conditions, and understanding a substation means keeping these two circuits and their temperatures and flows distinct.
Each substation carries a local controller that regulates how it draws heat. Its main task is to hold the building's secondary supply temperature at a setpoint, usually a weather-compensated one that rises as the outdoor temperature falls, by modulating a control valve on the primary side to admit more or less network water through the heat exchanger. The same controller manages hot-water preparation and often limits the return temperature to keep the network efficient. Because it regulates locally, the substation responds to the building's demand moment to moment, while its setpoints can be adjusted to serve network-wide efficiency goals.
Alongside the controller sits the heat meter, the device that records how much energy the building has consumed. A heat meter measures the flow through the substation and the temperature difference between the primary supply and return, and multiplies them over time to compute the heat delivered, which is the basis for billing the building. Beyond the accumulated energy for billing, the meter exposes instantaneous values, the current flow, the supply and return temperatures, and the current power, that are just as useful for monitoring the substation's behavior as for charging for it.
These devices make their data available over standard fieldbus protocols, and the specific values are addressed as registers. Heat meters very commonly speak M-Bus, a protocol designed for utility metering, and many substation controllers and meters also support Modbus. Through these interfaces a supervisory system can read the meter's registers for energy, flow, and temperatures, and read or write the controller's registers for the secondary setpoint and status. Knowing which register holds the supply temperature, which holds accumulated energy, and which holds the setpoint is the practical detail that turns a substation into a set of data points a SCADA platform can poll and adjust.
From a network operator's point of view there is not one substation but a fleet of them, one per connected building, spread across the whole service area, and the value of SCADA is treating them as a manageable population rather than hundreds of separate visits. For each substation a supervisory platform polls a consistent set of points: the primary and secondary supply and return temperatures, the flow, the accumulated and instantaneous heat consumption from the meter, the control valve position or command, and any fault and status flags from the controller. Read across every substation, these points give the operator the network's demand and behavior building by building.
A cloud SCADA platform such as Merobix is well matched to this because the substations are inherently dispersed, each a small remote outstation reporting its M-Bus or Modbus registers over a cellular or fixed link. Aggregating them into a hosted platform lets the operator see and manage the whole fleet from one place, without an on-site server behind each connection or at the plant. The two capabilities that matter most at fleet scale are remote setpoint tuning and fault detection: the operator can adjust a substation's secondary temperature or return-temperature limit remotely to improve comfort or network efficiency, and can be alerted the moment a substation faults or drifts rather than waiting for a resident to complain.
Fleet-wide visibility also turns the metering data into an operational tool, not just a billing record. A substation running a persistently warm return, meaning it is not extracting heat well, wastes network capacity and pumping, and comparing return temperatures across the fleet surfaces the poor performers so they can be tuned or investigated. Likewise a substation whose consumption or temperatures deviate from its neighbours in similar buildings flags a possible fault or a valve stuck open. By polling the same registers from every substation and watching them together, a cloud SCADA layer lets a heat network operator maintain comfort and efficiency across a large, distributed fleet with targeted remote action rather than blanket site visits.
An indirect substation uses a plate heat exchanger to transfer heat from the district network water to the building's own separate water, so the two circuits never mix and the building is isolated from network pressure and water quality. A direct substation connects the network water straight into the building's circuits without an exchanger, which is simpler but couples the building hydraulically to the network. Indirect substations are generally preferred in modern networks because the separation lets the network run at conditions the building's equipment could not tolerate directly.
A heat interface unit is a compact, packaged form of heat substation, typically serving a single dwelling such as an apartment, that combines the heat exchanger, control valve, controller, and often the heat meter in one wall-mounted unit. It performs the same role as a larger building substation, transferring heat from the network to the dwelling's heating and hot water and metering consumption, but scaled to an individual home. In a block of flats each dwelling may have its own heat interface unit fed from a communal connection to the network.
It polls the substation's controller and heat meter over a fieldbus, most often M-Bus for the meter and sometimes Modbus for the controller, reading registers that hold values like supply and return temperatures, flow, accumulated and instantaneous energy, valve position, and status flags. It can also write registers such as the secondary temperature setpoint to tune the substation remotely. A cloud platform aggregates these polled points from many dispersed substations into one view, enabling remote setpoint changes and fault detection across the whole fleet.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.