Changing the carrier on a traditional SIM means physically swapping the little plastic card, which is fine on a phone but painful when the device is a gateway on a wellpad hours away. An eSIM, an embedded SIM soldered into the device, removes that constraint by holding carrier profiles that can be loaded and switched over the air. This guide explains what an eSIM and its eUICC are, how remote provisioning lets a field gateway change carriers without a truck roll, how a bootstrap profile gets the device online in the first place, and how multi-IMSI arrangements improve roaming resilience for remote telemetry.
eSIM provisioning in one line: An eSIM is an embedded SIM, built around an eUICC chip, that stores carrier profiles which can be downloaded and switched remotely over the air rather than by physically swapping a card. Remote provisioning lets a field gateway change its carrier profile without anyone visiting the site, and multi-IMSI arrangements let a SIM present different network identities to improve roaming resilience. Together they make a remotely deployed gateway's connectivity reconfigurable from a distance.
An eSIM is not a card you insert but a chip, the embedded universal integrated circuit card or eUICC, mounted permanently inside the device. What makes it powerful is that the eUICC can hold one or more carrier profiles and can download new ones and switch between them under remote control, whereas a traditional SIM is tied to the single operator whose card it is. The carrier identity is now data on a reprogrammable chip rather than a fixed property of a physical card, and that shift is what enables remote provisioning.
Remote provisioning is the standardized machinery that delivers and manages those profiles over the air. A management system can push a new carrier profile to the eUICC across the cellular link, enable it, and disable the old one, so the device ends up on a different network without anyone touching it. The device needs some connectivity to receive that first profile, which is the job of a bootstrap profile: a starter profile, often with limited scope, that gets the eUICC online just enough to download the operational profile it will actually run on. Once the operational profile is installed and enabled, the device operates on it normally.
The whole model is designed for devices that are deployed and then hard to reach, which describes field telemetry precisely. Because the carrier can be changed remotely, decisions about which network a device uses are no longer locked in at the moment of installation. A gateway can be shipped and installed with a bootstrap profile, brought online, and then provisioned onto whichever operator makes sense for its location, all without a technician handling the SIM, which is the core advantage the eUICC brings over a fixed physical card.
The practical payoff of remote provisioning is eliminating the truck roll for a carrier change. On a traditional SIM, moving a remote gateway to a different operator, because coverage changed, because a contract ended, or because the incumbent carrier's service degraded, means sending someone to the site to physically swap the card. For a fleet of gateways scattered across a large area, that is a slow, expensive exercise, and it means connectivity decisions are effectively frozen once devices are deployed unless you are willing to pay for site visits.
With an eSIM the carrier change is a remote operation. If a site's current network becomes unreliable or a better option appears, the operator can provision a new carrier profile to that gateway's eUICC over the air and switch it across, and the device is on the new network without anyone leaving the office. This turns carrier choice from a one-time installation decision into something manageable over the life of the deployment, which matters when coverage, pricing, and network performance all change over the years a field asset stays in service.
This flexibility also de-risks the initial rollout. Because the operational profile can be assigned after installation, devices do not have to be individually kitted with the correct carrier's SIM before they ship, and a device installed in one location can be reprovisioned if it ends up somewhere with different coverage. For an operation adding or relocating remote sites over time, being able to decide and change the carrier remotely removes a logistical constraint that physical SIMs impose, and keeps the fleet's connectivity adaptable rather than fixed at the moment each device was built.
Roaming resilience is where multi-IMSI arrangements come in, and they are a related but distinct idea from switching profiles. An IMSI is the identity a SIM presents to a network, and a multi-IMSI SIM can present more than one, effectively letting it appear as a subscriber of different networks depending on where it is and what is available. For a device that might sit at the edge of coverage or move between areas served by different operators, being able to fall back to another network identity when the preferred one is unavailable makes the connection more robust than a single fixed identity would allow.
Combined with remote provisioning, this gives a remote gateway two complementary tools for staying connected. Multi-IMSI improves the odds that the device finds a usable network at its location without any intervention, adapting to available coverage in the moment, while remote provisioning handles the larger, deliberate change of moving the device onto a different operator's profile when that is the right long-term decision. One is about automatic resilience at the edge of coverage; the other is about managed carrier changes over the device's life. Both reduce the number of situations in which a person has to physically visit a remote site to fix connectivity.
For a cloud SCADA platform such as Merobix, the value of all this is uninterrupted data from sites that are expensive to reach. The platform simply needs the telemetry to keep arriving; eSIM remote provisioning and multi-IMSI work below that level to keep each gateway connected through carrier changes and patchy coverage without dispatching a technician. An operator can respond to a carrier issue at a remote site by reprovisioning from afar rather than losing days to a site visit, and multi-IMSI quietly keeps marginal sites reporting by using whatever network is reachable. The result is that the connectivity layer becomes something managed remotely, matching the remotely-managed nature of the cloud platform it feeds.
A normal SIM is a removable card tied to a single carrier, so changing operators means physically swapping it. An eSIM is an embedded chip, the eUICC, soldered into the device that can hold multiple carrier profiles and download or switch them remotely over the air. That makes the carrier identity reprogrammable data rather than a fixed physical card, which is what enables remote provisioning for hard-to-reach field devices.
A bootstrap profile is a starter carrier profile, often with limited scope, that gets the eUICC online just enough to download the operational profile the device will actually run on. Because remote provisioning needs some connectivity to deliver the real profile, the bootstrap profile solves the chicken-and-egg problem of a freshly deployed device having no network yet. Once the operational profile is installed and enabled, the device runs on that.
A multi-IMSI SIM can present more than one network identity, letting it appear as a subscriber of different operators depending on where it is and what is available. If the preferred network is unavailable at a location, the SIM can fall back to another identity and connect through a different operator, without anyone intervening. This makes a device at the edge of coverage more likely to find a usable network than a single fixed identity would.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.