You can make every asset smart and expensive, or you can make the network smart and keep the asset cheap. We chose the network. Here is the reasoning, and what it means for cost, battery life, and coverage.
When you set out to track a fleet of assets, there is a fork in the road on day one, and the decision you make there shapes everything that follows. You can put a full cellular radio on every asset, so each one reports its own position from anywhere. Or you can put a small, cheap beacon on the asset and let the surrounding infrastructure do the reporting. Most of the market took the first road. We took the second, on purpose, and this article explains why.
Putting a radio on every asset feels like the safe choice. The asset phones home by itself, so you never depend on anything nearby. It is simple to reason about and easy to demo.
The trouble is what it commits you to at scale. A radio on every asset means a subscription on every asset, a battery budget on every asset, and a firmware surface on every asset. The device gets larger, more expensive, and more power-hungry, which means it also needs servicing. You have made the asset smart, and in doing so you have made the asset a recurring line item. Multiply that by a fleet of thousands and the connectivity bill, not the hardware, becomes the number that decides whether the deployment survives its second year.
Here is the observation that changed our design. Most industrial and cold chain assets do not wander unpredictably across open country. They move through a known set of places: a yard, a loading dock, a distribution center, the inside of a vehicle, a warehouse aisle, a customer site. The route between those places is often the part where nobody needs a live position, and the places themselves are where every meaningful event happens. An asset arrives, is loaded, crosses a threshold, waits, leaves.
If the events that matter happen at known nodes, then the intelligence belongs at the nodes, not on every object passing through them.
INTERtrack assets carry a Bluetooth Low Energy tag. It is small, it is inexpensive, and it does one thing well: it announces itself. The thinking, the connectivity, and the power sit in dual-mode gateways placed at the nodes, on gates, in vehicles, across a warehouse. The gateway hears the tags around it, adds context such as location and time, and forwards clean events to the platform over its own uplink.
The asset stays dumb and cheap. The network gets smart. That single inversion is the reason the rest of the numbers work.
Cost stops scaling with the fleet. Adding another hundred tagged assets does not add another hundred subscriptions. Connectivity is concentrated in a comparatively small number of gateways, so the per-asset cost of being tracked trends toward the price of the tag itself.
Battery life stops being a maintenance program. A BLE tag that only advertises sips power. The tags we build around are rated for well over five years in the field, which in practice means fit-and-forget. There is no fleet-wide battery-swap season, because the power-hungry components live in gateways that have mains power or a vehicle to draw from.
Complexity stops living on the asset. A cheap beacon has almost no firmware surface and almost nothing to break. When you do need to improve behavior, coverage, or logic, you touch a manageable set of gateways rather than reflashing thousands of devices in the field.
No architecture is free, and we would rather name the trade-off than pretend it away. Reading at known nodes means you get rich, reliable events where your gateways are, and silence where they are not. For assets that spend their lives moving between fixed places, that maps almost perfectly onto what you actually need to know. For the genuinely mobile leg, the same dual-mode gateways ride along on vehicles, so the coverage travels with the asset rather than being permanently welded to it.
The point is not that a radio on every asset never makes sense. It is that for the way industrial and cold chain fleets really operate, making the network smart gives you the same visibility for a fraction of the running cost, with tags you can deploy and forget. We would rather spend our engineering on the intelligence layer than on a battery you have to change.
Detecting a temperature excursion / breach is trivial. Knowing who owns it, whether it was resolved in time, and being able to prove it later is the hard part. That is where cold chain operations succeed or fail.
Read article →
Most tracking tools tell you where an asset is. INTERtrack tells you what to do about it. Here is why we built an operations layer, not another map.
Read article →
