Tolerance in Servicing Plans
The GENERATEWORKORDERSTOLERANCE setting controls whether an asset that is close to (but has not yet reached) a service threshold gets flagged for immediate service. This page walks through an example showing how tolerance affects work order generation.
Example scenario
- A vehicle is added with an Initial Clock of 19,600 miles
- Estimated usage: 20,000 miles per year
- Service Plan: minor service every 20,000 miles
- GENERATEWORKORDERSTOLERANCE: 5 (meaning 5%)
The asset’s service data (Maintenance > Service Data in the Asset Editor):
With 5% tolerance
Generating work orders with these settings:
The result is four outstanding work orders:
The initial clock reading of 19,600 is within 5% of the 20,000-mile service interval (the tolerance window starts at 19,000 miles), so the system flags an immediate service. Subsequent services follow the normal annual schedule.
With 0% tolerance
Setting the tolerance to 0 (no tolerance) and running the same process produces only three work orders, with the first service scheduled a year out:
This demonstrates that tolerance is useful for catching assets that are nearly due for service, avoiding a situation where an asset just misses a service window and has to wait a full additional cycle.
Related Articles
- Creating a Service Plan — How to create a service plan
- Generating Work Orders — How the system generates work orders
- Service Interval Units — Available units for service intervals
- Asset Clock Readings — Managing clock-based readings for assets