Installation Guide
Installation Guide
Installation Guide
Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.
Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support,
SharePoint, or [Link], any documentation related to work processes, workflows, and best practices that is provided by Intergraph
as guidance for using a software product.
Terms of Use
a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the
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 and Documentation. 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.
b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license
agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a
reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial use. The Other Documentation
may not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and
for any reason by Intergraph Corporation by giving written notice to Licensee.
Disclaimer of Warranties
Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph
Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability
and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed
a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its
publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used
or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
Limitation of Damages
IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL,
SPECIAL, OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF
REVENUE OR PROFIT, LOSS OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT
INTERGRAPH CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS
MADE. EXCEPT WHERE PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN
CONNECTION WITH THE SUBJECT MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2)
YEARS AFTER THE EVENT GIVING RISE TO THE CAUSE OF ACTION HAS OCCURRED.
IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS
LIABILITY TO THE MAXIMUM EXTENT ALLOWED BY SAID LAW.
Export Controls
Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its
subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are
subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software
Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access)
under the following circumstances:
a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce
Denied Persons, Entities, and Unverified Lists, [Link] the U.S.
Department of Treasury Specially Designated Nationals List, [Link] and the U.S.
Department of State Debarred List, [Link]
c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design,
development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive
nuclear uses.
d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export
Compliance Department, Huntsville, Alabama 35894, USA.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, FrameWorks, I-Sketch, SmartMarine, IntelliShip, ISOGEN, SmartSketch,
SPOOLGEN, SupportManager, SupportModeler, Sapphire, and Intergraph Smart are trademarks or registered trademarks of
Intergraph Corporation or its subsidiaries in the United States and other countries. Hexagon and the Hexagon logo are registered
trademarks of Hexagon AB or its subsidiaries. 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-2013, 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.
Internationalization .................................................................................................................................... 13
Documentation Comments
For the latest support information for this product, comments or suggestions about this
documentation, and documentation updates for supported software versions, please visit
Intergraph Smart Support ([Link]
Updated the Enable Error Log dialog box. For more information, see Troubleshooting the
Software (on page 206). (P3 CP:275291)
You can now run a silent install of Smart 3D hot fixes. For more information, see Silent
Installation (on page 80). (P3 CP:285588)
You can now configure the display settings to correctly set the Render Mode to Shaded
with Hardware Enhanced Edges in the Format View dialog box. For more information, see
Smart 3D Workstation Recommendations (on page 19). (P4 CP:261779)
Added new information about SQL permissions for Smart 3D users. For more information,
see Assign Access Permissions for SQL (on page 117). (P4 CP:261802)
When defining a workspace, roles now work across all object types and can improve
performance. For more information, see Define Workspace Dialog Box (on page 188) and
Define roles (on page 190). (P4 CP:258039)
Installation Overview
This document guides you through the process of installing Intergraph Smart TM 3D.
Step-by-step instructions are provided whenever possible. However, because of operating
system and database updates released after this document was published, the steps provided in
this document might not reflect the new updated workflow. Please be prepared to use your
technical knowledge to perform the same overall workflow.
After reading the Internationalization (on page 13) information, please review the Smart 3D
Hardware and Software Recommendations (on page 16) section carefully before you proceed to
Database Server Setup (on page 32).
Third-Party Integration
Equipment Modeling Capability
Whether using one of the delivered symbols or a custom symbol that you define yourself,
symbols are a key building block used to create your model. The software uses two basic types
of symbols: 2D and 3D.
The 2D symbols are used to represent structural member cross-sections. Two-dimensional
symbols for structural cross-sections are delivered in the [Product
Folder]\SharedContent\CrossSections and [Product Folder]\SharedContent\Profile Xsections
folders. You can use any of the defined cross-sections or define your own cross-sections using
the software's 2D Symbols application. This application allows you to define different
representations for the cross-section using layers. You can also define variables to drive the
dimensions of the cross-section symbol.
An extensive library of 3D symbols is delivered in the various subfolders located in the [Product
Folder]\SharedContent folder on the reference data server computer. The 3D symbols are used
to represent equipment, hangers, HVAC components, piping components, and so forth in your
model. You can also create custom three-dimensional symbols using the SmartPlant 3D
Symbol/Part Definition Wizard.
The SmartPlant 3D Symbol/Part Definition Wizard allows you to create and customize three-
dimensional symbols that fit your company or project. The wizard produces a Visual Basic®
project for building the symbol ports and graphics, and generates an Excel workbook for
bulkloading the symbol data into the Catalog database.
While not prerequisite software, you can also use Solid Edge with Smart 3D. With Solid Edge,
you can build intelligent equipment reference data libraries of base parts that can be placed into
the Smart 3D model. An entire catalog of standard equipment can be modeled with Solid Edge,
as well as custom, one-of-a-kind equipment for specific plants.
Additional information on the software's equipment modeling capabilities, including parameter
descriptions of the delivered symbols, how to create 2D and 3D symbols and incorporate them
into your reference data, is available in the Smart 3D Reference Data Guide, the 2D Symbols
User's Guide, and the 3D symbols documents for Piping, HVAC, Equipment, Electrical, and
Structure tasks. Each of these documents is available from Help > Printable Guides in the
software.
Installation Checklist
For the recommended installation workflow, please see the installation checklist
(S3DInstall_Checklist.pdf), available in the Help folder on the product media. This checklist is
also delivered during product set up to C:\Program Files (x86)\Common
Files\Intergraph\Smart3D\Help folder for future reference.
Internationalization
Supporting internationalization in a homogeneous environment is one of the enhancements
available in SmartPlant Enterprise. A homogeneous environment uses elements from only a
single locale. For example, a German customer running on a German operating system using
only German characters and German cultural conventions is a fully supported homogeneous
environment configuration.
Homogeneous Environments
When starting a new project, use extra care during installation and configuration to ensure the
proper creation and maintenance of homogeneous environments:
All the computers (servers and clients) within an integrated SmartPlant Enterprise
implementation must have the same regional settings, and no one should change the
regional settings after the project has started.
Do not cross the decimal locale boundary. This is the most common cause of numeric data
corruption and calculation errors. Having users with different regional settings (such as with
a period versus a comma for the decimal point) causes the software to interpret values
unpredictably. For example, a pipe run with a pressure of 35.3 psi can be read by the
software as 353 psi to the user with different regional settings. A cable length defined as 39
ft 11,21 inches has been interpreted as 121718910971323 meters when published to an
XML file. These incorrect interpretations may be used in internal software calculations and
can be impossible to backtrack or correct. Do not change the decimal point character to try
to solve an issue. Doing so will only corrupt values in the database or in text files.
Do not cross the character-set locale boundary. For example, the character set boundary
between Western (Latin-based) and Eastern Europe (Cyrillic-based), or between Eastern
Europe and Japan.
Create Oracle databases using AL32UTF8 for the database character set and AL16UTF16
for the NLS character set.
Never modify the NLS_LANG registry entry on an Oracle client. Doing so causes the
character data not to convert to Unicode.
Create Microsoft SQL Server databases with locale-specific collation settings and ensure
that all databases have the same setting.
Heterogeneous Environments
In contrast, a heterogeneous environment using elements from different, or even multiple
locales, is not supported. Many customers are currently operating in unsupported
heterogeneous environments and are often not aware of that fact. Examples of heterogeneous
environments:
Entering or viewing Japanese data on an US/English operating system
Using German Regional Settings (where the decimal point is a comma) on a US/English
operating system
In This Section
Smart 3D Database Server Recommendations ............................ 17
Smart 3D Workstation Recommendations .................................... 19
Software Loading Order ................................................................ 22
Disk Partitioning Guidelines ........................................................... 24
Smart 3D Project Hardware Sizing Recommendations ................. 25
Applicable Hardware
Database server
File server
Hardware Recommendations
Intel Xeon® 5600 Series or better (64-bit instruction set, not Itanium ®)
32 GB to 128 GB or greater RAM depending on project size
For hard drive size, see Smart 3D Project Hardware Sizing Recommendations (on page 25)
Backup system for server
Access to DVD drive, either locally or through a network connection
1 GbE or higher network interface for client connections, latency should be less than 1 ms
between client and database server
and upgrading to future releases. Please contact Intergraph Customer Support for specific
configuration questions.
Software Prerequisites
Adobe Reader (Required to view documentation PDFs. You can download Acrobat Reader
from the Adobe web site.)
Microsoft XML Core Services (MSXML) 6.0 (Database server only)
Microsoft .NET 4.5.2 or later
For more information on hardware requirements, see Smart 3D Project Hardware Sizing
Recommendations (on page 25).
For information on disk space usage and determining RAID configuration, see Disk Usage
(on page 198).
For specifications regarding minimum hard drive disk space requirements by the product
setup, see Disk Partitioning Guidelines (on page 24).
On the server, distribute files across several disk drives with the following minimum
distribution: operating system and database software on one drive, database data files on
another drive, and the database log file on the third drive.
Ensure that your system's security certificates are updated prior to installation.
Beginning with Windows 10 and Oracle [Link], Microsoft and Oracle will enforce the
Internet Host Table Specification RFC 952 which mandates that component hostname labels
can contain only alphanumeric characters. Host names using underscores (‘_’) are not
allowed. Refer to Oracle Support Articles 1603775.1 and 1957895.1 and Microsoft KB
101785.
See Also
Smart 3D Hardware and Software Recommendations (on page 16)
Applicable Hardware
Administrative client
Modeling client
Interference detection computer
Drawings batch computer
Name generator computer
Duplication and synchronization computer
SmartPlant Piping Specification Remote computer
Hardware Recommendations
Intel Core i7, Quad Core
6 GB RAM (2 GB RAM for operating system plus 4 GB RAM for single Smart 3D instance.
Other concurrently running programs will require additional RAM based on the programs
specific requirements.)
Access to a DVD drive, either locally or through a network connection
Monitor capable of a minimum of 1280 x 1024 resolution
Graphics card designed for 3D-intensive applications that meets the following requirements:
32-bit main RGBA pixel buffer
Hardware OpenGL 2.1 support
Hardware Z buffer: 24 bit or higher
256 MB RAM
8-bit stencil buffer
Hardware Alpha blending support
Graphics acceleration set to full
Hardware Anti-aliasing support recommended
Latest available drivers should be installed
1 GbE or higher network interface, latency should be less than 1 ms between client and
database server
Video Cards
There have been many enhancements to the graphic engine of Smart 3D. Most issues are
resolved by loading the most current display driver or rolling your current display driver back one
version. If the current driver does not fix your particular card's problem, then please copy the
[Link] file from [Product Folder]/Core/Tools/Administrator/Bin to [Product
Folder]/Core/Shared/bin and contact your Smart 3D support representative.
We recommend workstation class graphics cards (designed for use with CAD applications) with
as much RAM as is affordable. The minimum RAM is 256MB, but more RAM is better. Because
the world of graphics cards changes so quickly, we can only document the specifications
required by Smart 3D.
All clients referencing Z+F Point Cloud data need to turn off the Smart 3D hardware with the
[Link] file.
When you set the Render Mode to Shaded with Hardware Enhanced Edges in the
Format View dialog box, the edges might not display properly. To fix the display, edit the
[Link] file as shown:
Ensure that the ViewSettings block is at the top of the file.
Type "DisplayEdgeOnGraphics=1" in the ViewSettings block.
This setting might adversely affect the display performance.
As a supplement to this information, a Microsoft Excel workbook is provided on Intergraph Smart
Support that records anecdotal evidence obtained from users. Please go to Intergraph Smart
Support at [Link] ([Link] and select
View Downloads > Smart 3D > Technical Notes and White papers > Display > Graphics
cards used with Smart 3D. This list is not comprehensive. In some cases, the Smart 3D middle
tier error log (with the error logging level set to at least "2-Detailed") will provide more
information. Please see the examples of messages returned in the error log listed below:
The graphics card or graphics card driver does not support Textures/Shaders. An updated
graphics driver could improve performance.
This indicates that the graphics adapter, driver or display settings do not support the
Shaded with Hardware Enhanced Edges render mode on the Format View dialog box. In
addition, the graphics adapter, driver or display settings do not support textures.
The graphics card or graphics card driver does not support Shaders. An updated graphics
driver could improve performance.
This indicates that the graphics adapter, driver or display settings do not support the
Shaded with Hardware Enhanced Edges render mode on the Format View dialog box.
However, textures are supported.
The graphics card or graphics card driver does not support Textures. An updated graphics
driver could improve performance.
This indicates that the graphics adapter, driver or display settings do not support textures.
However, the Shaded with Hardware Enhanced Edges render mode on the Format View
dialog box is supported. Please note that the performance may be slow on an ATI card.
Hardware Acceleration is Turned off VBO Texture and Hardware edges will not be
supported.
This message indicates that Hardware Acceleration in Display Settings is disabled or the
client is being accessed through Remote Desktop or Citrix Client. This also applies to
systems that use Intel chipset graphics acceleration, where hardware acceleration is
disabled due to driver stability. If Hardware Acceleration in Display Settings is disabled, it
should be enabled by clicking Advanced on the Settings tab of the Display Properties
dialog box. Then, the Hardware Acceleration can be modified from the Troubleshoot tab.
Software Prerequisites
Microsoft Internet Explorer 11 or later (required for viewing the documentation delivered with
the software)
Adobe Reader 11 or later (required for viewing Printable Guides. You can download Acrobat
Reader from the Adobe web site.)
Microsoft .NET Framework 4.5.2 or later
Microsoft XML Core Services (MSXML) 6.0 SP1
Microsoft Office 2013 (32-bit only)
Intergraph Batch Services SP1 ([Link]) if you plan to use the computer for remote batch
processing
Intergraph SmartPlant License Manager 2012 (12.0) or higher
For specifications regarding minimum hard drive disk space requirements by the product
setup, see Disk Partitioning Guidelines (on page 24).
Dual screen configurations should have either a single graphics card with two VGA outputs
or two identical graphics cards. The graphics cards should otherwise meet the requirements
of the specified graphics card recommendations.
Use thread safe video drivers and CAD application certified video cards when using multiple
processor systems.
Ensure that your system's security certificates are updated prior to installation.
Beginning with Windows 10 and Oracle [Link], Microsoft and Oracle will enforce the
Internet Host Table Specification RFC 952 which mandates that component hostname labels
can contain only alphanumeric characters. Host names using underscores (‘_’) are not
allowed. Refer to Oracle Support Articles 1603775.1 and 1957895.1 and Microsoft KB
101785.
See Also
Smart 3D Hardware and Software Recommendations (on page 16)
Oracle 12c R1 ([Link]) Standard Edition Oracle 12c R1 ([Link]) Client Release 32-bit; (Do
2 or Enterprise Edition (64-bit) not use the Oracle "light client" as it does not
include some DLLs required by Smart 3D.)
-OR-
Oracle 12c R1 ([Link]) Client Release 64-bit is
required if you are running 64-bit Interference
Checking or 64-bit Drawings Batch.
-OR-
Microsoft SQL Server 2014 (Standard Microsoft SQL Server 2014 Client1; (64-bit)
Edition for stand-alone environments;
Enterprise Edition for Global Workshare
environments; 64-bit)
1 MicrosoftSQL Server 2014 Client is required only for the client software installation if the
Project Management option is installed; otherwise, they are not integral to the default
workstation software installation.
2 When creating drawing borders or embedded reports within the Drawings and Reports task on
computers with Office 2013 (32-bit), you must modify the security settings in Microsoft Excel to
allow Visual Basic projects to run. For more information about Office 2013 and service packs,
refer to the Microsoft web site.
Do not skip any restarts that are recommended by the system. Doing so can
have unintended consequences.
Other users who want to perform different tasks in the overall design workflow might need
additional software, such as:
Additionally, if you intend to export PDS projects, you must install the appropriate PDS add-in.
The PDS data export add-ins are delivered on the product DVD.
This version of the software supports PDS 2011 SE and PDS 2011 R1 SE.
PDS software and all of its prerequisite software are also required in order to use the PDS
integration functionality. For more information, see Integrating with PDS (on page 135).
If you are installing the Name Generator Service on an Oracle 32-bit Client computer, the
computer must be configured to access the Oracle database server through Net Manager.
If you are installing the 64-bit Name Generator Service on an Oracle 64-bit database server
computer, the firewall must be configured to allow DCOM Dynamic Ports. For more
information, see Configure the Firewall to Allow DCOM Communication in Windows Server
(on page 95).
1The default setup for a Smart 3D workstation computer provides all the environments
necessary for general Smart 3D modeling.
2 The complete setup for a Smart 3D workstation computer includes all features and adds the
administrative functionality: plant creation, database migration, access management, database
interference detection, and includes the following options only: Project Management, Server
Connectivity, Bulkload Reference Data, and Database Interference Detection Service.
Additionally, a complete setup includes the Piping Specification Remote Access Server
option, which installs the necessary software for correlating piping specification data between
Smart 3D and SmartPlant P&ID, respectively.
You also will need additional disk space if you intend to use other products, such as Visual
Studio or Solid Edge. Please consult your system administrator for this and additional software
not provided by Intergraph.
Do not continue with installation until enough disk space is free on the computer
acting as the database server and each workstation computer as stated in the aforementioned
guidelines.
Concurrent Users
The size of the system depends partly on the number of concurrent users, that is, users actively
working at the same time. In a Global Workshare Configuration (GWC), it is probable that work
will be done at several sites in a non-concurrent way. In this case, there is less impact on
performance. For example, if you have two sites with 60 users at each site but the users at the
two sites do not work at the same time, you could consider the user load to be 60 users.
In a Global Workshare Configuration when users are working concurrently at several sites, the
work done at one site will impact each site as the data is pushed to the other sites. In a hub and
spokes configuration, the data is first pushed to the hub then the hub pushes it to the other sites.
We estimate that the equivalent user load (the number of effective users) for each server to be
the users on that server plus 25% of the total concurrent users of all the other sites. For
example, in a configuration with 6 sites and 40 users at 5 sites, and 5 users at 1 site:
When 3 sites (with 40 users) are working concurrently, the equivalent number of users at
each site is: 40 (concurrent users for this site) + (0.25 * (2 * 40)) (users for the 2 other sites)
= 60 users.
When all 6 sites are working concurrently:
a. The equivalent number of users at each of the 40-user sites is: 40 + (0.25 * (165)) = 81
users
b. The equivalent number of users at the 5-user site is: 5 + (0.25 * (200)) = 55 users.
Modeling (detail design) and administrator computers can be on separate or on the same
computer
Use a separate distribution server for Global Workshare Configuration
Server Specifications
Project size Small Medium Large
Oracle 12c Standard Edition 2 only supports setups of up to two sockets and 16 threads.
Running a Microsoft SQL Server or Oracle database on an Itanium processor-based server
has not been certified and should not be done.
Hard Drives
Distribute files across several disk drives on the server. Each drive does not need a large
capacity. The speed of the drive is important, so use 15K RPM or faster.
For hard drive size, see Smart 3D Project Hardware Sizing Recommendations (on page 25)
Backup system for server
Access to DVD drive, either locally or through a network connection
1 GbE or higher network interface for client connections
For small projects, a single server (the hub in a hub and spoke configuration) can act as a
publisher, a distributor, and a subscriber all at the same time. For medium projects in a Global
Workshare Configuration, the database server can also serve as the distribution server.
For large projects with many sites, use two different servers: one as publisher and subscriber
and the other as the distributor. Using a separate server as the distributor helps to reduce the
load on the publisher.
License Server
SmartPlant License Manager (SPLM) uses server/client architecture to distribute licenses for
Smart 3D (and other SmartPlant Enterprise products.) SPLM requires very little system
resources and so can be installed on the batch server, file server, IFC server, or database
server as long as the hardware configurations below are observed.
Intergraph recommends that the SmartPlant License Manager license machine software be
installed on a stable, single node, hardware configuration (such as a simple PC), with a static IP
address, because license key installation and license seat usage authentication depends on the
information gathered from the physical hardware.
Any changes that cause the hardware information to differ from the
information used to generate the license key will result in a failure of the authentication process.
For information about using SmartPlant License Manager in virtual environments, see Appendix
F: SmartPlant License Manager and Virtual Configurations.
Multiple SmartPlant License Manager license machines can be used in the user's network as
long as each system is a unique hardware system/installation. If SmartPlant License Manager
license machines are cloned after the license key has been installed, license management will
fail on the cloned system. Each SmartPlant License Manager license machine requires its own
unique license key.
Installing any database involves significant decisions regarding the size of the database, the
maximum number of users, the frequency of automatic backups, and other important issues.
Therefore, the following sections provide only suggestions for tuning your database
configuration to work with Smart 3D. The ultimate database creation and configuration depends
on the policies and standards at your company.
Supported Databases
Smart 3D currently supports Microsoft SQL Server 2014 and Oracle 12c R1 ([Link]).
When using the software in a Global Workshare Configuration (GWC), you can install
Oracle Enterprise Edition or Oracle Standard Edition. If you are using Microsoft SQL Server, you
must install Microsoft SQL Server 2014 Enterprise Edition.
For more information about supported databases, see Smart 3D Database Server
Recommendations (on page 17).
Windows Authentication
The Windows authentication method uses Windows users to control access to the databases.
Users must be added to the Windows domain, added to the database user access control, and
added to permission groups in Project Management.
Database User
The database user method uses user names and passwords defined in Oracle or Microsoft SQL
Server to control access to the databases. We recommend that you create two database users,
one user for administrative access and one user for general users.
If you choose to use the database user method, must create database login ini files. The ini files
contain the database server name, user name, and password Smart 3D is to to use to connect
to the databases. For more information, see Create Database Login ini File (on page 33).
After the ini files are created, you must define the location of the ini file on each computer. For
more information, see Database Authentication Settings (on page 34).
Smart 3D administrators must secure the ini file using the operating system to
prevent unauthorized access.
1. Double-click ..\Smart3D\ProjectMgmt\Tools\bin\[Link].
2. Click New.
3. Define the ini file name and the folder location.
4. Select the Database Type.
5. Click Add Server.
6. Type in the name of the database server, the database user name, and the database user
password in the appropriate cells.
Database server names must be unique in the file.
7. Click Test.
Access to the database server is tested using the defined user name and password. Passed
appears if the connection was successful. Failed appears if the connection failed.
8. Click Save.
You cannot save a file if there are failed connections.
Topics
Install Microsoft SQL Server 2014 ................................................. 36
Install any Required SQL Server 2014 Upgrades ......................... 41
Verify Automatic Startup of Microsoft SQL Server 2014 Services 41
Register Microsoft SQL Server ...................................................... 42
Assign System Administrator Privileges for SQL Server 2014 ...... 42
Create a SQL Server Database Alert ............................................ 43
SQL Server Port Assignments ....................................................... 46
3. Click Installation, and then select the New SQL Server stand-alone installation or add
features to an existing installation option.
4. Enter your SQL Server 2014 product key provided by Microsoft, and click Next.
5. Accept the license terms, and click Next.
Wait while the SQL Server Setup files are installed on the computer.
6. Click Next.
7. On the Microsoft Update page, check Use Microsoft Update to check for updates based
on your company's policy. Click Next.
Wait while the setup files are installed.
After the setup files are installed. Review the results for any failures that must be fixed
before you continue. Click Next.
8. On the Setup Role page, select SQL Server Feature Installation, and click Next.
10. Set the instance root directory and shared feature directories as you need.
11. Click Next.
12. Define your instance name and the instance root directory. Click Next.
13. On the Server Configuration page, specify a domain account name with administrative
privileges on the database server. Then, set the Startup Type to Automatic and continue.
16. On the Server Configuration tab of the Database Engine Configuration page:
Select Windows authentication mode if you plan to use Windows user names and
passwords to access the databases.
Select Mixed Mode if you plan to use database user names and passwords to access
the databases.
See Understanding Database Authentication (on page 33) to learn about the differences
between the two choices.
17. Specify at least one SQL Server Administrator. You will need this administrator login later to
open SQL Server Management Studio.
18. On the Data Directories tab, verify the directories are set as you need.
19. Click Next, and complete the installation as prompted.
If any errors occur during installation, refer to the Summary Log for more information and
contact Intergraph Support for further assistance.
The MSSQL service is appended with the named instance you specified when you
installed Microsoft SQL Server. For example, if you installed SQL Server as an instance
named Instance1, the service displays as MSSQL$Instance1.
4. To change the Status or Startup Type fields, click Tools > Services in Server Manager.
5. Right-click the service name, and select Properties from the shortcut menu.
6. On the General tab, select Automatic from the Startup type list.
7. In the Service status section, click Start.
8. Click OK.
3. Type the user account to be assigned administrative privileges in the Login name text box.
For example, type AdminUser1.
4. Select Server Roles under the Select a page heading to display the Server Roles list.
5. In the Server Roles list, select the sysadmin check box.
4. Expand Data Collector Sets in the tree view, and right-click on User Defined.
5. Select New > Data Collector Set from the shortcut menu.
6. Type the name for the data collector set, click Create manually (Advanced), and then click
Next.
11. Select a counter in the Select counters from list list, select a counter, and the click Add.
14. In the Limit box, enter a threshold value. Depending on the object you selected, the
software generates the alert when the value for the counter is more than or less than the
threshold value. Click Next to continue.
15. Click Finish.
Your new data collector set displays in the User Defined page.
16. To configure the alerts, double-click on your data collector set name and then right-click the
data collector. Select Properties from the shortcut menu.
17. On the Alerts tab, you can set additional alerts and define the unit of time for the duration of
the sample interval.
18. Set options in the Alert Action and Alert Task tabs to specify the actions to occur each
time the alert is triggered.
19. Click OK to close the Properties dialog box and activate the alert settings.
For more information about using System Monitor and setting up SQL Server
alerts, see the documentation delivered with Microsoft SQL Server and Windows Server.
1433 TCP From workstation to server; from server SQL Server Instance
to workstation
Collation field.
Existing CatalogDB template
Specifies the path and file name of the existing [Link] template to be copied and
converted to the new collation.
New CatalogDB template
Specifies the path and file name of the new [Link] template to be created. This
name updates automatically to a new default whenever you change the value in the
Collation field.
OK
Creates the new templates with the selected collation.
Cancel
Closes the SQL Server Collation Utility without creating any new templates.
9. In the Template file to be used to create site schema field, select the new template with
the desired SQL Server collation that you created with the SQL Server Collation Utility.
10. When creating or restoring the catalog database for the new site, be sure to select the
template with the correct collation. If the collation for the selected catalog does not match
the collation for the site, the following message appears: "The collation for the selected
template, [Link], does not match the collation for the site. Please select another
template."
This message also appears in the Bulkload Utility and in the New Catalog
command in Project Management if the collation does not match the site.
The [Link], SM_ShipCatalogDB.dat, and MHE_CatalogDB.dat
template files contain sample Smart 3D reference data and, while the templates contain
many useful examples, they are not certified for production use by Intergraph.
11. When you create the plant, reports, and reports schemas in Project Management, Smart 3D
automatically uses the collation of the site database.
12. In the future, when you create additional sites or catalogs, remember to select the correct
template with the desired collation.
See Also
Install Microsoft SQL Server 2014 (on page 36)
Oracle Instances
If one server hosts the databases of several products, Intergraph recommends that each
product database be a separate instance, each of which can host multiple plants.
The advantage of placing each product database in its own instance is that only the affected
application will be off-line during backup, performance tuning, and other database maintenance
activities. Additionally, global tuning parameters that apply to one instance can be tailored to the
specific product requirements.
According to Oracle documentation, the only limit to the number of instances you can have on
any machine is the availability of resources. However, the number of instances on one database
server should be minimized because each additional instance puts additional load on the server.
Each instance adds redundant tablespaces, rollback segments, background processes, and
memory requirements for each SGA (System Global Area). For this reason, you should start by
putting the database of one product for several plants into a single instance. Then, when the
number of plants increases, or a plant becomes very large, consider separating the database
into new instances, adding server memory, or even adding database servers.
Oracle recommends that database activity on the database server consume no more than
60 percent of the available memory. Refer to your Oracle documentation for specific
requirements.
Do not use the @ character in any Oracle passwords.
There are Oracle restrictions for the database global name and corresponding database link
name (they are required to match). There are three known restrictions on global database
names:
a. No hyphens are allowed.
b. The computer name cannot start with a number.
c. There is a maximum of 30 characters for the name.
Topics
Oracle Server Configuration .......................................................... 50
Install and Configure Oracle Server Software ............................... 50
Oracle 12c Server Installation ........................................................ 51
Create the Oracle 12c Database ................................................... 52
Configure Oracle Net Services ...................................................... 60
Initialize the Oracle Database ........................................................ 61
Verify Automatic Startup of Oracle Database Services ................. 63
Oracle Post-Installation Requirements .......................................... 63
Add Firewall Exceptions on the Oracle Database Server .............. 64
Oracle Database Port Assignments ............................................... 65
9. Click Yes.
10. On the Installation Location page, define the Oracle base and Software location folders.
Click Next.
11. On the Summary page, click Install.
12. Click Close when the installation has completed.
3. On the Creation Mode page, select Advanced Mode, and click Next.
4. On the Database Template page, select the Custom Database option, and click Next.
5. On the Database Identification page, enter the Global Database Name and the SID for
the database. These names are generally identical and can be no longer than eight
characters.
7. Enter the Global Database Name and SID. Clear the Create As Container Database
option. Smart 3D does not support pluggable databases. Click Next.
8. On the Management Options page, click Next without changing the default selections.
Configure Enterprise Manager (EM) Database Express and port 5500 are the default
options.
9. On the Database Credentials page, select a security option and provide the appropriate
information. Click Next.
10. On the Network Configuration page, select Create a New Listener, and then enter a
name and port number. Click Next.
11. On the Storage Locations page, select File System and Use Common Location for All
Database Files. Browse to and select the appropriate files location.
A subfolder is created in the folder you specified and is named with the SID you provided in
step 4.
12. If the database will not be used in a Global Workshare Configuration, select Specify Flash
Recovery Area in the Recovery Configuration screen, and click Next.
If the database will be used in a Global Workshare Configuration, select Enable Archiving,
and click Edit Archive Mode Parameters.
The Archive log parameters dialog box displays.
13. Select Automatic Archiving to specify the location of the archive log files. Click OK.
All the database components are selected by default if you are creating a
container instance. Leave them all selected if that is the case.
17. Select the Typical Settings option. The percentage of memory allowed for an instance of
Oracle should not exceed 40%. If you have more than one Oracle instance on this server,
the allocated memory should not exceed 40% of the system memory.
All products in SmartPlant Enterprise that participate in integration should set their
encodings to Use Unicode (AL32UTF8) for the Database Character Set option, and to
AL16UTF16 - Unicode UTF-16 Universal character set for the National Character
Set option.
For more information about the Character Set options, see your Oracle installation
documentation.
22. Select the Connection Mode tab, and select Dedicated Server Mode.
23. Click Next.
24. On the Creation Options page, click Customize Storage Locations.
The control files should be divided among multiple physical hard drives. This file
is needed by the database to start.
25. Verify that the path in the Tablespaces folder is correct for SYSAUX, SYSTEM, TEMP,
UNDOTBS1, and USERS.
The information in the Datafiles and Redo Log Groups folders can retain the
default settings as long as the folder path does not need updating.
26. Create an additional Redo log file, and set the Redo log file size for each group to 512000 K.
Not every setting is preserved in the template file. If you re-use template
files, check the parameters carefully to verify that the settings are correct.
Repeat this procedure until all of the Oracle service names participating in the Workshare
have been configured as a local net service.
For more information about using Oracle Net Configuration Assistant, see the Oracle
Database Net Services Administrator's Guide delivered with the Oracle database software.
An administrative user must run the scripts on the server. Before proceeding, place a copy
of each of the sample script files on the server computer.
The scripts must be run in the order listed because previous scripts create items that are
used in subsequent scripts. Do not deviate from the following sequence of steps.
4. If you are using OS authentication, edit the external user identified in the file as needed. Use
the following syntax: DOMAIN NAME\USERNAME, and then click File > Save.
Any typed alpha character must be capitalized.
-OR-
If you are using database user authentication, edit the external user identified in the file and
replace by the database user name. Also, replace IDENTIFIED EXTERNALLY with
IDENTIFIED BY [the user password].
Example replace:
CREATE USER "DOMAIN\USERNAME" PROFILE DEFAULT IDENTIFIED EXTERNALLY
with:
CREATE USER S3dStandardUser PROFILE DEFAULT IDENTIFIED BY
S3duserPassword
User logins cannot contain spaces. The database user name and password are
case sensitive.
5. Open SQL Plus. The Log On dialog box appears.
6. In the User Name field, type SYS AS SYSDBA.
7. In the Password field, type the password for the SYS account.
8. At the SQL prompt, type @<File Location>:\[Link], and press Enter.
For example, if you placed a copy of the script file in the root folder on the C drive, type
@C:\[Link].
9. After the script finishes, click File > Exit.
The OracleService is your Oracle database instance. It is appended with the named
Oracle System identifier (SID) you specified when you created the Oracle database. For
example, if your SID is Plant1, the service appears as OracleServicePlant1.
The TNSListener service is required to allow clients to connect to the Oracle database.
4. To change the Status or Startup Type fields, right-click the service name, and select
Properties from the shortcut menu.
5. On the General tab, select Automatic from the Startup type list.
6. In the Service status section, click Start.
7. Click OK.
1521, 1526 TCP From workstation to For Oracle Client SQL Net Connection
server; from server to (1521 is default). Can be changed using
workstation Oracle Net Configuration Utility to port
within range 1024-65535. For information,
see
[Link]
2_01/install.112/e16773/[Link]#CIHCC
JCF.
5560, 5580 TCP From workstation to For Oracle SQL Plus (5560 is default). Can
server be changed within range 5560-5579.
For information , see
[Link]
05_02/[Link]#BEHFDBEE – section
D.5.
443 TCP From workstation to For Oracle HTTP Server SSL Port (443 is
server default). Can be set to either 443 or 4443.
For information, see
[Link]
4_01/core.1013/e10403/[Link]#i65
3967.
7809 TCP From server to server Required for Oracle Global Workshare.
GoldenGate is now used for replication and
this port is needed for the GoldenGate
Manager to handle communication
between the servers.
7810-7820 TCP From server to server Required for Oracle Global Workshare.
Golden Gate is now used for replication
and this port is needed to facilitate the
transfer of transaction information between
the GoldenGate instances.
Client/Workstation Setup
The Smart 3D client software is used for general modeling, as well as for performing a variety of
administrative activities, including managing permissions, backing up and restoring data,
creating plants, and monitoring database interference detection. Additionally, the software
provides features that extend the capabilities of the software to include importing model data
and integrating Smart 3D with SmartPlant P&ID.
If you have a previous version of Smart 3D installed, you need to remove it before installing
the new version. For more information, see Application Maintenance (on page 194) in the
Intergraph SmartTM 3D Installation Guide.
The system language specified for Microsoft Office must be the same as the system
language specified by the operating system. For example, if your operating system language
is English, Microsoft Office must also be set to English.
If you choose to do a custom installation of Office, be sure to select the .NET Programming
Support for Excel, which is required for the Model Data Reuse command.
If running in a Citrix environment, the MSDN license key must be a VLM license key for
multiple users to run reports.
See Also
Loading Prerequisite Software on the Client (on page 68)
There are internationalization considerations concerning the SQL Server collation settings
you specify that relate to reference data, using SmartPlant Enterprise integrated systems,
Global Workshare Configuration, multiple locales, backup/restore, reports, and upgrading to
future releases. Please contact Intergraph Customer Support for specific configuration
questions.
If you are using a XenApp 6.5, XenApp 7.6, or XenDesktop 7 RDS local data store (farm),
you must install Microsoft SQL Server Client before installing XenApp 6.5, XenApp 7.6, or
XenDesktop 7 RDS.
1. Insert your Microsoft SQL Server DVD, and start the setup program.
2. From the Planning page, select System Configuration Checker to check for pre-requisite
applications and identify potential installation problems. You might have to restart your
computer if any pre-requisite applications were installed.
3. Click Installation, and then select the New SQL Server stand-alone installation or add
features to an existing installation option.
4. Enter your SQL Server 2014 product key provided by Microsoft, and click Next.
5. Accept the license terms, and click Next.
Wait while the SQL Server Setup files are installed on the computer.
6. Click Next.
7. On the Microsoft Update page, check Use Microsoft Update to check for updates based
on your company's policy. Click Next.
Wait while the setup files are installed.
After the setup files are installed. Review the results for any failures that must be fixed
before you continue. Click Next.
8. On the Setup Role page, select SQL Server Feature Installation, and click Next.
10. When you get to Installation Rules, make sure all operations have passed.
11. From Ready to Install, click Install.
12. When the installation has been completed, review the summary log file for any problems.
Smart 3D is a 32-bit application that uses the 32-bit Oracle Client even when loaded on a
64-bit client operating system.
However, the 64-bit Oracle Client is required on computers where the 64-bit Interference
Checker or 64-bit Drawings Batch Publishing is installed.
Do not use the Oracle "light client" as it does not include some DLLs required by Smart 3D.
You do not need to install the Oracle Client if you are using Microsoft SQL Server as your
database provider.
The Oracle Client and the [Link] file must be installed and configured on the Batch
Services and Interference Server computers.
Topics
Oracle 12c Client Installation ..........................................................73
Configure the Oracle Client ............................................................76
Configure Windows Firewall for the Oracle Client ..........................77
4. On the Oracle Home User Selection page, select Use Windows Built-in Account. Click
Next.
5. In the Oracle Base box, enter a unique folder location for the Oracle client.
6. In the Software Location box, enter a unique folder location.
7. Click Next.
8. On the Available Product Components page, select the options as shown below. Clear
the Oracle SQL Developer option.
9. Click Next.
10. Click Next.
Oracle performs prerequisite checks.
11. Click Install.
16. Click Yes on the message that the installation was successful but the configuration assistant
failed.
17. Click Close.
18. Copy the [Link] file from another previously configured system. The
[Link] file is located in <Oracle Home>\Network\Admin.
If you are using material handling mode, you must install Intergraph SmartSketch 2016 (9.0
or later) before installing Smart 3D. If you install Smart 3D first, then Smart 3D will not work
properly. You must separately purchase SmartSketch (SGBY297AV).
Smart 3D requires the SmartPlant License Manager software for concurrent licensing for
both the core Smart 3D product and for each module. This licensing software is delivered on
its own DVD that comes with your Smart 3D DVD. For more information about using and
configuring concurrent licensing, see the SmartPlant License Manager Installation and
User's Guide (SPLMInstall_UserGuide.pdf).
During setup, the %temp% value is defined as the user %temp% of the person who runs the
setup. In Windows, each user's C:\Documents and Settings\username\Local Settings\Temp
is protected from other Windows users. Consequently, you must set the system environment
variable TEMP value to a folder location where everyone has write access (for example,
c:\temp). For more information about editing system variables, see the Help and Support
Center (click Start > Help and Support Center from the Windows task bar).
1. Insert the Intergraph Smart 3D DVD. If the DVD does not start automatically, right-click
[Link] in the root folder of the DVD and select Run as administrator.
2. Click Additional Software, and the select the optional software that you need to install, if
any:
Install SmartPlant Schema Component (on page 135)
Install PDS Export Tools (on page 135)
3. Click Back if needed.
4. Click Full Installation.
5. Type your name or organization information.
6. Select the components to install on this computer:
Smart 3D Installation - Installs the Smart 3D client component that contains the
modeling tasks such as Common, Piping, Equipment, Structure, and so forth.
Project Management - Installs the Project Management client used for creating
models, managing access control, and upgrading databases. Select this option for
an administrator's computer. You must also install the Server Connectivity option
(below) and the Microsoft SQL Server client tools. The Microsoft SQL Server client
tools are not required on computers where Project Management is not installed or
if you are using Oracle as your database provider.
Bulkload Reference Data - Installs sample Microsoft Excel reference data
workbooks and the utilities needed to bulkload the workbooks into the Catalog task.
Select this option for people working with reference data and the Catalog task. You
must also install the Server Connectivity option if you select this option.
Piping Specification Remote Access Server - Installs the necessary software for
correlating piping specification data between Smart 3D and SmartPlant P&ID. This
option sets up the computer as a remote access server by registering the
SP3DPipingSpecRemoteAccessServer COM+ component. For more information
about the P&ID integration capabilities of the software, see Integrating with
SmartPlant P&ID (on page 137) in the Intergraph SmartTM 3D Installation Guide.
If you select this option, make sure that the Distributed
Transaction Coordinator service is not set to Disabled. The Piping Specification
Remote Access Server installation will fail if this service is disabled.
Database Interference Detection Service - Installs the software required for
database interference detection. You must configure this service through Windows
Services. Requires the Project Management and the Server Connectivity
components. For more information, see Interference Checking Setup (on page 146).
Server Connectivity - Installs required database connectivity components for
Project Management, the Bulkload Utility, Piping Specification Remote Access
Server, and the Database Interference Detection Service.
64-bit Services - Installs the 64-bit version of the Interference Checking and
Drawings Batch Services components.
64-bit Services cannot be uninstalled individually. You must
remove all of Intergraph Smart 3D from the computer to remove the 64-bit Services
component.
Name Generator Installation - Installs the 32-bit version of the Name Generator. Install
this one if you are installing the Name Generator on a computer where the Oracle 32-bit
client is installed.
Name Generator 64-bit Installation - Installs the 64-bit version of the Name Generator.
Install this one if you are installing the Name Generator on a computer running a server
operating system, you are using Microsoft SQL Server, or you are installing on an
Oracle database server.
For more information about which version of the Name Generator you need and
about the Name Generator in general, see Name Generator Service Setup (on page
86).
Make sure that the Distributed Transaction Coordinator service is not set to
Disabled. Name Generator installation will fail if this service is disabled.
Reference Data Installation - Installs the reference data needed to run Smart 3D. You
should pick one server on which to install the reference data. Do not install reference
data on each client or administrator computer. For more information, see Reference
Data Setup (on page 97).
Intergraph Smart 3D PDS Model & Data Translators Installation - Installs the PDS
Model & Data Translators (licensed-separately, SEBY801) component that further
extends the PDS integration capabilities by allowing you to export Piping, HVAC,
Electrical, Equipment, and Structure model data from PDS into Smart 3D. For more
information, see Install Smart 3D PDS Model & Data Translators (on page 136).
Intergraph Smart 3D Tribon Interface Installation - Installs the Tribon Interface
(licensed-separately, SEBY812) component that allows you to import Tribon Initial
Design M3 structural data into Smart 3D in marine mode for planning and outfitting
purposes. For more information, see Smart 3D Tribon Interface Setup (on page 104).
Programming Resources Installation - Installs the Programming Resources
component which provides developers with the tools necessary to customize the
software by creating custom commands or custom programs. For more information, see
Programming Resources Setup (on page 100).
Serial numbers are used for product identification only. A license key is
required to run the software. For more information about installing and using SmartPlant
License Manager, see the SmartPlant License Manager Installation and User's Guide
(SPLMInstall_UserGuide.pdf).
7. Read the license agreement. Click to agree to the Software License Agreement, and then
click Install.
The selected options are installed on the computer.
8. Click Finish.
If you installed Smart 3D on a computer with version 4.5.2 of the .NET
Framework installed, you must reboot your computer after installation completes.
Silent Installation
You can install and remove the software using a command line rather than the normal user
interface allowing you to perform unattended installations. The following command line
parameters and arguments can be used to perform a silent installation of the product:
[Link] SERIALNUMBER=### SLAACCEPT=YES [INSTALLDIR=<Path>]
[X64SERVICES=Yes] [ADDLOCAL=Feature1,Feature2]
[REMOVE=Feature1,Feature2]
If you installed Smart 3D on a computer with version 4.5.2 of the .NET
Framework installed, you must reboot your computer after installation completes.
Required Arguments
SERIALNUMBER=<serial number>
SLAACCEPT=YES
SLAACCEPT=Yes means that you are accepting the Software License Agreement.
If the PIDService feature is added, the following are also required:
NAMEGENUSERNAME=<mydomain\myuserid>
NAMEGENPASSWORD=<mypassword>
Optional Arguments
INSTALLDIR=<path to install to> The default is C:\Program Files (x86)\Smart3D
ADDLOCAL=<comma delimited list of features to install> See the table below for additional
information.
REMOVE=<comma delimited list of features to remove> See the table below for additional
information.
ADDLOCAL and REMOVE refer to user-selectable features. There are features that the
user cannot see that are automatically installed that are not referenced in the list below.
For ADDLOCAL and REMOVE, ALL can be used, as in, ADDLOCAL=ALL or
REMOVE=ALL
X64SERVICES=YES
This command line installs the product into the default location, C:\Program Files
(x86)\Smart3D. No logging file is created unless a problem occurs. If a problem occurs, a
logging file with a brief description of the problem is created in the Temp folder.
[Link] SERIALNUMBER=12345678901234 SLAACCEPT=Yes
This command line installs the product into location, D:\Program Files\Smart3D.
[Link] SERIALNUMBER=12345678901234 SLAACCEPT=Yes
INSTALLDIR="D:\Program Files\Smart3D"
This command line installs all features, including PIDService into the location, D:\Program
Files\Smart3D.
[Link] SERIALNUMBER=12345678901234 SLAACCEPT=Yes
INSTALLDIR="D:\Program Files\Smart3D" ADDLOCAL=ALL
NAMEGENUSERNAME=<mydomain\myuserid> NAMEGENPASSWORD=<mypassword>
This installs all of the features listed above except PIDService into the location D:\Program
Files\Smart3D.
[Link] SERIALNUMBER=12345678901234 SLAACCEPT=Yes
INSTALLDIR="D:\Program Files\Smart3D" ADDLOCAL=ALL REMOVE=PIDService
This command line removes the software with no user interaction but displays the progress on
screen.
[Link] UNINSTALL
This command line installs all features with Smart 3D except for the 64-bit service.
[Link] SERIALNUMBER=12345678901234 SLAACCEPT=Yes
ADDLOCAL=ALL
This command line installs all features with Smart 3D including the 64-bit service.
[Link] SERIALNUMBER=12345678901234 SLAACCEPT=Yes
ADDLOCAL=ALL X64SERVICES=YES
Citrix Installations
If you are installing Smart 3D in a Citrix environment, you need to be aware of the following.
Windows stores system path statements for individual executable files under the following
registry path (depending on the platform):
32-bit O/S: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\App_name.exe
64-bit O/S: HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App
Paths\App_name.exe
When a program registers an application path this way, Windows adds the path statement to the
search path whenever the application is run. This path information becomes part of the System
Search Path search order.
When applications are launched through Terminal Services (or Citrix), these path statements
are not automatically added. If an application requires this path, then the path information from
the appropriate AppPath registry key must be added to the path variable of the System
Environment.
Ensure that you back up the current value of the system path to a file for later
reference if there is an issue. Making a mistake during the modification of the system path
variable can render the computer unusable. It is essential to know the path contents prior to the
modification to bring the computer back with any real confidence if there is a problem.
1. In the Registry, copy the data of the Path value for the application executable:
32-bit O/S: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Paths\App_name.exe
64-bit O/S: HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App
Paths\App_name.exe
6. Paste the value data from the Registry to the end of the Path string.
Hardware Requirements
For optimal performance, the following minimum hardware requirements are recommended:
2.8 GHz Pentium® 4 processor or higher
Minimum of 1 GB memory
100 BaseT or higher network interface
Minimum of 5 MB hard drive disk space on the drive where Name Generator Service is
installed
Prerequisite Software
For optimal performance, the following minimum software requirements are recommended:
For large installations: Microsoft Windows Server 2012 R2
or
For small installations: Windows 10 64-bit (maximum 20 connections)
Microsoft .NET Framework 4.5.2 or later
Adobe Acrobat Reader
32-bit or 64-bit Oracle Client if you are using Oracle as your database
If you are installing Smart 3D Reference Data on a computer running Windows Server 2012
R2, enable the COM+ Network and DTC access, and then add the necessary users to the
Distributed COM Users group.
If you are installing the Name Generator Service on the database server computer, you must
register the Microsoft SQL Server, see Register the Microsoft SQL Server.
If you are installing the Name Generator Service on an Oracle 32-bit Client computer, the
computer must be configured to access the Oracle database server through Net Manager.
You must install the 32-bit Name Generator if you are using a 32-bit Oracle client.
Installing the 32-bit Name Generator with 32-bit Oracle Client on a 64-bit Oracle server
causes slower database performance.
You can install the 32-bit Name generator on 64-bit workstations with 32-bit Oracle client
loaded.
The Name Generator Service works when installed on 64-bit Oracle database servers. We
recommend that if you are running Oracle 64-bit on a 64-bit server, install the 64-bit Name
Generator.
After installing the Name Generator Service, the firewall on that computer must be
configured to allow DCOM Dynamic Ports. For more information, see Configure the Firewall
to Allow DCOM Communication in Windows Server (on page 95).
3. Expand the Component Services node under the Console Root, and then expand the
Computers and My Computer nodes.
6. Select COM+ Applications under the My Computer node, and then click More Actions >
New > Application.
7. Click Next on the Welcome to the COM Application Install Wizard page.
8. Select Create an empty application on the Install or Create a New Application page.
9. On the Create an Empty Application page, type S3DNameGenerator in the Enter a name
for the new application text box.
10. Select Server application as the Activation type, and then click Next.
11. On the Set Application Identity page, select This User:, and then enter the user name and
password to set the proper identity under which the COM+ application will run on the
computer. Click Next.
You must specify an account with Windows administrative privileges on the computer.
If you are configuring the Name Generator Service on a computer on which Microsoft
SQL Server is installed, the user account must also be a SQL Server Login that has a
system administrator role in SQL Servers; otherwise, the Name Generator Service will
not run. For information about creating a SQL Server Login and assigning administrator
privileges, see Register the Microsoft SQL Server.
12. On the Add Application Role page, select CreatorOwner in the Roles list, and click
Remove.
13. Click Next.
14. Click Finish to begin the installation.
When the installation is complete, a S3DNameGenerator node is placed under
COM+ Applications.
24. Enter the user and password to set the proper identity under which the COM+ application
will run on the computer.
You must specify an account with Windows administrative privileges on the computer.
If you are configuring the Name Generator Service on a computer on which Microsoft
SQL Server is installed, the user account must also be a SQL Server Login that has a
system administrator role in SQL Servers; otherwise, the Name Generator Service will
not run. For information about creating a SQL Server Login and assigning administrator
privileges, see Register the Microsoft SQL Server.
25. Click Apply.
26. Select the Security tab.
27. Under Authorization, clear the Enforce access checks for this application option if
selected.
28. Click OK to complete the configuration procedure.
29. Configure MSDTC. For more information, see Configure Microsoft Distributed Transaction
Coordinator (on page 94).
See Also
Name Generator Service Setup (on page 86)
12. Click Yes if you are prompted to stop and restart the MSDTC service.
SharedContent Share
Create a share for the SharedContent folder that is created during the Reference Data setup. All
users must be granted read permissions on the share; those users responsible for creating
output and reference data must have write access. You will need to specify this location name
when you use the Database Wizard to create the Site and Catalog databases.
Additionally, if you installed Reference Data in the default folder (C:\Program Files
(x86)\Smart3D\3DRefData\), you must adjust access permissions as follows:
Access the Properties page for the SharedContent folder and modify the share permissions
on the Sharing tab. At a minimum, permissions must allow read access for all users, and
write access to those users responsible for creating output.
Access the Properties page for the SharedContent folder and modify the share permissions
on the Security tab to give users full control disk access for the SharedContent folder and
subfolders.
See Also
Reference Data Setup (on page 97)
You can create hierarchy folders as needed under the Custom Symbols folder.
If a custom .dll has a localizer .dll, both files must be located in the same folder.
.dlls ending with "–Ref..dll" or "_Ref..dll" are treated as reference .dlls and are ignored.
Do not copy these .dlls from the client machine containing the Visual Basic source code.
3. Run Tools > Update Custom Symbol Configuration.
Create or update the custom symbol configuration file
Whenever a symbol or naming rule class is accessed, the software searches for the .dll as
follows:
a. The software checks for the ProgID entry in the xml files. If an entry exists, then the
corresponding .dll is loaded, and an instance of the class is created.
b. If an entry does not exist, the software searches previously registered .dlls on the local
computer.
c. If any entry is not found for the ProgID in either .xml file, and the .dll is also not
registered on the local machine, the software returns an error. In this case, you should
copy the .dll to the [Reference Data Folder]\SharedContent\Custom Symbols folder and
run Update Custom Symbol Configuration in Project Management.
If a ProgID entry exists in the .xml files, that .dll is used even though another or the same
copy of the .dll is registered on the local machine. The order of priority when creating an
instance of an object is: [Link], [Link], and then the
registry.
When you add a new custom .dll to the [Reference Data Folder]\SharedContent\Custom
Symbols folder or modify an existing custom .dll, you must re-run Update Custom Symbol
Configuration in Project Management.
If a Visual Basic 6 component uses helper classes, and the helper classes are instantiated
by calling CreateObject, you must replace CreateObject. If the helper class is in the
same project, then replace it with new. If the helper class is in a different project, then
replace it with SP3DCreateObject. SP3DCreateObject tries to instantiate the object
using the information in .xml files. If the software does not find an entry in .xml files for the
given ProgID, then it calls CreateObject, and implements SP3DCreateObject in the
[Product Folder]\Core\Runtime\SP3DCoCreateInstance..dll. When SP3DCreateObject
needs to be used, [Product Folder]\Core\Runtime\[Link] needs to be
referenced in the Visual Basic project. Example usage of SP3DCreateObject is shown
below:
Set oHelperObject = SP3DCreateObject(strHelperProgId)
If the Visual Basic 6 symbol class has any public structures or types, they should be made
private. For example:
Public Type InputType
Name As String
Description As String
Properties As IMSDescriptionProperties
uomValue As Double
End Type
Should be changed to:
Private Type InputType
Name As String
Description As String
Properties As IMSDescriptionProperties
uomValue As Double
End Type
Debugging and maintaining Visual Basic project references, reference .dlls, and binary
compatibility are beyond the scope of this document. Contact your Intergraph Support
representative if you have questions.
Catalog database. Included with the Symbol Wizard, is a Visual Basic add-in called the
Equipment Symbol Upgrade Wizard. This wizard allows you to upgrade Smart 3D version
5.0 Equipment symbols to Smart Occurrence-based equipment symbols.
References Helper - Locates and references type libraries quickly and easily. The ability to
reference a type library with this tool saves valuable time otherwise required when searching
via Project > References in your Visual Basic project.
Programming Help - Installs the Programming Help online documentation on the local
computer.
Example Code - Provides source code necessary for creating custom Visual Basic
commands for Smart 3D. Also includes source code for customizing Visual Basic reference
data rules and symbols. These rules are bulkloaded into the catalog.
Debug Code for Task Host - Runs your Smart 3D Visual Basic project in debug mode.
.NET Programming - Installs .NET Microsoft Visual Studio integrated programming help
and examples.
In order to display the .NET documentation delivered with .NET Programming,
you must use the Visual Studio Help Library Manager to configure the Microsoft Help
Viewer.
3D Schema Browser - Displays the metadata and the relationships in the software.
During installation, the software registers the wizard on the client computer. The wizard
can be accessed from the Add-Ins menu in the Visual Basic application.
A Visual Basic add-in called the Equipment Symbol Upgrade Wizard is also delivered
during installation of the SmartPlant 3D Symbol/Part Definition Wizard. The Equipment
Symbol Upgrade Wizard allows you to upgrade Smart 3D version 5.0 Equipment
symbols to Smart Occurrence-based Equipment symbols. For more information about
registering and launching the Equipment Symbol Upgrade Wizard, see the SmartPlant
3D/SmartMarine 3D Programmer's Guide available from Help > Printable Guides in the
software.
See Also
Programming Resources Setup (on page 100)
Create Databases
Administrative privileges are required to create databases. Do not proceed unless you are an
administrator on the database server computer and in the database provider software.
Management Help and the Catalog Help files. These help files are delivered in C:\Program Files
(x86)\Smart3DDocumentation\Help on the workstation computer.
For creation date and size information on each database, in Microsoft SQL Server you can open
the SQL Server Enterprise Manager. This software also provides further technical details about
the relational tables in each database.
The following illustration shows the relationships of the databases:
These databases are created on a central server using the Database Wizard on a workstation
computer on which the Project Management and Server Connectivity options are installed.
4. From the Site database server list, select the database server on which your Site database
will reside.
Only registered SQL Servers appear in the Site database server list. If your server
does not appear, follow the steps in Register the Microsoft SQL Server.
5. Enter the name of your Site database in the Site database name text box. Include the type
of database in the name that you type. For example, type MySiteDB, My_SDB, or
ProjectXYZ_SDB, where SDB stands for Site Database. Using the database type in the
name makes identifying the Site database in SQL Server Management Studio easier. You
must name the databases with unique names.
When you name the Site database, the Site schema server and Site schema
name boxes default to match the Site database server and name.
6. Enter the workshare location for the Site database in the Site database workshare
location text box. You can use any string that represents your physical location.
This location is the location of the host Site database and is required even if the
host is not going to be replicated for worksharing purposes. During generation of the Site
database, the software creates a location object and associates it with the Site database.
7. Enter a name rule ID in the Name rule ID text box. By default, the software leaves this field
blank. You can enter any string identifier, numeric or alpha.
The Name Generator Service that runs on the server computer you specify in the
Name generator server for site box (step 8) supplies unique names to items placed in the
Model database. In a replicated configuration, there are multiple servers and multiple
instances of the Name Generator Service running at each location; consequently, there is
no way to ensure unique and sequential naming of placed objects. The value entered in the
Name rule ID text box functions as a substring (an internal ID number) that represents the
location at which an item is placed into the replicated model.
8. Enter the name of the server computer on which the Name Generator Service is configured
in the Name generator server for site box.
A name server must be a valid computer running on the Windows domain and
one that has been properly configured to run as a name server. If you do not have a name
generator server set up, see Name Generator Service Setup (on page 86).
9. You cannot change the default locations for the site database files in the Physical database
and Log file boxes.
10. Click Browse to the right of the Template file to be used to create site schema text
box.
The Browse for file on server: database_server_name dialog box appears.
11. If you installed the Reference Data on your database server, browse to the Plant, Marine, or
MaterialHandling folder in the [Installation folder for Smart 3D Reference
Data]\DatabaseTemplates file path.
If you did not install the Smart 3D Reference Data on your database
server, you must copy the files in the Plant, Marine, or MaterialHandling folder in the
[Installation folder for Smart 3D Reference Data]\DatabaseTemplates file path on the
reference data computer to a folder on a local drive on the database server computer.
12. Select the [Link] file, which is used by the software when creating your Site schema
database.
13. Click Next.
The Catalog Database and Schema page displays.
14. Select whether you want to use an existing catalog or restore a catalog from backup.
The Use existing catalog created in Project Management or Bulkload option to use
an existing Catalog that is already available. If you intend to create a custom catalog,
select this option and use the Bulkload utility delivered with the product. If you have
used previous versions of Smart 3D, more than likely this is the option that you want. If
you select this option, skip to step 20.
The Restore catalog from backup option restores a catalog from a Microsoft SQL
Server backup file. If you choose to create a new Catalog database for the site using
this option, the wizard will restore the .DAT file specified in the Template file to be
used to create the Catalog database and schema box. Default Catalog database .dat
files are delivered in the Plant, Marine, or MaterialHandling folder in the [Installation
folder for Smart 3D Reference Data]\DatabaseTemplates file path with the Reference
Database installation.
The [Link], SM_ShipCatalogDB.dat, and MHE_CatalogDB.dat
template files contain sample Smart 3D reference data and, while the templates contain
many useful examples, they are not certified for production use by Intergraph.
15. Select the name of the database server in the Catalog database server list on which your
Catalog database will reside.
Again, only registered Microsoft SQL Servers appear in the Site database server
list. If your server does not appear, follow the steps in Register the Microsoft SQL Server.
16. Enter the name of your catalog database in the Catalog database name box. This step also
automatically populates the name of your Catalog schema database in the Catalog schema
name text box. Include the type of database in the name that you type. For example, type
MyCatalogDB, My_CDB, or ProjectXYZ_CDB, where CDB stands for Catalog Database.
Using the database type in the name makes identifying the Catalog database in SQL Server
Management Studio easier.
17. Select the ellipsis button to the right of the Symbol and custom program file folder box,
and browse for and select the SharedContent share on the Smart 3D reference data
computer. If you did not create this share already, see Configure Network Shares (on page
97).
The path in the Symbol and custom program file folder box must be a UNC
path (\\server_name\share_name). To obtain a UNC path, click the ellipsis button and
browse under Network, not under Computer.
18. Select the ellipsis button to the right of the Template file to be used to create catalog
database and schema text box and browse for the name of the catalog template file that
you want the software to use when creating your Catalog and schema databases. If you
installed Reference Data on your database server, browse to the Plant, Marine, or
MaterialHandling folder in the [Installation folder for Smart 3D Reference
Data]\DatabaseTemplates file path.
If you did not install the Reference Data on your database server, you must copy the files in
C:\Program Files (x86)\Smart3D\3DRefData\DatabaseTemplates on the reference data
computer to a folder on a local drive on the database server computer.
19. You cannot change the default locations for the catalog database files in the Physical
database and Log file boxes.
20. Click Next.
21. On the Ready to Load Databases page, click Next to create your databases.
22. When the Database Wizard displays the database names that you entered, click Finish.
8. Click Load to bulk load the Structural Manufacturing custom classes into the site.
Length Between Perpendiculars – Length (along the x-axis) between the Aft
Perpendicular (AP) and the Forward Perpendicular (FP).
Breadth – Total width of the hull (along the y-axis).
Depth Molded – Depth (along the z-axis) from the molded baseline to the upper deck
level (freeboard); measured at midship.
Design Draught Molded – Height (along the z-axis) from the baseline to the design
waterline. The design waterline is based on the operational load of the ship.
Starting Point of Rise of Floor – Distance (along the y-axis) from the centerline to the
start of the Floor Rise at midship.
Rise of Floor – Distance (along the z-axis) from the baseline to the floor at the
beginning of the bilge radius.
Radius of Bilge Circle – Radius of the bilge.
Start Point of Parallel Part – Distance (along the x-axis) from the Aft Perpendicular to
the start of the parallel midbody.
End Point of Parallel Part – Distance (along the x-axis) from the Aft Perpendicular to
the end of the parallel midbody.
Midship or position at Maximum Breadth – Midship frame along the x-axis for a ship
with a parallel midbody, or the midship frame along the x-axis where maximum breadth
occurs for a ship without a parallel midbody.
X Position of AP – Position of the Aft Perpendicular frame along the x-axis at the
transom above the waterline.
X position of FP – Position of the Forward Perpendicular frame along the x-axis at the
bow above the waterline.
Ship Type – Any text string for ship type, such as FPSO or LNG.
Linking Servers
The Linked Servers option in Microsoft SQL Server Management Studio allows you to connect
to another instance of SQL Server running on a different server.
If you have two or more database servers (target database servers) then you need to link them
to the source database server. This allows Copy by Family in the Molded Forms task to support
retrieving or copying data from different servers.
Test Connection
Right-click the target database server that you linked to the source database server, and
select Test Connection from the shortcut menu.
"The test connection to the linked server succeeded." dialog box is displayed.
10. Select User Mapping under the Select a page heading to display the Users mapped to
this Login list.
11. Select the Map check box for one of the seven databases containing a Smart 3D project.
12. For an administrator user, select db_owner and public as the database roles on the
Database role membership for list.
-OR-
For a standard user, select public, db_datareader, and db_datawriter as the database
roles on the Database role membership for list.
13. For a standard user, right-click on the database name and select Properties.
a. Select the user login and on the Permission for, select the Explicit tab and grant
Execute.
b. Select the Effective tab and check that the standard user has the permission:
CONNECT, DELETE, EXECUTE, INSERT, SELECT, UPDATE permissions.
The six permissions above are required. User might have additional permissions
but they are not required for a Smart 3D standard user.
14. Repeat the procedure for each of the remaining six databases.
15. Click OK.
See Also
Create Databases (on page 105)
To better differentiate between one database and another, include the type of database
in the name you type. For example, type Model1SiteDB.
Do not use a name which starts with a digit as its first character. For example, if you
enter a name such as 1ModelSiteDB, Oracle will not create the database.
When you name the Site database, the Oracle service (for the Site schema) and Site
schema name default to match the Oracle service for the Site database and the Site
database name.
6. Enter the workshare location for the Site database in the Site database workshare
location text box. You can use any string that represents your physical location.
This location is the location of the host Site database and is required even if the
host is not going to be replicated for worksharing purposes. During generation of the Site
database, the software creates a location object and associates it with the Site database.
7. Enter a name rule ID in the Name rule ID text box. By default, the software leaves this field
blank. You can enter any string identifier, numeric or alpha; however, special characters are
not supported.
The Name Generator Service that runs on the server computer supplies unique
names to items placed in the Plant (Model database). In a replicated configuration, there are
multiple servers and multiple instances of the Name Generator Service running at each
location; consequently, there is no way to ensure unique and sequential naming of placed
objects. The value entered in the Name rule ID text box functions as a substring (an internal
ID number) that represents the location at which an item is placed into the replicated Plant.
8. In the Name generator server for site box, type the name of the server computer on which
the Name Generator Service is installed.
A name server must be a valid server running on the Windows domain and one
that has been properly configured to run as a name server.
9. Use the default paths for the site database files in the Data tablespace file name and
Index tablespace file name boxes.
10. Click Browse to the right of the Template file to be used to create site schema text
box to browse for the name of the dump file ([Link]) the software uses when
creating your Site schema database. The location of the file is on the reference data
computer at \\[Server
Name]\DatabaseTemplates\[Plant\Marine\MaterialHandling]\[Link].
11. Click Next.
12. On the Catalog Database and Schema page, select the name of the Oracle net service for
the Catalog database connection in the Oracle service list.
The option control at the top of the page allows you either to create a new Catalog
database by restoring a backup or use an existing Catalog database. If you choose to
create a new Catalog database using the Restore option, the wizard will restore the
.dmp file specified in the Template file to be used to create the Catalog database
and schema field. Depending on your model, the selections are [Link],
SM_ShipCatalogDB.dmp, or MHE_Catalog.dmp. The default is to Restore catalog
from backup. If you select Use existing catalog, then no further options are available.
If you intend to create a custom catalog, you must select the Use existing catalog
option and use the Bulkload utility delivered with the product.
The [Link], SM_ShipCatalog.dmp, and MHE_CatalogDB.tmp
template files contain sample Smart 3D reference data and, while the templates contain
many useful examples, they are not certified for production use by Intergraph.
13. Enter the name of your catalog database in the Catalog database name box. This step also
automatically populates the name of the Catalog schema database in the Catalog schema
name text box.
14. Use the default paths for the catalog database files in the Data tablespace file name and
Index tablespace file name boxes.
15. Click Browse to the right of the Symbol and custom program file folder box to browse for
and select the SharedContent share on the Reference Data computer.
The SharedContent share must be created after installing Reference Data. For more
information, see Configure Network Shares (on page 97).
The path in the Symbol and custom program file folder box must be a UNC path. To
obtain a UNC path, click Browse and browse under Network, not under Computer.
16. Click Browse to the right of the Template file to be used to create catalog database and
schema text box to browse for the name of the dump file ([Link],
The software delivers two log files - one for the Site database generation process and one
for the Catalog database restore process - on the server computer at the local user %temp%
folder.
You must name the databases with unique entries.
During the Site database creation process for an Oracle plant, the software attempts to
connect to the Site database to create the user interface prior to generating the views,
resulting in a "table or view does not exist" error being reported in the various log files. Since
views are generated after the user interface is created, these errors cannot be avoided.
Additionally, these errors do not have any negative impact on using the software and can be
disregarded when reviewing the log files.
Intergraph recommends that you increase and/or redefine initial tablespace values based on
the expected scope of your project(s). For more information, see your Oracle
documentation.
See Also
Create Databases (on page 105)
Cable [Link]
[Link]
[Link]
[Link]
[Link]
Cableway [Link]
[Link]
[Link]
[Link]
Conduit [Link]
[Link]
[Link]
MatingPort Sheet
GenericDataPipingFemale Sheet
PlainPipingGenericData Sheet
Electrical [Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link] for designed equipment
Standard Nozzle [Link] for designed equipment
Ten_Specs_CatalogData.xls
Grids [Link]
[Link]
[Link]
Apart from these workbooks, you must load the parts and
assembly workbooks that you intend to use.
HVAC [Link]
[Link]
[Link]
[Link]
[Link]
Carnes HVAC [Link] for Carnes HVAC parts
Lindab HVAC [Link] for Lindab HVAC parts
Spiral HVAC [Link] for Spiral HVAC parts
Interference [Link]
Checking
[Link]
[Link]
Piping [Link]
[Link]
[Link]
[Link]
Ten_Specs_SpecificationData.xls
Ten_Specs_CatalogData.xls
Space [Link]
Management
[Link]
[Link] for volumes
[Link]
[Link]
Structure [Link]
[Link]
[Link]
[Link]
[Link]
[Link]
[Link]
Marine Workbooks
The marine-specific Excel workbooks are located at [Product
Folder]\ShipCatalogData\BulkLoad\DataFiles.
SM_CopyByFamilyRules.xls Identifies the rules which determine the value of the physical
connection attributes to be propagated to the target based
on the family. Examples of physical connection attributes
are RefSideSecondBevelMethod and
RefSideSecondBevelDepth.
SM_SquareEdgeTrimRules.xls Defines the rule for controlling square edge trim, which is
mostly used for parts generated for materials handling.
SM_StructPalettePath.xls Defines the .xml files that determine the hierarchy of catalog
browsers related to openings, brackets, APS plates, and
SeamOrProfile members.
In addition, some of the marine tasks deliver reference data in their Data folders (for example,
[Product Folder]\ShipCatalogData\BulkLoad\DataFiles\Compartmentation). The following table
lists these files and a brief description of them.
Molded Forms stiffener import-export [Link] Defines molded forms rules for
stiffeners.
Right-click the model database in the Project Management tree view, and then select
Regenerate Reports Database. For more information on regenerating a reports database,
see Regenerate the Reports Database.
The database upgrade runs in multiple processes to improve the performance, and is
applicable only for model databases for the current software version. The model upgrade log file
displays the number of processes. For example, "5-5-2016 4:48:59 PM Executing Parallel
MTMC Processing with 4 Processors."
Most of the commands that provide access to SmartPlant integration functionality exist on the
SmartPlant menu in the various Smart 3D task environments. For example, in the Drawings
and Reports task, you can use the commands on the SmartPlant menu to publish orthographic
drawings, 3D model data, isometric drawings, and reports. You can also use the SmartPlant
menu to access the SmartPlant Foundation Web Client in order to browse in SmartPlant
Foundation and subscribe to change notifications and compare documents. In other Smart 3D
tasks, you can use the SmartPlant menu commands to correlate items between the Model and
the SmartPlant Foundation database and retrieve P&IDs, DDP files, Cable Schedules, Plant
Breakdown Structure and Work Breakdown Structure, and Project Lists.
For detailed information about using the SmartPlant integration commands found in Smart 3D,
see the Common User's Guide and the Orthographic Drawings User's Guide. Both documents
are available with the Help > Printable Guides command in the software.
For more information about configuring Smart 3D to work in an integrated environment, see
Configure for an Integrated Environment (on page 134).
Install SmartPlant P&ID first if you plan to install SmartPlant P&ID and Smart 3D on the
same computer.
When installing the Piping Specification Remote Access Server component, you must also
install the Bulkload Reference Data and the Server Connectivity components as they are
required for the Piping Specifications Remote Access Server to work.
Verify that the Distributed Transaction Coordinator service is enabled before installing the
Piping Specification Remote Access Server.
In order to use Piping Specification Remote Access you must perform additional installation
and configuration on the computers running SmartPlant P&ID. See the Installing Smart 3D
Piping Specification Remote Access Client section in the SmartPlant P&ID Installation and
Upgrade Guide for more information about installing the Smart 3D Piping Specification
Remote Access Client. Also, see the Piping Specification Utility section in the SmartPlant
P&ID Utilities Guide for additional configuration information.
The "server" used by the Piping Specification Remote Access Client and the SP3D P&ID
Client Tester application is the computer on which the Piping Specification Remote Access
Server COM+ application has been installed and configured. This server can be different
from the database server on which the Site database server and Site schema server reside.
For more specific information about using the SmartPlant P&ID integration functionality included
with the software, please contact Intergraph Support ([Link]
See Also
Configure the Piping Specification Remote Access Server Service (on page 139)
Register the Site Database for P&ID Access (on page 143)
You must have administrator privileges on the computer in order to perform this installation
procedure.
You must perform this procedure if you have installed Smart 3D on a server operating
system, such as what happens in a Citrix environment.
The Piping Specification Remote Access Server service is installed as part of the Smart 3D
Installation setup. You must also install the Bulkload Reference Data and the Server
Connectivity components as they are required for the Piping Specifications Remote Access
Server to work. For more information, see Install Smart 3D Client Software (on page 78).
The computer on which you have installed the Piping Specification Remote Access Server
becomes a "server" for SmartPlant P&ID clients and therefore must be powered on and
available whenever P&ID needs to access the catalog. For example, you could use the
computer that is used for the Interference Checking service.
If you are installing Smart 3D Reference Data on a computer running Windows Server 2012
R2, enable the COM+ Network and DTC access, and then add the necessary users to the
Distributed COM Users group.
3. Expand the Component Services node under the Console Root, and then expand the
Computer and My Computer nodes.
6. Select COM+ Applications under the My Computer node, and then click Action > New >
Application on the horizontal toolbar. The COM+ Application Install Wizard displays.
7. Click Next on the Welcome to the COM Application Install Wizard page.
8. Select Create an empty application on the Install or Create a New Application page.
9. On the Create an Empty Application page, type SP3DPipingSpecRemoteAccessServer
in the Enter a name for the new application text box.
10. Select Server application in the Activation type field, and then click Next.
11. On the Set Application Identity page, verify that This user is selected, and enter user
name and password to set the proper identity under which the COM+ application will run on
the computer.
18. On the Security tab, disable Enforce access checks for this application and click OK.
4. In the Set Site Database for Piping Spec Remote Access dialog box, enter the Site and
Site schema database names and servers in the appropriate fields.
5. Click OK.
In order to use Piping Specification Remote Access you must perform additional installation
and configuration on the computers running SmartPlant P&ID. See the Installing SmartPlant
3D Piping Specification Remote Access Client section in the SmartPlant P&ID Installation
and Upgrade Guide for more information about installing the SmartPlant 3D Piping
Specification Remote Access Client. Also, see the Piping Specification Utility section in the
SmartPlant P&ID Utilities Guide for additional configuration information.
The "server" used by the SmartPlant 3D Piping Specification Remote Access Client and the
SP3D P&ID Client Tester application is the computer on which the SmartPlant 3D Piping
Specification Remote Access Server COM+ application has been installed and configured.
This server can be different from the database server on which the Site database server and
Site schema server reside.
See Also
Integrating with SmartPlant P&ID (on page 137)
4. After the installation is complete, you must enter your login credentials for SmartPlant
Reference Data Client.
5. You can either use an existing login from the Current Logins tab, or you can create a new
login from the New Login tab.
For more information, see the SmartPlant Reference Data Installation Guide (.NET) available on
the SmartPlant Enterprise Reference Data installation page.
Install Smart 3D and all of its components in a folder with a short path that does not contain
any spaces.
Set up the SmartPlant Reference Data listener for default mode running.
Database detection options are set in the Project Management task. You can also start and stop
the interference database detection process in the Project Management task.
Interference detection requires disk space for the file cache that temporarily stores the
interference data. Before starting the interference process, the interference server checks to see
if enough space exists in the TMP location for the file cache. The server also checks to see if
you have the proper permissions to write, read, and delete files in the TMP location. During the
process, if the space becomes too low, the software stops IFC, and then displays an error
message. These checks primarily apply to the server-based interference process. Although,
they can apply to the local checking process if extremely low or no disk space is available for the
temporary folder on the local computer.
Configure automatic disk defragmentation in order to free space for the file
cache.
After you start the process, use the Status tab on the Interference Server Settings dialog box
to monitor the start time, progress of the interference checking, time when the last part was
modified, and the status of the checking. A box at the top of the dialog box identifies the model
that you are checking.
The software automatically checks new or modified objects apart from existing objects. When
you create or modify an object, the software checks for interference against all objects in the
Model database. The interferences generated by this process are persistent; that is, the
interferences are stored in the database like any other objects in the software. You can also
modify these objects by changing the properties. Interferences are also assigned to a
permission group; thereby the entire process is under the control and restrictions of an
administrator.
You can interrupt the automatic interference checking process during a work session without
forcing a recheck of all parts in the database when the process is brought back online. When
you restart the interference check process, the software begins checking where it left off when
the process went offline. However, if you change any of the options on the Interference Server
Settings dialog box for Database Detect, all pre-existing interference checking processes are
cleared from the database, and checking restarts from the beginning.
The server-based interference checking runs continuously. Therefore, you can perform an
interference check at any time and view the interferences of interest that result from the
background check by refreshing the workspace. After you have reviewed the interferences, you
can remove an interference automatically from the database by editing the objects so that the
interference no longer exists. You can then see the results of your edit by refreshing the
workspace. Because certain types of interferences are allowable, you also have the capability to
mark such interferences as acceptable.
Be aware that there is a four minute interval between the time you make your edits and the time
that the database detect service rechecks the objects. After the database detect process
reaches 100%, the software issues a query only every two minutes to locate newly modified
objects. Therefore, it is possible that there is a six minute delay before a modified object is
processed. We do not recommend changing the default four minute interval. However, if you are
in Project Management with the Interference Server Setting dialog box open, press
CTRL+SHIFT+F12 to change the default four minute interval.
You must run the Database Detect process before running an interference report. The
report is not intended to run on local interferences.
The interference checking service does not consume a license when it starts. It consumes a
license only while processing the model. For more information, see Checking Interferences.
Errors that are encountered during startup of the Database Interference Detection service
are logged to the Event Viewer Application Log with the source name IFCNTSvc. The
service can automatically recover from these situations:
network interruptions
lost database connection
the interference checking process runs out of memory
the interference checking process or service is terminated for any reason
Do not run the 32-bit and 64-bit interference detection services simultaneously on a
computer. IFC must only run as a single instance for the entire model.
You can also click Add and search for users using the Select Users and Groups
dialog box. This is a common Windows dialog box. For information regarding the
options in this dialog box, see your Windows documentation.
To remove a user or group from the Add names grid, select the appropriate row, and
then click Remove.
6. In the Type of access list, select the type of access you want to assign. The software
automatically updates the associated row in the Add names grid.
7. Click OK.
8. Click OK again to close the Access Permissions dialog box.
1. In the Project Management tree, right-click the Interference Server icon under the
model for which you want to start Database Detect. Then select Properties on the shortcut
menu.
2. In the Interference Server Settings dialog box, assign interference checking priorities to
aspects.
Maintenance, for example, is a typical aspect listed in the Aspect column. If a
check of this aspect is important, you can indicate the priority as Required. If Maintenance
is low priority or not important, you can indicate the priority as Optional or Not Checked.
3. Specify the interference comparison criteria:
Required - Required - Defines interferences classified as hard/hard. For example, one
pipe physically intersects with another pipe. Severe interferences are shown in red.
Required - Optional - Defines interferences that are not as severe and are classified as
hard/soft. For example, one pipe overlaps the optional aspect of the other object.
Optional interferences are shown in yellow.
Optional - Optional - Defines interferences that are not severe and are classified as
soft/soft. For example, the maintenance aspect of one piece of equipment overlaps the
maintenance aspect of another. Optional interferences are shown in yellow.
Smart 3D - External Data - Considers objects outside the active model for
interferences. For Local Detect, this option is enabled by default. For Database Detect,
this box must be checked if you want attached Reference 3D models, inserted
MicroStation and AutoCAD files to be considered. This option only checks objects
against objects in external references and also checks for interferences between two
external R3D objects.
Smart 3D - Point Cloud - Considers Smart 3D objects and point cloud objects for
interferences. For Database Detect, this option must be selected to consider Smart 3D
objects and point cloud objects. For Local Detect, select the Smart 3D Point Cloud
check box to consider local interferences. The point cloud must have a valid connection
to the model with no unresolved vendor licensing issues for this check box to be
available.
4. In the Include clearance list, select the needed clearance rule. Clearance interferences are
shown in green.
5. From the Assign results to permission group box, choose the permission group to which
all the detected interferences are assigned.
6. In the Marker size field, type the value for the size of the interference symbols that generate
in the model.
Choose a marker size that is clearly readable, but one that does not interfere with
the smaller details in the workspace view.
7. Click Start on the Database Detect tab. After you click Start, the Status tab on the
Interference Server Settings dialog box displays the progress of the processing for parts
that existed previously and for new or changed parts during the run.
If the IFC Server detects that your system resources are too low (due to a
significant process requiring the majority of system memory), then the IFC process stops and
displays a message box notifying you that the service has stopped for this reason. The IFC
process will automatically attempt to restart when it runs out of memory.
The Smart 3D Interference Detection service does not consume a license when it starts. It
consumes a license only while processing the model. For more information, see
To start the server interference detection process, you must have at least Read access to all
objects in the model and Write access to the model itself. Access privileges are assigned for
each permission group in the Project Management task. During the IFC process, if the
software denies access to an object, the server process stops and a message appears.
To view the status of the database interference detection process, right-click the
Interference Server icon in the Project Management tree, and click Properties. On the
Interference Server Settings dialog box, click the Status tab.
When the database interference check process is running, only the Stop command is
available. When the process is not running, the Start command and all process property
gadgets are available. The Stop command is not available.
When the database interference check is running and you add any permission group without
Read permissions for the server, the server automatically receives Read permissions and
finds collisions with the placed objects in that permission group.
When you modify permission groups in Project Management, the host for the existing,
running task does not receive the changes. To update the information, you must exit and
restart the interference detection process.
See Also
Interference Server Settings Dialog Box (on page 153)
This option only checks active model objects against R3D external objects. IFC also
checks clashes between R3D objects belonging to different R3D projects. The
option does not check for interferences between other external objects such as
MicroStation to 3D AutoCAD.
Reference 3D models that contain tessellated data take a significant amount of time
for interference checking to process. For quicker IFC performance, set Interference
Detection to Do Not Participate.
Smart 3D - Point Cloud - Includes an attached point cloud during interference
checking. The point cloud must have a valid connection to the model with no unresolved
vendor licensing issues for this option to be available.
Include clearance rule
Specifies the clearance rule to add to the Required type of interference check.
Assign results to permission group
Specifies the permission group to which all the detected interferences are assigned. The list
displays only those permission groups to which the server containing the interference
checking software has write access.
Marker size
Specifies the size of the interference graphic marker. Choose a size that is clearly visible,
but one that does not interfere with the smaller details in the workspace view.
Start
Begins the Local Detect interference checking process. This option is only available in the
Project Management task.
Stop
Stops the Local Detect interference checking the process. This option is only available in the
Project Management task.
Elapsed time - Displays the amount of time (hour, min, sec) during which the
interference checking has been running for the new or changed parts.
Estimated completion - Displays the amount of time (hour, min, sec) estimated until
the interference checking process completes.
Process start
Displays the time (mm/dd/yyyy hh:mm:ss) the process started.
Existing parts at process start
Displays the following time information for existing parts when the process was started.
Current range to - Displays the date and time (mm/dd/yyyy hh:mm:ss) at which the
interference checking started for the existing parts.
From - Displays the date and time (mm/dd/yyyy hh:mm:ss) at which the interference
checking ended for the existing parts.
First part created - Displays the date and time (mm/dd/yyyy hh:mm:ss) at which the
first part was created in the database.
Elapsed time - Displays the amount of time (hour, min, sec) during which the
interference checking has been running for the existing parts.
Estimated completion - Displays the amount of time (hour, min, sec) estimated until
the interference checking process completes.
Status message
Displays textual information about the current status of the process on the server.
[Link]
Replaces the Interference Checking Restart functionality. The ProgID for this command is
[Link]. No arguments are required. You must first select a
model in Project Management before you can run this custom command.
This command deletes all interferences in the selected model. It then configures IFC to start in
Warm Reboot mode the next time you start IFC through the Interference Server Settings
dialog box. For more information, see Interference Server Settings Dialog Box (on page 153).
This command displays a warning that it is about to delete all interferences in the model. If you
click Yes on the warning dialog box, the command executes and then displays a message
indicating that the process is complete.
Batch Services
Smart 3D uses the Intergraph Batch Services 2010 SP1 ([Link] or later) application to
help you run large, time-consuming operations on a separate computer or during off hours,
leaving your workstations available for other tasks. Due to the intensive nature of batch
operations, using one or more computers dedicated as batch computers is recommended.
You can install both batch processing methods on any computer on which the Smart 3D client
software has been installed. You must also install the Project Management and Server
Connectivity features on your batch computers. Intergraph Batch Services is delivered on
separate media from Smart 3D and does not require a serial number.
The batch computer supports the following processes:
Updating drawings in the Drawings task
Detailing and un-detailing parts in the Structural Detailing task
Generating manufacturing parts and XML output files in the Structural Manufacturing task
Updating the Manufacturing Services Manager in the Structural Manufacturing task
Importing and exporting Structure objects
Importing Tribon XML files
Finding common parts
Generating planning joints
Running block assignments
Printing, publishing, and refreshing drawings
Updating Reference 3D models
Backing up Smart 3D databases
Restoring Smart 3D databases
6. Type your name and organization name, and then click Next.
8. Click Display. Read the license agreement, and then click Yes.
9. Review the default installation folder ($WindowsDrive:\Win32App\Ingr\Batch\).
If you plan to use this installation of Intergraph Batch Services with Plant
Design System® (PDS), do not install Intergraph Batch Services to a folder path that
contains spaces, such as c:\Program Files (x86)\Batch. Although Intergraph Batch Services
supports spaces in folder paths, PDS does not.
If you select Run all jobs as same user to configure account mapping, define the user
name and user name password under which jobs should run.
5. Click Add, and then type the username of a user into the Add Names box, or the group
name of a group, to which you want to grant privileges.
6. Specify local users and groups (on your computer) by username or group name only. Use
one of the following formats when keying in a username or group name:
domain_name\username or system_name\username
domain_name\group_name or system_name\group_name
Separate multiple users or groups with a semicolon (;).
7. Select the type of privilege you want to grant the user or group (Manager or Operator).
8. Click OK.
9. Repeat steps 5 through 8 for each user or group to which you want to grant privileges.
10. When you have finished assigning privileges to users or groups, click OK on the Server
Properties dialog box.
2. If the batch server cannot find an exact match, the batch server then searches the account
mapping entries using the job owner’s domain or computer name, with “*” (meaning any
user) as the username.
3. If no match is found, the batch server then searches the account mapping entries using “*”
(meaning any computer or domain) as the domain name, with the job owner’s username.
4. Finally, if a match still has not been found, the batch server searches with “*” as the domain
name and “*” as the username.
How you configure account mapping depends on the security needs and configuration of your
site. For more information on configuring account mapping, see Configure Account Mappings in
the Installation Guide.
3. Click OK in the confirmation box to stop and restart the Intergraph Batch Services.
Run this tool at least once on the computer on which the job needs to be submitted,
or on the computer where the job needs to be run. This tool sets some environment
variables as well as creating the batch queues.
4. Open Control Panel > Administrative Tools > Services.
5. In Services, select Intergraph Batch Server from the list, and then click Stop.
6. With Intergraph Batch Server service still selected, click Start.
7. To verify that the batch queues were created, open Intergraph Batch Manager and then
select your server in the tree view.
The WinZip application is no longer required on the batch server to compress any emailed
attachments. Compression is now done with functionality included in the Intergraph Smart
3D delivery.
This tool cannot create pipe queues. Use Intergraph Batch Services to create pipe queues.
Verify that the C:\Windows\SysWOW64\config\systemprofile\Desktop folder exists if you are
using a 64-bit or Windows Server operating system. Ask your system administrator create
the Desktop folder with full permissions if it does not exist.
Ensure that the default queue is configured for a job in Project Management, and that
the configured queue exists on all client computers.
For pipe queues, you need to add the required destinations to the queue. For more
information, see Creating and Configuring Pipe Queues in the Smart 3D Intergraph
Batch Services User’s Guide.
Optional Queues
Displays the Configure Optional Queues dialog box.
Configure Optional Queues Dialog Box
Maximum Allowed Time
Specifies the maximum allowed time to process a job type in the queue. If the job is not
completed in the allowed time, it terminates and the software sends a time-out notification to
the mailing list specified at the time that you submitted the job. By default, the Maximum
Allowed Time is not specified, and the job runs without any time limit. To specify a
Maximum Allowed Time, you must first select Is TimeOut Supported.
When queue times are defined on the Configure Optional Queues dialog box, Maximum
Allowed Time displays the total of those times.
Set a value for Maximum Allowed Time that allows enough time for each job to
execute.
If a job is submitted on a pipe queue but is executed on a different queue, the
Maximum Allowed Time for the job is read from the submitted pipe queue.
Is TimeOut Supported
Enables Maximum Allowed Time functionality. This option is not selected by default.
You can create custom batch jobs. For more information, see Creating and
Scheduling Custom Batch Jobs in the Smart 3D Reference Data Guide.
The printer name on the client computer must match the printer name on the batch server.
Every mapped account must open Microsoft Excel once on every batch server.
Microsoft Excel must have the same security settings that are necessary for interactive
updates. Excel must be configured correctly for every IBS-mapped account on the batch
server.
You must add the following entries to the system path for 3D model data documents to
update:
[Product Folder]\Core\Runtime
[Product Folder]\GeometryTopology\Runtime
You must run the ConfigureDrawingsBatch utility each time you change mapped account
settings.
If you are running 64-bit drawings batch services and Oracle, you must install the 64-bit
Oracle client on the computer running the batch services.
Paper Size – Displays the paper sizes supported by the selected printer.
Use 64-bit if available
Updates drawings with 64-bit processes. This option is only available for Update actions
performed on composed drawings.
If you select Use 64-bit if available and run Update on a folder component containing
composed drawings and other drawing types, the composed drawings are updated with
64-bit processes. All other drawings are updated with 32-bit processes.
Schedule
Creates the job and opens the Schedule Batch dialog box.
If you click Schedule with no actions in Actions to Queue, you receive a
message, and the dialog box remains open.
2. Select the action, and click Add to move it into Actions to Queue.
You can add actions to the queue in any order, but the software processes the actions
in the following order: Refresh, Update, and then all other actions. If you add Update,
but you do not add Refresh, Update is the first action processed.
You can only add one Save As action to the queue.
3. Define any action options. For more information, see Batch Processing - Intergraph Smart
Batch Services (on page 169).
4. Click Schedule to create the job and open the Schedule Batch dialog box.
Multiple documents:
1. Do one of the following:
a. Right-click a set of multi-selected documents or components in the Detail View, and
select Batch.
b. Right-click a component in the Management Console, Detail View, or Drawings
Console, and select Batch.
2. Select the action, and click Add to move it into Actions to Queue.
You can add actions to the queue in any order, but the software processes the actions
in the following order: Refresh, Update, and then all other actions. If you add Update,
but you do not add Refresh, Update is the first action processed.
You can only add one Save As action to the queue.
3. Define any action options. For more information, see Batch Processing - Intergraph Smart
Batch Services (on page 169).
4. Click Schedule to create the job and open the Schedule Batch dialog box.
Create a Template
Templates are user-parameterized actions that are saved in the session file and available for
future batch jobs. You can only create templates based on the Print action.
Create a new template:
1. Select the Print action, and click Add to move it to Actions to Queue.
2. In Action Options, make the necessary changes to the action.
3. Type a new Template Name for the action.
4. Click Save Settings As Template.
Delete a template:
1. Select the template to delete.
2. In Action Options, click Delete.
Every X weeks
Specifies how many weeks pass between job runs. In addition, you can select on which
days the job runs. This option is available when you select Weekly from Run job.
Day X of the month
Specifies on which day of the month the job runs. This option is available when you select
Monthly from Run job.
The X Y of the month
Specifies on which day of the month the job runs. For example, you can select the last
Monday of the month. This option is available when you select Monthly from Run job.
Job Start
Notifies you when the job starts, if Outlook is set up.
Job Completion
Notifies when the job completes, if Outlook is set up.
Job Abort
Notifies you if the job aborts, if Outlook is set up.
Address Book
Selects the name of the person to be notified by e-mail of the job status, if Outlook is set up.
If Outlook is not available, this option does not work. You can also type the address
manually. The person you define here receives an email with the job log files after the job
finishes.
The Batch Services SMTP option must be configured on the batch server for this to work.
For more information, see the Intergraph Smart Batch Services documentation.
The WinZip application is no longer required on the batch server to compress any emailed
attachments. Compression is now done with functionality included in Smart 3D.
Server
Displays the name of the server on which the board management service runs.
Started by
Displays the user name of the person who started the board management service.
Modification of Parts
Whenever you modify a part in the UnAssigned Parts folder and an intersection with a block
boundary occurs, the software places the part on the list of intersections and sets its status as
Assigned to the block from which it originated.
When you modify a part that exists outside of the UnAssigned Parts folder, the assembly
hierarchy is left unchanged. If an intersection with a block boundary occurs, the software places
the part on the list of intersections and displays its status as Assigned. If you modify a part and
as a result it is fully contained within a new parent block, the software considers the part as new
and leaves it in the UnAssigned Parts folder.
If a part intersects with the block boundary between previously well-known blocks (block cutting
plane modification), the part is left in the block from where it originated, and the status in the list
of intersections is set as Assigned in that block. If the part intersects with one or two blocks that
were previously unrelated, the software places the parts in the UnAssigned Parts folder of the
parent block and lists them among the intersecting parts for the involved blocks or block cutting
planes. Assemblies that are emptied of parts are deleted.
You can set a percentage tolerance to assign a part to a block that contains the
greater portion of the part. When part that is inside a block has a percentage volume greater
than the specified tolerance, it is assigned to this block. For information on how to set tolerance,
see Planning Reference Data Guide.
Block Assignment
The block assignment process assigns and reassigns parts to blocks. When the process is
activated, the software automatically and continuously queries the database for new and
modified parts to assign and reassign to a block.
You can also specify which types of parts should be processed and how they should be
processed.
For the block assignment process to run automatically and continuously, a dedicated server or
workstation computer is required. If a dedicated computer is available, you can initiate the block
assignment process manually at regular intervals.
Modification of Parts
Whenever you modify a part in the UnAssigned Parts folder and an intersection with a block
boundary occurs, the software places the part on the list of intersections and sets its status as
Assigned to the block from which it originated.
When you modify a part that exists outside of the UnAssigned Parts folder, the assembly
hierarchy is left unchanged. If an intersection with a block boundary occurs, the software places
the part on the list of intersections and displays its status as Assigned. If you modify a part and
as a result it is fully contained within a new parent block, the software considers the part as new
and leaves it in the UnAssigned Parts folder.
When parts have been assigned to assemblies, defining or modifying a block boundary is more
complicated. Consequently, Intergraph PPM recommends that as much of the designed building
method be preserved as possible. Defining or moving block boundaries removes disassociated
parts, assemblies, and part of assemblies from the block in which they were originally assigned
during the initial design of the assembly hierarchy.
To preserve the design decisions documented in the assembly hierarchy, the block assignment
process only moves parts to the block in which fully contained and duplicate parts of the
assembly hierarchy are represented in the original block. The duplication includes the assigned
assembly properties. If the duplication involves a whole branch of the assembly hierarchy, that
branch is deleted from the original block. In the following illustration, Block B1 is reduced in size
by the modification of a block cutting plane. The neighboring block, Block B2, is increased in
size by the operation. Parts are moved and assembly A1.2 is duplicated to block B2:
If a part intersects with the block boundary between previously well-known blocks (block cutting
plane modification), the part is left in the block from where it originated, and the status in the list
of intersections is set as Assigned in that block. If the part intersects with one or two blocks that
were previously unrelated, the software places the parts in the UnAssigned Parts folder of the
parent block and lists them among the intersecting parts for the involved blocks or block cutting
planes. Assemblies that are emptied of parts are deleted.
You can set a percentage tolerance to assign a part to a block that contains the
greater portion of the part. When part that is inside a block has a percentage volume greater
than the specified tolerance, it is assigned to this block. For information on how to set tolerance,
see Planning Reference Data Guide.
If the software detects that the server you selected in step 2 is not running the appropriate
software, you are prompted to select another server.
You must have read and write permissions to the model database to start and stop the block
assignment process. For more information about access permissions, see your Smart 3D
administrator.
the process could immediately find a new or modified part and process it. Meanwhile, you
may have also selected the part for modification, but your changes will likely be lost because
of the assignment update.
Current search range from
Displays the start date and time of the current range. The date/time readout is continuously
updated and is read-only.
Current search range to
Displays the end date and time of the current range. The date/time readout is continuously
updated and is read-only.
Found parts awaiting assignment
Specifies the number of parts found by the block assignment process within the current
search range and that are yet to be assigned. This data is continuously updated and is read-
only.
Total number of parts processed
Displays the number of parts processed. This data is continuously updated and is read-only.
Number of parts processed in grace period
Displays the number of parts processed during the grace period. This data is continuously
updated and is read-only.
Estimated Remaining Time for Assignment
Displays how long the process is expected to continue. This data is continuously updated
and is read-only.
Run In Background
Accepts the changes and closes the dialog box. The block assignment process will continue
to run in the background. This button is only available after you select Start.
Submit Job
Opens the Schedule [Task] dialog box, which is used to define the batch settings for block
assignment using Intergraph Batch Services. For more information about the batch settings,
see Schedule [Task] Dialog Box (on page 172).
Start
Starts the block assignment process as a continuous process on the specified server.
Stop
Stops the block assignment process on the specified server.
Close
Accepts the changes and closes the dialog box. This button is only available after opening
the Block Assignment dialog box when block assignment is already started.
Getting Started
This section discusses how to map individual workstation computers to the server databases,
start the software, and begin performing various tasks in the software environment.
You must create the seven databases before running the software. For
additional information, refer to the section entitled Create Databases (on page 105).
In This Section
Update Site Database Name and Path ......................................... 185
Open Smart 3D .............................................................................. 187
Configure Your Tasks .................................................................... 187
Define Your Workspace ................................................................. 188
Save Session Files ........................................................................ 193
3. In the Site database server box, type the name of the server on which the Site database
resides or select it from the drop-down list of recently used Site database servers.
4. In the Site database name box, type the name of the Site database or select it from the
drop-down list of recently used Site databases.
5. The Site schema server box value is set when you specify the Site database server and
Site database name.
6. The Site schema name box value is set when you specify the Site database server and
Site database name.
If SQL is not installed locally, you can get the names from your database
administrator.
7. Click OK.
Oracle Databases
1. Open the Modify Database and Schema Location utility.
2. In the Database type list, select Oracle.
3. In the Oracle service name box, type the name of the Oracle net service for the Site
database connection or select it from the drop-down list of recently used Oracle service
names.
4. In the Site database name box, type the name of the Site database or select it from the
drop-down list of recently used Site databases.
5. The Oracle service name box value is set when you specify the Oracle net service and Site
database name.
6. In the Site schema name box value is set when you specify the Oracle net service and Site
database name.
7. Click OK.
The first time you run the software after installing it, the software prompts you for the
Site database name and sets the Site database name and path automatically.
See Also
Getting Started (on page 185)
Open Smart 3D
When you work on your model in Smart 3D, you use a session that allows you to save certain
settings, such as window size, layout, and view orientation from one work session to the next.
If you have a previously saved session, you can double-click the session file to open Smart 3D.
The software loads your data from the last session, and then you can click Refresh Workspace
to update all views with the most current information from the database.
If a session if not available, you can open Smart 3D from the operating system menu. The
software then asks you to choose a template to create a new session.
A user who is a member of the Windows Administrators group on the
workstation computer must start the software once on the workstation computer before a user
without administrative privileges can successfully start the software.
The following procedure shows the steps to open Smart 3D from the operating system menu.
1. Click Start > All Programs > Intergraph Smart 3D > Smart 3D.
2. Select one of the templates on the New dialog box.
A template is a standard Workspace file. You use a template as a pattern to
assemble the parameters that you want for a new work session. Two standard templates
are delivered with the software: English Units and Metric Units.
3. Click OK.
After you open Smart 3D, you can use commands on the File menu to create new
sessions, open previous sessions, save sessions, and close sessions. For more information,
refer to the online documentation for the Common task or the Common User's Guide available
from Help > Printable Guides command in the software.
See Also
Getting Started (on page 185)
To use the tasks available in Smart 3D, you must configure them for your session. After you
configure the tasks that you want to use, you must then define your workspace. After you define
your workspace and configure your task list, you can save your session file.
1. In Smart 3D, click Tasks > Configure Task List.
2. On the Configure Task List dialog box, select each task in the list that you want to add to
the menu from the Available task environments list.
You can select multiple tasks by dragging down the list or holding Shift and
dragging.
3. Click Add.
4. Click OK.
You have to perform the above procedure only once for your session file. The software
remembers the tasks when you re-open the session file.
For detailed information regarding how to configure tasks in Smart 3D, refer to the online
documentation for the Common task or the Common User's Guide available from Help >
Printable Guides.
Filter
Displays a maximum of ten of the last filters selected for the workspace. This box is blank if
no filters were previously defined and used.
If you select the More option, the Select Filter dialog box appears. This dialog box displays
a tree view of other filters you can select. For more information, see Select Filter Dialog Box
in the Common User's Guide. The Create New Filter option opens the Filter Properties
dialog box where you can create a new filter. The software places the resulting new filter in
the My Filters folder. The software then returns to the Define Workspace dialog box where
the new filter name is displayed. If your permissions include edit privileges, the Define
Workspace dialog box also allows you to rename or delete filters and edit filter properties.
Properties
Displays the Filter Properties dialog box that provides tabs of optional properties for the
selected filter, or query criteria, you can select and apply to your filter. The System,
Assembly, and Named Space tabs allow you to select large groups of objects in the
database. If you want a more restricted selection, choose a tab such as Permission Group
or Object Type. The Permission Group tab properties limit the selection to only those
objects in a designated group. The Object Type tab displays a tree view of all objects in the
system. The objects are organized primarily by the task where you created them. Using this
tab restricts your selection to only those objects of the selected types. For more information,
see Filter Properties Dialog Box in the Common User's Guide.
Role
Provides a list of user roles that you can select for the workspace. You can define roles to
suit the type of work you are performing, to reduce the number of model objects loaded into
the workspace, to improve performance, and to load the optimal objects in your workspace.
Reducing the number of objects loaded into the workspace improves performance by using
less memory, reducing network traffic, and speeding workspace definition and refresh.
Each role defines a specific set of disciplines (class object types) and related subclass
object types. If you select a role, only the object types defined for the role and meeting
criteria of the selected Filter display in the workspace. Delivered roles include:
None
Civil Designer
Electrical Designer
Equipment Designer
Hanger & Support Designer
HVAC Designer
Piping Designer (Aboveground)
Piping Designer (Underground)
Ship Early Designer
Ship Detail Designer
Ship Production Designer
Structural Designer
Plant Reviewer
Ship Reviewer
Roles and their included object classes and subclasses are defined in the
[Link] file in the [Reference Data Folder]\SharedContent\XML folder. If
the file is missing, the Define Workspace dialog box does not display the Role box. Your
administrator can customize [Link]. For more information, see Define
roles (on page 190).
If you switch to a different task, you can also redefine your workspace to a new role to
suit the new task. For example, if you change from Tasks > Piping to Tasks > HVAC,
you can change Role from Piping Designer (Aboveground) to HVAC Designer.
If you frequently switch tasks, your administrator can create a new role that includes
objects for all used tasks.
You can also save role-specific session files. For more information, see Managing
Sessions in the Common User's Guide.
The shortcut keys for the Define Workspace command are CTRL+W.
You can also access the Select Filter dialog box by clicking Tools > Select by Filter.
Before loading the query results to your workspace, the software determines whether your
computer has enough virtual memory to contain the results. If you do not have adequate
memory available, the software displays a warning that your workspace size is likely to
exceed the available memory of your computer. You can continue by clicking Yes. If you
click No, the query load stops, and the Define Workspace dialog box returns so that you
can redefine your search criteria.
Define roles
The list of roles for selection in the Role box in the Define Workspace dialog box of File >
Define Workspace is defined in the [Link] file in the [Reference Data
Folder]\SharedContent\XML folder. Your administrator can customize [Link].
<Smart3D>
<Role Name="" StyleSet="" Version="">
<Discipline ClassName=""/>
<Discipline ClassName="">
<Node ClassName=""/>
<Node ClassName="">
<Node ClassName="">
</Node>
</Discipline>
</Role>
</Smart3D>
The XML format defines three criteria in a hierarchy:
1. Role - The optimization category.
<Role Name=" " StyleSet=" " Version=" ">
Name - Defines the role name that displays in the Define Workspace dialog box Role list.
StyleSet - Defines the set of project colors and symbols (styles) used to display objects
defined by the role.
The StyleSet names in [Link] are placeholder values and
have no effect on object styles. Style sets work with color configurations defined in the
Project Management task, but no color configurations for role style sets are delivered with
the software. Style sets require additional filtering of objects and can affect performance. For
more information, see Default Color Configuration Dialog Box in the Project Management
User's Guide. Contact Intergraph Support if you want to create style sets for roles.
2. Discipline - The top level of the object class to include in the role.
Use this format when you want to include all subclasses of the object class:
<Discipline ClassName=" "/>
Use this format when you are also defining specific subclasses:
<Discipline ClassName=" ">...</Discipline>
3. Node - Individual subclasses to include under the object class. Use Node when you do not
want to include all subclasses.
Use this format when you want to include all subclasses of the subclass:
<Node ClassName=" "/>
Use this format when you are also defining specific subclasses of the subclass:
<Node ClassName=" ">...</Node>
The ClassName attribute defines an object class or subclass name as it displays in the
object hierarchy used in Smart 3D. You can see a tree view of the object hierarchy in the
Object Type tab of the Filter Properties Dialog Box.
The software supports the nesting of three levels of Node classes.
Roles applied to filters that include referenced files or referenced 3D files must include the
specific reference classes to populate the Workspace Explorer tree view. If these classes
are missing from the role definition, references are added by the filter but the Workspace
Explorer cannot be populated. Examples include:
<Discipline ClassName="Reference 3d File"/>
<Discipline ClassName="Referenced File"/>
You can see all reference class names in the object hierarchy.
The discipline and node names must match those defined in the Smart 3D object hierarchy.
If in any of these names do not match an existing classification, an error message displays
when the role filter is loaded. The software excludes the node in error from the workspace.
Example Roles
<?xml version="1.0" encoding="windows-1252" ?>
<Smart3D>
<Role Name="Electrical Designer" StyleSet="Electrical"
Version="1.0">
<Discipline ClassName="Cableway">
Equipment Designer Equipment and Furnishing All Equipment and Furnishing objects
After the Define Workspace dialog box closes, the window refreshes. After the refresh is
complete, the Common window is active. Everything in the Tasks menu is now available.
For more information on workspaces, sessions, and filters refer to the online documentation
for the Common task or the Common User's Guide available from Help > Printable Guides.
Application Maintenance
You have three options for Application Maintenance for Smart 3D:
Update - Change the selected features that were installed. Install and/or uninstall individual
features to match the new selection.
Repair - Using the current feature set installed, repair any missing or corrupted files from the
installation.
Uninstall - Removes registry entries, files, and directories that do not contain user data and
are not shared by other programs and were put there by the installation.
You can access Application Maintenance from Control Panel > Programs and Features >
Intergraph Smart 3D, and then click Change.
Selecting Uninstall from Programs and Features does not access the Application
Maintenance utility. The uninstall process is started automatically.
For more information on modifying, repairing, or removing the software, see Modify or Repair
Intergraph Smart 3D Software (on page 195).
Before adding and removing features from the setup, review the dependencies that can
exist between one feature and another. For more information, see Setting Up the Client
(see "Client/Workstation Setup" on page 67).
If you selected the Piping Specification Remote Access Server feature to be
installed, you need to enter a username with administrative privileges to the computer.
In the Password box, enter the password of the user.
2. Click Update.
3. When the installation process is complete, click Finish.
During the setup, the %temp% value is defined as the user %temp% of the person who
runs the setup. In Windows, each user's C:\Documents and Settings\username\Local
Settings\Temp is protected from other Windows users. Consequently, you must set the
system environment variable TEMP value to a folder location where everyone has write
access (that is, C:\Temp). For more information about editing system variables, see the
Windows online documentation (click Start > Help from the Windows task bar).
If you installed the Piping Specification Remote Access Server feature during the
setup, you must verify that the COM+ application is installed and configured on the
administrator computer. For more information, see Configure the Piping Specification
Remote Access Server Service (on page 139).
You can install the Database Interference Detection Service on a different workstation
computer. For more information, see Install Database Interference Detection Service
(on page 148).
Disk I/O
Data file and log file location and sizing are critical to obtaining optimal performance. I/O is one
of the most common bottlenecks in database servers. Consequently, sizing I/O is critical to
performance.
Disk drives should not be run at more than 75% of the maximum I/O capacity.
The two types of I/O are Random I/Os and Sequential I/Os. The type of I/O determines the
number of I/Os per second that a disk drive can handle. Random I/Os require a longer time to
complete than sequential I/Os.
Random I/Os
The amount of time spent performing random I/Os is governed by the time it takes to perform
the seek operations. Since the random I/O involves requests for data on different parts of the
disk, most of the time spent in the I/O will be the seek time. If a disk drive takes 10 milliseconds
(averaging read and write), it is theoretically possible to perform 100 random seeks per second
(1/.001 sec), excluding such things as overhead associated with the I/O bus or latencies
associated with processing the I/O. Queuing begins as you get closer to the theoretical limit of
the disk drive. As queuing occurs, the I/O latency increases and database performance begins
to suffer.
You can increase the system's random I/O capacity by spreading the data across
multiple files or install the data files on a RAID array.
Data files are mostly accessed by random I/Os.
Sequential I/Os
Because there is no seek operation involved in sequential I/O, a disk drive can handle several
hundred sequential I/Os per second without seeing increasing latencies. Therefore, using
sequential I/O whenever possible can greatly improve the performance of the disk drives.
Microsoft SQL Server and Oracle keep a log of the transactions; this log is primarily sequential
to take advantage of sequential I/Os.
In order to achieve maximum performance, the data file and log file must not
be on the same physical drive.
See Also
Recommendation for Database Monitoring (on page 197)
Monitoring the Databases (on page 197)
Disk Usage (on page 198)
Disk Usage
Disk usage should remain under 85% of the maximum disk capacity, and the partition should not
be compressed.
Catalog Database - Medium to Low level of reads and writes (select, insert, update, and
delete activities). Activities such as bulkload and copy to catalog are write activities. Both
can write a significant amount of data.
Catalog Schema - Low level of reads and very low level of writes. Activities such as
bulkload are used to write occasionally, but the amount of data is relatively small.
Site - Very Low level of reads and writes. While the Site is not read-only, the write activity is
limited to a maximum of several rows per week.
Site Schema - Very Low level of reads with no writes.
Report Database and Report Schema - Read only. They contain views that are composed
of queries mainly from the Site, Catalog, and Model Databases.
Microsoft SQL Server tempdb has a high level of read and write.
The following table is based on a Microsoft SQL Server setup and shows some reasonable
orders of magnitude for small pilots based on testing conducted by Intergraph. The most critical
files for performances and monitoring are isolated on their own physical drives (the G and H
drives) while the less critical files share two drives (the E and F drives). The operating system,
SQL server and paging files are installed on their own drives.
Model data 10 GB 1 GB G
Site data 50 MB 10 MB E
Site log 50 MB 10 MB F
The size of your Model database log file depends on your backup strategy. For more
information about backing up your Smart 3D data, see the Project Management User's
Guide, available from Help > Printable Guides.
Tempdb size is reset to the default every time the server is re-started.
We recommend that you have the same number of Tempdb data files as you have physical
cores on the server machine, if you have up to eight physical cores. If you have more than
eight cores, add eight data files, and only add more data files as necessary. Each data file
should have the same initial size, growth increment, and drive location as specified above.
See Also
Smart 3D Database Server Recommendations (on page 17)
Recommendation for Database Monitoring (on page 197)
Monitoring the Databases (on page 197)
Assign System Administrator Privileges for SQL Server 2014 (on page 42)
Server Monitoring
The details on how to monitor system counters and log the results to a file can be found in the
operating system documentation. Intergraph PPM assumes that the reader is already familiar
with that topic.
While doing the monitoring at Intergraph PPM, we started from a very broad selection of
counters. The analysis of these system parameters with the number of users on the system
conducted us to focus on a subset of counter found the most relevant for the scalability and
dimensioning analysis. The list of highlighted counters is not a definitive list of what should be
monitored, but the list of counters that should be watched with the closest attention. We
recommend starting from a wide selection of counters and discard later what is found not to be
pertinent.
Testing has demonstrated that these counters can be monitored every second to analyze a
specific workflow or every 10 seconds if you plan on monitoring the system for longer times.
A log file of the user activity should be kept in order to relate the server activity to the actions
of the user.
You can also use the System and Configuration Analyzer tool (SCA) to monitor these
parameters. This tool can be downloaded from eCustomer.
Processor
Processor average usage should be kept under 80% for each processor. Isolated spikes over
80% are acceptable.
We recommend monitoring the following counters:
% Processor time
% Privileged time
% User time
% Interrupt time
Memory
Available Mbytes
Page fault per second
Page read per second
Page write per second
Pages per second
Page fault per second needs to be monitored only to make sure the system is not
overloaded.
Network
Byte received per second
Byte sent per second
Current bandwidth
Output queue length
Record PING times between client and server to verify that the software is not being affected by
other network traffic.
Database (ORACLE)
Oracle performance counters can be monitored using the web-ui that installs with Oracle or by
using the System and Configuration Analyser tool (SCA) available from eCustomer. Please
consult Oracle documentation for details on it.
Oracle Database Counters:
Dictionary Cache Hit Ratio – Should be > 90
Library Cache Hit Ratio – Should be >= 99%
DB Block Buffer Cache Hit Ratio – Should be > 90
Log Switch Interval – Should be greater than 30 minutes
Oracle Reports:
Automatic Database Diagnostics Monitor (ADDM) report – This report can be generated
from the Oracle Database Console or using the SCA tool available on eCustomer.
See Also
Recommendation for Database Monitoring (on page 197)
Results Analysis
The classical way to analyze database activity is to analyze the activity generated by each
command (place an order, repeat order, order status, and so on) and extrapolate the response
of the system to a given load. For example, if placing an order causes one physical read on the
data file disk, the maximum number of orders that can be placed in one minute can be
computed.
Given the huge number of commands that exist in the software, this approach is not practical for
our system. Instead, the focus is placed on measuring the typical activity per interactive user for
a given environment. Getting reliable average data requires having several users working
concurrently. The data generated by a single interactive user is usually too noisy to be used.
After the data is collected for a given load, the response of the system can be extrapolated to a
higher load assuming a linear response up to a critical value. Refer to Microsoft SQL Server or
Oracle performance tuning documentation for more details.
Example
The following graphic shows some of the system parameters while two users are routing pipes
and two users are creating beams in structure:
CPU
CPU capacity = 2 (processors) 500 MHz = 1 GHz
CPU usage per user = CPU capacity (average CPU % used / number of users) = 1 GHz
.15/4 users = approximately .0375 GHz per user
Therefore, for a single 1.0 GHz processor:
Usage capacity = 1.0 GHz .75 (critical usage percentage or usable capacity)
Number of users = Usable capacity / CPU usage per user
The system should support (0.75/0.0375) GHz per user = 20 users per GHz.
Model Data File
Total physical I/O per second = 2.75 (Model DB writes) + 0.003 (Model DB reads) = 2.75
physical I/O per second for 4 users = approximately 0.69 physical I/O per second per user
Ignoring RAID factor and taking a standard Max I/O = 70 75% = 52
Therefore using the same disk characteristics, can support 59/0.68 = 75 users per disk.
Model Log File
Total physical I/O per second = 2.83 (ModelDB writes) + 0.003 (ModelDB reads) = 2.83
physical I/O per second for 4 users
Ignoring RAID factor and taking a standard Max I/O = 70 75% = 52.
Therefore using the same disk characteristics, can support 52/0.71 = 73 users per disk.
Testing has determined that the main hardware parameters driving the scalability of the
system are the CPU and the I/Os.
A system different than the one used for testing purposes can lead to completely different
results. For example, if the memory is scarce, more loads are placed on the I/O system.
Because the log file I/Os are mostly sequential, the system can achieve about 150
sequential I/Os per second per physical disk, compared with only 50 random I/Os per
second per physical disk.
Other Considerations
Interference Checking (IFC)
IFC imposes a very significant load on the database server (equivalent to several simultaneous
interactive users). We recommend turning off IFC to measure the database activity generated by
the interactive users using the design applications (piping, structure, and so on).
Reports
Some reports can put a heavy burden on the server. Intergraph PPM advises monitoring the
reports activity separately from the database activity generated by the interactive users using
design applications (piping, structure, and so on).
See Also
Recommendation for Database Monitoring (on page 197)
Log Files
To enable the error log file, use Windows Explorer to navigate to [Product
Folder]\Core\Tools\Administrator\Bin and execute [Link]. This utility allows you
to configure the delivery location of the log file, the file name, and four levels of logged
information.
Log Detail
Specifies the error reporting level. The higher the level, the more information is written to the
log file. Intergraph recommends that you use 1 - Normal at all times. The higher level error
reporting (2 - Detailed, 3 - Complete, and 4 - Exhaustive) slows the software performance,
and is only necessary if Intergraph Smart Support [Link]
requests detailed log information while tracking a problem. Select 0 - Disabled to disable
the error log.
Options
Add OS stats (cputime, memory)
Adds your operating system status (such as CPU percentage and memory usage) to each
log message. Please note that selecting this option slows down the software performance
and likely your entire system's performance. You only need to check this option at the
request of Intergraph Smart Support [Link] It is important to
notice that if Smart 3D uses more than 2 GB of memory during execution, the OS stats
logged for each error take more than half a second to calculate. Intergraph recommends
that this option be checked only temporarily as requested by Intergraph Smart Support
[Link] while tracking an issue.
Add stack trace to records
Adds the stack of the function registering the error. Please note that this option slows down
software performance and likely your entire system's performance.
Preserve User Settings
Saves the Log Detail value and the error log file name for just the active user. If you have
administrative privileges, you can clear this option to save the Log Detail value and error
log file name for all users on this computer.
Generate new log file name on startup
Creates a new error log file name when you restart the software. If you need to save an
existing copy of the log file, you can either check this option or rename the file before
starting the software. Clear this option to overwrite the log file each time you start the
software.
Launch memory monitor on startup
Check this option to start the Memory Monitor automatically every time Smart 3D starts. You
can also click Start Memory Monitor to manually start the Memory Monitor. For more
information, see Appendix: S3DMemoryMonitor in the Smart 3D Common User's Guide.
Log File
Specifies the path and name of the log file. Alternatively, you can simply specify the folder in
which to save the log file. You can use environment variables to specify the file location. For
example, you can type "%temp%\[Link]." We recommend that you specify a location
where all users have write access; otherwise, problems associated with updating the error
log file may prevent users from receiving the correct response. For example, if you set the
log to write to UserA's Temp folder, then UserA is the only one who can create or update the
log file. Other users (with the exception of an administrator) will not have access to UserA's
Temp folder. Likewise, if you configure the software to generate the log file in a folder under
the Program Files path, only those users who belong to the Power Users or the
Administrator groups will have write access to the log file. Keep disk access privileges in
mind when you are configuring the log file.
An error log is always created. If there is not a location specified, the default location is your
Temp folder, or %TEMP%, for the process being executed. If the software crashes or completes
in another abnormal way, the error log is left on disk to help Intergraph Smart Support
[Link] diagnose the problem that occurred. In addition, it is
possible that two more files are created: WER_SP3DErrors_<timestamp>.log and
S3DHost_<timestamp>.dmp. When contacting Intergraph Smart Support
[Link] please also make these files available as part of your
Service Request.
Troubleshooting Tools
You can use tools delivered with the Core to troubleshoot the software. These tools are located
in [Product Folder]\Core\Tools\Administrator\Bin.
[Link] - Allows you to forcefully crash Smart 3D. This is useful when you want to
log a hang, either in a command that never completes or a command that takes a long time
to process. It can also be useful when an unexpected error dialog displays and you want to
log a Service Request for the issue. In Smart 3D, crash events are recorded in a .dmp file
and stored in the specified Temp folder. Along with the .dmp file, copies of the Errorlog and
WER_SP3DErrors.log file are also stored in the specified Temp folder, which are all useful in
determining the reason for certain problems that occur in the product. [Link]
allows you to crash Smart 3D to obtain a copy of the .dmp, Errorlog, and WER_SP3DErrors
file for troubleshooting purposes. When activated, [Link] allows you to select
which instance of Smart 3D you want to forcefully crash. Contact Intergraph Smart Support
[Link] for more information about the options available in this
utility and when to use them.
[Link] - See above for more information.
[Link] - Allows you to troubleshoot video card issues. Contact Intergraph
Smart Support [Link] for more information about the options
available in this utility and when to use them.
[Link] - Displays the version for each task component in the software.
In addition, a tool named [Link] is available to help troubleshoot. This tool displays the
installed version of each component in the software.
For more detailed information about troubleshooting tools delivered with the software, see the
Troubleshooting Reference Guide. The guide is available from Help > Printable Guides in the
software.
User Assistance
Smart 3D user assistance makes command information available as you perform tasks. You can
access different kinds of information any time that you are running the software. This information
could include reference topics, narrative descriptions, or step-by-step instructional material.
Printable Guides
User's Guides in PDF format are accessible, flexible, and fully searchable alternative to Help.
The information found in the User's Guides is also available from Help. The User's Guides
delivered with the software are located in C:\Program Files (x86)\Common
Files\Intergraph\Smart3D\Help. Copies of the user's guides can also be found in the Help folder
on the Intergraph Product DVD. To view these PDF documents, you will need Adobe Acrobat
Reader with Search version 3.0 or higher. You can download the latest version of the Acrobat
Reader from the Adobe web site. After you have installed the Acrobat Reader, you can open
files individually by using the File > Open command in the Acrobat Reader.
Help
Smart 3D offers a variety of ways for you to receive help on how to use the software.
A structured table of contents, an index, and full-text search capabilities provide easy access to
Help topics. You can access the table of contents by clicking Smart 3D on the Help menu.
Smart 3D Help is a complete reference tool accessible at any time the application is in use. Help
provides complete command descriptions for each toolbar button, menu command, and ribbon
in the software. It also gives step-by-step procedures for common tasks; for example, if you
need to perform a certain task, search and display the topic. You can move or resize your
application and Help windows so that they are next to each other. As such, you can follow the
procedures without having to search for the pages in the documentation.
Smart 3D Help is task-specific. For example, to view Common Help, enter the Common task,
and click Help > Smart 3D Help. To see more specific information, select one of the major
topics or perform a search on a specific topic.
Show/Hide
Show or hide the left pane of the dialog box, including the Contents, Index, and Search.
Back
Returns you to the last Help topic you viewed. This button is disabled when you reach the
first topic in the series.
Forward
Displays the next topic in a series of related topics. This button is disabled when you reach
the last topic in the series.
Options
Displays a list of functions available for the Help viewer.
Contents
Displays a hierarchical listing of the topics in the Help file.
Index
Displays an index for the Help file.
Search
Performs a full-text search on a word or phrase that you entered in the Search box.
For more information, refer to the Common User's Guide available from Help >
Printable Guides within the software.
Customer Assistance
For the latest Support Services information for this product, use a World Wide Web browser to
connect to [Link]
Common Acronyms
Acronym Meaning
2D Two-Dimensional
3D Three-Dimensional
CD Compact Disc
GB Gigabyte
GHz Gigahertz
I/O Input/Output
MB Megabyte
MHz Megahertz
SP Service Pack
SM3D SmartMarine 3D
SP3D SmartPlant 3D
VB Visual Basic
G Internationalization • 13
General Tab (Block Assignment Dialog
Box) • 182 L
Getting Started • 185 License Server • 31
Global Workshare Configuration Distribution License Server and Name Generator
Server Sizing • 29 Server Sizing • 30
Granting Batch Service Privileges • 162 Linking Servers • 116
[Link] Loading Prerequisite Software on the Client
t • 156 • 68
Loading Prerequisite Software on the
I Database Server • 35
Initialize the Oracle Database • 61
Install and Configure Oracle Server M
Software • 50 Making Other Batch Servers Available • 168
Install any Required SQL Server 2014 Marine Workbooks • 127
Upgrades • 41 Minimum Reference Data • 122
Install Database Interference Detection Modeling (Detail Design) Workstation Sizing
Service • 148 • 27
Install Microsoft .NET Framework Modify or Repair Intergraph Smart 3D
(Database Server) • 35 Software • 195
Install Microsoft Office • 68 Monitoring the Databases • 197
Install Microsoft SQL Server 2014 • 36 Move custom .dlls to SharedContent folder •
Install Microsoft SQL Server 2014 Client • 98
69
Install PDS Export Tools • 135 N
Install Smart 3D Client Software • 78
Install Smart 3D PDS Model & Data Name Generator Service Setup • 86
Translators • 136
Install SmartPlant Schema Component • O
135 Open Smart 3D • 187
Install the SmartPlant 3D Command Wizard Optional Schedule Properties Dialog Box •
• 102 173
Install the SmartPlant 3D Symbol/Part Oracle 12c Client Installation • 73
Definition Wizard • 103 Oracle 12c Server Installation • 51
Installation Checklist • 12 Oracle Database Port Assignments • 65
Installation Overview • 10 Oracle Post-Installation Requirements • 63
Installing and Configuring Microsoft SQL Oracle Server Configuration • 50
Server 2014 • 36
Installing and Configuring Oracle Client
Software • 73
P
Installing and Configuring Oracle Server Preface • 8
Software • 49 Programming Resources Setup • 100
Installing Intergraph Batch Services • 159 Project Size Estimates • 26
Integrating with PDS • 135
Integrating with SmartPlant P&ID • 137 R
Integrating with SmartPlant Reference Data
Recommendation for Database Monitoring •
• 144
197
Interference Checking (IFC) Server Sizing •
Reference Data Setup • 97
30
Register Microsoft SQL Server • 42
Interference Checking Setup • 146
Register the Site Database for P&ID Access
Interference Server Settings Dialog Box •
• 143
153
T
Third-Party Integration • 11
Troubleshooting the Software • 206
U
Understanding Database Authentication •
33
Update Site Database Name and Path •
185
Upgrade Database Version • 131
Upgrade replicated databases • 131
User Assistance • 208