Skip to main content
IronKernel
Products Solutions For Customers About FAQ Contact
IronKernel Platform

TMS: Telematics and External Provider Integrations

Telematics ingestion supports ELD mappings, adapter orchestration, and sync workers with tenant-safe persistence.

Problem

Telematics ingestion supports ELD mappings, adapter orchestration, and sync workers with tenant-safe persistence.

Capability

Multi-provider ELD adapter framework with Geotab reference implementation.

How it works

  1. 1 Telematics ingestion supports ELD mappings, adapter orchestration, and sync workers with tenant-safe persistence.
  2. 2 Geofence-aware event generation and background sync provide robust provider and snapshot operations.

Operational outcomes

  • Telematics ingestion supports ELD mappings, adapter orchestration, and sync workers with tenant-safe persistence.
  • Geofence-aware event generation and background sync provide robust provider and snapshot operations.

Integration boundaries

  • TMS↔CMMS Fleet Integration
  • TMS↔Crew Personnel Integration
  • TMS↔YMS Yard Coordination

Proof model

Feature-level proof

  • Telematics and External Provider Integrations scope is defined in product module catalog.

    verified

    docs/products/tms/product.md · Module Catalog > Telematics and External Provider Integrations

  • TMS load lifecycle orchestration includes planning, persistence, and downstream contract surfaces.

    verified

    docs/products/tms/product.md · Module Catalog > Load Lifecycle and Planning

    Code: backend/services/tms/internal/modules/loads

    Contract: proto/tms/loads/v1

  • TMS load lifecycle workflows are implemented in service modules and proto contracts.

    verified

    docs/products/tms/product.md · Module Catalog > Load Lifecycle and Planning

    Code: backend/services/tms/internal/modules/loads

    Contract: proto/tms/loads/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (4).