LEAVE Cargo security monitoring
Cargo in transit.
Risk in view.
Connect route, access, cable integrity and communication status to a clear review and response process.
Explore the solutionMonitoring in practice
From a risk signal
to a traceable record.
Correlate route, authorization, cable and communication records to organize an evidence-led review.
Door open. Check authorization.
Door and lock changes coincide with an unplanned stop, without matching authorization. Retain location, time and activity records for review.
- Door
- Open
- Authorization
- No match
- Stop duration
- 8 min
- Last report
- 10 s
- Combined cues
- Door, lock and stop events coincide
- Permission review
- Check permitted place, time and operator
- Next action
- Contact driver and customer; retain findings
- 1Event recorded
- 2Acknowledged
- 3Response archived
This browser-local example sends no notifications.
Route monitoring
Follow the agreed route.
Surface exceptions early.
Bind jobs to planned routes, permitted corridors, stops and time windows and compare the actual journey.
- Route corridors & geofences
Configure route-specific tolerances and depot, customer and restricted-area geofences.
- Stops & job progress
Review unscheduled or extended stops and timing exceptions against road conditions and dispatch changes.
- Check location quality first
Consider accuracy, report age and successive fixes. A single drifting fix is not a confirmed deviation; retain the last valid position offline.
Within the planned corridor
Illustrative distance from route: 0.1 km; last report 10 seconds ago. Continue checking location and progress.
Access monitoring
Every opening.
With context and authorization.
Correlate door, lock, light and device events to distinguish planned handovers from potentially unauthorized access.
- Correlate access signals
Use configured door, lock, light and movement signals together; availability depends on hardware.
- Check place, time & permission
Compare events with permitted geofences, access windows, operators and jobs; flag missing or out-of-scope authorization.
- Before & after context
Retain opening and closing times, lock identity, operation source, permissions and available images.
A light change alone does not establish unauthorized opening. Review packaging, door and lock state, permissions and other evidence.
Permitted place, time and operator match
Opening occurs in the permitted depot window with a matching operation record. Record a planned handover and the closing state.
Tamper detection
When the seal changes,
keep the evidence.
Use compatible locks and devices to detect cable and device-state changes, linked to location and the active job.
- Cable integrity detection
Supported locks monitor cable-loop integrity; review interruptions against authorized unsealing and possible faults.
- Lock & device tamper signals
Where supported, ingest enclosure tamper, unexpected unlocking and removal signals and retain operation logs.
- Alerts & local records
Connected devices report alerts; supported devices buffer offline events. Keep event time separate from notification time.
Detection depends on cable circuits, sensors and firmware. The diagram is not a specification of a particular lock.
Cable intact · Sealed state recorded
Cable-loop state is normal in this example. Integrity sensing does not guarantee all cargo conditions; also review lock, door and handover context.
Signal & connectivity
Understand signal loss.
Keep the context.
Review GNSS, cellular service, heartbeat and battery for potential interference or persistent disconnection, with supporting indicators and alternative explanations.
- Separate position loss & disconnection
Show limited positioning when GNSS is lost but the network remains online. Offline devices show their last valid report.
- Cross-check several signals
Review signal changes, duration, battery and surroundings. Metal obstruction, tunnels, poor coverage and power loss can also explain disconnection.
- Buffering & reconnection
Supported devices backfill lock states and events after reconnection. Immediate delivery is not guaranteed while fully offline.
Suspected interference is a review cue, not proof. Dedicated detection requires appropriate validated hardware.
Connected; location and state updating
GNSS, cellular service and heartbeat have valid records. Show report age and device state.
Incident response
After detection,
track the response.
Connect route, access, tamper and signal events to responsible teams, review steps and recorded responses.
- Route events by risk & job
Configure notifications, escalation and ownership by event, cargo priority and region.
- Review the surrounding evidence
Review the last valid position, route, lock, permissions, sensors and available video.
- Authorized response & audit history
Follow the response plan with acknowledgment, notes, attachments and closure reasons. Remote control requires separate configuration.
Detect → Notify → Review → Record response
- 1Event detected
Device records are linked to the job and a review event is created.
- 2Under review
The responsible team reviews device, job, permissions and context.
- 3Response recorded
Review and response notes are retained. Demo completion does not establish that an actual risk is resolved.
This demo only changes local workflow state. It sends no alerts or device commands.
Evidence & handover
From sealing to delivery.
A connected security record.
Link waybill, cargo, lock identity and job with events, permissions and response records for handover review.
- Bind identity & job
Record lock and device IDs, seal state and handover staff, then compare changes at delivery.
- Retain events & data gaps
Retain collection and receipt times, location quality, backfill and responses; separate observations from conclusions.
- Connect business systems
Export task or event records by permission and connect transport, warehouse and customer systems through APIs.
CG-DEMO-1028
- Recording window
- 08:00 – 13:30
- Bound device
- LOCK-DEMO-16
- Traceable records
- Route, permissions, lock, connection
- Data completeness
- Gaps and backfilled intervals flagged
Production summaries include rule versions, exceptions, data gaps and handling records, with role-based archiving and exports.
Device selection
Match the field requirement
with the right device.
Planning your solution
Practical guidance on device selection, coverage and integration before you start.
Discuss your projectDoes an opening event prove cargo theft?
No. Review permitted locations and times, operation records, door or lock status, location and handovers. Light or communication exceptions also require device and transport context.
What information is needed for deployment?
Provide asset or packaging types, routes, handover procedures, mounting and power constraints, and events to monitor. Match tracking devices, electronic locks or other sensors with platform rules.