How to Configure Maintenance Types (Desktop)

Users may assign a Maintenance Type to Maintenance Requests and Work Orders. Maintenance Types can be one of the Tenna default types or a custom type that users configure. Below are details on how to manage Maintenance Types.

Permission Requirements: Users must have the Maintenance Settings permission enabled in order to manage Maintenance Types.

There are Tenna default Maintenance Request Types that cannot be renamed or deleted:

  • Repair
  • Damage
  • Warranty
  • Accident
  • Preventative Maintenance

đź’Ą 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

Click on "Settings" on the top right side of the screen.


2

Click on the "Configurations" tab and then click on "Maintenance".

3

Scroll down to Maintenance Types.

You will see the Tenna default Maintenance Types. These cannot be edited or deleted.

4

Select to apply the Maintenance Types to Work Orders and/or Requests.

Using the check boxes next to each Maintenance Type, users can select to allow each Maintenance Type to be applied to either Maintenance Requests or Work Orders.

For example, the below configuration would mean that Work Orders will not show “Accident” as a possible choice for Maintenance Type when creating a work order. Similarly, “Warranty” will not be a possible choice for Maintenance Type when creating a Maintenance Request.

5

To create a custom Maintenance Type, select "Add Type".

6

Enter a custom Maintenance Type and select Work Orders and/or Maintenance Requests with the checkboxes.

7

Select the checkbox icon under the Actions column to save the new Maintenance Type.

You can also select the “x” icon to remove the new Maintenance Type.

Select "Add Type" again to create additional custom Maintenance Types.

8

Click "Update" to finish.

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