Benchmark Management
Import and manage component failure benchmark data for reliability analysis.
Overview
Benchmark Management allows admins to create and maintain a dataset of historical component failure data. This data powers MineSync's reliability analytics, including Weibull analysis, fleet-vs-benchmark comparisons, vehicle risk scores, and cost impact projections.
Key Concepts
What Is Benchmark Data?
A benchmark data entry records a single component failure event:
| Field | Description |
|---|---|
| Component | The component that failed (from the component catalog) |
| OEM | The equipment manufacturer (optional) |
| Model | The equipment model (optional) |
| Hours at Failure | The operating hours when the failure occurred |
| Occurred At | The date of the failure |
| Application | The operating environment or use case (e.g., "Hard Rock Mining") |
| Root Cause | Why the failure happened (e.g., "Wear", "Contamination") |
| Data Source | Where the data came from (e.g., "OEM Bulletin", "Fleet Records") |
| Notes | Free-text notes |
How Benchmark Data Is Used
Benchmark data feeds into several analytical features:
- Lifecycle Statistics -- Average life, min/max, and sample sizes per component and model
- Weibull Analysis -- Reliability curves and hazard rates (requires at least 3 data points)
- Fleet Comparison -- Compare your fleet's actual component life against benchmark averages
- Vehicle Risk Scores -- Identify vehicles approaching benchmark failure thresholds
- Cost Impact -- Project annual maintenance costs using benchmark MTBF and historical costs
- Seasonal Analysis -- Identify failure patterns by month
- Site Comparison -- Compare component performance across mine sites
- Application Analysis -- See how operating conditions affect component life
How to Use
Adding Benchmark Data
- Navigate to Admin > Benchmark Management.
- Click Add Entry.
- Select a component from the catalog.
- Enter the hours at failure, date, and optional fields (OEM, model, application, root cause, data source).
- Save.
Bulk Import
For large datasets, use the bulk create feature:
- Prepare your data with the required fields (componentId, hoursAtFailure, occurredAt).
- Use the bulk import tool to upload multiple entries at once.
Each entry is individually audit-logged.
Editing and Deleting
- Click an entry to edit its fields. The system verifies tenant ownership before allowing changes.
- Delete entries that are incorrect. Physical deletion is used (not soft-delete).
Viewing Analytics
Benchmark analytics are available from the Benchmark section of the application (not the admin page). The admin page focuses on data management; the analytics dashboards consume the data.
Available analytics include:
- Component lifecycle stats with scope toggle (local fleet vs global)
- Model summary with change-out counts per component
- Component drill-down with histograms and percentile breakdowns
- Weibull curves for reliability modelling
- Fleet vs benchmark comparison with utilization adjustment
- Root cause breakdown charts
- Data source breakdown for data provenance
Common Questions
How many data points do I need for meaningful analysis?
Weibull analysis requires at least 3 failure data points per component. For reliable statistics, aim for 10 or more data points per component-model combination.
Can I filter benchmark data by application or root cause?
Yes. The lifecycle statistics endpoint supports filtering by OEM, model, date range, application, and root cause.
Is benchmark data tenant-scoped?
Yes. Each tenant maintains its own benchmark dataset. Data from one tenant is not visible to another.
Who can manage benchmark data?
Only Admin users can create, update, or delete benchmark data entries. All users can view the analytics.