Administrative Deletion of Model Clash Issues on Model Coordination Module

[cwinchester.hmc]

When models are clashed together through a coordination space in the Model Coordination module, Issues are generated by selecting a primary model and clashing model. However, if the wrong model is chosen as primary, the issue that is created will not appear in issues panel for the desired model in Revit. But once the issue is created, it cannot be amended, deleted, or otherwise recreated. The only method available is to create a new coordination space, republish models, and re-clash. This process can easily take a full day to complete and is no guarantee that wont immediately happen again. In order to fix this problem, Account or Project Administrators should be given the ability to delete or amend issues in a Model Coordination space. Additionally, these admins should be given the ability to delete coordination spaces (currently this is not possible either). Otherwise, the Model Coordination module will be fraught with irrevocable user errors and perhaps become completely untenable product save for the most advanced and diligent users.

[ElrinaMills]

Hi,

This is true, but you do not need to go through the whole setup again. you can take the wrongly created issue and set it to void with a description saying it was created on the wrong model.

Additionally, you can easily swap between the primary and secondary model in model coordination by choosing the dropdown and selecting the other model. 

Model coordination spaces cannot be deleted but they can be made inactive by the project administrator.

It is good practice to make sure that only relevant people have access to the coordination space.

You can have multiple coordination spaces, and limit access to it.

Coordination spaces can be created from any folder, Project Files or Plans. 

Generally, it is seen as acceptable to use the Shared folder as the coordination space. The models in here get updated automatically every time a team shares a new model in Design Collaboration (Given that the Publish, package, consume workflow is being followed).

I hope this helps a bit.

[cwinchester.hmc]

Unfortunately, voiding the issue does not re-instantiate the clash. Furthermore, the models cannot be reassigned to primary versus clashing model once the issue is created. Finally, my understanding is that the coordination space does in fact need to be recreated in order to re instance clashes and allow for issues to be created as desired. That is why I'm suggesting a solution be developed to allow admins to amend and delete issues.