One of the many cost-saving features in the RTA Fleet Management Software is the ability to track and schedule vehicle preventive maintenance (PM) schedules. PMs allow the shop to inspect vehicles on a regular, timely basis to prevent maintenance problems.
If a PM schedule is strongly adhered to, you can expect a 15% to 40% reduction in unscheduled repairs and costly road calls.
Adding PM Schedules
PM schedules and histories are set up in vehicle records. Up to 260 PMs can be tracked per vehicle, by various methods and/or a combination of methods-by meters, alternate meters, gallons, hours, days, etc.
If you wish to track PMs for equipment or other items, they must be set up as vehicles in RTA.
To set up PM schedules for an individual vehicle record, follow the steps listed below:
Add vehicle to RTA Web - refer to Adding Vehicles for instructions on adding vehicles in RTA Web
Access the Technical Info Tab from the vehicle file
Click the add PM option
Enter the PM Code - Max of 2 characters - the first character must be a letter from A-Z and the second is optional though must be a number from 0-9
Try to come up with a coding scheme that categorizes the PMs in an orderly manner. For example, many fleets use PM A for a 3000 mile service and PM B for a 6000 mile service.
Enter the VMRS Code associated with the PM - Codes 066001000 through 066009000 are set up in the RTA system for use with PMs
Start typing 066 into the VMRS field and the drop down will automatically navigate to the PM section of the VMRS list
When the VMRS code of a work order line matches exactly with the PM VMRS code, the system automatically updates the PM record when the job is complete
Refer to Work Order Table of Contents for more information on work orders in RTA Web
The PM Description will auto fill with the associated description for the VMRS code selected
Define the Interval for the PM to occur - will this PM need to occur routinely based on days, miles, or gallons
Identify the included PM - RTA is capable of nesting PMs - enter the PM code of the PM desired to nest with this PM
For example, PM A could be a lube, oil, and inspection and PM B could be a fuel filter and by nesting PM B to PM A, when PM B is completed, PM A will be included for completion as well
Nesting PMs makes data entry easier and faster because when a PM is completed, the RTA system updates that PM record as well as the nested PM record(s)