Excursion alerting with named escalation
Limits are set per product and zone, with time-above-threshold logic to ignore brief spikes. An excursion alerts a named owner by app, SMS or call, and escalates on a timer if unacknowledged.
Cold Chain & Compliance
A cold chain failure is not a temperature problem. It is a proof problem.
Continuous temperature, humidity and door telemetry from the cold room to the delivery point — with the compliance record produced while the product is still moving.
- Built for
- Quality, logistics and warehouse teams
- Connects
- Probes, loggers, reefers and cold rooms
- Deploys
- Sovereign cloud, private cloud or on-site
/ The shift /
What is actually happening today — and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01You find out afterwards.
The excursion is discovered when the load arrives, or when the customer rejects it. By then the only decision left is who absorbs the loss.
- 02The record is assembled by hand.
Somebody exports logs, matches them to shipments and builds the compliance pack — late, manually, and under pressure when a shipment is questioned.
- 03Nobody owns the alert.
A reading crosses a limit at 2am. It reaches a dashboard that nobody is looking at.
/ How it works /
From signal to decision in four moves.
Each step runs on the shared IoT Cube foundation, so nothing here is a separate system to maintain.
- 1
Connect every probe
Cold room probes, reefer controllers, door sensors and in-transit loggers report continuously, with readings buffered wherever signal drops.
- 2
Attach readings to the shipment
Each reading is tied to a batch, shipment, vehicle and route, so the record follows the product rather than the device.
- 3
Decide on the excursion
Product-specific limits and time-above-threshold rules separate a door opening from a real excursion, and rank it by risk.
- 4
Act while it can be saved
The named owner is alerted, escalation runs if nobody responds, and the action taken is written into the compliance record.
/ What you get /
Capability, not just visibility.
Continuous condition monitoring
Temperature, humidity and door status are sampled continuously from probes and reefer units, stored with device timestamps, and buffered at the edge when connectivity drops.
Chain of custody per shipment
Readings are linked to shipment, batch, vehicle and route references from WMS or ERP. Handover points are recorded, so custody is clear at every stage.
Compliance reports generated automatically
Per-shipment and per-site reports are produced from the stored record, including excursions, acknowledgements and corrective actions, and exported in the format your client or authority asks for.
Cold rooms and vehicles together
Warehouses, cold rooms and fleet sit in one site hierarchy, so the same product can be followed from storage to loading to delivery.
Sensor health and calibration tracking
Battery, signal, last reading and calibration dates are tracked per probe. Stale sensors and expiring certificates raise tasks before they weaken the record.
/ Use cases /
Where teams put it to work first.
Save a load in transit
Alert the on-call controller while a reefer is still recoverable, and write every call and action into the shipment record.
Answer a questioned delivery
Produce the full temperature trace, route and door events for a shipment from its reference, without rebuilding it by hand.
Monitor cold rooms overnight
Escalate door-open and out-of-range alarms to a named person out of hours, until someone acknowledges them.
Keep sensors audit-ready
Track calibration dates, battery and last reading per probe, and raise tasks before a weak sensor weakens the record.
/ Benefits by team /
Every team gets a different answer from the same record.
01
Quality
Batch decisions are made from a continuous, timestamped record rather than a downloaded logger and an assumption.
02
Logistics
Excursions reach the controller while the load can still be saved, with vehicle and route already attached.
03
Compliance
Client and regulator reports are generated from the stored record, so an audit becomes an export.
04
IT
Shipments link to WMS and ERP references through APIs, and readings buffer at the edge when coverage drops.
/ In practice /
What it looks like on an ordinary Tuesday.
Three moments where the platform earns its place. Scenarios are illustrative.
The signal
A reefer on the Dammam–Riyadh run climbs past 5°C at 02:14 and keeps rising.
- 1
The platform confirms the rise is sustained and alerts the on-call logistics controller.
- 2
The controller calls the driver, who finds the unit has tripped and restarts it.
- 3
Readings, calls and actions are written to the shipment record as it happens.
The outcome
The load is assessed with a full record instead of rejected on arrival without one.
/ Technology /
Four layers. One record underneath.
Device-neutral at the bottom, open at the top, and sovereign all the way through.
01
Devices in the field
Keep the hardware you already have
- Temperature and humidity probes
- Door sensors
- Reefer units
- Cold room controllers
- In-transit loggers
- Gateways
02
Connectivity & protocols
Any carrier, any protocol
- MQTT
- LoRaWAN
- NB-IoT / LTE-M
- BLE
- Modbus RTU / TCP
- 4G/5G via any Saudi carrier
- Reefer telematics APIs
03
IoT Cube platform
Sovereign, multi-tenant, AI-neutral
- Time-series store
- Rules & alerting engine
- Edge buffering
- Workflow automation
- Reporting & exports
- Role-based access & audit
04
Your systems of record
Data lands where decisions are made
- WMS
- ERP
- Quality and QA systems
- Customer portals
- Regulatory reporting
A national distributor moved from manual compliance packs to records generated continuously. A questioned shipment went from days of reconstruction to a single export.
Story pending customer confirmation/ What you measure /
Numbers that replace arguments.
The indicators this solution produces continuously, per asset, per site and per contract.
Excursion count
Number of confirmed out-of-range events, by site, route, vehicle and product.
Time to acknowledge
How long from an excursion alert to a named person accepting it.
Time out of range
Cumulative minutes a product spent outside its limits, per shipment or batch.
Record completeness
Share of shipments with an unbroken, timestamped record from dispatch to delivery.
Sensor health
Probes that are offline, low on battery or past their calibration date.
Report turnaround
Time taken to produce a compliance or client report when a shipment is questioned.
/ Rollout /
Start with one decision. Scale what works.
- Phase 1
Map products, limits and duties
We list sites, vehicles, sensors and products, and agree temperature limits, escalation owners and the reports your clients and authority expect.
- Phase 2
Connect one lane end to end
A cold room, its loading bay and the vehicles on one route are connected, with shipments linked from WMS or ERP.
- Phase 3
Prove the alert and the record
Real excursions are handled through the escalation path, and quality signs off that the generated report stands up to an audit.
- Phase 4
Extend across the network
Remaining sites, fleets and product lines join on the same rules and reports. Weeks, not quarters, per wave.
/ Security & sovereignty /
Sovereign is a place, not a promise.
In-Kingdom residency
Data stored and processed inside Saudi Arabia, on infrastructure you can name in a tender.
Built to national controls
Designed to align with NCA cybersecurity controls and the Personal Data Protection Law.
Isolated by tenant
Tenant isolation, role-based access and a full audit trail across users, actions and devices.
Your cloud or site
Deploy into a sovereign cloud, your private cloud or on-premises without becoming a different product.
/ Built on IoT Cube /
Runs on the platform, not beside it.
Products already running this solution on the shared foundation.
Built on IoT Cube
TEFCO
Saudi IoT and telematics hardware — GPS tracking, RFID, AI cameras, sensors and RTLS, installed and supported.
Built on IoT Cube
tracking.me
Saudi AI and IoT fleet tracking, telematics, RFID, tyre management and connected mobility solutions.
Built on IoT Cube
Shipr
All-in-one logistics for transportation management, fleet maintenance, freight forwarding and customs operations.
/ Industries /
Where this solution shows up.
/ Questions /
Frequently asked.
Is the reporting acceptable to regulators and clients?
The record is continuous, timestamped, attributable and exportable. Confirm the specific format your authority or client requires and we will map it.
What happens where there is no signal?
Data is buffered at the edge and uploaded when connectivity returns. The record has no gaps.
Can we monitor cold rooms and vehicles in one place?
That is the point of doing this on a platform rather than in two products.
Can the records support our SFDA obligations?
The platform keeps the continuous, attributable record that storage and transport requirements depend on. Reporting is mapped to your SFDA requirements and your licence type, which we confirm with you during discovery.
Do we have to replace our loggers and reefer units?
Usually not. Existing probes, loggers and reefer controllers can report through gateways or their own telemetry. New sensors are added only where the record has gaps.
Can shipment data link to our WMS and ERP?
Yes. Shipments, batches and delivery points come in from WMS or ERP, and the temperature record goes back out against the same reference through APIs or scheduled exports.
/ Explore more /
Other solutions on the same foundation.
Fleet & Asset Operations
Know where assets are, how they are performing, and where attention is needed.
Driver Safety & Journey Management
Connect journeys, behaviour, safety events and operational response.
Predictive Maintenance
Use condition and usage data to move from failure response to planned work.
Bring us the decision that takes too long today.
Start with the problem. IoT Cube provides the foundation underneath.