P&ID - Working in Session Duplication mode

Purpose

How to setup the 3DEXperience CATIA Schematic application to be able to create P&ID that will contain single instance per component reference. This mode of creation is called Duplication mode because every objet placed from the catalog will be duplicated to be manage separetly and to be isolated from the catalog objects.

 

Context

When placing component from catalog you can select 2 modes of placement

  • Instantiate : same reference that is instantiated multiple times -> Reference object is multi instance

  • Duplicate : a new reference object is created  at each placement -> Reference object is single instance

 

The instantiation mode is the more efficient in term of performances but it has some limitation in term of data management and lifecycle

 

The standard duplication mode takes more time when placing component in P&ID because object and symbol is duplicated into the database at each placement. But it has some advantages in term of data management and lifecycle

  • This mode is typicaly used when you need to modify Componenent reference object (attributes/lifecycle) separetly for 2 components that are placed from the same reference object in catalog ; and also from the reference object stored into the catalog

  • This mode is recommended in the following case

  •  

    On Premise

    On Cloud

    Change reference attributes on the P&ID components (Equipment, valve, ...

    X

    X

    Need to add customer attributes on P&ID components

     

    X

    Manage Revision at level of the P&ID components (Equipment, …

    X

    X

    this mode can introduce too much latency at each component placement --> the following practice explain how to solve this issue

 

Solution : Session duplication mode solution

Statut (without using session duplication mode):

Placing component in duplication :

  • takes too much time
  • Creates too many unecessary objects in the database

Reason : the system is duplicate the component and the symbole into the database before placing them in the P&ID Sheet

 

Target 

Reduce time when placing component in duplication mode

Reduce number of unecessary object in the database

 

Proposal : 

Usage of Session Duplication mode

  • Separate the symbol Rep object from the component reference object placed in P&ID
  • Create the objects into the database only when saving the data

 

How to setup Schematic App to work with Session duplication mode

Step by step detailled video

 

Process Scheme

Manage Non standard symbols