IronKernel Platform

TMS: Personnel Operations (Personnel Ops Module)

TMS owns driver operational state (HOS, GPS location, truck assignment, availability, performance metrics).

Problem

TMS owns driver operational state (HOS, GPS location, truck assignment, availability, performance metrics).

Capability

TMS owns driver operational state (HOS, GPS location, truck assignment, availability, performance metrics).

How it works

1 Personnel service owns operational state (HOS/GPS/truck/availability/onboarding/performance/retention) with clean TMS-only proto surface.
2 Onboarding, batch readiness checks, and assignment workflows are integrated with Crew and dispatch gates.

Operational outcomes

Personnel service owns operational state (HOS/GPS/truck/availability/onboarding/performance/retention) with clean TMS-only proto surface.
Onboarding, batch readiness checks, and assignment workflows are integrated with Crew and dispatch gates.

Integration boundaries

TMS↔CMMS Fleet Integration
TMS↔Crew Personnel Integration
TMS↔YMS Yard Coordination

Proof model

Feature-level proof

Personnel Operations (Personnel Ops Module) scope is defined in product module catalog.
verified
docs/products/tms/product.md · Module Catalog > Personnel Operations (Personnel Ops Module)
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.

Open solution Open feature map

TMS overview Dispatch Operations Readiness and Eligibility

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.

Open solution Open feature map

CRM overview Intake and Qualification Conversion and Provisioning

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.

Open solution Open feature map

CMMS overview Maintenance Operations Asset Dispatchability

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.

Open solution Open feature map

YMS overview Gate Operations Dock Scheduling

Continuity routes for this capability

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

Compliant Speed

Formula: Crew -> TMS

Open continuity route

Detention Detection

Formula: YMS -> TMS

Open continuity route

Dispatch Confidence

Formula: Crew + CMMS -> TMS

Open continuity route

Operational validation path

Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.

Back to TMS Back to feature index View solution pathways Get in touch