OPM Bolts and Gaskets: How to control them

We are seeing a number of issues in our models where OPM will control what line/spec bolts and gaskets are associated with where the joint is at a line change or spec break.  The modeler needs to be able to control this, not OPM.

Has anyone else run into this, and if so, how are you dealing with it?

  • OpenPlant places the gaskets and bolts from the spec/lineNumber that it is currently selected when the flange to flange connection is made.  So currently the bolts and gaskets are placed on the new spec/lineNumber and not the previous spec/lineNumber.  

    If the bolts and gaskets need to be put on the first spec/lineNumber then the spec/lineNumber will need to be changed back to its original setting then the first flange would need to be deleted and replaced thus pulling the bolts and gaskets from the original spec and placing it on the original lineNumber.

    Other users have encountered this issue and a change request has been made to do the following:

    • Allow the user to set the behavior between having the bolts and gaskets use the existing flange spec/lineNumber or new spec/lineNumber.
    • Allow Pipeline manager to reassign the spec/lineNumber of bolts and gaskets.
    Joey Bertone
    Available
    Senior Technical Support Engineer
    iTwin Services 
  • Hi Joey,

    Thank you for your reply.

    We do not see this behavour.  I have just tested this to make sure my workflows are correct, and regardless of the settings in SPPC, the bolts and gaskets are assigned to the linenumber of the first flange.

    We are using work packs and commodity codes to manage purchasing, so this issue becomes very important to us.

    On a related note, we have also seen where modifying a seemingly unrelated component (an upstream tee) causes OPM to "rebuild" the flanged connection and reassign the linenumber and spec for the bolts and gaskets.  Automatic behavour like this is unacceptable, as it has a direct affect on material lists.

    Will there be a priority build to address these issues?  Currently we are working to support the shutdown of a gas metering facility, so our data must be exact.  This issue is currently causing us a lot of grief, and we could sure benefit from a solution.

    Thank you,

    Scott