AxialOps: Dashboard & Overview
Central command center providing at-a-glance equipment health status and actionable insights with three modes: Technical Dashboard (expert users with device statistics, alert summary, vibration...
Capability
How it works
- 1 Real-time technical and executive dashboard composition (health cards, charting, KPI strips, report drill-down) with role-based visibility.
- 2 Interactive analysis launcher and study sessions that jump directly into selected vibration workflows.
Operational outcomes
- Real-time technical and executive dashboard composition (health cards, charting, KPI strips, report drill-down) with role-based visibility.
- Interactive analysis launcher and study sessions that jump directly into selected vibration workflows.
Integration boundaries
- Dashboard & Overview
- Device Management
Proof model
Feature-level proof
Dashboard & Overview scope is defined in product module catalog.
verified
docs/products/axialops/product.md · Module Catalog > Dashboard & Overview
AxialOps dashboard and overview workflows are implemented in portal-facing service modules.
verified
docs/products/axialops/product.md · Module Catalog > Dashboard & Overview
Code: backend/services/axialops/internal/modules/dashboardgateway
Contract: proto/axialops/session/v1
AxialOps analysis workflows are implemented in axialops backend modules.
verified
docs/products/axialops/product.md · Module Catalog > Analysis Workbench
Code: backend/services/axialops/internal
Contract: proto/axialops/learning/v1
Solution routes that reuse this feature
Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (0).
This feature is currently not linked to a named solution route. Review this behavior directly, then validate continuity through adjacent solution and feature-map routes.
Continuity routes for this capability
Route-level continuity checks where this feature appears in product-pair workflows.
This capability is currently mapped in adjacent solution and continuity routes. Browse linked solution routes first, then return here when cross-route continuity is expanded.
Operational validation path
Use adjacent feature and solution routes to inspect how this capability participates in cross-product execution.