Skip to main content
Preços
Iniciar sessãoMarcar demo

Coordination Space

A Coordination Space defines the scope of a clash detection or IDS workflow. It allows you to select the models that will participate in a specific coordination process before creating any Clash Tests or IDS analyses. Every Clash Test and IDS analysis belongs to a Coordination Space and can only analyze the models included in that space. For this reason, creating a Coordination Space is the first step before configuring clash detection rules or IDS requirements. <img width="886" height="468" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-e97932d0914a8f72354d88028acce78f13dbdddb.png" />

Why use a Coordination Space?

Large BIM projects often contain many federated models. However, not every coordination activity needs to include all of them. A Coordination Space allows you to define a smaller working scope by selecting only the models relevant to a particular coordination objective. This makes coordination more organized, improves performance, and allows different teams or project areas to work independently. For example, although a project may contain the federated models for an entire residential development, you may want to coordinate each building separately.

Example

A residential development may include the following models:

  • Building A
  • Building B
  • Building C
  • Site Infrastructure Instead of running every Clash Test or IDS analysis against all project models, you can create separate Coordination Spaces for each area. Each Coordination Space contains only the models required for that coordination activity. <img width="523" height="410" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-b0b60dbfd4a10500df5c23e9080641b989412163.png" />

Creating a Coordination Space

  1. Open the Design module.
  2. Go to Clash Tests or IDS Library.
  3. Click New Coordination Space.
  4. Enter a name for the Coordination Space.
  5. Select its Purpose: o Clashes o IDS (Requirements)
  6. Select the models that will participate in the coordination.
  7. Choose how each model version will be managed: o Latest Version – Always uses the most recent version available in the CDE. o Pinned Version – Locks the Coordination Space to a specific model version.
  8. Save the Coordination Space.

Note: All selected models must already be available in the CDE. Once the Coordination Space has been created, you can begin creating Clash Tests or IDS analyses within it. <img width="886" height="549" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-08d9d63da5d8ae6c673154dc8a84c48718926913.png" />

Managing Coordination Spaces

Click the name of the current Coordination Space below the ribbon to open the management menu. From there, you can:

  • Create a New Coordination Space.
  • Manage the Coordination Space name, description, purpose, and selected models.
  • Duplicate the current Coordination Space.
  • Archive the Coordination Space to hide it without deleting it.
  • Delete the Coordination Space permanently. <img width="886" height="337" alt="image" src="https://svwpkiotdzcxsmuprvyf.supabase.co/storage/v1/object/public/localized-images/help-docs/ua-4d4300dc3e5f9c249b083e79e56e7c455278babe.png" />

Best practices

  • Create one Coordination Space for each coordination objective.
  • Include only the models required for that workflow. Although individual Clash Tests and IDS analyses can further restrict which models are analyzed, the Coordination Space defines the overall scope.
  • Use descriptive names that clearly identify the coordination scope, such as Building A, Tower 2, or MEP Coordination.
  • Use Pinned Versions when you need repeatable or auditable coordination results, and Latest Version when working with continuously evolving models.

Este artigo foi útil?

Voltar para Design