How to Change the Default Line Jumper in OpenPlant PID CONNECT Edition



Applies To 
Product(s):OpenPlant PID CONNECT Edition
Version(s):

10.07.00.32 Update 7 & Onwards

Environment: Windows 8.1/10 (64-bit)
Area: Customization
Subarea: User Interface
Original Author:Ashutosh Patil,Bentley Product Advantage Group

Background:

In OpenPlant PID, By default when two lines cross a gap is created. In this process you will modify the schema so that the jumper as shown in rectangular box used when two lines cross is an arc instead of the standard gap

Steps to Accomplish

  1. Launch Bentley Class Editor CE directly through desktop icon .



  2. Bentley Class Editor can also be launched through OpenPlant Project Administrator CE.
    In OpenPlant Project Administrator, Click on OpenPlant PID application for the required project in WorkSpace and click on Tools.
    After clicking on OpenPlant PID, in Tools → Class Editor icon gets enabled as shown in image below.



  3. Considering OpenPlant_ Metric : Open the OpenPlant_PID.01.08.ecshema.xml & supplement it with OpenPlant_PID_Supplemental_Design.01.08.ecshema.xml through below default std path.
     (OpenPlant_PID.01.08.ecshema: Std Path(C:\ProgramData\Bentley\OpenPlant CONNECT Edition\Configuration\Workspaces\WorkSpace\WorkSets\OpenPlantMetric\Standards\OpenPlant\Schemas)  

  4. In Piperun go to Jumper Mapping custom attribute.
    Presently it is inherited from BASE_PIPE_RUN from pid.01.08 schemas as highlighted below. So Class Name is Faded or greyed out.



  5. Right Click on Class Piperun → Cutsom Attributes→ Add/Remove.
    In Applied Custom Attributes → Change the location of Jumper Mapping custom attribute from OpenPlant_PID.01.08 to OpenPlant_PID_Supplemental_Design.01.08 such that the changes in schemas would saved at project level itsel.
    Hit on Ok.



  6. In Piping Network Segment Class or Piperun now the Jumper Mapping custom attribute can be edited easily. 
    Type in  Class Name type - ARC_JUMPER and Priority -1 as shown below.



    Different Pipeline Classes use the JUMPER_MAPPING custom Attribute too. .
    Hence MAJOR_PIPELINE, EXISTING_MAJOR_PIPELINE, MINOR_PIPELINE, STEAM_PIPELINE by default is set to use standard PID_JUMPER .

    - If changes are not reflected while placing Major, Minor, Steam Pipelines, then go to same schema and select on each of those classes
    - Change PID_JUMPER to ARC_JUMPER on each class jumper Mapping custom attribute same like for PIPING_NETWORK_SEGMENT and save the changes

    For Major Pipeline
     

    For Minor Pipeline



    For Steam Pipeline



    Save the changes made in all Pipeline and start the OPPID CE.

    Class Name is the name of the jumper to use over this class. Priority is specific to pipeline/pipe runs jumping.  So

    -  If 2 different pipeline classes, the class with the larger Priority number jumps the smaller Order.

    -  If they have same priority, then the config var is used.

    -  If same pipeline classes, then the config var is used.  Currently this is in pid.cfg

    # Run breaking hierarchy, when intersecting runs have same class# 1 means horizontal segment will not break # 0 means vertical segment will not break

    SCHEMATICS_JUMPER_SAME_CLASS_HORIZONTAL_PRIORITY = 1

    Using the example above:

    • If a Major Pipeline (1) crosses a Minor Pipeline (2), the Minor would have the Pid Jumper in it.
    • If a Minor Pipeline (2) crosses a Tracing Pipeline (7), the Tracing would have the Pid Jumper in it.

    1. Launch OpenPlant PID CE.



    2. Place a New Major Pipeline on same placed Major pipelines.
      As it can be observed  that Arc is getting placed instead of gap as shown in arrow. But the same need to be placed for existing Pipeline as shown in red box in image below.



    3. To bring the ARC_JUMPER into an existing pipeline, hit enter such that keyin dialog box would be enabled. Select the Existing Pipeline on which Jumper need to be reflected and type in Keyin
       
      Keyin -, “pid piperun jumpcomponents & hit Enter.



    4. After hitting enter automatically on existing Pipeline the Arc Jumper gets reflected easily.



      Thus changing Jumper from Gap to Arc based user requirement.
       

    See Also

    communities.bentley.com/.../how-to-set-show-flow-arrows-to-true-in-default-way-in-openplant-pid-connect-edition

    Still a Problem?

    If above problem still persists, then please create a Service Request and contact the Bentley Product Advantage group.  Please include a list of all relevant details to get in depth analysis for a solution or workaround