Production system Modeler Description & Customization

This section first presents the objects representing the  ProductionSystem 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 Mfg System or Operation model is based on

• 4 types of Mfg System References aggregating other components:
  • Mfg System or Operation Instances.
  • Mfg System IO Ports.
  • Material path Connections.
  • Time constraint Connections.
• And 10 types of Operation References aggregating other components:
  • Mfg  Operation Instances.
  • Time constraint Connections.

This is summarized in the following UML schema:

• The Mfg System or Operation Reference are the components that can aggregate other components. A Mfg System or Operation Reference  can be instantiated. These resulting components are Mfg System or Operation instances.

• Manufacturing system

  • Is the entity producing the manufactured product

  • Contains operational specifications (operations) for the physical world

  • Has a number of inputs/outputs (Mfg system IO ports)

  • Types of systems : General, Storage, Tranfer, Transformation.

• Operation

  • Implements process functions

  • Has a duration

  • May be connected to others operations thru Time Constraints

  • Is implemented by one physical program of physical resource

  • Types of Operation : General, buffer, curve, loading, unloading, punctual, remove, sink, source, transfer.

Mfg System or Operation is implemented through one modeler PLM class package of the same name. The Product package, like any PLM package, consists in PLM Classes enriching the PLM Core Classes.

Mfg Systems or Operations specialize the PLM Core modeler by adding PLM attributes and semantics.

" XXX " may be replace by any types of systems or operations.

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

Mfg System or Operation must be customized.

When a PLM attribute is defined (inside modeler PLM package) some features like its editability criteria, mandatory /optonal 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

No specific rule to customize UI mask file.