Construction site connectivity: global IoT SIM, eSIM and CMP procurement across 180+ countries
· 7 min read · Technical Whitepapers
Global IoT SIM coverage spans 180+ countries; published rates open at €1.0282/GB across 166 priced markets, while eSIM provisioning is quoted per project.
Construction site connectivity means linking tower crane telematics, concrete maturity sensors, gate systems and site-office routers to cellular networks through one managed SIM estate. The procurement question is coverage plus cost per active device. A global IoT SIM covering 180+ countries is priced per country, with data from €1.0282/GB and SIM fees from €0.1428 per active SIM per month as the lowest published rates across 166 priced markets.
Where connected assets sit on a construction site
A live site runs at least four traffic profiles. Crane cameras and time-lapse rigs push video upstream and need 4G or 5G capacity with a data allowance measured in gigabytes. Concrete maturity loggers, tank-level probes and ground-movement sensors send a few hundred bytes a day, which is where LTE-M and NB-IoT attach where those networks are available.
Plant telematics is the second profile: excavators, telehandlers and generators that move between projects and sometimes between countries. Zipit Wireless notes that devices must switch between carrier networks reliably as they cross regions, and that inefficient handoffs can cause packet loss, temporary latency spikes or complete disconnection [7].
The third profile is people and temporary offices — welfare cabins, site Wi-Fi and snagging tablets on a 4G or 5G router. All of them can sit on one estate: a physical Global IoT SIM where a card can physically be reached, an eSIM profile delivered over the air where it cannot, and the CMP platform to track usage and activation state per project. The RESTful API is what carries that state into a site cost report or an asset register.
Trigger conditions that choose between a physical SIM, an eSIM and a multi-carrier SIM
If every asset in the estate stays inside one country, buy a physical Global IoT SIM at the published per-country rate and keep the SIM estate static. If the same device list spans several countries, or the same module ships to sites in different regions, move to eSIM with over-the-air provisioning: Voye Data Pool describes remote provisioning as the way to scale a device deployment without the logistics of physical SIM replacement [5].
If a single device has to hop between networks inside one country, compare a multi-carrier SIM against multiple eUICC profiles. Zipit Wireless warns that switching IMSIs to hold a connection introduces latency, which shows up first on video uplinks and command traffic [6]. If the rollout spans borders or runs into volumes beyond ordinary distribution, it moves to a project quote rather than published rates.
If you need to validate a module before the hardware is on site, note the test asymmetry: an eSIM test profile is free, while a physical test SIM is charged at the normal card price. That difference is worth budgeting when several router or module variants are being evaluated in parallel.
What the monthly bill is actually made of
Hardware is the capital line: router or module, antenna, IP-rated enclosure and power. On a crane, the installation window — an electrician plus a lift or climbing crew — commonly outweighs the connectivity line in year one. Data is the variable line. Take a 500-device estate: 400 sensors at 50 MB a month and 100 camera or router devices at 2 GB a month. That is 20 GB plus 200 GB, so 220 GB.
At the lowest published data rate of €1.0282/GB — the floor across priced countries, not a rate for any single market — 220 GB costs about €226.20 a month. Active-SIM fees add 500 × €0.1428 = €71.40. The combined floor is roughly €297.60 a month for 500 active SIMs, before platform fees, installation or maintenance.
Platform and maintenance are the lines that surprise people. The CMP platform is what makes activation state and per-project usage visible; the RESTful API is what carries those numbers into finance or asset systems. Maintenance shows up as truck rolls: a failed physical SIM means a site visit, while a profile action can be done remotely. Because the catalog price is published per country, each site's connectivity line can be modelled before the order is placed; eSIM provisioning is priced separately on quote.
Published parameters a buyer can contract against
| Parameter | Published value | Why it changes the order |
|---|---|---|
| Country coverage | 180+ countries with 2G/3G/4G/5G plus LTE-M and NB-IoT where available | One SIM estate can cover a multi-region fleet, but the radio technology on a given site depends on the local network |
| Priced markets | 166 countries published per country; other covered countries price on request | A site in an unpriced country holds the order until a quotation is issued |
| Lowest published data rate | €1.0282/GB, the floor across priced countries and not the rate of any named market | Anchors the sensitivity model for camera and router traffic |
| Lowest published SIM fee | €0.1428 per active SIM per month | SIMs left active on a finished site keep billing; deactivate them in the CMP platform |
| eSIM provisioning | Over the air, priced separately on quote | Allows mobilisation before hardware ships |
| Test profiles | eSIM test profile free; physical test SIM charged at the normal card price | Sets the pilot budget for module validation |
| Multi-country or high-volume orders | Negotiated quotation | Changes the contract shape from published rates to negotiated terms |
What changed in remote SIM provisioning and in roaming economics
Remote SIM provisioning is now standardised. G+D states that its IoT connectivity offering supports the major GSMA specifications for Remote SIM Provisioning — SGP.02, SGP.22, SGP.32 and SGP.42 — which is what makes an eUICC profile a portable asset instead of a carrier-locked card [4]. For a buyer, that turns a hardware question into a specification question: check which of those generations your module firmware and your chosen CMP platform actually implement before committing a fleet.
Roaming is the other boundary. Zipit Wireless notes that tying a deployment to a single network carries the legal and financial pitfalls of permanent roaming, and that negotiating one contract with a cellular provider is daunting for device OEMs [6][7]. Multi-carrier and multi-IMSI designs exist for that reason. The practical consequence is that handoff behaviour — not the coverage map — is the thing to test before scaling.
Pitfalls that show up between pilot and rollout
Handoff gaps. Put a device on a route that crosses two networks and log packet loss, latency spikes and reattach time; Zipit Wireless identifies all three as handoff failures [7]. A pilot that only ever sees one network will not surface them.
IMSI-switch latency. Zipit Wireless notes that swapping IMSIs to maintain connectivity introduces latency that can delay data transmission and reception [6]. If the device cannot tolerate that delay, test whether a multi-carrier design or multiple eUICC profiles behave better on your traffic.
Data-budget drift. A single firmware update pushed over cellular can consume a month of telemetry allowance in one afternoon; model the worst case rather than the average before fixing a data allowance per device.
SIM lifecycle leakage. Published SIM fees are charged per active SIM per month, so SIMs left active on a demobilised site keep costing. Verify in the CMP platform that deactivation is possible and that the RESTful API reports the resulting state.
Radio assumptions. LTE-M and NB-IoT are available where local networks support them, so confirm the attach technology at the specific site, not from a country-level datasheet, before specifying a low-power sensor.
When published per-country rates are enough and when to route the order through a quote
Published per-country rates are enough for a single-country estate with a predictable traffic profile — a sensor fleet that sends tens of megabytes a month, on devices a technician can physically reach. You can model data and active-SIM fees for each site and contract without negotiation.
Move to a project quote when the rollout spans several countries, when volumes grow beyond ordinary distribution quantities, or when eSIM provisioning is the delivery mechanism, since eSIM is priced separately on quote. That is also the point to fold CMP platform and RESTful API requirements into the same conversation, because activation-state discipline — switching SIMs off when a project ends — is where a multi-country estate's savings actually land.
Published Global IoT SIM parameters and what they change in a construction order
| Parameter | Value | Why it matters for buying |
|---|---|---|
| Country coverage | 180+ countries with 2G/3G/4G/5G plus LTE-M and NB-IoT where available | Decides whether one SIM estate can cover a multi-region fleet, while the radio technology on a given site depends on the local network |
| Priced markets | 166 countries published per country; other covered countries price on request | A site in an unpriced country holds the order until a quotation is issued |
| Lowest published data rate | €1.0282/GB, the floor across priced countries and not the rate of any named market | Anchors the sensitivity model for camera and router traffic |
| Lowest published SIM fee | €0.1428 per active SIM per month | SIMs left active on a finished site keep billing; deactivate them in the CMP platform |
| eSIM provisioning | Over the air, priced separately on quote | Allows mobilisation before hardware ships to site |
| Test profiles | eSIM test profile free; physical test SIM charged at the normal card price | Sets the pilot budget for module and router validation |
| Multi-country or high-volume orders | Negotiated quotation | Changes the contract shape from published rates to negotiated terms |
Physical Global IoT SIM against eSIM profiles for a construction estate
| Dimension | Physical Global IoT SIM | eSIM (over-the-air profile) | When to choose |
|---|---|---|---|
| Provisioning route | Card shipped to site and inserted | Profile delivered remotely | eSIM when mobilisation starts before hardware arrives; physical when a technician is already on site |
| Published cost basis | Per-country data rate plus monthly active-SIM fee | Priced separately on quote | Published rates for a single-country static estate; quotation for eSIM |
| Testing | Test SIM charged at the normal card price | Test profile free | eSIM when validating several module variants in parallel |
| Recovery after failure | Site visit to replace the card | Remote profile action | Remote or hard-to-reach assets such as cranes and tower lighting |
| Country change | Card logistics across borders | New profile pushed over the air | Multi-country fleets or plant redeployed between projects |
Frequently Asked Questions
How many countries does a single global IoT SIM cover for a construction fleet?
Global IoT SIM coverage runs to 180+ countries with 2G/3G/4G/5G, plus LTE-M and NB-IoT where those networks are available. Data rates and monthly active-SIM fees are published per country for 166 countries; the remaining covered countries are priced on request.
What does an eSIM cost compared with a physical SIM?
eSIM provisioning is priced separately on quote, so there is no published per-GB rate for it. The test difference is explicit: an eSIM test profile is free, while a physical test SIM is charged at the normal card price. The commercial case for eSIM rests on avoiding card logistics and site visits rather than on a unit rate.
Which published price should go into a site budget model?
Use the per-country rate for the site in question. The lowest published figures — data from €1.0282/GB and SIM fees from €0.1428 per active SIM per month — are floors across all priced countries, not the rate of any single market, so treating them as a universal rate will understate most sites.
When does a construction rollout need a negotiated quotation rather than published rates?
Larger volumes and multi-country rollouts are quoted rather than sold from the published list, and eSIM is priced on quote. The trigger is normally geographic spread across the estate or a device count that goes beyond ordinary distribution quantities.
What breaks first when connected plant moves between countries?
Handoffs. Zipit Wireless identifies packet loss, temporary latency spikes and complete disconnection as the failure modes when devices transition between carrier networks [7], and notes that switching IMSIs to maintain a connection introduces its own latency [6]. Test the border crossing before scaling the fleet.
Do we need a CMP platform for a small construction estate?
A single-site estate with a handful of SIMs can be tracked manually. The CMP platform becomes load-bearing once several projects run at the same time, because it exposes per-project usage and allows SIMs to be deactivated — and the published SIM fee is charged per active SIM per month. Voye Data Pool describes usage monitoring across multiple projects as a core reason for managing connectivity centrally [5].