The setting of the Worst Case Update Threshold is entered at the AVEVA Clash Manager - Customise window. The value of the setting has a significant effect on the performance of the system. There is a large performance degradation if the setting is too low; a performance gain if the setting is correct.

AVEVA Clash Manager holds information regarding the worst case clash status of a design element. This information is used in MOM and is shown as the clash status of an item for example: PIPE, STRU, FRMW and holds the clash-free status of the controlled item.

The first method (Single Update method) involves processing an individual clash element, searching the database for the worst case and updating the element clash status accordingly. This single element processing is quick for single clashes, but its speed of processing is directly proportional to the number of clashes to be processed.

So if this method is used to process, for example, 1000 clashes, it would take approximately 1000 times longer. The second method (Global Update method) used by the software involves a Global clash worst case process and is designed to work with ALL of the clashes in the database.

Use the Worst Case Update Threshold value to determine when this more efficient Global update is triggered, rather than using the single update method, which would be very slow for large numbers of selected clashes in the clash groups grid. So, in summary, this setting value will trigger the Global update for ALL clashes in the database rather than using the single clash element processing method.

If it is preferred not to use the Global Update method, set the Threshold to a very large value so that the system never reaches the trigger point and works on the single clash-by-clash method.