iLogic configurator workflow for large assemblies

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
There's a lot of information out there on different methods (multibody solids, suppressing components using Level of Detail etc) I understand everyone's needs are different and there's no one correct method for all, but from what I'm about to describe, I'm wondering what peoples opinions are on how they would approach my model with iLogic?
I have created a fairly complex assembly, which consists of approx 350 unique assemblies/parts at one time and about 6 levels of sub-assemblies. I have hundreds of other alternative parts/assemblies that I swap in and out throughout the various assembly levels.
Top Level
The majority of configuration takes places in my top level where there are 6 main assemblies which are subject to replacement with an alternative (currently using Component.Replace to do this). There are approximately 3 alternative assemblies for each of the 6 mains.
Sub Assemblies
There's a fair bit of iLogic rules in sub-assemblies also, mainly using the following functions to delete, place and replace parts/assemblies:
Component.Replace
AddUsingiMates (API)
Parts
In parts I am mainly suppressing features and changing materials using:
Feature.IsActive
iProperties.Material
So I'm currently using the bottom-up method of modelling. The model is parametric and to achieve this I am manipulating parameters in a base part which are then derived into all the parts for use in their equations and iLogic rules. The parameters in the base part are driven by an iLogic rule in top level assembly with user parameters.
See attached video for a short example.
Thanks,
Craig