Onboarding New CMPs
IoT.live supports onboarding new Connectivity Management Platforms (CMPs) into its unified orchestration framework.
CMP onboarding enables enterprises to:
- Centralise connectivity management
- Harmonise operational workflows
- Integrate lifecycle orchestration
- Support eSIM provisioning workflows
- Expand multi-carrier operations
[IMAGE PLACEHOLDER: CMP onboarding overview]
CMP onboarding overview
The platform documentation describes IoT.live as a:
- CMP aggregation platform
- Unified orchestration framework
- Multi-carrier operational management layer
Onboarding a new CMP allows the platform to integrate:
- Connectivity lifecycle management
- Usage reporting
- Provisioning workflows
- Batch operations
- eSIM orchestration
within a single operational environment.
Typical onboarding objectives
CMP onboarding commonly supports:
- Enterprise connectivity consolidation
- Carrier expansion
- eSIM lifecycle orchestration
- Multi-region deployments
- Operational automation
- Unified inventory visibility
Typical onboarding scenarios include:
- New carrier adoption
- Enterprise migration projects
- Global deployment expansion
- eSIM provisioning initiatives
Supported integration models
The platform documentation references support for:
- Pure SOAP API integrations
- Pure REST API integrations
- Hybrid API integrations
- Reporting-feed integrations
- CMP-specific operational connectors
The onboarding process depends on:
- CMP architecture
- API availability
- Operational capabilities
- Reporting support
- Lifecycle orchestration compatibility
[IMAGE PLACEHOLDER: Supported integration models]
Recommended onboarding workflow
Typical CMP onboarding process:
- Validate CMP compatibility
- Establish API access
- Configure integration credentials
- Test inventory retrieval
- Validate lifecycle operations
- Configure reporting workflows
- Test batch operations
- Validate async orchestration
- Execute pilot deployments
- Expand production rollout
[IMAGE PLACEHOLDER: CMP onboarding lifecycle]
API integration requirements
CMP onboarding may require:
- API credentials
- Technical documentation
- Endpoint access
- Authentication configuration
- Reporting feed access
Depending on the CMP environment, integrations may use:
- SOAP APIs
- REST APIs
- Export/report feeds
- Hybrid operational workflows
Inventory validation
Early onboarding stages should validate:
- Subscription visibility
- Inventory synchronisation
- Status mapping
- Identifier consistency
- Usage visibility
Recommended validation includes:
- ICCID verification
- IMSI visibility checks
- Lifecycle status mapping
- Rate plan retrieval validation
Lifecycle orchestration validation
A critical onboarding step is validating:
- Connectivity lifecycle behaviour
- Provisioning workflows
- Batch operations
- Async processing
- eSIM lifecycle alignment
Recommended validation workflows include:
- Status changes
- Rate plan updates
- Batch operations
- Export workflows
- Provisioning orchestration
[IMAGE PLACEHOLDER: Lifecycle validation workflow]
eSIM orchestration alignment
Where eSIM workflows are required, onboarding should validate:
- eIM compatibility
- SGP.22 support
- SGP.32 support
- Activation code workflows
- Lifecycle synchronisation
The documentation strongly recommends:
- Using CMPs already supported within IoT.live where possible
- Validating orchestration behaviour carefully before production rollout
Reporting and export validation
Operational visibility should be validated during onboarding including:
- Usage reporting
- Inventory exports
- Audit visibility
- Historical reporting
- Async operation tracking
Reporting capability may vary depending on:
- Carrier implementation
- CMP architecture
- API maturity
- Regional deployment model
Pilot deployment strategy
Recommended rollout strategy:
- Complete technical validation
- Onboard limited pilot inventory
- Test operational workflows
- Validate lifecycle orchestration
- Monitor async behaviour
- Expand deployment gradually
This reduces:
- Operational risk
- Provisioning inconsistencies
- Carrier integration conflicts
- Lifecycle alignment issues
[IMAGE PLACEHOLDER: Pilot deployment workflow]
Operational governance
Enterprise onboarding projects should establish:
- Operational ownership
- Access controls
- Audit procedures
- Rollback planning
- Monitoring processes
- Deployment governance
Recommended governance includes:
- Segregated testing environments
- Controlled rollout phases
- Operational approval workflows
- Structured audit tracking
Common onboarding challenges
Typical onboarding challenges may include:
- API limitations
- Reporting inconsistencies
- Lifecycle mapping differences
- Async processing behaviour
- Carrier-specific operational models
Recommended mitigation strategies:
- Validate workflows early
- Execute pilot testing thoroughly
- Monitor orchestration behaviour carefully
- Maintain detailed onboarding documentation
Security considerations
CMP onboarding may expose:
- Operational lifecycle controls
- Provisioning systems
- Usage reporting
- Customer inventory
- Connectivity workflows
Recommended controls include:
- Dedicated integration credentials
- Restricted operational permissions
- Audit logging
- Secure credential storage
- Segregated testing environments
CMP onboarding should always be validated carefully before enabling production orchestration workflows.
Best practices
Recommended CMP onboarding practices include:
- Validate compatibility early
- Test lifecycle workflows thoroughly
- Use staged rollout strategies
- Monitor async operations fully
- Audit operational activity consistently
- Align CMP onboarding with eSIM orchestration planning