Excursion alerting with named escalation
Limits are set per product and zone, with time-above-threshold logic that ignores brief spikes. An excursion alerts a named owner by app, SMS or call, escalating on a timer.
Cold Chain & Compliance
A load can hold temperature the whole way and still lose the claim.
Continuous temperature, humidity and door telemetry from cold room to delivery point, with the compliance record written while the product moves.
- 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 happens today, and what changes.
Flip between the operation as it runs now and the operation once the data is joined up.
- 01The excursion is discovered on arrival, or when the customer rejects the load.
The only decision left is who absorbs the loss.
- 02Somebody exports logs, matches them to shipments and builds the compliance pack by hand after the shipment is questioned.
- 03A reading crosses a limit at 02:00 and reaches a dashboard nobody is looking at.
No alert has an owner.
/ 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, buffering where 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 /
What cold chain & compliance gives you.
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.
Chain of custody per shipment
Readings are linked to shipment, batch, vehicle and route references from WMS or ERP, and handover points are recorded at every stage.
Compliance reports generated automatically
Per-shipment and per-site reports cover excursions, acknowledgements and corrective actions, in the format your client or authority asks for.
Storage and transport in one hierarchy
Warehouses, cold rooms and fleet share one site model, covering storage, loading and delivery.
Sensor health and calibration tracking
Battery, signal, last reading and calibration dates are tracked per probe. Stale sensors and expiring certificates raise their own tasks.
/ Use cases /
Where teams put it to work first.
Save a load in transit
Alert the on-call controller while the reefer is still recoverable, and write every call and action into the shipment record.
Answer a questioned delivery
Produce the temperature trace, route and door events for a shipment from its reference alone.
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 come from a continuous timestamped trace.
02
Logistics
Excursions reach the controller while the load can still be saved, with vehicle and route attached.
03
Compliance
Client and regulator reports are generated from the stored record.
04
IT
Shipments link to WMS and ERP references through APIs, and readings buffer at the edge when coverage drops.
/ In practice /
Three moments from a working week.
Each one starts with a signal and ends with someone acting on it. The scenarios are illustrative.
The signal
A reefer on the Dammam to 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.
/ 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 /
The numbers this produces.
Measured continuously, per asset, per site and per contract.
Excursion count
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 trace 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 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 run 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 adopt the same limits and reports, lane by lane.
/ Security & sovereignty /
Where your data lives, and who can reach it.
- In-Kingdom residency
- Built to national controls
- Isolated by tenant
- Your cloud or site
/ Built on IoT Cube /
Products already doing this.
Each one runs this solution on the shared foundation.
Built on IoT Cube
TEFCO
Saudi distributor of IoT and telematics hardware: trackers, dashcams, sensors, RFID, routers and EV chargers, fitted and supported.
Built on IoT Cube
tracking.me
AI and IoT fleet management for Saudi Arabia: routing, driver safety, predictive maintenance, RFID and tyre management.
Built on IoT Cube
Shipr
Transport management for Saudi road freight: dispatch, driver evidence, delay attribution and bilingual ZATCA invoicing.
/ Industries /
Where this solution shows up.
/ Questions /
Frequently asked.
The record is continuous, timestamped, attributable and exportable. Tell us the format your authority or client requires and we will map to it.
/ Explore more /
Other solutions on the same foundation.
See cold chain & compliance on your own assets.
Bring the hardware you already run. We will connect a sample of it and show you the operating picture it produces.