IoT eSIM in practice

Why SGP.32 becomes important at scale

Many IoT initiatives work well on a small scale but lose momentum as the number of devices increases. What is manageable with 10 devices quickly becomes expensive, sluggish, and difficult to control with 500 or 5,000.

This is where IoT eSIM and SGP.32 become relevant. Instead of building the process around physical SIM replacements, you can specify a model where connectivity becomes part of the operational chain. SGP.32 is also designed for IoT devices with limited interfaces and a more fleet-driven model than user-driven, as clearly described in the review of SGP.32 for IoT.

For many businesses, however, the work begins even earlier, with the choice of the right IoT connection, operator plan, and hardware. Advisera not only helps with advice on such decisions, but also provides IoT connectivity for businesses based on the business's requirements for coverage, operation, and scale.

If you want to reduce future lock-in now, it is wise to review both the hardware, process, and supplier model before placing a bulk order.

The first questions to ask

Start by defining the problem you are actually trying to solve. For some, a robust IoT SIM and a good operator agreement are enough. For others, remote profile management is crucial right from the start.

• 1. Real pain: What does a physical SIM replacement cost in terms of planning, travel, access, downtime, and administration?
• 2. Device type: Does your module and eUICC actually support SGP.32, or does the data sheet just say "eSIM"?
• 3. Bootstrap: How does the device get its first connection without ending up in a catch-22 situation where the profile must be downloaded before there is a network?
• 4. Coverage: How do you ensure operation in basements, concrete environments, vehicles, or geographical areas where the standard option is not sufficient?
• 5. Ownership: Who internally owns the cost, portal or API, alarm flows, and incident management when connectivity becomes business-critical?

These five questions quickly weed out solutions that look good in demos but create friction in the field.

If you would like to compare different options right now, you can read more about IoT connectivity via Advisera and get help assessing which model is best suited based on the number of devices, environment, and service life.

The questions that determine operability

The next step is to set requirements for the operational model. This is often where the difference between a functioning pilot and a solution that can be used for several years becomes apparent.

• 6. Profile strategy: When should profiles be assigned, how many are needed, and how quickly do you need to be able to change them in the event of problems or new conditions?
• 7. Security model: Do you need public internet, private APN, VPN, or clear segmentation between customers, sites, and product lines?
• 8. Cost control: Are there data caps, alerts for abnormal usage, and the ability to quickly pause or suspend individual subscriptions?
• 9. Exit: Can you export inventory, move profiles, and switch suppliers without changing hardware or rebuilding the process from scratch?

Here, you also need to check how responsibilities and components are distributed within the ecosystem. In SGP.32, eIM and IPA, among other things, play a major role in integration, distribution of responsibilities, and supplier selection, as explained in Trusted Connectivity Alliance's review of SGP.32 components and working methods.

In addition, you should ask about fallback and rollback when changing profiles. If a new profile does not work, the device must be able to recover in a controlled manner, not get stuck in retry or restart loops in the field.

If you are facing a procurement process, it may therefore be wise to ask the supplier to show you the process step by step, rather than just portal views and general promises. Contact Advisera if you would like to discuss IoT connectivity, operator options, and commercial arrangements for the next phase..

Common misconceptions about IoT eSIM

Several common assumptions lead to errors early on. Therefore, it is beneficial to clarify the concepts before finalizing the design and purchasing.

The first misunderstanding is that eSIM automatically means SGP.32. In practice, eSIM describes the SIM functionality being present in an eUICC, while SGP.32 is the IoT-adapted model for remote provisioning and operation.

The second is that roaming solves everything. Roaming or multi-networks can help, but coverage is still affected by the radio environment, antenna selection, installation, and local network policies.

The third is that one portal is enough. When it comes to volume, APIs, alerts, routines, and clear ownership often become more important than a stylish dashboard.

Finally, it is risky to think that these issues can be postponed until you scale up. Hardware choices, bootstrap, and exit conditions are much more difficult to change when thousands of units are already out there.

Here, it is also important to distinguish between theory and actual delivery capability. It is not enough to understand the standard on paper. You also need a partner who can help you choose and deliver the right IoT connection for your use, from pilot to rollout.

Frequently Asked Questions

Is SGP.32 right for all IoT solutions?

No. If you have few devices, a stable environment, and easy physical access, a well-chosen IoT SIM may be sufficient. SGP.32 becomes most interesting when you need to be able to control profile management and connection arrangements over time without physical intervention.

Does the device need to have a screen or user interface for SGP.32 to work?

No. On the contrary, SGP.32 is designed for IoT devices that often lack a screen and have limited resources. This is an important difference compared to more user-driven eSIM models.

Is it sufficient for the supplier to state that the module has eSIM?

No. You need to check exactly what support is available in the modem, eUICC, and the intended operating model. Otherwise, you risk purchasing hardware that does not support the way you need to work.

What question is most often overlooked in procurement?

Bootstrap and exit are often overlooked. Many focus on price and coverage but forget how to establish an initial profile and how to exit a supplier model if conditions change.

Can Advisera help even if we haven't chosen a solution yet?

Yes. Advisera can both provide advice on choosing a setup and arrange IoT connectivity based on your technical and commercial requirements.

If you want to take a first, practical step, you can gather four pieces of information internally: number of devices, geographical distribution, installation environments, and what a physical SIM replacement actually costs you in terms of time and money. This alone will usually make it clearer whether IoT eSIM with SGP.32 should be investigated now or later.

If you would like to discuss requirements, supplier options, or plans for the next phase, please contact Advisera for an unbiased review of your IoT connection. Read more about Advisera's IoT connection here.