Unit Maintenance Plans

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.4.
For the latest version of this help file can be found here.

< Previous section | Table of Contents | Index | Next section >

In order to use MainBoss's facility for generating planned maintenance work orders, you must connect three things:

Tasks: what work should be done (see Tasks)
Timing: when the work should be done (see Maintenance Timings)
Units: where the work should be done (see Units)

Unit maintenance plans put it all together. Once you've created a unit maintenance plan, MainBoss can create planned maintenance work orders for all the appropriate units. The work orders are created using information from the task record, and according to the schedule given by the timing record.

Timing Basis: The timing basis for a unit maintenance plan helps to determine when PM jobs should be scheduled. For example, suppose you do a particular job several days later than it was actually scheduled. The next time you do the same job, should it be scheduled relative to when the job was supposed to be done or when it was actually done?

As an example, suppose a particular job takes several days. If the job is supposed to be done every 90 days, does that mean 90 days after the job starts or 90 days after the job ends?

To answer such questions, a unit maintenance plan offers you several options for how you reschedule the next job. These options are called the timing basis. Possibilities are:

Work Start: The next job is scheduled relative to the "Work Start Date" of the previously scheduled job. (This is the "Work Start Date" as stated in the job's work order; MainBoss assumes that this date reflects when the job was actually started.)

Work End: The next job is scheduled relative to the "Work End Date" of the previously scheduled job. (This is the "Work End Date" as stated in the job's work order.)

Scheduled Date: The next job is scheduled relative to when the previous job was supposed to take place, whether or not the job was actually done on that date. Note that the other two possibilities (Work Start and Work End) use the actual start and end dates, which may not be the same as the dates originally scheduled.

Specifying the Schedule Basis: When you first set up a unit maintenance plan, you must select the schedule basis. This tells MainBoss when to start the clock ticking for future tasks.

For example, suppose you're setting up MainBoss and you specify that a particular vehicle needs an oil change every three months. During set-up, you have to tell MainBoss the last time the vehicle had an oil change; then MainBoss can correctly schedule oil changes in future.

Similarly, when you buy new equipment that needs planned maintenance, you must specify when to start the clock for future maintenance. Usually, you start the clock on the day you start using the equipment.

For tasks that are scheduled by meter readings rather than date, the schedule basis is the meter reading on which to base future planned maintenance. For example, if a vehicle gets an oil change every 3000 miles, the default schedule basis is the odometer reading for the most recent time the oil was changed.

You may choose to change the schedule basis after your maintenance plan has begun. For example, suppose you're repairing a vehicle and you decide to do an oil change at the same time, even though the oil change isn't due yet. You would specify the schedule basis as the current date, so that the next oil change will take place at the proper time.

Scheduling Examples: Suppose you want a particular job to be scheduled on the second Tuesday of every month. You can do this using a month schedule (see MonthScheduleEditor) with the following settings:

Create a maintenance timing record with a period of one month (i.e., one month between jobs).
In the Exceptions section of the timing record, turn off every day of the week except Tuesday.
In the unit maintenance plan record, set "Timing Basis" to Scheduled Date. This ensures that the next job is based on when the previous job was supposed to be done, as opposed to when it was actually done.
Lastly, click Change Schedule Basis. This opens a window where you can set the schedule basis to the second Tuesday of the past month. (For example, if it's now October 1, set the schedule basis to the second Tuesday in September.) This starts the clock ticking on the second Tuesday in September, so the next job will be scheduled for the second Tuesday in October.

You can use a similar procedure for schedules like "the first Friday of the month" or "the fourth Monday of the month". Unfortunately, there's no good way to do "the last Monday of the month" since some months have four Mondays while others have five Mondays. For most organizations, however, "the fourth Monday of the month" is probably an acceptable compromise for "the last Monday of the month".

As another example, suppose you want a job to be done on the 15th of every month. The process is similar:

Use a maintenance timing record with a period of one month.
In the unit maintenance plan record, set "Timing Basis" to Scheduled Date.
Click Change Schedule Basis and set the basis to the 15th of the previous month. For example, if it's now May, set the basis to April 15. This ensures that the next job will be scheduled for May 15.

Deferrals and Inhibits: If there are days that a particular job can't be done, what do you do if the job comes due on such a day? For example, what if a job can only be done on weekends but it comes due in the middle of the week? MainBoss offers you two choices:

You can defer the job. This means delaying the job until the first day it can actually be done. For example, if a job can only be done on weekends but it comes due on Wednesday, you can defer the job until Saturday.
Alternatively, you can inhibit the job. This means skipping the job entirely. You don't do the job until the next time it comes due.

In most cases, you'll defer jobs rather than inhibit them. However, consider a job like "Sweep all sidewalks." You might do this job every day you're open for business; however, on days when you're not open, you can safely skip the job.

For more on deferrals and inhibits, see Maintenance Timings.

Unscheduled Maintenance Plans: You can use unit maintenance plans to create immediate work orders. For example, suppose a car isn't due for an oil change but for some reason you want to do an oil change anyway. The New Unplanned Maintenance Work Order button (found in Unit Maintenance Plans) can create a corresponding work order immediately, without going through the usual scheduling process.

This same facility can be used to create standardized work orders for jobs which aren't typically done on any schedule. For example, consider the job of changing a car's muffler. While this is a common sort of job, it's done as needed rather than following a schedule.

You can still create a unit maintenance plan for this sort of job. As usual, this unit maintenance plan will have a task (describing what should be done in the muffler change) and a unit (specifying which car should have its muffler changed). However, for the maintenance timing record, you can specify one that has no associated periods. Such a timing record indicates that the job never comes due on its own; the job will only be done when you explicitly click New Unplanned Maintenance Work Order.

Using this approach, you can associate any number of standardized unscheduled jobs with a unit. For example, you can write up standardized task descriptions for all standard maintenance jobs on cars and create unit maintenance plans for those jobs on every car you maintain. In each case, the unit maintenance plan will have a maintenance timing record that has no periods, so the job will never come due on its own. Instead, you can just use New Unplanned Maintenance Work Order whenever you want to do the job on the car. You only have to write up the job description once (when you create the task record); from that point on, you can create immediate work orders from the unit maintenance plan.