Im mulling over a response to Matt Wheelers presentation at Mike Brightman’s 2024 sketchup conference about the power of DC’s.
He had a massive window/door library and someone said, “hey, what about using DC’s?”.
So I have a massive cabinet modeling library. Close to 400 pieces. I can see where I could reduce that library down to maybe 20 DC’s or less to cover all the options.
However, im also trying to solve an auto-text workflow. DC’s are great for managing data associated with a product which then can be used in Layout for faster application of leader notes and product tables.
What Im stuck on is what is the best approach. If I reduce down to just a few DC’s for all options will the DC also adjust name, dims and other types of data I need when I make a change?
Example: DC cabinet is a 30" wide frameless base cabinet with a single door and 3 shelves behind the door. Name: FRB_1DR_3SLF
Let’s say I want to make that cabinet 48" wide and turn it into a 3 door with drawers above the doors and one shelf behind the door.
Would the DC update the name of that cabinet? FRB_3DR_3DWR_1SLF
Could I have data fields like drawer, door handle, door hinge, drawer slide, shelf, door, drawer front, material, finish? Would the DC be able to update for each cabinet and allow me to use the data in LayOut?
Additional notes:
Im a Mac user and don’t use Excel but Apple Numbers
My current modeling library is built for speed. I don’t model cabinet interior parts. Object is a box, a door, a hardware proxy, shelf and door swing dashed lines. I leave cabinet interior details for detail models that are in an equally large scrapbook library. Drag and drop saves time.
I haven’t started this transition. Im hoping all the community here can help me upgrade my knowledge base and help me come up with a more complete outline.
I have built very basic DCs for windows / doors to be used in construction documents, and have some timber components. In the timber components I use ‘Concatenate’ and then list the fields I need in a custom text field. I imagine you could do similar, but you will be pulling in child components / sizes / etc.
I have not done this with my window components, but when I find time I will update them to show the overall size so on LO documents I can quickly show leaders to the windows and have the overall RO size called out. I generally wait until the CD phase for final selection of windows / doors (they usually change from what I want to what the client wants to spend $$ on…). - so I will include a table with the schedule with manufacturer model numbers and ROs.
I am interested to see where this thread goes. My experience with trying to leverage DCs for modelling hasn’t gone well, possibly because of my limited experience, but also a lack of trust in data not updating and components becoming unique when not expected. Perhaps they needed to become unique, but I felt like I was loosing control of my model. At least with static components you know what you have and if necessary it can be quicker to edit a component or replace it than wrestle with the contents of a DC.
This is just my personal view, I’m not suggesting DCs aren’t the right solution to your problem.
My entire workflow is based off DCs that do this. I build decks so forgive me if I am slow to reply, busy time of year. I get a takeoff from generate report where all the info is generated by custom DC attributes, generally with IF and Concatenate statements. Here is a very basic one, 2x cedar lumber. The custom reporting attributes are preceded with AA_ so they populate the top of the attributes list. These are all the same DC but the list name and quantity change based on the DC’s configuration.
Question: The “Stair with PVC Tread” title; can that change based on changes to certain parameters?
Also, as I said in my OP, Im not an excel user. Only use Apple Numbers. Is there any workaround for using the spreadsheet output in Layout so that it auto-updates if there are changes in the model?
I’m interested.. been on a bit of a DC binge over the last month , mainly low poly models of branded furniture and appliances for space planning and schematic design eg.. LG fridges and IKEA storage units where 1 model covers multiple variations.. but I haven’t considered their notation in Layout yet..
I think @endlessfix mentioned something about this before. Don’t remember if Apple breaks that or not. Seems like he was saying that Layout will break the formatting if you change the file, but can’t remember.
This is a beautiful thing. Im doing something very similar as far as building libraries for appliances and decorative plumbing fixtures. Would be very keen on hearing more about your efforts. LG and IKEA is good. Im mostly Subzero/Wolf but cover KitchenAid, Meile and a few others for custom units. Do a lot of Kohler and few custom brands for plumbing as well.
I think you have it right, that one model can cover multiple manufacturers and variations. Ultimately the placement is all about the render or the 2D elevation and needing all the specific detail for each model is really a waste.
How many different DC’s? How many variations covered in each? Do you build them for panel ready if needed?
Still curious about how titles work after selections have been made? What’s your solution?
Good memory, that was a while ago, I was just outlining the same dialogue that @bmike shows (available on first import or via right click on the table and choosing Excel Reference Options). If the import excel formatting box is ticked then any formatting you execute within layout will be overwritten with each fresh import, if it is not ticked then it won’t do that. The numbers-excel-layout workflow is a bit annoying to have the extra step, but it works.
by title I assume you mean the model selected… that can be isolated and displayed using CHOOSE function and displayed in the itemcode attribute o it appears in the OPTION tray and I assume also extracted by report generator.
you can download the model from 3DWH in the link given in my earlier posts.. and examine the DC coding.. I have not gone deep into creating reports as TRIMBLE has disabled that feature to perpetual license holders due to unexplained “security risks” . Also have not looked how these DC’s integrate with LAYOUT file notation capabilities although the DC attribute data should be accessible there..
My focus has been on creating value added low impact components that try to offer useful decision information to the designer such as accurate dimensions, space requirements, code compliance, MEP requirements, indicative pricing, colour options, manufacturers documentation links etc in an efficient format.
thanks @endlessfix
Glad the memory is good in this area. Glad Im getting clarity on this. A bit annoying is about par for the Mac Sketchup/Layout course. Can’t wait for the unifying release. Maybe Numbers will get a boost to be on par with Excel in utility.
