Is an embedded SIM more secure than a physical SIM for rail telematics?

No measurable difference in the sources reviewed. eSIMs run a similar eUICC software stack to traditional SIMs and offer at least an equivalent level of security [4], and all eSIM profiles must meet GSMA security requirements regardless of carrier or region [8]. What eSIM changes is provisioning labour, carrier portability and log quality — not the security baseline.

Can I move a device to a different carrier without sending an engineer to it?

With a physical SIM, no — a carrier change requires physical access and a replacement card. With an eUICC, remote SIM provisioning downloads profiles over the air from the mobile network operator's profile management service, so the subscriber can be changed without touching the device [4]; that is a 0-site-visit operation [2].

What does IoT SIM management actually cover in a procurement contract?

At minimum: device inventory, assigned carrier profile, carrier identity (MCC/MNC), profile-switch timestamps, and the platform retention window for those records. Cellular IoT is 22% of all global connections [6], so the management layer is a per-device monthly line item on nearly any fleet-scale contract — typically €0.20–€1.00 per device per month at 1,000+ device tiers based on publicly published platform pricing.

What should a connectivity management platform log for a cold-chain or POS audit?

Carrier identity per device with a timestamp. In the deployment pattern behind this guide, carrier identity logs become the audit trail for cold-chain compliance, and the same CMP log should record MCC/MNC 63301 and any eSIM profile switch timestamp for the POS estate. Verify that the MCC/MNC in the log matches the carrier allocation named in the contract annex.

What is over-the-air SIM provisioning in practice?

It is remote SIM provisioning: SIM profiles are downloaded over the air from the mobile network operator's eSIM profile management service, and the device owner can switch or deploy a new cellular service provider at any time using RSP [4]. Operationally it converts a hardware logistics problem into a software workflow.

How much does an IoT SIM cost per device per month for rail freight?

Based on published carrier rate cards, low-data rail telematics profiles typically fall in the €1–€5 per device per month band per country profile before volume tiers, with multi-country arrangements priced separately. Any figure covering two or more carriers, a profile portfolio or a named log retention period requires a project quote rather than a catalog rate.

IoT SIM Deployment for Greenland Rail Freight: eUICC Compliance and a 500-Unit Cost Model

Q: What is an IoT SIM, and how is it different from a consumer SIM?

An IoT SIM is a subscription credential for machine-to-machine traffic, governed by the GSMA Embedded SIM Specification for M2M covering architecture, implementation, testing, security and compliance for eUICCs in M2M and IoT [5]. The practical difference for procurement is that permanent roaming restrictions apply across countries and carriers, and ignoring them creates risk for the entire project [1].

Q: What is the main difference in provisioning between eSIM and physical SIM?

Physical SIMs require manual activation steps before they connect, and at scale that means hours spent activating cards individually or navigating multiple carrier portals with different interfaces [1]. eSIM replaces that with over-the-air profile download and switching, which removes the manual activation step from the deployment checklist [2].

Q: Does GSMA certification matter at the procurement stage, or only at design?

It matters at procurement. Without GSMA specification compliance for eSIM technology, enabled devices cannot obtain the required digital certificates, which prevents them from operating effectively within the GSMA remote provisioning ecosystem [4]. Compliance certification runs against SGP.16, and the compliance process for eUICC-capable devices is described in SGP.24 [5] — both belong in the technical annex as required evidence.

September 28, 2026 · 12 min read · Regional Info

IoT SIM Deployment for Greenland Rail Freight: eUICC Compliance and a 500-Unit Cost Model

Rail freight IoT SIMs in Greenland: GSMA SGP.16 eUICC compliance, permanent-roaming checks, and a 500-unit TCO with catalog vs project quote triggers.

An IoT SIM deployment for rail freight in Greenland is the procurement and engineering process of specifying cellular connectivity for rail and intermodal assets whose final leg terminates at Greenlandic ports — and it is a multi-country eUICC estate, not a single-carrier contract. Cellular IoT accounts for 22% of all global connections [6], and every country added to the route adds a roaming restriction, a profile-switch event and an audit field to the connectivity management log.

Buying it splits two ways. Standard single-carrier IoT data plans can be ordered from catalog pricing as a per-device, per-month line item; anything touching two carriers, more than one eSIM profile, certificate lifecycle evidence or a Greenland-specific regulatory and customs review goes to project quote. Based on publicly available carrier rate cards, low-data rail telematics profiles typically sit in the €1–€5 per device per month band per country profile, and the soldered-eUICC premium over a plastic SIM socket typically falls in the €1–€5 per unit band at published module catalog pricing. Neither figure is a quote.

WHY IT MATTERS

The constraint moved from 'can I get coverage?' to 'can I prove which carrier was on the device at a given timestamp?' Traditional SIM cards require manual activation steps before they can connect, so fleet-scale rollouts mean hours spent activating cards one by one or navigating multiple carrier portals with different interfaces [1]. Permanent roaming restrictions add a second boundary: a device that sits permanently on a foreign network can be restricted, so profile localisation has to be planned at deployment stage rather than discovered on the first invoice [1].

Remote provisioning removes the site visit. An eUICC device can be re-pointed at a different carrier over the air, which is a 0-site-visit operation compared with a physical card swap [2].

Compliance is the third boundary. GSMA specification compliance is what allows an eSIM-enabled device to obtain the required digital certificates; without certification, devices cannot operate effectively within the GSMA remote provisioning ecosystem [4]. The GSMA Embedded SIM Specification for M2M defines architecture, technical implementation, testing, security and compliance for eUICCs in M2M and IoT, with compliance certification running against SGP.16 and the compliance process for eUICC-capable devices set out in SGP.24 [5].

For contracting entities inside the EU, two regimes — NIS2 and GDPR — impose strict requirements on how connected devices are managed [2]. Where the operating entity sits outside the EU, procurement teams should treat the applicable regulation set as a legal-review line item inside the project quote, not as an attribute on a catalog page.

TYPICAL APPLICATIONS

These four application profiles each map to a different buying path: a plastic Global IoT SIM, a soldered eSIM with a profile portfolio, a CMP platform subscription, or a RESTful M2M API integration.

Rail-Linked Cold Chain and Reefer Monitoring

Reefer and cold-chain units need a carrier identity record that can still be produced months after the crossing. Deployment teams report that carrier identity logs become the audit trail for cold-chain compliance, which makes the platform log — not the SIM — the deliverable being procured. Ask for the retention window in the contract: a CMP that keeps carrier identity logs for 90 days and one that keeps them for 3 years are different products selling at the same headline per-device price.

Wagon and Container Tracking Across the Rail-to-Port Handoff

Assets that change carrier footprint mid-route are the canonical eSIM case. Remote SIM provisioning lets a device download a local profile at its final destination instead of running on a home-network profile for the whole journey [6], and a fleet can be reconfigured after installation rather than at the factory [7]. If the route crosses two or more carrier footprints, price the eSIM profile portfolio into the connectivity line, not the hardware line.

POS and Freight Office Terminals

Fixed terminals still need a defensible log. For a POS estate, the same CMP log should record MCC/MNC 63301 and any eSIM profile switch timestamp, so that a dispute over a transaction window can be resolved from the connectivity record alone. That requirement turns the CMP platform and its RESTful M2M API into the deciding purchase, ahead of the per-MB rate.

Fixed Terminal Infrastructure

Gate controllers, yard lighting, weighbridges and fixed CCTV usually sit on one carrier, one profile and one country for their whole service life. That is the profile where a catalog-priced Global IoT SIM with volume tiers is sufficient, and where a multi-carrier eSIM estate is over-specified.

TECHNICAL SPECIFICATION AND COMPARISON

The two tables below cover the eight specification dimensions that change which contract you sign, and the six dimensions where eSIM and physical SIM actually diverge for rail freight. Security is deliberately included because it is the dimension most often assumed to favour eSIM.

Specification dimension	What the standard or source defines	Procurement consequence
---	---	---
eUICC form factor	Soldered chip replacing the plastic SIM card [4]	Removes SIM socket, tray and manual swap from BOM and maintenance scope
GSMA M2M eSIM specification	Architecture, technical implementation, testing, security and compliance framework for eUICC in M2M/IoT [5]	Restricts shortlist to compliant profile suppliers and management services
Compliance certification	SGP.16 M2M eSIM compliance requirements and procedures [5]	Certificate evidence must be requested before design freeze
eUICC-capable device process	SGP.24 compliance process and basic requirements [5]	Defines which modules a vendor can legitimately sell as eUICC-capable
Certificate eligibility	With no GSMA compliance, enabled devices cannot obtain required digital certificates [4]	Non-compliant parts fail at remote provisioning, not at bench test
Profile change mechanism	Over-the-air remote SIM provisioning from the MNO profile management service [4]	Eliminates physical SIM logistics, transport and customs cycles
Security baseline	All eSIM profiles must meet GSMA security requirements regardless of carrier or region [8]	One security review template covers every carrier and region
Roaming constraints	Regulations vary by country and carrier; ignoring them creates project-wide risk [1]	Adds one permanent-roaming check per country on the route

The SGP.16 and SGP.24 pair is the part typically missed in RFPs. A vendor can supply a compliant chip and still fail a rollout if the device side has not been qualified under the eUICC-capable device process [5], which is why certificate evidence belongs in the technical annex rather than in a marketing response.

Dimension	eSIM (eUICC)	Physical SIM	When to choose
---	---	---	---
Provisioning labour	Profiles downloaded over the air from a management service [4]	Manual activation steps; hours per batch across multiple carrier portals [1]	eSIM when a second site visit costs more than the eUICC premium
Carrier change	Remote profile switch, 0 physical interventions [2]	Requires physical access to the asset and a replacement card	eSIM when the asset is in transit or inside a sealed unit
Country localisation	Supports localisation for devices moving between regions [2]	Localisation needs a different card per region	eSIM when the route crosses two or more carrier footprints
Security	Similar eUICC software stack with at least equivalent security to traditional SIMs [4]	Same eUICC-class stack, at least equivalent security [4]	Security is the one row where the two do not differ
Lock-in risk	Carrier-agnostic switching reduces lock-in and manual labour costs [6]	High potential for carrier lock-in and manual labour cost [6]	eSIM for multi-year, multi-country contracts
Audit trail	CMP logs carrier identity, MCC/MNC and profile-switch timestamps	Carrier identity changes depend on manual record-keeping	eSIM when the log is a contract deliverable

Note what the comparison does not say. Read together, sources [4] and [8] support the conclusion that eSIM is not more secure than a physical SIM — both run an eUICC-class stack meeting GSMA security requirements. What eSIM changes is provisioning labour, carrier portability and log quality, which are the three lines that show up in a rail freight budget.

SELECTION NOTES

When the asset stays inside one carrier footprint for its entire service life and the data profile is small, order a plastic Global IoT SIM on catalog pricing. When the route crosses two or more carrier footprints, or when the asset is physically inaccessible for months, specify eSIM, because the alternative to a remote profile switch is a physical card change at the asset [2].

When the contract deliverable includes an audit trail — cold chain, POS, customs — the selection criterion becomes the CMP platform and its RESTful M2M API. If the platform cannot return carrier identity and an eSIM profile-switch timestamp in the same per-device record, the log will not survive an audit query, regardless of the per-MB price.

Catalog pricing is sufficient when the scope is one country, one carrier, one fixed data tier and no certificate evidence requirement. Project quote is required when the scope is two or more countries or carriers, when more than one eSIM profile is needed per device, when NIS2 or GDPR obligations attach to the contracting entity [2], or when a Greenland-specific regulatory, customs or certificate-evidence review is on the critical path.

COST MODEL / TCO

Hardware

The soldered-chip premium over a plastic SIM socket design typically runs €1–€5 per unit at published module catalog pricing. Rail-qualified enclosures, antenna placement and shock and vibration testing are project-quote items, not catalog items. At 500 units, a €3 premium is €1,500 of incremental BOM — small relative to a single blocked reefer movement.

Connectivity

Based on published carrier rate cards, low-data rail telematics profiles typically fall in the €1–€5 per device per month band per country profile, with multi-country or multi-IMSI arrangements priced separately. Volume above the bundled tier is billed per MB, so a firmware update that increases reporting frequency by 5× changes unit economics mid-contract. Treat the per-country rate card as an input to the TCO model, not as a quote.

Platform and API

CMP and API access is usually a per-device monthly fee with a platform minimum. At 1,000+ device tiers, publicly published platform pricing commonly sits between €0.20 and €1.00 per device per month, but retention window, log export frequency and RESTful M2M API call volume are the variables that move the quotation. Get the retention window and API rate limits in writing as contract terms.

Installation and Maintenance

Each avoided site visit is the payback engine. Installation, harness routing and commissioning are priced at local contractor rates and belong in the project quote; the eUICC removes SIM tray work from the maintenance scope, so the labour comparison is one commissioning visit against one commissioning visit plus N later SIM-swap visits over the contract term.

Payback Arithmetic

At a 500-unit fleet and a €3 per unit eUICC premium, incremental hardware spend is €1,500. Break-even is one avoided cross-border SIM-swap cycle across the fleet, because a swap consumes physical access, transport and often a repeat customs or sealing step. Compute payback as (site visits avoided per year × local visit cost) ÷ (eUICC premium × unit count); every input except the eUICC premium must come from a project quote.

PROCUREMENT REALITY CHECK

Scenario: a cold-chain shipper must prove which carrier served a reefer unit during a specific crossing, and a separate POS estate must reconcile transaction windows. The deciding question is not the per-MB rate — it is whether the CMP can export a per-device carrier identity log with timestamps. In the deployment pattern behind this guide, carrier identity logs serve as the audit trail for cold-chain compliance, and the same CMP log is expected to record MCC/MNC 63301 and any eSIM profile switch timestamp for the POS estate. Vendor selection so runs in three steps: (1) can the platform export those fields per device without custom development; (2) does the contract state the retention window and export frequency; (3) does the RESTful M2M API return them under the agreed call volume. Only after those three are answered does per-device monthly pricing become comparable.

FROM THE FIELD

Deployment teams report that carrier identity logs become the audit trail for cold-chain compliance; for POS, the same CMP log should record MCC/MNC 63301 and any eSIM profile switch timestamp. Procurement managers note that the MCC/MNC value captured in the log must match the carrier allocation stated in the contract annex — if it does not, the audit trail fails on the first query rather than at renewal. The operational lesson is that the SIM and the platform are bought as one system: a favourable per-MB rate on a CMP that cannot timestamp a profile switch produces an audit gap that no discount offsets.

WHEN CATALOG PRICING IS ENOUGH — AND WHEN IT GOES TO PROJECT QUOTE

Catalog pricing is enough when the deployment is one country, one carrier, one fixed data tier, no eSIM profile lifecycle beyond a bootstrap profile, and no auditor or regulator asking for a carrier identity log. At that specification the published per-device, per-month rate card is the entire cost basis, and a Global IoT SIM order can be placed without engineering review.

A project quote is required as soon as any one of five conditions is true: two or more countries or carriers on the route; more than one eSIM profile per device; NIS2 or GDPR obligations attaching to the contracting entity [2]; a contract deliverable that names the CMP log retention period and export fields; or any Greenland-specific regulatory, customs or certificate-evidence review. Each condition adds a line the catalog page cannot express — and each is a reason to re-test the design before the pilot scales to full fleet.