A PM schedule controls when a PM task recurs. When you add a schedule to a PM template, Limble generates the PM task on the timing you set, so recurring maintenance goes out on its own without someone creating it each time.
You can add a schedule when you build a PM template or add one to an existing template later. Each template holds its own schedule, and you can turn a schedule on or off without deleting it.
Schedule types
There are three schedule types. When you pick a type, the schedule shows only the fields that type needs, so you set just the timing that applies.
Time-based schedules repeat on a calendar interval:
Daily - repeats every set number of days.
Weekly - repeats on chosen days of the week.
Monthly - repeats on a chosen day or week of the month.
Yearly - repeats on a chosen date each year.
Usage-based - repeats after the asset runs a set amount of usage (e.g., run hours or cycles).
Threshold-based - repeats when an asset number field reaches a set value.
Usage-based and threshold-based schedules read from asset numerical data, so the asset needs a number field set up for these to work.
Active and inactive schedules
A schedule is either active or inactive.
An active schedule generates PM tasks based on the schedule's timing.
An inactive schedule is saved on the template but does not generate tasks, so you can pause recurring work without losing the schedule setup.
Create and manage PM schedules
Important to know: some PM scheduling functionality is not available in the new Limble desktop experience yet.
To use advanced scheduling options (like holidays, seasons, and stacked PMs) return to Limble legacy. Once configured in legacy, they will carry over to the new desktop.
A single PM schedule can't yet be applied to multiple assets.