Problem
Load-board contracting and capacity sourcing foundations support DAT/Truckstop integrations and ranking.
IronKernel Platform
TMS: Load Board and Capacity Acquisition
Load-board contracting and capacity sourcing foundations support DAT/Truckstop integrations and ranking.
Capability
DAT and Truckstop foundations.
How it works
- 1 Load-board contracting and capacity sourcing foundations support DAT/Truckstop integrations and ranking.
- 2 External capacity sourcing is connected to booking/offer flow and operational assignment pathways.
- 3 Coverage Workspace now provides broker-first and carrier-first modes with capability-aware listing actions, booking queue visibility, and...
Operational outcomes
- Load-board contracting and capacity sourcing foundations support DAT/Truckstop integrations and ranking.
- External capacity sourcing is connected to booking/offer flow and operational assignment pathways.
- Coverage Workspace now provides broker-first and carrier-first modes with capability-aware listing actions, booking queue visibility, and...
Integration boundaries
- TMS↔CMMS Fleet Integration
- TMS↔Crew Personnel Integration
- TMS↔YMS Yard Coordination
Proof model
Feature-level proof
Load Board and Capacity Acquisition scope is defined in product module catalog.
verified
docs/products/tms/product.md · Module Catalog > Load Board and Capacity Acquisition
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).
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.
Continuity routes for this capability
Route-level continuity checks where this feature appears in product-pair workflows.
Compliant Speed
Formula: Crew -> TMS
Open continuity routeDetention Detection
Formula: YMS -> TMS
Open continuity routeDispatch Confidence
Formula: Crew + CMMS -> TMS
Open continuity routeOperational validation path
Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.