CMMS: Compliance and Safety Operations
Recall, DVIR, and incident safety workflows with auditable operational evidence.
Capability
How it works
- 1 Compliance and safety lifecycle includes recall/DVIR/incident operations with auditable tracking.
- 2 Compliance overview scoring now incorporates recalls, DVIR defects, incident severity, DOT outcomes, and credential-risk signals.
- 3 CSA BASIC and credential health surfaces are tenant-scoped through auth-context organization resolution.
- 4 Expired qualification and recall workflows surface dispatch blockers and investigation contexts.
Operational outcomes
- Compliance and safety lifecycle includes recall/DVIR/incident operations with auditable tracking.
- Compliance overview scoring now incorporates recalls, DVIR defects, incident severity, DOT outcomes, and credential-risk signals.
- CSA BASIC and credential health surfaces are tenant-scoped through auth-context organization resolution.
Integration boundaries
- Journey Contracts (Normative)
- Crew Integration
- TMS Integration
Proof model
Feature-level proof
Compliance and Safety Operations scope is defined in product module catalog.
verified
docs/products/cmms/product.md · Module Catalog > Compliance and Safety 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.