SmartPlant 3D Installation Guide

S

E C T I O N

5

SmartPlant 3D Hardware and Software

Recommendations

A typical data flow between client and server computers is shown below. Before beginning an installation of SmartPlant 3D, verify that your computers meet the hardware recommendations and software requirements.

Multiple services can be installed on the same physical computer for small projects.

SmartPlant 3D Installation Guide 19

SmartPlant 3D Hardware and Software Recommendations

In This Section

SmartPlant 3D Database Server Recommendations .................... 21

SmartPlant 3D Workstation Recommendations ............................ 22

Software Loading Order ................................................................. 26

Installation Checklist ...................................................................... 27

Disk Partitioning Guidelines ........................................................... 27

SmartPlant 3D Project Hardware Sizing Recommendations ........ 28

Silent Installation ............................................................................ 35

Silent Installation for Service Packs .............................................. 38

20 SmartPlant 3D Installation Guide


SmartPlant 3D Database Server Recommendations

Before beginning an installation of SmartPlant 3D, verify that your servers meet the following hardware recommendations and software requirements.

Applicable Hardware



Database server



File server

Hardware Recommendations



Intel Xeon

®

5600 Series or better (64-bit instruction set, not Itanium



4 GB to 32 GB or greater RAM depending on project size

®

)



For hard drive size, see SmartPlant 3D Project Hardware Sizing Recommendations (on

page 28)



Backup system for server



Access to DVD drive, either locally or through a network connection



1 GbE or higher network interface for client connections

Supported Operating Systems



Microsoft Windows Standard/Enterprise Server 2008 R2 (64-bit)

Supported Database Servers



Microsoft SQL Server 2008 Service Pack 3 (Standard edition for stand-alone environments;

Enterprise edition for Global Workshare environments; 64-bit)



Oracle 11g R2 (11.2.0.2) with Patch 8 (Standard edition for stand-alone environments;

Enterprise edition for Global Workshare environments; 64-bit)

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.

With SmartPlant 3D, 64-bit servers can be used with 32-bit operating systems, databases, and workstations. For increased performance, Intergraph recommends a 64-bit server, operating system, and database, especially for medium and large projects. The 64-bit versions of SQL

Server 2008 SP3 and Oracle 11g R2 (11.2.0.2) with Patch 8run on the 64-bit version of

Microsoft Windows Server 2008 R2.

Software Prerequisites



Adobe Reader (required to view the Software License Agreement and Printable Guides. You can download Acrobat Reader from the Adobe web site.)



Microsoft XML Core Services (MSXML) 6.0 (Database server only)



Microsoft .NET 3.5 SP1 (Database server only)



For more information on hardware requirements, see SmartPlant 3D Project Hardware

Sizing Recommendations (on page 28).





For information on disk space usage and determining RAID configuration, see Disk Usage

(on page 64).



For specifications regarding minimum hard drive disk space requirements by the product

setup, see Disk Partitioning Guidelines (on page 27).



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.

See Also

SmartPlant 3D Hardware and Software Recommendations (on page 19)

SmartPlant 3D Workstation Recommendations

Before beginning the installation of SmartPlant 3D, verify that your end-user workstation computers meet the following hardware recommendations and software requirements.

Applicable Hardware



Administrative client



Modeling client



Interference detection computer



Drawing batch computer



Name generator computer



Duplication and synchronization computer



SmartPlant Piping Specification Remote computer

Hardware Recommendations



Intel Core i7, Quad Core



6 GB RAM



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 network interface

Video Cards

There have been many enhancements to the graphic engine of SmartPlant 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



"CoreDisplaySettings.ini" file from [Product Folder]/Core/Tools/Administrator/Bin to [Product

Folder]/Core/Shared/bin and contact your SmartPlant 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 SmartPlant 3D and publish the cards we have actually used in certification.

All clients referencing Z+F Point Cloud data need to turn off the SmartPlant 3D hardware with the CoreDisplaySettings.ini file.

The following graphics cards have been tested and support the display enhancements:



ATI Fire GL V3600

To obtain better graphic performance with SmartPlant 3D, change the following settings:



On ATI FireGL video cards, right-click on the desktop and select

Properties > Settings

> Advanced. On the Configuration tab, create a new configuration profile called

SmartPlant 3D. After this configuration profile is created, select the SmartPlant 3D profile, select Modify, and then check Force copy swap.



ATI Radeon HD 2400 Pro



NVidia GeForce 7600 GT

To obtain better graphic performance with SmartPlant 3D, enter change following settings:



On NVidia GeForce cards, right-click on the desktop and select

Properties > Settings

> Advanced. On the NVIDIA Card tab, select OpenGL Settings in the Performance

and Quality Settings section. In the dialog box that opens, change the Buffer-Flipping

Mode selection to Use block transfer, and then click OK.



NVidia Quadro FX 580



NVidia Quadro FX 880M



NVidia Quadro FX 1800

The following graphics cards do not support the display enhancements:



ATI Fire GL V3100



ATI Radeon x1300/1500



Intel 82945G Express



NVidia GeForce FX 5200



NVidia Quadro FX 3450/4000

As a supplement to this information, a Microsoft Excel workbook is provided on eCustomer that records anecdotal evidence obtained from users. Please go to eCustomer at

https://crmweb.intergraph.com (https://crmweb.intergraph.com/ecustomer_enu) and select

Download Software Updates > Products > SmartPlant 3D > Technical Notes and White papers

> Graphics cards used with SmartPlant 3D.

Neither of the previous lists is comprehensive. In some cases, the SmartPlant 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 via Remote Desktop or Citrix Client. If Hardware Acceleration in

Display Settings is disabled, it should be enabled by selecting the "Advanced" button on the

Settings tab of the Display Properties dialog. Then, the Hardware Acceleration can be modified from the Troubleshoot tab.

Due to the 32-bit precision limitations of graphic cards, you may need to create several design coordinate systems so that the objects being modeled are within 10,000 meters

(6.2 miles) of the global coordinate system. Objects modeled outside this limit will not display correctly. If your model coordinate values are larger that this limit (for example, E = 20,000, N =

30,000), to get the coordinate readout that you want, you should define a coordinate system at correspondingly large negative values (example, E = -20,000, N = -30,000). Then, use the coordinate system you created as your active coordinate system for modeling and output. Do not bring this new coordinate system into your workspace or you will have the display problems that you are trying to avoid.

24

Supported Operating Systems



Microsoft Windows 7 Service Pack 1 - Professional or Enterprise with UAC 'On' at Level 3

(Default) (32-bit and 64-bit)



Microsoft Windows Vista Business with Service Pack 2 with UAC 'On' (Default) (32-bit and

64-bit)



Microsoft Windows Server 2008 R2 (64-bit) only as a client for Citrix XEN App 6.0

Citrix XENApp 6.0 can be installed only on the Windows 2008 Server R2 64-bit operating system. The Windows 2008 Server acts as a client in this case. The Windows

2008 Server R2 64-bit operating system can also be used to install an ancillary server, such as IFC, Drawings, or Intergraph Batch Services.



Microsoft Windows XP Professional SP3 (32-bit)



Microsoft Windows XP Professional SP2 (64-bit)

Supported Database Clients



Microsoft SQL Server 2008 Standard Service Pack 3 (32-bit and 64-bit) (Required for

Project Management and Interference Checking, otherwise optional)



Oracle 11g R2 (11.2.0.2) with Patch 8; 32-bit only (Required for all client computers)

Software Prerequisites



Microsoft Internet Explorer 8.0 or greater (required for viewing the documentation delivered with the software)



Adobe Reader 9.0 or later (required for viewing the Software License Agreement and

Printable Guides. You can download Acrobat Reader from the Adobe web site.)



Microsoft XML Core Services (MSXML) 6.0 (required for extracting isometric drawings)

SmartPlant 3D Installation Guide




Microsoft .NET Framework 3.5 SP1



Microsoft Visual C++ 2008 SP1 Redistributable Package with MFC Security Update



Microsoft Office 2003 (Windows XP only), Microsoft Office 2007, or Microsoft Office 2010

(32-bit only) (Windows Vista, Windows 7, or Windows Server 2008 R2)



Intergraph Batch Services 6.1.0.3 or later if you plan to use the computer for remote batch processing



For specifications regarding minimum hard drive disk space requirements by the product

setup, see Disk Partitioning Guidelines (on page 27).



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.

See Also




Software Loading Order

The ability to run the software successfully is greatly affected by the order in which all the necessary and underlying products are loaded. Follow the loading order below to prevent components being out-of-sync. Following this loading order also helps with analysis of any post-installation problems you might encounter.

The following table outlines the established load order for the prerequisites associated with each of the SmartPlant 3D installations:

Database Server Installation

Windows Server 2008 R2 (64-bit)

Microsoft .NET 3.5 SP1

Adobe Reader

Oracle 11g R2 (11.2.0.2) with Patch 8 (Standard

Edition for stand-alone environments; Enterprise

Edition for Global Workshare environments;

64-bit)

or

Microsoft SQL Server 2008 Service Pack 3

(Standard Edition for stand-alone environments;

Enterprise Edition for Global Workshare environments; 64-bit)

Workstation Installation

Windows 7 SP1 Professional or Enterprise with

UAC 'On' at :Level 3 (Default) (32-bit and 64-bit),

Windows Vista Business SP2 (32-bit and 64-bit),

Microsoft Windows XP Professional SP3 (32-bit), or Microsoft Windows XP Professional SP2 (64-bit)

Microsoft .NET Framework 3.5 SP1

Microsoft Visual C++ 2008 SP1 Redistributable

Package with MFC Security Update

Internet Explorer 8.0 or greater

Microsoft XML 6.0

Microsoft SQL Server 2008 requires XML

6.0 and will automatically install it as part of the

SQL Server 2008 Prerequisite installation.

Adobe Reader

Microsoft Office 2003, Office 2007, or Office 2010

(32-bit)

2

Oracle 11g R2 (11.2.0.2) with Patch 8 Client

Release (32-bit only); (Do not use the Oracle "light client" as it does not include some DLLs required by SmartPlant 3D.)

or

Microsoft SQL Server 2008 Client Service Pack 3

1

(32-bit and 64-bit)

;

SmartPlant License Manager 2010 (11.0) or higher

26

1

Microsoft SQL Server 2008 Client (with SQL Server 2008 SP3) 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 Microsoft Office 2003, Office 2007, Office 2010 (32-bit), you must modify the security settings in Excel to allow Visual Basic projects to run. For more information about Office

2003, Office 2007, Office 2010, and service packs, refer to the Microsoft web site

(http://www.microsoft.com/).



Do not skip any restarts 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 Visual Basic 6.0; Visual Studio 2008 SP1; Siemens Solid Edge

Version 20 or ST3; Tekla Structures Version 16.0, 16.1, or 17.0; or AceCad StruCad Version 16.

Additionally, if you intend to reference or export PDS projects, you must install the appropriate

PDS add-in. The PDS data reference and export add-ins are delivered on the product DVD.



This version of the software supports PDS 2010 SE and PDS 2011 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 116).



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 Client computer, the firewall must be configured to allow DCOM Dynamic Ports. For more information, see

Configure the Firewall to Allow DCOM Communication in Windows 2008 Server (on page

79).

Special Consideration for Non-English Locales

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. For overall assistance with installing the software in a non-US English environment, visit the Intergraph Support web site at http://www.intergraph.com/support.

Virus Scanners and Performance

Other programs running on the computer, such as virus scanners, media players, and mail programs, might affect the performance of SmartPlant 3D. Virus scanners affect performance by continuously checking the data files and log files. Exclude the database data folder on the database server from the virus scanner. For maximum performance, reduce the number of processes running while using SmartPlant 3D.

See Also


Installation Checklist

For the recommended installation workflow, please see the installation checklist

(SP3DInstall_Checklist.pdf), available in the Help folder on the product media. This checklist is also delivered during product set up to c:\Program Files\Common

Files\Intergraph\SmartPlant\Help folder for future reference.

Disk Partitioning Guidelines

For best performance when loading and running the software, partition the hard drive according to the following guidelines:



Format all partitions as NTFS file systems (FAT is not supported).



By default, the software is installed to C:\Program Files\SmartPlant\3D. Verify that you have sufficient free space on your C:\ partition (or another partition if you want to install there).



Recommended Disk Space for Software Setup

SmartPlant 3D Installation - Default setup for a workstation computer

1

1.8 GB

SmartMarine 3D Installation - Default setup for a workstation computer

1

2.8 GB

SmartPlant 3D Installation - Complete setup for a workstation computer

2

2.25 GB

SmartPlant 3D Reference Data - Default setup for database server 1.27 GB

SmartMarine 3D Reference Data - Default setup for database server 1.95 GB

1

The default setup for a SmartPlant 3D workstation computer provides all the environments necessary for general SmartPlant 3D modeling.

2

The complete setup for a SmartPlant 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,

SmartPlant 3D Server Connectivity, Bulkload Reference Data, and Database Interference

Detection Service. Additionally, a complete setup includes the 3D Model Import and Piping

Specification Remote Access Server options, which installs the required components for importing model data into SmartPlant 3D and the necessary software for correlating piping specification data between SmartPlant 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 Process, Power & Marine.

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.

SmartPlant 3D Project Hardware Sizing

Recommendations

Use these guidelines and examples in sizing SmartPlant 3D hardware configurations, including those that include Global Workshare Configuration (GWC). The recommendations are based

SQL Server 2008 SP3 and Oracle 11g R2 (11.2.0.2) with Patch 8.

Hardware sizing, especially for servers, depends on many factors such as:



The number of concurrent users per site



The number of sites (Global workshare)



The size of the project (which translates into the size of the databases)



Other software that is running on the machine

For best performance in medium to large Global Workshare Configurations, Intergraph recommends using 64-bit hardware and operating system. It is possible to use 64-bit hardware and a 32-bit operating system.

With a Microsoft SQL database on 64-bit hardware and operating system, SmartPlant 3D was tested with 11 Global Workshare sites. The 64-bit version of Oracle can support a few more sites. It is possible to combine 64-bit hardware and operating systems on servers with 64-bit or

32-bit client workstations running 32-bit operating systems.



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.

Project Size Estimates

Use the following estimates to help define project size. The model database is an important factor in determining project size.

The number of users for each project size below (small, medium, and large) is the effective

number connected to a single server. The effective number of users should be calculated by taking into consideration:

1. Global Workshare Setup - use the 25% formula above

2. Drawing Batch server - add 3 users

3. Remote IFC - add 1 user

One small project



1 to 15 effective users on one database server



Model database up to 8 GB



Server is used for model and catalog databases and catalog file server



Separate interference checking (IFC) computer



Separate drawing batch computer



Name generator server and licensing computer



Modeling (detail design) and administrator workstations can be on separate or on the same computers

One medium project



16 to 50 effective users on one database server



Model database 8 – 15 GB



Databases and catalog file server








One or more separate drawing batch computer






Modeling (detail design) and administrator computers can be on separate or on the same computer



Use a separate distribution server for Global Workshare Configuration

One large project



51 to 100 effective users on one database server (contact Intergraph if you plan to have more than 100 effective users on one database server)



Model database 15 GB or more



Databases and catalog file server (have a separate catalog file server for multiple large projects or plants sharing the same catalog)






Multiple separate drawing batch computer






Modeling (detail design) computers



Use a separate distribution server for Global Workshare Configuration



Administrator computer

Modeling (Detail Design) Workstation Sizing

The project size does not have a significant impact on the workstation because users will use filters to define the objects with which they will be working.






6 GB RAM










OpenGL Graphics Cards

The following graphics card information is specific to 32-bit workstations. Intergraph is investigating graphics cards for 64-bit workstations.

Graphics cards designed for 3D intensive applications that generate low CPU overhead and meet the following requirements (AGP or better):



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 recommended to improve speed of translucent object display



Hardware Anti-aliasing support recommended



Use latest available drivers

Not all OpenGL graphics cards provide satisfactory results. Many of the recent generation video cards provide some level of OpenGL acceleration. Some manufacturers provide poor OpenGL drivers that can cause artifacts. Testing has shown that NVIDIA provides good drivers for its

Geforce2 and beyond Graphics Processing Units (GPU). Cards with double-buffered overlay


SmartPlant 3D Hardware and Software Recommendations planes (such as the Wildcat cards) have an advantage because highlighting can be done without having to do saves and restores, which may benefit performance in specific cases.

See Also

SmartPlant 3D Workstation Recommendations (on page 22)

System Administrator Workstation Sizing

The Administrator Server includes Project Management synchronization, a memory intensive process.






6 GB RAM










Database Server Sizing

With SmartPlant 3D, 64-bit servers can be used with 32-bit operating systems, databases, and workstations. For increased performance, Intergraph recommends a 64-bit server, operating system and database, especially for medium and large projects. The 64-bit versions of Microsoft

SQL Server 2008 SP3 and Oracle 11g R2 (11.2.0.2) with Patch 8run on the 64-bit version of

Microsoft Windows Server 2008 R2.

For large projects, Intergraph recommends having a database server that is dedicated to

SmartPlant 3D and runs only one project. For medium and small projects, several projects can be run on the same database server. However, having multiple projects on the same server increases the server requirements. When sharing several projects, add additional hard drives and increase the memory and CPUs. Also consider the impact of sharing on your network.

Server Specifications

Project size

Number of processor cores (one Core 2 Duo counts as two)

Memory for SQL Server 2008 SP3 and Oracle

11g R2 (11.2.0.2) with Patch 8

Small

2

4 – 8 GB

Medium

2 – 4

Large

4 – 8 or more

8 – 16 GB 32+ GB

Bus Size, OS, and Database 64-bit 64-bit 64-bit

The type of memory has a limited impact on the overall performance.

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. Add disk arrays to maximize performance if you experience any I/O bottleneck.

Intergraph recommends RAID 10 for performance and redundancy.



Small Project with SQL Server

The following example shows a configuration for a small project using Microsoft SQL Server

2008 SP3. The minimum distribution is three physical drives.

C: Drive Operating system and SQL Server software

E: Drive Database data files (.mdf files)

F: Drive Database log files (.ldf files)

Large Project with SQL Server

The following example shows a configuration for a large project using Microsoft SQL Server

2008 SP3.

C: Drive RAID 1

E: Drive

F: Drive

G: Drive

RAID 10

RAID 10

RAID 0 or 1 hard drive

2 hard drives internal to the server for the operating system and the Page File

8-12 SAN drives for the data files for the SQL Server Master,

Site, Site Schema, Catalog, Catalog Schema, Model, Report, and Report Schema databases.

4-8 SAN drives for log files for the SQL Server Master, Site,

Site Schema, Catalog, Catalog Schema, Model, Report, and

Report Schema databases.

2 SAN drives for the SQL Server temp database and

SmartPlant 3D backup files and the Page file

Large Project with Oracle

The general recommendation for a large project on an Oracle database is:

User

S3D .d files 10

S3D .i files 10

Redo Log

& SYSAUX

RAID

Level

10

Undo Log 10

Physical Disks in Array

Disk Space Requirement Purpose or Contents

12 No specific requirement

(N.S.R.) / 500 GB

Oracle .d data files for databases

8 N.S.R. / 150 GB

4

4

3

N.S.R. / 150 GB

N.S.R. / 150 GB

500 GB

Oracle .l index files for databases

Oracle Redo Logs,

StreamsTableSpace

(Workshare only)

Oracle Undo Logs and

Oracle System Files

Oracle Archive Log Archive

Log

OS, page file

5

1 2 N.S.R. operating system and page file

Be sure to spread the Oracle files across separate arrays for added redundancy.



Global Workshare Configuration Distribution Server Sizing

Global Workshare Configuration (GWC) might require a separate server for distribution for large projects.



Intel Xeon

®

5600 Series or better (64-bit instruction set, not Itanium



4 GB to 32 GB or greater RAM depending on project size

®

)



For hard drive size, see SmartPlant 3D Project Hardware Sizing Recommendations (on

page 28)



Backup system for server



Access to DVD drive, either locally or through a network connection



1 GbE or higher network interface for client connections



Distribution database on a RAID 1 or RAID 10 disk array (RAID 5 is not ideal because of the many writes produced by replication.)



Distribution database log file on its own dedicated RAID 1 disk array

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.

Interference Checking (IFC) Server Sizing

You should have a remote project processing computer for interference checking (IFC) that is separate from the computer hosting the databases. The interference checking computer can process more than one Plant. This computer does not need to be a high-end server, but should meet the minimum hardware requirements for a client computer. See SmartPlant 3D

Workstation recommendations (on page 22) for these requirements.

There is not a specific hard drive size requirement because the interference detection service does not store information locally.

Batch Server Sizing

You can use remote project processing computers, or batch servers, to off-load compute intensive tasks such as updating drawings in the Drawings task or running database backups and integrity checks in Project Management.

You should have at least one remote project processing computer for each site database. This remote computer does not have to be a high-end server, but should at least meet the minimum hardware requirements for a client computer. See SmartPlant 3D Workstation

Recommendations (on page 22) for these requirements.



A batch server runs only one batch job at a time. The maximum number of batch jobs that can run in parallel for a site database is equal to the number of batch servers.



You can use one or more batch servers for a single site database containing multiple model databases.



You cannot use a single batch server for multiple site databases.



File Server Sizing

You will need a computer to act as a file server with enough disk space for symbols and files.

This computer does not need to be a high end-server, but should meet the minimum hardware requirements for a client computer. See SmartPlant 3D Workstation Recommendations (on

page 22) for these requirements.

License Server and Name Generator Server Sizing

The Name Generator Service can be installed on a stand-alone computer or can be installed on the same computer used for the file server, batch server, IFC server, or license server.

License Server

SmartPlant License Manager (SPLM) uses server/client architecture to distribute licenses for

SmartPlant 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.

Hardware Configurations

The SmartPlant License Manager licensing computer software should 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 automated changes that cause the hardware information not to match with the information used to generate the license key will result in a failure of the authentication process.

Virtual (including VMware®), shadowed, mirrored, dynamic, or distributed hardware configurations cannot be used as a SmartPlant License Manager licensing computer. This includes terminal (application) servers, networked and distributed storage management systems, and so forth. When these specialized systems occur in the user's network, the

SmartPlant License Manager Server licensing computer should be installed on a separate dedicated hardware configuration system. The SmartPlant License Manager licensing computer should be situated on the user's network where it can be accessed by all systems that are running application software that relies on the SmartPlant License Manager licensing computer for license management.

Multiple SmartPlant License Manager licensing computers can be used in the user's network as long as each system is a unique hardware system/installation. If SmartPlant License Manager licensing computers are cloned after the license key has been installed, then the license management will fail on the cloned system. Each SmartPlant License Manager licensing computer requires its own unique license key.



RAID (redundant array of independent disks) and SAN (storage area networks) are not supported on a SmartPlant License Manager license computer.

The license computer must have the same version (or later) of SmartPlant License Manager installed as any client computers. In other words, you cannot use a newer version on a client computer to retrieve a license from an older version of SmartPlant License Manager on the licensing computer. The license computer must have the same version (or a newer version) installed than the clients.



Silent Installation

You can use the Windows Installer to install and uninstall the software using a command line rather than the normal user interface. One advantage of using a command line to install software is that you can perform unattended installations. The following command line parameters and arguments can be used with the Windows Installer executable (msiexec.exe) to perform a silent installation of the product:

To get a list of command line arguments for msiexec.exe, enter in a command window: msiexec.exe /?

Required arguments (for silent install):

/qn

/i <path and file name of msi file>

SERIALNUMBER=<serial number>

SLAACCEPT=Yes

If the PIDService feature is added, the following are also required:

NAMEGENUSERNAME=<mydomain\myuserid>

NAMEGENPASSWORD=<mypassword>



/qn means no user interface of any form is displayed. If you do not include /qn on the command line, dialog boxes are displayed during the installation process.



SLAACCEPT=Yes means that you are accepting the Software License Agreement.

Optional Arguments

INSTALLDIR=<path to install to>

ADDLOCAL=<comma delimited list of user-selectable features to install>

REMOVE=<comma delimited list of user-selectable features to remove>

/L <path, file name of logging file>

/x <path to msi file>

Default

C:\Program Files\SmartPlant\3D

See the table below for additional information.

See the table below for additional information.

Uninstalls SmartPlant 3D



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



The arguments for the command line are case-sensitive.



If you are going to install SmartPlant 3D silently with a script under a Terminal Services

Server in Application Server mode, we recommend that you update the script to include a

Change User mode command to set the user mode to Install mode first, and then back to

Execute mode after the SmartPlant 3D installation command. This ensures that changes written to registry key HKEY_CURRENT_USER are properly redirected to their corresponding HKEY_LOCAL_MACHINE registry after each user logs in into the


SmartPlant 3D Hardware and Software Recommendations system. These steps are also recommended when applying hot fixes and service packs in a silent install.

List of User-Selectable Features

In the following table, the first column contains the displayed feature name as seen on the

Select Features dialog box during regular installation. The second column contains the command line feature name, which is case sensitive, to use with the ADDLOCAL and REMOVE arguments. The third column displays if the feature is displayed by default if ADDLOCAL and

REMOVE are not set.

To add or remove user-selectable features, use ADDLOCAL and REMOVE. If neither of these arguments is used, the features shown below are not installed. If

ADDLOCAL is set to

ProjectEnvironment and Server (ADDLOCAL=ProjectEnvironment,Server),

ProjectEnvironment (Project Management) and Server (SmartPlant 3D Server Connectivity) are installed.

Displayed Feature Name

Project Management

Piping Specification Remote

Access Server

SmartPlant 3D Server

Connectivity

Bulkload Reference Data

Database Interference Detection

Service

Command Line Feature Name

ProjectEnvironment

PIDService

Server

Bulkload

IFCService

Installed by Default

No

No

No

No

No

36

Examples of running client silent install from the command line:

This command line installs the product into the default location, C:\Program

Files\SmartPlant\3D. 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. msiexec.exe /i "<Path>\S3DInstallation.msi" SERIALNUMBER=12345678901234

SLAACCEPT=Yes /qn

This command line installs the product into the default location, C:\Program

Files\SmartPlant\3D. It also creates a verbose logging file called loggingfile.log into the path provided. msiexec.exe /i "<Path>\S3DInstallation.msi" SERIALNUMBER=12345678901234

SLAACCEPT=Yes /qn /Lvoicewarmup "<path>\loggingfile.log"

This command line installs the product into location, D:\Program Files\SmartPlant\3D. It also creates a verbose logging file called loggingfile.log into the path provided. msiexec.exe /i "<Path>\S3DInstallation.msi" SERIALNUMBER=12345678901234

SLAACCEPT=Yes INSTALLDIR="D:\Program Files\SmartPlant\3D" /qn

/Lvoicewarmup "<Path>\loggingfile.log"

This command line installs all features of SP3D, including PIDService into the location,

D:\Program Files\SP3D. No logging file is created (unless an error occurs).


SmartPlant 3D Hardware and Software Recommendations msiexec.exe /i "<Path>\S3DInstallation.msi" SERIALNUMBER=12345678901234

SLAACCEPT=Yes INSTALLDIR="D:\Program Files\SmartPlant\3D" ADDLOCAL=ALL

NAMEGENUSERNAME=<mydomain\myuserid> NAMEGENPASSWORD=<mypassword>/qn

This installs all of the features listed above except PIDService into the location D:\Program

Files\SmartPlant\3D. No logging file is created (unless an error occurs). msiexec.exe /i "<path>\S3DInstallation.msi" SERIALNUMBER=12345678901234

SLAACCEPT=Yes INSTALLDIR="D:\Program Files\SmartPlant\3D" ADDLOCAL=ALL

REMOVE=PIDService /qn

This command line uninstalls the software with no user interaction but displays the progress on screen. msiexec.exe /passive /x "<path>\S3DInstallation.msi" /l+*

C:\temp\Passive_Removal.log

You can identify installation errors by searching for the string "return value 3" in the log file.

If you do not specify a name or location for the log file, it is automatically given a unique name beginning with the characters "MSI" and ending with the .LOG file extension. The log file is created in the %temp% folder.

Reference Data Installation Options

You must specify which version of the reference data product to install, such as SP3D, SM3D, or MHE. The argument that controls the version is PRODUCTTOINSTALL.

Example of running reference data silent install from the command line:

To install SP3D reference data in default location (C:\Program Files\SmartPlant\3D): msiexec /i "<path>\S3DReferenceData.msi" SLAACCEPT=Yes ADDLOCAL=ALL

PRODUCTTOINSTALL=SP3D /qn

Name Generator Installation Options

The name generator requires a separate installation procedure after installing the reference data. You must include the NAMEGENUSERNAME and NAMEGENPASSWORD arguments when installing the name generator.

Example of running name generator silent install from the command line:

To install the Name Generator in default location (C:\Program Files\SmartPlant\3D):



On the 32-bit computers, you can use the following command-line argument: msiexec /i "<path>\S3DNameGenerator.msi" SLAACCEPT=Yes ADDLOCAL=ALL

NAMEGENUSERNAME=<mydomain\myuserid> NAMEGENPASSWORD=<mypassword>

/qn



You can also use the above command-line argument on the 64-bit computers to install the

64-bit version of the Name Generator.



To install the 32-bit version of the Name Generator on the 64-bit computers, use the following command-line argument:

Msiexec.exe /i “<path>\S3DNameGenerator.msi” SLAACCEPT=Yes ADDLOCAL=ALL

X86NAMEGEN=true NAMEGENUSERNAME=<mydomain\myuserid>

NAMEGENPASSWORD=<mypassword> /qn



To install Symbols and Custom Documentation in default location (C:\Program

Files\SmartPlant\3D): msiexec /i "<path>\S3DReferenceData.msi" SLAACCEPT=Yes

ADDLOCAL=Symbols,CustomDoc /qn

See Also

SmartPlant 3D Database Server Recommendations (on page 21)

Recommendation for Database Monitoring (on page 185)

Monitoring the Databases (on page 63)

Assign System Administrator Privileges for SQL Server 2008 (on page 48)

Silent Installation for Service Packs

You can use the Windows Installer to install the service pack software using a command line rather than the normal user interface. One advantage of using a command line to install software is that you can perform unattended installations. The Windows Installer and the

SP3DHotFixInstaller command line options do not run from the UNC path. You need to map to a drive letter. If errors occur during installation, they are logged to your temp folder in a file called patchinstaller.log.

The following command line parameters and arguments can be used with the Windows Installer executable msiexec.exe) to perform a silent service pack installation of the product:

To get list of command line arguments for msiexec.exe, enter in a command window: msiexec.exe /?

Syntax msiexec.exe /update "<path and file name of msp file>" /qn

Required arguments (for silent install):

/qn

/update <path and file name of msp file>

Where <command option> is:



Installation - This installs the service pack or hot fix.



Referencedata - This installs the Reference Data service pack or hot fix.



ProgrammingResources - This installs the Programming Resources service pack or hot fix.

Optional Arguments

/L Logging file. /L<logging options> "<path>\<Log Filename>.log"

The arguments for the command line are case-sensitive.

See Also

SmartPlant 3D Database Server Recommendations (on page 21)

Monitoring the Databases (on page 63)

Assign System Administrator Privileges for SQL Server 2008 (on page 48)


SmartPlant 3D Installation Guide

SmartPlant 3D Hardware and Software

Recommendations

SmartPlant 3D Database Server Recommendations

Applicable Hardware

Hardware Recommendations

Supported Operating Systems

Supported Database Servers

Software Prerequisites

SmartPlant 3D Workstation Recommendations

Applicable Hardware

Hardware Recommendations

Video Cards

Supported Operating Systems

Supported Database Clients

Software Prerequisites

Software Loading Order

Special Consideration for Non-English Locales

Virus Scanners and Performance

Installation Checklist

Disk Partitioning Guidelines

Recommended Disk Space for Software Setup

SmartPlant 3D Project Hardware Sizing

Recommendations

Concurrent Users

Project Size Estimates

One small project

One medium project

One large project

Modeling (Detail Design) Workstation Sizing

OpenGL Graphics Cards

System Administrator Workstation Sizing

Database Server Sizing

Server Specifications

Hard Drives

Small Project with SQL Server

Large Project with SQL Server

Large Project with Oracle

Global Workshare Configuration Distribution Server Sizing

Interference Checking (IFC) Server Sizing

Batch Server Sizing

File Server Sizing

License Server and Name Generator Server Sizing

License Server

Hardware Configurations

Silent Installation

List of User-Selectable Features

Examples of running client silent install from the command line:

Reference Data Installation Options

Name Generator Installation Options

Silent Installation for Service Packs

Table of contents