Overview

In AutoCAD or AutoPLANT, sometimes dialogs can freeze up or become corrupted. This is a solution to trouble shoot these sort of problems.

Solution

• First, if the dialog itself will not load or it loads with "hatch" over it, then the OCX or DLL files may not be registered properly. Please consult Bentley Technical Support in order to find out which files to replace or register.
• Second, there is an AutoCAD option that allows a user to lock layers. Be sure to check this setting before continuing.
  
  Window > Lock Location > All > Unlocked
  
  
• It is also possible that the AutoCAD profile has become corrupt. In order to reset the profile, delete the following file:
  
  C:\Documents and Settings\user.name\Application Data\Autodesk\AutoCAD 2009 (or other version)\R17.2\enu\Support\Profiles\<profile name>\Profile.aws
  
  If this does not work, it is possible that another profile is corrupted. Replace the following file using a non-corrupted one from another workstation.
  
  C:\Documents and Settings\user.name\Application Data\Autodesk\AutoCAD 2009\R17.2\enu\Support\Profiles\FixedProfile.aws

See Also

Product TechNotes and FAQs

External Links

Bentley homepage

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

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

Overview

With Bentley View installed on the machine, following 'ProjectWise Login Error' is displayed on opening the document through Bentley Vision in a ProjectWise enabled AutoPLANT project:

Steps to Resolve

To avoid this:

1. Kill the 'BPCom32Host.exe *32' from Task Manager.
2. Next load the document through ProjectWise Explorer.

Once above is done, this issue will not reoccur.

Note: Removing Bentley View from the machine fixes the problem. 

Comments or Corrections?

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

Overview

This TechNote goes over important issues dealing with ProjectWise integration with AutoPLANT with "Side by Side Installation" of ProjectWise.  "Side by Side Installation" refers to having two or more different releases of a product running on the same machine.  In this case, it is referring to the XM release of AutoPLANT and Projectwise with the V8i release of the same products.  The two versions of ProjectWise that this document focuses on is 8.9.4.89 for XM and 8.11.4.16 for V8i.  The versions of AutoPLANT are 8.9.3.30 (with SP2 8.9.3.49 and Framework 8.9.4.47) for XM and 8.11 (pdw 8.11. and Framework 8.11.5.41)

Things to Know

• When installing ProjectWise, the folders need to be different.  Be sure to make sure that ProjectWise V8i does not override the XM ProjectWise folder.  If this happens, then the XM version will no longer work. 
• Which ProjectWise was installed last, usually the V8i, that version will override the other versions Application integration.  What this means is that when going into AutoPLANT's Project Administrator, the error below will prompt.  In order to work around this, the machine has to have a Version Switch done to it.  Please look in the Version Switching section of this TechNote for details on how to do this.
• When launching any ProjectWise Shortcuts (created by dragging a folder or datasource on to the desktop), they will load in the last installed ProjectWise.  The probelm with this is that an XM Datasource can NOT be opened in the V8i Explorer.  So if there is a link on the desktop that points to a XM datasource and it is clicked, ProjectWise Explorer V8i will launch and the program will hang for a long time before prompting an error. 
• Datasources created in one version can not be opened by clients (ProjectWise Explorer) of a different version.  For example, a V8i datasource can NOT be opened with the ProjectWise XM Explorer
• There is a patch for XM to allow it to work with ProjectWise V8i.  This is recommended if the client needs to work on both AutoPLANT releases, but doesn't want to run both ProjectWise V8i and XM on the same machine. 

Version Switching

In order to use AutoPLANT's Project Administrator with the corect version of ProjectWise, the computer running the two versions most have the correct version set, ie. XM for XM and V8i for V8i.  The one exception to this would be to run with AutoPLANT patch that allows XM to work with V8i ProjectWise that was mentioned above.  In order to do the Version Switching, the client will need to do the following:

1. Opening the Control Panel loads the explorer.exe process, which may interfere when you try to switch the version of the ProjectWise Network Configuration Utility. Before you begin, it is recommended that you restart your computer, or otherwise ensure that the explorer.exe process is not running. If you have not opened the Control Panel since starting your computer, you can probably skip this step.
2. Open a command prompt and go to "...\ProjectWise\bin" or "...\ProjectWise V8i\bin" depending on where it was installed
3. To switch the active version type the following for each version (Note: Excluding the " " for the command below, it is just to show the whole command that is needed)
   1. For ProjectWise XM type "cscript versionSwitch.vbs /89" 
   2. For ProjectWise 2004 type "cscript versionSwitch.vbs /85"
   3. For ProjectWise V8i type "cscript versionSwitch.vbs /811"

Questions

For more information on running ProjectWise XM and V8i Side by Side, please contact Technical Support. 

See Also

Add link to referring product TechNote entry by enclosing its topic name in brackets.

Add links to other related wiki entries.

Product TechNotes and FAQs

External Links

Add links to any helpful external resources by entering the name and using the hyperlink button to provide the URL. For instance:

Bentley homepage

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

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

If the Project Type Conversion Wizard* is not installed how do I manually convert my Distributed Project Mode to the Central Mode? 

* The Project Type Conversion Wizard is a tool found in the Tools menu of Project Administrator.  However, the Project Type Conversion Wizard is only installed with Plant Design Workgroup.

Please follow the steps outlined below to convert the project:

1. Make sure everyone is out of the project.  Backup the project.
2. Browse to the Data Repository for the project. This will be the Projdata.mdb or SQL Server, Oracle Database.
3. Open the Properties3d table and modify the DBACCESSTYPE Value from 1 to 2 as outlined below:

Distributed Project Type value is 1.  The Central Project Type value is 2.

See Also

Product TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

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

Overview

When integrating AutoPLANT with ProjectWise, it is possible to use a Windows' Domain Account rather then a SQL account.  This TechNote goes over the basic steps in setting this up.  One thing to note in this TechNote is that the same Domain Account was used in all the steps that called for one.  Also, this TechNote doesn't go over the details of Integrating an AutoPLANT Project with a ProjectWise Datasource.  It mainly covers the use of a Domain Account with this integration.  Some steps maybe skipped in this document and it is advised that someone experienced in Integration perform this process. 

Setting up the Server

The first thing that is needed is to setup the server side of things.  This includes setting the ProjectWise Services to use a Domain Account, creating the database(s) in SQL, and creating the ODBC Connection.

In order for ProjectWise to work correctly with the AutoPLANT Integration, it is best to set the Integration Server to use a Domain Account to start itself rather than the Local System.  This can be done by going into the Administrative Tools>Services.  From there locate the 'ProjectWise Integration Server V8i' and set the 'Log On As' to a Domain Account, like the image below -

For those unfamiliar with AutoPLANT and ProjectWise Integration, the databases can be setup in two different ways.  They can either share a database or they can both have their own database.  The thing to keep in mind is that if they each have their own, they most have the same Owner.  To get the database setup using the Domain Account, it is best to create the user in SQL first, then when the database is being created, point to this user as the Owner like the example below -

In this example, two databases were used.  One for ProjectWise called PW-TEMP and the other for AutoPLANT called AP-Temp.  Both were pointed to the same Domain Account as shown above.  The next step was to setup the ODBC connection using the Domain name.  In this process, the ProjectWise database is used and the option 'With Windows NT authentication using the network login ID.' was selected as seen below -

Creating the Datasource

Now that the server is setup and the databases are ready to be used, the Datasource needs to be created.  This is done through ProjectWise Administrator.  During this process, the ODBC that was created to point to the PW-TEMP database is used.  Also, when the application requests the database user account, the Domain Account is used. 

In this example, the Domain Account was also used for the ProjectWise datasource's Administrator Account.  This has been tested with a basic user name and password such as admin/admin and it should also work when using the Domain Accounts.

Once all the other options are completed and the datasource is being created (please note that AutoPLANT integrated datasources don't typically use the Template option so that may need to be unchecked), the program should ask for the location of the Storage area.  Here the Datasource Administrator account password is needed for verification.  If the Domain Account was used, then place that password in.

This will finish up the Datasource creation. 

AutoPLANT Project Creation

During the creation of the AutoPLANT project, the 'Use Windows NT Integrated security' needs to be used and the Domain Account that was used as the SQL owner of the AutoPLANT database needs to be logged into that machine. 

This is because the users of both databases (AutoPLANT and ProjectWise) MOST be the same owner, even if they are part of the same database.  Once the AutoPLANT Project is created, the integration can begin. 

Integration

Now that all the connections should be using the Domain Account and both the AutoPLANT Project and the ProjectWise Datasource are created, the integration can being.  (NOTE - there is now specific order when creating the AutoPLANT Project and the ProjectWise Datasource, they can be done in any order, but both need to be completed to being the integration process). 

The integration process is done in AutoPLANT's Project Administrator (not to be confused with ProjectWise Administrator).  Go through the options for setting up the integration and when it comes time to log into the ProjectWise Datasource, be sure to use the Domain Account. 

Once this and the other settings are correct, the integration can be done. 

See Also

Plant TechNotes and FAQs

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

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

Overview

For OpenPlant Isometrics Manager Bill of Material, desired attributes can be added/modified using Report.def file present in Config folder located in its project root. It can be experienced using both OpenPlant modeler and AutoPlant.

Problem Description

PIECE_MARK information only shows for reducers/Pipes and valves. To facilitate the same information on other fittings/components/Fasteners/Etc, user needs to modify schema through class editor by assigning PIECE_MARK property to all classes to enable to get it on all components. Below are the steps to achieve it. 

Steps to Resolve

1. Launch Class editor and navigate the project folder. Below are the project root mentioned:
   C:\%ProjectRoot%\Config\OpenPlant\schemas.
   
   
2. Open ‘OpenPlant_3D.01.04.ecschema.xml’ schema.
   
   
3. Supplement it with ‘OpenPlant_3D_Supplemental_Isometrics_Isoextractor.01.04.ecschema.xml’ schema.
   
   
4. Create a property PIECE_MARK under Device class in order to inherit the property under all available piping component. The best way to do  is to copy the property from existing class and paste it under Device class.
   
   
5. For instance Select Pipe Class and check property PIECE_MARK to copy it and then paste it under Device class. See image below.
   
   
   
   
   
   Note - Recheck the copied property which should contain ‘ AutoPlant_PDW_Property_Map’ custom attribute as shown in above image.
   
   
6. Save and close Schema.
   
   
7. Generate Isometrics and verify results. See image below of one sample output. 
   
   

See Also

Comments or Corrections?

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

To skip the labels on Flange Assemblies in Isometrics Drawing.

Background

In OpenPlant Isometrics Manager, on flanged assemblies mating component do possess seals and fasteners which labels altogether like Fx Gy Bz. In some cases requirement is to display only flange index. By using the SKIP variable, modeler can disable the other labels on isometric drawing. Below steps illustrates on modifying the rep_sortgroups.txt file. Below explanation has been illustrated in context with OpenPlant Modeler & OpenPlant Isometrics Manager.

Steps to Accomplish

1. Launch OpenPlant Isometrics Manager and open Isometric Configuration dialog box.
2. From Advanced option and click on Explore Style configuration option. See image below.
   
   
   
   
3. Navigate to style folder and select rep_sortgroups.txt file.
4. Check feature for SKIP as shown below.
   
   
   
   
5. Make the changes to following sort groups as shown in below image. 
   
   
   
   
6. Save & close the file. 
7. Generate isometrics & verify the results. 
   
   
   

Case 1

To Delete the Gasket & Fastener from BOM report

Add expression in report.def file as shown in below image: 

To Show Gaskets & Bolts in Bill Of Material separately

Note:Using the Above two modification in report.def file will provided flexibility to user to customize the BOM irrespective of Labels in drawings.

         See results below:

Case 2

To not assign PARTID to the BOLTS that are excluded in the BOM.

Even when we exclude any component from the BOM, the Isometrics Engine assigns PARTID to it and excludes it from the Bill Of Materials, resulting into improper numbering in the BOM. So it is advisable that we do not assign a PARTID label to the component.

To exclude it from getting a PARTID, open the rep_sortgroups.txt and add SKIP = 1 at the last line as shown in the below image.

See Also

You may also refer OpenPlant Isometrics Manager help file menu for Explore Style Configuration option. 

Comments or Corrections?

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

Overview

To make branching components appear in the drop down list of the branch table.

Problem Description

Although present in the specs, the branching components are not available in the branch table of the SpecGen.

Steps to Resolve

1. Load the spec in the Specification Generator utility.

2. Confirm if all the required catalogs are attached.

3. It is checked in the branch table if all the components are there in the drop down list. If not there then go to the file menu and select SpecGen Preferences

4. Create additional Branch Tables in Spec option should be checked.

5. In the Spec menu, dynamic filtering should be unchecked.

6. Open the branch table menu option and uncheck filter spec. 

7. Press OK and build entire spec, this time it wll show all the available branching components in the branch table of the SpecGen.

Still a Problem?

If above problem still persist, then please create a Service Request and contact the Bentley Product Advantage group.  Please include a list of all relevant details to get in depth analysis for a solution or workaround. 

Comments or Corrections?

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

To Change the graphics of Pipe union from Hexagonal to Circular

Background

Currently in OpenPlant Modeler, Pipe Union has a Hexagonal Graphics.

As per project requirement it might be needed to have a Pipe Union component with Circular Shape.

Steps to Accomplish

1. Launch Class Editor from OpenPlant Project Administrator
   
   
   
   
2. Open OpenPlant_3D schema and supplement it with
   
    -> OpenPlant_3D_Supplemental_Information_3DComponent.01.07.ecschema.xml
    -> OpenPlant_3D_Supplemental_ModelingViews.01.07.ecschema.xml
    -> OpenPlant_3D_Supplemental_Modeling.01.07.ecschema.xml
   
   
3. Browse to classes -> Plant Base Object -> Named Item -> Device -> Piping component -> Inline Pipe Component -> Pipe union
   
   
   
   
4. Go to Properties tab and search for FLATS property and select it
   
   
   
   
5. Click on Custom Attributes -> Add/Remove..
   
   
   
   
6. Remove the attribute OpenPlant_Physical_Catalogue_Property_Map by double clicking it
   
   
   
   
7. Click Ok and save the schemas and exit Class Editor
8. Launch OpenPlant Modeler and verify results
   
   

See Also

Comments or Corrections?

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

Overview

This is a complete install order for AutoPLANT Products which includes some addition software packages that can be used along side with AutoPLANT. Some of the listed software is optional, depending on which products are being used. See the notes under each software for more information.

Install Order and Versions

1. Support AutoCAD software
2. MicroStation V8 XM Edition Software Prerequisite Pack - 08.09.04.01
   • Required for Bentley View and Bentley Navigator
3. Bentley View XM Edition - 08.09.04.51
   • Viewer for Document Manager and Vision
4. Bentley ProjectWise V8 XM Edition - Client Setups - 08.09.04.89
   • Only needed if running ProjectWise
5. Bentley AutoPLANT P&ID XM Edition - 08.09.03.05
   • 2D piping package
6. Bentley AutoPLANT Plant Design XM Edition - 08.09.03.30 (ReadMe)
   • 3D piping package which includes Piping, Equipment, Raceways, Isometrics, & SpecGen
7. Bentley Plant Framework XM Edition - 08.09.03.72 (ReadMe)
   • Upgrade for 3d package, required for SP2 upgrade
8. Bentley Process & Instrumentation XM Edition - 08.09.03.44 (ReadMe)
9. Bentley AutoPLANT Plant Design XM Edition Service Pack 2- 08.09.03.49 (ReadMe)
   • Upgrade for 3d piping package
10. Bentley Plant Framework XM Edition - 08.09.04.47
    • Upgrade for framework for all Plant, required for ProjectWise
11. ProSteel 3D R18.0 - 08.10.00.17
    • Optional Structural software Package
12. Bentley Navigator XM Edition - 08.09.05.70
    • Optional Software

See Also

Add link to referring product TechNote entry by enclosing its topic name in brackets.

Add links to other related wiki entries.

Product TechNotes and FAQs

External Links

Add links to any helpful external resources by entering the name and using the hyperlink button to provide the URL. For instance:

Bentley homepage

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

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

To remove the valve operator orientation at specific plane in generated isometrics.

Background

Requirement is to remove Valve operator orientation tag in isometrics. Below steps describes how to remove the valve operator orientation tag under User label option provided to user to customize it as per their requirement
.

Steps to Accomplish

1. Open Bentley Project Administrator.
2. In Project Administrator browse the project in which need to edit the valve operator orientation.
3. In the given Project open the OpenPlant Isometrics configuration as per the steps mentioned in the below screenshot.
    
   
   
   
4. In Isometric Configuration, under Exclude field, enter IE_OPDIR=N|S|E|W|UP|DOWN as per the steps given in below screenshot.
   
   
   
   
5. N|S|E|W|UP|DOWN denotes the planes direction(north, south, east, west up, down) i.e if the operator lies in these mentioned planes, the operator orientation will not shown in the generated Isometrics. All other angular orientation will be shown in generated isometrics.
6. Save & close Isometric Configuration dialog box.
7. Generate the Isometrics to check/confirm for the results.
   
   
   
   
8. Noticed that the Valve operator in the downward direction is not shown in the generated Isometrics, while the operator in the angular direction is shown in the generated isometrics.

See Also

Comments or Corrections?

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

What are the prerequisites required to install OpenPlant Support Engineering?

The Desktop Prerequisite Pack v08.11.09.03 needs to be installed to your workstation prior to the installation of OpenPlant Support Engineering V8i incase internet connection is not available at time of install. The Desktop Prerequisite Pack is available from the Web Software Downloads/MySELECT CD area of SELECTservices Online.

Does it Require ProjectWise to Install? 

ProjectWise is Optional. ProjectWise is only required when connecting to OpenPlant Model Server. 

Version to Check:

• ProjectWise Server 8.11.9 with ProjectWise Explorer client 8.11.9.590, 8.11.9.574, 8.11.9.559 

What Operating Systems does it Support?

• Microsoft® Windows 7 (64 Bit)
• Microsoft® Windows 8.1 
• Microsoft® Windows 10 (64 Bit)

What are OpenPlant Support Engineering Workflows?

• OpenPlant Support Engineering can be used with referenced i-models from OpenPlant Modeler and structural tools such as ProStructures.
• OpenPlant Support Engineering can also works in conjunction with OpenPlant Model Server in a component based workflow by referencing out piping components or work breakdown structure elements in order to begin work and then checking in support components upon completion to OpenPlant Model Server. These support objects can then appear in isometrics generated from OpenPlant Isometrics Manager.

What are the Tools or Features provided by OpenPlant Support Engineering?

• Accurate placement of supports, support assemblies, and support placeholders (locators)

• Manual and automated placement algorithms

• Universal placement dashboard

• Supports and support parts from multiple vendor catalogs

• Assembly creation tools

• Automatic support drawing generation

  • Additional tools for annotation and notes.Bill of materials automatically generated.

  • Bill of materials automatically generated.

  • Drawing border can be customized with multiple views, bill of materials, notes and part callout sections.

• Flexible report generation.
• Supports for Piping, HVAC and Raceway.

A detailed explanations for all above can be found in OpenPlant Support Engineering articles. 

What are the current limitations under OpenPlant Support Engineering?

• Structural objects from Prosteel are not currently intelligently recognized by the program.  For More details refer help file. 
• Using .dgn files for interaction between the two products is currently not supported.

Is it Possible to Import Regional standard catalog for Steel Section?

• Structural steel section catalog can be imported in OpenPlant Support Engineering using Project Dashboard. For more information check Help File. 
• User may use SQLlite application to create a DB file which will further get imported inside the Project Dashboard. 

Is it Possible to Import the data available in excel file format for Steel Section?

• Yes with new SS6 release of OpenPlant Support Engineering, it is possible to import the data in excel format with an option "Catalog Loader" present in Project Dashboard.

Is it Possible to use AutoPLANT drawings?

• Yes! It support AutoPLANT.dwg. This is support from SS6 Version.

Can I get list of what's new items for SS6 release?

• Yes! you can check either in Readme file or click here>>>

See Also

OpenPlant Support Engineering                                                                                                                                        

External Links

Check Videos Content - LEARN Server

Comments or Corrections?

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

Errors/ Reading Logs/Message dialogs/Crashes

While working on modelling software, it is quite natural that some errors, crashes, warning messages may generates while referring 3D models and placement of Supports and generating various reports. In this Section, it will illustrate those errors, reading logs and other issues. 

See Also

Product TechNotes and FAQs

OpenPlant Support Engineering [FAQ]

External Links

Bentley Technical Support KnowledgeBase

Bentley LEARN Server

Comments or Corrections?

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

Overview

There might be situations when user is tryin to install AutoPLANT Modeler and while installing Prerequisites and Common Tools for AutoPLANT Applications, setup is failing to install Bentley Class Editor with error 1603.

After trying to install same Bentley Class Editor manually, a warning message about missing .NET Framework v3.5 was popping out and again failing to install Bentley Class Editor.

Unsuccessful Prerequisites installation is not allowing to install AutoPLANT Modeler.

Steps to resolve

Windows 10 Operating System does not always contain .NET Framework v3.5 enabled. Bentley Class Editor cannot be installed if the .NET Framework v3.5 is not present in the machine. AutoPLANT Modeler cannot be installed if we do not have Bentley Class Editor.

1. Search for "Turn Windows features on or of"
   
   
   
   or open Programs and Features dialog and select it from there
   
   
2. In This dialog mark .NET Framework 3.5 checkbox and click O
   
   
   
   
   
3. Then select to Download files from Windows Update
   
   
   
   
4. Windows will download and install selected .NET Framework 3.5
   
   
   
   
5. After successful NET Framework 3.5 installation you can start Prerequisites and Common Tools for AutoPLANT Applications installation again and it will add missing Bentley Class Editor. AutoPLANT Modeler will be allowed to install as well

But there might be some cases when Windows updating is disabled, users are working only in network without internet access or there are other restrictions which are not allowing to use this standard Windows Update tool.

Windows 8 and above, the .NET Framework is an operating system component and cannot be independently installed or uninstalled. If users are disabling Windows updating, then user’s actions are required to enable updating or install .NET using installation CD/DVD/ISO with the help of this command:

DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:E:\sources\sxs
(E is drive letter in which is mounted Win10 ISO)

Comments or Corrections?

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

Background

This article will explains what steps are required to associate Pipeline Tag Number with Valve Tag Number. In this article we will give relationship with RUN_HAS_IN_RUN.

Steps to Accomplish

1. Launch Class Editor.

2. Open OpenPlant PID.01.07 schema.
   
   
   

3. Supplement with OpenPlant_PID_Supplemental_Imperial.01.07.ecschema.
   
   
   
   

4. Navigate to Pipe Run class.
   
   

   
   
   

5. Switch to NUMBER Property. Add Custom Attribute.
   
   

   
   
   

6. Add Notify Related Component of Property Value Change Custom Attribute, see below image.
   
   

   
   
   

7. Fill Data as shown below.
   
   

   
   
   

8. Add Hide Property Custom Attribute on NUMBER Property, Pipe RUN Class.
   
   

   
   
   

   
   
   

9. Fill details as highlighted in below image.
   
   

   
   
   

10. Save All Settings.
    
    

Verify Result

• Launch OpenPlant PID.

• Open desired file.

• Place a Pipeline.

  
  
  

• Place a Valve on Pipeline, it should takes automatically the same Number as of Pipeline Number.
  
  

See Also

Comments & Corrections

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

Overview

To remove text wrapping issue in generated isometrics

Background

The user is facing a problem in which when he edits the BOM text, he gets the all the text aligned towards left as shown in the image below. On following the below mentioned steps the user will be able to edit the BOM text without hampering the justification.

AutoPLANT Modeler-OpenPlant Isometrics Manager

Steps to Resolve

1. Open Project Administrator, in the project, expand the OpenPlant Isometrics Manager node and select the settings option to launch Isometric Configuration dialog.
   
   
   
   
2. From the Isometric Configuration dialog, open seed file.
   
   
   
3. In seed file, open View Attributes and enable the text nodes.
   
   
   
4. Select text node 60 and delete it.
   
   
   
   
5. Select key-in browser and type NN=60 to start the node counter from 60.
   
   
   
   
6. Select the Place text node from text tasks and place at the same position as the previous text node.
   
   
   
   
7. Generate isometrics and verify results.
   
   
8. Double click on the BOM text and confirm that improper text wrapping issue does not persist. See image below.
   
   

See Also

Still a problem?

if above problem still persist, then please create a Service Request and contact the Bentley Product Advantage Group. Please include a list of all relevant details to get in depth analysis for a solution or workaround.

Comments or Corrections?

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

To change BOM text to upper case in OpenPlant Isometrics Manager.

Background

In OpenPlant Isometrics Manager, as per project requirement by user, BOM Text should display in upper case. See default BOM output. 

With current SS6 version of OpenPlant Isometrics Manager, hook.ini file provides the ability to generate BOM with Upper case. Below are the steps to describe the solution.  

OpenPlant Modeler & OpenPlant Isometrics Manager

Steps to Accomplish

1. Launch OpenPlant Isometrics Manager.
2. Select Project unit, say OPModeler_Metric here and click OK. See image below.
   
   
   
   
3. Click on Configuration Icon to launch Isometric configuration dialog box.
   
   
   
   
4. From Isometric configuration dialog box, select Advanced node and click on Explore Style option to allow user to navigate to the style folder.
   
   
   
   
5. Select As-Built folder and open hook.ini file in notepad or Notepad++. 
   
   
   
   
6. Check for variable under [0100] & remove ; sign to enable this expression. 
   
   
   
   
7. After removing the color of this line would turn to black. See image below. 
   
   
   
   
8. Save & Close Schema.
9. In style folder create a file as hook.bat& add below expression to it.
   
   [0100]
   
   RUN = $(IE_CONF)hook100.bat
   
   powershell -Command "(Get-content -Path '%L00FILE%').ToUpper() | Out-File '%L00FILE%' -encoding 'UTF8'"
   
   
   
   
10. Save & close file.
11. Generate Isometrics & verify results. See image below. 
    
    

Still a Problem?

If above problem still persist, then please create a Service Request and contact the Bentley Product Advantage group.  Please include a list of all relevant details to get in depth analysis for a solution or workaround. 

See Also

Comments or Corrections?

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