Hello,
As everyone knows, tagging linked elements results often with disassociated tags and the need to verifying/rework the tags. This is the way Revit works.
Now the question : our BIM manager advises that keeping all worksets open will help with this problem. Can anyone confirm that his advises have some logic behind them?
Opening all the worksets in our case takes at least 20gb of memory and occasionally we are slowed down by the lack of memory - especially when workin with multiple models (with all the worksets open). The BIM representative doesn't seem to consider lack of memory to be a problem.
Thank you in advance!
Gelöst! Gehe zur Lösung
Gelöst von SteveKStafford. Gehe zur Lösung
Gelöst von cbcarch. Gehe zur Lösung
Gelöst von SteveKStafford. Gehe zur Lösung
What's more important is that you reload linked files involved before sync'ing work. Tags disappearing is usually related to changes to an element that prevent Revit from recognizing those elements as the "same". If you reload the linked file(s) that is changing routinely (getting tagged) before using SwC then you'll find you can avoid some of the disappearing tag issues.
Wrote this blog post describing the issue too.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
yeah .. I would agree with @ToanDN
Tag withing Linked file, and use " by linked view " in VG ..
Make sure both Views in main project, and View in the linked file is of same Scale, so
What you see is what you get...
Same thing you can do for Dimension etc, use live refernece lines and not connected with linked files
so that you dont miss anything even when file is unloaded, or changes...
. and if you are worried about coordination then
you can always link files for coordination..
Example
Site Plan Revit file - - - Link ( overlay ) - - - house / unit ( for reference / coordination )
house/unit fiel - - - linke ( overlay or attached ) - - - - in Site Plan Revit file..
Thank you for your answers,
Yes, all are good solutions. For construction plans we have a secondary view in the linked model in order to tag certain elements and that view is then used in the primary model to show the models.
To specify the project a little:
The site consists of multiple buildings. All the models have at least the surrounding buildings (including their structural and MEP models) as links (in their respective workset). Of course, the buildings are built in different phases so a loaded linked file may show absolutely nothing on the drawings since its content will be realized in a future phase.
The project in total is a way out of the typical scale and the amount of views is huge so we can't create a second/third/fourth view for each view requiring tags. There are also structural/MEP models which we cannot manipulate.
Even the architectural models have been divided in multiple models : interieur, exterieur, casework for example. For example, to be able to work effectively with the casework, it is necessary to have the interieur model open too. The interieur model takes already 20gb of memory when opened with all the worksets. The casework model takes maybe 10gb. That leaves very little to work with.
In this context, does the BIM managers logic hold? That is, to minimize tags being disassociated by keeping all worksets open. Once a computer has 0mb of free memory, it becomes very slow. I have once observed revit to shutdown 2 hours in this kind of situation.
Sounds like the Hardware is struggling to keep up with the Software.
Consider adding more RAM, if the projects are very large/memory intensive as you describe.
RAM is fairly inexpensive and will improve performance for your team.
Thank you for your answer. Yes, upgrading hardware is something to investigate. The problem in this approach is that first of all, our team is fairly large so any hardware upgrades would have to be done on a lot of computers.
Second problem with the hardware approach is that we are far from finishing the project and the numbers I have given are not for the biggest building. When the biggest building reaches the execution level detail, nobody can really know how much memory will be needed.
Roughly, the biggest building is maybe 4-5x the size of the buildings I have given numbers. Even that model is divided in several models, but as we are advised to open all the worksets any optimization in that sense is useless.
Our BIM managers advises us to dimension elements from the linked models and not to draw or model an architectural proxy for the element to be dimensioned.
Yes, we are having issues with disappearing dimesions also.
Tagging and adding dimensions to elements in a linked file is at risk every time you sync. It is not a reliable process no matter what your BIM Mgr says or that Autodesk's documentation says it is possible. Possible yes, good idea, no.
For persistent reliable documentation the By Linked View approach provides that. It does however mean you have to have some measure of control over those linked views. If you own those models too then you document specific views for using By Linked View and whenever you see those linked models you override the views it is visible in by assigning the Visibility/Graphics to use By Linked View, choosing the correct view.
Placeholder elements (families) are another way to deal with it, even though you say your BIM Mgr says no. The dimensions are not going to be lost if they are referencing a local element. Although poorly made content can cause Revit to delete dimensions when you swap families or types.
If you must reference linked elements with dimensions and tags - then reloading the linked files before using SwC will reduce the number of times those elements are orphaned or deleted. If you get a message about deleting dimensions, use Cancel and Reload the Link(s), then try again. Make a record of every time you do this or lose information and take it back to your BIM Mgr. Eventually they'll realize they need to reconsider their position, especially the more people that start doing that too. Nobody likes redoing things unnecessarily.
If you're dealing with a scope too large to print at the desired scale consider using Dependent Views. You create a parent view (overall plan) at the required scale and then use Duplicate as Dependent to create views that are the same as the parent but allow for individual cropping of the view. This way you can create a Part A, B, C, D etc. Any documentation you add to the Parent will appear in the Children (Dependent View). True in the reverse, any annotation you add to the Children will also be in the Parent too. Add annotation in the parent view and there is much less redundant work in the children.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
The problem with the hardware upgrades is that the BIM manager doesn't acknowledge his responsibility for determining what is the suitable hardware needed to work on the project. I for one, consider the lack of memory (= loss of time / slow downs related to it) as a red flag.
Thank you for your answer
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.