This session goes beyond the SGP.32 specification to focus on what product, engineering, and operations teams should get right to make IoT eSIM deployments succeed at scale. Kigen and floLIVE break down the “day 0 → day 1 → day 2” realities: how eIM becomes the eSIM remote manager and source of truth for eUICC remote management, and why eIM swaps must be both technically validated and commercially permitted to avoid vendor lock-in. Plus, how direct vs indirect profile downloads impact interoperability, security posture, and support for constrained devices.
floLIVE now supports GSMA SGP.32 globally through its partnership with Kigen, enabling compliant and hybrid IoT eSIM deployments at scale.
Read more about the SGP.32 capabilities
The webinar also covers hybrid deployments (coexisting with earlier standards and existing SM-DP+ infrastructure), as well as how In-Factory Profile Provisioning (IFPP) removes manufacturing friction when internet access/activation codes aren’t viable.
From the operational side, SGP.32 enables more control and requires a structured operational setup. Teams need to align people, process, and platforms: commercial agreements with profile vendors/MNOs, compliance and security requirements.
Also key is the orchestration needed to avoid “connection shock” (bricking devices) and “cost shock” (losing visibility into usage and billing). floLIVE explains how CMP–eIM integration and a CMP aggregation layer can unify visibility, troubleshooting, and billing across multiple profiles/CMPs, while still supporting legacy approaches like multi-IMSI applets alongside SGP.32 profile switching.
Key steps to operational readiness: