Since we have been having issues lately with workshared models crashing, running slow, and displaying very un-model behavior, it has been decreed by the Powers That Be that I conduct a Lunch and Learn session to educate my errant team mates and bring them back to the path of Revit Righteousness.
I am sure that all of you would have experienced what I have just described. Can you list some best practices that have worked for you?
Gelöst! Gehe zur Lösung
Gelöst von alan.quinn. Gehe zur Lösung
Gelöst von ToanDN. Gehe zur Lösung
I think that will be the title of my presentation that day (snicker)
What specific model grandeur would you caution against?
Just following up on ToanDN response. My line is "Just because you can model flashing does not mean you should". Having said that all models and projects are not created equally. A $250,000 bathroom model can be as complex as a forty story hotel but the file sizes will be different. However, I will want to see nail heads in the bathroom as I want to make sure the guy or gal with the hammer is placing that nail exactly where I want it, but I will not want to see door handles in the hotel.
Rule of thumb on larger Revit projects is model the big stuff and call out the little stuff in requirements. The old line "The devil is in the details" is a good one to keep in mind when working in Revit.
Here's a list of things to keep your Revit models running smoothly.
1. Save locally all the time.
2. Save to central at least once per hour.
3. Close Revit when not in use.
4. Cut a new local if you were out of the projects for more than a few hours.
5. Run Audit, Purge, check Warnings once per week.
6. Save-as a new central once per week.
Hope this helps and let me know if you have any additional questions or comments.
Thanks Alan! Always helps when things are confirmed in black and white - LOL!
Warnings is a big one... don't ignore them. I have stopped a model from being worked on until the errors were fixed because there were so many of them. I made the project designers do it of course, as I wasn't familiar with the project status...else I would have deleted all the bad stuff ![]()
Groups are helpful...but make sure they are used for model elements and not just for detail items...that is why we have detail items. Lots of groups in a model causes chaos later.
DWG's are for coordination...not for design. If they are linked in all over the place (or inserted...shudder) then that can mess stuff up.
Families that utilize DWG's....learn to build families in Revit and not use DWG's.
Have lots of unused 3D views? Purge em!
That's a few...there are more...but Warnings is the most important...
Oh...always start with a fresh Local file...never reuse a local. If you reuse a local it causes the central model to pause and update that local to wherever it needs to be to update to current status. If it has been a while, everyone is going to have to wait.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.