< Previous section | Table of Contents | Index | Next section >
The Preview button of the Work Orders —> Generate Work Orders window displays a preview of work orders that are to be generated for preventive maintenance tasks. Note that the previewing facilities do not actually generate the work orders themselves; the preview shows work orders that will be generated if you tell MainBoss to go ahead.
The preview window contains the following:
- Start Work: This column lists the starting date for each work order.
- Task: This column lists the identification code for the corresponding task.
- Unit: This column lists the equipment or space involved in the work order.
- Trigger: This column lists the "trigger point" for each job. The meaning of "trigger point" depends on whether a particular job is scheduled by date or by meter reading.
If a job is scheduled by date, the trigger point is the date when the job would be scheduled if not for other factors. For example, suppose a particular job is intended to be done on the first of every month, except when that day falls on a weekend. In this case, "Trigger" will be the first of the month, even if "Start Work" is bumped to the following Monday.
If a job is scheduled by meter readings, the trigger point is the meter value when the preventive maintenance job becomes necessary. For example, suppose that work on a piece of equipment is required when the meter reaches 1000; also suppose that your workers enter meter readings every day, and one day the reading is entered as 1005. The trigger point is reported as 1000, even though the reading actually recorded was 1005.
- Disposition: This column provides additional information about the job. Possibilities include the following:
- Generate: The job will be generated normally.
- Skip: A job may be skipped when it has a seasonal schedule. For example, if a job comes due in January, but the schedule says the job is only required from April to October, the job may simply be skipped.
- Defer: A job is deferred when it cannot be carried out on the trigger date. For example, if a job comes due on a weekend but the schedule says that job can only be performed on weekdays, the job will be deferred until the following Monday. Jobs may also be deferred when they are overdue; for more information, see Specifying Task Schedules.
- Forecast: A prediction of when a job should occur. This is used for tasks scheduled according to meter reading; using previous meter readings, MainBoss estimates when the appropriate meter will reach the trigger point for the job.
- (Seasonal): Used in connection with Skip and Defer to indicate that a trigger date fell in the off-season.
- (Weekday): Used in connection with Skip and Defer to indicate that a trigger date fell on a disallowed day of the week.
- (Overdue): Used in connection with Skip and Defer to indicate that the trigger date for a job has already passed.
- (Existing W/O): Used in connection with Skip and Defer to indicate that the trigger date occurs before the Work End date of an existing (open) work order or a proposed work order for the same unit.
- (Disabled): Used in connection with Skip and Defer to indicate the entire schedule has been disabled with Do not use this schedule.
- Also reschedules: Used when a scheduled job has the effect of rescheduling other jobs (for example, when work scheduled by meter reading has the effect of rescheduling work by date on the same unit).
- No Schedule Basis, skipped: Indicates that the "Schedule Basis" field in the unit schedule was left blank. Since "Schedule Basis" specifies a starting point for MainBoss's scheduling facilities, MainBoss cannot create a schedule for the unit. For more about "Schedule Basis", see Specifying Task Schedules.
- Insufficient readings, skipped: Indicates that a schedule is meter-based but MainBoss does not have enough meter readings to establish a schedule.
- Meter reading codes: A number of codes may be used in connection with meter readings (either in the Trigger or Disposition column):
- +/-: Reading was extrapolated from existing readings.
- 1 (superscript): Only one reading has been made on the meter.
- ?: Meter reading appears to have been entered incorrectly. This means that one or more readings are lower than previous readings. (All meter readings are supposed to increase over time rather than decrease.) The associated message is usually Insufficient readings, skipped.
- 0 (superscript): No data exists for predicting a future reading.
- Errors: If a line contains a ! character, it indicates a scheduling error. This may appear in the date and/or a meter reading.
- Generate: Clicking Generate tells MainBoss to go ahead and generate the work orders as displayed. After the work orders have been created, MainBoss closes both the preview window and the "Generate Work Orders" window.
- Cancel: Clicking Cancel returns to the previous window without generating work orders.
For more about preventive maintenance in general, see Tasks. For more about generating work orders, see Generating Preventive Maintenance Work Orders. For more about setting up preventive maintenance schedules, see Scheduling preventive maintenance jobs.
< Previous section | Table of Contents | Index | Next section >
