Getting Started

Onboarding IoT Gateway as your telematics provider requires integrating with Bifrost. For this integration, we handle the infrastructure deployment on our end, so your role is mainly to provide the initial requirements and verify access once everything is live.

The integration is divided into three main phases:

1. Pre-flight. Collect the information Bifrost needs to make it official. This includes business unit details, the telemetry schema, firmware integration status for each controller, and the cloud account that will be using Bifrost.
2. Onboarding Request. Submit those requirements to the Bifrost team to register your business unit, controller schemas, and consumer account. Once submitted, our team handles the setup and deployment, with no further action needed on your side.
3. Validation Checklist. Follow our validation checklist to confirm you can access all the functionalities available.

Integration deliverables

Once the integration is complete, you will have access to the following resources:

• This handbook, your guide to using Bifrost.
• The API Reference, covering endpoints to register devices, issue commands, or collect telemetry.
• IAM roles bifrost-prod-viewer-{businessUnitKey}-role, bifrost-prod-editor-{businessUnitKey}-role, and bifrost-prod-owner-{businessUnitKey}-role. See Permission Levels.
• A telemetry data stream, bifrost-prod-telemetry-{businessUnitKey}. See Where Data Lands.

info

The {businessUnitKey} refers to the key provided in pre-flight. AWS resources are named after it for consistency.

Technical support

During your integration, raise any blockers or questions in your project's Tier 1 or Tier 2 meetings, where the Bifrost team tracks progress with you, or reach the team directly at bifrost.support@carrier.com. For common questions, check the FAQ, or review the platform architecture in IOTCL Design.