Material Modeler Description & Customization

This section first presents the objects representing the Material modeler. Then it describes how this object model view has been translated towards PLM objects based on PLM Core Modeler objects. You will see the description of each PLM package defining these PLM objects.

Material modeler is composed of two main parts: objects used to define a material and its properties, and the object to model the fact that an entity of the modeler PRODUCT is 'made of' or 'covered by' a given material.

This is summarized in the following UML schema:

Fig.1 Material UML Model

• Material: is the main object of the modeler. It models a physical material entity. It is composed of Domains
• Domain: is an object that gathers attributes (and their value) defining the material. A domain represents the view of the material in a given application or for a given subpart of physics. For instance 'Drafting' domain contains the specific hatching pattern of the material used in drawings. A given domain belongs to a single material. Each domain of a material has a type that is stored in the V_discipline attribute. Depending on the type it is allowed or not to have multiple domains of a same type aggregated by a material. If it is allowed, one of the domain can be flagged as the 'default' one. Some applications use this flag to solve ambiguity when many domains of a given type are available.
• Selector: a selector exposes a subset of attributes from one or many domains. A given selector belongs to a single material. A selector and the domains it is pointing at are aggregated by the same material. When a domain gathers models of the material that are mutually exclusive, a selector can be created to expose some of these models that are complementary and consistent.

• Applied-Core-Material: is the object that models the fact that an entity of PRODUCT modeler is 'made of' a given material. An Applied-Core-Material has a unique link towards a material (that is to be subtyped as a Core Material). It has also another link towards a single 'materialized' entity named support. It is aggregated by a Product named context. The support is either the context itself, a Representation Instance aggregated by the context or its Representation Reference.
• Applied-Covering-Material: is the object that models the fact that a Product or a Product Instance is covered by a thin layer of a given material. It has a unique link towards a material (that is to be subtyped as Covering Material). It has another link towards a single support that is either the context or a Product Instance aggregated (directely or not) by the context.

Material modeler is described through 3 modeler PLM packages :

Applied-Core-Material and Applied-Covering-Material are implemented using the same class of CATMaterial PLM Package: CATMatConnection. It is the V_discipline attribute of CATMatConnection that is used to sub-type Applied-Core-Material and Applied-Covering-Material.

Fig.2 CATMaterial UML model

This section lists and describes the PLM Opening ID implemented by the following PLM classes of the XXX modeler.

• CATMatReference,
• ExternalClassName2, Implemented Business Logic

<Explanations:

• col1 : PLM Openings ID name: the ones of INFRA + the ones provided by this modeler
• col2 : Describe the behavior of the implementation >

<Explanations:

• col1: PLM Openings ID name: the ones of INFRA + the ones provided by this modeler
• col2: Describe the behavior of the implementation >

This part consist in to create a new package when the modeler PLM package must be customized.

When a PLM attribute is defined (inside modeler PLM package) some features like its editability criteria, mandatory /optional option, can be overwriten by UI mask. You can say this PLM attribute is not writable in Query context, this PLM attribute is mandatory in Create context, this user PLM attribute is not never visible and so one. A set of UI masks form a security mask file. We say security mask because it is associated with these files security information. For a people, and a given context can be associated a security mask.

For each customized Modeler PLM package, at least one UI mask file must be created (for the default security mask ), since it must contain the new PLM Attributes. When you use the tool to create a customization, a default UI mask file is provided taken into account the added PLM attributes. You can modify the default file to introduce your change .

If you want create a new security mask file, you should provide a UI mask for all the "AsIs" modeler PLM packages and for each customization of the "Customizable" modeler PLM package.

Rules to respect for a new UI mask creation

To create a UI mask you should respect the following rules :

• CATMaterialRef PLM Package
  • Attribute V_Group of CATMatReference class should remain editable in Create context and Visible in Read context.

You can yourself integrate your business logic for each customization of:

• CATMatReference

  PLM Opening ID	Remarks
  PLMImportExportAttributesValuation
  PLMIdentificationInitialization

• MaterialDomain

  PLM Opening ID	Remarks
  PLMImportExportAttributesValuation
  PLMIdentificationInitialization

<Each package name in the reference table is an external name, but the links refer to a file whose the name is build with the package's internal name >