Zoomed Image
USA
800 691 9120
UK
01225 704844

Asset Clock Readings

xAssets Planned Maintenance User Guide
Asset Service Data

Asset Clock Readings

This page explains the clock reading fields on the Asset Service Data screen, how the system uses them to calculate service due dates, and best practices for keeping readings up to date.

What Are Clock Readings?

Clock readings track an asset's usage over time and are essential for consumption-based service intervals. The system uses these readings to calculate when an asset is due for its next service. Common examples include odometer readings for vehicles, running hours for generators, and page counts for printers.

In the example below, a vehicle's clock is recorded in miles from the odometer.

Screenshot

Clock Reading Fields

Initial Clock

The clock reading on the day servicing begins for this asset. You must enter this value before generating any work orders.

  • When to set: Before the first Generate Work Orders run for this asset.
  • Once set: After the first work order has been generated, changing this value has no effect on future calculations.
  • Example: A new vehicle joins the fleet with 12,780 miles on the odometer. Enter 12780 as the Initial Clock.

Est Clock / Year

The estimated annual usage (e.g., 20,000 miles per year). The system uses this to project when the clock will reach the next service threshold.

  • If not specified, the system attempts to calculate annual usage from the difference between the Initial Clock and the Last Clock Reading.
  • Without either an estimated or actual reading, clock-based servicing cannot be scheduled.
  • Example: A delivery van averages 25,000 miles per year. Enter 25000 as the Est Clock/Year.

Last Clock Reading

The most recent actual reading, entered together with the Last Clock Reading Date. Update this as often as readings are available — it can also be updated electronically if the asset supports telemetry integration.

The system factors this reading into work order generation for more accurate scheduling. The more frequently you update the reading, the more accurately the system can predict when the next service is due.

Tip: When you record a clock reading in the Servicing section of a work order, the asset's Last Clock Reading and Last Clock Reading Date are updated automatically. This means that closing a work order after completing a service keeps the clock data current without a separate update step.

How Clock Data Affects Work Order Generation

The system calculates the projected service date as follows:

  1. Takes the Initial Clock (or Last Clock Reading if available)
  2. Adds the service interval (e.g., 10,000 miles)
  3. Divides the remaining distance by the estimated annual usage to project the date
  4. If the projected date falls within the generation window (From Date to End Date), a work order is created

The GENERATEWORKORDERSTOLERANCE setting can flag assets that are close to (but have not yet reached) their service threshold for immediate service. See Tolerance in Servicing Plans for a worked example.

Best Practices

  • Update clock readings regularly — stale readings lead to inaccurate scheduling. Aim for at least monthly updates.
  • Set Est Clock/Year even if you update actual readings regularly — it provides a fallback for calculation if a reading is missed.
  • For fleet vehicles, consider integrating with telematics systems to automate clock reading updates via data transformations.