Meter Based Pm
Meter-Based Preventive Maintenance (PM) is a maintenance strategy that triggers work orders when an asset reaches a specific usage threshold, such as runtime hours, cycles, or miles, rather than a fixed calendar date. This aligns service frequency with actual wear and tear, optimizing maintenance intervals based on real asset usage.
In shop floor maintenance, Meter-Based PM is implemented through a CMMS like ServiceGrid, where technicians configure a meter (e.g., 'Pump Runtime Hours') and set a threshold (e.g., '500 hours'). When the meter reading hits the threshold, the CMMS automatically generates a work order and updates asset history. Effective implementation requires real-time data capture via IoT or PLC, or prompt manual entry of meter readings, to ensure accurate 'Units to Go' forecasts. This approach is critical for assets with variable usage, such as pumps, conveyors, or vehicles, preventing over- or under-maintenance.
- Synchronized Meter Readings: Failure to update the CMMS meter reading immediately after service causes miscalculation of the 'Estimated Next Due Date,' leading to missed or premature PMs.
- Non-Continuous Meters: Attempting to use discrete or non-continuous meters (e.g., start-stop counters) for PMs, which only support continuous meters like odometers or flow counters.
- Low Usage Neglect: Relying solely on meter-based triggers without a time-based fallback (e.g., max 7 days without PM) for assets that rarely run, causing seal degradation or lubricant aging due to stagnation.
How does the CMMS calculate the Estimated Next Due Date for a meter-based PM?
It uses the formula: Current Date + (Units to Go / Average Units per Day), where 'Units to Go' is the difference between the threshold and the last recorded meter reading.
What is the critical difference between Meter-Based and Condition-Based maintenance?
Meter-based is predictive of wear based on cumulative usage (e.g., every 5,000 cycles), whereas condition-based is reactive to real-state anomalies (e.g., vibration > 5mm/s) triggered only when a specific condition is met.
Can Meter-Based PMs float on a fixed schedule?
Yes, if configured as floating (USETARGETDATE = 0), the system generates the work order based on the earliest of: the estimated meter reading date or the fixed time interval.