Separate the asset from its connectivity
A vehicle, terminal or industrial device can remain in service while its connectivity arrangement changes. The organization responsible for the device may also differ from the account that pays for its subscription.
Model the asset reference, the customer relationship and the mobile subscription separately. Their links should explain who can request a change and which system is responsible for carrying it out.
Design onboarding for the device context
A phone with an engaged user and an unattended device do not offer the same setup experience. An IoT onboarding process needs to account for the device's capabilities, available connectivity and the chosen provisioning ecosystem.
The software workflow should make progress visible even when a person is not standing beside the device. That includes clear ownership of incomplete activation and a way to reconcile the commercial record with provisioning status.
Carry the relationship through the lifecycle
Enterprise fleets change owners, departments and service requirements. A system that handles only initial activation leaves later amendments to manual work. Include suspension, reassignment and retirement in the data and order design.
This is where telecom software can be relevant to manufacturing, transportation, finance and public-sector operations without claiming to replace their specialist business systems.
- Record customer, asset and subscription relationships.
- Assign change permissions to the correct organization.
- Match provisioning to the device interaction model.
- Reconcile lifecycle changes with the connectivity provider.