Logistics and Cold Chain
In the cold chain the real risk is not the bill, it is the stoppage. When cooling stops, stock is lost within hours, and whether a generator will actually start is known on the day it is tested, not the day it is needed.
Continuity
When the profile breaks, something happened
The daily load curve of a cold store is remarkably regular. Cooling packs cycle to a rhythm, door openings cluster at known hours, and the overnight base load barely moves.
That regularity is monitoring’s strongest asset. Overlay the profiles and the one day that diverges is visible at a glance. Divergence is a fault, a door, or a change in operations.
- Daily profiles drawn on one axis
- Overnight base load tracked separately
- The diverging day is flagged automatically
A rising base load usually means the cooling pack is cycling more often. The cause may be a failing door seal or a fouled condenser, and both appear in the profile long before they appear on a bill.
Daily Profiles
7 days overlaidStandby power
A generator is trustworthy on the day it is tested
Whether backup power works is only truly known during a real outage, and finding out then is too late. That is why generators are tested on a schedule and every test is recorded.
The panel tracks fuel level continuously and marks tests and refills on the same axis. A warning goes out when the level drops below the refill threshold, and a reminder appears when the gap between tests grows.
- Fuel level and remaining runtime
- Test and refill records on one axis
- Battery, heater and transfer switch status
Remaining capacity is written in hours, not litres. What a site manager needs is not “820 litres in the tank” but “eleven hours at full load”.
Generator Fuel
continuous measurement41%
Eleven hours at full load; a refill warning goes out below the threshold.
- last refill · 12 Aug
- test · 18 Aug
- 820L
- kalan
- 11h
- tam yükte
Continuity
A whole year in one frame
In the cold chain, continuity is proven by an unbroken record rather than a sentence. “We had five events last year” is a line in a table; the real information is where in the year those events sat and how long the quiet stretches between them ran.
The panel records every day. Seen as a whole year in one frame, the seasonal rhythm, the weekend dips and the clustering of events are read together.
- Daily cooling load across the full year
- Faults, services and tests marked separately
- The same record serves audits and customer reports
Where events cluster is not a coincidence: a fault at the summer peak usually arrives alongside a delayed service. This frame tells you when to bring the maintenance calendar forward.
The Year on Record
365 days · cooling loadlow load high load 5 işaretli gün
Control
Charging, lighting and offices move onto a calendar
In a warehouse most loads other than refrigeration can be scheduled: forklift charging points, warehouse and yard lighting, office HVAC, dock heaters.
The remote control module ties those points to the shift calendar and to hourly prices. Charging shifts to the night tariff, yard lighting follows sunset, offices come on with the shift.
- Charging points scheduled against hourly prices
- Yard lighting on the solar calendar
- Refrigeration packs stay out of control, view-only
The cold chain is deliberately outside the control scope. The panel sends no commands to refrigeration packs; their job is to be watched and, when needed, to raise an alarm.
Assistant
You can ask the assistant about the bill too
The most disputed lines on a warehouse bill are capacity overruns and reactive charges. Both result from momentary behaviour, which makes the cause hard to recall once the bill arrives.
The AI assistant makes that connection: it matches the bill line to the measurement record and tells you which day and which half hour produced it.
- Bill lines matched to the measurement record
- The hour and the cause arrive together
- The dispute file comes from the same record
The same assistant works on the cooling side, reading profile breaks, base load creep and alarm history together to say which event actually needs attention.
Assistant
from the measurement record-
Where did this month’s capacity charge come from?
- Enver
From a single day: 14 August, 06:15 to 06:45. Average demand in that half hour was 812 kW against a contracted 750 kW. Three loads coincided: refrigeration packs at full load during morning pull-down, forklift charging points that had not left the night schedule, and dock doors opening at shift start. Moving the charging schedule half an hour earlier would have broken the peak, and that rule can be defined on the remote control side.
- half-hourly demand record
- control point records
- capacity line on the bill
Which modules work in a warehouse
| Module | What it does here |
|---|---|
| Chillers and Cooling | Cooling pack efficiency, condenser and tower tracking |
| Standby Power | Fuel, test records, readiness status, monthly report |
| Energy Consumption | Area breakdown, base load, charging station load |
| Power Quality | Voltage dips and outage records |
| Bill Validation | Capacity and reactive line checks |
| Remote Control | Charging, lighting and office schedules; capacity rules |
| AI Assistant | Tying bill lines to measurement, event summaries |
When an alert is worth having
In the cold chain an alert earns its value through speed, but a noisy alerting system does more harm than a slow one: within a week nobody looks any more.
That is why thresholds are not single numbers. Dead bands and hysteresis are applied, repeats of the same event are grouped into one notification, and alerts are suppressed during planned shutdowns. The aim is not to report every deviation but to report the one that needs a response, in the first minute.
Let us measure what is happening on your site.
In a one-hour call we look at your existing setup and set out exactly which measurement points are needed and what you would be able to see.