Clash Sets

It is recommended that the number of Clash Sets for a project is kept to a minimum.

There are no limits on how the Clash Sets are structured, for example, by area, discipline, design status or combinations of these. The following examples show how Clash Sets have been configured:

• By design area and discipline – with structural as the obstruction and all other disciplines checked against the structures

• By design discipline and design status – with disciplines checked against each other based in model design status. An example of this approach is to only clash check items with built or checked status

• By design area/sub-area, discipline and design status – for a large project, it may be necessary to subdivide design areas into smaller sub-areas, strips or modules, in order to complete a clash set or series of clash sets overnight, in batch mode. These smaller Clash Set runs execute quickly, but incur additional administrative overhead to coordinate the Clash Set execution.

It is recommended that the administrator constructs their own Obstruction, Check and Exclude lists using wildcards, where possible. This reduces the amount of administration required during the life of the project, because, as sites, zones or elements are added or deleted from the design databases, they will be automatically included or removed from Clash Set lists that use wildcards.

AVEVA has seen a number of situations where clients have started a project with a large number of clash sets (x100s) and, through experience gained during the life of the project, have rationalised these down to a more manageable number (x10s). Therefore, before implementing Clash Manager, think carefully about the approach you will take when defining your Clash Sets, and make sure the number of Clash Sets is kept to a manageable size.