SpecGen: Create New Catalog. Placing FLEX HOSE in OPM. Not sure which (or both) is the issue.

When I create a new catalog using the catalog editor in SpecGen, I edit the Schema, then Add Table.

At this point, do I have to select one of the table names from the drop-down list, or can I create an entirely new table?  There is nothing in the drop-down for flexible hoses.

I have been trying to create a new table, and just naming it FLEX_HOSE, but once I do that, I Select the FLEX_HOSE table, then Add new component: FLEXIBLE_HOSE

But once created, Catalog Editor creates a PIPE table, and places the FLEXIBLE_HOSE component there, and not in the FLEX_HOSE table I had previously created.

At first I just blew this off, and went through the process of building my catalog.  There are only 6 sizes, so it wasn't too much work to add all the data.  Once entered, I added the catalog to my SPEC.mdb.  Everything looked fine.

I went into my model and tried to place a Flex Hose:

and OPM said:

Any assistance would be greatly appreciated.

Rahul, before you reply and tell me to submit an SR, I am already doing it as we speak.  My intention here was to reach out to the User Community.  The fact that I even need to submit an SR just to be able to place a common component into a model is indicative of a larger problem with OPM in general, but I digress...

  • Hello Mike,

    Thanks a lot for raising SR on your concern,

    OpenPlant Modeler requires important parameters & correct table definition to be placed in OPM.

    Please refer below attached video that explains the workflow to create Flexible Hose in OpenPlant SpecGen. Attached video also explains the placement verification of flexible hose in OpenPlant Modeler.

    HTH
    Regards | Deepak Singh

    Answer Verified By: Mike.McGinnis 

  • Hello Mike, 

    We appreciate your involvement here on Forum and we encourage everyone to participate here, as it can be shared to every user and analyst and you can get suggestion from everywhere. 

    Reason for asking to log SR is not a random behavioral decision. We are participating in discussion and further requesting user to log SR to allow us to forward the concern to Product Management or Development team to implement it in future version on product to make it up and running.

    As you may aware that any customization done or suggested by the analyst is solely based on few unit testing and no major smoke test done on that so we primarily also taking care of it that something gets logged and hence to enhance the product. 

    The priorities goes like this - 

    A. Participation on Forum. - 
         If any quick solution provided is fine or to provide existing wiki article. 

    B. Request for SR - 
        request user to create SR, in case a detail investigation is required or may turned into Enhancement/Defect. 

    C. Request to have a call or Private Chat - 
         Here again encouraging user to participate on forum. 

    We are also Glad that you contact Bentley using this media, which we are encouraging to everyone. We will ensure that you will be getting all possible assistance here. 

    Happy Posting!!Thumbsup tone3

    HTH

    -Regards | Rahul Kumar

    Regards,

    Rahul Kumar

    Product Engineer – Global Technical Support | Community Moderator

  • Thanks Deepak for sharing Video. 

    we may capitalize it and develop a knowledge base here so that other user should get benefit. 

    HTH, 

    -Regards | Rahul Kumar

    Regards,

    Rahul Kumar

    Product Engineer – Global Technical Support | Community Moderator