Business outcome
The revenue engine. Full EDI suite and automated load tendering to optimize your distribution network and carrier performance.
Transportation Management
TMS is IronKernel's transportation operating system for planning, dispatching, executing, and settling freight moves across company assets and brokered capacity.
The revenue engine. Full EDI suite and automated load tendering to optimize your distribution network and carrier performance.
Transportation Management
Each deep product includes feature pages with problem/capability flow and evidence references.
Trip/Stop migration is staged with quote-to-delivery lifecycle support for multi-stop and partial/LTL workflows.
Open featureMulti-panel layout for unassigned loads, available drivers, and active work.
Open featureCarrier network lifecycle includes profile management, tender negotiation, and response/counter workflows.
Open featureBilling and AR workflows deliver invoice lifecycles, payment allocations, collections, and automated reminders.
Open featureTMS owns driver operational state (HOS, GPS location, truck assignment, availability, performance metrics).
Open featureDVIR capture and defect workflows are reachable through DriverService and integrated with workflow surfaces.
Open featureCustomer profile and rate-management models support carrier/customer operations and credit/rate workflows.
Open featureLoad-board contracting and capacity sourcing foundations support DAT/Truckstop integrations and ranking.
Open featureDocument intake paths ingest portal/mobile/API/email payloads into settlement/dispute contexts.
Open featureEDI 204/990/214/997 lifecycle supports trading partner onboarding and polling/control operations.
Open featureContext-linked messaging, participant workflows, and persisted conversation history are fully implemented.
Open featureAnalytics runtime delivers operational KPI, billing, retention, and forecast dashboards from live domain tables.
Open featureMulti-channel notification, subscription control, and delivery health monitoring are implemented across transport targets.
Open featureTelematics ingestion supports ELD mappings, adapter orchestration, and sync workers with tenant-safe persistence.
Open featureCopilot now persists and streams chat sessions with tenancy-aware attribution and reader-safe consumption.
Open featureThese solution routes consume this product to validate cross-flow continuity and buyer outcomes (4).
Dispatch confidence
Outcome: Dispatch decisions are anchored in shared readiness and asset state before assignment.
Dispatch decisions are stabilized when readiness, credentials, and asset state are checked before assignment.
Commercial to execution
Outcome: Converted commercial records move into execution with less re-entry and clearer ownership.
Commercial handoff friction drops when conversion and execution planning are connected by shared identifiers.
Maintenance and dispatchability
Outcome: Asset maintenance posture and dispatchability context remain visible through execution windows.
Maintenance posture remains actionable when dispatchability and work execution share the same readiness context.
Yard throughput
Outcome: Site execution is coordinated through shared gate, dock, and appointment workflows.
Gate, dock, and appointment behavior stays coordinated when yard workflows are linked to dispatch context.
Power-pair routes compress solution continuity into evaluation runbooks for this product.
Compliant Speed
Formula: Crew -> TMS
Open continuity routeDetention Detection
Formula: YMS -> TMS
Open continuity routeDispatch Confidence
Formula: Crew + CMMS -> TMS
Open continuity routeProduct-level proof
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
TMS dispatch operations consume readiness and fleet state through dedicated dispatch runtime modules.
verified
docs/products/tms/product.md · Module Catalog > Dispatch and Operations
Code: backend/services/tms/internal/modules/dispatch
Contract: proto/tms/dispatch/v1
Dispatch workflows are implemented in dedicated operations modules.
verified
docs/products/tms/product.md · Module Catalog > Dispatch and Operations
Code: backend/services/tms/internal/modules/dispatch
Contract: proto/tms/dispatch/v1
TMS carrier and brokerage workflows are implemented for carrier selection and lifecycle operations.
verified
docs/products/tms/product.md · Module Catalog > Carrier and Brokerage Operations
Code: backend/services/tms/internal/modules/carriers
Contract: proto/tms/carriers/v1
TMS billing and A/R workflows are implemented with dedicated service modules and finance contracts.
verified
docs/products/tms/product.md · Module Catalog > Billing and Accounts Receivable
Code: backend/services/tms/internal/modules/billing
Contract: proto/tms/billing/v1
TMS personnel operations are supported through personnel modules and organization boundaries.
verified
docs/products/tms/product.md · Module Catalog > Personnel Operations (Personnel Ops Module)
Code: backend/services/tms/internal/modules/personnel_ops
TMS DVIR and compliance evidence captures are implemented through inspection and messaging flows.
verified
docs/products/tms/product.md · Module Catalog > DVIR (Driver Vehicle Inspection Reports)
Code: backend/services/tms/internal/modules/dvir
Contract: proto/tms/health/v1
TMS customer and rate management surfaces are implemented for pricing and configuration workflows.
verified
docs/products/tms/product.md · Module Catalog > Customer and Rate Management
Code: backend/services/tms/internal/modules/customers
Contract: proto/tms/customers/v1
TMS load board and capacity operations are implemented through loadboard modules.
verified
docs/products/tms/product.md · Module Catalog > Load Board and Capacity Acquisition
Code: backend/services/tms/internal/modules/loadboard
Contract: proto/tms/loads/v1
TMS document and OCR workflows are implemented in document service modules.
verified
docs/products/tms/product.md · Module Catalog > Document and OCR Workflows
Code: backend/services/tms/internal/modules/documents
Contract: proto/tms/documents/v1
TMS EDI trading flows are implemented as dedicated exchange pathways.
verified
docs/products/tms/product.md · Module Catalog > EDI Workflows
Code: backend/services/tms/internal/modules/edi
Contract: proto/tms/edi/v1
TMS messaging and collaboration are implemented through conversation and notification modules.
verified
docs/products/tms/product.md · Module Catalog > Messaging and Collaboration
Code: backend/services/tms/internal/modules/messaging
Contract: proto/tms/messaging/v1
TMS analytics and executive intelligence use dedicated analytics modules and query contracts.
verified
docs/products/tms/product.md · Module Catalog > Analytics and Executive Intelligence
Code: backend/services/tms/internal/modules/analytics
Contract: proto/tms/analytics/v1
Move into feature detail pages, then follow cross-product pathways to validate execution continuity.