Maintenance Timings

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

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

Maintenance timing records are used when scheduling planned maintenance jobs. A timing record represents information like "every three months" or "every second Tuesday" or "every 5000 kilometers".

Most timing records are simple. However, some maintenance organizations have complicated scheduling needs ("every ten days, but weekends don't count and never schedule the job on Mondays because Joe doesn't work that day"). MainBoss can accommodate such complexities, but setting up such a schedule requires more work.

Periods: A single timing record can contain several conditions under which a job be done. For example, vehicle oil changes are often required every three months or 3000 miles, whichever comes first. Therefore, MainBoss lets you create a single timing record with two conditions: one for "every three months" and another for "every 3000 miles". (These conditions are called periods.) A job with such timing will be done when either condition comes true.

Enabled Days: In many organizations, some or all of the personnel only work on weekdays. Therefore, planned maintenance jobs shouldn't be scheduled on weekends. In other situations, however, certain types of jobs should only be scheduled on weekends, to avoid interfering with normal weekday operations.

To accommodate such considerations, MainBoss lets you specify which days of the week are acceptable for a particular job. For example, suppose a timing record has checkmarks for Monday through Friday, but not for Saturday or Sunday. This says that any jobs using this timing should only be performed on weekdays, not on weekends. Therefore, MainBoss will never schedule such jobs for Saturday or Sunday.

As another example, if you only checkmark Wednesday (with all other days blank), MainBoss will only schedule corresponding jobs on Wednesdays. You might do this if you want to schedule a job for the first Wednesday in every month.

Seasons: MainBoss lets you specify timing based on seasons. For example, you might perform planned maintenance on air-conditioners in summer but not in winter; you might perform planned maintenance on heaters in winter but not in summer. Therefore, every timing record lets you set "Season Start" and "Season End" values if you wish. For example, if you set "Season Start" to May 1 and "Season End" to October 31, corresponding maintenance jobs will only be scheduled between those two dates.

Seasons are often related to "cold weather/hot weather" distinctions, but they don't have to be. For example, the maintenance department in a shopping mall might try to avoid scheduling work during the busy Christmas shopping season. Similarly, the maintenance department for a school might try to schedule certain types of jobs for holiday periods when there will be no students around.

Deferrals and Inhibits: If you tell MainBoss not to schedule jobs for certain days of the week or for certain times of year, what should MainBoss do if a job comes due on a date that's not allowed?

For example, suppose you say that a job should be scheduled every 30 days. What happens if the next job should be scheduled for a Saturday, but Saturdays aren't permitted?

Normally, you want MainBoss to schedule the job for the next permissible day. For example, if the job should be scheduled on Saturday but you've ruled out weekends, you probably want MainBoss to schedule the job for the first acceptable day (Monday). In some cases, however, it may be more appropriate to skip the job completely. This is particularly true of seasonal jobs; if you want to skip certain jobs in summer, you probably don't want them all to be scheduled for the first day after summer ends.

Therefore, MainBoss gives you the option of saying, "Schedule as soon as possible after the date" or "Just skip the job and catch it the next time". This applies in three different situations:

Overdue work orders: A work order is overdue when the job comes due before the date when you generate planned maintenance work orders. For example, you generate new work orders on June 4, but there was a job you should have done on June 1. Your options are:

Defer overdue work orders to the date maintenance is generated: In our example, this means scheduling the job for June 4, the day you generate the work orders.

Inhibit generation of overdue work orders: This means skipping the work entirely—you missed the June 1 date, so you'll do the job the next time it comes around on the schedule.

Seasonal exceptions: This applies when a particular job is seasonal (for example, you only inspect air-conditioners during summer months). You state the start and end dates of the season when the job can be scheduled, then you specify one of the following options:

Defer work orders triggered outside the season until the start of the season: In our air-conditioner example, this means scheduling the next inspection for the starting day of the summer months.

Inhibit generation of work orders outside the season: This means skipping the work entirely—if a job comes due outside the season, just ignore it. You only do jobs that come due within the season.

Weekday exceptions: This applies when a particular job can only be done on certain days of the week. You specify which days are allowed, then you specify one of the following options:

Defer work orders triggered on disabled weekdays until the next enabled weekday: For example, if a job can only be done on Saturdays and it comes due on a Thursday, you schedule the job for the Saturday as soon after the Thursday as possible.

Inhibit generation of work orders on disabled weekdays: This means skipping the work entirely—if a Saturday job comes due on a Thursday, you just don't do it. You keep skipping the job until it actually comes due on a Saturday.

These options are set on a record-by-record basis. You can specify which jobs should be skipped and which should be scheduled as soon as possible after they come due.

Scheduling Jobs: The process of scheduling jobs goes like this:

  1. Create a task record that describes the job. (For details, see Tasks.)
  2. Create a maintenance timing record that describes the schedule, e.g. every 3 months.
  3. Create a unit maintenance plan record that assigns timing to a task, and specifies which units should be scheduled for such tasks. For details, see Unit Maintenance Plans. That section also contains a number of scheduling examples.

For information on viewing timing records, see Viewing Maintenance Timing Records. For information on creating and editing timing records, see Editing Maintenance Timing Records.

See Also:

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