Hello Aitor,
From your post, it looks you have (almost) all possible ways under considerations already, so just adding fwe comments. I'm also curious what WC issue you mention, since you describe quite general case which 90% of the users will resolve with simplified representations.
1. Use top assembly Simprep
pros : existing views / existing structure etc.
cons : some WC issue (? extra downloads / checkouts ?)
2. Use ProPROCESS. It can be used even better than you say (create several PROCESS assemblies). You can just create ASSEMBLE STEP that will suit each configuration that you need, adding new components (by ADD) and removing unnecesary (DISASSEMBLE). SO you do not use SImpreps at all.
pros : single model / existing structure / no extra downloads .
cons : no templates (but with the above, you probably do not need too many PROCESS ASSEMBLIES)
3. Use External Simpreps. This is an exported "snapshot" of certain simplified representation. It will contain only relevant objects, but you will need to create as many External Simpreps (ESRs) as you need configurations.
pros : use existing structure / easy creation / can have template / smart WC management (only members get downloaded).
cons : multiple extra objects should be created (as many as you need BOM configurations)
usually ESRs are used for pure assembly concurrent design through PDM, but they definitely can serve your case as well.
Regards
- Vlad