![]() In which case we simply open the change-schedule to get an overview of changed elements and annotation. All in all it's a pretty time-consuming procedure which could be eased if Revit keeps track of changes. Changes to annotation have to be done' manually'. But Navisworks only checks geometry - not annotations. Those clashes then have to be conveyed back into Revit to make model changes. The work-around we use now is to load the new and previous model in Navisworks and clash them to spot the differences. The structural engineer doesn't make a list of all changes to a structural model, so if we link that model in our model, we don't have a clue about those changes. Whats thing change over time in third party models? For example, the structural engineer decided to change beam sizes and as a result, they pop out under the ceiling. That's one scenario.Īnother scenario is evolving models. But in case of many changes, it's a tedious job. Now if it's about a couple of changes, then it's easy to eyeball. They send back the changed model and then we have to check if they actually made the changes. They have to link our model and make the necessary changes. Things that need to be changed are marked up in our model which we then send to the other parties. When we receive a MEP and Structural model, we have to check if it fits our architectural model. ![]() Hey all, can you guys elaborate a little on the workflow you'd like to carry out here?įor example, linked models. ![]() Revit converts it into a a transient object and keeps the hosted objects with it.Ģ) Based on user's choice you can remove the transient object from the model and along with it all the hosted objects.ģ) In an event it was an accident then the user shall have an option to convert the transient object back to valid object.Ĥ) Almost like "Reveal Hidden" Tool but for Deleted Items until it is purged as a choice.Īutodesk please see if this qualifies for a separate idea or falls under this same category of tracking changes. Here is the workflow that may work better.ġ) Someone deletes the Host objects. The design team didn't noticed it until very late and when it was discovered the quicker solution (for all kinds of reason) was to just recreate the ceiling and insert all the ceiling hosted elements back again. We recently encountered an issue where someone had accidentally deleted a Ceiling object and along with it all the ceiling hosted objects in it. I think the desire to keep track of deleted items in Revit falls under this category.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |