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

Tower: Fleet Operations Intelligence

Correlates fleet readiness, HOS, DVIR, and exception signals into intervention-ready work queues.

Problem

Manager decisions slow down when readiness, compliance, and exception signals are fragmented by workflow surface.

Capability

Correlates fleet readiness, HOS, DVIR, and exception signals into intervention-ready work queues.

How it works

  1. 1 Persistent fleet status strip across Tower pages (on-duty, driving, off-duty, sleeper, personal/yard, in-shop, late-load, DVIR-defect, readiness-degraded...
  2. 2 Cross-page smart alerts feed with direct drill-through for HOS, DVIR, maintenance-capacity, readiness degradation, and late-load risk.
  3. 3 Fleet investigations workspace for HOS critical queue and DVIR recurring-risk cohorts.
  4. 4 Intervention queue route for manager triage across HOS critical, DVIR risk, late loads, message-SLA breaches, manual...

Operational outcomes

  • Faster intervention on risk queues across dispatch and compliance operations.
  • More coherent fleet-level decision context in a single management lane.

Integration boundaries

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

Proof model

Feature-level proof

  • Fleet Operations Intelligence scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Fleet Operations Intelligence

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