Simulation Modeler Description & Customization

This section first presents the objects representing the Simulation 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 simulation modeler is composed of two main parts: objects used to define a simulation, its categories and its contents, and a connection to the simulated model.

This is summarized in the following UML schema:

Fig.1 Simulation UML Model

• Simulation Object: is the root of the simulation. It aggregates 3 categories : Model, Scenario and Result.
• Category: is an object that allows to classify data into 3 categories : Model, Scenario and Result. This object can not be customizable. Into each category different types of PLM object can be classified.
  • Under Model category, several External documents and one System connection can be aggregated.
  • Under Scenario category, several External documents, one Scenario Representation can be agrregated.
  • Under Result category, several External documents, one Result representation, several non V5 representation and seveal Published result can be aggregated.

Simulation modeler is described through four modeler PLM packages :

• SIMObjSimulationGeneric
• SIMObjSimulationCategoryAndProdCnx
• SIMObjSimulationV5Generic
• SIMObjSimulationPublishedResultCnx

SIMObjSimulationGeneric

All simulations are implemented using the SIMObjSimulationObjectGeneric class of SIMObjSimulationGeneric PLM Package. It is the V_discipline attribute of this PLM class that is used to sub-type the simulation. Currently the existing discipline values are : .

• Kinematics
• GenerativeStress
• DesignSight
• ManufacturingSimulation
• LogicalSimulation
• ProductionSystem
• CAASimulationSample.

Non V5 representation is implemented using the SIMObjSimulationRepReferenceGeneric  and SIMObjSimulationRepInstanceGeneric  classes of the PLM package SIMObjSimulationGeneric. they can contain for instance results of the computations of the solver.

Fig.2 SIMObjSimulationGeneric  UML model

V5 rep representation is implemented using the SIMObjSimulationV5RepReferenceGeneric and  SIMObjSimulationV5RepInstanceGeneric classes of the PLMPackage SIMObjSimulationV5Generic. It contains all the features needed for the simulation : excitations, probes, scenarios, results, sub-results ...

Fig.4 Package SIMObjSimulationV5Generic UML model

V5 rep representation is implemented using the SIMObjectSimulationPublishedResultCnx class of the PLMPackage SIMObjSimulationPublishedResultCnx. It is used to connect fetaures results with non V5 or V5 representation.

Fig.5 Package SIMObjSimulationPublishedResultCnx UML model

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

• PLMImportExportAttributesValuation,  this business logic is used for File Base Design Import.
• PLMIdentificationInitialization,  this business logic is used for PLM New.

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

• SIMObjSimulationGeneric, contains at least one "ToBeCustomized" PLM class, it have to be customized to be used.
• SIMObjSimulationCategoryAndProdCnx, only contains instantiable PLM classes, no customization can be done.
• SIMObjSimulationV5Generic, only contains instantiable PLM classes, no customization can be done.
• SIMObjSimulationPublishedResultCnx, only contains instantiable PLM classes, no customization can be done.

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 sec urity 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 :

• No particular rules.

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

• SIMObjSimulationObjectGeneric

PLM Opening ID	Remarks
PLMImportExportAttributesValuation
PLMIdentificationInitialization

 

• SIMObjSimulationRepReferenceGeneric

PLM Opening ID	Remarks
ManageNavRep
PLMIdentificationInitialization
ManageNavRep

• SIMObjSimulationV5RepReferenceGeneric

PLM Opening ID	Remarks
PLMIdentificationInitialization