How to Change the Criterion for Duplicate Check in OpenPlant ModelServer


Applies To
Product(s):OpenPlant ModelServer & OpenPlant Modeler
Version(s):08.11.11.395 & 08.11.09.568
Environment:Windows 7/8 (64 bit)
Area:Configuration
Subarea:
Original Author:Harpreet Singh, Bentley Product Advantage Group

Background

By default, the criterion for duplicate check is based on NAME property of the pipeline. If a pipeline with the duplicate Name is being checked into server, you will be prompted to remove the duplicity. This article will explain, if you want to change this criterion to be based on NUMBER property so that pipelines with the same number can’t be checked into server, what changes you need to achieve this.

Steps to Accomplish

  1. Launch class editor.

  2. Load OpenPlant schema and supplement it with OpenPlant_Supplemental_Tagging schema.

  3. Go to PIPING_NETWORK_SYSTEM class.

  4. Change the property name in ‘BusinessKeySpecification’ custom attribute to NUMBER.



  5. Save the changes in the schema.

  6. Now load OpenPlant_3D schema in class editor from your project and supplement it with OpenPlant_3D_Supplemental_Modeling schema.

  7. Go to PIPING_NETWORK_SYSTEM class.



  8. Change the property name in ‘BusinessKeySpecification’ custom attribute from NAME to NUMBER.



  9. Right click on Pipeline node and select ‘Add/Remove’ option as highlighted below.



  10. Add ‘InstanceLabelSpecification’ custom attribute from the list and click the highlighted button.



  11. In the lower section, change the location of the schema to be OpenPlant_3D_Supplemental_Modeling.



  12. Type NAME in the property name field of the custom attribute.



  13. Save the changes in the schema and close class editor.

  14. To verify the result, create two pipelines with the same NUMBER as shown below.



  15. You will be prompted with Duplicate tags during the check in process.

Comments or Corrections?

Bentley's Product Advantage Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!