Has anyone any experience on how to handle CO's at CA stage?
Design Options doesn't really work at this stage since there would be 100's of elements (or more) that would need to be added to the option.
I am thinking of using a combination of phasing and worksets.
If a Change Order is valid the you simply archive the model to a different file and revise the current file to reflect the changes.
Yes I thought that initially, but what if the decision takes a long time and you want to continue working on the model.
@Kev_D wrote:Yes I thought that initially, but what if the decision takes a long time and you want to continue working on the model.
Sounds odd when you say "continue working on the model". You're in construction. What kind of COs are you talking about?
..let me clarify: "CA" mean Construction Administration to me. COs at CA, mean change orders during time of construction.
Sorry, I will track back a little. I was in a rush leaving work typing the last reply.
I am in architecture and we are making changes to the model in Contract Admin. The client wants to see different options for certain areas. Design Options is too cumbersome at this stage since we would need to add so much to each option. We want to show proposed changes from the different options that the client wants to see, while also continuing to make other actual changes. We would like to just remove the option that they do not want. Again, Design Options would be ideal, but would involve too much work.
We are looking at a phasing option along with a workset that can handle the proposed changes. So... when one is approved the other can be demolished or something like that.
We don't want to keep archiving models at every change.
So, after more thought and trial and error, I think I finally have the question I want to ask (Stick with me here).
Example:
Question..... How do I revert back to model as was prior to CO #1, while still keeping Co #2 & CO #3?
I can see an answer coming here for the above problem....
Archive the model after CO#1, continue with the existing model and input CO#2 & CO#3, then when CO#1 is scrapped the you just delete the archived model.
On the other hand, what if CO#1 gets approved, you will then have to open the archived model and input those changes to the new existing model.
This is what I call.. 'Double Jobbing!'
Do I make sense here? Imagine this scenario in a much more complex project with multiple changes in different areas of the building within each CO. And then having 100 CO's.
I have done a lot of research trying to find a good explanation/process of how to deal with Construction Admin in Revit. Very little info out there, but surely this happens. Project Managers in my office sometimes make the change and hope for the best, or create a sketch and pdf it and undo everything, wait for approval and then input the changes to the model (if it is approved). This is not efficient.
Depends on what sort of changes they are that drive the solutions. And solutions can varies from detail lines over copies of current views, to building the changes in a different phase, to building the changes in a design option, to creating an entire copy of the project file and revise it. It's really a case by case basis.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.