How to Create a Preventive Maintenance Service Package (Desktop)

A PM Service Package is a group of one or more Services that is applied to individual assets or all assets in particular category.

Pro Tip! Setting up a PM Service Package is the second step to configuring standard preventive maintenance alerts on your assets for future maintenance scheduling.

View How to Create a Service (Desktop) to complete the first step in this workflow.

Permission Requirements: Users must have the Maintenance Settings permission turned on in order to create a preventative maintenance service package.

💥 Maintenance is a premium product and requires a separate license. Please contact your Account Manager for more information on premium product licenses or reach out to Customer Support at [email protected] or call 888.836.6269.

1

Navigate to the Create PM Service Package page.

You can access the Create PM Service Package page by:

  • Selecting “Settings” in the top navigation bar, then the Maintenance tab, then “Create PM Service Package”
  • Selecting Maintenance in the left side navigation bar, then Preventative Maintenance, then “Create PM Service Package”

2

Create PM Service Package title.

Pro Tip! Remember that this package will be a group of individual services, so name it wisely. For example, “500 Hour Service” or “Emission Inspection”.

Your package title must be unique, meaning you cannot name it with the same title as an existing package.

3

Select (+) Add Services to assign services to the package.

Select from the list of existing services by selecting the checkbox next to each service. When finished selecting, select Add Services on the bottom right.


4

In the next section, select (+) Add Assets.

Apply the PM Service Package to assets by selecting the checkbox next to each one.

To easily find assets:

  • Use the Search bar
  • Use the Filters

Pro Tip! Filter down your grid based on Category, Designation Type, Organization, Asset Status and/or Fuel Type. Then, select the top column checkbox to bulk select all assets in the filtered grid.

5

Select "Create PM Package Trigger".

6

Create a PM Package Trigger.

The way you configure your PM Service Package trigger will determine how the package is automated. There are two trigger options: Package or Service.

6a

Choose the Package Trigger.

Package Trigger allows you to create a custom trigger for this package, overriding the triggers set for the individual services within the package.

To trigger the package based on Usage:

  1. Select Hours or Miles depending on the asset type intended for this service.
  2. Select a Service Occurrence: One Time or Recurring
  3. Select a Trigger Value:
    1. For One Time, enter a value for the number of hours or miles the asset should reach to trigger the service. The service will trigger when the hours or miles of that asset read the entered value. The service will not recur.
      1. Use case: An asset with a x-mileage/hour warranty, and want to service the asset prior to the warranty running out.
    2. For Recurring, enter a value for the number of hours or miles that the service should re-trigger.
      1. Enter values for the start and end of the schedule.
      2. For example: If you intend to trigger this service every 1,000 miles, beginning at 50,000 miles and ending at 100,000 miles, the service will be triggered again at 51,000 miles, 52,000 miles, and so on until it reaches 100,000 miles and stops triggering.

Note: An end value is optional. If an end value is not entered, the service will continue to trigger forever until manually stopped or deleted.

  1. Select a Scheduling Preference
    1. “No, Always Use My Trigger Value”: The next service will trigger at your specified, fixed number of Hours or Miles. The Hours/Miles of the last performed service (if done off-schedule or prior to a trigger) will not impact this fixed trigger. This selection is more predictable.
      1. For example: If you set a 5,000-mile recurring trigger, the service will trigger every 5,000, 10,000 15,000 miles regardless of when the service actually takes place.
    2. “Yes, Adjust it Every Time a Service is Completed”: The next service will trigger based on when the last service was performed. Unlike the Original Service Trigger, the Last Serviced Trigger countdown will re-start and build off the hours or miles specified on the asset when it's last service was approved. This selection is less predictable.
      1. For example: If you set a 5,000 mile recurring trigger and service is approved (completed) at 4,000 miles, the next service would trigger at 9,000 miles.

  1. Set a Reminder
    1. None: No reminder will be sent.
    2. Hours or Miles (depending on your selection): Enter value for reminder to send x hours or miles before the service is triggered.
      1. Example: If you set a 5,000 mile recurring trigger and enter 100 as the value for the reminder, the chosen receivers will be reminded of the upcoming service every 4,900 miles.
    3. Percentage: Enter a value for reminder to send x% before the service is triggered.
      1. Example: If you set a 1,000 hour trigger and set the reminder for 80%, the reminder will be sent when the asset reaches 800 hours.
    4. Select who will be reminded:
      1. This list populates from your Org Chart. Select the check box next to the job title to select all people in that job title. You can also select the file icon next to the job title to open a list of all people in that job title and individual select specific people.

Note: This reminder is tied to the New Upcoming Preventative Maintenance notification. Users that are not part of a Permission Code/Group with the notification "on" and set to Relevant Users (or do not have data access control for the service's assigned assets) will not receive this notification.

To trigger the package based on Time:

  1. Select a Frequency
    1. One Time: Select the single date you want the service to trigger on. This service will not recur.
    2. Daily: Enter a value for the number of days between each service trigger. In the below example, the service will trigger every 90 days starting on 10/25/23. The service will no longer trigger after 3/31/24.

      Note: An end value is optional. If an end value is not entered, the service will continue to trigger forever until manually stopped or deleted.

    3. Weekly: Enter a value for the number of weeks between each trigger. Select the days of the week. Select a starting date and (optional) end date.
      1. Selecting multiple days in the week will result in triggers for each of the days selected. The below example would trigger each week on Monday and Friday.
    4. Monthly: Enter a value for the number of months between each trigger. Select a starting date and end date.
    5. Yearly: Enter a value for the number of years between each trigger. In the example below, the service will trigger every year on the 1st of January and July.
  2. Set a Reminder
    1. None: No reminder will be sent.
    2. Days: Enter a value for the number of days before the service is triggered for the reminder to be sent.
    3. Select Recipients:
      1. Select the check box next to the folder to select all users with that title.
      2. Select the folder icon to open the folder and select individual users under the title.

Note: This reminder is tied to the New Upcoming Preventative Maintenance notification. Users that do not have this notification turned on (or do not have data access control for the service's assigned assets) may not receive this notification.

6b

Choose the Service Trigger.

Service Trigger will trigger each service in the package by their pre-configured individual triggers.

If you select Service Trigger, you will be able to confirm or edit the next interval for each usage-based service.

Time Based services cannot be edited.

Any services added that are not compatible will show an error message.

7

Select "Create PM Service Package"

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.