Document Assumptions - Intergraph Smart 3D - Installation & Upgrade

Intergraph Smart 3D Upgrading from 2019 to 14 Update 1
Language
English
Product
Intergraph Smart 3D
Subproduct
Upgrade Guide
Search by Category
Installation & Upgrade
Smart 3D Version
12.1 (2019)

The upgrade procedures described in this document are based on these assumptions:

  1. The Smart 3D configuration and associated files you intend to upgrade to 14 Update 1 must already be upgraded to 2019 release. Smart 3D does not support upgrading directly from releases prior to 2018.

  2. The Smart 3D configuration and associated files you intend to upgrade must be updated with the latest Hot Fix installed. If you are unsure whether you have installed the latest Hot Fix, please check with your Hexagon Support representative.

  3. All customized files on the SharedContent (Symbols) share must have different names than the delivered files they were based on. If the files have not been renamed, they are overwritten and your customizations are lost after the upgrade process is completed. If the file containing your customizations is required to retain the same name as the delivered file on which it was based, contact your Hexagon support representative for assistance on how to upgrade these files. It is recommended that all custom content be kept in a separate folder.

  4. For Smart 3D configurations in an integrated environment:

    1. SmartPlant Foundation databases must be upgraded/migrated to version 10.0 before upgrading the databases to 14 Update 1.

    2. HxGN SDx databases must be upgraded to Update 52 or greater to support the future upgrade to Clipper, which is the supported platform for 14 Update 1. Please note that registration to SDx is not supported for 14 Update 1 Oracle databases, and the upgrade of Change Management models used for project as-built workflows are not supported in 14 Update 1.

  5. All reference files (DGN, DWG, R3D, and so forth) are accessible by the user account performing the upgrade.

  6. The user account performing the upgrade procedure must have the respective Windows-based permissions to successfully carry out file operation in the file system.

  7. The user account performing the upgrade procedure must have administrative rights to either MSSQL or Oracle production databases to successfully carry out the upgrade process that require database write access.

  8. Because the upgrade process is a time-consuming procedure, we recommend that you schedule upgrading after hours or during non-working hours. During this period, all activity on the project being upgraded must be halted until the process is completed.