Component Family Modeler Description & Customization |
| Technical Article |
|
This article presents the Component Family modeler. |
This section first presents the objects representing the Component Family modeler. Then it describes how this object model view has been translated towards PLM objects based on PLM Core Modeler objects.
The component family modeler is not customizable itself but is dependant from the product modeler that has to be customized. Two business logics are used in Component Family to adapt to product modeler customization. We also detail here some conditions that have to be fulfilled so that Component Family modeler works well.
The Component Family modeler is a component generator (parts, assemblies). It uses a generic model definition (from Product modeler) with a table of values that contains its parametric variability.
Each row of this table defines an element of the family. This element will be a clone of the generic model, with different parameters values and without the design table feature.
All family elements generation are done under the identity of the family owner (through a PLM Batch). This ensures and easy management of needed rights, and also ensures that all the generated models belong to family owner.
The component family modeler enables “on-demand” generation of family elements models: family elements can be classified in catalog chapter before they are generated. When a user asks for the instantiation of such an element, this element is generated if it is not yet.
Because of the “on-demand” generation, the Component Family modeler needs to ensure that the generic model is not modified between two models generation (so that all family element models are built using the same generic model). This is realized through maturity rules: the generic model components must all be at a maturity state defined in the business logic. A command available in the Component Family editor eases the maturity change of those components. It uses the list of transitions declared in the above business logic to change the maturity of generic model components. This only works if the connected user has the necessary rights to apply all the transitions provided in the business logic.
The family elements generated models are created by a cloning operation of the generic model. This operation is done on the server side and it needs that clone requests contain the definition of the new identifier set of cloned components. Another business logic has been provided to perform this task.
To find out more about the associated Business Logics, see the How to Implement the Component Family Maturity Business Logic? and the How to Implement the Component Family Naming Business Logic? topics.
The family owner needs the following rights to perform following actions:
No customization is possible
| Version: 1 [July 2010] | Document created |