Spp Id Install Guide

(1)

SmartPlant P&ID

Installation and Upgrade Guide

SP-P&ID 2009 SP4 (6.0.4) and SPEM 2009 SP5 (6.1.5) January 2009/September 2011

(2)

Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation.

U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.

Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation

P.O. Box 240000 Huntsville, AL 35813

Terms of Use

Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.

Warranties and Liabilities

All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. 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 discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.

Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work.

Trademarks

Intergraph, the Intergraph logo, PDS, SmartPlant, SmartMarine, FrameWorks, I-Convert, I-Export, I-Sketch, IntelliShip, INtools, ISOGEN, MARIAN, SmartSketch, SPOOLGEN, SupportManager, and SupportModeler are trademarks or registered trademarks of Intergraph Corporation or its subsidiaries in the United States and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation. MicroStation is a registered trademark of Bentley Systems, Inc. Other brands and product names are trademarks of their respective owners.

(3)

SmartPlant P&ID Installation and Upgrade Guide 3

S

E C T I O N

1 Welcome to SmartPlant

The Intergraph SmartPlant family of process industry solutions is an open line of

discipline-specific software tools that provide an integrated solution for the entire plant life cycle. Knowledge-based, intuitive, easy-to-use, accessible, flexible, and data-driven, SmartPlant supports global workflows. The software enables users to create logical and physical definitions of the plant model and enables access to plant data from conceptual design to decommissioning. SmartPlant is the fulfillment of the Intergraph vision to speed and improve the creation of

information and to provide this data to multiple users at any moment in the appropriate form. Workflows are compressed, reducing production time, lowering costs, enhancing global execution, and extending the life and usability of plant information.

The successor to the Intergraph Plant Design System (PDS), SmartPlant includes expanded functionality for front-end engineering and design (FEED), construction, operation, and maintenance phases.

Installation Checklist

For the recommended installation workflow, see the SmartPlant P&ID Installation Checklist: (SPPIDInstall_Checklist.xls), delivered during product setup to the ..\SmartPlant\P&ID Workstation\Program\resdlls\0009\ folder.

Introducing SmartPlant P&ID

SmartPlant P&ID creates intelligent P&IDs by populating the database with relevant plant data. This method provides valuable information throughout the plant life cycle. As a

data-centric, rule-based solution for the P&ID life cycle, SmartPlant P&ID helps users improve design quality, data consistency, and standards compliance. With quick access to supporting engineering data, SmartPlant P&ID significantly cuts design and modification time and increases accuracy with its exclusive data-centric approach and use of design rules, automatic checks, and drag-and-drop capabilities.

SmartPlant P&ID is vastly different from graphic-driven P&ID solutions of today. All data from the P&ID is stored in the plant database and adheres to plant standards. The graphical

representation of the P&ID is a view or a report of the data. The strong data import and export facilities of SmartPlant P&ID allow users to populate the system with relevant plant data, such as process data from process simulation databases based on Aspen Basic Engineering from Aspen Technologies, Inc. or equipment and line lists. You can then use this information in the

SmartPlant P&ID Stockpile to design the P&ID.

The rule-based and automation capabilities of SmartPlant P&ID also differentiate it from other P&ID systems. SmartPlant P&ID features a comprehensive, user-definable rule-based system that assists the engineer during the design phase of the plant and subsequent life cycle

phases. Data is entered directly into the database; rules are executed; and feedback is immediate. The design rule-base confirms data consistency and compliance with plant and engineering standards, allowing faster, more efficient design with less iteration.

SmartPlant P&ID incorporates the latest Microsoft technologies, such as OLE automation, to provide integration with existing data and other systems. Running on various Microsoft Windows

(8)

8 SmartPlant P&ID Installation and Upgrade Guide operating system platforms, SmartPlant P&ID does not require a traditional, expensive CAD engine for P&ID creation. The open architecture of SmartPlant P&ID permits integration with other systems, such as Intergraph PDS, SmartPlant Instrumentation, and Aspen Basic Engineering, all of which allow users to share data with third-party software.

SmartPlant P&ID Program Group

SmartPlant P&ID provides multiple views of a central, unified data structure that represents the plant model. A view is a visual presentation of the data in the plant model and can be a schematic drawing or a table. The plant model is the computer representation of the conceptual design, including all plant components and their relationships. By manipulating model views, you can organize the information within the plant model to better understand and maintain the data. SmartPlant P&ID has several programs and utilities for running and managing your plant data.

SmartPlant P&ID provides the design environment for

SmartPlant P&ID drawings.

SmartPlant P&ID Drawing Manager allows you to create

and delete drawings, manage drawing versions, and print multiple drawings. Drawing Manager also allows you to perform Workshare and project-specific commands.

SmartPlant P&ID Insulation Specification Manager

allows you to create and modify lookup tables for insulation specifications and thicknesses.

SmartPlant P&ID Options Manager defines plant-wide

graphic standards for symbology, gapping, heat tracing, and formats. Options Manager also defines paths to SmartPlant P&ID files and directories.

SmartPlant P&ID Rule Manager defines rules for

placement and property copying on placement.

SmartPlant Engineering Manager performs higher-level data management tasks, such as specifying user permissions, designing plant hierarchies, and so forth. For more information about SmartPlant Engineering Manager, see the SmartPlant Engineering Manager User's Guide and the appropriate sections of this guide.

SmartPlant Engineering Manager

SmartPlant Engineering Manager provides all the tools you need to effectively set up and manage your work with SmartPlant applications. SmartPlant Engineering Manager takes advantage of a client/server design that greatly enhances performance and lowers the cost of ownership. Because it is built on few Microsoft dependencies and is not web-based, SmartPlant Engineering Manager requires no web server. The intuitive user interface design, with its streamlined layout, allows you to easily manage user access and to share plant data.

Supporting SmartPlant P&ID, SmartPlant Instrumentation, and SmartPlant Electrical, SmartPlant Engineering Manager manages the plant structures while the applications themselves are responsible for manipulating the actual data (including creating, deleting, modifying, launching, and so forth). SmartPlant Engineering Manager allows you to view not only the data related to the whole site but also data related to individual plants and projects. You can create and maintain SmartPlant Engineering sites, plant structures and projects, in addition to adding plant group types, modifying plant attributes, creating and modifying hierarchies, and associating SmartPlant applications.

(9)

SmartPlant Engineering Manager Program Group

The SmartPlant Engineering Manager program group provides several utilities for managing your plant data.

SmartPlant Engineering Manager allows you to create the

SmartPlant site and plants. You can create plant structures, plant groups, hierarchy templates, as well as define the access to plant data on many levels.

Catalog Manager allows you to create and modify symbols and

labels.

Data Dictionary Manager allows you to add properties to

SmartPlant database tables, define external programs, view relationships, and create and modify select lists.

Data Dictionary Template Comparison Utility allows you to

determine the differences between two data dictionary template files or between one data dictionary template file and the corresponding data dictionary/schema from a plant.

Filter Manager allows you to create and modify filters to

discriminate on database data. Filters are used for displaying data in symbology, gapping, graphical views, reports, rules, and so forth.

Format Manager defines available formats for units of measure

properties.

Refresh Site Roles Utility allows you to automatically refresh the

roles in a site on a scheduled basis.

Reference Data Synchronization Manager provides tools for

comparing, synchronizing, and managing reference data across multiple plants. Used in conjunction with the Update Drawings functionality in Drawing Manager, this application is especially useful when you need to maintain a central set of reference data for all plants across a site without having a network or database connection between plants.

Upgrade Utility guides you through upgrading your SmartPlant

Engineering data.

(10)

(11)

S

E C T I O N

2

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 (like 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

Using databases with different character encodings such as CL8MSWIN1251 or JA16SJIS  Using multiple languages in a project, especially when crossing language-group boundaries Using an English server with different local language clients

(12)

International / Bi-lingual Projects

International bi-lingual projects are possible; however, great care must be used when configuring these environments. Limitations exist and must be properly understood:

Oracle and MS SQL Server databases can reside on any language operating system, as long as the databases have been created and configured with proper Unicode and collation settings.

All Microsoft operating systems (Japanese, Russian, German, and so forth) can enter English characters. The reverse, however, is not true in most cases.

Keyboard-locale can be changed as long as a character-set and code- page boundary is not crossed. For example, English, German, French, and Spanish characters can all be used in the same project because the same Windows code-page (1252) is used. However, Russian characters (code-page 1251) cannot be used in a US/English environment.

You must decide which language operating system will be the master for bi-lingual projects. The following is an example of a Russian-based project:

Companies in the United States and the United Kingdom are working a project with a Russian company and the deliverables (drawings, reports, and so forth) must ultimately be provided in Russian. The companies in the U.S. and the U.K. are working the project using the "master" Russian operating systems (possibly using virtual Russian operating systems running on VMware Workstation). The U.S. and U.K. companies can install and use English Microsoft Office products on the Russian operating system because Office products are globally enabled. If a Russian interface exists for the SmartPlant Enterprise application, then Russian users can use the Russian interface while the English-speaking users would continue to use the US/English interface. English-speaking engineers can enter English characters. Russian-speaking engineers can enter Russian characters.

However, because the Russian locale uses different decimal and character-set locales, everyone (English and Russian engineers) must use the Russian decimal symbol which is a comma. For customization purposes, databases can be modified to accommodate new Russian-specific requirements (fields, properties, and so forth.) Using filters, display sets, and other software features, bi-lingual projects can be further customized. Graphic data, reports, and so forth can be created in either or both languages.

Do not change regional settings to reflect a U.S. environment in order to resolve problems in a non-US/English homogeneous configuration. Doing this creates a heterogeneous configuration that will cause other possibly hidden problems that cannot be corrected. Everyone working on a project must use the same regional settings and character set throughout the life of the project.

Questions and Assistance

(13)

S

E C T I O N

3 Hardware and Software

Recommendations

Before beginning an installation of the SmartPlant software, verify that your servers meet the following requirements. These requirements assume that the SmartPlant software is not installed on the database server. You can install the SmartPlant software on the database server if you want to, but we do not recommend it.

SmartPlant Engineering Manager may be installed on its own workstation or it can run on the same computer with other engineering applications, such as SmartPlant P&ID or SmartPlant Electrical.

SmartPlant P&ID Database Server

Hardware Recommendations

Pentium machine with 2.4 GHz processor 2 GB RAM (or more for a large database) 100 BaseT or higher network interface

For all installations, DVD drive access, either locally or through a network connection

Supported Operating Systems

Microsoft Windows Standard Server 2003 R2 Service Pack 2, 32-bit and 64-bit Microsoft Windows Enterprise Server 2003 Service Pack 2, 32-bit

Microsoft Windows Enterprise Server 2003 R2 Service Pack 2, 64-bit Microsoft Windows Standard Server 2008 R2 Service Pack 1, 64-bit Microsoft Windows Enterprise Server 2008 R2 Service Pack 1, 64-bit

The operating system must be installed in the account where you have administrator privileges.

(14)

Supported Database Servers

 Microsoft SQL Server 2005 Service Pack 4, 32-bit and 64-bit  Microsoft SQL Server 2008 Service Pack 2, 64-bit

 Oracle Database 10g Release 2 (10.2.0.5), 32-bit and 64-bit  Oracle Database 11g Release 2 (11.2.0.2), 64-bit

Recommended Disk Space

Oracle Software SQL Server Software SmartPlant Engineering Manager Software Oracle Server installation 2 GB SQL Server Server installation 1 GB Initial SmartPlant Engineering Manager database 250 MB Initial Oracle instance 500 MB SQL Server Temporary database 100 MB

Total: 2.5 GB Total: 1.1 GB Total: 0.25 GB

SmartPlant P&ID Workstation

Hardware Recommendations

 Pentium IV with 2 GHz processor or higher  2 GB RAM

 100 BaseT or higher network interface

 DVD drive access, either locally or through a network connection

 Windows supported printer access, either locally or through a network connection

Supported Operating Systems

 Microsoft Windows XP Professional Service Pack 3, 32-bit  Microsoft Vista Business Client 1.0 Service Pack 2, 32-bit

 Microsoft Windows 7 Professional and Enterprise Service Pack 1, 32-bit and 64-bit Windows 7 is certified with UAC ‘On’ at Level 3 (Default)

Supported Database Clients

 Oracle 10g Client Release 2 (10.2.0.5), 32-bit  Oracle 11g Client tools (11.2.0.2), 32-bit

 Do not use Oracle 'light client' as it does not include some of the required .dll files.

(15)

Recommended Disk Space

Oracle Software SQL Server Software SmartPlant Software

Oracle Client installation 1 GB SQL Server Client installation 100 MB SmartPlant Engineering Manager 2009 SP5 (full installation) 250 MB SmartPlant P&ID 2009 SP4 (full installation) 250 MB SmartPlant Schema Component 25 MB SmartPlant Client 30 MB

Total: 1 GB Total: 0.1 GB Total: 0.55 GB

Software Prerequisites

 Adobe® Reader 9.0 or later compatible version (required for viewing the Software License Agreement and Printable Guides). The latest version is downloadable from the Adobe Web site.

 SmartPlant License Manager 2010. The licensing is delivered on its own CD that comes with your SmartPlant P&ID product CD.

 Microsoft Internet Explorer 7.0 or 8.0 (required for viewing the Online documentation delivered with the software)

 Microsoft XML Core Services (MSXML) 6.0 Service Pack 1

 One of the following versions of Microsoft Office (Microsoft Excel is required for working with report templates and for viewing the Installation Checklist and various other files):

Microsoft Office Version Supported Operating Systems

2003 Service Pack 3 Windows XP or Server 2003

2007 Service Pack 2 with Hotfix Package (msoshext-x-none.msp): February 22, 2011 http://support.microsoft.com/kb/2483216

Windows Vista or Windows 7

2010 (32-bit only) with Hotfix Package (msoshext-x-none.msp): February 22, 2011 http://support.microsoft.com/kb/2483230

Select for download the 32-bit file: office2010kb2483230fullfilex86glb

Windows 7 or Server 2008

Microsoft Office must include the installation of Visual Basic for Applications.  SmartPlant 3D Piping Specification Remote Access Client, Version 01.00. The Piping

Specification Client software is required for using SmartPlant 3D specifications in the

SmartPlant P&ID Piping Specification Utility and is available on the SmartPlant P&ID product CD.

 Microsoft Data Access Components (MDAC) 2.8 Service Pack 1

MDAC is delivered as part of Microsoft Windows XP, Windows Server 2003, Vista, and Windows 7 installations.

(16)

Optional Software

Apart from SmartPlant Engineering Manager and SmartSketch, the following software programs are not Intergraph corporation software and are owned by third parties. It is the responsibility of the customer to select in its sole discretion the applicable third party software the customer desires to use to generate reports and Intergraph makes no recommendation as to the choice of said third party software. The customer is responsible for obtaining a valid license to use said third party software from the owner of said third party software and to pay any license fees to the owner of said third party software for the use of said third party

software. INTERGRAPH DISCLAIMS AND MAKES NO WARRANTY EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR THE WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE IN REGARDS TO SAID THIRD PARTY SOFTWARE.

 For administrative functions, SmartPlant Engineering Manager 2009, SP5  For working in a Citrix environment, Citrix Presentation Server 4.5 or XenApp 6

 One of the following drawing software programs (for compatibility with the 'Save As' feature):  SmartSketch 2009, 2009 SP1, 2009.1, or 2009.1 SP1

 Autodesk AutoCAD 2000 or 2002

(17)

S

E C T I O N

4 Oracle Installation and Configuration

Because system configurations, database software, and individual company standards vary, use this section as a checklist instead of step-by-step instructions. Consult your Oracle software documentation for information as to which versions of Oracle database can be used with which versions of the Windows operating system.

Please contact Intergraph Customer Support (http://support.intergraph.com) for specific configuration questions.

Oracle Instances

If one server hosts the databases of several products, Intergraph recommends that each product's database be a separate instance, each of which can host multiple plants.

The advantage of placing each product's database 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.

We recommend installing and configuring Oracle locally, not by remote desktop connection. Oracle recommends that database activity on the database server consume no more than 50

percent of the available memory.

Configure Oracle Networking Components

Oracle Net combines configuration abilities with component control to provide an integrated environment for configuring and managing client connections to services via a net service name. SmartPlant Engineering Manager and P&ID use the Oracle Net service to establish and maintain network sessions from client applications to the Oracle database server. After a network session is established, this utility acts as a data courier for the client application and the database server.

See the Oracle Net Services Administrator's Guide and the Oracle Net Services Reference Guide in your Oracle documentation for more information about using this utility and creating net service name connections. If you follow the procedures provided to Install Oracle Server Software (Basic Installation for Enterprise Edition) and Install Oracle Client Software, the Oracle Networking Components should be configured correctly.

 For SmartPlant P&ID to access the database, you must load and configure Oracle Net

Services on the database server and on each end-user SmartPlant workstation. If

(18)

18 SmartPlant P&ID Installation and Upgrade Guide SmartPlant Engineering Manager is installed on the database server, you must load and configure Oracle Net Services on that server, in addition to the Oracle TCP/IP Protocol

Adapter.

If SmartPlant Engineering Manager is installed on a workstation other than the database server, you must load the Net Services and the Oracle TCP/IP Protocol Adapter on the SmartPlant Engineering Manager computer. You must also load the Net Services and the

Oracle TCP/IP Protocol Adapter on the Oracle database server.

 Net Manager is installed with the Net Services software and allows you to create a database Net Service Name, which SmartPlant uses to communicate with the database.

 The version of Net Services must be the same on all computers.

Oracle Installation Workflow

The following workflow is necessary for installing Oracle for use with SmartPlant P&ID. Depending on which version of Oracle you are using and on the operating system installed on your machine there may be differences in the required workflow. Consult your Oracle software documentation for information as to which versions of Oracle database can be used with which versions of the Windows operating system.

Please contact Intergraph Customer Support (http://support.intergraph.com) for specific configuration questions.

 Installing Oracle Database Server (on page 18)  Create an Oracle Listener (on page 19)

 Creating an Oracle Instance (on page 19)  Installing Oracle Client (on page 23)

Installing Oracle Database Server

The following editions of Oracle Database Server are available:

 Standard Edition — For department or workgroup level applications, or for small-to-medium sized enterprises (SMEs). It is engineered to provide core relational database management services and options. If you select this installation type, you must purchase additional licenses if you want to install extra Enterprise Edition options.

 Enterprise Edition — For enterprise-level applications. It is engineered for mission-critical, high-security online transaction processing (OLTP) and data warehousing environments. If you select this installation type, all separately licensable Enterprise Edition options are installed.

 Personal Edition — Not supported by SmartPlant Instrumentation.

(19)

Install Oracle Database Server

1. Double-click the Oracle setup icon..

2. On the Select Installation Method page, click Basic Installation, and from the Installation Type list, select the required installation.

Do not select Personal Edition. SmartPlant Instrumentation does not support this installation type.

3. Clear the Create Starter Database check box and then click Next.

4. On the Product-Specific Prerequisite Checks page, ignore the Checking Network Configuration requirements warning and click Next.

5. On the Warning dialog box, click Yes.

6. On the Summary page, click Install.

7. Complete the installation and then click Exit. 8. Restart the server machine.

9. Install the latest Oracle patch.

Create an Oracle Listener

1. On the Start menu, click All Programs > Oracle – OraDb10g_home1 > Configuration and Migration Tools > Net Configuration Assistant.

2. In the Oracle New Configuration Assistant Wizard, select Listener configuration and click Next.

3. Select Add, and click Next.

4. Define the listener name, for example, LISTENER and click Next.

5. On the Listener Configuration, Select Protocols page, select TCP and click Next.

6. On the remaining Wizard pages, click Next and then click Finish to complete the listener creation.

Creating an Oracle Instance

The Oracle instance is a workspace on the Oracle database server where Oracle keeps a single database. You can create as many instances as required and, in this way, append as many databases as you need on a single database server. However, note that appending instances on your Oracle database server can slow down your work in the P&ID database located on that server.

You need to create a new instance in Oracle if you have an existing Oracle database server whose parameters do not comply with the parameters required to use P&ID on Oracle. This way you can append the P&ID database to existing Oracle databases on your Oracle database server without losing your existing Oracle database information.

The instance creation process contains the following major steps:

1. Creating a new instance initialization file from an existing initialization file. 2. Modifying the database parameters in the new instance initialization file.

3. Modifying the Listener.ora file which Oracle will run when carrying out the instance creation process.

(20)

20 SmartPlant P&ID Installation and Upgrade Guide When creating an instance, Oracle takes-up some disk space. Therefore, you must have enough free disk space on the hard disk where the Oracle database is located to be able to create the new instance. The disk usage is as follows:

Oracle instance environment — 50 MB recommended

Oracle instance after running Oracle DB Setup — 80 MB recommended Oracle instance after initializing a domain — 150 MB recommended

See your Oracle User Guide for additional information about limitations on creation of instances.

Requirements for Oracle Instance Creation

Before creating an Oracle instance, make sure that you have Administrator's access rights in both your Oracle server database and the operating system installed on the server machine. If you still need to create an instance from the account in which you do not have Administrator's rights, and if your company's policy allows you to change the Oracle security, you can do the following: in the Sqlnet.ora file, add the # symbol before the

Sqlnet.Authentication_Services = (NTS) parameter to comment it out. The default location of

the Sqlnet.ora file will look similar to the following path:

\\<Oracle home folder>\Product\<Version*>\db_1\Network\Admin\ (* An example of the 6.0.4 folder name is 10.2.0)

Before starting an Oracle database you need to ensure that the RAM that this database occupies does not exceed the available RAM on your server. You can calculate the amount of RAM needed for the database by using the following Oracle parameters:

SHARED_POOL_SIZE (at least 10 MB) DB_BLOCK_SIZE

LOG_BUFFER SORT_AREA_SIZE

JAVA_POOL_SIZE and LARGE_POOL_SIZE are additional parameters that affect the RAM that the Oracle database occupies. These parameters appear if you select certain options when running the Oracle Database Configuration Assistant using a custom installation type.

For the DB_BLOCK_SIZE parameter, make sure that the value is at least 8192. As an alternative to the above calculation, you can use the following target parameters to determine the maximum amount of RAM:

sga_target (at least 100 MB is recommended)

pga_aggregate_target (at least 20 MB is recommended)

Create a New Oracle Instance

Make sure that all passwords, user names, folders, and files of the new instance are different from those of any existing instance.

All user names and passwords must use ASCII / English characters. Oracle does not support non-ASCII / English characters in user names or passwords and will not work. This limitation is an Oracle limitation, not Intergraph's.

1. On the Start menu, click All Programs > Oracle – OraDb10g_home1 > Configuration and Migration Tools > Database Configuration Assistant.

2. On the Welcome page, click Next.

3. In the Database Configuration Assistant Wizard, click Next until you reach the page Step 2 of 12: Database Templates.

(21)

SmartPlant P&ID Installation and Upgrade Guide 21 4. Select Custom Database and click Next.

5. On the page Step 3 of 12: Database Identification, do the following:

a. In the Global Database Name box, define the database name, for example, PID10gdb.

b. In the SID box, accept or modify the instance name that the software enters automatically

as you type the database name.

The database name and the instance name do not have to be the same. 6. Click Next.

7. On the page Step 4 of 12: Management Options, clear Configure the Database with

Enterprise Manager, and then, click Next.

8. On the page Step 5 of 12: Database Credentials, in the Password and Confirm Password boxes, type the password, for example, Oracle.

The following terms are reserved and cannot be used as passwords: manager (reserved for the SYSTEM user) and change_on_install (reserved for the SYS user).

9. Click Next until you reach the page Step 7 of 12: Database File Locations, and then do the

following:

a. Select Use Common Location for All Database Files.

b. Specify the path and folder, for example, D:\oracle\. c. Click Next.

10. On the page Step 8 of 12: Recovery Configuration, clear Specify Flash Recovery Data and click Next.

11. On the page Step 9 of 12: Database Content, do the following: a. On the Database Components tab, clear all the check boxes.

b. Click Standard Database Components, and then, on the Standard Database Components dialog box, clear all the check boxes and click OK.

c. If prompted you to disable local database management, click Yes. d. On the Custom Scripts tab, click No scripts to run.

e. Click Next.

12. On the page Step 10 of 12: Initialization Parameters, on the Memory tab, do the following: a. Select Custom.

b. Beside Shared Memory Management, select Automatic.

c. In the SGA Size box, enter 160 M Bytes.

(22)

22 SmartPlant P&ID Installation and Upgrade Guide The recommended total memory for one Oracle 10g instance is 260 M Bytes.

e. Click the Character Sets tab and do the following:

i. Under Database Character Set, select Use Unicode (AL32UTF8).

ii. Under National Character Set, select AL16UTF16 (the default)

The same database character set and national character set values should also be defined on your server.

The Default Language and Default Date Format values will reflect locale-specific

information.

(23)

SmartPlant P&ID Installation and Upgrade Guide 23 13. On the page Step 11 of 12: Database Storage, if you intend to create a SmartPlant Electrical or SmartPlant P&ID database in the current Oracle database, change the data file size of the

TEMP and USERS tablespaces to 100 MB.

To change the size, double-click the field under Size. 14. Click Next.

15. On the page Step 12 of 12: Creation Options, click Finish. 16. On the Confirmation dialog box, click OK.

17. Restart the server machine.

Oracle System User Requirements

The following lists describe the minimum Oracle system user privileges that need to be defined in order to work successfully with SmartPlant Engineering Manager and SmartPlant P&ID.

Default System User Privileges

CREATE ANY PROCEDURE CREATE ANY SEQUENCE CREATE ANY SYNONYM CREATE ANY TABLE CREATE ANY TRIGGER CREATE ANY VIEW CREATE DATABASE LINK

(24)

24 SmartPlant P&ID Installation and Upgrade Guide CREATE PUBLIC SYNONYM

CREATE ROLE

CREATE ROLLBACK SEGMENT CREATE SESSION CREATE SYNONYM CREATE TABLESPACE CREATE TRIGGER CREATE USER CREATE VIEW

DROP ANY SYNONYM DROP ANY TABLE DROP ANY TRIGGER DROP ANY VIEW DROP TABLESPACE DROP USER

EXECUTE ANY PROCEDURE INSERT ANY TABLE

SELECT ANY DICTIONARY SELECT ANY TABLE UNLIMITED TABLESPACE

Default Oracle Roles

The following roles are created by Oracle when an instance is created. These roles are expected to be present by SmartPlant Engineering Manager.

Role Privilege

CONNECT ALTER SESSION

CONNECT CREATE CLUSTER

CONNECT CREATE DATABASE LINK

CONNECT CREATE SEQUENCE

CONNECT CREATE SESSION

CONNECT CREATE SYNONYM

CONNECT CREATE TABLE

CONNECT CREATE VIEW

CONNECT EXECUTE ANY PROCEDURE

(25)

Role Privilege

RESOURCE CREATE INDEXTYPE

RESOURCE CREATE OPERATOR

RESOURCE CREATE PROCEDURE

RESOURCE CREATE SEQUENCE

RESOURCE CREATE TABLE

RESOURCE CREATE TRIGGER

RESOURCE CREATE TYPE

Installing Oracle Client

The Oracle client provides P&ID with the means to interface with the Oracle database server. You install the Oracle client after you have completed the Oracle database server installation. You can install the Oracle client either on a file server or on the local station. If you install the Oracle client on a station, make sure you have the appropriate access rights to the Oracle database server.

After the Oracle client installation process is complete, you proceed by installing P&ID. Before you start the installation process, make sure that the machine (file server or local station) has access to a CD-ROM or DVD drive. If your machine does not have access to a suitable drive, you need to copy all the installation files from the installation media to your local hard disk.

Installing Oracle Client Prerequisites

Make sure that your Oracle server version is 10.2.0.5.

Set up your client Windows regional and language options as you require. You can only set up these options before the client installation. If you want to change the regional and language options after the installation, you will have to reinstall the Oracle client for the changes to take effect

After the client installation, you must not change any of the default values of the NLS_LANG parameter on the client.

Install Oracle Client

1. Start the Oracle Universal Installer for Oracle client 10.2.0.4.

2. On the Select Installation Type page, from the list, select one of the following:

 Administrator — For users who need Administrator functions, such as the ability to create tablespaces.

 Runtime — For all other users.

3. On the Specify Home Details page, enter the name of the folder that will appear in the Start

menu and the folder path for the installation.

The Start menu folder name is also the name given to the Oracle Home folder in the Registry.

4. Clear the Create Starter Database check box and then click Next.

(26)

26 SmartPlant P&ID Installation and Upgrade Guide 6. On the Summary page, click Install.

7. On completion of the installation, when the Oracle Net Configuration Assistant opens, select the Perform typical configuration check box.

8. On the Welcome page, click Next.

9. On the Oracle Net Configuration Assistant: Done page, click Finish.

10. Complete the installation and then click Exit. 11. Restart the client machine.

12. Create an alias to the Oracle database on the client machine using Oracle Net Manager. The alias name can contain any alphanumeric characters without spaces.

13. Install the Oracle client 10.2.0.5 patch.

Register DLLs with RegSrv32

If you install Oracle Client on your SmartPlant workstation after installing SmartPlant Engineering Manager or P&ID software, the setup process will not register the igrOraspconnect.dll file. To rectify this, after you install Oracle Client, do the following:

1. From the Windows Control Panel, select Add/Remove Programs.

2. From the list of programs on your computer, select Intergraph P&ID. 3. Click Change/Remove.

4. On the Setup Type page, select Add/Remove install components (in SmartPlant P&ID

only).

5. Select Repair.

Oracle Tuning Recommendations

We recommend using the following Oracle tools for optimizing your database performance with the SmartPlant products.

OPTIMIZER_MODE Initialization Parameter

The OPTIMIZER_MODE initialization parameter establishes the default behavior for choosing an optimization approach for the instance. This parameter can be set in the initSIDname.ora or

init.ora file to one of the following four values. For more information, see the Oracle performance

tuning documentation at http://pbscrm.intergraph.com/pbs/sppid/Freeware/OracleAnalyzer.zip (http://pbscrm.intergraph.com/pbs/sppid/Freeware/OracleAnalyzer.zip).

CHOOSE — The optimizer chooses between a cost-based approach and a rule-based approach

based on whether statistics are available for the CBO. If the data dictionary contains statistics for at least one of the accessed tables, then the optimizer uses a cost-based approach and optimizes with a goal of best throughput. If the data dictionary contains no statistics for any of the accessed tables, then the optimizer uses a rule-based approach. This is the default value for the parameter.

ALL_ROWS — The optimizer uses a cost-based approach for all SQL statements in the session

regardless of the presence of statistics and optimizes with a goal of best throughput (minimum resource use to complete the entire statement). If you are not gathering statistics on your database, we do not recommend using this setting.

FIRST_ROWS — The optimizer uses a cost-based approach for all SQL statements in the

session regardless of the presence of statistics and optimizes with a goal of best response time (minimum resource use to return the first row of the result set). If you are not gathering statistics on your database, we do not recommend using this setting.

(27)

RULE — The optimizer chooses a rule-based approach for all SQL statements regardless of the

presence of statistics. If you are not gathering statistics on your database, we do not recommend using this setting.

Oracle Cost Based Optimizer (CBO)

We recommend using the Oracle Cost Based Optimizer (CBO) on Online Transaction Processing (OLTP) systems. Use the following settings to encourage the CBO to use indexes instead of full table scans.

OPTIMIZER_INDEX_CACHING = 90 OPTIMIZER_INDEX_COST_ADJ = 35

Before you can use the CBO, you must set the OPTIMIZER_MODE initialization parameter to CHOOSE.

ARCHIVELOG Mode

We also recommend running Oracle in ARCHIVELOG mode, which copies filled online redo logs to disk. You must specify the mode at database creation or by using the ALTER DATABASE statement. You can enable automatic archiving either dynamically using the ALTER SYSTEM statement or by setting the initialization parameter LOG_ARCHIVE_START to TRUE.

Running the database in ARCHIVELOG mode has several advantages over NOARCHIVELOG mode. You can:

Back up the database while it is open and being accessed by users. Recover the database to any desired point in time.

To protect the ARCHIVELOG mode database in case of failure, back up the archived logs. For more information, please see the SQL*Plus Backup and Recovery Concepts document in your Oracle documentation.

Other Recommendations

Some users have found using the following settings beneficial.

 System Tablespace Max_Extents = UNLIMITED (If you choose to set this parameter to 505, the database monitoring system will warn you if the system tablespace is growing heavily. This setting has no impact on performance.)

 Tablespace System / initial und next set to 64KB (Setting the pctincrease parameter to 50 allows you to take advantage of the dynamic growth provided by Oracle, leading to larger extents in a large database.)

 RollBackSegment und Temp-Tablespace create rollback segment <name> tablespace

rbs storage (optimal 10MB)

 begin dbms_stats.gather_database_stats (cascate => TRUE); end;/ (Gathers statistics on the schemas. Use with the OPTIMIZER_MODE variable set to ALL_ROWS.)

(28)

(29)

S

E C T I O N

5 Microsoft SQL Server Installation and

Configuration

The installation and configuration procedures described in this guide include only the steps required to install and use SmartPlant software in the Microsoft SQL Server

environment. Therefore, it is recommended that you refer to your Microsoft SQL Server User's Guide for additional information about Microsoft SQL Server.

If you intend to use the SmartPlant P&ID Connected Workshare functionality, you must use an Oracle database rather than SQL Server. Connected Workshare does not support SQL Server; however, Standalone Workshare does support SQL Server.

Because system configurations, database software, and individual company standards vary, use this section as a checklist instead of step-by-step instructions. For specific configuration

questions, contact Intergraph Customer Support (http://support.intergraph.com).

1. Using the Typical installation, load the Microsoft SQL Server software on your database

server.

2. Configure SQL Server to create your custom database. You will need to provide the database node name, Administrator user name, and Administrator password when performing the configuration.

SQL Server Client is required on any computer running SmartPlant Instrumentation on which you intend to perform administrative activities such as site, plant, or project creation, or on any computer on which backup or restore operations are performed.

When creating and configuring your databases, keep in mind that plant structures must be created in a SQL Server database separate from the site server database and that each plant must be in its own database. Database node names may not include periods (.) or spaces. If the backup location for your SQL site is located on a separate computer from your database,

you must modify the logon information for the SQL Server services using the procedure that follows.

When creating a database for SmartPlant Engineering Manager, the database name may not include periods (.) or spaces.

Create Microsoft SQL Server databases with locale-specific collation settings and ensure that all interacting databases have the same collation settings

(30)

Modify Logon Information for SQL Server Services

1. From the Windows Control Panel, select Administrative Tools > Services.

2. In the Services list, double-click SQLServer (MSSQLServer) to open the SQLServer (MSSQLServer) Properties dialog box.

The default instance for SQL Server 2005 is SQLServer (MSSQLServer).

In place of the default instance, you can use a named instance, for example: SQLServer (SPPID).

3. Click the Log On tab.

4. Select This account and type the user name and password for the domain user who will be

starting the MSSQLSERVER service. 5. Save your changes.

6. If the user defined in This account does not already have permissions to the share where backups are stored, grant the user read/write permissions to that share.

For more information about MSSQLServer properties and granting permissions to domain users, refer to your SQL Server and Windows documentation.

Install SQL Server 2005

1. Start SQL Server 2005 Setup.

2. On the Microsoft SQL Server 2005 Setup wizard, click Next until you reach the Components to Install page.

3. On the Components to Install page, do the following:

a. Select SQL Server Database Services.

b. Select Workstation components, Books Online and development tools and then click Next.

4. On the Instance Name page, select Default instance and click Next.

5. On the Existing Components page (if displayed), click Next.

6. On the Service Account page, do the following:

a. Select Use the built-in System account and then select Local system.

b. Under Start services at the end of setup, select SQL Server and click Next.

On the Service Account page, you must only select the SQL Server service. The other two services (SQL Server Agent and SQL Browser) are not needed for any SmartPlant software product. After the database server setup, the SQL Server service is created with the Automatic startup type, the SQL Server Agent service is created with the

Manual startup type, and the SQL Browser service is not created.

7. On the Authentication Mode page, do the following:

a. Select Mixed Mode.

(31)

SmartPlant P&ID Installation and Upgrade Guide 31 8. On the Collation Settings page, ensure that Collation designator and sort order is

selected, and from the list, select the appropriate designator corresponding to the national environment defined for the operating system on the client machines. For example, if the client environment is Russian, select Cyrillic_General as the collation designator.

If the national environment of the client machines is identical with the national environment defined for the server, just accept the default values on this page.  Ensure that the Case sensitive check box is cleared.

9. Click Next and complete the remaining steps.

10. After clicking Finish, restart the server machine.

Configure SQL Server Database Server

This procedure explains how to configure the server to avoid running out of memory.

By default, the server is configured to use unlimited memory.

As a quick alternative to this procedure, you can stop and then restart the server. To implement this procedure, you must have DBA permissions.

1. Click Start > Programs > Microsoft SQL Server 2005 Setup > SQL Server Management Studio.

2. On the Connect to Server dialog box, enter the required information as follows:

a. Beside Server type, select Database Engine.

b. Beside Server name, select the name of your server or instance.

c. Beside Authentication, select SQL Server Authentication.

d. Type a login name.

e. Type a strong password of a least 6 characters; this is a password that must include

upper- and lower-case characters, numeric and non-alphanumeric characters. f. Click Connect.

(32)

32 SmartPlant P&ID Installation and Upgrade Guide 3. In the Microsoft SQL Server Management Studio window, under the Object Explorer,

select the server (top-level node), right-click, and on the shortcut menu, click Properties.

4. Select the Memory page and do the following:

a. Select Use AWE to allocate memory.

b. Under Maximum server memory (in MB), set a suitable value.

If it is likely that a large number of users will connect to the database concurrently, set the maximum memory to a higher value to avoid poor performance.

5. Select the Database Settings page and change the value of Default index fill factor to 80.

Set Database Maintenance Options for SQL Server

You set the database maintenance options for SQL Server using the DBCC Utility. It is recommended that you run the following options about once a week:

CHECKCATALOG CHECKDB

You must use an SA connection for running these options. You should also update the database statistics as needed.

(33)

Run DBCC Utility Options for SQL Server

1. Open the SQL Server Management Studio.

2. In the Microsoft SQL Server Management Studio window, under the Object Explorer,

select the server (top-level node), right-click, and on the shortcut menu, click New Query. 3. Type the appropriate query using the syntax shown, for example:

DBCC CHECKCATALOG ('Site_Server1_DB')

You must enclose the name of your database within the quotes and parentheses as shown.

Identical syntax applies for the CHECKDB command. 4. Click Query > Execute.

5. View the Messages window for the results of the query.

You can save the results to an external file. To do so, click Query > Results To >

Results to File.

The software automatically corrects basic problems. For more complex problems, you must refer to the query results and correct these problems manually.

Update Statistics for SQL Server

1. Open the SQL Server Management Studio.

2. In the Microsoft SQL Server Management Studio window, under the Object Explorer,

select the server (top-level node), right-click, and on the shortcut menu, click New Query. 3. Type the following SQL script with the name of your database, for example:

USE Site_Server1_DB GO

EXEC SP_UPDATESTATS

This script updates the statistics for every table in the database.

Installing SQL Server Client

The SQL Server client provides with the means to interface with the SQL Server database server. You can install the SQL Server client on each client machine after you have completed the SQL Server database server installation.

Before you install the SQL Server client on a client machine, ensure that: SQL Server database server is installed on a database server machine.

The SQL Server client version is compatible with your SQL Server database server version. You have appropriate access rights to the SQL Server database server.

You do not need to install the SQL Server client on the computer where you installed the SQL Server database server, as all the client utilities are automatically installed during the SQL Server database server installation. See your SQL Server User Guide for additional information about SQL Server components and utilities.

(34)

Install SQL Server Client

1. Start SQL Server Client Setup to open the Microsoft SQL Server 2005 CTP Setup wizard. 2. Accept the licensing agreement.

3. Click Next until you reach the Registration page.

4. On the Registration page, type in the user details.

5. Click Next until you reach the Feature Selection page.

6. On the Feature Selection page, select the desired features.

(35)

SmartPlant P&ID Installation and Upgrade Guide 35 7. Click Next until you reach the Setup Progress page.

The Setup Progress page displays the progress and status of the components being installed.

(36)

36 SmartPlant P&ID Installation and Upgrade Guide 8. Click Next, to go to the Completion page.

(37)

S

E C T I O N

6 Installing the Software

This section describes how to set up your database and install SmartPlant Engineering Manager, SmartPlant P&ID and supporting software. Before you begin installing the software, verify that the computers on which the software components will be installed meet the requirements described in the SmartPlant Engineering Manager Hardware and Software Recommendations (on page 13).

The Open Database functionality, incorporated into all parts of the SmartPlant software, allows you to install pieces of the software on several different workstations. You do not have to maintain a server for just SmartPlant Engineering Manager. For example, you can install SmartPlant Engineering Manager and its related managers on one workstation, SmartPlant P&ID and its related managers on another, and the reference data on yet another workstation or file server. You could install all of the SmartPlant software on one workstation, or you could install SmartPlant Engineering Manager on one workstation, SmartPlant Catalog Manager on another workstation, and the remaining SmartPlant software on another workstation.

When installing on Vista or Windows 7 with the User Account Control setting at the default level, you should run setup.exe as an Administrator user, even if you are not logged on as an Administrator. To do this, select setup.exe, right-click and then select the Run as

administrator option. If not logged on as an Administrator, you will be prompted for Administrator

credentials to allow you to continue the setup.

Setting up the Database

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 SmartPlant software. The ultimate database creation and configuration depends on the policies and standards at your company.

SmartPlant Engineering Manager includes a number of deferrable database constraints, which are rules used to ensure database integrity by checking values at the time the information is written to the database. If all of the information does not fall within these embedded constraints, the information is not written to the database, and the software rolls back the transaction.

These deferrable database constraints are applied only when you use an Oracle database; SQL Server does not support them.

Spp Id Install Guide

SmartPlant P&ID

Installation and Upgrade Guide

Contents

S

1

Welcome to SmartPlant

Installation Checklist

Introducing SmartPlant P&ID

SmartPlant P&ID Program Group

SmartPlant Engineering Manager

SmartPlant Engineering Manager Program Group

S

2

Homogeneous Environments

Heterogeneous Environments

International / Bi-lingual Projects

Questions and Assistance

S

3

Hardware and Software

Recommendations

SmartPlant P&ID Database Server

Hardware Recommendations

Supported Operating Systems

Supported Database Servers

Recommended Disk Space

SmartPlant P&ID Workstation

Hardware Recommendations

Supported Operating Systems

Supported Database Clients

Recommended Disk Space

Software Prerequisites

Optional Software

S

4

Oracle Installation and Configuration

Oracle Instances

Configure Oracle Networking Components

Oracle Installation Workflow

Installing Oracle Database Server

Install Oracle Database Server

Create an Oracle Listener

Creating an Oracle Instance

Requirements for Oracle Instance Creation

Create a New Oracle Instance

Oracle System User Requirements

Default System User Privileges

Default Oracle Roles

Installing Oracle Client

Installing Oracle Client Prerequisites

Install Oracle Client

Register DLLs with RegSrv32

Oracle Tuning Recommendations

OPTIMIZER_MODE Initialization Parameter

Oracle Cost Based Optimizer (CBO)

ARCHIVELOG Mode

Other Recommendations

S

5

Microsoft SQL Server Installation and

Configuration

Modify Logon Information for SQL Server Services

Install SQL Server 2005

Configure SQL Server Database Server

Set Database Maintenance Options for SQL Server

Run DBCC Utility Options for SQL Server

Update Statistics for SQL Server

Installing SQL Server Client

Install SQL Server Client

S

6

Installing the Software

Setting up the Database