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

Tower: Driver Cockpit Dashboard

Consolidates driver-facing operational state and quick entry points for dispatch actioning.

Problem

Consolidates driver-facing operational state and quick entry points for dispatch actioning.

Capability

Consolidates driver-facing operational state and quick entry points for dispatch actioning.

How it works

  1. 1 Driver profile header with status, truck, location, and quick operational context.
  2. 2 Active load summary and stop timeline entry points.
  3. 3 HOS clock visualization and warning-level rendering.
  4. 4 Driver statistics for active/completed load counts and mileage context.

Operational outcomes

  • Driver profile header with status, truck, location, and quick operational context.
  • Active load summary and stop timeline entry points.
  • HOS clock visualization and warning-level rendering.

Integration boundaries

  • TMS (Primary Runtime Source)
  • CMMS (Embedded Health Context)
  • YMS (Task Execution Context)

Proof model

Feature-level proof

  • Driver Cockpit Dashboard scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Driver Cockpit Dashboard

  • Tower driver oversight and cockpit workflows are implemented in dedicated portal pages and hooks.

    verified

    docs/products/tower/product.md · Module Catalog > Driver Cockpit Dashboard

    Code: frontend/apps/portal/src/products/tower/pages

    Contract: proto/tms/loads/v1

  • Tower oversight surfaces are implemented in portal product modules.

    verified

    docs/products/tower/product.md · Module Catalog > Load and Stop Oversight

    Code: frontend/apps/portal/src/products/tower

    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 (0).

This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.

Continuity routes for this capability

Route-level continuity checks where this feature appears in product-pair workflows.

This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.