Bonus Point about the Organizer in ARCHICAD
Are you following Patrick May’s Tumblr blog yet? Great ArchiCAD advice over there too. He reminded me of another nice feature of the Publisher that I thought warranted a quick bonus post. You can open the View Map or Layout Book of another ArchiCAD file in the left hand side of the Organizer (you can also do this from the Navigator). This allows you to drag and drop views from File B into File A. The added views will be linked back to the original file. Layouts transferred this way will create new sheets with linked views, but the sheets themselves won’t be linked back to the original file. They’ll be native to the host. Head over to Patrick’s blog for a few more good thoughts on this.
Here’s the pretty diagram from the original post and video, updated to reflect the two file concept.
Did you enjoy this post? Follow Shoegnome on Facebook, Twitter, and Youtube for more…
Jim walls
Used this several times but it is underutilized with our workflows. Might be nice to create standard details in a file and use this method to borrow from the file in a host project file when needed.
Jared Banks
I’ve never done that myself, but I know of a lot of firms who swear by that method. Including many of my ArchiCAD Heroes. I believe Link Ellis has a video out there on that very process. And if Link approves then it’s the right method!
Patrick May
I have a dedicated pln file for “standard” 3d documents and details, as well as modeling custom fabricated parts and details. This keeps the project file clear of floating components or free of dedicated stories for custom model parts for these details.
I then link to the project file using the organizer (after creating 3d documents in the details.pln file).
Jared Banks
very cool. I love the idea of a standard details file. And then upping it with use of 3D documents… even better!
Paul Setti
This is a great idea. I am going to implement this solution as common details are so valuable. I’ve been wanting to convert my 2d details to 3d. I now can do this without worrying about starting fresh each project. Thank you.
Patrick may
This solution also helps keep layers clean. My detail file has layers for step by step details (skylight, window and door flashing and install). Layer- step 1, step 2… And 3d documents with each layer setting for the same model view
MarkV
Guys, this is a really great idea!! But how does this work if the source detail is changed? Does the linked one change automatically? If yes, can I keep that from happening? Older files need to stay “old” for proper archiving. If no (or I can decide), then this is awesome!
When the project is done, can those views be archived with the project or “bound” (to use an AutoCAD term)? Different from you guys, I start with my Detail file as my project template, then remove what I do not need. The current project has the current detail, but older projects reflect the information as it was at the time. Large projects that take a year or two to build cannot have their details automatically being updated because I (or the manufacturer) found a better way. If this is not a problem or that shared details dont automatically update upon open, then again this is awesome!
Another question: over the past 20 years, I have constantly updated my computer files and locations for better work-flow and document retrieval. One of the things that always bugged me about AutoCAD is that if you x-ref a file, the source MUST stay in its original location or you cannot open old projects (or current) and find the information. That is almost impossible since my organizing methods change and the operating systems change their organizational procedures too.
Jared Banks
Mark, you can make the links automatic or manual update. And you can embed/break the views’ links. Also (I’m a little rusty on this) you can place the details as PMKs instead of views. Then you can unlink the PMKs and edit them directly. I believe. It’s been a LONG LONG time since I’ve done that.
The short answer to everything though is: yes you can do all that. Keeping links in the right location can be annoying, but I also believe you can organize those with absolute or relative paths (this means the folders can move a bit on your hard drive). I’ll aim to do some research on that for a related post I’m writing right now. But even if the links get accidentally broken, they are very easy to relink.
The solutions are one of the reasons I’m such a fan of ArchiCAD. There are about 10 ways to do this linked Detail concept. And each has a different benefit and drawback. So it’s just a matter of finding the right mix for your projects.
MarkV
Wonderful. Thanks!
Douglas Fletcher
We’ve been doing this for the last several months on our BIM Server with mixed results. Occasionally, it can produce some unpleasant bugs, as in, another user opens the host file and not all detail drawings show up on sheets. Also, seems to be a higher propensity for crashes. Still trying to sort out the mechanics of it, but right now, our working theory is that it works great as solo projects, but the combination of source/host files on the BIM Server with multiple users creates problems.
Otherwise, in theory, this is the ideal way to handle details as the other ways of collecting details from previous projects have their own issues. Really wish Graphisoft would sort out an easy way of collecting details from various source files. Another add to the wish list.
Nando Mogollon
a bit late on the discussion, but anyway…
Its is a really good practice to keep typical details on what I call a “Warehouse File” just like Patrick. Then link views to any current project.
Then in order to keep building knowledge, we add new and variations of the details on the Warehouse File.
A plus is keeping all sort of good Complex profiles, Composites and examples in the warehouse file – in case you need to “go shopping” for objects and elements settings.
Just be aware of attribute pollution if the standards on the warehouse file and the project file are different. (i.e. working as third party for a teamwork file sitting in a different company)