topic Detail Library in Libraries & objects

Detail Library

Anonymous — Mon, 07 Oct 2013 00:01:05 GMT

Ok I am still new to ArchiCAD and with my new job, but the way they have been doing details isn't as efficient as I am sure it could be.

I am coming from Revit to ArchiCAD and there are a few features in Revit I really liked an wish to implement into my new job and ArchiCAD.

Its just I don't know if it is possible or how to do it.

Let me try to explain what I wish to accomplish:

What I would like to create is a Detail Library, where U save all your details on to a central file where you can then pick an choose the details you need for the project you are working on from a list rather then coping one by one. I would like it that I could select all the details I need an it imports them all to my job and on their own (as a Independent detail) with it retaining its own detail name that it was under in the Detail Library file. Just like a Hotlink BUT the detail can be amended to suit the project.

Is this possible in ArhiCAD?

Thank you in advance.

Re: Detail Library

Steve Jepson — Tue, 15 Oct 2013 22:22:06 GMT

A Template file might be something that would change your need for detail libraries.

Re: Detail Library

Anonymous — Sun, 17 Nov 2013 23:04:12 GMT

~Bump

I am still looking for a solution, things kinda got busy in the office, but still need a better way of doing details....rather then opening a template file with all details.

Then creating a independent view an pasting the detail there an naming the view. Can become quite troublesome if you have a lot of details to do this for.

How do other ppl do their details, would be very interested so see how you all do it.

Re: Detail Library

Arcadia — Mon, 18 Nov 2013 01:19:53 GMT

There are quite a few different ways that people do this. Personally I have sets of std details drawn in a grid pattern on several worksheets. I drop the whole worksheet onto my layout as many times as I need and re-size it to the appropriate grid square for the detail I want on the worksheet. Works fine for me. All these details are on the template already so when I create a new job I can delete the worksheets that contain certain detail classes (ie for construction types) that I know I wont need then I'm left with just one detail worksheet placed with multiple instances on the layout for as many std details as I need. If I want to customize a detail I just use the detail tool then copy and past into it from a base standard detail or I just amend the standard on my details worksheet.

Some like having details externally that are linked but this creates problems as if you update your external std it will update in your project as well which can cause inconsistencies especially if you need to customize something. Better to have all details within your project file.

I hope this helps. I'm sure you will come up with a system that works for you. Other's may think their own system is better than mine but that's the beauty of Archicad - you can skin cats in many different ways:)

Re: Detail Library

Anonymous — Mon, 18 Nov 2013 22:34:05 GMT

Ya we use something similar as to you currently, but a little messier lol i would say, we have a lot of extra pointless things we could cut out.

Anyone else care to shear how they do their detailing?

Re: Detail Library

Laszlo Nagy — Tue, 19 Nov 2013 07:48:13 GMT

Arcadia wrote:
Some like having details externally that are linked but this creates problems as if you update your external std it will update in your project as well which can cause inconsistencies especially if you need to customize something. Better to have all details within your project file.

I would be using this method if I needed to.
I think the concern you raised can be handled relatively easy:
Go to the Drawing Manager, select all those external source details and click the Break Link button.
Now all those Drawing will become embedded into the Project File and you don't have to worry about them changing.
If you now go to their settings Dialogs you will see that the Update Status field says "Embedded", and the Store Drawing in the Project File became checked if it was not checked before.

Re: Detail Library

Arcadia — Tue, 19 Nov 2013 07:55:42 GMT

That's a good tip Laszlonagy but you still wouldn't be able to customize the details on the fly as needed without first pasting them into the project. I'd rather keep everything in the template and delete/change what I need to.

Re: Detail Library

Laszlo Nagy — Tue, 19 Nov 2013 08:16:53 GMT

Yes, you are right, that method only works well if you need to place those Details without the need to make any modifications on them.

Re: Detail Library

Anonymous — Tue, 19 Nov 2013 14:10:19 GMT

I kept an extra instance of Archicad open that has all of my libraries, notes, and details. It's layer list is standardized for this office so I can copy and paste to and from my projects easily. When I go to do details or add any 2d work, I just copy and paste what I need over so my project files don't get choked up. And when I make something new in the project, I just copy and paste it back to the storage project so I can keep it for future use. Even if it just a couple of small changes, because then it becomes kind of a history that has its own benefits for little over head. I also use it as a viewer for my libraries so I don't have to have the project folders loaded up with unnecessary libraries. Still have to load the parts into the project though.

I'm similar to Arcadia's system is I have worksheets filled with clusters of details. then I just copy what I need over so all the details are just on one worksheet in the project. Then I place as many views as I need off that one worksheet to the layouts. This prevents that sequential updating of views to all views based off that worksheet update at the same time.

I tried hot-linking but again, like Arcadia, that prevents me from being able to customize on the fly so I don't. Instead I copy and paste everything.

Oh, and I thought I should add that there is teamwork in Archicad, unlike Revit. So that storage file that I'm talking about you can share that project on teamwork and everyone can join that project and copy and paste to it, updating as needed so everyone gets the benefit of continuously updating details.

Re: Detail Library

Richard Morrison — Tue, 19 Nov 2013 16:21:13 GMT

I think it depends on the size of projects you are doing. Since I'm doing relatively small residential work, I copy my standard details file to the project folder, so the "Details" PLN lives together in the same folder with the "Model" PLN. With this copy and the project PLN file open concurrently, you can use the Organizer in the Project File to just "drag & drop" details (views) onto the project file layout. Thus, you will have the Layout Sheets for the Model in one column, while the Views for the Details will be in the other column. (Hence, drag & drop) When you need to edit a detail, you will right-click on the view in the Layout, and choose "Open Source View" which open the detail for editing in the OTHER file. Then when you save after editing, you update in the Model file. Very fast.

If the editing is so extensive that you want to keep it for other projects, you can add it as a Detail in the Office Standard Detail file that will be copied for future projects.

If you are doing larger projects, Link Ellis has some good videos on how his firm does this. http://www.screenr.com/user/linkellis

Re: Detail Library

Link — Tue, 19 Nov 2013 20:53:11 GMT

Detail cataloging can be made very simple with a good template set up.

What I have shown below is the end result of that. The first tutorial is about setting up a separate detail project and publishing a PDF for users to browse through as a reference, as well as corresponding module files. These modules can be dragged and dropped into any project. From there there can be edited seperately to suit the project without affecting the original. Alternatively you could create a new detail in the detail project to keep for future projects, and republish the catalog and module files:

http://www.screenr.com/z1y

The next tutorial shows how you can easily look up the catalog and find the respective module of the detail you need. You can simply drag and drop it into your project.

http://www.screenr.com/91y

I have just taken it a step further by having pre-linked views and layouts set up to further expedite the documentation process. You don't need to go to that level just yet as it does take a lot of consideration especially when it comes to attribute management.

I hope these help you. I am currently in Auckland. If you need any assistance in-person or remotely just PM me.

Cheers,
Link.

Re: Detail Library

Anonymous — Tue, 19 Nov 2013 21:01:54 GMT

Wow, Thank you guys this really helps give me ideas how to possible set up our new way to do our libraries.

Also Link, those tutorials look good, will watch them some time today, and if have any questions will definitely look you up

In all honesty I liked the way Revit did external details an was kinda hoping ArchiCAD had something similar but these methods works as well.

Once again thank you for your help, I will post any hurdles I come across in my endeavour to set up our detail library

Re: Detail Library

Link — Tue, 19 Nov 2013 21:07:02 GMT

Sure thing. Hopefully you can see that ArchiCAD can do things as well (or dare I say better?! ) than Revit if you are able to let go of the Revit methodology and try ArchiCAD processes with optimism.

Work as a team and do things ArchiCAD's way.

Cheers,
Link.

Re: Detail Library

Arcadia — Tue, 19 Nov 2013 22:36:34 GMT

Sounds like zeropointreference and myself are doing much the same thing except he is storing his details externally and I have them in the project file. I just want to add something else about my method. As I said I have my std details arranged in a grid pattern on worksheets (different work sheets for different details classes) in a logical organized fashion of rows of various types of details etc. I have kept the same system from the start and when new details are added they go at the end of the row. I never swap a detail out for a different one in the grid just update it. What this means is that when I have to update an old project for re-use (ie if a builder I work for has a series of std models they use which I convert into jobs as they sell them) to update the details I just delete the the details and past in the latest versions of them from my template. This means I don't have to do any work on my layouts as the details are all in the same spots on my worksheet. I hope that made sense:) Just pays to think about future use when setting up an organized system.

Re: Detail Library

Anonymous — Wed, 20 Nov 2013 02:05:08 GMT

Thats a good point, will keep that in mind, also I do like the idea of having the std details on the job template file, so its always there, an only need to update the template when a new detail needs to come in.

But do you do with unique details? Do you add them to the template too or just leave them in the job they were created in? as who knows when u might need them.

Re: Detail Library

Arcadia — Wed, 20 Nov 2013 02:31:10 GMT

Yes unique details do come up and I sometimes copy them into the template if I think I may need them in future. Most unique details are just done referenced to a section somewhere and left in the project as they are unlikely to be re-used.

Re: Detail Library

Anonymous — Mon, 25 Nov 2013 23:41:07 GMT

laszlonagy wrote:
Arcadia wrote:
Some like having details externally that are linked but this creates problems as if you update your external std it will update in your project as well which can cause inconsistencies especially if you need to customize something. Better to have all details within your project file.
I would be using this method if I needed to.
I think the concern you raised can be handled relatively easy:
Go to the Drawing Manager, select all those external source details and click the Break Link button.
Now all those Drawing will become embedded into the Project File and you don't have to worry about them changing.
If you now go to their settings Dialogs you will see that the Update Status field says "Embedded", and the Store Drawing in the Project File became checked if it was not checked before.

Those files you have embedded, what happens if you decide to update it, what would you do? an how would you do it?

Re: Detail Library

Laszlo Nagy — Wed, 27 Nov 2013 11:35:21 GMT

Maysum wrote:
laszlonagy wrote:
Arcadia wrote:
Some like having details externally that are linked but this creates problems as if you update your external std it will update in your project as well which can cause inconsistencies especially if you need to customize something. Better to have all details within your project file.
I would be using this method if I needed to.
I think the concern you raised can be handled relatively easy:
Go to the Drawing Manager, select all those external source details and click the Break Link button.
Now all those Drawing will become embedded into the Project File and you don't have to worry about them changing.
If you now go to their settings Dialogs you will see that the Update Status field says "Embedded", and the Store Drawing in the Project File became checked if it was not checked before.

Those files you have embedded, what happens if you decide to update it, what would you do? an how would you do it?

In the Drawing Manager you can always select any Drawing in the list and use the Link Drawing to button to re-link it to any internal view or external source.