Known Issues in OpenPlant PowerPID V8i (SELECTseries 5)
V08.11.10
Known Issues of Bentley OpenPlant PowerPID V8i (SELECTseries 5)
- When doing a File Compress never enable 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 SS3, 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 Synchronization dialog, press No, if in the middle of an operation
- 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. Install OPPID on master site
- 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. Run OPPID and connect to the database
- 4. Close OPPID
- 5. Apply replication to database
- 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. User OPPID as always