Maintenance Triggers

Preventive maintenance triggers indicate a certain interval which, when it occurs, maintenance should be done on an asset. For example, typical maintenance triggers would be when a vehicle reaches a certain number of miles, when a certain amount of time has passed, or when an asset reaches a certain number of hours of runtime.

Refer to Defining Compliance Types for more information about linking and unlinking preventive maintenance triggers.

Maintenance triggers are generally defined as one of the following:

  • Calendar Anniversary is a fixed calendar interval type where regardless of the time lapse between the work creation and completion, the future maintenance schedule date remains the same. This type of interval scheduling is generally used to fulfill regulator compliance for inspections and licensing requirements on fixed date schedules. For example, this would trigger an inspection every three months regardless of when the last inspection was completed.
  • Runtime Anniversary is a fixed interval type maintenance where regardless of the metered operation between the recent activity or service history and completion of work, the maintenance is not re-forecast. For example, this would trigger an inspection after every 100 hours of runtime service.
  • Calendar Interval is a fluid interval type where the forecasted scheduled date is adjusted and re-forecast based on the completion date of the previously completed work which is managed through service history. For example, this would trigger a pump valve cleaning every 3 months with the next trigger based on the most recent cleaning.
  • Runtime Interval is a fluid interval type where the maintenance schedule is adjusted and re-forcast based on the completion runtime readings of the previously completed activity. For example, this would trigger a pump bearing bracket cleaning every 100,000 gallons flow of water with the next trigger based on the gauge reading at the time of the last cleaning.

Maintenance Cycles

Preventive maintenance is triggered, or cycled, based on the maintenance schedule defined for the asset type. Batch processing determines when and how to create work orders depending on whether or not non-final activities already exist for the activity type and service history detailed on the maintenance trigger. Settings on the maintenance trigger such as the Allow Multiple In Process Activities flag determine whether or not a new activity is triggered if there are any non-final activities for the activity type and the asset being evaluated. If new activities should be created based on all criteria being met, the system automatically creates a work order based on the template work order indicated on the maintenance trigger.

Work records automatically generated by the system can be automatically scheduled to the field. From the maintenance trigger record, users can configure the system to automatically schedule preventive maintenance work to go to one of the crew's "Weekly" shifts. Configuration for automatic scheduling of work to a crew looks for the following conditions:

  • In the Work Order Defaults zone, Auto Schedule value is set to Yes and the Crew value is defined with a crew name. If the Crew field is vacant, scheduling looks for a crew name defined on the template work order or work activity.
  • Scheduling only considers those shifts that are in a Planning status.
  • If the generated activities have a Required By Date, only those shifts with a start date prior to the activity's Required By Date are considered. The system starts with the earliest eligible shift having enough available and remaining hours to work the job. If no shift satisfies the requirement, the system schedules the activity to the shift with the most available hours.
    Note: This feature is not applicable for activities whose activity type specifies an external system.

Users with the necessary authority in the system can manually execute maintenance triggers, as necessary, using actions on the Asset portal. Upcoming triggers are displayed in a zone in the Asset portal where users can execute the Cycle Now action to manually cycle the maintenance