Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Needs review
Workspace OpenPlant Modeler
Created by Guest
Created on Mar 12, 2026

Align/Simplify Nominal Diameter and Design Size Behavior Across PID and Modeler

Nominal diameter and design size behave differently in OpenPlant PID and OpenPlant Modeler, causing duplicate data entry and a high risk of mismatched pipeline sizes between 2D and 3D.

Current behavior

In PID:

  • Design size

    • Drop-down PickList.

    • Controls pipeline size, valve size, and what appears in pipeline annotations/tags (when configured).

  • Nominal diameter

    • Write-in field with a default value of 4".

    • Not linked to annotations, valves, or design size.

    • Can easily become inconsistent with design size, since both must be updated separately.

We explored linking design size to nominal diameter to avoid entering the same size twice, but were told this is not possible because nominal diameter is a hard-coded “special” property.

In Modeler:

  • Nominal diameter is the primary size property for line information.

  • It is a PickList in Modeler (unlike the write-in field in PID).

  • If we hide or stop using nominal diameter in PID, 3D line sizes in Modeler are no longer correct.

Result: We must enter size twice (design size and nominal diameter) and manually keep them in sync across 2D and 3D.


Requested enhancement

  1. Unify and/or link design size and nominal diameter so that:

    • Only one size input is needed.

    • Both PID and Modeler use that value consistently for pipelines, valves, and 3D line sizing.

  2. Provide configuration to:

    • Choose a single “master” size property (design size or nominal diameter).

    • Ensure annotations, tags, and 3D models all reference that property.

  3. Once a master is defined, allow hiding or de-emphasizing redundant fields without breaking data flow to 3D.


Value / impact

  • Eliminates duplicate data entry and reduces human error.

  • Keeps 2D PID and 3D Modeler pipeline sizes consistent.

  • Improves data integrity and workflow efficiency.

  • Delivers the level of customizability expected from OpenPlant for core pipeline properties.


How frequently will feature be used? Several times a day
How much time will you save? Save endless time trying to figure out inconsistencies, putting the same data in several fields, etc.
Your Industry Energy Infrastructure