
Applies To | |
Product(s): | OpenPlant PID CONNECT Edition Update 8 |
Version(s): |
10.08.00.51
|
Environment: | Windows 10 (64-bit) |
Area: | Schema Customization |
Subarea: | Jumper Gap |
Original Author: | Deepak Singh, Bentley Product Advantage Group |
In OpenPlant PID CONNECT Edition, requirement is to control jumper gaps for instrument lines and process lines.
Background
In OpenPlant PID CONNECT Edition, jumper gap gets created when any process or instrument line crosses each other. The jumper of instrument line crossing over process line creates a larger gap, refer image below.

In this wiki article, we will explore on customization that will control the jumper gap distance for instrument lines w.r.t process lines.
Steps to Accomplish
- Using Bentley Class Editor, load OpenPlant PID schema of desired workset.
- Supplement with OpenPlant_PID_Supplemental_Design schema, refer image as shown below.

- Navigate to SPACING_DEFAULT class, notice the Double List applied custom attribute. Refer image as shown below.

- Items value defined in above custom attribute control the jumper gap between process and instrument line. Change the value & define a lower value to control (reduce) the gap. Refer image as shown below.

- Similarly, navigate to SPACING_PIPE_RUN class. Notice the Double List applied custom attribute. Refer image as shown below.

- Items value defined in above custom attribute control the jumper gap between process lines. Change the value & define a higher value to control (increase) the gap. Refer image as shown below.

- Save all the schema changes & verify the result in OpenPlant PID. In our result, now jumper gap between process line should be larger whereas jumper gap between process & instrument line should be smaller. To verify the result, we will route new lines near to already routed process & instrument lines.

- For already routed process & instrument line, if we want to control the jumper gaps as per schema customization then we need to evoke “pid piperun jumpcomponents” key-in.
Note: Please ensure that you are running the key-in on a backup model file first to cross validate the outcome.
- Select the routed arrangement first using mouse selected & evoke key-in. Click on enter to execute the key-in. Notice that once key-in executed jumper gaps gets uniform as per schema changes.

See Also
communities.bentley.com/.../how-to-change-the-default-line-jumper-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.