Connectivity
Choosing an IoT SIM: questions to ask before a device rollout
A SIM that connects on a desk is only the start. Verify the network, management tools and recovery process your devices will need once they leave the office.
- Device + SIM
- Mobile network
- Application
A successful first connection proves that a device can connect under the conditions of that test. It does not prove that a fleet will remain manageable across locations, outages and years of service. A procurement brief should cover those conditions before comparing the price of a SIM or a data bundle.
Our recommendation is to evaluate the whole connectivity service. Whether a supplier calls a plan an IoT SIM, an enterprise SIM or a consumer plan tells you less than its documented capabilities, restrictions and support arrangements. Ask for evidence against the device requirements rather than assuming that a category label guarantees suitability.
Verify the exact radio and location
Record the modem model, supported bands, firmware, antenna and intended radio technology. Ask the provider to confirm the networks available under the actual subscription, in the actual deployment locations.
Soracom’s SIM documentation illustrates why this matters: network availability differs by radio technology, and matching frequency bands alone does not establish that a particular network offers the required service. This is provider documentation, not a coverage promise for TERA CONNECT or another supplier.
For a hypothetical sensor rollout, test a device inside its enclosure at the intended installation position. A desk test near a window is not a substitute for a test inside a cabinet. Record connection attempts and recovery after power loss, not only the strongest signal reading.
Ask what the operations team can control
Fleet management deserves its own acceptance criteria. Soracom documents SIM management and connection-status information as part of its service. Use that as an example of a capability to investigate, not a feature to assume every supplier includes.
Ask your candidate providers to demonstrate activation, suspension, usage monitoring and access permissions. If your own systems need to perform these actions, request the API documentation and test error handling. Confirm what happens when a device exceeds its data allowance and who receives the notification.
Compare proposals with a checklist
This checklist is a suggested procurement aid. The answers should come from the provider and a representative pilot.
Scroll sideways to compare all columns.
| Question | Evidence to request |
|---|---|
| Will this modem connect where it is installed? | Network and radio compatibility confirmation, followed by an on-site test |
| Can we diagnose a disconnected device? | A demonstration of connection history, usage and available diagnostics |
| What happens during abnormal data usage? | Written limits, alerts, charges and suspension behavior |
| Where does the traffic go? | A data-routing diagram for the selected plan and locations |
| Can we change connectivity without visiting the device? | Supported provisioning method and a demonstrated recovery procedure |
| What happens at the end of the contract? | Export, transfer, deactivation and replacement terms |
Separate routing from coverage
A local radio connection and the path to your application are separate questions. Soracom’s rendezvous-point documentation describes how traffic routing depends on subscription and device location. Other providers may use different arrangements.
Request a diagram showing the mobile network, provider infrastructure and application destination. Test the resulting path against the application’s response-time requirements. If private connectivity is required, ask how it is provided and which responsibilities remain with the application team. A SIM label alone is not a security assessment.
Check the device lifecycle
Physical form factor and remote provisioning are different considerations. The GSMA specifications catalogue distinguishes consumer eSIM specifications from the SGP.32 IoT specification. Do not assume that an eSIM-capable device supports every provisioning workflow.
Ask which specification and implementation the proposed hardware supports, what services are required, and how a failed profile change is recovered. Demonstrate that process before installing devices that are difficult to reach. Keep a record of who can authorize changes and how the device will be retired.
TERA CONNECT covers connectivity within AMMEGATECH, including IoT SIM. A practical starting brief includes device details, installation locations, expected data patterns and the required recovery behavior. Use the pilot to resolve those questions before committing the wider fleet.