Logical Modeler Description & Customization

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

This is summarized in the following UML schema:

Fig.1 Logical, Model

• Logical  domain gathers:

  • Logical System: Hierarchical assemblage of interconnected sub-systems. Systems can be re-used (instantiated).
  • Logical Connection : links ports of systems, i.e. the explicit exchange of data between systems.
  • Logical Port: Specifies the links between ports of systems. There are two kinds of logical ports: causal (In, Out and In/Out direction) and a-causal (no direction). 
  • System Type: Information associated to a logical port to specify the type of data going through that port.
  • Logical Communication (also called MUX (Multiplexer) and DEMUX (De-multiplexer)). When defining structured Types, it is necessary to provide constructor and destructor of such type. The logical MUX (Multiplexer) and DEMUX (De-multiplexer) are used for this purpose.
  • Logical Representation: enables to store private data such as picture, simulation data result, etc.

  In addition 3D definition can be added to Logical systems:

  • Logical 3D Representation: to associate 3D representation to a logical system to offer easy-to-use 3D modeling for system reservations, enabling system architects to validate the system architecture early on in the process.
  • Logical 3D Publication: Use for design purpose to expose 3D private data of the representation (e.g. Plan).

The Logical model is implemented with PLM Core Object as follows:

Fig.2 PLM Core Objects

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

RFLVPMLogicalReference , Implemented Business Logic

RFLVPMLogicalInstance , Implemented Business Logic

RFLVPMLogicalRepReference , Implemented Business Logic

RFLVPMLogicalRepInstance , Implemented Business Logic

RFLVPMLogicalPort , Implemented Business Logic

RFLVPMLogicalConnection , Implemented Business Logic

RFLVPMSystemTypeReference , Implemented Business Logic

RFLVPMSystemTypeInstance , Implemented Business Logic

RFLVPMLogicalCommunicationReference , Implemented Business Logic

RFLVPMLogicalCommunicationInstance , Implemented Business Logic

RFLVPMLogical3DRepReference , Implemented Business Logic

RFLVPMLogical3DRepInstance , Implemented Business Logic

RFLVPMLogicalPublication , Implemented Business Logic

When a PLM attribute is defined (inside modeler PLM package) some features like its editability 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 each customization of:

• RFLVPMLogicalReference

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

•  RFLVPMLogicalInstance

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

•  RFLVPMLogicalRepReference

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

•  RFLVPMLogicalRepInstance

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

•  RFLVPMLogicalPort

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure
FLConnectionCreationCheck	Checks validity when a connection is about to be established between two ports
FLTypeAssociationCheck	Checks validity when a Type is about to be associated to a port.

•  RFLVPMLogicalConnection

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

•  RFLVPMSystemTypeReference

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

• RFLVPMSystemTypeInstance

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

• RFLVPMLogicalCommunicationReference

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

• RFLVPMLogicalCommunicationInstance

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

• RFLVPMLogical3DRepReference

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

• RFLVPMLogical3DRepInstance

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure

• RFLVPMLogicalPublication

PLM Opening ID	Remarks
Business Logic Reference	Refer to openness provided by PLM infrastructure