Configured Structures
Before creating Configured Structures in the Native Client, the Model information must first be created in the web client.
Once the Model is created, it can be applied to a physical product via "Configuration Context". Configuration Context is the 150% node(s) in the tree. Directly below the Configuration Context level is where effectivity can be applied, which is where the tree transitions from 150% to 100%. This is a very important concept which can have darastic impacts to business processes if not carefullly set up - especially if your information is connected to DELMIA. For support in the EBOM Configuration Management process, please reach out to True North PLM.
At a minimum, the products directly above an instance needing effectivity require Configuration Context. It can also be beneficial to continue going up the tree to apply configuraiton context to allow filtering at those levels.
Adding Configuration Context to a Physical Product
Applying Model Version and Variant Effectivity Manually
Authoring Context VS Work Under
There are 3 methods for applying effectivity to content in the Native Client.
1: Manually: apply effectivity to the instance(s) by hand
2: Authoring Context: apply effectivity to the session, and the session will apply to the instance(s)
3: Work Under: apply effectivity to the change action, and the change action will apply to the instance(s)
Depending on your business processes and BOM maturity, one or multiple of these methods may be useful. It is recommended to keep the number of people using these methods to a small population, as it can be confusing and it can also get "out of control" quickly if done incorrectly. These methods of course assume the effectivity of interest is already available via the web client Model Definition or Variant Management application.