ems.webmail967704
2012-09-17, 05:49 PM
We have an ongoing project that entails multiple renovations of an existing office building. Each renovation is it's own project. After doing some research in various forums, we had implemented a process where all geometry that is unique to each project is contained in the Revit file for that project, and files from other projects are linked in.
The issue that has arisen, however, is that some projects include modifications to work performed in a previous renovation. For instance, renovations from Phase 3 are due to be completed in late 2013 and will remain in place for a year, and then parts of Phase 3 will be demolished and a new elevator will be installed. Further complicating this is that we need to document the new elevator work before the work in Phase 3 is completed, and there is the possibility that ASI's will be issued and the as-built conditions will be different from what is in the Phase 3 model when we begin documenting the new elevator.
Some of the solutions that we have come up with are adding a future phase to Phase 3 and doing demo for the elevator in that project, but we have not found that doing demo in one file and new construction in another file is an efficient or intuitive way of working, especially where demo for a new project encompasses geometry from more than one previous project. Doing a save-as for Phase 3 is an option, but means that we will have to coordinate any changes in the Phase 3 model with the model for the new elevator project. This happens a number of times, and having to do all the coordination manually across multiple files, with multiple people working on different projects, is somewhat of a nightmare and not very BIM-ish at all.
This wouldn't be nearly as big of a problem if it was all part of one Revit file, but doing multiple projects in one file has it's own set of issues, like control of visibility of callouts, datums, etc., as well as the file performance of a file with so many views and sheets, as well as having to append our sheet numbering system to deal with having multiple sheet sets.
Our next step was to try to do the whole thing within one Revit file, but then link in the model to separate revit files and create views and annotations of the linked model for documentation, but I don't know if this is the best solution?
I was hoping that someone out there has a suggestion for how to deal with this situation? Any assistance is sorely needed and deeply appreciated.
Thanks.
The issue that has arisen, however, is that some projects include modifications to work performed in a previous renovation. For instance, renovations from Phase 3 are due to be completed in late 2013 and will remain in place for a year, and then parts of Phase 3 will be demolished and a new elevator will be installed. Further complicating this is that we need to document the new elevator work before the work in Phase 3 is completed, and there is the possibility that ASI's will be issued and the as-built conditions will be different from what is in the Phase 3 model when we begin documenting the new elevator.
Some of the solutions that we have come up with are adding a future phase to Phase 3 and doing demo for the elevator in that project, but we have not found that doing demo in one file and new construction in another file is an efficient or intuitive way of working, especially where demo for a new project encompasses geometry from more than one previous project. Doing a save-as for Phase 3 is an option, but means that we will have to coordinate any changes in the Phase 3 model with the model for the new elevator project. This happens a number of times, and having to do all the coordination manually across multiple files, with multiple people working on different projects, is somewhat of a nightmare and not very BIM-ish at all.
This wouldn't be nearly as big of a problem if it was all part of one Revit file, but doing multiple projects in one file has it's own set of issues, like control of visibility of callouts, datums, etc., as well as the file performance of a file with so many views and sheets, as well as having to append our sheet numbering system to deal with having multiple sheet sets.
Our next step was to try to do the whole thing within one Revit file, but then link in the model to separate revit files and create views and annotations of the linked model for documentation, but I don't know if this is the best solution?
I was hoping that someone out there has a suggestion for how to deal with this situation? Any assistance is sorely needed and deeply appreciated.
Thanks.