
CLD · Logistics & Cold Chain
Field note · Logistics & Cold Chain
Cold chain: the controllers attached to the refrigeration units
It is three in the morning and a blast freezer is holding a pallet of ice cream at minus twenty-five. Nobody is in the building. The compressors cycle, the evaporator fans hum, and a small grey box on the wall decides, every few seconds, whether to keep going.
That box is a controller. It reads temperature and pressure, runs the compressors and the defrost, and holds the setpoint. It belongs to a control system as surely as the PLC on a bottling line does. In most warehouses it sits under the refrigeration contract, though, so it rarely makes the network drawing, and that gap is what this note is about.
Everything on the wall can talk
Every cold room, freezer and dock has one of these controllers. Bigger sites add a pack controller over a bank of compressors, and a supervisory unit in the plant room that gathers them all. Out on the yard, each reefer carries its own controller and a temperature logger, usually with a cellular modem so the shipper can follow the box anywhere.
Then the automation. Conveyors, sorters and automated storage each bring their own controllers, directed by the warehouse management system. In a cold store most of this meets at one gateway that collects readings from the refrigeration, the loggers and the automation, and sends them to the platform the customer logs into. That gateway is the most interesting point on the site, and the best place to listen.

Built to be reached
The monitoring is there on purpose. A customer paying for a cold chain wants to see the temperature of their goods. The contractor who services the plant needs to see the compressors. So the controllers speak to anyone who asks: a Modbus register map, an MQTT client publishing to a broker, a web page on the logger, a cloud agent on the supervisory unit.
Here is the catch. The reading and the setpoint live in the same register map, on the same port, behind the same password or none at all. Modbus has no idea who is asking. A broker that takes a temperature from a logger will also take a command for that unit from anyone who can reach it, unless someone configured it otherwise.
The path that carries a reading out is the same path that carries a setpoint in. It was only ever one path.
The contractor's door. Remote access to the refrigeration plant is usually a modem or a small VPN box fitted at installation. The contractor holds it, it reaches the supervisory unit with full write rights, and it almost never appears on the site's own asset list.
A cold store loses product quietly
When most plants have a control problem, they lose time. A cold store loses stock, and it does so without a sound. Move a setpoint three degrees. Start a defrost at the wrong hour. Raise an alarm threshold so nothing fires. The compressors keep running, the doors keep opening, and the loggers keep faithfully recording a number that is now wrong for what is inside.
Rank it by what is on the pallet. A temperature excursion is a product-loss event with a network cause. Weigh it by what the goods in that room are worth and how long they can stand the excursion, not by how clever the route in was.
And then there is the paperwork. If a logger can be written to, the record that proves the cold chain was kept could have been edited. For pharmaceuticals and food, that record is the product's passport.

Why the UAE makes it sharper
Heat. Refrigeration here runs flat out all year. There is no slack in the plant, so an excursion a cooler climate might ride out for an hour arrives faster.
Fast fit-outs. Free-zone warehouses are leased and fitted out quickly, often by whoever could start that week. The refrigeration contractor's network, the integrator's network and the office network frequently end up as one, because that was the fastest way to get the building working.
Cellular monitoring. Monitoring is usually a cloud service over a SIM. That is often the right design, and it also means there is a route from the internet to the refrigeration that never touches the site's firewall. It goes out through a modem in a cabinet the IT team may not know exists, fitted by a contractor who does not think of it as a network device.
Keep the view, change the direction
Nothing here means switching the monitoring off. The customer still sees their temperature, the contractor still sees the compressors, the loggers still log. What changes is which way each path runs.
Readings go out on a road that only goes out. The gateway reads the controllers and publishes upward, and nothing on the monitoring side can reach back down to a register. Where there is a broker, it accepts writes only from named, authenticated clients, and only on the topics those clients own. A logger's web page answers the plant network, not the office or the internet.
Setpoints come in through a different door. That door is brokered, time-boxed and logged. The contractor connects through a jump point the site controls, for a session someone on site approved, and the session is recorded. The old modem is removed or put behind that jump point.
ISA/IEC 62443-3-2 describes this neatly: the refrigeration is a zone, the monitoring is one conduit out of it, and the contractor's access is a second conduit with its own rules.
Listen at the gateway first. You learn what reports where without sending a single packet to a controller holding a room below freezing.
The first step is simply knowing what is there. A passive capture at the gateway and at the plant-room switch shows which controllers report where, which outside paths reach them, and which monitoring services could write as well as read. Then the refrigeration goes onto the same asset list as the automation, and each path is ranked by what the goods behind it are worth.
Sources
New to the vocabulary? Learn OT covers it from zero, free.
From the lab


