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
Preparing for the Upgrade ..............................................................................................10
Backup the Model and the SharedContent (Symbols) Share.....................................11
Check the Integrity of the Databases ..........................................................................11
Verify the Consistency of Piping Specifications .............................................................. 11
Determine if Synchronize is Required .............................................................................. 12
Synchronize the Version 2009.1 or Version 2011 SP1 Model with the Version 2009.1 or Version
2011 SP1 Catalog.............................................................................................................. 12
Resolve the Version 2009.1 or Version 2011 SP1 To Do List ......................................... 12
Check Version 2009.1 or Version 2011 SP1 Database Integrity ...................................... 13
Verify Reference Files ...................................................................................................... 13
Contents
Resolve the 2011 R1 To Do List ................................................................................39
Check 2011 R1 Database Integrity .............................................................................39
Regenerating the Reports Database ...............................................................................40
Copy Filters from Catalog...............................................................................................41
Appendix I: Upgrading Your Tool Schema...................................................................42
Appendix II: Upgrading Your SmartMarine 3D Reports Template Files .................43
Upgrading to 2011 R1 Reports ...................................................................................43
Impact of Changing the Middle Tier Report dlls to C++ ...........................................44
Appendix III: SharedContent (Symbols) Share Changes in 2011 ...............................45
4
Guide
Preface
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
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
Introduction
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 SP1 and later allow custom DLLs to be used without
registering them. For more information, see Upgrading Custom Symbols and
Naming Rules, page 24.
6
Guide
Introduction
Step 3. Upgrade your databases The software performs this process
automatically; however, you can control it using the Database Wizard and the
Project Management task. For more information, see Upgrading the Databases,
page 27.
Step 4. Upgrade your version 2009.1 or version 2011 SP1 reference data After
upgrading the databases, your model should have the same functionality as it did
in version 2009.1 or 2011 SP1. However, some new features and fixes in version
2011 R1 may require that you update your reference data to take advantage of
them. This step integrates the additions and modifications that are included in
version 2011 R1 of the software into your version 2009.1 or version 2011 SP1
reference data. You integrate these additions and modifications based on changes
that are documented in the reference data workbooks that are delivered with 2011
R1. Because this step may be a lengthy process, you can delay this process until a
later time and go on to the next step. For more information, see Upgrading the
Reference Data, page 35.
Step 5. Synchronize the Model with the Catalog This step loads the Catalog
database changes into the model. For more information, see Synchronizing the
Model with the Catalog, page 38.
Step 6. Regenerate the Reports database For more information, see Regenerating
the Reports Database, page 40.
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.
Introduction
Note
Introduction
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..
Unless otherwise stated, the steps in this section apply to all cases and
must be performed BEFORE starting the upgrade process.
Unless otherwise stated, you must perform the steps in this section on
a Workstation computer on which SM3D version 2009.1 or version
2011 SP1 is installed, as well as the latest Hot Fix(es).
To help diagnose any upgrade problems you encounter, move all logs
and reports you create in this section to a common location where you
can easily access them.
10
Guide
For assistance with the Backup command, refer to the Back Up and
Restore Data section in the version 2009.1 or version 2011 SP1
Project Management Users Guide, available with the Help >
Printable Guides command in the software.
2. For data security, copy your SharedContent (Symbols) share to a different
location.
11
13
For assistance with the Backup command, refer to the Back Up and
Restore Data section in the version 2009.1 or version 2011 SP1
Project Management Users Guide, available with the Help >
Printable Guides command in the software.
14
Guide
For Case D, which only applies for version 2011 SP1, for more details on each
case, see Upgrade Cases, page 7. Before installing 2011 R1 SM3D Reference
Data software, backup and copy all files from their installation folder to another
location on the server. These files may be necessary if you need to create a new
version 2009.1 Site, Catalog and/or Plant in the future.
All Cases A, B, C, and D
1. Install the required 2011 Enterprise Platform software on the server, if not
already.
Notes
15
Using the Restore as Copy mode will remove the registration with an
integrated environment for the new model.
Using the Restore as Copy mode will remove the registration with an
integrated environment for the new model.
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.
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.
17
If the files have not been renamed, they will be overwritten and your
customizations will not be present after the upgrade is complete.
18
Guide
Important
19
21
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.
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.
23
These steps are only necessary if you have customized the file
Styles.sha and after performing the steps in Upgrading the
SharedContent (Symbols) Share, page 18. These steps assume that the
delivered Styles.sha file is located in the
SharedContent\Drawing\templates folder on the SharedContent
(Symbols) share and that your customized file is backed up at some
other location.
1. Rename the delivered Styles.
2. Copy your customized Styles.sha file to the SharedContent\Drawing\templates
folder on the SharedContent (Symbols) share and rename it, if necessary, with the
name Styles.sha.
SmartMarine 3D 2011 R1 Upgrade Guide
25
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.
26
Guide
You will need the following references to complete the steps in this
section.
For assistance with this step, refer to the Upgrade a Site Database
section in the 2011 SP1 Project Management Users Guide, available
with the Help > Printable Guides command in the software.
2. Using the 2011 R1 client workstation that includes the Project Management
environment, 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 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
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.
SmartMarine 3D 2011 R1 Upgrade Guide
27
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
28
Guide
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.
See the 2011 R1 Global Workshare Users Guide for more detailed
instruction.
1. At the Host location, use the version 2009.1 client workstation that includes the
Project Management component to consolidate the Marine configuration.
29
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.
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 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.
30
Guide
For assistance with this step, refer to the Upgrade the Site and Site
Schema Databases section in the 2011 R1 Project Management Users
Guide, available with the Help > Printable Guides command in the
software.
If there are non-trusted satellites in the work share then the below
message will be displayed with Yes and No options.
Failed in establishing trusted connection to one or more satellite
servers involved in the Global Work share configuration.
Host Server / Database: ServerName / DatabaseName
Migration will treat them as untrusted sources and generate the
required scripts to manually migrate them. Do you want to
continue?
On selecting Yes, the migration will proceed further and on selecting
No the migration will not continue.
2. At the Host location, using the version 2011 R1 client workstation that
includes the Project Management component, upgrade non-replicated
views by executing all of the scripts and views detailed in the upgrade
SiteDBName_ReadMe.txt file.
a. Script information is recorded in the upgrade
SiteDBName_ReadMe.txt file.
31
For assistance with this step, refer to the Upgrade the Catalog and
Catalog Schema Databases section in the 2011 R1 Project
Management Users Guide, available with the Help > Printable
Guides command in the software.
32
Guide
Notes
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 the AddToPublications_.bat file to execute the script.
4. Ensure that all data is replicated between the Host and Satellite(s)
before performing the next view generation step.
5. Regenerate the Catalog and Catalog Schema views on each
Satellite using the View Generator. The View Generator
executable, ViewGenerator.exe, is delivered in the [Product
Folder]\Core\Tools\Administrator\Bin folder.
6. In an integrated environment at the Host location for Marine configurations, run
the Generate Design Basis command from the version 2011 R1 client
workstation that includes the Project Management component.
7. If Generate Design Basis was performed, regenerate the Catalog and Catalog
Schema views on each Satellite using the View Generator.
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.
8. At the Host location, using the version 2011 R1 client workstation that includes
the Project Management component, upgrade the Model database.
Notes
For assistance with this step, refer to the Upgrade the 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.
33
2.
3.
4.
5.
6.
For non-trusted satellites, the respective .bat file and the sql
file need to be copied to the satellite location and be executed
manually.
Repeat the above step for each Satellite location.
Run all the AddToPublications_.bat file(s) on the corresponding
Satellite location.
Repeat the above step for each Satellite location.
Ensure that all data is replicated between the Host and Satellite(s)
before performing the next view generation step.
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
34
Guide
You will need the following references to complete the steps in this
section.
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
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.
35
Using the version 2011 R1 client workstation open the folders [Product
Folder]\CatalogData\BulkLoad\Datafiles and [Product
Folder]\ShipCatalogData\Bulkload\Datafiles to review the most recent
delivered catalog data.
Select the files that correspond to the discipline in which you are interested in.
Review the Revision History worksheet for each file. Note which additions or
changes you want to incorporate into your reference data.
Note
When using Delete and Replace mode in the Bulkload Utility, all
existing catalog entries for each worksheet will be deleted and
replaced with the contents of the worksheet being bulkloaded. In cases
where worksheets exist in multiple workbooks (i.e. Pipestock,
PipingGenericDataBolted, PipingCommodityMaterialControlData,
etc.), missing data must be bulkloaded in Append mode to restore
data which was deleted.
36
Guide
37
You will need the following references to complete the steps in this
section:
38
Guide
If there are any objects in your model whose configuration status is not
set to Working, it is possible that they will appear in the To Do List
as a result of the Synchronize process.
After their removal from the To Do List, the objects can be changed
back to their original configuration status.
39
40
Guide
41
a. [SharedContent]\XML\SP3DPublishMap.xml.
b. [SharedContent]\XML\P3DComponent.xml.
c. [SharedContent]\XML\DesignBasis_Map.xml.
42
Guide
43
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.
Old ProgID
New ProgID
ReportsDatabaseHelper.BulkBindingHelper
ReportsDatabaseHelper.DatabaseHelper
MiddleReportsServices.BulkBindingHelper
MiddleReportsServices.DatabaseHelper
MiddleReportsServices.LabelServices
MiddleReportsServices.RichTextValidator
MiddleReportsServices.ReportsRuntimeFramework
MiddleReportsServices.CacheController
MiddleReportsServices.CodeListsCache
MiddleReportsServices.CurrentFormatting
MiddleReportsServices.FormattingStack
MiddleReportsServices.ReportingDomain
MiddleReportsServices.TemplatesCache
RichTextValidation.Validator
SP3DReportsRuntime.CFrameWork
SP3DReportsRuntime.CCacheController
SP3DReportsRuntime.CCodeListsCache
SP3DReportsRuntime.CFormatting
SP3DReportsRuntime.CFormattingStack
SP3DReportsRuntime.CReportingDomain
SP3DReportsRuntime.CTemplatesCache
44
Guide
Copy/Paste
45
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
46
Guide
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
SmartMarine 3D 2011 R1 Upgrade Guide
47
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
49