The setting of the Worst Case Update Threshold is entered at the Clash Manager Options form. 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. The principles are as follows.

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 e.g. PIPE, STRU, FRMW and holds the clash-free status of the controlled item. The software has two ways of updating this status as a result of the user, or a clash run, changing the clash status of an 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 you were to use this method 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. As this involves processing large amounts of data the software utilises more sophisticated processing methods to speed things up. The second method is used at the end of every clash run to determine the worst case clash status for all elements in the database.