Problem
Asset readiness signals are often fragmented, forcing dispatch on stale assumptions.
IronKernel Platform
CMMS: Asset Dispatchability
Multi-asset registry with normalized identity and operational status across 27 asset types — 16 fleet types (tractor, trailer, chassis, straight truck, etc.) and 11...
Capability
Multi-asset registry with normalized identity and operational status across 27 asset types — 16 fleet types (tractor, trailer, chassis, straight truck, etc.) and 11...
How it works
- 1 Asset registry and fleet dispatchability now support 27 asset types with lifecycle + readiness scoring.
- 2 Dispatch and assignment decisions consume canonical fleet scoring and maintenance blockers.
- 3 Asset filtering now surfaces all registered fleet and hardware asset types for operator workflows.
Operational outcomes
- Shared view of dispatch-ready assets across teams.
- Lower risk of assignment to non-ready assets.
Integration boundaries
- Journey Contracts (Normative)
- Crew Integration
- TMS Integration
Proof model
Feature-level proof
Asset Dispatchability scope is defined in product module catalog.
verified
docs/products/cmms/product.md · Module Catalog > Asset Registry and Dispatchability
CMMS asset dispatchability state is maintained in fleet modules and shared to downstream execution planners.
verified
docs/products/cmms/product.md · Module Catalog > Asset Registry and Dispatchability
Code: backend/services/cmms/internal/modules/assets
Contract: proto/cmms/fleet/v1
CMMS dispatchability workflows are implemented in asset and fleet modules.
verified
docs/products/cmms/product.md · Module Catalog > Asset Registry and Dispatchability
Code: backend/services/cmms/internal/modules/assets
Contract: proto/cmms/fleet/v1
Solution routes that reuse this feature
Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (2).
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.
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.
Continuity routes for this capability
Route-level continuity checks where this feature appears in product-pair workflows.
Dispatch Confidence
Formula: Crew + CMMS -> TMS
Open continuity routeDispatchability Assurance
Formula: Crew + CMMS -> TMS
Open continuity routeHealthy Yards
Formula: CMMS + YMS
Open continuity routeOperational validation path
Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.