OPPID: Standard Preferences

Hello Martin,

What specifically do you want to accomplish by adding these additional properties here?

This can not be accomplished in OpenPlant PID. Each class that uses size (Pipeline, Pipe run, inline components) has this value defined at the individual class level and when required, automatically adopt the size from the related component. Place a pipeline, then place the valve in the line. The valve adopts the line size from the associated pipe run. This is expected behavior. The same can apply for other properties. Insulation properties (thickness, type) can be set on the pipe run and then passed to the inline components upon their insertion.

The current Specification and End condition will change based on the class settings. The spec is default, but can change when the component is inserted. End condition is unique, in that when defined in the schema to use a specification mapping class for valves, they will adopt the end condition from the spec instead from the setting in Standard Preferences. Both of these properties can be handled at the class level OR based on the Standard Preferences settings. Again, tis is controlled by the schema configuration.

The difference between behavior in OpenPlant PID and OpenPlant Modeler is the PID functional components and properties typically carry more project centric data than the 3D components and as such need to adopt and adjusts from the related component. In 3D you are more likely (this does not mean always) to place a valve as a valve and maybe not directly in a pipeline - thinking design workflow, In a PID, you typically wouldn't place a valve and then move it to a pipeline. You typically start with equipment, add pipelines, then inline components and then other components such as instruments, etc.

Hello Tony,

it is a question of workflow. 
Typically I would draw the main process lines on my PID first.

In most cases I would have defined an insulation type, insulation thickness, (...) for these lines. This could be done with the default values in the schema. And this stays the same for lets say 10 - 15 lines.

Alright for the first lines, but now I switch to different lines. Lets say e.g. water.
I can change the service in the Standard Preferences, but these will also have different insulation, insulation thickness, type and so on. 
Now I have to define these property values for every line again and again, because every new pipeline starts with the default values coming from schemas.

Would be nice if I could set more values like I can set the Service when I know that my upcoming 25 lines will be with this service, this insulation material, this type, this thickness and so on.

Same goes for nominal diameter. Especially handy, when the pipe sizes have not been defined yet and you can just choose the placeholder size "x" for all the water lines for example. 

Hope it is understandable :) 

Hello Tony,

it is a question of workflow. 
Typically I would draw the main process lines on my PID first.

In most cases I would have defined an insulation type, insulation thickness, (...) for these lines. This could be done with the default values in the schema. And this stays the same for lets say 10 - 15 lines.

Alright for the first lines, but now I switch to different lines. Lets say e.g. water.
I can change the service in the Standard Preferences, but these will also have different insulation, insulation thickness, type and so on. 
Now I have to define these property values for every line again and again, because every new pipeline starts with the default values coming from schemas.

Would be nice if I could set more values like I can set the Service when I know that my upcoming 25 lines will be with this service, this insulation material, this type, this thickness and so on.

Same goes for nominal diameter. Especially handy, when the pipe sizes have not been defined yet and you can just choose the placeholder size "x" for all the water lines for example. 

Hope it is understandable :)