Reasons for Suppressed Tasks on Proposed Work Orders

Purpose

A Task on a Proposed Work Order can be suppressed for a number of reasons.

The reason for each suppression is described in detail in the following topics:

• Suppressor Task Message
• Season Message
• Duplicates Message
• Last done Task on an outstanding Work Order Message
• Last done Task on an earlier Proposed Work Order Message
• Incomplete Configuration Message
• Task’s “Running” and Asset’s “Currently Running” settings not compatible Message

Please note!

• A Work Order cannot be created for a Proposed Work Order for which all Asset Tasks are suppressed.
• Some Proposed Work Orders include suppressed Asset Tasks as well as Asset Tasks that are due to be executed, in which case when a Work Order is created from the Proposed Work Orders then only the due Asset Tasks appear on the Work Order.
• Suppressed Asset Tasks only appear in a list of Proposed Work Orders.
• Tasks with incomplete configuration are grouped into a suppressed Proposed Work Order with Status “Configuration Incomplete” for each Site.
• The Proposed Work Order with the Proposed Work “* Tasks (nn) which could NOT be scheduled due to incomplete configuration” contains all suppressed Asset Tasks with incomplete configuration for a specific Site. The Failed Reason on the Proposed Work Order - Tasks tab identifies the Asset Task’s data field for which configuration is incomplete, for example “Last Scheduled Service Date not specified”.
• Configure the Asset Tasks correctly, delete the existing Proposed Work Orders, then generate Proposed Work Orders (with configured Tasks) before creating scheduled Work Orders.
• When using the “Schedule from Last Done” Scheduling Method then:
• • A Proposed Work Order is generated for the next occurrence of a due Asset Task.
  • Proposed Work Orders are generated for all other occurrences of the due Asset Task but the Asset Task is suppressed.
    This provides the Planner with a view of future scheduling requirements, assuming that the next occurrence is completed on the date that it is scheduled.
    The Planner must create the Work Order for the next occurrence of the Asset Task, and ensure that the Work Order and its Asset Task is are complete before generating the list of Proposed Work Orders again to generate the next occurrence of the Asset Tasks.
    For example, a monthly Asset Task was last executed in January so when Proposed Work Orders are generated its February Asset Task will be generated and the Asset Tasks for March, April etc. will be suppressed. February’s Work Order must be completed before March’s Proposed Work Order can be generated.

© 2016 Pragma