Professional Documents
Culture Documents
May 2012
DSP3D-PE-200078E
Copyright
Copyright 1999-2012 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains
confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and
international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.
Portions of this software are owned by Spatial Corp. 1986-2012. All Rights Reserved.
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the
licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license
for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this
software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee
permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and
delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or
redistribution.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Convert, I-Export, I-Sketch, SmartMarine, IntelliShip, INtools,
ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of
Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered
trademarks of Microsoft Corporation. ACIS is a registered trademark of SPATIAL TECHNOLOGY, INC. Infragistics, Presentation
Layer Framework, ActiveTreeView Ctrl, ProtoViewCtl, ActiveThreed Ctrl, ActiveListBar Ctrl, ActiveSplitter, ActiveToolbars Ctrl,
ActiveToolbars Plus Ctrl, and ProtoView are trademarks of Infragistics, Inc. Incorporates portions of 2D DCM, 3D DCM, and HLM by
Siemens Product Lifecycle Management Software III (GB) Ltd. All rights reserved. Gigasoft is a registered trademark, and
ProEssentials a trademark of Gigasoft, Inc. VideoSoft and VXFlexGrid are either registered trademarks or trademarks of
ComponentOne LLC 1991-2012, All rights reserved. Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of
Oracle Corporation and/or its affiliates. Tribon is a trademark of AVEVA Group plc. Alma and act/cut are trademarks of the Alma
company. Other brands and product names are trademarks of their respective owners.
Contents
Contents ..............................................................................................................................3
Preface .................................................................................................................................5
Introduction ........................................................................................................................6
Upgrade Overview ........................................................................................................6
Upgrade Cases ..............................................................................................................7
Document Assumptions ................................................................................................9
Preface
This document provides guidelines for upgrading SmartMarine 3D (SM3D)
version 2009.1 or version 2011 Service Pack 1 (SP1) Marine configurations (models,
catalogs and supporting files) to version 2011 R1 Marine configurations.
SmartMarine 3D 2011 R1 supports upgrade from the following versions:
Version 2009.1
Version 2011 SP1
Since most of the steps to upgrade are the same regardless of which version is being
upgraded, the document refers to the versions being upgraded as version 2009.1 or
version 2011 SP1. Where there are differences, the document will clearly state the
version to which the special instructions apply.
Note
All Marine configurations from earlier versions need to be upgraded to
version 2009.1 or version 2011 SP1. Please see the appropriate SM3D
Upgrade Guide, delivered with the corresponding version 2009.1 or version
2011 SP1 software, for upgrading to one of these versions.
Steps are also included to upgrade Marine configurations that are in a SmartPlant
Enterprise integrated environment, as well as those in a Global Workshare
configuration.
Important
For Global Workshare configurations, upgrade from version 2009.1 to
version 2011 SP1 requires a consolidation of databases. Steps to
upgrade Marine configurations in a workshare environment have been
incorporated into this document.
For Global Workshare configurations (GWC), upgrade from version
2011 SP1 to SmartMarine 3D 2011 R1 does not require a
consolidation of databases. Steps to upgrade Marine configurations in
a workshare environment have been incorporated into this document.
Because SmartMarine 3D registration information was not upgraded in
SmartPlant Foundation 4.x, SmartMarine 3D must re-register with
SmartPlant Foundation after upgrading to SmartPlant Foundation 4.x.
For a definition of terms used in this guide, refer to the Glossary section in the
Common Users Guide, available with the Help > Printable Guides command in the
software or with the Help command in the Common task.
Send documentation comments or suggestions to PPMdoc@intergraph.com.
Introduction
Upgrading is the process of converting an existing model, with all its associated files
and databases, from compatibility with an older version of SmartMarine 3D (SM3D)
to compatibility with the next sequential version of the software. The databases you
must upgrade include the Site, Site schema, Catalog, Catalog schema and Model
databases. The associated files you must upgrade are those that are located in the
SharedContent (Symbols) share. This set of databases (plus the Reports and Reports
schema databases) and files are collectively referred to as the Marine configuration.
Upgrade Overview
Important
SmartMarine 3D 2011 R1 supports upgrade from version 2009.1 and
version 2011 SP1. For convenience, this document refers to the
versions being upgraded as version 2009.1 or version 2011 SP1
unless there are steps that apply to only one version.
For Global Workshare configurations, upgrade from version 2009.1 to
version 2011 R1 requires a consolidation of databases. Steps to
upgrade Marine configurations in a workshare environment have been
incorporated into this document.
For Global Workshare configurations (GWC), upgrade from version
2011 SP1 to SmartMarine 3D 2011 R1 does not require a
consolidation of databases. Steps to upgrade Marine configurations in
a workshare environment have been incorporated into this document.
There are six major steps in upgrading SM3D data from version 2009.1 or version
2011 SP1 to version 2011 R1.
Step 1. Prepare for the Upgrade This step includes backing up your data,
determining the integrity of the databases, and cleaning up the databases as
needed. The databases must be in as clean a state as possible prior to upgrading so
that errors will be minimized during the process. For more information, see
Preparing for the Upgrade, page 10.
Step 2. Upgrade your files in the SharedContnet (Symbols) share This process
is a set of manual procedures. For more information, see Upgrading the
SharedContent (Symbols) Share, page 18.
Note
SmartMarine 3D 2011 SP1 and later allow custom DLLs to be used without
registering them. For more information, see Upgrading Custom Symbols and
Naming Rules, page 24.
Upgrade Cases
Upgrading from version 2009.1, the platform requirements have changed for servers
and clients for version 2011 R1. Therefore, users must backup the version 2009.1
Marine configuration and restore it using a client/server configuration that has the
new platform requirements for version 2011 R1. Upgrading from version 2011 SP1,
the platform requirements are similar and do not require client/server configuration
changes. The same basic workflow will apply for each Case listed below: In the
course of describing the details of each major step, this document will take into
consideration four possible upgrade scenarios, or cases, each requiring a slightly
different workflow. Before beginning the upgrade process, select the case that applies
to your situation and follow the workflow for that case where applicable.
Case A. In-place upgrade of entire version 2009.1 or version 2011 SP1 site to
version 2011 R1 on one server.
This case assumes a full transition of the Site and all of its Models from version
2009.1 or version 2011 SP1 to version 2011 R1 on the same server. Due to the
platform requirement changes in version 2011 R1 from version 2009.1, the server and
client have to be updated to the new platform requirements before upgrading to
version 2011 R1. However, the platform requirements should not be updated until the
steps in the Preparing for Upgrade section of this document are completed. Then,
version 2011 R1 software should be installed on the server and client and all
databases upgraded in-place.
Note
Case A is the only case where upgrade in a GWC is reasonable and
supported.
Case B. Moving (relocating) databases and upgrading them on another
server.
This should be the most common procedure used for version 2009.1 to 2011 R1
upgrades due to platform requirement changes. This is for cases where all Models and
Catalogs associated with the Site are moved from one server, restored on another
server and upgraded. Or when some of the Models are moved to another server and
upgraded while others in the Site remain on version 2009.1 or version 2011 SP1 on
the original server. When Marine configurations from one Site are relocated and
upgraded to another server, the SharedContent (Symbols) folder must also be copied
and upgraded to the new server or location.
Case C. Restoring archived databases and upgrading them with only version
2011 R1 software.
This case deals with archived backups of version 2009.1 or version 2011 SP1 Marine
configurations that are restored in a location where version 2009.1 or version 2011
SP1 is not available. In addition to the full database backup, a corresponding backup
of the SharedContent (Symbols) folder is required.
Case D. Coexistence of version 2009.1 or version 2011 SP1 and 2011 R1
Marine configurations on one server.
This is the most complex case. In general for version 2009.1 Marine configurations,
there can be several Sites on one server, each compatible with a different version of
SM3D. In these cases, all Catalog and Model databases within one SM3D Site must
be in the same SM3D version. SM3D does not support different versions of Catalogs
and Models within one Site database. For version 2011 SP1 or version 2011 R1
Marine configurations, since version 2011 has new platform requirements different
than version 2009.1, all Sites on one server cannot have version 2009.1 Sites as well
as version 2011 SP1 or version 2011 R1. Version 2009.1 does not support the new
version 2011 platform software requirements. Therefore this Case D does not apply to
upgrading to version 2011 R1 from version 2009.1, and either Case A, B, or C will be
applied for all version 2011 R1 from version 2009.1 upgrades.
Notes
If multiple version 2009.1 Marine configurations are replicated in Case
D and just one (or some of them) needs to be upgraded, you must
consolidate the databases being upgraded and transfer them
(backup/restore) to the new Host server which has new platform
software requirements. Once the upgrade process is completed, the
Marine configurations can be reconfigured to a Global Workshare
environment.
If multiple version 2011 SP1 Marine configurations are replicated in
Case D and just one (or some of them) needs to be upgraded, it is
Document Assumptions
The procedures described in this document are based on these assumptions:
1. The Marine configuration and associated files you intend to upgrade to 2011 R1
must already be upgraded to version 2009.1 or version 2011 SP1. SM3D does not
support upgrading directly from versions prior to 2009.1.
2. The Marine configuration and associated files you intend to upgrade must be
updated with the latest Hot Fix. If you are unsure whether you have installed
the latest Hot Fix, please check with your Intergraph support representative.
3. The necessary changes described in the Catalog Data workbooks delivered with
version 2009.1 and version 2011 SP1 have been implemented in your workbooks
and bulkloaded to the respective version 2009.1 or version 2011 SP1 Catalog
database.
4. 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 will be overwritten and your customizations lost after the
upgrade process is complete. If the file containing your customizations is required
to retain the same name as the delivered file on which it was based, contact your
Intergraph support representative for assistance on how to upgrade these files.
Note
This only applies to users that decide to use Option 2 when upgrading
their SharedContent (Symbols) share, see Upgrading Custom Symbols and
Naming Rules, page 24 of this document, this step is not needed if Option
1 is used..
5. For Marine configurations in an integrated environment, SmartPlant Foundation
databases will need to be upgraded to version 3.8.8, 4.2.0, 4.2.1, 4.3.1 or 4.3.2
before upgrading the SM3D databases to 2011 R1.
6. All reference files are accessible by the user account performing the upgrade.
Important
Intergraph PPM recommends that you do not create the SharedContent
(Symbols) folder under the product folder. Please copy the
SharedContent folder and move it to another location to be shared.
For more information on upgrading the SharedContent (Symbols)
folder in 2011 SP1 see, Upgrading the SharedContent (Symbols)
Share, page 18.
Case A
1. For version 2009.1 upgrades, using a version 2009.1 workstation with Project
Management installed, restore the Site and the Marine configurations to the
server.
2. For version 2011 SP1 upgrades, the databases should still be located on the server
and there is no need to restore.
Important
Use the Restore command in the Project Management task to restore
the Model(s) if they will keep their original names.
Use the Restore as Copy command in the Project Management task to
restore the Model(s) if one or more Models need to be renamed.
Notes
Using the Restore as Copy mode will remove the registration with an
integrated environment for the new model.
For assistance with the Restore and Restore as Copy commands,
refer to the Backing Up and Restoring Data section in the Project
Management Users Guide, available with the Help > Printable
Guides command in the software.
Case B
1. Using a version 2009.1 or version 2011 SP1 workstation with Project
Management installed, restore the Site and the Marine configurations to the new
server.
Important
Use the Restore command in the Project Management task to restore
the Model(s) if they will keep their original names.
Use the Restore as Copy command in the Project Management task to
restore the Model(s) if one or more Models need to be renamed.
Notes
Using the Restore as Copy mode will remove the registration with an
integrated environment for the new model.
For assistance with the Restore and Restore as Copy commands,
refer to the Backing Up and Restoring Data section in the Project
Case C
1. Using a version 2011 R1 workstation with Project Management installed, restore
the Site configuration to the new server.
Notes
For assistance with the Restore command, refer to the Backing Up and
Restoring Data section in the Project Management Users Guide,
available with the Help > Printable Guides command in the software.
The Restore As Copy command works only when restoring a backup
made with the same version of the software used for restoring. If you
need to rename the Models or the Catalog after the upgrade is
completed, the Model can be Restored as Copy with the new name
from a backup of the upgraded Marine configuration.
Case D
1. Using a version 2011 SP1 workstation with Project Management installed, either
restore the Site from backup with a new name if the upgraded Model(s) and
Catalog will keep the original name, or create a new Site if you intend to use the
Restore as Copy command.
Note
For assistance with the Restore and Restore as Copy commands,
refer to the Backing Up and Restoring Data section in the Project
Management Users Guide, available with the Help > Printable
Guides command in the software.
2. Using a version 2011 SP1 workstation with Project Management installed, restore
the Model(s).
Important
Use the Restore command to restore the Model(s) to the restored Site
if they will keep their original names after ensuring that they are
already deleted from the original Site.
Use the Restore as Copy command to restore the Model(s) if one of
these two situations apply:
1. One or more Models need to be renamed.
2. The Catalog must be copied and renamed because it is shared by a
Model which is not upgraded.
Important
Delivered files in this folder cannot be renamed, however, their
contents can be modified. Any customizations made to these files can
be copied back into the 2011 R1 files.
SharedContent\Data contains bitmaps referenced by Hangers and Supports,
custom schema and mapping files for Reference 3D, and mapping files for
Translators.
SharedContent\Drawings catalog location for the Drawings and Reports
environment.
SharedContent\DrawingsWrappers contains additional catalog files for the
Drawings and Reports environment.
SharedContent\EdgeFeatures - contains Symbol2D generated edge features for
detailed plate systems and profile systems
SharedContent\FlangeContours - contains Symbol2D generated flange contours
for bracket plate systems with flange as reinfrorcement
SharedContent\FlangeCuts - contains Symbol2D generated flange cuts for
detailed profile systems
SharedContent\HangersAndSupports contains Symbol2D files referenced by
Hangers and Supports.
SharedContent\HoleMgmt - contains Symbol2D generated hole cuts
SharedContent\Labels catalog location for labels.
SharedContent\MarineLibrary - contains Symbol2D generated symbols and
display bitmaps specific to the new marine library
SharedContent\NozzleOrientations contains bitmaps used to display nozzle
properties.
SharedContent\Openings contains bitmaps and Symbol2D generated cross-
section for Structures opening command.
SharedContent\Penetrations - contains Symbol2D generated slots for detailed
plate systems penetrated by profile systems
SharedContent\PmfgIsoStyleData catalog information for the various styles
used to create piping isometric drawings.
SharedContent\Profile Xsections - contains Symbol2D generated cross sections
for profile systems placed in Molded forms
SharedContent\Reports catalog location for reports.
SharedContent\ShapeTypes contains bitmaps and xml definition of Shapes.
SharedContent\ShipDrawings - contains Symbol2D generated symbols used in
marine drawings
SharedContent\Sketched Features - contains Symbol2D generated sketched
features for detailed profile systems
SharedContent\SmartPlantStructure additional bitmaps referenced by Structure.
SharedContent\SolidEdgeParts contains Solid Edge par and asm files for
Equipment.
SharedContent\StructManufacturing - contains Symbol2D generated symbols for
manufactured parts, profiles and members
SharedContent\SymbolIcons contains bitmaps referenced by route.
later in the upgrade process. If the version 2009.1 or version 2011 SP1 files are
overwritten with the 2011 R1 files, the upgrade will fail for Marine
configurations in an integrated environment. This is the reason for renaming
the folder. See Appendix I: Upgrading Your Tool Schema, page 42.
5. Copy the contents of the delivered 2011 R1 SharedContent (Symbols) share over
your Models version 2009.1 Symbols or version 2011 SP1 SharedContent
(Symbols) share. DO overwrite files with the same name, after ensuring you
have renamed the version 2009.1 or version 2011 SP1 SharedContent
(Symbols) files that you have customized.
Note
The SharedContent (Symbols) folder cannot be shared by Models
using different versions of SM3D. Therefore, the upgraded Marine
configuration must use its own copy of the SharedContent (Symbols)
folder, while the original Symbols or SharedContent folder stays in
version 2009.1 or version 2011 SP1.
6. Sign Assemblies
Intergraph Process, Power & Marine signs all delivered .NET assemblies with a
strong name. Signing an assembly is a way to guarantee the authenticity of an
assembly. If you create your own custom .NET assemblies, we recommend that
you sign them with your company's private key. Refer to Visual Studio help for
information on signing an assembly.
7. Grant Trust to Client Computers
To utilize .NET based commands, symbols or rules, your administrator must
apply the required security setting in order to enable .NET code from Shared
Content (Symbols) to be trusted. This is required because by default in .NET all
code from a network location is untrusted. If adding trust is not done, you will
receive the following error message when running a .NET command: "Not able
to get the ThirdParty Plugin from the Catalog Rule or Default Rule". In addition,
you will not be able to place objects using .NET symbols in the model. This is
also required before Bulkloading .NET symbols, as doing so may put existing
objects in the To Do List. You must set each computer that uses the signed
assemblies trust access to the assemblies. The most convienent way to do this is
to generate an msi file on one client machine and distribute the permissions to
each client computer. You will need the .NET Framework 2.0 Configuration
utility, which is available in the .NET Software Development Kit. You can also
search the Microsoft web site for "configwizard.msi download".
1. Install the .NET Framework 2.0 Configuration utility on a client computer.
2. Select Start > Control Panel > System and Security > Administrative
Tools > Microsoft .NET Framework 2.0 Configuration.
3. In the Console Root tree, expand .NET Framework 2.0 Configuration >
My Computer > Runtime Security Policy > Machine > Code Groups >
All_Code > LocalIntranet _Zone.
4. Under Tasks, click Add a Child Code Group.
5. Select Create a new code group.
6. In the Name box, type Delivered Smart 3D Content
7. Click Next.
8. In the Choose the condition type for this code group, select Strong
Name.
9. Click Import.
10. Browse to and select one of the signed assemblies.
Important
You need to select one of the Intergraph Process, Power & Marine signed
assemblies from the shared content folder. All Intergraph Process, Power
& Marine assemblies are signed with the same key, so it does not matter
which assembly you select. You can also select from the product location,
eg
[Smart3DWorkstationInstallationDirectory]\Core\Container\Bin\Assembli
es\Release\CommonMiddle.dll.
The public key displays.
11. Clear the Name check box.
12. Clear the Version check box.
Note
By clearing the Name and Version check boxes, the computer trusts all
assemblies that were signed with the same strong name key.
13. Click Next.
14. Select FullTrust from Use existing permission set.
15. Click Next.
16. Click Finish.
17. Right-click Runtime Security Policy, and then select Create
Deployment Package.
18. Select Machine.
19. Specify the file name and folder location for the .msi file.
20. Click Next.
21. Click Finish. This should generate the msi file with the given name in the
specified folder.
22. Distribute the .msi file to each client. You can do this using the Remote
Installation approach allowed by Microsoft.
Important
After you do this procedure for the Intergraph Process, Power & Marine
assemblies, you need to repeat the steps for the custom assemblies that
you have created and signed.
Command Line Alternative
If you wish to do it in an alternative manner, instead of creating and distributing
msi files, you can run a command line executable to grant the client computer
access to the assemblies on the shared content share. You must run the following
executable as an administrator from a command-line window on each client
computer:
"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe" -pp off -
machine -addgroup LocalIntranet_Zone -url \\server\share\* FullTrust -name
"SharedContent Share"
where \\server\share is the computer name and share name for the SharedContent
share.
Important
You must rerun this command line each time a .NET assembly is added to
the share.
The above process should be run on all client machines that need to utilize
.NET symbols.
In order for Remote IFC to utilize .Net symbols, the above process should
be run on all Remote IFC Server machines.
8. Copy the Structure subfolder, SystemSymbolConfig.XML,
MapClassIdToLevelDiscipline.txt, OptimizationForRole Marine Sample.xml,
and OptimizationForRole Plant Sample.xml files from the newer XML folder
and overwrite the files in the version 2009.1 or version 2011 SP1 XML folder
renamed in the previous step. Remove the newer XML folder and rename the
version 2009.1 or version 2011 SP1 XML folder back to XML.
9. For Marine configurations in an integrated environment, ensure that the files in
the SharedContent\Xml folder are not Read-only.
DesignBasisSchema subfolder
EFUpdateCache subfolder
Designbasis_map.xml
Designbasis.xml
ExemptCorrelateClasses.xml
P3DComponent.xml
SP3DPublishMap.xml
SPItoSP3DPortMapping.xml
10. If you have customized any files on the SharedContent (Symbols) share (for
example, report template files, etc.) that were based on a delivered template file,
you may need to modify this file to incorporate Intergraphs fixes and
enhancements. Refer to Appendix II, starting on page 43. If so, do one of the
following:
1. Implement Intergraphs 2011 R1 changes into your version 2009.1 or
version 2011 SP1 customized file.
OR
2. Repeat the customizations you made in version 2009.1 or version 2011
SP1 in the new 2011 R1 file.
11. See Appendix III, starting on page 45, for a list of symbol files that have version
number changes that may require additional action to update existing occurrences
in the model.
Note
For Global Workshare configurations, make sure any template file
changes are incorporated into each sites SharedContent (Symbols)
share.
Note
Custom COM components (for symbols or naming rules) written in
Visual C++ should not be placed on symbol share in 2011 R1.
Option 1: Move Custom DLLs to SharedContent Directory
For more information and steps on how to manage and move Custom DLLs to the
SharedContent directory , refer to the 2011 R1 Project Management Users Guide,
available with the Help > Printable Guides command in the software.
Or
The same information is also in each [Discipline name] 3D Symbols Reference
document, available with the Help > Printable Guides command in the software.
Option 2: Continue to Use the Custom DLLs as They Are
With this option the custom DLLs can be used as they are used in Version 2007 (7.x)
and earlier. This means that the custom DLLs will be registered on each client
software installation. Some of the custom DLLs may have to be recompiled on the
Version 2011 (9.0) platform. If you select this option, then there is no impact except
the recompilation impact in some cases. Recompiled DLLs must be distributed to
each client machine.
Note
The steps below are only necessary if you need to incorporate new
line styles included in the delivered file that are not included in
your customized Styles.sha.
3. Open your customized Styles.sha file.
4. Select the Format > Style menu item. The Style form appears.
5. On the Style form, select Resources.
6. Select the Add button on the Style Resources form.
7. On the Add form, browse to the delivered Styles.sha file that you renamed and
select OK.
8. Select OK on the Style Resources form.
9. Select Apply then Close on the Style form.
10. Place a line using one of the new line styles included with the delivered file. This
will permanently copy the new line style to your customized Styles.sha file.
11. Delete the line.
12. Repeat the previous two steps for each line style you want to add to your
customized Styles.sha.
13. Save and exit the customized Styles.sha file.
Note
All custom symbols have to be located in the ..\SharedContent\Custom
Symbols folder and have to be unregistered on the system running the
Update Custom Symbol Configuration command.
4. For Marine configurations in an integrated environment, run the Generate Design
Basis command from the 2011 R1 client workstation that includes the Project
Management component.
Note
For assistance with this step, refer to the Generate the Design Basis
section in the 2011 R1 Project Management Users Guide. You can
access this guide using the Help > Printable Guides command in the
software.
5. Using the 2011 R1 client workstation that includes the Project Management
component, upgrade the Model database.
Note
For assistance with this step, refer to the Upgrade the Ship (Model
Database) section in the 2011 R1 Project Management Users Guide.
You can access this guide using the Help > Printable Guides
command in the software.
Case C
1. Using the 2011 R1 client workstation that includes the Project Management
component, upgrade the Site and Site Schema databases.
Note
For assistance with this step, refer to the Upgrade the Site and Site
Schema Databases section in the 2011 R1 Project Management Users
Guide. You can access this guide using the Help > Printable Guides
command in the software.
2. Using the 2011 R1 client workstation, restore the Model with Catalog in the
upgraded Site on the new server.
Note
For assistance with the Restore command, refer to the Backing Up and
Restoring Data section in the 2011 R1 Project Management Users
Guide, available with the Help > Printable Guides command in the
software.
3. Using the 2011 R1 client workstation that includes the Project Management
component, upgrade the Catalog and Catalog schema databases.
Note
For assistance with this step, refer to the Upgrade the Catalog and
Catalog Schema Databases section in the 2009.1 Project Management
Users Guide, available with the Help > Printable Guides command
in the software.
4. Using the 2011 R1 client workstation that includes the Project Management
environment, run the Tools > Update Custom Symbol Configuration command.
This command creates or updates a file called CustomSymbolConfig.xml under
the ..\SharedContent\Xml folder. After the file CustomSymbolConfig.xml is
created, SmartMarine 3D will use the custom DLLs from
..\SharedContent\Custom Symbols folder.
Note
All custom symbols have to be located in the ..\SharedContent\Custom
Symbols folder and have to be unregistered on the system running the
Update Custom Symbol Configuration command.
5. For Marine configurations in an integrated environment, run the Generate Design
Basis command on the 2011 R1 client workstation that includes the Project
Management component.
Note
For assistance with this step, refer to the Generate Design Basis
Command section in the 2011 R1 Project Management Users Guide.
You can access this guide using the Help > Printable Guides
command in the software.
6. Using the 2011 R1 client workstation on which the Project Management
component is installed, upgrade the Model database.
Note
For assistance with this step, refer to the Upgrade the Model Database
section in the 2011 R1 Project Management Users Guide, available
with the Help > Printable Guides command in the software.
Note
For assistance with this step, refer to the section Consolidate Ship from
Workshare section in the 2009.1 Global Workshare Users Guide,
available with the Help > Printable Guides command in the software.
2. After consolidation, check that all permission groups belong to the Host location.
Then follow the steps detailed in the Non-Global Workshare Configuration, page
27.
3. After all upgrade steps in Non-Global Workshare Configuration section have
been completed, the databases can be replicated again if desired.
Notes
For assistance with this step, refer to the section Consolidate Ship from
Workshare section in the 2011 R1 Global Workshare Users Guide,
available with the Help > Printable Guides command in the software.
All Cases A, B, C, and D for version 2011 SP1 to verison 2011 R1 upgrades
Notes
For Global Workshare configurations, upgrading from version 2011
SP1 to SmartMarine 3D 2011 R1 does NOT require a consolidation of
databases, but it is an option to do so. Continue to the next step.
If upgrade in a non-consolidated state is required then follow the next
section Global Workshare Configuration (Non-Consolidated).
See the 2011 R1 Global Workshare Guide for more detailed
instruction.
1. At the Host location, use the version 2011 SP1 client workstation that includes the
Project Management component to consolidate the Plant configuration.
Note
For assistance with this step, refer to the section Consolidate Plant
from Workshare section in the 2011 SP1 Global Workshare Users
Guide, available with the Help > Printable Guides command in the
software.
2. After consolidation, check that all permission groups belong to the Host location.
Then follow the steps detailed in the Non-Global Workshare Configuration, page
27.
Notes
For assistance with this step, refer to the section Consolidate Plant
from Workshare section in the 2011 SP1 Global Workshare Users
Guide (SQL Server) or Global Workshare Users Guide (Oracle),
available with the Help > Printable Guides command in the software.
views by executing all of the scripts and views detailed in the upgrade
ModelDBName_ReadMe.txt file.
a. Script information is recorded in the upgrade
ModelDBName_ReadMe.txt file.
b. Scripts and upgrade ModelDBName_ReadMe.txt file are created in
the C:\Temp\SatelliteMigration folder.
Steps to execute script(s):
1. Run the individual Satellite_Instance
name_ModelDBNameMigration_X.bat file on the corresponding
Satellite location.
Notes
X is the location Id of the satellite. Based on the number of
satellites, the respective number of .bat files will be created.
For non-trusted satellites, the respective .bat file and the sql
file need to be copied to the satellite location and be executed
manually.
2. Repeat the above step for each Satellite location.
3. Run all the AddToPublications_.bat file(s) on the corresponding
Satellite location.
4. Repeat the above step for each Satellite location.
5. Ensure that all data is replicated between the Host and Satellite(s)
before performing the next view generation step.
6. Regenerate the Model views with Catalog Schema on each
Satellite using the View Generator. The View Generator
executable, ViewGenerator.exe, is delivered in the [Product
Folder]\Core\Tools\Administrator\Bin folder.
Note
To run ViewGenerator on the Model Database, select the Model
database as the Data Database and select the Catalog Schema database
as the Schema Database.
Overview
In SmartMarine 3D 2011 R1, numerous changes have been made to the reference
data. These changes, which include enhancements as well as fixes to the data or
software, are incorporated into the reference data workbooks delivered with the
product. The changes are also reflected in the database seed templates provided by
Intergraph.
Notes
The reference data workbooks can be found in the folder [Product
Folder]\CatalogData\Bulkload\Datafiles and [Product
Folder]\ShipCatalogData\Bulkload\Datafiles.
For more information about the reference data delivered with the
software, refer to the Understanding Reference Data section in the
2011 R1 SmartMarine 3D Reference Data Guide, available with the
Help > Printable Guides command in the software.
new 2011 R1 Report filters from the Default Filters 2011 R1 folder to
the version 2009.1 or version 2011 SP1 Default Filters folder as needed.
and the report query interpreter recompiled with 2011 R1 for the report to work.
Below table shows all such ProgIDs relevant to reports that must be changed for 2011
R1.
Notes
In order for insulation to be applied and displayed for a newly placed
nozzle in a model upgraded from version 2009.1 to version 2011 SP1,
the Update Symbol custom command needs to be ran for the following
ProgIds of the NozzleVBsymb.dll symbol.
GSCADNozzleVBSymb.FlangedNozzle
GSCADNozzleVBSymb.HvacNozzle
GSCADNozzleVBSymb.ElbowNozzle
Please be aware that doing so will trigger an update on all existing
connected route features.
For nozzles that already exist in the model before an upgrade is
performed or for nozzles placed in new models created with version
2011 SP1, users do not have to run the Update Symbol command for
insulation to be correctly applied and displayed.
2011 SP1
The following files located in the SM3D 2011 SP1 SharedContent\Bin folder have
different version numbers compared to the SM3D 2009.1 Symbols\Bin folder.
Upgrade and Synchronize Model with Catalog will automatically apply the necessary
updates to existing objects within the model.
SharedContent\Bin\HangersAndSupports\Symbols\Release\hs_S3DStrap.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\hs_S3DUBolt.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\hs_S3DYokeClamp.dll
SharedContent\Bin\SmartPlantStructure\Symbols\Release\SP3DDoorAsm.dll
SharedContent\Bin\SmartPlantStructure\Symbols\Release\SPSSlabAssemblyConnect
ions.dll
SharedContent\Bin\Piping\Symbols\Release\OutfittingCrossSectionsSymbols.dll
SharedContent\Bin\Shapes\Symbols\Release\SketchCSSymbol.dll
SharedContent\Bin\SmartPlantStructure\Symbols\Release\SPSEqpFndMemSys.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMAssyConRul.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMCollarRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMCornerFeatRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMEdgeFeatureRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMEndCutRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMPhysConnRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMSlotRules.dll
SharedContent\Bin\StructDetail\Symbols\Release\WeldSymbols.dll
SharedContent\Bin\HoleMgmt\SmartOccurrence\Release\HoleRules.dll
2011 R1
The following files located in the SM3D 2011 R1 SharedContent\Bin folder have
different version numbers compared to the SM3D 2011 SP1 SharedContent\Bin
folder. Upgrade and Synchronize Model with Catalog will automatically apply the
necessary updates to existing objects within the model.
SharedContent\Bin\HangersAndSupports\Symbols\Release\FlSample_Part.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\GeneralProfileSymbols.dl
l
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrAssemblySymbols.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrBeamAtt.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrBracketSymbols.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrCTAssemblySymbols
.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrDesignSupportSymbo
l.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrSupDuctParts.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrSupPadSymbols.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrSupShoes.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrSupStructuralSymbol
s.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HgrSupTemporarySymbo
ls.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Anvil.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Bline_Channel.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Bline_Tray.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_FINL_Parts.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Generic.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Halfen_PC.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Hilti_MIParts.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Hilti_MQParts.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_HVAC.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_JIMCBOM.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Lisega.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_LRParts.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Power.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Base.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Bm.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Clmp.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Const.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Dyn.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Iso.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Misc.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Rod.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_RodFit.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Shoe.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Strp.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Trap.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\Hs_Psl_Var.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_S3DDummyLeg.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_S3DGuide.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_S3DWeld.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_SmartCutbackSteel.d
ll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_SmartSteel.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_TrayShip.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Util_Metric.dll
SharedContent\Bin\HangersAndSupports\Symbols\Release\HS_Utility.dll
SharedContent\Bin\HangersAndSupports\Rules\ReleaseHgrPipePartSelRule.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMAssyConRul.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMCornerFeatRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMEndCutRules.dll
SharedContent\Bin\StructDetail\SmartOccurrence\Release\SMSlotRules.dll
SharedContent\Bin\HoleMgmt\SmartOccurrence\Release\HoleRules.dll