Best approach for a configurator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Within our company we have been looking for the best workflow to go from design, to fabrication, to mounting on site. We make curtain walls, which mostly consist of mullions, transoms, glazing, panels, … Our biggest issue lies with the mullions and transoms because these are the most complex, the most varying and we actually fabricate these internally.
A mullion (or transom, but I’ll focus on the mullion) is basically a purchased profile, which is cut in the correct length (and sometimes angle) with a bunch of holes, cutouts, …
There are a bunch of things that have to be assembled onto this profile during our fabrication like gaskets, screws, plates, … I have made most of these things as content center parts because most are purchased and can vary in length.
At the moment I make one “master” assembly for a mullion and try to put in every known variable, which can then be configured by entering the parameters on an ilogic form and running some illogic rules (in the correct order, as some things are calculated during or after a specific rule ran).
Because we can have a couple hundred different mullions in a big project this means we now have to copy this master assembly (and the underlying profile part, which always has to be 1 to 1) lots of times. This is done manually at the moment, but probably could be done with illogic fairly easily.
If I have a variation that wasn’t included in my master assembly (or part) I can just add a feature manually after copying the master, or decide to change the master assembly from that point on. There is no link between existing copies and my original master assembly.
After the models are done I constrain them onto a grid I created (using a macro that will find the pre-created work features existing in both the grid and the master assembly) to rebuild our complete curtain wall. And then create a detailed fabrication drawing for every copy of my master assembly (again using a macro to put dimensions between pre-created work features existing in the master assembly).
This works, period. Are there things to improve about this? Most definitely!
Now, my colleague has a bit of a different view on this whole thing. He basically wants to enter all the data into excel, and start building assemblies based on that data. Notice I said building, because he wants to skip making a master assembly, and go straight to generating parts and placing them in a new empty assembly. I believe that in principle this would be possible, however I also believe that the code would be immensely complex and long for a non-programmer (IF we get it to work at all, that is).
In some sense I can see some benefits in this workflow, because if you’d have to change something to all the copies you already made, you could edit the excel, edit the code and rebuild the assemblies. And of course, not having to manually copy everything could save a little bit of time too (even though I’m very wary of this because it could overwrite existing files without you even noticing).
However, here are some issues that I suspect we will run into:
First, we are not programmers, so I think that this would be very hard to make this, and the chance to have issues in the code which will cause errors or issues further on seems very big to me.
Second, because we are not programmers I’m not convinced that writing or editing this code would be easier or faster than creating or editing a master file like I have done previously.
Third, I believe that when you’re just entering numbers into excel without any visual check the chance of making errors increases, and maybe this could even take longer than entering this data straight into Inventor.
Fourth, I think that if we want to create a somewhat detailed drawing we’ll either have to create dimensions manually or have some work features existing in our assembly to create dimensions programmatically. If these all also have to be created with code, this will further increase the complexity and the length of the code.
Fifth, to rebuild our complete curtain wall in an efficient way I also think we would need some work features to constrain everything.
One very important factor in this whole thing is that we NEVER know every single variation we will encounter before we start. We NEVER have ALL data gathered before we start.
To give an example to this, I’m currently working on a 13 floor building. The first 7 floors are already fabricated, 5 of which are already mounted on site, but I’m still waiting on information to make the remaining floors.
Also it could very well be that from 300 different mullions, only one has some specific hole or cutout, in some way I’m flexible at the moment because I can just change that one specific mullion without having an impact on all the others. I think that if you want to build everything from an excel, you would need to have some parameter or something in every single mullion which would make it so there’s no hole, except in the one exception where the parameter would make it so that there is a hole.
Now, I’m wondering what the best way forward would be. My initial idea, my colleagues idea, a mix of the two, something completely different, …?
If anyone could share their experiences, thoughts, ideas, … that could be very helpful!
Sorry for writing a book on this post, I hope my explanation is clear enough to understand my general points, if not, feel free to ask more questions.