OPPID SS5: How to get service from pipe run into instrument?

Sanrise,

Here is a documnet deifning the precedure to pass SERVICE from PIPELINE to PIPE RUN to INSTRUMENT and other inline components.

I hope this helps,

Tony DeRosa

Bentley Plant

Hello Tony,

We didn't get the SERVICE-property to INSTRUMENT although we followed your instructions. With valve we managed to get it work. Any ideas?

Hello Tony,

We got the SERVICE-property transferred to the instruments and valves as
you wrote in your instructions. But instruments and valves get the right
service code after the pipelines service code is changed.

We would like to get the right service-property appear automatically to
instruments and valves when we place them to the pipeline.

In a Modeler's schema the service property of a valve is calculated from the pipeline service and it can't be changed for the valve.

We'd like the same feature for PID piping components. We can use the same as 3D for valves (as below).

But we'd like the same for instruments also. So that users can only change the SERVICE property for a pipeline and not for any other piping component.

Sanrise,

I will look in to the procedure as to why the service is only being set after an edit. It does work here so perhaps I missed the addition of a custom attribute in the document.

I am not sure if we can set the service value to be non-editable on the individual components. I will need to check this.

I will get back to you shortly.

Thanks,

Tony DeRosa

Bentley Plant

Sanrise,

What version number of OpenPlant PowerPID are you running?

Go to Help About and get me the full version number.

Thank you,

Tony DeRosa

Bentley Plant

Tony,

I'm using version 08.11.10.202.

- Sanna-

Sanna,

I have discovered that the Notfy Related Component of Property Value Change custom attribute MUST have the "Related Class Name" field explicitly defined - IE oppid:PIPING_COMPONENT.

In my case I did not have to do this to the OBJECT_HAS_INSTRUMENT notify node so for this I would verify all your settings.

See the revised attached document.

I hope this helps,

Tony DeRosa

Bentley Plant

Sanna,

I have discovered that the Notfy Related Component of Property Value Change custom attribute MUST have the "Related Class Name" field explicitly defined - IE oppid:PIPING_COMPONENT.

In my case I did not have to do this to the OBJECT_HAS_INSTRUMENT notify node so for this I would verify all your settings.

See the revised attached document.

I hope this helps,

Tony DeRosa

Bentley Plant

Hello Tony,

There is a big difference between PPID SS5 old and new version. We’d like to use the new version.
Here’s a comparison, how the two versions behave on our system about this issue.
Have you tested this in version PowerPID_08.11.10.202?

PowerPID_08.11.10.38 (Select Series 5):
(Old version)
If we put oppid:PIPING_COMPONENT in “Related Class Name” field, the service code doesn’t pass on to the instrument. And if we change pipelines service code, the instrument doesn’t still get the service code. With this option only valves get service information automatically when we place them to the pipeline.
But when we put oppid:INSTRUMENT in “Related Class Name” field (see below) the valves and instruments get the right service code directly when we place them to the pipeline.
 

PowerPID_08.11.10.202 (SS5):
In this version we only get service code automatically passed to the valves if we put oppid:PIPING_COMPONENT in “Related Class Name” field. Instrument doesn’t get service code even if we change the pipeline’s service code. And instrument and valve doesn’t get any service code even if we put oppid:INSTRUMENT in to “Related Class Name” field.
The crucial thing for us is to get service code from pipeline to instrument automatically!

- Sanna

Sanna,

I have configured this in PowerPID 08.11.10.202 and it is working fine. Both inline components and instruments are getting service from PIPELINE to PIPE RUN to the instrument or valve at initial insertion and when the service is changed on the PIPELINE the new value is cascading to the instruments and valves.

At this point all we can do is for you to send me your schema's from your workspace. If you like please zip up the complete workspace folder and then message me here and I will send you a link to post the files for me to review.

If it's easier then email me the files at tony.derosa@bentley.com

Thank you,

Tony DeRosa

Bentley Plant

Tony,

Now I have zip our workspace folder. We are using OPPowerPID_ISOproject.

Sanrise,

Please provide me a email address where I can send you a link to post your workspace.

Thanks

Tony

sanna.ristimaki@outotec.com