From RSP integration to fleet-wide control
eSIM IoT Manager is designed to be operational within a day. The architecture is API-first and sits above your existing RSP infrastructure without replacing it.
Step 1 – Connect your RSP infrastructure
Connect eSIM IoT Manager to your SM-DP+, eIM, or connectivity management platform via the API integration layer. The platform supports standard RSP APIs used by major vendors. If you are running a managed service through a provider like Eseye, BSIM, or Transatel, the integration connects to their platform endpoints.
For SGP.32 deployments, the eIM API integration allows eSIM IoT Manager to communicate with the eSIM Orchestrator layer. If you want to understand the SGP.32 architecture including the eIM and IPA roles, sgp32.co.uk has a detailed breakdown.
Step 2 – Register your device fleet
Import your devices by EID individually, via CSV bulk import, or automated discovery from your RSP. Every device gets a profile record tracking its current profile state, network status, and history. Devices can be grouped by region, project, customer, or any custom taxonomy you define.
Step 3 – Set your connectivity policies
Define the rules for how each fleet segment should behave – which networks to prefer, when to trigger automatic failover, what thresholds should raise alerts, and which lifecycle events should trigger profile updates. Policies run automatically once set. Manual override is always available.
Step 4 – Monitor and operate
The fleet dashboard gives real-time visibility across every device. Connectivity status, profile state, last seen timestamp, and network performance are surfaced per device and aggregated at fleet level. Alerts fire on failure conditions and route to your notification endpoints.
Step 5 – Manage lifecycle
Profiles age, networks change, commercial agreements expire, and devices eventually reach end of life. eSIM IoT Manager tracks the full device lifecycle and surfaces upcoming expirations, migration candidates, and decommission candidates. Lifecycle operations run in bulk with policy guardrails.
On bootstrap. The chicken-and-egg problem of getting a device online before it has a production profile is one of the first operational issues teams hit with SGP.32. eSIM IoT Manager monitors bootstrap status per device and flags provisioning failures at the earliest possible point. For background on why bootstrap connectivity is the trickiest part of eSIM deployment, sgp32.co.uk covers it in detail.