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

TMS: Dispatch Operations

Multi-panel layout for unassigned loads, available drivers, and active work.

Problem

Dispatch decisions degrade when readiness and site context are not available at assignment time.

Capability

Multi-panel layout for unassigned loads, available drivers, and active work.

How it works

  1. 1 Surface assignment candidates in dispatch workspace.
  2. 2 Apply readiness and eligibility checks.
  3. 3 Publish assignment and monitor active exceptions.

Operational outcomes

  • More consistent assignment quality under operational pressure.
  • Reduced preventable dispatch exceptions.

Integration boundaries

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

Proof model

Feature-level proof

  • Dispatch Operations scope is defined in product module catalog.

    verified

    docs/products/tms/product.md · Module Catalog > Dispatch and Operations

  • 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).