Functional Process Modeler Description & Customization

This section first presents the objects representing the Functional Process 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.

The Functional Process model specifies the product transformations to realize the manufactured product. The transformation can be ordered through relation between transformations either Data Requirement (i.e. Data driven) or Precedence (i.e. Time driven).

Within PPR domains, the Functional Process domain enables to define the way to assemble the product specified in Physical domain. To enable the traceability the functional process implements (i.e. Satisfy) components of the product assembly.

This is summarized in the following UML schema:

Fig.1 Functional Process, Model

• Functional process domain gathers:

  • Structure entities:
    • Process Function Reference: defines the function to realize.
    • Process Function Instance: use of a Function Reference in the context of another Reference. 
    • Precedence port: specifies the precedence interface of a Function. The direction of a port can be In or Out.
    • Data requirement port: specifies the data interface of a Function. Data can be either requested or provided by the Function depending on the direction of the connected port In or Out.
    • Process Function Representation Reference: enables to store private data such as picture, simulation data result, etc.
    • Process Function Representation Instance: use of a Function Representation Reference in a given context
  • Intra domain relationship:
    • Required signal: links Precedence ports of sibling Functions. Specifies the workflow of functions : a Function can start as soon as all port Out of connected Functions are validated.
    • Required data: links data requirement ports of sibling Functions. Specifies the workflow of data between Functions.
    • Data requirement exposition connection: specifies the data either requested or provided by a Function of an upper or lower level.
    • Data requirement materialization connection: specifies explicitly the data provided by a port. it may be a specification for the Function or a result of the Function.
  • Inter domains relationship:
    • Implement Reference and Instances: relationship between Functional Process domain and Physical domain. The relation is oriented FROM source TO target: the source is sensitive to target changes. Such relationship allows bidirectional (Forward & Backward) traceability since the target is a requirement for the source.

The Functional Process model is implemented with PLM Core Object as follows:

The following array shows the links between the conceptual and PLM Core objects:

This section lists the PLM Opening ID integrated at modeler level for the following PLM classes of the Functional Process modeler and the associated default implementation if any.

DELFmiFunctionInstance, Implemented Business Logic

DELFmiFunctionRepresentationReference, Implemented Business Logic

DELFmiFunctionRepresentationInstance, Implemented Business Logic

This part consists on creating 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 editable criteria, mandatory/optional option, can be overwritten 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.

Rules to respect for a new UI mask creation

No specific rule to customize UI mask file.

You can yourself integrate your business logic for any  PLM classes of the Functional Process modeler by associating a script to each PLM Opening ID.

By default, some rules are delivered for following entities customized in VPM environment delivered as sample.

DELFmiProcessReferenceSample, Implemented Business Logic

DELFmiFunctionRepresentationReferenceSample, Implemented Business Logic