I am looking to determine a best-practice structure for projects with multiple project files. I currently have a single-site, multi-phase, multi-building, multi-unit within buildings project. I am trying to determine the best method to stay organized. Below is a diagram outlining my thoughts on how to structure it. I am open to suggestions and improvements. It is complicated project, so I would like to establish a workflow for my team. This diagram doesn’t account for consultants (that is a whole other level of complexity).
Do you treat each building as its own project and mash them together at the end in PDF form? Do you issue 3-4 different sets of documents that reference the other document sets, that as a whole constitute the Construction Documents?
Also looking for suggestions on managing details that are the same between different project files (buildings and units). We have worked with a shared details file in the past. It works, but is complex.
My brain hurts. ![]()
*edited to revise diagram and show Unit PDFs
Well, the first thing that caught my eye is that "Overall Site Project" doesn't interact with anything. That seems odd to me.
My thought is to isolate that as much as possible and only show building pads. Could be a flawed theory. In reality the Building models will be linked in, but chiefly for reference only.
if you retitle your thread "Multi-File Organization Best Practices and Free Porn", it might get more activity.
Rethought the workflow and looked at another option. This option links all sub-models into a big, single project model, and from that model flows the PDFs and Construction Documents.
I could, but I don’t want to risk getting banned from the forum. I need you guys too much.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.