Instrument location codes in OPPID

Most sheet borders have letters up the sides and numbers across the top and bottom to help in locating items on the drawing. In the instrument table there is a field called 'Location Code'. Is this the intended function of this field? If not what is it for? Could it be used for this purpose?

If the answer is yes, then can OPPID be setup to automatically enter the code for an instrument (or valve) when it is placed in a drawing? Seems like it wouldn't be that hard to do (for a Bentley programmer anyway!). The user would need to define their grid and the system would have to check those coord. against the coord. of the placed item.

I looked online and I didn't see anything that addressed this that I could tell.

Thanks,

  • Hello,

    The Location Code field in the database is used to store the value for the instrument location based on the instrument type - Field, Control Room Panel, Back of Control Room panel etc.

    In terms of getting the border coordinates defined for components on the drawing (A2, or C3 etc.). This has been submitted as an enhancement request but is not available in the application today.

    I highly recommend you log in and submit an enhancement request. The greater number of users who ask for a feature will help Bentley to prioritize the request.

    PS -I have attempted to do this based on the current schemas and data that I can pull from a component, but have been unsuccessful in getting this to work. It will require some code to partition the drawing frame based on the border size and letter/number origin and sequence (up the side, across the top etc.)

    Regards,

    Tony DeRosa

    Bentley Plant 

     

    Tony DeRosa

    Senior Application Engineer

    Bentley Plant



  • Thanks Tony,

    There is another field named Instr_Loc, can this one be used in the interim?

  • Hello Gary,

    Currently, automatically extracting the grid data from OpenPlant PID is not possible. As far as using the fields LOC_CODE or INSTR_LOC - you could use either field. In my initial post I noted that the LOC_DEO filed was used to define the physical instrument location in the plant (IE Panel, Field etc.).

    The current issue is that today, we can not extract the grid location of a component from within OpenPlant PID.

    You could MANUALLY enter this value but this would defeat the purpose of intelligently using the border grid system.

     

    Tony DeRosa

    Senior Application Engineer

    Bentley Plant



  • Hello Gary,

    I have an update for this request. I have been successful in extracting the coordinates of instruments, and mapping these to a border letter/number grid system.

    It is not as pretty as I would like it to be but it does work. I still need to wrap up testing. As soon as this is complete, I will formalize and finalize the solution. I will post on the Wiki page of this Community site.

    A few things about what I have done:

    1. This will work for one size of drawing border only. It can be made to work for multiple borders provided the numeric and alpha axis both start in the lower left hand corner of the border and the spacing between grid letters/numbers is the same across all borders.
    2. It takes multiple properties, ECExpressions, and System.String symbol sets to get to each decimal equivalent  for each axis - vertical and horizontal. This is the part that I consider to be " not pretty". I will work on this as time permits and attempt to clean this up.
    3. This is configured for INSTRUMENT class only at this time.
    4. This will require the addition of a new field to the database. The property that contains the border grid location will be mapped to this to field.
    5. Note - because this is a property mapped to the database, every move of an instrument will require a sync to the plant project database in order to update this property. Often users will not sync a file when they move an element. Synching can be set to automatically occur on file close allowing the property to be updated in the database, thus avoiding this issue.

    Regards,

     

    Tony DeRosa

    Senior Application Engineer

    Bentley Plant