| Applies To | |||
| Product(s): | Bentley OpenPlant Modeler | ||
| Version(s): | 08.11.09.404 | ||
| Environment: | N/A | ||
| Area: | Schema | ||
| Subarea: | |||
| Original Author: | Joey Bertone, Bentley Technical Support Group |
Background
This document will focus only on the migration for out of the box or default set of schemas. For the customizations done by the user, they will need to review and apply the changes to the schemas of the new version.
The user customization typically involves one or more of the following things:
- Addition or deletion of new class/classes in the OpenPlant 3D schema (OpenPlant_3D.01.04.ecschema.xml file). Typically we don’t delete classes from 3D schema.
- Addition or deletion of new properties in one or more classes in the OpenPlant 3D schema.
- Addition or deletion of custom attributes in one or more classes in the OpenPlant 3D schema.
When moving from 383 to 404, to support the above changes, user also needs to modify following set of schemas
- OpenPlant_3D_Supplemental_Modeling.01.04.ecschema
- OpenPlant_3D_Supplemental_ModelingViews.01.04.ecschema
- OpenPlant_Supplemental_Tagging.01.04.ecschema
- OpenPlant_Supplemental_Units_Imperial.01.04.ecschema
- OpenPlant_3D_Supplemental_Model_Server.01.04.ecschema
- OpenPlant_3D_ProjectProperties.01.02.ecschema
Starting with the delivered set of schemas (project and common) for the SS5 Refresh 383 version, identify the scope of changes to the out of the box schemas. For example, when if a user did some customizations to the out of the box SS5 Refresh 383 versions, those changes should have been noted. Now he should apply similar customizations should be done by him to SS5 Refresh 404 version.
The changes done to the default SS5 Refresh 383 schemas can be reviewed by comparing the 2 set of schemas using Bentley Class Editor. The Bentley Class Editor is an optional install from the OpenPlant Modeler installation. Run a repair or change install of OpenPlant to install Bentley Class Editor
Once the changes to the out of the box schemas (SS5 Refresh 383) have been noted, the same set of changes should be applied to the SS5 Refresh 404 out of the box schemas using Bentley Class Editor to create the SS5 Refresh 404 customized schemas.
This is a 3 step process using Bentley Class Editor:
- Identify applied customizations to the SS5 Refresh 383 set of delivered/out of the box schemas, ignore this if you already know the changes.
- Identify the differences between SS5 Refresh 383 and SS5 Refresh 404 out of the box environments.
- Compare the ‘SS5 Refresh 383 customized’ and ‘SS5 Refresh 404 customized’, review and commit changes.
Steps to Accomplish
Use Bentley Class Editor to compare schemas and apply changes
Bentley Class Editor can be launched from Start > All Programs > Bentley > Bentley Class Editor V8i 08.26 > Bentley Class Editor V8i 08.26
Before using the Bentley Class Editor for the above purpose, we need to know one limitation and its workaround for using it successfully. The project schema (OpenPlant_3D.01.04.ecschema) version in SS5 278, SS5R 383 and SS5R 404 is the same which is 01.04 and Class Editor does not allow comparing schemas with the same version. To get past this we need to change the schema version for the purpose of comparison.
- Using a text editor tool (Notepad ++ or some other), open the SS5 Refresh 383 OpenPlant 3D schema
- Change the version from1.4 to 1.3 and also display Label from OpenPlant3D.01.04 to OpenPlant3D.01.03 and save the changes.
- Close the file and rename it from OpenPlant_3D.01.04.ecschema to OpenPlant_3D.01.03.ecschema.
Now we can proceed to schema differencing.
- Launch Bentley Class Editor, File > Open the SS5 Refresh 383 OpenPlant 3D schema (OpenPlant_3D.01.03.ecschema)
- This prompts for the Bentley Base schema so select the corresponding SS5 Refresh 383 Bentley Base schema (available in the common schemas folder).
- From Tools menu, select the Schema Differencing option. In the Schema Differencing dialog, from the Target Schema drop down, select the Browse option and then select the SS5R 404 OpenPlant 3D schema (OpenPlant_3D.01.04.ecschema).
- This prompts for the Bentley Base schema so select the corresponding SS5R 404 Bentley Base schema (available in the common schemas folder).
- After a few seconds the Compare button on the Schema Differencing dialog is enabled, hit it.
- After few seconds of processing this will show the differences as below, select the Display > Differences option to review the changes.
- Expand the check box on classes, review the properties, select the required changes and then hit the Commit option on this dialog.
- Once all the changes are committed, the process is complete.
It would also be required to review and apply the changes to other schemas than the OpenPlant 3D schema if during the user customization, the user has done changes to other schemas listed above. However, the procedure for that should be the same.
Known Issues
If any changes are made to existing supports, olets, notes or fasteners after updating after updating from SS5 383 to SS5 404 then the following commands will need to be run. if the following key-ins are not run then this will result in one or more of the following: failure to create iso sheets, failure to publish i-models, failure to generate isometrics drawings and generation of incorrect isometric drawings.
Supports
If you have supports modeled in your dgn files using OPM 383, and then if you open the dgn file in OPM 404 and perform move/manipulation operations, you will need to run the following key-in to update reference coordinate points for the support components:
mechaddin migrateSupports
If you have supports modeled in your dgn files using OPM 383, and then if you open the dgn file in OPM 404 and if you specifically move the support such that it is now associated with another pipe, you will need to run the following key-in to update association for the support with the pipe:
mechaddin fixsupportassociations
If this key-in is not run (needed only after moving support to another pipe done using OPM 404) and user tries to create iso-sheet, publish i-model and then generate isometrics, it will be generated incorrectly, and the support will still be associated with the previous pipe.
Olets
If you have olets in your dgn files using OPM 383, and then if you open the dgn file in OPM 404 and perform move/manipulation operations, you will need to run the following key-in to update reference coordinate points for the olet components:
mechaddin migratetapconnections
Notes
If you have Notes in your dgn files using OPM 383, and then if you open the dgn file in OPM 404 and perform move/manipulation operations, you will need to run the following key-in to update reference coordinate points for the notes components:
mechaddin migratenotes
If these respective key-ins are not run (needed only after move/manipulation done using OPM 404) and user tries to create iso-sheet, publish i-model and then generate isometrics, it will fail.
Fasteners
If you have components modeled and an iso-sheet has been created out of them in OPM 383 and then you migrate to OPM 404 and then add/edit/delete/modify components in such a way that new fasteners are created by deleting old fasteners, then you will need to run the following key-in to update association of fasteners with the already existing iso-sheet:
mechaddin fixisosheetfastenerassociation
If this key-in is not run (needed only in case of new creation of fasteners) then the isometrics generation will fail.