Fleets do not keep their connectivity provider for long. According to one recent market study reported by Automotive Fleet in March 2025, fleets using telematics solutions shift to another provider about every four to four-and-a-half years. That is a short cycle for something that has to be physically installed in every vehicle. It also means most fleet IoT deployments are not a first install at all. They are a replacement, done while the trucks keep running, by a team that already got burned once.
This guide is the calendar. It walks through the seven phases of a transportation IoT rollout, gives typical durations for a 100-vehicle and a 1,000-vehicle fleet, and then lists the six things that most often add weeks. Every duration here is a typical range drawn from how these projects usually run. None of it is a guarantee, and your own numbers will move with the device you pick and the installers you can book.
A quick primer before the phases. An IoT transportation solution is four things working together: a device in or on the vehicle (a tracker, a dashcam or a sensor), a cellular SIM or eSIM inside that device, a data plan that lets the SIM send data over a mobile network, and the software platform that turns that data into a map, an alert or a report. Fleet telematics is the general term for the data a vehicle sends this way: location, speed, engine status, driver behavior. Video telematics is the dashcam version of the same idea, where the device also records and uploads footage. Deploying the solution means getting all four parts working on every vehicle, not just buying them.
What a Fleet IoT Rollout Involves (and a Realistic Timeline at a Glance)
The table below is the whole transportation IoT rollout in one view. Durations are typical for a mid-size fleet where the device is already certified for the networks you plan to use, and they assume phases overlap where they can. Treat them as planning ranges, not promises.
| Phase | What happens | Typical duration, 100 vehicles | Typical duration, 1,000 vehicles | What makes it longer |
|---|---|---|---|---|
| 1. Define requirements | Decide what each device must send, how often, from where, and how many SIMs you need now and in a year | 1 to 2 weeks | 2 to 4 weeks | Several device types, several countries, no owner for the decision |
| 2. Choose the network technology | Pick LTE-M or NB-IoT for battery trackers, LTE Cat-1 or Cat-4 for dashcams and live tracking | 1 week (overlaps with Phase 1) | 1 to 2 weeks | A device that is not yet certified on the network you want |
| 3. Choose the SIM | Multi-network, multi-IMSI, single-network or eUICC eSIM; agree the plan and order test SIMs | 1 to 3 weeks | 2 to 6 weeks | Procurement and contract review, cross-border profile questions |
| 4. Verify coverage on real routes | Run a 10 to 20 vehicle pilot on your actual corridors, depots and border crossings | 2 to 4 weeks | 4 to 8 weeks | Coverage surprises at depots, a change of SIM type after the pilot |
| 5. Set up the connectivity platform | Bulk activation, SIM groups, usage alerts, integration with the fleet software | 1 to 2 weeks | 3 to 6 weeks | Custom integration with the fleet platform, an internal IT queue |
| 6. Secure the deployment | Private APN or VPN, device rules, IMEI lock | 1 week | 2 to 4 weeks | Private APN provisioning, security sign-off |
| 7. Install in waves and monitor | Installer scheduling, per-vehicle sign-off, a 30-day data check | 2 to 4 weeks of installs, then 30 days of monitoring | 8 to 16 weeks of installs, then 30 days of monitoring | Installer availability, vehicles that are on the road when the crew arrives |
| Total, end to end | About 2 to 4 months | About 5 to 9 months | Device lead time is the single biggest swing factor |
Two things stand out from that table. First, the SIM and data plan are rarely the long pole. Second, a 1,000-vehicle fleet IoT deployment is not ten times slower than a 100-vehicle one, because most of the planning happens once. Installation is the part that scales with vehicle count, and that is where the calendar stretches.
Phase 1: Define Requirements: What the Devices Must Send, How Often, and From Where
Start with the data, not the hardware. A connectivity plan for vehicle tracking is priced on how much data each device sends per month, so the first job is to write that number down for every device type you plan to fit. A GPS tracker that reports position every 30 seconds sends a few megabytes a month. A dashcam that uploads event clips sends hundreds of megabytes, and one that streams on demand can go past a gigabyte. Mixing the two on one plan without knowing the split is the most common way an IoT for fleets budget goes wrong in month two.
Then decide where the data gets processed, because that changes the plan. Edge processing means the device does some of the thinking itself, for example a dashcam that detects harsh braking on board and only uploads the clip. Cloud processing means the device sends everything and a server does the work. Edge devices send less data and tolerate a weak signal better; cloud-first devices need a steadier connection and a bigger plan. For real-time fleet tracking, most operators end up with a mix: edge for video, cloud for position.
The last requirements question is growth. A fleet that needs 100 SIMs today may need 500 next year, and the person asking for the first batch is often not the person who will manage the next one. Write down the expected count at 12 months, because it affects the plan tier, the platform setup in Phase 5 and the number of SIMs you keep in reserve.
Phase 2: Choose the Network Technology: LTE-M and NB-IoT for Battery Trackers, LTE for Dashcams
Transportation IoT rollouts usually involve two kinds of device with two different needs, and picking one network technology for both is a mistake.
Powered devices, such as dashcams and wired vehicle trackers, want bandwidth. They run on LTE, which is the standard 4G mobile network, and typically on a device class called Cat-1 or Cat-4. Those class numbers describe how fast the modem can send and receive. Cat-1 is enough for position updates and event clips. Cat-4 is what you need for live video. Some fleets are moving dashcams to 5G, but for most transportation IoT rollouts today LTE Cat-1 or Cat-4 is the sensible choice and the one with the widest device selection.
Battery devices, such as trailer trackers, container sensors and anything on an unpowered asset, want the opposite. They need to sleep for hours, wake up, send a small packet and go back to sleep on a battery that lasts years. That is what LPWA is for. LPWA stands for low-power wide-area, and in cellular terms it means two technologies: LTE-M and NB-IoT. LTE-M (Long Term Evolution for Machines) is a cut-down version of 4G built for devices that move, so it hands over between cell towers properly and supports voice if needed. NB-IoT (Narrowband IoT) uses an even narrower slice of the network, reaches further into basements and metal enclosures, and uses even less power, but it handles movement poorly and is best for things that mostly sit still. For a trailer that spends its life on the highway, LTE-M. For a sensor in a yard, NB-IoT.
Two practical notes for fleet telematics connectivity. First, LTE-M and NB-IoT roaming across borders is less mature than ordinary LTE roaming, so if your trailers cross into Canada or Mexico, confirm the SIM provider’s LPWA coverage per country before you buy the trackers. Second, the physical conditions inside a vehicle matter. A SIM in an engine bay or on a trailer chassis sees vibration, heat and cold that a phone never does, so specify an industrial-grade SIM with an operating range that covers your climate. The plastic in a consumer SIM is not built for a decade under a truck.
Phase 3: Choose the SIM: Multi-Network, Multi-IMSI or eUICC eSIM, and What Each Does to the Schedule
This is the phase where IoT solutions for transportation are most often over-thought, so here are the plain definitions and then a rule of thumb.
A multi-network SIM is one that can connect to more than one carrier’s network in the same country and switch when one is weak. In practice it does this through roaming agreements: the SIM belongs to one home operator and is allowed onto partner networks. For a fleet, the effect is that a truck losing one carrier’s signal on a rural stretch picks up another carrier’s instead of going dark. What it does to a fleet IoT deployment schedule is the important part: a multi-network SIM shrinks the coverage pilot in Phase 4, because you are testing whether any of several networks reaches a location rather than whether one specific network does.
A multi-IMSI SIM takes that a step further. IMSI stands for International Mobile Subscriber Identity, which is the number that identifies a SIM to a network. A multi-IMSI SIM stores two or more of these identities, each tied to a different operator, and a small program on the SIM picks the one that fits the country the vehicle is in. The practical benefit is that the device looks like a local subscriber in each country instead of a permanent roamer, which matters for cross-border fleets because some countries restrict permanent roaming. Our own multi-IMSI IoT data plans page explains the mechanics if you want the detail.
Intelligent (steered) roaming is different again, and people often confuse it with multi-IMSI. With steered roaming, the SIM keeps one identity, and the home operator’s network decides which partner network the device should attach to, usually based on cost and quality. The device does not change who it is; the network changes where it is sent. It is simpler and cheaper, and for IoT for fleets that stay inside one country it is usually enough. Multi-IMSI is what you buy when the vehicles cross borders regularly and you cannot afford a country that blocks permanent roaming.
eUICC is the fourth option, and it changes the maintenance side of the calendar more than the install side. eUICC stands for embedded Universal Integrated Circuit Card, and it is the technology that makes an eSIM programmable. An eSIM is simply a SIM that is soldered into the device or delivered as a chip that can be rewritten. With eUICC, the SIM profile (the identity and the plan) can be downloaded and switched over the air, so if you change provider in year four, nobody has to visit 1,000 vehicles with a pin tool. The trade-off is that eSIM profile management involves a bit more setup at the start, and the device must support it.
Then there is the single-network SIM, which the industry tends to talk down and which deserves a fairer hearing. One of our video telematics customers, SureCam, chose a single-network IoT SIM on purpose. Their dashcams run across the US, Canada and Mexico, and a single-network plan gave them the predictability and price they wanted on a footprint they had already verified. We tend to describe them as a bit of a unicorn, because most fleets do want multi-network, but the point stands: if your routes are known and one carrier covers them, the simplest plan is often the right one. You can read the video telematics case study for the detail on how that deployment runs.
The rule of thumb Trafalgar Wireless gives fleet operators asking which IoT transportation solution fits: a single-country fleet on fixed routes can run on steered roaming or even a single network; a single-country fleet on variable routes wants multi-network; a cross-border fleet wants multi-IMSI; and any fleet planning to keep the devices longer than four years should insist on eUICC so the next provider switch is a software job. Settle the physical form factor at the same time. A surprising number of quotes stall because the buyer says micro SIM when they mean eSIM, or asks for an eUICC card and then discovers the device only takes a plastic 3FF. Confirm the form factor with the device maker before the request for quotes goes out, not after.
Phase 4: Verify Coverage on Your Actual Routes, Not the Map
A coverage map shows where a carrier’s model says a signal exists outdoors. It does not show the inside of a metal-roofed depot, the bottom of a loading dock, a trailer yard behind a hill, or a border crossing where two countries’ networks fight over the device. That gap is why a pilot phase exists, and it is the phase most often skipped by fleets in a hurry.
Run the pilot with 10 to 20 vehicles chosen for variety, not convenience. Put trackers on the trucks that run the worst routes, the ones that park at the depot furthest from town, and the ones that cross a border if any do. Run it for two to four weeks so you catch a weekend at the yard, a run through the rural corridor, and at least one full cycle of whatever your normal schedule is. For a 1,000-vehicle fleet IoT deployment, four to eight weeks is more realistic because you have more route types to cover and more depots to visit.
Log four things per vehicle per day: the percentage of expected check-ins that arrived, the network each check-in used, the number of times the device switched network, and the data actually consumed. The first number tells you whether fleet telematics connectivity is good enough on that route. The second and third tell you whether your multi-network SIM is doing its job or bouncing between carriers in a way that drains battery. The fourth tells you whether your Phase 1 data estimate was right, which is the single cheapest thing to learn before you order a thousand plans.
For freight corridors that cross into Canada or Mexico, watch the border specifically. A SIM that behaves perfectly in Texas can sit for minutes on the Mexican side while it attaches to a new network, and if the device times out and reboots in that window you will see a hole in the trace. Multi-IMSI SIMs handle this best because they switch identity to a local profile; ordinary roaming SIMs handle it acceptably; a single-network domestic SIM will not handle it at all, which is fine only if the vehicle never crosses.
Some routes genuinely have no cellular signal, and no SIM can fix that. Remote mining roads, long stretches of the northern plains, parts of the Rockies. For those, the honest answer is a satellite fallback device on the vehicles that run those corridors, paired with the cellular tracker for everywhere else. Budget it as a separate line item for a minority of vehicles rather than assuming cellular alone covers 100 percent of the map.
Phase 5: Set Up the Connectivity Platform: Bulk Activation, Groups, Alerts, and the Fleet-Software Integration
The connectivity management platform is the web tool where SIMs are activated, grouped, monitored and suspended. It is separate from your fleet software (the map and reporting tool your dispatchers use), and it is worth understanding the difference because IoT connectivity for transportation lives or dies in this layer once the trucks are installed.
Set up the platform before the first wave of installs, not after. That means three concrete jobs. Bulk activation: loading the SIM identifiers as a batch and moving them into the right lifecycle state, rather than clicking through 1,000 SIMs one at a time. SIM lifecycle states are the stages a SIM passes through: inactive (delivered but not yet billing), test (a limited free allowance while installers verify the device), active (billing on the plan), suspended (paused, for a vehicle that is off the road or a device that has been stolen) and retired (permanently closed). A platform that lets installers activate a SIM into the test state on the day of install and lets you flip the whole group to active at the end of the wave saves real money, because you are not paying for a plan on a truck that is still waiting for its camera.
Groups and alerts come next. Group the SIMs by depot, by vehicle type or by wave, whichever matches how your operations team thinks. Then set usage alerts per group: a warning at 80 percent of the plan allowance and a hard cap if you want one. In any transportation IoT rollout a dashcam stuck in an upload loop can burn a month’s data in a day, and the alert is how you find out before the invoice does.
Integration with the fleet software is the job that most often lands in someone’s queue and stays there. Most fleet platforms take the SIM’s data through an API, which is a standard way for two pieces of software to talk to each other, and the connectivity platform exposes a matching API so that a SIM’s status and usage can show up next to the vehicle it lives in. For a 100-vehicle fleet this is often a one-week configuration task. For 1,000 vehicles with a custom fleet platform it can be three to six weeks, mostly waiting on your own IT team.
To optimize SIM management for a large fleet across countries, the platform is also where you enforce the SIM choice from Phase 3: which profile a group uses, which countries a group is allowed to roam in, and what happens when a device leaves its expected region. Set those rules once per group and let the platform apply them to every new SIM added later.
Phase 6: Secure the Deployment: Private APN, VPN and Device Rules
Security in a fleet IoT deployment is mostly about one question: does device data cross the public internet or not? The tool that answers it is the APN.
APN stands for Access Point Name. It is the gateway a SIM uses to get from the mobile network onto the internet. A public APN sends your device traffic out to the open internet like a phone. A private APN is a gateway dedicated to your organization, so device traffic goes from the SIM into a closed route straight to your servers and never touches the public internet. For a fleet, the practical benefits are that the devices cannot be reached from outside, a stolen SIM is useless in another device, and the data from 1,000 dashcams arrives at your platform through one controlled door.
A VPN (virtual private network) can be layered on top or used instead for smaller deployments. A VPN encrypts the traffic between the device and your network so that even if it crosses the public internet, nobody can read it. The request we see most often from fleet operators planning IoT connectivity for transportation is a combination: a few dozen SIMs on a private APN, with a VPN between a handful of them for a specific secure link, and a modest data allowance per SIM. That is a normal, reasonable shape for a security setup and any provider you talk to should be able to quote it without drama.
Device rules are the last piece. IMEI lock ties a SIM to one device’s hardware identity (the IMEI is the serial number of the modem), so the SIM stops working if someone moves it. Country and network restrictions per group stop a SIM from roaming somewhere it should not be. Suspension rules move a SIM to suspended automatically if usage spikes past a threshold. None of these take long to set up, and all of them are cheaper than the incident they prevent.
Time-wise, a private APN typically adds one to four weeks to a transportation IoT rollout, because the provider has to provision the gateway and your IT team has to agree the addressing. Start it in parallel with Phase 5 rather than after it. Our post on private APNs for secure IoT covers the setup in more depth if your security team wants the technical version.
Phase 7: Install in Waves and Monitor the First 30 Days
Installation is where the calendar of a fleet IoT deployment becomes physical. A dashcam install with power, camera mounting and a check of the upload takes an installer somewhere between 45 minutes and two hours. A plug-in tracker takes ten minutes. A trailer tracker with a battery pack and a mounting bracket sits between the two. Do the arithmetic for your own device before you promise a completion date, because a two-person crew fitting dashcams will get through roughly six to ten vehicles a day, and the vehicles have to be parked for it.
Wave sizing follows from that. For 100 vehicles, two or three waves of 30 to 50 spread across two to four weeks lets you fix what the first wave teaches you before the second starts. For 1,000 vehicles, waves of 100 to 150 across eight to sixteen weeks are typical, organized by depot so the crew is not driving between sites. Never install the whole fleet in one push. The first wave always turns up a mounting position that blocks the camera, a power cable that does not match a vehicle model, or a SIM that was left in inactive by mistake.
Define what done means for one vehicle in a fleet IoT deployment, in writing, before the first install: the device is powered, the SIM shows as active in the connectivity platform under the right group, the fleet software shows the vehicle’s position within the expected interval, and a test event (a hard brake, a door open) arrives end to end. An installer signs each vehicle off against that list. Without it, done drifts to mean the camera is screwed in.
Then watch the first 30 days for the whole wave. Three numbers matter. The check-in success rate per vehicle, which should sit above 98 percent on the routes the pilot passed. The data consumption per SIM against the plan, which tells you whether the plan tier from Phase 1 was right. And the number of SIMs that needed a support ticket, which tells you whether the installer sign-off actually caught the problems. If any of the three is off for one depot and not the others, the problem is almost always physical (a mounting position, a depot with a metal roof), not the plan.
What Sets the Schedule: The Six Things That Most Often Add Weeks
Every one of these has pushed a fleet IoT deployment past its planned date. They are listed roughly in order of how much damage they do.
Device lead time and certification. Trackers and dashcams are ordered from a manufacturer and typically ship in four to twelve weeks, longer for custom variants. If the device has not already been certified for the networks you plan to use (carriers require this, and in the US it involves a body called PTCRB alongside FCC approval), add eight to sixteen weeks that nothing on the connectivity side can shorten. Ask the device maker for its certification list before you sign, and prefer a device that is already approved on the networks in your Phase 4 pilot.
Cross-border profile and regulatory rules. Some countries limit how long a foreign SIM may roam, and some require a local identity for devices that stay. If your trucks cross into Mexico, Canada or further, the SIM choice in Phase 3 has to account for it, and the provider may need two to four weeks to set up the right profiles. Discovering this after the pilot means rerunning part of the pilot.
Installer availability. Installation crews are booked weeks out in busy seasons, and a fleet cannot park half its vehicles on a weekday. The realistic install rate for a mid-size fleet is a few dozen vehicles a week, and that is the number that turns a 1,000-vehicle fleet IoT deployment into a multi-month project regardless of how fast the SIMs arrive.
Integration with the fleet platform. The connectivity platform and the fleet software have to talk, and the work usually lands with your own IT team or the fleet software vendor. A standard integration takes days; a custom one can take a month, mostly waiting in a queue. Start the request in Phase 1 so it is ready by Phase 5.
Coverage surprises in the pilot. A depot that turns out to sit in a signal hole, a route with a dead stretch, a border crossing where devices reboot. Each one is usually fixable (a different antenna position, a multi-network plan instead of a single-network one, a satellite fallback for a few vehicles), but each fix means part of the fleet IoT deployment pilot runs again. Budget two extra weeks for it and be pleased if you do not need them.
Procurement and contract steps. The buyer’s own purchasing process. The request for quotes, the comparison of three or four providers, the legal review of the plan terms, the purchase order. Two to six weeks is typical, and it sits squarely on the critical path because test SIMs cannot ship until the paperwork does. If there is one place a fleet can pull its own timeline in, it is here: agree the plan terms while the pilot runs, not after.
Together, these six are also most of the total cost of ownership of IoT transportation solutions. TCO means everything the solution costs over its life, not just the plan price, and for a fleet the lines are: the device, the SIM, the monthly data plan, roaming charges, platform fees, installation labor, downtime while a vehicle is off the road for an install or a repair, and SIM swaps when a device or a provider changes. The plan price is usually the smallest of those. Installation labor and downtime are usually the largest, which is why the wave plan in Phase 7 matters more to the budget than the price per megabyte.
Cost and Uptime: How to Compare Plans and SLAs Before You Commit
By the time three or four quotes for IoT connectivity for transportation are on the table, most fleet operators compare them on the price per SIM per month and pick the lowest. That comparison misses two things: how the plan behaves when your usage is uneven, and what the provider actually promises when something goes wrong.
| Pricing model | How it works | Fits best |
|---|---|---|
| Per-SIM fixed allowance | Each SIM gets its own monthly data cap at a fixed price | Uniform devices with steady, predictable usage such as plug-in trackers |
| Pooled (or dynamic pooled) | All SIMs in a group share one pool of data; a busy SIM borrows from a quiet one | Mixed fleets where dashcams and trackers sit on the same plan, or usage that varies by season |
| Pay as you use | You pay for the data actually consumed each month, sometimes with a small platform fee per SIM | Pilots, seasonal fleets, and low-volume devices where a fixed cap would mostly go unused |
| Tiered or committed volume | A lower rate in return for committing to a minimum SIM count or term | Large fleets with a stable count that can commit for a year or more |
Pooled plans are the ones to ask about for IoT solutions for transportation that run more than one device type. A dashcam that has a bad month and a tracker that barely moves average out, and you stop paying overage on one while wasting allowance on the other. Roaming is the other line to read carefully: ask whether the quoted rate already includes the countries in your pilot or whether roaming is billed on top, and get the per-country rate in writing for anywhere your vehicles go.
An SLA (service level agreement) is the written promise about how reliable the service will be and what happens when it is not. A useful SLA for fleet telematics connectivity states four things: an uptime figure for the provider’s own core network and platform (commonly quoted as a percentage such as 99.9 percent, and the SLA should say what is excluded, because the provider does not control the radio network in a field), how that uptime is measured and over what period, what service credits apply if it is missed, and the support response times by severity, ideally with a named contact rather than a ticket queue.
Two more terms help you compare providers on reliability rather than on brochure language. MTBF is mean time between failures: the average stretch the service runs before something breaks. MTTR is mean time to repair: the average time from a failure to the fix. A provider with a long MTBF and a short MTTR is what you want, and the MTTR is the one to press on, because it is the number that decides how long your fleet sits blind when something does go wrong. Ask how the provider detects a SIM that has stopped reporting, who gets alerted, and how long a replacement profile or SIM takes to reach a vehicle.
Return on investment for IoT connectivity for transportation is then a plain sum. On the cost side, the TCO lines above. On the benefit side, the things fleet operators actually measure: fewer at-fault claims where dashcam footage exists, lower fuel from route and idling data, fewer breakdowns caught by engine alerts, and less time spent on the phone finding out where a trailer is. The connectivity plan is a small part of the cost side and the thing that makes every line on the benefit side possible, which is the reason to pick it on reliability and fit rather than on the last cent per SIM.
How Trafalgar Wireless Supports Fleet Rollouts
We supply the connectivity layer of the seven phases above, and that shapes where we fit. Trafalgar Wireless supplies the IoT SIMs, eSIMs and data plans for fleet, transportation and logistics operators, plus the IoT Suite platform used to activate, group, monitor and suspend them, and we support the deployment through the people who sold it rather than through a call center.
In practice that means a few specific things during a transportation IoT rollout. During Phase 3 we will tell you plainly which SIM type fits your routes, including when a single-network plan is the right answer, because we have customers running exactly that. During Phase 4 we provide test SIMs so the pilot runs on the real plan you will buy. During Phase 5 we set up bulk activation and lifecycle states in IoT Suite with you, and we will show you the platform’s back end live before you commit, because we think a buyer should see the real tool and not a slide about it. During Phase 6 we provision private APNs and support VPN configurations for the operators who need them. And across all of it, your account manager is also your service manager.
The two public IoT transportation solutions we point people to are both video telematics companies, which is the fastest-growing corner of transportation IoT and the one where connectivity matters most, because a dashcam that cannot upload is a very expensive mirror. SureCam runs network-connected dashcams with GPS tracking across the US, Canada and Mexico on our connectivity and our management platform. HD Fleet runs fleet tracking dashcams on our data plans, and their case study includes a video from their CEO on the coverage, service and value the deployment delivered. Neither of them needed a bespoke solution. They needed reliable plans, a platform that automated the administrative work, and someone who answered the phone.
Frequently Asked Questions
How long does it take to deploy IoT tracking across a 500-vehicle fleet?
For a 500-vehicle fleet IoT deployment, a typical end-to-end timeline is four to six months, assuming the device is already certified and the fleet software integration is standard. The two biggest variables are device lead time (four to twelve weeks from order, longer if certification is still needed) and installer capacity (a few dozen vehicles a week for dashcams, faster for plug-in trackers). The SIMs and data plans are rarely the part that sets the date.
Do I need a pilot if the provider gives me a coverage map?
Yes. A coverage map shows where a signal exists outdoors at the carrier’s modelling level, not inside a metal-roofed depot, at the bottom of a loading dock, or at a border crossing. A 10 to 20 vehicle transportation IoT rollout pilot on your real routes over two to four weeks is the only way to find those holes before you have 500 trucks depending on them.
Should I use an eSIM or a physical SIM for vehicle trackers?
If the device will stay in service longer than four years or will cross borders regularly, use an eUICC eSIM so the network profile can be changed over the air without touching the vehicle. If the device is short-lived, stays in one country, or simply does not support eUICC, a physical industrial-grade SIM is fine for fleet telematics connectivity and usually cheaper to start with.
Can one SIM cover the US, Canada and Mexico?
Yes, with the right plan. A multi-network or multi-IMSI IoT SIM can attach to partner networks in all three countries, and a multi-IMSI SIM will switch to a local identity as the vehicle crosses so it is not treated as a permanent roamer. Trafalgar Wireless supplies IoT SIMs and data plans that cover North America and beyond for fleet operators, and SureCam’s dashcams run across all three countries on them. Confirm the per-country rates and any LTE-M or NB-IoT coverage limits before you buy the devices.
What is the difference between multi-IMSI and eUICC for a fleet?
Multi-IMSI is about which network identity the SIM uses right now: it stores several identities and picks the best one for the country it is in, which helps cross-border fleets. eUICC is about changing the SIM’s profile over its lifetime: it lets you download a new provider profile remotely, which helps when you switch providers or plans years later. A fleet can use both on the same eSIM.
What should a connectivity SLA include?
An uptime figure for the provider’s core network and platform with the exclusions spelled out, the method and period used to measure it, the service credits that apply if it is missed, and support response times by severity with a named contact. For fleet telematics connectivity, ask for the provider’s MTTR (mean time to repair) as well, because that is the number that decides how long your fleet is blind when something fails.
Key Takeaways
- The SIM is rarely the long pole. Device lead time, certification, installer capacity and your own procurement usually set the date for IoT transportation solutions, not the data plan.
- Plan for two device classes. LTE Cat-1 or Cat-4 for dashcams and powered trackers; LTE-M for battery trackers that move; NB-IoT for sensors that mostly sit still.
- Match the SIM to the routes. Single-network or steered roaming for fixed domestic routes, multi-network for variable domestic routes, multi-IMSI for cross-border fleets, and eUICC on anything you expect to keep more than four years.
- Pilot on real routes. Ten to twenty vehicles, two to four weeks, logging check-in rate, network used, switches and data consumed. Coverage maps do not show the inside of a depot.
- Set up the platform before the first install. Bulk activation, lifecycle states, groups and usage alerts, plus the fleet-software integration requested in Phase 1.
- Install in waves and define done. A written per-vehicle sign-off and a 30-day check on check-in rate, data per SIM and support tickets.
- Compare plans on behavior, not price per SIM. Pooled plans for mixed fleets, roaming rates in writing, and an SLA that states uptime, measurement, credits and MTTR.
A fleet IoT deployment is a logistics project that happens to involve SIMs. The fleets that finish on time are the ones that treat it that way: they write the requirements down in the six lines a provider can quote against, they pilot on the ugly routes first, and they book the installers before they compare the plan prices. Get those three things right and the connectivity part is the easy bit.
If you are a fleet, transportation or logistics operator planning IoT transportation solutions for your vehicles and want a straight answer on which SIM, plan and platform setup fits your routes, Trafalgar Wireless provides the IoT SIMs, eSIMs, data plans and the IoT Suite management platform that fleets deploy on, with real people supporting the rollout from pilot to the last wave. Get in Touch!
