iot
Cargo and vehicle tracking, refrigerated trailer temperature, a geofence at every customer and the waiting time logged with the time. For carriers and shippers, on the same platform, over the cell tower where there is one and over the DG satellite network where there is not.
Waiting time, temperature and security. All three end up in a contract, a guideline or a claim, and all three are settled with records, not witnesses.
Detention is set by contract: a free window at the dock, then a charge for every extra hour. Without timestamps, the claim is one word against another. The geofence logs the arrival, the start of unloading and the departure the invoice needs.
For medicines in the EU, Good Distribution Practice requires the temperature to stay within range during transport and the monitoring equipment in vehicles to be calibrated at regular intervals. In the US, the FDA sanitary transportation rule asks carriers of temperature-controlled food to show, when the shipper or receiver asks, that the agreed temperature was held.
Route deviation, an unplanned stop or ignition at the wrong hour becomes an alert for your control room or security provider, at any hour. What tracking and response a high-value load needs is set with your insurer; the tracker supplies the event.
Every trip becomes a timeline with position, temperature and every stop, ready for the customer, the insurer and the auditor.
Position, route and stops of every vehicle, and a dedicated locator on the cargo or container when it changes vehicles.
Our own temperature and door sensors in the refrigerated trailer, with continuous logging and an alert when the temperature leaves the range for longer than agreed or the door opens away from the customer. The trip report comes out ready.
A geofence at every customer and every dock: arrival, start of unloading and departure, with the time. Detention stops being an argument.
Route deviation, unplanned stops and ignition at the wrong hour become alerts for the control room or the security provider.
It goes inside the load or container and logs position, temperature and impact during the trip. If the box arrived damaged, the record shows where and when it took the hit.
REST API for TMS, ERP and security providers.
Illustrative example. Temperature ranges and waiting limits are configured per customer.
Routes, customers, type of cargo, temperature range, what your insurer and your customers require, and which trackers are already in place.
A few vehicles and customers, with the report compared against your current records for a month.
The fleet, the geofences for each customer, the temperature ranges and the control room dashboard.
Support, per-customer reports and alert tuning.
The truth about satellite. Over the cell tower and over the DG satellite network, position and temperature arrive in minutes, with the time of each reading. The tracker, the trailer temperature sensor, the door sensor and the damage logger are manufactured by us. What the survey decides is how often data is sent outside cellular coverage, which sets the cost, since each satellite message costs more, and what your insurer requires beyond that.
The record is continuous and timestamped, and the sensor can be calibrated with a certificate. Whether it satisfies your quality procedure depends on the procedure: the survey checks the range, the calibration and the report your quality team needs.
The report shows the arrival and departure time at every customer, logged by the geofence. It is evidence of fact; the charge follows your contract or tariff.
Events can flow by API to your security provider or control room. What the device needs to do comes from your agreement with the insurer.
Yes, with a locator on the load, the pallet or the container, independent of the vehicle.
An answer from an engineer, not a bot. Tell us the type of cargo, the temperature range and what your customers ask for.
Sources: EU Guidelines on Good Distribution Practice of medicinal products for human use (2013/C 343/01) · FDA Sanitary Transportation of Human and Animal Food, 21 CFR Part 1, Subpart O.