How To Prevent Batch Work Generation from Stopping

Did you know that there are things you can check to help ensure automatic Batch Work Generation does not stop for any of your assets?

Blue Mountain RAM’s Batch Work Generation (BWG) feature automatically and regularly reads your Asset Event Schedules and creates Work for them as their Due Dates come into the range specified. However, certain scenarios can stop the Work records from being made when they should be.

Let’s take a look at what can stop BWG and how you can prevent them:

1. Asset Event lists unassignable Measurement Data Templates (MDT) or Work Plan Templates (WPT)

MDTs and WPTs have a status in which they are unassignable. BWG will not add work for an Event listing an unassignable object.

How to prevent it: Ensure that users change the status of MDTs and WPTs in a timely fashion so work generation is only halted appropriately. Ensure that retired or obsolete MDTs and WPTs are immediately unlisted from active Events.

2. The Event Schedule does not have a Due Date

If users forget to fill-out the schedules, BWG has nothing to respond to and work will not be generated.

How to prevent it: Ensure that when events are added, their schedules are immediately completed, including the Due Date. Use Quick Find to search your All Asset Schedules query: Due Date IS EMPTY. Supply missing data.

3. No rule assigned for Work to be created

Work generated for scheduled Events uses the rule listed for them on the parent Event’s field, ‘Work Rule To Assign’. If this is blank, the default rule specified in Dataset Options is used. If both are blank, BWG will stop.

How to prevent it: Ensure that users always complete the Event’s ‘Work Rule To Assign’ field. Ensure that each dataset lists Default Rules for Work in Dataset Options. Use Quick Find to search your All Events query: Work Rule to Assign IS EMPTY. Supply missing data.

4. Work record field cannot hold quantity of data from a linked field

If the data in the source field cannot fit in the receiving field, BWG will not add the work record.

How to prevent it: Ensure that users know about any limits for a field sending data to a work record field. Consider avoiding such links in future configurations.

5. Status of parent Asset or Event has ‘Exclude from BWG’ enabled

The purpose of the exclusion setting is to suspend automatic work generation. For example, Inactive or Retired assets probably should not have work generated until they are no longer Inactive or Retired.

How to prevent it: Ensure that users update the status of Assets and Events in a timely fashion, so work generation is not halted longer than it should be.

6. Creation of Work is to generate a Notification, but Notification-related settings are incomplete or incorrect

If Rule configuration to send a Notification as Work is added cannot be fulfilled, then the Work will not be added and BWG fails.

How to prevent it:  Ensure that Notification and Mail configurations in Blue Mountain RAM and SQL Server are tested and correct.

7. A Work record that documents the Schedule’s Due Date already exists

BWG checks existing Work records and will not add a second one for the same Event schedule.

How to prevent it: Ensure that users know Work records are automatically generated. Users should view and/or search queries to find their work records. Train users in the use of Quick Find and Quick Search.

For further information, consult your Blue Mountain RAM User, Administrator and Installation Manuals. If necessary, please contact our friendly Support Technicians at with questions. Also, please enjoy calling and speaking with your Regional Sales Manager (RSM) at 800-982-2388 if you are interested in Blue Mountain RAM training or services.

Leave a Reply