Suppression banding prevents duplicate recurring work orders when one maintenance schedule already includes the work from another schedule.
This feature is useful when an asset has multiple maintenance schedules and a larger maintenance activity already includes the work performed by a smaller maintenance activity. When configured, LLumin CMMS+ can automatically skip lower-level recurring work orders when a higher-level recurring work order is due within a specified number of days.
When to Use Suppression Banding
Use suppression banding when one recurring work schedule includes all work performed by another recurring work schedule.
Common examples include:
- Monthly, quarterly, and annual preventive maintenance schedules
- Vehicle maintenance programs with minor and major service intervals
- Inspection programs where larger inspections include all tasks from smaller inspections
Do not use suppression banding if each recurring work order contains unique work that must be completed separately.
For suppression banding to work correctly, the dominant recurring work should be due on the same day as, or after, the subordinate recurring work and within the configured suppression interval.
Example
An asset has the following recurring work schedules:
- Monthly Air Filter Replacement
- Quarterly Oil Service
- Annual Major Repair
The Annual Major Repair includes the work performed during the monthly and quarterly services. In this case, the monthly and quarterly recurring work schedules can be suppressed when the annual maintenance is due.
Configure Suppression Banding
Configure suppression banding on the recurring work record that you want to suppress.
Add a Suppression Band
- Open the recurring work record that may be suppressed.
Navigate to the Suppression Banding tab.
Select Add.
Select the recurring work that should suppress the current recurring work.
Click Select.
Enter the suppression interval in days.
Save the recurring work record.
The selected recurring work appears in the Suppression Banding grid.
When the selected recurring work is due on the same day as, or within the suppression interval after, the current recurring work, the current recurring work order is not generated.
Example: Monthly and Annual Maintenance
The following recurring work schedules exist for the same asset:
| Recurring Work | Due Date |
|---|---|
| Monthly Service | December 1 |
| Annual Service | December 3 |
The Annual Service includes all work performed during the Monthly Service.
If the Monthly Service has a suppression band configured for the Annual Service with a suppression interval of 5 days:
- The Monthly Service work order will not be generated.
- The Annual Service work order will be generated.
- The Monthly Service schedule advances to its next occurrence.
This prevents technicians from performing the same maintenance activities twice.
Example: Multiple Levels of Suppression
A common configuration includes:
- Monthly PM
- Quarterly PM
- Annual PM
In this configuration:
- The Quarterly PM suppresses the Monthly PM.
- The Annual PM suppresses the Monthly PM.
- The Annual PM suppresses the Quarterly PM.
When quarterly maintenance is due, the monthly work order is skipped.
When annual maintenance is due, both the monthly and quarterly work orders are skipped.
When Not to Use Suppression Banding
Do not use suppression banding when each recurring work schedule contains different maintenance tasks.
For example:
- Monthly PM contains only filter replacement.
- Quarterly PM contains only oil changes.
- Annual PM contains only bearing replacement.
Because each recurring work order contains unique work, all three work orders should be generated when they become due.
Additional Notes
- Suppressed recurring work orders are not generated.
- Suppression does not affect the recurring schedule. The schedule continues normally after suppression.
- You can configure multiple suppression bands for a single recurring work record.
- The suppression interval applies both before and after the due date of the recurring work being evaluated.
- When a recurring work order is suppressed, the suppression is recorded in the recurring work Activity Log under Trigger History.