Processing - OpenPlant Isometrics Manager

Processing - OpenPlant Isometrics Manager

To Discuss content related to Processing isometrics Drawings in OpenPlant Isometrics Manager.

Product TechNotes and FAQs

OpenPlant Isometrics Manager [FAQ]

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Known Issues in OpenPlant PID V8i (SELECTseries 5)

V08.11.10

• When doing a File Compress neverenable the 'delete empty cell headers' option. Doing so will remove Pipelines, Instrument Loops, and Assemblies.
• Design History Undo and Redo have been disabled due to data integrity issues.
• AXSYS:
  • When doing an AXSYS to OPPID conversion, the user must be sure to open the AXSYS created dgn in the correct OPPID project. The AXSYS drawings are metric and should be opened in the OPPowerPID_Metric project or user created metric project. If not, a unit consistency error will be displayed and the dgn will not be converted. The user must restore the backup file and open again in the correct project.
  • Conversion of AXSYS Dgn files: Certain classes such as REACTOR are not currently converted as the same classes as they are not supported in OpenPlant PID, where possible they are converted to the next Class in the OpenPlant Schema hierarchy such as VESSEL. If this is not possible they will be imported as a cell.
  • Import of AXSYS Generated OWL files: Import of modifications in the class SHELL_AND_TUBE_HEAT_EXCHANGER in AXSYS via the OWL file will fail as the version of the ISO 15926 Supplemental Schema had a missing reference. Updates made via the imodel import will work fine.
• When cancel a pump placement onto a pipe run, a bad virtual nozzle is left behind. If not removed, that end of the pipe run can no longer be connected to. To fix,
  • Either Undo
  • Or manually select the bad virtual nozzle and Delete it.
• Placing a spec break at the end of a run will not work properly. Using the CP2 as the Insert By point will throw an exception. Using the CP1 will work; however it is not possible to later route another pipe run from that spec break. Therefore spec breaks should be placed inside of pipe runs.
• Integration with ProjectWise Ss4 and Ss4R, with "Plant" environment, has an issue creating the doucment. It will cause database synchronization problems. The Revision field is a VARCHAR(4) in the database. In the schema, the document revision is a double.
  • One time solution inside Project Wise Administrator:
    • PWA->DataSource->Environments->Plant->Attributes
    • double click or use right click "revision" to open the "revision Properties" dialog
    • in the Value tab, set the Default value to 0
    • in the Editing tab, set the Format string value to
      • "%4.1f" for one character after the decimal point
      • "%4.2f" for two characters after the decimal point
      • "%d" for no decimal point
    • If one time solution was not used:
      • If creating document with wizard, set the revision value during "Define Document Attributes"
      • If creating document without wizard, after creating document, open the document properties and set revision under Attributes tab
• Fence Copy loses logical groups: pipelines, instrument loops, and assemblies
  • Workaround: use Element Selection, instead of Fence
  • If had Copied using Fence,
    • For Pipelines:
      • 1. select pipe run(s), which are no longer in pipeline
      • 2. press desired pipeline type from Task menu, ex. Major
      • 3. dialog prompts to add to Pipeline, select Yes to add run(s) to pipeline
    • For Instrument Loops:
      • 1. select component(s), which are no longer in loop
      • 2. press Instrument Loop from Task menu
      • 3. dialog prompts to add to loop, select Yes to add component(s) to loop
    • For Assemblies: there is no workaround. If copied using Fence, the components will be placed as individual components. The assembly is dropped.
• Error moving two reducers together on same pipe run. This would be the case if you wish to move a control station along a pipe run segment.
  • Workaround: Reducers should be moved individually. Ex. to move control station a little to the right
    • 1. Drag/Move the reducer to the right of the bypass, further right
    • 2. Move the bypass and its components
    • 3. Drag/Move the reducer to the left of the bypass
• When using Interval synchronization mode, if synchronize in the middle of an operation sometimes an exception occurs in the Message Center. Operations include placing, dragging and/or manipulation commands.
  • Workaround: In the Interval Synchronize dialog, press No, if in the middle of an operation
• Problems can be exhibited when trying to generate drawings via Instrumentation and Wiring in a MicroStation environment, if OpenPlant PowerPID is installed after after I&W.
  • Workaround: Observing the following installation order will prevent these problems:
    • 1. OpenPlant PowerPID
    • 2. MicroStation
    • 3. Instumentation and Wiring
• OpenPlant PowerPID documents cannot be created or edited from Vision, if OpenPlant PowerPID is installed after Bentley Plant Framework.
  • Workaround: Observing the following installation order will prevent these problems:
    • 1. OpenPlant PowerPID
    • 2. Bentley Plant Framework
• Item Browser's Highlight and Zoom options have been disabled for logical groups: pipelines, instrument loops, and assemblies. It is still possible to highlight and zoom their individual components.
• Error synchronizing database when database replication is used
  • This has been fixed in OpenPlant PowerPID Ss5 08.11.10.59 and higher.
  • Workaround with OpenPlant PowerPID Ss5 08.11.10.47 thru 58: This is a one time setup workaround.

1. 1. 1. Install OPPID on master site
   2. 2. Modify theh project's pcf to set _AP_CHECK_COLUMN_ALTER_REQUIRED=1.  This new variable is explained in pid.cfg, defaulting to 0.  If this step is skipped, each time you start OPPID, your modifications in step 6 below will be wiped out!
   3. 3. Run OPPID and connect to the database
   4. 4. Close OPPID
   5. 5. Apply replication to database
   6. 6. Modify triggers, created by replication, for all replicatd tables to include SET NOCOUNT ON before the update statement and SET NOCOUNT OFF after the update statement.
   7. 7. User OPPID as always

Overview

To switch a drawing from one project to another, please do the following:

1. Open the affected DGN in OpenPlant PowerPID.
2. From the menu select Utilities > Key In.
3. In the ensuing dialog, type pid plantproject disassociate.
4. Close the DGN and manually move it to the appropriate project folder.
5. Re-open the DGN and it should prompt you for which project you want to associate it with.

See Also

Product TechNotes and FAQs

Plant TechNotes And FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

Bentley's Technical Support Group requests that you please submit any comments you have on this Wiki article in the "Comments" area below. THANK YOU!

Introduction

By default the control valve tag includes Area property in the tag format as shown below.



Currently, the instrument tag format is being inherited here because CONTROL_VALVE class is a child of INSTRUMENT class. So, if user want to remove the area property from the tag format he needs to modify the schema.

Steps to Follow

1. Open Class Editor and load OpenPlant schema from C:\ProgramData\Bentley\PowerPID (SELECTseries 5)\WorkSpace\OPPowerPID\schemas path.
   
   
2. Supplement it with the OpenPlant_Supplemental_Tagging schema from your project schema.
   
   
3. Locate the CONTROL_VALVE class and select NAME property from properties tab.
   
   
   
   
4. Click Override button on the right.
   
   
   
   
5. Now click Custom Attributes button and select Add/Remove option.
   
   
   
   
6. Change the location of both the schema to OpenPlant_Supplemental_Tagging.01.04 and click OK.
   
   
   
7. Save the changes in schema.

Verify the Result

Here compatibility across different release versions of OpenPlant Product Group with Operating Systems, ProjectWise and various Database types is presented. The compatibility matrixes are available in pdf format thus could be downloaded.

Follow below links for  instant access to required matrix:

• Operating System Compatibility with OpenPlant Releases
• ProjectWise Compatibility with OpenPlant Releases
• Database Compatibility with OpenPlant Releases

Operating System Compatibility with OpenPlant Releases

(Please visit the site to view this file)

ProjectWise Compatibility with OpenPlant Releases

(Please visit the site to view this file)

Database Compatibility with OpenPlant Releases

(Please visit the site to view this file)

Background

Defining a new/custom plant object in Project Administrator will lead to failing Isometrics generation using OPIM from within AutoPLANT session (in-session generation). The reason this happens is due to the fact that the new (custom) plant object does not have an appropriate mapping in the schema which can tell the generation process about it.

Steps to Accomplish

Loading OpenPlant_3D Schema

1. Open class editor and open ‘OpenPLANT_3D.01.04.ecshema.xml’ from project location.

            For ex.(default metric project path)

            C:\ProgramData\Bentley\Plant V8i\BentleyPlantV8iProjects\SAMPLE_METRIC\Config\OpenPlant\schemas

Define New Class.

1. Next step is to create a new derived class under NAMED_ITEM class. Find the NAMED_ITEM class using Search option in Class Editor or browse manually. (refer below image)

2. Once NAMED_ITEM class located, right click on it and select “Add Derived Class” to add a new class. Give     an appropriate name to new class like SHEETNR_CLASS etc. (refer below image)

Define Custom attribute.

1. Add a custom attribute to that class. This would help to map it to the appropriate table in the plant database. For this, right click on the class and select Add/Remove… option under Custom Attributes menu as shown below

         2. This would launch a dialog as shown below. Select AP_3D_ClassProperties and add it into the list of                        Applied Custom Attributes. Press OK on this dialog to add it to the class.

Define Mapping in Custom Attribute Properties.

1. Now need to map the class to the table in the project database. In the “ClassNames”  section of AutoPLANT_PDW_Class_Map, right click and select Add element option. This would add a child node to ClassNames as ClassNames[0]. Type the name of the project database table.

       2.  Press “Save” button to save this schema and reload the drawing to start using OPIM in-session.

      3.  Verify result.

Adding new property

Add the new property SHEETNO to Piping Component and also add AutoPLANT_PDW_PROPERTY MAP

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this Comments or Corrections?" section. THANK YOU!

. 

Introduction

In OpenPlant PID, there are annotations for Pipelines which are represented in a box. By default, there are three properties which are annotated in the annotation box Size, Pipe Run, Pipeline Name as shown below. As per project requirement users may need to customize the annotation to change the properties of his choice. Below steps will illustrate the procedure to customize the pipeline box annotation.

Steps to Follow

1. Open Class Editor.
   
   
2. Load OpenPlant_PID schema and supplement it with OpenPlant_PID_Supplemental_Imperial schema.
   
   
3. Locate the PIPE_LINE_ANNOTATION_ALT7 class in the schema.
   
   
   
   
4. Switch to Properties tab and add a new property PIPELINE_FLOW_RATE.
   
   
   
   Note: Change the Property type from 'string' to 'double'.
   
   
5. Add 'Property Custom Attribute' on this property and add the default value as Flow Rate.
   
   
   
   
6. Save the changes in schema and close Class Editor.
   
   
7. Open Miscellaneous.cel file in OPPID from the concerned project and open PIPELINE_ANNOTATION_ALT1 model.
   
   
   
   
8. Go to Element>Tags>Define.
   
   
   
   
9. Select PIPELINE in Sets section and you will see the related properties in tags section on the right.
   
   
   
   
10. In this step, we will remove the PIPELINE_NAME property which represents Pipeline Tag.
    
    
    
    
11. Click Add button to add PIPELINE_FLOW_RATE property into the tags.
    
    
    
    
12. Click OK and exit out of the Tag sets command.
    
    
13. Go to Tools>Text>Tags>Attach Tags.
    
    
    
    
14. Select PIPELINE in attach tags dialog.
    
    
    
    
15. Select the boundary of the box and select PIPELINE_FLOW_RATE from the dialog and click OK.
    
    
    
    
16. Place the Flow Rate tag into the box.
    
    
    
    
17. Save the settings in the Miscellaneous.cel file and switch to drawing.

Verify the Result

1. Place a new Pipeline in the model and give the value to Flow Rate property.
   
   
   
   
2. Now in Annotations task, select Pipeline Annotations and then Pipeline Box Annotation from the list.
   
   
   
   
3. Now Place the box annotation alongside the pipe run.
   
   
   
   As you can see above the value has come up correctly in the annotation box but the units did not. It's a known limitation as of now and an enhancement has been logged for this and should be implemented in the future releases.

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Background:

DWG line styles are a subset of MicroStation line styles. Because of this disparity, there are a number of features in MicroStation line styles that do not translate directly to DWG.

Below steps help you to map OpenPlant Isometrics Manager isometric DGN line style to his matching dwg line style.

Steps to accomplish:

Edit OPIM.csv file. 

1.      Generate isometric in dgn format.

2.      Go to file>Save As

3.      Select save as type Autodesk (R) DWG Files(*dwg).

4.      Click on option tab. Refer below image.

5.     Click on edit csv tab.

6.     Click on line style worksheet.

7.       Click on folder button to add all existing line style in dgn.

8.    Once all dgn line style available, map dgn line style with suitable dwg line style. Refer below image:

       

         Refer below image to check dwg line style name.

9.     Close the csv file.

10.   Click Apply Line Style Mapping.

11.   Click ok.
12.   Generate isometric to review the result.

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

OpenPLANT HVAC

This technical video will explain how to package a project to send to another client or technical support.  Often times this is needed for project work share or to debug problems that can occur.  Project Packager will create a copy of the project and project data.  These files are pushed to a zip file created.  The data is copied to XML format ready to be unpackaged the same route.  Please refer to the video for these details:

(Please visit the site to view this video)

This applies to most applications. I am using Data Manager as an example.

User starts Data manager application. It starts up and shows as an icon at the bottom of the Windows screen by the START button. It appears to be started off the screen and the user cannot see the Data Manager application.

1. Select Data Manager icon on the bottom of the screen.

2. Press Alt + space

3. Press M

4. Press any arrow key on keyboard.

5. Drag back to main monitor.

Introduction

By default the bentley Process & Instrumentation application package is not automatically configured for the use of OpenPlant PowerPID. In order to use Bentley Vision with OPPID it needs to be added to the configuration files

Adding OPPID to the configuration files

To view/edit/modify OPPID drawings, the at.ini configuration file must be manually updated. Currently Vision only supports one OPPID workspace at a time. So if you are working in different workspace such as ISO or Metric the At.ini must be modified.

NOTE: The paths mentioned may vary depending on install location or version.

1. Open the at.ini file in Notepad. This file is located in C:\ProgramData\Bentley\Plant V8i\CFG

OPPID needs to be regisered as application in the GENERAL section of the at.ini file

• Search the at.ini file for "[GENERAL]". This section may look like this:
• Examine the APPLICATIONS variable and check to see if there is an OpenPLANT P&ID entry. If there is none add it to end of the list

[GENERAL]
AP=%NETWORK_ROOT%
APWS=%LOCAL_ROOT%
AT_BIN_DIR=%NETWORK_ROOT%\bin
APP_RELOAD_FLAG=0
APTMP=C:\ProgramData\Bentley\Plant V8i\Tmpdir\
APPROJDB=C:\Bentley Plant V8i Projects\
MSCADAPP=C:\Program Files\Bentley\MicroStation V8i (SELECTseries 1)\MicroStation\ustation.exe
ProjectDetailsForLogin=0
SavedUserPW=
LastUser=Supervisor
CurProject=0001 APPLICATIONS=DocManager;PIPING;ISOMETRICS;/.../P&ID;STRUCTURAL,OpenPLANT P&ID;

The OpenPLANT P&ID value is also used as a section header in the at.ini

• Search for the [OpenPLANT P&ID] section header in the at.ini. If there is none add it

[OpenPLANT P&ID]
REGAPP=OPPID
DESCRIPTION=OpenPLANT P&ID


The application configuration variables and their meaning:

 Example:

[OpenPLANT P&ID]
REGAPP=OPPID
DESCRIPTION=OpenPLANT P&ID
WSConfig= -wuuntitled
OPPID_PROJ= -wpOPPowerPID_Imperial
FILETYPES=DGN
DGN=seed_eng.dgn
PATH= C:\ProgramData\Bentley\PowerPID (SELECTseries 5)\WorkSpace\Projects\OPPowerPID_Imperial\Dataset\seed
MSCADAPP= "C:\Program Files (x86)\Bentley\PowerPID (SELECTseries 5)\PowerPID \powerpid.exe"

Application Setup

If the OPPID is not in the Vision Document Tab, it must be added. To do this selection File->Application Setup. From this Dialog add OPPID to the list.

Background

OpenPlant Isometrics Manager places Flow arrow annotation in the NOTES cell. Some user wants to turn off the Flow arrow annotation. We can do this by turning off the User label Notes, but it would turn off all notes

Following steps helps to turn off flow arrow annotation but keep remain on other notes.

Steps to Accomplish

1. Open isometric configuration.

2. Click on isometric style tab.

3. Select ‘User label note’.

4. Add following entry

   Exclude: EC_CLASS=’FLOW_ARROW’

    

5. Save the file and generate isometric to review the result.

Note: For OpenPLANT Isometric manager 08.11.09.470 and above add the entry in Variable Shape Note instead of Note lablels like below image.

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!

Introduction

When generating Orthographic drawings alongside OpenPLANT Modeler it is essential to make sure most updated input will be used by Orthographic engine. It sometimes can happen that changes were done to the source file but the Orthographic engine does not use the updated model for generation.

To avoid this type of scenario’s make sure to enable “clear intermediate files” option prior to generate drawings. Please see below Image

Steps to Accomplish

See below valves, pipes, tees and other components missing in the orthographic drawing

Results after clearing Intermediate files:

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this Comments or Corrections?" section. THANK YOU!

Problem Description

During isometric generation user has configured report.def to move pipe support form Shop session to Field session. However, the sequence of components in the field doesn't confirm their standard.

Steps to Resolve 

1. Uncomment support entries from report.def file.

       2.  Go to project location and open ‘style.cfg’ file in notepad.
              Example: C:\ProgramData\Bentley\Plant V8i\Bentley Plant V8i Projects\SAMPLE_METRIC\Config\OpenPlant\Isometrics\styles\IFC\config

        3.   Edit ‘style.cfg’ as per below image.

          4. Save the file.
          5. Generate isometric by using specific style (IFC).

See Also

http://communities.bentley.com/products/plant/design___engineering/w/plant_design_and_engineering__wiki/17465.how-to-add-field-material-under-shop-material-in-openplant-isometric-bom

Comments or Corrections?

Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this Comments or Corrections?" section. THANK YOU!