Using issues in the Hypermodel | Design Collaboration

[Juan_Yusta_f]

Hi everyone

I'm working with a several companies in a project together in ACC. We are using Design Collaboration to work with colaborative design. The fact is, when a "company A" (architectural team) create Issues in the Hypermodel, the issue is displayed for "company B" (structural team) when they are asigned, but they only can see the issue in the panel, but not in the model.

How can we create issues in the hypermodel to other teams? o what's the best workflow to do it?

We need that team A can create issues and team B can see those in the same hypermodel or shared model.

PS: Team A have their folder and Team B too, team B doesn't have access to team A files.

Thanks in advance!

[andr3sant0s]

Hi @Juan_Yusta_f 

The reason why Team B can't see the placement of the issue it's because they don't have permissions to view the file.

This file is stored in the Team A folder and the placement is a hyperlink for that specific file.

In order to Team B to be able to see the placement you need to give permission to that folder.

[Juan_Yusta_f]

Hi @andr3sant0s , thanks for the response,

There's a way to create and manage issues without adding permisions to other team folders? I mean, each team has is own folder privately, so, what's the recomended workflow to manage issues to every team?

I was thinking on create a federated model with the "views" tool of the models from the shared folder, so everyone has access to that folder. It's that a solution?

We need a hypermodel to put issues visibles to everyone

[andr3sant0s · Accepted solution]

The issue permissions have nothing to do with permission to files.

You can have an issue admin but that won't solve your problem.

The workflow that I suggest is having a BIM Coordinator for the entire project, this member will have access to both teams folders and will be able to create the issue to the specific team.

Your suggestion of having a federated model from the shared folder is valid, but with this option you won't have the issue placed in the model used work in progress.

[Juan_Yusta_f]

Thanks @andr3sant0s  for your response,

---

The workflow that I suggest is having a BIM Coordinator for the entire project, this member will have access to both teams folders and will be able to create the issue to the specific team.

---

So you're saying that this bim coordinator will take the issue and create it in the other team's model?
Currently the architect created the issue in the hypermodel and the engineer can't see it, so this "bim coordinator" should take that issue and create it in the engineer's folder?

Can you recommend another way to have the issues in a single federated model? Or is it easier to just give the engineer viewing access to the architect's folder?

I'm just trying to find the best alternative, I know there are several ways!

Thanks again

[Chad-Smith · Accepted solution]

---

@Juan_Yusta_f wrote:

I mean, each team has is own folder privately, so, what's the recomended workflow to manage issues to every team?

---

You partially answered your question with this comment.

Design Collaboration is by design intended to be used for private team review. You have your Working model which is supported by Consumed models, and these are all found in your Team's Project Model. You will never see a Shared model in your Project Model; it must by Consumed.

This means that all Issues raised in your Project Model are private to your own Team.

You can create an Issue against another Team's model, but you need to select their Shared model on the Timeline and explore it.

For entire project collaboration (all Teams), you are much better to use Model Coordination.

I generally like the features in Design Collaboration, but it is too confusing for most users, especially those users who are new to it.

[admaecc211151]

I have same question.

Since all models have the same coordinates, why can't the issues just lead me to the coordinate (and create a temp section box if there is) in my current model?

[Juan_Yusta_f]

Thank you @Chad-Smith and @andr3sant0s !!

It make more sense now 👌