There is a concept in IoT connectivity called a truck roll. It is the industry term for sending an engineer to a device location to do something that should not require a human to be physically present. In 2026, one of the most common reasons for a truck roll in a managed IoT fleet is a SIM swap – changing the physical SIM card to move a device to a different operator.
At small scale, truck rolls are an annoyance. At the scale most serious IoT deployments operate, they are a significant cost centre. A conservative estimate of £150 per truck roll, with a 1% annual SIM swap rate across a fleet of 10,000 devices, produces a line item of £15,000 per year that exists purely because connectivity decisions are baked into hardware rather than managed in software.
Dynamic connectivity, enabled by eSIM switching, eliminates that line item.
What Static Connectivity Actually Means
Static connectivity is not just about the SIM card. It is a whole operational model. The SIM is provisioned at deployment with a single operator relationship. That relationship determines the device coverage, the data rates, the roaming behaviour, and the regulatory compliance posture for the lifetime of the device.
When any of those factors change – and over a 15-year device lifetime, all of them will change – the response options under a static connectivity model are limited. You can accept the degraded situation. You can negotiate with your operator to change something within their platform. Or you can physically replace the SIM.
The static model made sense when eSIM technology did not exist and remote profile management was not a practical option. It no longer makes sense when the technology to replace it is available and standardised.
What Dynamic Connectivity Means in Practice
Dynamic connectivity means the network relationship is managed as a software configuration rather than a hardware decision. The device has an eUICC capable of holding multiple operator profiles. The appropriate profile is loaded remotely. When conditions change, the profile changes through an eSIM switching platform – no physical intervention required.
The operational shift this creates is significant:
- Coverage problems are resolved remotely rather than through site visits
- Operator contract changes happen at the fleet level rather than device by device
- Cross-border deployments use local operator profiles rather than permanent roaming
- Network technology transitions (such as 3G sunset) are managed as profile migrations rather than hardware replacements
- Failover to a backup operator happens automatically based on rules rather than requiring manual intervention
The Role of SGP.32
SGP.32 is the technical enabler of dynamic connectivity at scale. Earlier eSIM standards – SGP.02 for M2M and SGP.22 for consumer – made remote profile management possible in principle but not practical for the constrained, headless IoT devices that make up the majority of industrial deployments.
SGP.32 changes the picture specifically for IoT because it supports CoAP over UDP for constrained networks, asynchronous operations for deep-sleep devices, and server-initiated profile management without any user interaction at the device. The three changes that matter most for dynamic connectivity are precisely what distinguishes SGP.32 from its predecessors.
Some of the dynamic connectivity benefits are available today with SGP.22 hardware through management platforms like Teltonika RMS and Robustel RCMS. But these are proprietary implementations that work for always-on routers and gateways. True dynamic connectivity across constrained IoT – the NB-IoT meters, the LTE-M trackers, the battery-powered environmental sensors – requires native SGP.32 support.
The Transition That Is Happening Now
The industry is not waiting for dynamic connectivity. It is building toward it progressively, with the hardware and infrastructure arriving in 2025-2026 and the enterprise-facing control layer – what we are calling eSIM switching platforms – emerging alongside.
The Robustel and Kigen partnership announced in October 2025 is a useful marker. A major router manufacturer working with a major eUICC provider to deliver both a retrofit plastic eSIM option (for existing hardware) and a roadmap to native SGP.32 for new designs is exactly the kind of transition signal that shows where the market is heading. The question for anyone specifying IoT hardware today is not whether dynamic connectivity will arrive – it is whether the hardware and management infrastructure they are deploying now will support the transition when it does.
The eSIM Switching Layer
Dynamic connectivity needs more than the GSMA standard and the hardware to run it. It needs an enterprise-facing control layer – a platform that abstracts the complexity of eIM architecture, SM-DP+ endpoints, and profile lifecycle management into something an operations team can actually use.
That is the eSIM switching platform. Not the infrastructure. Not the SIM. The interface and the intelligence that sits above both and makes dynamic connectivity operationally accessible at scale.
For the technical foundation, see the SGP.32 guide. For what the control layer looks like in practice, see What is eSIM Switching?. For how different hardware categories implement dynamic connectivity today, see the eSIM Hardware Guide.