If you run connectivity for an enterprise, you already know the dirty secret: the SIM is the least interesting part of your problem.

Yes, SIMs (and eSIMs) matter. They are the credentials. The key. The thing that lets a device attach to a network. But enterprises do not lose sleep over “which SIM” in isolation.

They lose sleep over fleets, failures, and the mess in the middle:

A factory sensor that silently drops off the network for six hours. A retail kiosk that burns through an “unlimited” plan because someone shipped it with the wrong APN policy. A vehicle fleet that crosses borders and suddenly acts like it has amnesia. A compliance team asking why 12 countries show up on the invoice when the deployment is supposed to be only in three.

That is why enterprises need orchestration, not SIM cards.

And the industry is moving in that direction fast, especially as eSIM standards and platforms evolve to put more control in the hands of the enterprise, not the operator, not the SIM vendor.

What “orchestration” really means in connectivity

Orchestration is the control layer that makes connectivity behave like an enterprise system, not a pile of subscriptions.

A good orchestration layer gives you one place to manage the lifecycle across operators, profiles, regions, and device types. It is the difference between “we have SIMs” and “we have control.”

Think of it as the single pane of glass that sits above:

• Connectivity Management Platforms (CMPs)
• Remote SIM Provisioning components (SM-DP+, SM-SR, or the newer IoT architecture components like eIM)
• Operator agreements and roaming constructs
• Policy, billing logic, alerts, diagnostics, and automation

This is not hypothetical. CMPs are explicitly positioned as the software layer that streamlines deploying, monitoring, managing subscriptions, troubleshooting, and analytics for IoT connectivity.

“Enterprises do not want more SIM vendors. They want one dashboard that shows who is connected, where, and at what cost.”

Why SIM-first thinking breaks at enterprise scale

In consumer land, a SIM is a “thing you put in a phone.” Even in travel eSIM, the mindset is still transactional: buy a plan, install, and go.

Enterprises do not live in that world.

Enterprises have:

• fleets (thousands to millions)
• long device lifetimes (years)
• mixed hardware (with and without UI, intermittent power, low bandwidth)
• complex geographies (multi-country deployments, supply chain drift)
• obligations (SLAs, security policies, compliance, cost predictability)

So the SIM becomes a liability if it is treated as the product.

Because the enterprise problem is not “activate.” It is “operate.”

This is exactly why the GSMA’s newer IoT eSIM architecture (SGP.32, alongside SGP.31 requirements) is framed around making remote provisioning workable for real IoT constraints, and why the concept of an IoT manager layer (eIM) keeps showing up in how the ecosystem explains it.

The control layer is where the value is moved

The market has done this before in other domains.

Servers became cloud. Hardware became an API. Networks became software-defined.

Connectivity is doing the same thing.

The value is shifting away from the credential (SIM) and toward the system that decides:

• Which profile should be active, when, and why
• What happens if the network degrades
• How is cost bounded
• How provisioning is secured and audited
• How issues are detected before customers notice

That control layer can sit inside a CMP (Cisco, Ericsson, and others), or alongside it as an abstraction layer that also speaks to eSIM provisioning systems. Cisco, for example, positions its IoT Control Center as managing connectivity and lifecycle at large global scale, which is exactly the orchestration story.
Ericsson similarly frames enterprise-facing IoT connectivity as something that should be plug-and-play for enterprises, meaning the complexity is being wrapped into platforms rather than pushed onto the enterprise team.

eSIM standards are quietly enabling orchestration

Here is the part most enterprise buyers miss: standards are not just “telecom paperwork.” Standards decide who holds the steering wheel.

In consumer eSIM (SGP.22), the architecture is typically SM-DP+ delivering profiles to devices in a secure way. That is great for phones and UI-driven devices.

In classic M2M eSIM (often referred to via older GSMA eSIM M2M architecture), you have components like SM-DP and SM-SR, with flows designed for long-lived, industrial deployments.

Now look at where SGP.32 is going for IoT. Multiple ecosystem explanations emphasize that it is designed for IoT realities and introduces a more scalable control approach for fleets, including the idea of an IoT manager function (eIM) that acts like the SIM control panel for fleets.

This matters because orchestration is not a “nice-to-have dashboard.” It is becoming structurally supported by how IoT eSIM is meant to work at scale.

What orchestration actually delivers day to day

Fleet control

A real orchestration layer lets you segment fleets, apply policies, and automate actions. Not “click to activate 10,000 times.” More like: “If devices in Region X exceed threshold Y, move them to Profile Z.”

Commercial sanity

Enterprises do not want 40 separate operator portals and a mystery invoice. CMPs and hub approaches pitch “single interface” and unified operations because that is what enterprise buyers are trying to buy: predictable cost and fewer moving parts.

Provisioning without drama

Profile lifecycle actions (download, enable, disable, delete) are core to remote SIM provisioning, and orchestration is what makes those actions operationally safe at fleet scale, not just technically possible.

Security posture you can explain to an auditor

Remote provisioning is built on secure channels, certificates, and controlled profile management. When the enterprise owns the operational layer, security becomes enforceable policy, not tribal knowledge living in one telecom specialist’s inbox.

So who’s selling orchestration today?

You can loosely group the “orchestration” market into three overlapping camps:

Connectivity Management Platforms

These are the big “manage subscriptions and fleets” platforms (often used by operators and enterprises). Industry narratives put players like Cisco and Ericsson in this world, and analysts describe CMPs as the layer that handles activation, subscription management, billing, and increasingly eSIM-related functions.

eSIM control and IoT manager layers

This is where the conversation gets more modern: standards-based management of eSIM profile operations across SM-DP+ platforms, often positioned as a “single pane of glass” for eSIM.

Hubs and integration layers

Some providers describe an “eSIM hub” or orchestration layer as the bridge between CMPs and provisioning systems, so enterprises are not forced to do bespoke integrations for every operator and every SIM stack.

These camps are also where you should expect consolidation. The orchestration layer tends to become sticky infrastructure, and sticky infrastructure attracts acquisitions and platform bundling.

The real buying decision

If you are an enterprise buyer, the most important question in connectivity is no longer “Which SIM or which operator?”

It is: “Who gives me operational control that survives scale?”

Because SIM cards do not give you governance. They do not give you automation. They do not give you cost boundaries. They do not give you cross-operator portability in practice, even if it exists on paper. They are credentials, not control planes.

The market trend is clear: connectivity is being productized as a managed system, with APIs, dashboards, policies, and lifecycle automation, not as a pile of subscriptions. CMPs are evolving in that direction, eSIM standards like SGP.32 are designed to better fit fleet realities, and ecosystem players are explicitly describing “single interface” management as the value.

So here is the conclusion I would actually bet on:

Enterprises that keep buying connectivity as “SIM supply” will keep living in reactive mode, stitching together portals, contracts, and manual fixes.

Enterprises that buy orchestration will start treating connectivity like any other critical infrastructure layer: observable, governed, automated, and replaceable when performance or commercial terms stop making sense.

And that is the quiet shift happening underneath the whole “eSIM boom” story. The SIM is getting demoted. The control layer is getting promoted.