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

Tower: Documents and Messaging

Manages operational documents and messaging with readable grouping, permissions, and operator workflows.

Problem

Manages operational documents and messaging with readable grouping, permissions, and operator workflows.

Capability

Manages operational documents and messaging with readable grouping, permissions, and operator workflows.

How it works

  1. 1 Driver document list with type, size, and timestamp context.
  2. 2 Upload flow for core operational document classes (BOL, POD, receipt, photo, other).
  3. 3 Driver conversation feed with date grouping and unread badges.
  4. 4 Template-assisted outbound messaging workflow for dispatch/safety scenarios.

Operational outcomes

  • Driver document list with type, size, and timestamp context.
  • Upload flow for core operational document classes (BOL, POD, receipt, photo, other).
  • Driver conversation feed with date grouping and unread badges.

Integration boundaries

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

Proof model

Feature-level proof

  • Documents and Messaging scope is defined in product module catalog.

    verified

    docs/products/tower/product.md · Module Catalog > Documents and Messaging

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