Issue Workflow between hotlink Files

[Gonzo666]

I have a serious situation where I have not found a solution (Graohisoft Germany neither):

I am working on a big project, that I split into different files because of the size of the project.

When exporting an IFC File, I export it directly from the main file because I want to export just one IFC modell and not several different modells that HVAC planers have to join together afterwards.

The problem I get is the following:

After doing a clash test (in Archicad or Solibri, it does not matter) and creating (or importing) the Issues, the components of the Issue are linked to the GUID they have in the main File.

This means that the components in an Issue, that are drawn in a File that is hotlinked, are not recognized in their source files, making the Issue workflow between hotlinked files useless and inefficient. If I want to solve the clash and modify the components in the Issue, I have to visually and manually look for them in the source file.

In other words, it is impossible to have an Issue workflow between hotllinked files.

This is a major setback in Archicad, specially for big projects that need to be split up.

I have talked to Graphisoft in Germany and they have answered that they have sent it to the developers.

Has anyone, in the same situation, found a solution or an efficient workaround for this problem?

Any toughts here, would be very, very helpful.

Thank you

[Erik Bjornhage]

Yep,

See attached Screenshots:

I have drawn an external load-bearing wall, set a door and a window then exported these as *.mod - linked into another file where I have drawn an identical wall, door and window. These are then exported (included nested) to a third file from where an IFC-export is done. You can clearly see the ID:s change. I can see how this can be a problem when trying to track and identify issues down through the model tree.

However, I can also see that @D4N  is onto something.

If you have several copies of a module in place and you find an issue with the placement of one wall in one instance, then that does not automatically mean that the issue applies to the placement of all walls. So, in order to accurately track the correct wall in the correct location the GUID cannot stay the same as in the original PLN-file throughout the model tree. Suddenly you would have a hundred walls with the same GUID - and then we have problems.

That also doesn´t mean that it's useless for large complex projects - it just means that the way we check and correct our models may have to be adjusted.

 

 

  

[Gonzo666]

Different GUIDs to avoid probelms, is ok with me.

It should be able, however, to idenifiy these Elements based on the GUID of the original File (i.e. with an internal AC attribute).

For an internal (AC--->AC) and external (IFC---> AC) Issue Workflow to work, right now, I am forced to export more Ifc Models from differnet files instead of exporting it from one main file. I am also forced to do a quality check with more files instead of one.

I need flexibilty to rapidly solve the different challenges that each BIM project brings.