Skip to main content
Preise
AnmeldenDemo buchen

Clash Tests

The Clash Tests page is the central workspace for organizing, managing, and running clash detection tests in a Coordination Space.

From this page, you can create and organize Clash Tests, run clash detection, monitor the latest run, and access the detected clashes in Clash Results.

Each Clash Test belongs to a Coordination Space and uses the models available in that space.

<img width="886" height="468" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-d777f53aaa2f9de5871ff99564dc09c9bccdc960.png" />

Before you start

Before working with Clash Tests, you need a Coordination Space configured for clashes.

The selected Coordination Space determines which Clash Tests and folders are displayed. You must select a Coordination Space before you can create a new Clash Test or folder.

For information about creating and configuring a Coordination Space, see Coordination Spaces.

Understanding the Clash Tests page

The Clash Tests page includes:

  • Ribbon — provides commands for creating, organizing, running, and managing Clash Tests.
  • Folders panel — organizes related Clash Tests into folders.
  • Search — helps you find Clash Tests by name or other searchable information.
  • Coordination Space selector — determines which Coordination Space you are working in.
  • Clash Tests table — displays the available tests and information about their configuration and latest results.

The table can display information such as the Clash Test name and type, default assignee and priority, workflow status counts, latest run status, and last update.

You can customize the visible columns to focus on the information that is most relevant to your coordination workflow.

Organizing Clash Tests with folders

Folders help organize related Clash Tests within a Coordination Space.

For example, you can create separate folders for architectural, structural, or MEP coordination tests.

Use New Folder to create a folder. You can then select a folder in the folders panel to display its Clash Tests.

You can also:

  • Rename a folder.
  • Move one or more Clash Tests to another folder.
  • Delete a folder.

If you delete a folder that contains Clash Tests, BIMWorkplace allows you to either move the tests to another folder or delete the folder together with its tests.

Important: If you choose to delete the tests, their Clash Results are also deleted.

<img width="886" height="218" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-83bb734eab70ae07e09eb453766df1a4f1931e73.png" />

Managing Clash Tests

The available commands depend on your permissions and on the selected Clash Tests.

CommandDescription
New RuleCreates a new Clash Test in the current Coordination Space.
OpenOpens the selected Clash Test to view or edit its configuration, depending on your permissions.
DuplicateCreates a copy of the selected Clash Test. Only one test can be duplicated at a time.
Move to FolderMoves the selected Clash Tests to another folder.
Move to SpaceMoves the selected Clash Tests to another Coordination Space.
Copy to SpaceCreates a copy of a Clash Test in another Coordination Space. Only one test can be copied at a time.
Edit PermissionsChanges access permissions for the selected Clash Tests.
DeletePermanently deletes the selected Clash Tests and their results.

Additional actions are available from the menu at the end of each Clash Test row, including running the test, viewing results, viewing run history, viewing evolution statistics, editing the test, and activating or deactivating it.

Activating and deactivating Clash Tests

A Clash Test can be Active or Inactive.

Deactivate a test when you want to keep its configuration and existing information but do not want it included when running all active tests.

You can activate it again when it is needed.

Running Clash Tests

You can run Clash Tests individually or execute multiple tests together.

  • To run an individual test, open its row menu and select Run Rule.
  • To run specific tests together, select them and click Run Selected.
  • To run all active Clash Tests in the current Coordination Space, click Run All.

Run All only runs Active Clash Tests. Inactive tests are not included.

After an execution starts, use the Last Run column to monitor its status.

<img width="886" height="276" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-b2bf5d7711b27baec53242a0e3ce857526234ba9.png" />

Viewing results, history, and statistics

Open the menu at the end of a Clash Test row to access information from previous executions.

  • View Results opens Clash Results for the selected test.
  • View History displays previous runs of the test.
  • Evolution displays statistics showing how the test results have evolved.

For information about reviewing and managing individual detected clashes, see Clash Results.

Managing Clash Test permissions

Access to individual Clash Tests can be controlled separately from the general Geometry Check permissions.

If no specific permissions have been configured for a Clash Test, access follows the user's Geometry Check permission in the Project Permissions.

When specific permissions are assigned to a Clash Test, access becomes restricted to the users, teams, and companies included in those permissions. Project Managers retain full access.

Use Edit Permissions to manage permissions for one or more selected Clash Tests.

Users with read-only access can view a Clash Test but cannot modify its configuration or perform actions that require edit access.

Deleting a Clash Test

Deleting a Clash Test permanently removes the test and all Clash Results associated with it.

BIMWorkplace asks you to confirm the action before deleting the test.

Warning: Deleting a Clash Test and its results cannot be undone.

If you only want to stop using a test temporarily, consider deactivating it instead.

Best practices

  • Give Clash Tests descriptive names that clearly indicate their purpose or the elements being checked.
  • Use folders to keep large sets of Clash Tests organized.
  • Create focused tests for specific coordination objectives instead of relying on a small number of very broad tests.
  • Deactivate tests that should no longer be included in Run All but may be needed again later.
  • Keep each Coordination Space focused on a clear coordination objective.

War dieser Artikel hilfreich?

Zurück zu Design