Problem
Reactive maintenance dominates when PM and work-order signals are not operationally integrated.
IronKernel Platform
CMMS: Maintenance Operations
Work order lifecycle is implemented end-to-end with server-persisted checklist execution, blockers, and technician workflow handoff.
Capability
PM schedules with auto-linking to matching asset cohorts.
How it works
- 1 Work order lifecycle is implemented end-to-end with server-persisted checklist execution, blockers, and technician workflow handoff.
- 2 PM and DVIR work-order creation paths now enforce duplicate-open-order prevention and asset-required creation.
- 3 Work-order execution can create inventory part orders directly from technician workflow context.
- 4 Labor timing and work order assignment flows are integrated with Crew readiness decisions.
Operational outcomes
- Higher preventive maintenance adherence.
- Reduced maintenance-driven operational disruption.
Integration boundaries
- Journey Contracts (Normative)
- Crew Integration
- TMS Integration
Proof model
Feature-level proof
Maintenance Operations scope is defined in product module catalog.
verified
docs/products/cmms/product.md · Module Catalog > Maintenance Operations
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.