The eSIM Lifecycle: From Factory Floor to Field Operation

The Five Phases of an eSIM Device Life

Most eSIM guides focus on the profile download moment – the point when a device gets its first operational SIM credentials. But the eSIM lifecycle starts long before that, in a factory where the eUICC chip is soldered to the PCB, and it continues long after, through years of profile management, operator switches, and eventually device decommissioning.

Understanding all five phases is essential for anyone specifying, deploying, or managing an IoT fleet.

Phase 1: In-Factory Profile Provisioning (IFPP)

Before a device leaves the factory, the eUICC chip needs to be loaded with at least a bootstrap profile. This happens through a process called IFPP – In-Factory Profile Provisioning. During circuit board assembly or final quality testing, the manufacturer uses specialised equipment to communicate with the eUICC and load the bootstrap credentials.

The bootstrap profile loaded at this stage is typically sourced from a connectivity partner – in the Teltonika example, Tele2 provides the bootstrap that ships pre-loaded on RUT series routers. The manufacturer integrates with the connectivity partner via an API connection to their SM-DP+ server, which prepares and delivers the bootstrap profile package for installation during the manufacturing process.

This is the “Single SKU” moment. Because the bootstrap profile provides global connectivity via roaming, the manufacturer builds one version of the hardware and ships it worldwide. There is no need for regional variants with different SIM cards installed.

Phase 2: Transit and Warehousing

Between leaving the factory and arriving on-site, the device may sit in transit or storage for weeks or months. During this period, the bootstrap profile is dormant – the device is powered off, consuming no data.

The key risk during this phase is bootstrap profile expiry. Most bootstrap profiles are valid for one year from manufacturing. If the logistics or procurement cycle extends beyond that window, devices may arrive at the deployment site with an expired bootstrap. This is an operational risk that should be tracked as part of fleet lifecycle management.

Phase 3: First Power-On and Bootstrap Activation

When the device powers on for the first time in the field, the eUICC activates the bootstrap profile. The device connects to the cellular network using the bootstrap credentials – typically via a global roaming SIM arrangement that gives it access to whatever network is available at the location.

The bootstrap connection is deliberately restricted. On a Teltonika device, it allows only DNS, DHCP, connection to the SM-DP+ server, and connection to the RMS management platform. The data allowance is limited – typically 10MB. This is enough to complete the operational profile download and nothing more.

The device uses this bootstrap connectivity to reach the eIM and announce itself: “I am device EID-XXXX. What profile should I have?” The eIM checks its configuration, identifies the correct operational profile for this device, and initiates the profile download from the SM-DP+.

Phase 4: Operational Profile Installation

The SM-DP+ server prepares an encrypted profile package for the device. The package is delivered via HTTPS (for well-connected devices) or CoAP over UDP (for constrained NB-IoT or LTE-M devices). The eUICC validates the cryptographic signature, decrypts the package, and installs the operational profile.

Once the operational profile is installed and enabled, the bootstrap profile goes dormant. The device is now running on its intended production credentials – a proper operator SIM with the data plan, APN configuration, and network access policy appropriate for its deployment.

For the first time, the device has full connectivity. It can reach its management platform, its data endpoints, and the internet. The bootstrap has served its purpose and is no longer used for normal operations.

Phase 5: Operational Lifecycle Management

Over the device lifetime – which for utility and industrial IoT may span 15 to 20 years – the operational profile will need to change. Network operators raise prices. Coverage changes. Operators merge or exit. Regulatory requirements around permanent roaming may force a switch to a local operator in a given market.

Under SGP.32, all of these changes are handled remotely via the eIM. An administrator pushes a profile switch command to an individual device or a fleet segment. The device receives the instruction (synchronously if it is currently connected, asynchronously when it next wakes if it is in deep sleep), downloads the new profile, and switches to it. No physical access. No site visit. No production downtime.

Phase 6: End-of-Life Decommissioning

When a device reaches end of life, its eSIM credentials need to be properly retired. The eIM sends a “delete profile” command to the eUICC. The active profile is removed, the device loses cellular connectivity, and the profile licence is released back to the operator.

This is one of the less-discussed benefits of eSIM over physical SIM: decommissioning is a software operation. A physical SIM that is not recovered may continue to consume plan fees. An eSIM profile that is remotely deleted cannot. For large fleets, this difference in decommissioning overhead is commercially significant over a long enough time horizon.

For a detailed breakdown of the bootstrap phase and its failure modes, see eSIM Bootstrap Issues. For how specific hardware manufacturers implement this lifecycle, see the eSIM Hardware Guide.