Pm Route
How does a PM Route differ from a standalone PM job plan?
A standalone job plan targets a single asset; a PM Route aggregates multiple similar job plans/assets into one execution sequence to maximize technician efficiency during rounds.
What KPIs are affected by PM Route execution?
Proper route execution improves MTBF (Mean Time Between Failures) by ensuring consistent condition-based inspections and reduces MTTR (Mean Time To Repair) by catching failures early.
How should attribute variables be defined in PM Route tasks?
Each task must include explicit acceptable ranges, 'not-to-exceed,' or 'not-to-fall-below' statements to eliminate ambiguity and enable FRACAS-driven PM optimization.
When is a PM Route inappropriate?
PM Routes are unsuitable for complex, asset-specific overhauls; they are best for routine, repetitive tasks like lubrication, sensor readings, and visual inspections.
A PM Route is a logical grouping of assets and/or job plans with similar work types, such as lubrication, readings, or inspections, consolidated into a single set of execution steps for a technician. This enables efficient 'rounds' rather than individual asset visits, reducing administrative overhead and ensuring consistent coverage of critical assets.
On the shop floor, technicians execute PM Routes as lubrication rounds or data collection rounds, visiting multiple assets in a sequence to perform recurring tasks like checking pressure, verifying belt tension, or oiling bearings without stopping the workflow for individual work orders. This approach reduces administrative overhead and ensures consistent coverage of critical assets, allowing maintenance to be performed efficiently without disrupting production.
Route Disruption by Ad-Hoc Fixes: Technicians stop a PM route to fix a broken item immediately, causing the remaining tasks in the route to be skipped and never completed.
Ambiguous Task Attributes: Routes include vague tasks like 'check system pressure' without defined acceptable ranges or 'not-to-exceed' limits, leading to inconsistent data collection and missed failure indicators.
Inadequate PM Strategy: Routes rely solely on fixed time/usage intervals regardless of actual asset condition, failing to catch failures earlier on the P-F curve and resulting in unplanned breakdowns during or after the route.