Documente Academic
Documente Profesional
Documente Cultură
Version 2013
March 2013
DSPI2-PE-200001B
Copyright
Copyright 1995-2013 Intergraph Corporation. All Rights Reserved. Intergraph is part of Hexagon.
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.
Terms of Use
Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee
has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software
product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to
the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable
number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for
licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution.
Trademarks
Intergraph, the Intergraph logo, PDS, SmartPlant, 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.
Contents
Preface .......................................................................................................................................................... 7
Internationalization .................................................................................................................................... 15
Symbol Editor allows you to customize symbols to fit your own design
conventions specifically for Layout reports and for Enhanced
SmartLoop drawings that use the Custom by Loop or Custom by Signal
generation methods.
In addition to the main application, a number of add-on utilities are available as separate
installations.
Intergraph IDEAL API is a set of components that are used to generate
reports containing SmartPlant Instrumentation data. IDEAL enables
you to retrieve data and display it in a Web browser in a format
appropriate for the report type.
DDP Export Utility allows you to specify parameters needed to create
a data file that is used to export dimensional data from SmartPlant
Instrumentation to Plant Design System (PDS).
External Editor allows you to view and modify external instrument
specification sheets (.psr and .isf files).
Process Data Editor allows you to view and modify external process
data sheets (.ipd files).
SAP Export Utility allows you to specify parameters needed to create a
data file that is used to export data from SmartPlant Instrumentation
to SAP.
Pre-Installation Requirements
The Setup Utility allows you to install required and optional components, such as SmartPlant
Instrumentation modules (for example, Administration, Instrument Index, Wiring), Import and
Merger utilities, documentation files, and so forth. You can install all or only some of the
components, depending on the amount of free space available on your hard disk, and your
engineering needs. For details of components that are required for working with SmartPlant
Instrumentation, see List of SmartPlant Instrumentation Components (on page 27).
You run Setup when:
Installing a new version of SmartPlant Instrumentation.
Upgrading an existing SmartPlant Instrumentation installation.
Adding selected SmartPlant Instrumentation components to an existing installation.
If you add any components to an existing installation, make sure that the version of the
components you install is the same as the version of the existing installation.
If you upgrade your current software version, it is recommended that you backup your current
database before you start the actual installation process.
For details of how to back up an entire Oracle or SQL Server database, you need to use Oracle
or SQL Server tools. For details, see SmartPlant Instrumentation Configuration and
Maintenance Guide, Backup and Restore. If you have System Administrator database access
rights, you can also back up your database by selecting to save a copy of your existing database
during the setup procedure.
When you install SmartPlant Instrumentation you need to determine the appropriate access
rights for each user (regular users, Domain Administrators and the System Administrator). For
details, see the Administration User's Guide, Access Rights.
You install SmartPlant Instrumentation either on the computer where you installed the
database server (file server) or on the local station. The following are some of the
environment characteristics that you should consider when deciding where to install
SmartPlant Instrumentation:
Free disk space The computer where you install SmartPlant Instrumentation should have
free disk space sufficient for the installation.
Network performance Most databases operate on local networks. Therefore, the local
network data transfer rate significantly influences the overall performance of the database
platform and SmartPlant Instrumentation. For this reason, if the local network
Internationalization
Supporting internationalization in a homogeneous environment is one of the enhancements
available in SmartPlant Enterprise. A homogeneous environment uses elements from only a
single locale. For example, a German customer running on a German operating system using
only German characters and German cultural conventions is a fully supported homogeneous
environment configuration.
Homogeneous Environments
When starting a new project, use extra care during installation and configuration to ensure the
proper creation and maintenance of homogeneous environments:
All the computers (servers and clients) within an integrated SmartPlant Enterprise
implementation must have the same regional settings, and no one should change the
regional settings after the project has started.
Do not cross the decimal locale boundary. This is the most common cause of numeric data
corruption and calculation errors. Having users with different regional settings (like with a
period versus a comma for the decimal point) causes the software to interpret values
unpredictably. For example, a motor with a rated power of 10.5 kW can be read by the
software as 105 kW 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 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:
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.
The operating system must be installed in the account where you have administrator
privileges.
The SmartPlant Instrumentation software cannot work with SQL Server 64-bit client
because it is a 32-bit application. The software works with SQL Server 32-bit client, which
can then work with SQL Server 64-bit server.
Total 2.5 GB
SQL Server 2008 Software SQL Server 2012 Software SmartPlant Instrumentation Software
SQL Server 2008 installation 4 GB SQL Server 2012 installation 6 GB Initial SmartPlant Instrumentation 200 MB
database
Software Prerequisites
Adobe Reader 11 or higher (required for viewing the Software License Agreement and
Printable Guides). The latest version is available from the Adobe Web site.
Microsoft Internet Explorer 9.0 (64-bit)
Microsoft .NET Framework 4
Windows Installer 4.5 (for SQL Server 2008)
Microsoft Office 2010 (32-bit or 64-bit)
SmartPlant License Manager Version 2012 (12.00.05.00 or later)
Oracle Data Access Components (ODAC) 11.2 release 2
Microsoft .NET Framework is delivered as part of Microsoft Windows Server
installation.
The operating system must be installed in an account where you have administrator
privileges.
Windows 7 is certified with UAC On at Level 3 (Default).
Total 1 GB
SQL Server 2008 Software SQL Server 2012 Software SmartPlant Instrumentation Software
SQL Server 2008 Client installation 2 GB SQL Server 2012 Client 2 GB SmartPlant Instrumentation application 1.6 GB
installation (full installation)
Software Prerequisites
Adobe Reader 11 or higher (required for viewing the Software License Agreement and
Printable Guides). The latest version is available from the Adobe Web site.
Microsoft XML Core Services (MSXML) 6.0 Service Pack 1
Microsoft Office 2010 (Microsoft Excel is required for working with report templates and
for viewing the Installation Checklist and various other files).
SmartPlant License Manager 12.00.05.00 or later.
Microsoft .NET Framework 4
Oracle Data Access Components (ODAC) 11.2 release 2
Microsoft .NET Framework is delivered as part of Microsoft Windows Vista and 7
installations.
Optional Software
Apart from 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 customer desires to use to
generate reports and Intergraph makes no recommendation as to the choice of said third party
software. 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.
One of the following drawing software programs, if needed for loop drawings:
SmartSketch 2011.x or similar graphical editor (required for editing border template
files and for symbol creation)
Autodesk AutoCAD version 2012 or higher. For compatibility with other versions, see
the Version Compatibility section of the Readme.htm file in the SmartPlant
Instrumentation folder
Bentley MicroStation J (not certified on Vista, Windows 7, or on a 64-bit machine)
Hardware Recommendations
Pentium IV with 3 GHz processor or Pentium dual core with 2 GHz processor or higher
2 GB RAM or higher
100 BaseT or higher network interface (1 Gbit recommended)
CD-ROM drive access, either locally or through a network connection
Windows supported printer access, either locally or through a network connection
The operating system must be installed in an account where you have administrator
privileges.
Windows 7 is certified with UAC On at Level 3 (Default).
Supported Database
Sybase Adaptive Server Anywhere 10.1
Software Prerequisites
Adobe Reader 11 or higher (required for viewing the Software License Agreement and
Printable Guides). The latest version is available from the Adobe Web site.
Microsoft Office 2010 (Microsoft Excel is required for working with report templates and
for viewing the Installation Checklist and various other files).
Microsoft .NET Framework 4
Optional Software
Apart from 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 customer desires to use to
generate reports and Intergraph makes no recommendation as to the choice of said third party
software. 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.
One of the following drawing software programs, if needed for loop drawings:
SmartSketch 2011.x or similar graphical editor (required for editing border template
files and for symbol creation)
Autodesk AutoCAD version 2012 or higher. For compatibility with other versions, see
the Version Compatibility section of the Readme.htm file in the SmartPlant
Instrumentation folder
Bentley MicroStation J (not certified on Vista, Windows 7, or on a 64-bit machine)
MicroStation Optional
Catalog Optional
Database
SmartPlant Optional
sample database
Installation Checklist
For the recommended installation workflow, see the SmartPlant Instrumentation Installation
Checklist:
(SPIInstall_Checklist.xls), delivered during product setup to the ..\SmartPlant\Instrumentation\
folder.
3. In the Installation for SmartPlant Instrumentation wizard, on the Welcome page, select
Remove and then click Next.
4. At the message prompt to confirm removal of the software, click OK.
5. At the Remove Existing Databases message prompt, click Yes or No as desired.
6. On the Maintenance Complete or Uninstall Complete page, click Finish.
14. On the Database Installation Options page, do one of the following to determine what to do
with your existing databases, such as In_demo.db (demonstration), Intools.db (empty), and
Intoolsef.db (for SmartPlant integration):
Keep old databases Select this option to use your existing databases from the
previous installation.
Back up old and install new databases Select this option to use new databases and
preserve the existing databases if you are upgrading your software version. Setup
renames the existing Intools.db to Intools(1).bk, In_demo.db to In_demo(1).bk, and
Intoolsef.db to Intoolsef(1).bk, where (1) is the running number for the old database.
Overwrite old databases Select this option to use new databases and delete the
existing databases.
If you overwrite your databases, you lose any user-defined data that you
have in these files.
15. On the Select Program Folder page, select the program folder where you want Setup to
install the program icons, and click Next to begin the installation.
16. On the Setup Complete page, if you want to view the Readme file, select the I would like to
view the Readme.htm file check box.
17. Click Finish.
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.
When installing Oracle 11g or creating an Oracle Instance, you must change the Installation
Parameter "sec_case_sensitive_logon" from Value = True to Value = False making sure a
check mark appears in the Override Default column. Failure to do so results in SmartPlant
Instrumentation being unable to connect to the Oracle database.
Path names for tablespaces in Oracle 11g must be no greater than 60 characters.
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.
7. Click Next.
8. On the Specify Installation Location window, specify the locations for the Oracle Base and
for the software location.
9. Click Next.
10. On the Summary window, click Install.
11. Complete the installation and then click Close.
12. Restart the server machine.
13. Install the latest Oracle patch.
on your Oracle database server can slow down your work in the SmartPlant Instrumentation
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 SmartPlant
Instrumentation on Oracle. This way you can append the SmartPlant Instrumentation
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.
4. Creating a new instance using the Database Configuration Assistant.
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.
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. If
your SmartPlant Instrumentation database has multiple specifications, we recommend that
you use the values 16384 or 32768.
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)
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, locate the Oracle folder and start the Database
Configuration Assistant.
2. On the Welcome page, click Next.
3. In the Database Configuration Assistant Wizard, click Next until you reach the page
Database Templates.
4. Select Custom Database and click Next.
5. On the page Database Identification, do the following:
a. In the Global Database Name box, define the database name, for example, SPI11gdb.
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 Management Options, clear Configure the Database with Enterprise
Manager, and then, click Next.
8. On the page 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 Database File Locations, and then do the following:
c. Select Use Common Location for All Database Files.
d. Specify the path and folder, for example, D:\oracle\.
e. Click Next.
10. On the page Recovery Configuration, clear Specify Fast Recovery Data and click Next.
11. On the page 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 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 Initialization Parameters, select the Memory tab and do the following:
a. Select Custom.
b. Beside Shared Memory Management, select Automatic.
c. In the SGA Size box, enter 160 M Bytes.
d. In the PGA Size box, enter 60 M Bytes.
The recommended total memory for one Oracle instance is 260 M Bytes.
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.
h. On the All Initialization Parameters dialog box, in the Name column, locate
sec_case_sensitive_logon.
a. Click Close.
13. On the page 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.
Roles
EXECUTE_CATALOG_ROLE <empty>
INTOOLS_ENGINEER with privileges:
CREATE VIEW
CREATE SYNONYM
CREATE SESSION
AUDIT ANY
CREATE TRIGGER
CREATE PROCEDURE
CREATE SEQUENCE
CREATE TABLE
SELECT_CATALOG_ROLE <empty>
3. Click Next.
4. On the Download Software Updates page, select Skip software updates and click Next.
5. On the Select Product Languages page, select English and click Next.
6. On the Specify Installation Location page, click the Browse button next to the Oracle Base
field and locate where you want to install the software.
The Software Location field is updated according to the information in the Oracle
Base field. If you want to change this location use the Browse button to navigate to the
required location.
7. Click Next.
8. On the Perform Prerequisite Checks page, click Next.
9. On the Summary page, click Install.
10. On the Install Product page, click Install.
11. On completion of the installation, click Finish
12. Restart the client machine.
13. 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. After
installing the Oracle client, the alias value appears in the Intools.ini file as a value of the
ServerName parameter in the [Database] section.
The systems described in the above figure can be physically located on the same computer or
on different computers which are connected on a local network.
The entire installation process consists of the following major steps:
1. Installing the Oracle database server. You perform this step only if you have not already
installed the Oracle database server on your system.
2. Installing the Oracle client and verifying the connection to the Oracle database server. You
perform this step only if you have not already installed the appropriate Oracle client on your
system.
3. Installing the appropriate SmartPlant Instrumentation components.
4. Connecting to the Oracle database and setting up the SmartPlant Instrumentation database
for Oracle (by running the DB Setup Utility).
5. Creating a new SmartPlant Instrumentation domain.
First, you install and configure the database server where SmartPlant Instrumentation will
store your data. Then you install the Oracle client through which SmartPlant Instrumentation
interfaces with the Oracle database server. If you have already installed Oracle as your
database server, you may need to modify your database server settings to adapt Oracle to
support the SmartPlant Instrumentation database.
After installing the Oracle database server and the Oracle client, you install SmartPlant
Instrumentation and configure the appropriate SmartPlant Instrumentation files. This way
you will also be able to use third-party applications such as CAD interfaces.
When Setup finishes installing the selected components, you need to configure SmartPlant
Instrumentation to connect and work with Oracle. At this stage, you create the tablespace
required for the Admin schema. For details, see the Administration User's Guide, Set Up a
SmartPlant Instrumentation Database for Oracle.
The final stage is to initialize a new domain in Oracle and set the initial parameters of the
domain. This way you prepare the database for creating the domain plant hierarchy and
defining engineering data.
If you are working with IDEAL, you must install SmartPlant Instrumentation Server,
which requires a special serial number. For installation details, see the SmartPlant
Instrumentation Server and IDEAL Installation and Configuration Guide.
The serial number is used for initial installation purposes only. A license key is
required to run SmartPlant Instrumentation. For more information, refer to the
SmartPlant License Manager Online Help.
8. On the Destination Folder page, specify the SmartPlant Instrumentation folder location and
click Next.
To choose an alternative destination, click Browse and navigate to the desired
destination folder, and then click Next.
9. For a custom installation, on the Select Features page, select the desired SmartPlant
Instrumentation components, and then click Next. To learn which components are required
to work with SmartPlant Instrumentation, see List of SmartPlant Instrumentation Components
(on page 27).
10. On the Oracle Server Information page, do the following:
a. In the Server box, type the communication alias name for your Oracle instance.
b. In the Database box, type the Oracle database name.
c. Click Next.
11. On the Select Program Folder page, select the program folder where you want Setup to
install the program icons, and click Next.
12. On the Start Copying Files page, view the settings of the current Setup session, and then
click Next to start copying the files to your hard disk.
After you click Next, Setup immediately starts copying all the components you
selected to the SmartPlant Instrumentation home folder. To undo this operation you will
have to uninstall SmartPlant Instrumentation. Therefore, if you need to make any
modification to the current Setup selections, click Back before you start copying the files.
13. On the Setup Status page, view the progress of the file transfer.
14. When the file transfer is complete, on the Important Notes page, read the text carefully as it
contains important information for the current version, and then click Next.
15. On the Readme dialog box, click Yes if you want to view the Readme file.
We recommend that you choose to view the Readme file, as it contains important
information about SmartPlant Instrumentation. You can find this file, Readme.htm, in the
SmartPlant Instrumentation home folder or in the root folder of the installation media.
16. On the Setup Complete page, click Yes if you want to restart your computer (before you can
use the program you must restart your computer).
17. Click Finish to complete the setup and installation.
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in
the SmartPlant Instrumentation installation. This printer is used for PDF generation and
should not be removed or used for any other purpose. If you are unable to generate PDF files
because this driver is missing, restore the driver by running the executable file PDFInstall.exe,
which is installed by default in the software installation folder path
..\SmartPlant\Instrumentation\.
8. When Setup detects an existing installation, it opens the Choose the Destination Folder
dialog box. Click Yes to install SmartPlant Instrumentation in the existing folder.
If you click No, the Destination Folder page opens. Click Browse and navigate to
another destination folder, and then click Next.
If you click No, you lose all the previous preferences and configuration
settings.
10. On the Database Installation Options page, do one of the following to determine what to do
with your existing databases, such as In_demo.db (demonstration), Intools.db (empty), and
Intoolsef.db (for SmartPlant integration):
Keep old databases Select this option to use your existing databases from the
previous installation.
Back up old and install new databases Select this option to use new databases and
preserve the existing databases if you are upgrading your software version. Setup
renames the existing Intools.db to Intools(1).bk, In_demo.db to In_demo(1).bk, and
Intoolsef.db to Intoolsef(1).bk, where (1) is the running number for the old database.
Overwrite old databases Select this option to use new databases and delete the
existing databases.
If you overwrite your databases, you lose any user-defined data that you
have in these files.
11. On the Styles.pbd File Installation Options page, do one of the following to determine what
to do with your existing Styles.pbd file:
Keep the old Styles.pbd Select this option to keep the old Styles.pbd file from the
previous installation.
Back up old and install new Styles.pbd Select this option if you are upgrading your
software version. Setup renames the existing Styles.pbd file to Stylesold(1).pbd,
where (1) is the running number of the old Styles.pbd file.
Overwrite the old Styles.pbd Select this option to replace the existing Styles.pbd file
with a new file.
The Styles.pbd file holds user-defined view style settings for the Browse window of
the Instrument Index module.
15. On the Setup Status page, view the progress of the file transfer.
16. When the file transfer is complete, on the Important Notes page, read the text carefully as it
contains important information for the current version, and then click Next.
17. On the Readme dialog box, click Yes if you want to view the Readme file.
We recommend that you choose to view the Readme file, as it contains important
information about SmartPlant Instrumentation. You can find this file, Readme.htm, in the
SmartPlant Instrumentation home folder or in the root folder of the installation media.
18. On the Setup Complete page, click Yes if you want to restart your computer (before you can
use the program you must restart your computer).
19. Click Finish to complete the setup and installation.
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in
the SmartPlant Instrumentation installation. This printer is used for PDF generation and
should not be removed or used for any other purpose. If you are unable to generate PDF files
because this driver is missing, restore the driver by running the executable file PDFInstall.exe,
which is installed by default in the software installation folder path
..\SmartPlant\Instrumentation\.
b. Accept the default path for Instance root directory or define another path.
c. Click Next.
10. On the Disk Space Requirements page, click Next.
If available disk space for the selected Instance root directory path is insufficient,
you will only be able to click Back and choose a different disk.
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.
12. On the Database Engine Configuration page, on the Account provisioning tab, under
Authentication Mode:
a. Select Mixed Mode.
b. Define the Built-in SQL Server System Administrator password as you desire in Enter
password.
c. Re-enter the same password in Confirm password.
d. Under Specify SQL Server administrators define at least one network user as system
administrator by clicking either Add Current User or Add and selecting an existing network
user.
e. Click Next.
13. On the Error and Usage Reporting page, click Next.
14. On the Installation Rules page, click Next.
15. On the Ready to Install page, review the list of components to be installed, then click Install.
16. On the Installation Progress page, once setup process is complete, click Next.
17. After clicking Close, restart the server machine.
1. Click Start > Programs > Microsoft SQL Server 2008/2012 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.
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.
5. Select the Database Settings page and change the value of Default index fill factor to 80.
You must enclose the name of your database within the quotes and parentheses as
shown.
Identical syntax applies for the CHECKDB command.
The software automatically corrects basic problems. For more complex problems, you
must refer to the query results and correct these problems manually.
GO
EXEC SP_UPDATESTATS
This script updates the statistics for every table in the database.
The systems described in the above figure can be physically located on the same computer or
on different computers which are connected in a local network. The installation process
consists of the following major steps:
1. Installing the SQL Server (you perform this step only if you have not installed the SQL Server
on your system yet).
2. Installing the SQL Server client (you perform this step only if you have not installed the
appropriate SQL Server client on your system yet).
3. Installing the required SmartPlant Instrumentation components.
4. Creating an initial SmartPlant Instrumentation database by (running the DB Setup Utility or
using Wizard name in SmartPlant Engineering Manager (refer to SmartPlant Engineering
Manager documentation for the database setup procedure).
5. Creating a new SmartPlant Instrumentation domain.
First, you install and configure the database server where SmartPlant Instrumentation will
store your data. Then you install the SQL Server client through which SmartPlant
Instrumentation interfaces with the SQL Server. If you have already installed SQL Server as
your database server, you may have to modify your database server settings to adapt SQL
Server to support the SmartPlant Instrumentation database.
After successfully installing the SQL Server and the SQL Server client, you install the selected
components and configure the appropriate configuration files. This way you will also be able
to use third-party applications such as CAD interfaces.
When Setup finishes installing the selected components, you need to configure SmartPlant
Instrumentation to connect and work with the SQL Server. At this stage, you create the
filegroups and database schema logon settings. For further information about filegroups and
database schema logon settings, see SmartPlant Instrumentation Database Setup for SQL
Server.
The final stage is to initialize a new SmartPlant Instrumentation domain in SQL Server and set
the initial parameters of the domain. This way you prepare the database for creating the
domain plant hierarchy and defining engineering data.
Ensure that you obtain the appropriate serial number for the desired type of SmartPlant
Instrumentation installation (standard installation or special server installation for use with
IDEAL).
The media for a multi-user version of SmartPlant Instrumentation only includes the runtime
version of Sybase Adaptive Server Anywhere, which cannot be used as a database engine
for SmartPlant Instrumentation. If you want to use SmartPlant Instrumentation in a
stand-alone mode with Sybase Adaptive Server Anywhere as a database engine, you must
obtain the media and a license (serial number) for SmartPlant Instrumentation Stand-Alone
for Sybase.
In this document, whenever a string appears in brackets, type the desired value
substituting the entire string, including the brackets. For example, instead of <SQL Server
home folder>, type c:\mssql
using and configuring concurrent licensing, refer to the SmartPlant License Manager Online
Help.
1. Insert the SmartPlant Instrumentation product media into the CD-ROM or DVD drive. If the
installation does not start automatically, double-click the Setup.exe file in the main folder.
2. Click SmartPlant Instrumentation Installation.
3. On the Welcome to the InstallShield Wizard for Intergraph SmartPlant Instrumentation
page, click Next.
4. On the Customer Information page, type your name, company name, and serial number,
and click Next.
If you are working with IDEAL, you must install SmartPlant Instrumentation Server,
which requires a special serial number. For installation details, see the SmartPlant
Instrumentation Server and IDEAL Installation and Configuration Guide.
The serial number is used for initial installation purposes only. A license key is
required to run SmartPlant Instrumentation. For more information, refer to the
SmartPlant License Manager Online Help.
9. On the Destination Folder page, specify the SmartPlant Instrumentation folder location and
click Next.
To choose an alternative destination, click Browse and navigate to the desired
destination folder, and then click Next.
10. For a custom installation, on the Select Features page, select the desired SmartPlant
Instrumentation components, and then click Next. To learn which components are required
to work with SmartPlant Instrumentation, see List of SmartPlant Instrumentation Components
(on page 27).
11. On the SQL Server Version page, select one of the following options (depending on your
database server version), then click Next:
SQL Server 2008 Client
SQL Server 2012 Client
16. On the Setup Status page, view the progress of the file transfer.
17. When the file transfer is complete, on the Important Notes page, read the text carefully as it
contains important information for the current version, and then click Next.
18. On the Readme dialog box, click Yes if you want to view the Readme file.
We recommend that you choose to view the Readme file, as it contains important
information about SmartPlant Instrumentation. You can find this file, Readme.htm, in the
SmartPlant Instrumentation home folder or in the root folder of the installation media.
19. On the Setup Complete page, click Yes if you want to restart your computer (before you can
use the program you must restart your computer).
20. Click Finish to complete the setup and installation.
After installing SmartPlant Instrumentation on a SQL Server platform, open the
Intools.ini file and under the [Database] section, ensure that the Lock parameter has one of the
following values:
Lock=RU (for a normal configuration)
Lock=RC (for an integrated environment)
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in
the SmartPlant Instrumentation installation. This printer is used for PDF generation and
should not be removed or used for any other purpose. If you are unable to generate PDF files
because this driver is missing, restore the driver by running the executable file PDFInstall.exe,
which is installed by default in the software installation folder path
..\SmartPlant\Instrumentation\.
9. When Setup detects an existing installation, it opens the Choose the Destination Folder
dialog box. Click Yes to install SmartPlant Instrumentation in the existing folder.
If you click No, the Destination Folder page opens. Click Browse and navigate to
another destination folder, and then click Next.
10. On the SmartPlant Instrumentation Configuration dialog box, do one of the following:
Click Yes to keep the existing Intools.ini file and preserve all the previous preferences
and configuration settings. If you choose this option, the software by-passes steps 12
- 14 below related to the input of data for the SQL Server database platform.
Click No if your existing Intools.ini file has been corrupted and you want to replace it
with a new default Intools.ini file.
If you click No, you lose all the previous preferences and configuration
settings.
11. On the Database Installation Options page, do one of the following to determine what to do
with your existing databases, such as In_demo.db (demonstration), Intools.db (empty), and
Intoolsef.db (for SmartPlant integration):
Keep old databases Select this option to use your existing databases from the
previous installation.
Back up old and install new databases Select this option to use new databases and
preserve the existing databases if you are upgrading your software version. Setup
renames the existing Intools.db to Intools(1).bk, In_demo.db to In_demo(1).bk, and
Intoolsef.db to Intoolsef(1).bk, where (1) is the running number for the old database.
Overwrite old databases Select this option to use new databases and delete the
existing databases.
If you overwrite your databases, you lose any user-defined data that you
have in these files.
12. On the Styles.pbd File Installation Options page, do one of the following to determine what
to do with your existing Styles.pbd file:
Keep the old Styles.pbd Select this option to keep the old Styles.pbd file from the
previous installation.
Back up old and install new Styles.pbd Select this option if you are upgrading your
software version. Setup renames the existing Styles.pbd file to Stylesold(1).pbd,
where (1) is the running number of the old Styles.pbd file.
Overwrite the old Styles.pbd Select this option to replace the existing Styles.pbd file
with a new file.
The Styles.pbd file holds user-defined view style settings for the Browse window of
the Instrument Index module.
13. On the SQL Server Version page, select one of the following options (depending on your
database server version), then click Next:
SQL Server 2008 Client
SQL Server 2012 Client
18. On the Setup Status page, view the progress of the file transfer.
19. When the file transfer is complete, on the Important Notes page, read the text carefully as it
contains important information for the current version, and then click Next.
20. On the Readme dialog box, click Yes if you want to view the Readme file.
We recommend that you choose to view the Readme file, as it contains important
information about SmartPlant Instrumentation. You can find this file, Readme.htm, in the
SmartPlant Instrumentation home folder or in the root folder of the installation media.
21. On the Setup Complete page, click Yes if you want to restart your computer (before you can
use the program you must restart your computer).
22. Click Finish to complete the setup and installation.
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in
the SmartPlant Instrumentation installation. This printer is used for PDF generation and
should not be removed or used for any other purpose. If you are unable to generate PDF files
because this driver is missing, restore the driver by running the executable file PDFInstall.exe,
which is installed by default in the software installation folder path
..\SmartPlant\Instrumentation\.
After installing SmartPlant Instrumentation 2013, the installation updates the Start
parameter in the Registry for the shipped profiles (In_templ, Intools, In_demo). If you
have any custom profiles, you must manually add the value -gp2048 to the Start parameter
under the Registry folder HK_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\Your_Profile,
for example:
<SmartPlant Instrumentation installation folder>\dbeng10.exe" -gp2048
The media for a multi-user version of SmartPlant Instrumentation only includes the runtime
version of Sybase Adaptive Server Anywhere, which cannot be used as a database engine
for SmartPlant Instrumentation. If you want to use SmartPlant Instrumentation in a
stand-alone mode with Sybase Adaptive Server Anywhere as a database engine, you must
obtain the media and a license (serial number) for SmartPlant Instrumentation Stand-Alone
for Sybase (the full engine is required when initializing a domain in Sybase Adaptive Server
Anywhere using another domain as a source).
We recommend reading the Readme.htm file, as it contains important information about
SmartPlant Instrumentation. You can find this file in your SmartPlant Instrumentation
home folder or in your installation media root folder.
If you are upgrading from an existing installation, make sure that all components of the
software are inactive before starting the Setup process.
If you are upgrading your current software version, it is recommended that you backup
your current database before you start the actual installation process. You can do this by
performing the backup procedure. If you have System Administrator database access
rights, you can also back up your database by selecting to save a copy of your existing
database during the setup procedure.
If you add any components to an existing installation, make sure that the version of the
components you install is the same as the version of the existing installation.
Before you start the installation process, make sure that your computer (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.
8. On the Destination Folder page, specify the SmartPlant Instrumentation folder location and
click Next.
To choose an alternative destination, click Browse and navigate to the desired
destination folder, and then click Next.
9. For a custom installation, on the Select Features page, select the desired SmartPlant
Instrumentation components, and then click Next. To learn which components are required
to work with SmartPlant Instrumentation, see List of SmartPlant Instrumentation Components
(on page 27).
10. On the Initial Database page, select the desired option for the initial database, and click
Next. The available options are:
Demo database Select this option to use a stand-alone demo database as your
default database.
Empty database Select this option to use a stand-alone empty database as your
default database.
11. On the Select Program Folder page, select the program folder where you want Setup to
install the program icons, and click Next.
12. On the Start Copying Files page, view the settings of the current Setup session, and then
click Next to start copying the files to your hard disk.
After you click Next, Setup immediately starts copying all the components you
selected to the SmartPlant Instrumentation home folder. To undo this operation you will
have to uninstall SmartPlant Instrumentation. Therefore, if you need to make any
modification to the current Setup selections, click Back before you start copying the files.
13. On the Setup Status page, view the progress of the file transfer.
14. When the file transfer is complete, on the Important Notes page, read the text carefully as it
contains important information for the current version, and then click Next.
15. On the Readme dialog box, click Yes if you want to view the Readme file.
We recommend that you choose to view the Readme file, as it contains important
information about SmartPlant Instrumentation. You can find this file, Readme.htm, in the
SmartPlant Instrumentation home folder or in the root folder of the installation CD-ROM.
16. On the Setup Complete page, click Yes if you want to restart your computer (before you can
use the program you must restart your computer).
17. Click Finish to complete the setup and installation.
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in
the SmartPlant Instrumentation installation. This printer is used for PDF generation and
should not be removed or used for any other purpose. If you are unable to generate PDF files
because this driver is missing, restore the driver by running the executable file PDFInstall.exe,
which is installed by default in the software installation folder path
..\SmartPlant\Instrumentation\.
8. When Setup detects an existing installation, it opens the Choose the Destination Folder
dialog box. Click Yes to install SmartPlant Instrumentation in the existing folder.
If you click No, the Destination Folder page opens. Click Browse and navigate to
another destination folder, and then click Next.
If you click No, you lose all the previous preferences and configuration
settings.
10. On the Initial Database page, select the desired option for the initial database, and click
Next. The available options are:
Demo database Select this option to use a stand-alone demo database as your
default database.
Empty database Select this option to use a stand-alone empty database as your
default database.
11. On the Database Installation Options page, do one of the following to determine what to do
with your existing databases, such as In_demo.db (demonstration), Intools.db (empty), and
Intoolsef.db (for SmartPlant integration):
Keep old databases Select this option to use your existing databases from the
previous installation.
Back up old and install new databases Select this option to use new databases and
preserve the existing databases if you are upgrading your software version. Setup
renames the existing Intools.db to Intools(1).bk, In_demo.db to In_demo(1).bk, and
Intoolsef.db to Intoolsef(1).bk, where (1) is the running number for the old database.
Overwrite old databases Select this option to use new databases and delete the
existing databases.
If you overwrite your databases, you lose any user-defined data that you
have in these files.
12. On the Styles.pbd File Installation Options page, do one of the following to determine what
to do with your existing Styles.pbd file:
Keep the old Styles.pbd Select this option to keep the old Styles.pbd file from the
previous installation.
Back up old and install new Styles.pbd Select this option if you are upgrading your
software version. Setup renames the existing Styles.pbd file to Stylesold(1).pbd,
where (1) is the running number of the old Styles.pbd file.
Overwrite the old Styles.pbd Select this option to replace the existing Styles.pbd file
with a new file.
The Styles.pbd file holds user-defined view style settings for the Browse window of
the Instrument Index module.
13. On the Select Program Folder page, select the program folder where you want Setup to
install the program icons, and click Next.
14. On the Start Copying Files page, view the settings of the current Setup session, and then
click Next to start copying the files to your hard disk.
After you click Next, Setup immediately starts copying all the components you
selected to the SmartPlant Instrumentation home folder. To undo this operation you will
have to uninstall SmartPlant Instrumentation. Therefore, if you need to make any
modification to the current Setup selections, click Back before you start copying the files.
15. On the Setup Status page, view the progress of the file transfer.
16. When the file transfer is complete, on the Important Notes page, read the text carefully as it
contains important information for the current version, and then click Next.
17. On the Readme dialog box, click Yes if you want to view the Readme file.
We recommend that you choose to view the Readme file, as it contains important
information about SmartPlant Instrumentation. You can find this file, Readme.htm, in the
SmartPlant Instrumentation home folder or in the root folder of the installation CD-ROM.
18. On the Setup Complete page, click Yes if you want to restart your computer (before you can
use the program you must restart your computer).
19. Click Finish to complete the setup and installation.
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in
the SmartPlant Instrumentation installation. This printer is used for PDF generation and
should not be removed or used for any other purpose. If you are unable to generate PDF files
because this driver is missing, restore the driver by running the executable file PDFInstall.exe,
which is installed by default in the software installation folder path
..\SmartPlant\Instrumentation\.
Be sure the <setup source folder path> specifies the path to the folder that
contains the setup.exe file that launches the SmartPlant Instrumentation InstallShield
Wizard, not the setup.exe file that launches the SmartPlant Instrumentation AutoPlay
executable. For example, on the SmartPlant Instrumentation media, the setup.exe file in
the SmartPlant Instrumentation folder is the file that launches the InstallShield
Wizard. Double quotes are required only if the path to the setup.exe file contains spaces.
The /r parameter tells the setup to automatically generate the silent setup file
(<filename>.iss), and to record all setup input.
The /f1"<path>\<filename>.iss" parameter specifies the path and filename for the
silent setup file. The double quotes are required around this path, with no space
between the /f1 and the opening double quotes. For example, if you type the
following command string, the software places the resulting .iss file in the c:\installfiles
folder \\sourceserver\instrumentation\setup.exe /r /f1"c:\installfiles\silentsetup.iss".
3. Work through the standard software installation on your database platform. For details, refer
to the appropriate procedure in the SmartPlant Instrumentation Installation and Upgrade
Guide.
When you click Display on the License Agreement dialog box while running setup in
record mode, the following message appears.
Click OK to acknowledge that you are accepting the license agreement for all users on
whose computers you will install the product. Setup then returns you to the normal
installation process by displaying the license agreement and enabling the Yes button
on the License Agreement dialog box.
4. At each workstation on which you want to install the software, open a Command Prompt
window and type:
Be sure to use the same setup executable that you used in step 2 above.
The environment of the machine on which you run the normal setup to create the .iss
file and the environment of the workstations on which you perform the silent mode
installation must be identical; that is, they must have the same operating system,
database platforms, software versions, installed files, drive partitions, and so forth.
The /s parameter tells the setup to run in silent mode using the indicated .iss file.
The /f1"<path>\<filename>.iss" parameter specifies the path and the filename for the
silent setup (.iss) file you want to run. The double quotes are required, with no space
between the /f1 and the opening double quotes. For example,
/f1"c:\installfiles\silentsetup.iss".
(Optional) Use the /f2"<path>\<filename>.log" parameter to record a log file of the
setup process. The double quotes are required, with no space between the /f2 and
the opening double quotes. For example, /f2"c:\installfiles\silentsetup.log". If /f2 is
not defined, a log file is created in the same location as the .iss file.
5. Check the .log file to ensure that the installation proceeded without errors. A successful silent
installation produces a .log file looking something like this:
[InstallShield Silent]
Version=v7.00
File=Log File
[ResponseResult]
ResultCode=0
[Application]
Name=SmartPlant Instrumentation
Version=2013 (xx.xx.xx.xx)
Company=Intergraph
Lang=0009
In general, if an error occurred, the ResultCode will be a number less than zero.
Possible result codes include the following:
Any value greater than 0 = Success.
-1 General error
-2 Invalid mode
-3 Required data not found in the
Setup.iss file
-4 Not enough memory available
-5 File does not exist
-6 Cannot write to the response file
-7 Unable to write to the log file
-8 Invalid path to the InstallShield
Silent response file
-9 Not a valid list type (string or
number)
-10 Data type is invalid
-11 Unknown error during setup
-12 Dialog boxes are out of order
-51 Cannot create the specified folder
-52 Cannot access the specified file or
folder
-53 Invalid option selected
6. Restart the computer.
This procedure also applies to the uninstall operation. The uninstall procedure should
use the same command and procedures as for the installation, both for the record mode and
for each workstation mode; however, you should specify a different name for the .iss file so as
not to overwrite the file used for the installation.
When you access the SmartPlant Instrumentation application via Citrix, we strongly
recommend that you do not perform any administration activities that run automatically
for a long time on a client machine. When you execute administration activities via Citrix
client, the software actually performs these activities on the server side, while the client
remains idle, and the connection to Citrix is lost, possibly resulting in corruption of
data. Examples of these types of administration activities are: initializing or upgrading a
domain, claiming items, or rebuilding stored procedures and triggers.
As a workaround, we recommend that you perform these kinds of activities either on your
database server machine or on a client machine using a configuration other than Citrix.
When using thin client mode, all users share a common database, resulting in intellectual
property being shared between all sites.
When starting SmartPlant Instrumentation, the software looks for the Intools.ini file in the
system path. This path is defined in the Path system variable.
To enable SmartPlant Instrumentation to work in thin client mode for multiple users, you
must load a separate Intools.ini file for each user who logs on to Citrix and delete the
Intools.ini file installed on the server. Also, when working with SmartPlant, IDEAL, the
SmartPlant Electrical Interface or DCS Vendor Interfaces, you must modify the registry path
key for each user, as described later.
6. On the Specify Application Appearance page, specify the window size, color, and start-up
settings according to your needs, and then click Next.
7. On the Specify ICA Client Requirement page, accept the default value, and then click Next.
8. On the Specify Servers page, add the Citrix server and then click Next.
9. On the Specify Users page, add the user accounts that are to be granted access to the
published application and then click Finish.
10. After publishing the application, do the following to create the .ica and .html files:
a. On the Citrix Management Console, select the SmartPlant Instrumentation application,
right-click, then click Create ICA File and follow the wizard instructions.
b. On the Citrix Management Console, select the SmartPlant Instrumentation application,
right-click, then click Create HTML File and follow the wizard instructions.
To prevent performance problems that may be caused if the software maps drive U: to
a server that is very remote from the Citrix server, ensure that the U: drive is on or
local to the Citrix server and that the 'TS Roaming Profiles' option is enabled.
Make sure that the common folder path contains the Intools.ini file. You can also use
this folder for temporary files.
2. Modify the system path statement on the server to include the common folder path in the
system path.
3. Modify the following application paths in the Windows Registry:
a. Select the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\Intools\<BaseVersion>, where
<BaseVersion> is the version number of the main release of the installed software.
b. Under this key, assign the folder path where SmartPlant Instrumentation is loaded on the
Citrix server, as shown in the example.
c. If you have installed a service pack version, select the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\Intools\<CurrentVersion>, where
<CurrentVersion> is the version number of the installed service pack.
d. Under this key, assign the common folder path as the value of the Path property, as shown in
the example.
4. In the path C:\Winnt\Application Compatibility Scripts, open the file Rootdrv2.cmd and set
the following parameter: Set RootDrive=U.
5. If you have not already done so, rename the Intools.ini file located in the server installation
home folder; for example, to Intools.ini.orig.
6. To ensure that each individual user has a separate folder for storing the temporary files, in the
Intools.ini file, do the following:
a. In the [Loop] section, change the Pathtemp parameter from the path on the server's
shared installation folder to U:\SmartPlant\Instrumentation (or specify some other
location if desired).
b. In the [Project] section, change the Logopath parameter from the path on the server's shared
installation folder to U:\SmartPlant\Instrumentation (or specify some other location if
desired).
c. In the [API] section, change the Apitemp parameter from the path on the server's shared
installation folder to U:\SmartPlant\Instrumentation (or specify some other location if
desired).
d. Copy the Intools.ini.orig file from the installation folder to each individual user drive in the
U:\SmartPlant\Instrumentation folder path, and rename the Intools.ini.orig file to Intools.ini.
This action ensures that each individual user has a separate folder for making
individual settings in the Intools.ini file. If desired, you can use a script file to
automate this step each time a new user logs on to Citrix.
(Merge.exe), and so forth. This includes the Enhanced Report Utility, Smartloop.exe (located
in the path <SmartPlant Instrumentation home folder>\RAD\) because XenApp also treats it as
a separate application. Publishing the Enhanced Report Utility allows you to use the Explorer
windows from the utility via Citrix.
1. Open the Citrix Delivery Services Console.
2. Under your farm, click Applications.
5. On the Name page, enter values for Display name and Application description, and then
click Next.
d. Click Next.
7. On the Location page, under Command line, click Browse and navigate to the executable
(.exe) file for the application being published, and then click Next.
f. Click Next.
9. On the Users page, add a domain user account that is to be granted access to the published
application as follows:
a. Click Add.
b. On the Select Users or Groups dialog box, click Add List of Names.
c. Enter names using the format user@domain.
g. Click OK on the Select Users or Groups dialog box to return to the wizard Users page.
h. Click Next.
10. On the Shortcut presentation page, do the following:
a. Click Change Icon to change the application icon if necessary.
c. Click Next.
12. Repeat the above steps for each application you want to publish.
The following graphic displays what SmartPlant Instrumentation publishes and retrieves and
shows the flow of data and the different types of data.
Use a hierarchy that contains a minimum of three levels when you create your plant in the
SmartPlant Instrumentation Administration module.
SmartPlant integration requires that the names of hierarchy items cannot be changed after
being created and that you cannot modify the hierarchy structure after you create the
project.
If you have installed Schema Component previously, the software prompts you to
remove the older version of the Schema Component before installing the new
version. After you uninstall the older version, click Schema Component Installation
again.
The installation process checks whether Microsoft Excel is installed on the server. If
Excel is not installed, the Schema Component installation will display a message box
stating that Excel is required. Click OK to dismiss the message box and continue the
Schema Component installation.
5. On the Select Optional Features page, leave the Schema Editor check box selected (the
default state), and then click Next.
The Schema Editor allows you to view and edit the SmartPlant schema, tool map
schemas, and authoring tool mapping.
If installing from the SmartPlant Foundation media, click SmartPlant Software in the
SmartPlant Foundation Installation window.
If installing from the SmartPlant Instrumentation media, click Add-In Software in the
SmartPlant Instrumentation Installation window.
your custom title blocks in native SmartPlant Instrumentation format and the conversion of
reports to .pdf files. For more information, see Install the Update Title Block Component for
SmartPlant Instrumentation (on page 122).
For the .brw, .ssf, and .spd file types, SmartPlant Foundation uses the component address
(ProgID): SPITitleBlock.TitleBlockInfo
These file types are already configured in the delivered database dump files.
PowerSoft Reports
The title block files for the reports in .psr format are in the location <SmartPlant
Instrumentation installation folder>\PSR\ and the available files are as follows:
A3tall_inchunit.psr
A3tall_pbunit.psr
A3wideborder_inchunit.psr
A3wideborder_pbunit.psr
A4tall_inch.psr
A4tall_pbunit.psr
A4tall_pbunit_general.psr
A4widerborder_inchunit.psr
A4widerborder_pbunit.psr
If you are creating your own custom reports in .psr format in which you want to include issue
data, you must create a custom title block and add macros as shown in the following table.
REV issuedrevision_x
SITE sitename
DIVISION divisionname
For the macro names, 'x' represents an integer used to specify the sequence, for example,
issueno_1, issueno_2, and so forth.
Enhanced Reports
The title blocks that use the .sma format are designed to be used by all the tools that
communicate in an integrated environment; however, if you use them in SmartPlant
Instrumentation as delivered, parts of the drawing may overlap the margins of the drawing
area. For this reason, you need to set values of the working area margins for any templates
that you intend to use for generating reports in an integrated environment. To prepare the
templates, you define the settings under Preferences > Enhanced Reports (for all layouts of a
particular report type) or for a specific layout as desired.
The template files are installed on the SmartPlant Instrumentation machine. The default
location for enhanced report templates for the reports used in an integrated environment is:
<SmartPlant Instrumentation installation folder>\RAD\Template\Generic\*.sma
The title block files are installed on the SmartPlant Instrumentation machine. The default
location for enhanced report title blocks for the reports used in an integrated environment is:
<SmartPlant Instrumentation installation folder>\RAD\Template\Generic\TitleBlocks\*.sym
The following settings represent the minimum values required for the working area margins:
B Tall 0 0 0.3 0
A3 Tall 0 0 0.3 0
A Wide 0 0 0.3 0
A3 Wide 0 0 0.3 0
A4 Wide 0 0 0.4 0
To place issue data on other title blocks for enhanced reports, use the SmartPlant
Instrumentation Place Drawing Property Label command in the Enhanced Report Utility. For
more information, see Enhanced Report Utility User's Guide > Working with Templates and
Title Blocks > Place Property Labels on a Drawing Sheet.
4. Click Next.
5. To accept the default installation location for the SmartPlant Instrumentation Title Block
component, click Next.
If you want to change the installation location, click Browse and navigate to the new
folder. Then, click Next.
6. Click Finish.
If you are working on a 64-bit computer, to enable PDF generation, create a new local
printer port with a custom name and then assign the PDF printer (SmartPlant PDF
Converter) to the port. For details, see Create a New Local Printer Port (64-bit server only)
(on page 123).
The driver used for printing the PDF files, SmartPlant PDF Converter 4.51, is included in the
SmartPlant Instrumentation installation.
Hardware Recommendations
2.4 GHz Pentium machine (for Oracle), 2 GHz or higher Xeon machine (for SQL Server)
2 GB RAM
Digital tape or DVD backup system for server
One CD-ROM drive
or
An accessible network CD-ROM drive
A hard drive with 100 MB free disk space for installation and creating files
5. After reading the license agreement, close Adobe Reader, and on the License Agreement
page, click Yes.
6. On the Choose Destination Location page, specify the folder location where you want to
install the software, and click Next.
It is recommended that you install External Editor in a folder other than the SmartPlant
Instrumentation home folder, for example: C:\Program Files. This folder must have
read / write access for users who are going to work with External Editor.
To choose an alternative destination, click Browse to navigate to the desired
destination folder, and then click Next.
7. On the Select Components page, select the components that you want to install. The
available components are:
External Editor Select this option to install the main External Editor software.
Shared DLL (Deployment Kit) This component is required if you have not installed
SmartPlant Instrumentation on your computer, or if you are installing External Editor in
8. On the Select Program Folder page, select the program folder where you want the software
to install the program icons, and then click Next to begin the setup.
9. On the Setup Complete page, click Finish to exit the setup.
to use the old In_demo.db and Intools.db files, you must backup these files before repairing
the installed components.
1. Insert the SmartPlant Instrumentation product media into the CD-ROM or DVD drive. If the
installation does not start automatically, double-click the Setup.exe file in the main folder.
2. Click SmartPlant Instrumentation Installation.
3. On the Welcome page, click Repair.
4. Click Next to overwrite all the existing software components with new components.
You are prompted whether to replace the existing databases. Click No if you want to
back up the existing databases.
In this guide, whenever a string appears in brackets, type the desired value substituting the
entire string, including the brackets. For example: instead of <Oracle home folder>, type
c:\orawin.
If you encounter problems during the upgrade process, contact your local SmartPlant
Instrumentation provider or Intergraph Support. To locate your Intergraph Support
service provider, use a World Wide Web browser to connect to
http://support.intergraph.com (http://support.intergraph.com/).
See Also
Prerequisites for Upgrading to Version 20 (see "Prerequisites for Upgrading to Version 2013" on
Database Upgrade (on page 136)
Post-Upgrade Tasks (on page 140)
General Prerequisites
General prerequisites deal with freeing disk space and performing a database check. Also, you
need to make sure that your source version of SmartPlant Instrumentation and the database
platform where SmartPlant Instrumentation resides allow you to complete the upgrade
procedure for Version 2013.
If the datafiles in a filegroup are not set to automatically grow files, and the total datafile
free space is less than half the total datafile used space, you must either resize the
filegroup using your SQL Server tools or add more datafiles for the filegroup using the
Administration module option Add Datafiles on the DBA menu of the System
Administration window.
If the datafiles in a filegroup are set to automatically grow files but the total free space on
the disk where the filegroup is located is less than half the total datafile used space, you
must create additional datafiles for this filegroup on another disk.
Specific Prerequisites
Specific prerequisites deal with various features and functionalities of SmartPlant
Instrumentation that are used according to specific engineering needs.
Upgrading on Oracle
SmartPlant Instrumentation 2013supports Oracle 11g; therefore if you have an earlier version
of Oracle, you must upgrade that version to Oracle 11g.
As a prerequisite for upgrading to Oracle 11g, you must already have an installation of
Oracle 10g.
Every sub-contractor must use SmartPlant Instrumentation in the national environment of
your Oracle client to ensure that units of measure are displayed correctly in the upgraded
version of SmartPlant Instrumentation. For more information, contact Intergraph
Customer Support.
See Also
Database Upgrade (on page 136)
2. On the client machine where SmartPlant Instrumentation is installed, uninstall the existing
version and then install Version 2013.
3. After installing Oracle Client 11g and SmartPlant 2013, use the Smart Upgrade (Admin) to
update your database to Oracle 011g.
4. Create a new instance in Oracle Server 11g. For more information, see Create a New Oracle
Instance (on page 39).
5. Run DBSetup.
6. Initialize a new domain using the upgraded database as your source
7. If you upgraded from a non-Unicode database, create a new Oracle Unicode instance and
initialize domains from the upgraded database to this new instance.
I Some scenarios require that you initialize new domains using the upgraded domains as
a source. You need to familiarize yourself with the domain initialization prerequisites and
procedures pertinent to your database platform. For details, see the Administration User's
Guide, Domain Initialization, Backup and Deletion, Domain Initialization.
In scenarios that involve domain initialization using another domain as a source, you
lose the source audit trail data. Therefore, before implementing such a scenario, we
recommend that you back up the existing audit trail data. For details, see the Administration
User's Guide, Domain Initialization, Backup and Deletion, Backing up Files Containing Audit Trail
Data.
4. After installing Version 2013, make sure that the INTOOLS.INI file still points to the original
database.
If you have any custom views in your database, you must remove them by
running the following SQL on the source database:
You will need to re-create the custom views again after the upgrade is complete.
Database Upgrade
The software automatically prompts you to upgrade your database when you try to log on to
SmartPlant Instrumentation after installing a new version, allowing you to select which domain
schemas you wish to upgrade.
If you do not upgrade all domains at this stage, you can later manually upgrade
individual domains one by one. For additional information see Upgrade Domain Schemas.
An upgrade to Version 2013 must be followed by:
1. Rebuilding stored procedures and triggers for all domains.
2. Rebuilding projects in As-Built domains.
You must upgrade all the domains in which you want to work in this SmartPlant
Instrumentation version. The time needed for upgrade depends on the database size. For a
large database, the upgrade process can take several hours.
Alternatively, you can upgrade several or all of your schemas (including admin schema) using
batch upgrade (See Batch Upgrade (on page 139)).
.
The log file contains the upgrade process information of your current or previous
upgrade session per domain.
The default log file directory is your user's Temp folder. To locate this folder, click the
Windows Start > Run > %temp%.
1. Select the desired schemas to upgrade by selecting the check box next to each, or select the
Select all check box if you want to upgrade all the schemas.
2. Click the Upgrade icon at the bottom to start upgrading all selected domains.
Once the upgrade process begins, each schema's status will update, according to the following:
Requires upgrade schema not selected for upgrade.
Pending schema selected for upgrade.
In progress the schema currently being upgraded.
Progress indicators below the schema grid show the current state and phase of each schema's
upgrade and the overall progress of the upgrade process.
Once upgrade is complete, each upgraded schema may have one of the following statuses:
Upgraded schema successfully upgraded.
Upgraded with errors schema upgraded, with errors
Upgrade failed schema not upgraded.
On completion of the domain upgrade process, the software records the upgrade
session information in a domain-specific log file, in the specified log file location.
3. In the SmartPlant Instrumentation Schema Upgrade window which opens, you can click
the Select log directory icon to specify the directory to which to save log files.
The default log file directory is your user's Temp folder. To locate this folder, click the
Windows Start > Run > %temp%\SpiUpgradeLog.
4. Select the desired schemas to upgrade by selecting the check box beside each schema, or
select the Select all check box.
Domain schemas which do not require upgrading are grayed-out and cannot be
selected.
5. Click the Upgrade icon at the bottom to start upgrading all selected domains.
6. Once the upgrade process begins, each schema's status will update (for additional
information, see Upgrade the Database).
On completion of the domain upgrade process, the software records the upgrade
session information in a domain-specific log file, in the defined log file location.
7. After upgrading, open SmartPlant Instrumentation and implement the Post-Upgrade Tasks
(on page 140) listed in the current guide.
8. Familiarize yourself with special instructions listed in Schem SPI Special Instructions.pdf
file, which resides in the SmartPlant Instrumentation home folder, and implement the
instructions for the features you consider relevant.
Upgrade of an owner operator domain can take significant time (several hours). You
must allow the software complete the upgrade process once started.
Batch Upgrade
In batch upgrade you can create a .bat file that updates all the desired domains, using the
Administration module mechanism.
To create a batch upgrade file:
1. In Notepad, create a batch file (e.g., BatchUpgrade.bat).
2. Enter a line for each domain you wish to upgrade (starting with a line for the admin schema),
as shown in the example below:
Upgrade 9999 //upgrade admin schema
For a complete list of domain project IDs, run the following SQL Query: SELECT *
FROM Project.
3. Double-click the batch file to run it and upgrade the defined domains.
If you added the -silent flag to the file, no dialog boxes or messages are shown.
You can schedule the batch file to run at a convenient time using Windows scheduler
(for example, during the night or over the weekend).
Post-Upgrade Tasks
There are various post-upgrade tasks you need to complete to be able to work with SmartPlant
Instrumentation. Some tasks are general tasks you must perform regardless of the data your
database contains or features of SmartPlant Instrumentation that you used before the
upgrade. For example, you must perform a thorough database check after upgrading. Other
tasks are related to specific options of the software. You do not have to complete a task if it
deals with features you never used before upgrading.
See Also
Upgrading SmartPlant Instrumentation (on page 131)
Update Link Definitions for Importing Data into the PANEL Table
If you use the Import Utility to import data to SmartPlant Instrumentation, you must update
the link definitions you use to import data into the PANEL table. When importing data into the
PANEL table, you must make link definitions for both the panel_category_id and
panel_sub_category fields. If you make a link definition for either one of these fields only, the
import does not work correctly.
See Also
Perform a Database Check and Make Domain Backups (on page 132)
You can only rebuild the default views supplied with the SmartPlant Instrumentation
database. You cannot rebuild any user-defined views.
Make sure that all users have logged out of the database before starting this procedure.
1. With the System Administration window open, click DBA > Rebuild Default Views in
Domains.
2. From the Domain list, select the domain whose database views you want to rebuild.
3. In the View-Only Domain schema password box, enter the logon password of the
View-Only Domain schema. The password characters appear masked.
You can change the password only once, when initializing a new domain. If you did
not change the password when initializing the selected domain, enter the default logon
password, which is <Domain schema logon name>_VIEW.
4. If working on SQL Server, type the SQL Server System Administrators password.
5. Click OK to start rebuilding the views of the selected domain.
Optimize Indexes
If you upgraded an Oracle or Microsoft SQL database, you must optimize your indexes before
continuing.
1. Log on to the SmartPlant Instrumentation Administration application as a System
Administrator.
B networking components 35
bi-lingual projects 15 system requirements 19
C datafiles 132
character set 39
date format 15
Oracle 10g database server 39
DBMS_PIPE 134
components 129
decimal point 15
modifying 129
Domain schema upgrade 138
repairing 129
E
connection 48, 79 error records 137
to Oracle database server 48
F
to SQL Server database server 79 filegroups 132
D Oracle installation 53
database 15, 35, 59 SQL Server installation 73
database maintenance 63 stand-alone installation 89
heterogeneous environment 15 K
keyboard locale 15
homogeneous environment 15
L
I
locale boundary 15
installation 51, 53, 54, 70, 73, 74, 82, 86,
89 log files 137
new Sybase Adaptive Server Anywhere SQL Server 2005 61, 63, 64
installation 82
client installation 64
Oracle installation flowchart 53
configuring 61
Oracle update installation 54
database maintenance 63
removing 130
DBCC Utility options 63
freeing disk space before upgrading installing Update Title Block Component
132 122
V
versions 134
views 141
W
workshare 95
workstation computers 22