Zoomed Image

Generating Work Orders for non-clock based assets

xAssets Planned Maintenance User Guide
Generating Work Orders for Planned Maintenance

Generating Work Orders for non-clock based assets

This page explains how to schedule maintenance for assets that do not have clock readings — such as printers, computers, furniture, fire extinguishers, or any asset where time-based intervals are sufficient.

When to Use Time-Based-Only Scheduling

Not all assets have measurable usage. For many asset types, maintenance is simply due after a fixed period of calendar time:

Asset Type Typical Schedule
Portable appliances PAT test every 12 months
Fire extinguishers Annual inspection
Office furniture Safety inspection every 2 years
Emergency lighting Monthly functional test
IT equipment Quarterly firmware review

The Workflow

The workflow is the same three-step process used for consumption-based assets — create a Service Process, create a Service Plan, and generate work orders — but the Service Plan uses time-based Service Interval Units (Days, Weeks, Months, Years) instead of consumption-based ones (Miles, Kilometres, Running Hours).

No Asset Service Data configuration is required. You do not need to set Initial Clock, Est Clock/Year, or Last Clock Reading for time-based-only plans. The system calculates due dates entirely from the plan's start date and interval.

Example: PAT Testing Printers Every 6 Months

To schedule PAT (Portable Appliance Testing) for printers every 6 months, with the first service carried out immediately:

  1. Create a Service Process named "PAT Test" with appropriate procedures and a default priority.
  2. Deploy the Service Process as a Service Plan to all printer assets.
  3. Configure the Service Plan with Service Every = 6 Months.
  4. Check the Service Immediately option.

Service Plan configured with time-based interval of 6 months and Service Immediately enabled

The Service Immediately option ensures a work order is created for the first run, rather than waiting 6 months for the first service to become due.

Tip: When deploying time-based service plans to a large number of assets, consider leaving "Service Immediately" unchecked to avoid generating a large batch of work orders all due on the same date. Instead, stagger the Start Date across different groups of assets (e.g., floor 1 starts in January, floor 2 in February) to spread the workload evenly.