Managing connectivity for thousands of IoT devices across multiple regions, network operators, and regulatory environments remains one of the hardest problems in enterprise IoT. A global IoT service provider in the utilities sector recently faced this exact challenge: scaling device deployments without multiplying operational complexity. Their solution — Thales and Simetric’s unified connectivity platform — provides a blueprint for any fleet operator considering the eSIM migration.
This article unpacks the architecture behind the Thales-Simetric partnership and provides a practical migration playbook for operators moving from physical SIM estates to eSIM-based managed connectivity.
The Problem: Physical SIM Fragmentation
Large IoT fleets typically operate across 5-15 mobile network operators (MNOs), each with separate contracts, management portals, and provisioning workflows. A utility company deploying smart meters across Southeast Asia might use AIS in Thailand, Telkomsel in Indonesia, and Globe in the Philippines — three separate SIM procurement pipelines, three sets of troubleshooting procedures, and zero visibility across the entire fleet from a single dashboard.
When a region experiences network degradation, operators must manually identify affected devices, triage by MNO, and coordinate with each carrier’s support team. Device replacements require physical SIM swaps, sending technicians to remote sites. This isn’t scalable.
The GSMA’s SGP.32 specification for IoT eSIM changed the equation, enabling remote SIM provisioning (RSP) over-the-air. But adopting SGP.32 requires integration with eSIM subscription managers, connectivity management platforms, and existing fleet orchestration systems — a multi-vendor integration challenge that most fleet operators aren’t equipped to handle in-house.
The Solution: Thales + Simetric Unified Platform
Thales brings the hardware and eSIM infrastructure — its eSIM IoT Manager (eIM) and eSIM Advanced Subscription Orchestrator (eSO) — while Simetric provides the connectivity management platform (CMP) layer through its Single Pane of Glass (SPOG) interface.
Architecture:
IoT Device (eSIM)
↓ SGP.32 RSP
Thales eSIM IoT Manager (eIM) ← eSIM lifecycle, profile download, subscription mgmt
↓ API
Thales eSIM Advanced Subscription Orchestrator (eSO) ← multi-MNO profile switching
↓ API
Simetric SPOG ← unified dashboard, SLA monitoring, troubleshooting, billing
↓
Enterprise IoT Fleet Operator
The value proposition: one contract, one dashboard, one support channel — covering multiple MNOs across any geography. When network conditions degrade on MNO A, the platform can trigger an over-the-air profile switch to MNO B without physical intervention.
Migration Playbook: 7 Steps to eSIM Fleet
Step 1: Audit Current SIM Estate
Before any migration, document what you have:
# Example audit structure
Fleet Audit:
├── Total devices: 12,400
├── Active MNOs: 7
├── SIM types: 4FF (85%), MFF2 (10%), eSIM (5%)
├── Regions: EU (4,200), SEA (3,800), NA (2,900), LATAM (1,500)
├── Monthly data: 2.3 TB aggregate
├── Avg SIM swap incidents/month: 47
└── Avg resolution time per incident: 3.2 days
Key metrics to capture: number of MNO contracts, SIM form factors, monthly data consumption per region, average incident resolution time, and total cost of SIM management (procurement + logistics + support). This baseline justifies the migration ROI.
Step 2: Classify Devices by Migration Pathway
Not all devices can or should migrate to eSIM. Divide your fleet into three tiers:
Tier 1 — Greenfield (new deployments only): Devices being procured now or in the next quarter. Specify eSIM (MFF2 or embedded) with SGP.32 compliance in RFQs. These ship with bootstrap profiles and connect to Thales eIM on first power-up.
Tier 2 — Replaceable (swap during maintenance): Devices in accessible locations with planned maintenance visits. Schedule physical module swaps during the next service window. Budget: ~$15-25 per device for module + labor.
Tier 3 — Brownfield (stays on physical SIM): Hard-to-reach devices, legacy hardware without eSIM support, or devices approaching end-of-life. These remain on physical SIMs until retirement. Include them in the Simetric SPOG through API integration with existing MNO portals where possible.
The target: 60-70% of fleet on eSIM within 18 months. Full migration isn’t necessary to realize 80% of the benefits.
Step 3: Select Coverage Partners
Work with Thales/Simetric to map your geographic footprint to MNO coverage:
coverage_map:
eu:
primary: Deutsche Telekom
fallback: Vodafone, Orange
sea:
primary: AIS (Thailand), Telkomsel (Indonesia)
fallback: Globe (Philippines), Maxis (Malaysia)
na:
primary: T-Mobile
fallback: AT&T, Verizon
latam:
primary: Claro (Brazil)
fallback: Movistar, TIM
The eSO orchestrator handles profile switching based on signal strength, cost, and SLA parameters you define. Configure thresholds: switch if latency > 200ms for 5 minutes, or if data cost per MB exceeds 1.5x baseline.
Step 4: Define Connectivity Policies
Create policy templates in Simetric SPOG:
- Cost-optimized: Prefer lowest-cost MNO, switch only on failure
- Performance-optimized: Prefer lowest-latency MNO, accept 20% cost premium
- Regulatory-compliant: Data must stay within national borders (sovereign IoT pattern, see Telia’s sovereign IoT service)
- Resilience-first: Maintain simultaneous connections to 2 MNOs (higher cost, zero downtime)
Apply policies per device group: smart meters use cost-optimized; autonomous vehicles use performance-optimized; healthcare devices use resilience-first.
Step 5: Run Pilot Migration
Select 100 devices across 2-3 regions for a 30-day pilot:
Week 1: Provision eSIM profiles via Thales eIM, verify connectivity on primary MNOs
Week 2: Test profile switching — simulate MNO failure, measure failover time
Week 3: Load test Simetric SPOG — push 5x normal telemetry volume, verify dashboard latency
Week 4: Run cost analysis — compare pilot connectivity costs vs. existing contracts
Success criteria for pilot:
- Profile switch completes in <60 seconds
- SPOG dashboard latency <2 seconds at 5x load
- Connectivity cost within 10% of existing contracts
- Zero device bricking during profile switches
Step 6: Full Migration in Waves
Migrate in waves of 500-1,000 devices per week:
- Wave 1: Least critical devices (non-revenue-impacting)
- Wave 2: Medium-criticality, single-region
- Wave 3: High-criticality, multi-region with rollback plan
After each wave, run a 48-hour stabilization period before starting the next. Track total migration errors — target <0.5% failure rate.
Step 7: Decommission Legacy MNO Contracts
As devices migrate, terminate physical SIM contracts per region. Coordinate termination dates to avoid gaps. This is where the ROI materializes: each terminated MNO contract eliminates a management portal, a support escalation path, and a monthly invoice to reconcile.
Real-World Impact: The Utilities Provider Case
The utilities provider referenced in the Thales-Simetric announcement operated across multiple regions and network partners. Their migration yielded:
- 40% reduction in connectivity management overhead (fewer dashboards, fewer contracts)
- 72% faster incident resolution (remote profile switching vs. physical SIM swaps)
- Zero-touch provisioning for new devices (bootstrap eSIM profile downloaded on first power-up)
- Single SLA monitoring interface across all MNOs
This aligns with the broader industrial IoT trend covered in the factory data audit guide. Connectivity is the foundation — without reliable data flow, predictive maintenance and AI-driven edge processing can’t deliver ROI. For more on building agent-driven IoT systems, see the ESP-IDF MCP Server guide. Browse all IoT resources in the IoT & Edge Computing Hub.
What to Do This Week
- Inventory your SIM estate — count devices, MNOs, regions, and monthly incidents
- Contact Thales/Simetric — request a coverage map for your geographic footprint
- Identify your Tier 2 devices — those with upcoming maintenance where module swaps are feasible
- Run the numbers — total annual SIM management cost vs. eSIM platform cost at your scale
The SGP.32 eSIM standard has removed the technical barriers to multi-MNO fleet connectivity. The Thales-Simetric platform removes the integration barriers. For fleet operators managing more than 1,000 devices across more than 2 MNOs, the migration pays for itself within 12-18 months.
Discover more from Susiloharjo
Subscribe to get the latest posts sent to your email.