CMMS: Dashboarding, Reporting, and Analytics
Multi-widget dashboard composition for multiple operational roles via Connect RPC (list, get active, set active, upsert, delete).
Capability
How it works
- 1 Multi-widget dashboard composition supports role-specific layouts, persistence, and operational alert thresholds.
- 2 Fleet health, cost, and compliance analytics now expose scheduled reporting and export-ready outputs.
- 3 Dashboard KPI summaries are server-side, quick actions are role-filtered, and mismatched placeholder widgets are removed.
Operational outcomes
- Multi-widget dashboard composition supports role-specific layouts, persistence, and operational alert thresholds.
- Fleet health, cost, and compliance analytics now expose scheduled reporting and export-ready outputs.
- Dashboard KPI summaries are server-side, quick actions are role-filtered, and mismatched placeholder widgets are removed.
Integration boundaries
- Journey Contracts (Normative)
- Crew Integration
- TMS Integration
Proof model
Feature-level proof
Dashboarding, Reporting, and Analytics scope is defined in product module catalog.
verified
docs/products/cmms/product.md · Module Catalog > Dashboarding, Reporting, and Analytics
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.