SPP Id Install Guide
SPP Id Install Guide
March 2015
DPID2-PE-200014Q
Copyright
Copyright © 1999-2015 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.
Documentation
Documentation shall mean, whether in electronic or printed form, User's Guides, Installation Guides, Reference Guides,
Administrator's Guides, Customization Guides, Programmer's Guides, Configuration Guides and Help Guides delivered with a
particular software product.
Other Documentation
Other Documentation shall mean, whether in electronic or printed form and delivered with software or on Intergraph Smart Support,
SharePoint, or box.net, any documentation related to work processes, workflows, and best practices that is provided by Intergraph
as guidance for using a software product.
Terms of Use
a. Use of a software product and Documentation is subject to the End User License Agreement ("EULA") delivered with the
software product unless the Licensee has a valid signed license for this software product with Intergraph Corporation. If the
Licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take
precedence and govern the use of this software product and Documentation. Subject to the terms contained within the
applicable license agreement, Intergraph Corporation gives Licensee permission to print a reasonable number of copies of the
Documentation as defined in the applicable license agreement and delivered with the software product for Licensee's internal,
non-commercial use. The Documentation may not be printed for resale or redistribution.
b. For use of Documentation or Other Documentation where end user does not receive a EULA or does not have a valid license
agreement with Intergraph, Intergraph grants the Licensee a non-exclusive license to use the Documentation or Other
Documentation for Licensee’s internal non-commercial use. Intergraph Corporation gives Licensee permission to print a
reasonable number of copies of Other Documentation for Licensee’s internal, non-commercial. The Other Documentation may
not be printed for resale or redistribution. This license contained in this subsection b) may be terminated at any time and for any
reason by Intergraph Corporation by giving written notice to Licensee.
Disclaimer of Warranties
Except for any express warranties as may be stated in the EULA or separate license or separate terms and conditions, Intergraph
Corporation disclaims any and all express or implied warranties including, but not limited to the implied warranties of merchantability
and fitness for a particular purpose and nothing stated in, or implied by, this document or its contents shall be considered or deemed
a modification or amendment of such disclaimer. Intergraph believes the information in this publication is accurate as of its
publication date.
The information and the software discussed in this document are subject to change without notice and are subject to applicable
technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document.
The software, Documentation and Other Documentation discussed in this document are furnished under a license and may be used
or copied only in accordance with the terms of this license. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL
EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT.
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.
Export Controls
Intergraph Corporation’s software products and any third-party Software Products obtained from Intergraph Corporation, its
subsidiaries, or distributors (including any Documentation, Other Documentation or technical data related to these products) are
subject to the export control laws and regulations of the United States. Diversion contrary to U.S. law is prohibited. These Software
Products, and the direct product thereof, must not be exported or re-exported, directly or indirectly (including via remote access)
under the following circumstances:
a. To Cuba, Iran, North Korea, Sudan, or Syria, or any national of these countries.
b. To any person or entity listed on any U.S. government denial list, including but not limited to, the U.S. Department of Commerce
Denied Persons, Entities, and Unverified Lists, http://www.bis.doc.gov/complianceandenforcement/liststocheck.htm, the U.S.
Department of Treasury Specially Designated Nationals List, http://www.treas.gov/offices/enforcement/ofac/, and the U.S.
Department of State Debarred List, http://www.pmddtc.state.gov/compliance/debar.html.
c. To any entity when Licensee knows, or has reason to know, the end use of the Software Product is related to the design,
development, production, or use of missiles, chemical, biological, or nuclear weapons, or other un-safeguarded or sensitive
nuclear uses.
d. To any entity when Licensee knows, or has reason to know, that an illegal reshipment will take place.
Any questions regarding export or re-export of these Software Products should be addressed to Intergraph Corporation’s Export
Compliance Department, Huntsville, Alabama 35894, USA.
Trademarks
Intergraph, the Intergraph logo, Intergraph Smart, PDS, SmartPlant, SmartMarine, FrameWorks, I-Sketch, IntelliShip, ISOGEN,
Sapphire, 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.
Internationalization .............................................................................................................9
Index ................................................................................................................................. 87
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.xlsx. The checklist is located in the same folder as this installation guide.
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 operating system platforms, SmartPlant P&ID does not require a traditional, expensive
CAD engine for the creation of P&IDs. 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.
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 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
Microsoft .Net Framework 4.0 (installed with SmartPlant P&ID) must be installed before
installing Oracle 11g 32-bit Client.
The client database software must be of the same version as the server database software.
Oracle 32-bit Client is required for both 32-bit and 64-bit Oracle databases.
Do not use Oracle 'light client' as it does not include some of the required .dll files.
For SQL Server, no client installation is required.
Software Prerequisites
Microsoft .Net Framework 4.0 and 4.5
SmartPlant License Manager (SPLM) 2010 Client (11.00) or 2012 Client (12.00). The
licensing is delivered on its own CD that comes with your SmartPlant P&ID product DVD.
Microsoft Internet Explorer 9, 10, or 11, 64-bit (required for viewing the Readme file, the
report generated from Rule Manager, and the Online documentation delivered with the
software)
Microsoft XML Core Services (MSXML) 6.0 Service Pack 1 or 6.0 Service Pack 3
Optional Software
Apart from SmartSketch, SmartPlant Engineering Manager, and Intergraph Smart 3D
SP3DPIDClient, the following software programs are not Intergraph corporation software and
are owned by third parties. It is the responsibility of the customer to select at 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 2014 R1
PDF reader (for viewing the printable guides and for displaying the license agreement when
installing Intergraph Smart 3D SP3DPIDClient)
Microsoft Excel from Office 2007 Service Pack 2, with Hot Fix package, Office 2010 Service
Pack 1 or 2 (32-bit only), or Office 2013 Service Pack 1 (32-bit only). (Microsoft Excel is
required for working with report templates, importing and generating reports, importing from
SmartSketch, saving drawings as MicroStation or AutoCAD, and for viewing the Installation
Checklist and various other files.)
Intergraph Smart 3D SP3DPIDClient 2014 R1 (10.01.15.0060) for use with Smart 3D 2014
or 2014 R1. This 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
DVD.
For working in a thin client environment, Citrix XenApp 6.5 or Citrix XenDesktop 7.0 RDS on
Windows Server 2008 R2 Service Pack 1, 64-bit (Standard or Enterprise)
One of the following drawing software programs (for compatibility with the 'Save As' feature):
SmartSketch 2014 or 2014 R1
Autodesk AutoCAD 2012
Bentley MicroStation V8
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 in its own instance is that only the affected
application will be off-line during backup, performance tuning, and other database maintenance
activities. Additionally, global tuning parameters that apply to one instance can be tailored to the
specific product requirements.
According to Oracle documentation, the only limit to the number of instances you can have on
any machine is the availability of resources. However, the number of instances on one database
server should be minimized, because each additional instance places 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.
Prerequisites
Make sure that a compatible Oracle server version is installed.
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.
For the current version of SmartPlant P&ID, Microsoft .Net Framework 4.0 must be installed
before installing Oracle client. If Oracle client was installed before .Net Framework, you may
see the following message when opening Drawing Manager:
SmartPlant License Manager software is required for concurrent licensing for both the core
SmartPlant P&ID product and for each feature, therefore you must install and configure
SmartPlant License Manager on your workstation before installing SmartPlant P&ID. This
licensing software is delivered on its own media. For more information about using and
configuring concurrent licensing, refer to the SmartPlant License Manager Online Help.
If you previously uninstalled a SmartPlant P&ID 2009 SPx Hot Fix, before installing the
current version of SmartPlant P&ID, you must first run the CleanUp Utility. To download and
run this utility, go to the URL for Intergraph Smart Support
(http://smartsupport.intergraph.com), then under Find the answer to your question type
20488 and follow the instructions.
1. Insert the SmartPlant P&ID DVD into the drive. If the installation does not start
automatically, double-click setup.exe in the main folder.
2. On the Welcome page, click the Additional Software link if you want to perform any of the
following installations:
Install SmartPlant P&ID Reference Data (on page 33)
Install Intergraph Smart 3D SP3DPIDClient (on page 23)
Install SmartPlant Engineering Manager (for details, see SmartPlant Engineering
Manager Installation and Upgrade Guide)
After installing additional software and closing the setup, to continue with the
installation of SmartPlant P&ID, on the Additional Software page, click Back.
3. To install SmartPlant P&ID, click Start Setup.
4. On the Details and Features page, enter your user name and company details.
By default, the user name and company name are obtained from the Registry. You may
change the values, but you may not leave these fields blank.
For an evaluation copy of the software, these fields are mandatory.
5. Enter your product serial number.
6. Under Select Installation Mode, choose whether to install SmartPlant P&ID or SmartPlant
P&ID Engineering.
7. Under Select Features to Install, select any additional features that you want to install.
Drawing Manager is always installed, together with SmartPlant P&ID or SmartPlant
P&ID Engineering, regardless of any other features you select.
8. In the Install Path field, accept the default installation path or if desired, specify a different
path, and then click Next.
9. On the License Agreement page, select your country or region from the list to view the
license agreement in your language and then select the I agree to the license agreement
and conditions check box.
10. Click Install.
11. On completion of the installation, if you want to open the Readme file, select View Readme.
12. Click Finish to close the installation wizard.
If you try to install SmartPlant P&ID software when you do not have write permissions to the
registry on the computer on which you are installing, a warning message appears. For
details of what to do if you see this message, see Grant Permissions to Write to a Registry
Key (on page 24).
The driver used for printing the PDF files, SmartPlant PDF Converter (Amyuni 4.5), is
included in the SmartPlant P&ID 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
InstallPDFConverter.exe, which is installed by default in the software installation folder path
..\SmartPlant\P&ID Workstation\bin.
Because SmartPlant P&ID installation requires SmartPlant License Manager for concurrent
licensing, you must first install the SmartPlant License Manager software on your
workstation and on every other workstation where you are going to install SmartPlant P&ID
in silent mode. For more information about installing and configuring SmartPlant License
Manager, see the SmartPlant License Manager Online Help.
You must ensure that there is sufficient disk space on each workstation for the installation.
Prior to creating a silent setup of SmartPlant P&ID over a network, ensure that the following
conditions exist:
For a new release, all previous existing versions of SmartPlant P&ID on the target
machine have been uninstalled prior to network installation.
The target machine does not have a directory by the same name to which SmartPlant
P&ID is to be installed.
The target machine meets the free disk space recommendations specified in SmartPlant
P&ID Workstation (on page 14).
All applications are closed.
Ensure that the command line includes spaces where shown before and after
arguments.
Double quotes are required only if the path to the setup.exe file contains spaces.
Argument values are case sensitive.
Mandatory arguments are validated by the setup procedure. If an argument or option is
missing, the setup stops and a log is produced with the name of the missing argument.
USERNAME Sets the user name See 'Notes' This argument is mandatory for
an Evaluation Mode installation
COMPANYNAME Sets the company name See 'Notes' This argument is mandatory for
an Evaluation Mode installation
ADDLOCAL The value of the No For use with the /install and
ADDLOCAL argument is a /modify arguments.
list of features that are to
Accepted values:
be installed locally. If the
ADDLOCAL argument is ALL — installs all available
not present in the features
command line, the
software installs features Specified list of features
according to the default delimited by commas. The
features must be present in
settings (for details, see
the Feature column of the
the Notes below).
Feature table. The features
available for this product are
listed in the Notes below.
REMOVE The value of the REMOVE No For use with the /modify
argument is a list of argument.
features that are to be
Accepted values:
removed or excluded when
modifying an installation. ALL — removes or excludes
from the installation all
features, including the main
application
Specified list of features
delimited by commas. The
features must be present in
the Feature column of the
Feature table. The features
available for this product are
listed in the Notes below.
Command line arguments and their values are case-sensitive; therefore you must ensure
that they are typed exactly as shown in the above table.
Each command line argument must be preceded by a '-' or '/' delimiter, for example: -
install - silent or /install / silent
If none of the arguments: install, uninstall, repair, or update is specified, install is
assumed as the default.
Drawing Manager and either SmartPlant P&ID or SmartPlant P&ID Engineering are always
installed. You can use the following ADDLOCAL / REMOVE arguments (case-sensitive) for
installing or removing specific features:
These examples show the use of either '/' or '-' as argument delimiters.
The 'Pause' command is optional and is used to display completion of the process in the
Command Prompt window.
A value of '%tmp%' for the log file path can be used to write the log file to the active user's
local 'Temp' folder.
If you are upgrading from a previous version of the software, you may also need to upgrade
your reference data. For details, see Upgrading Reference Data (on page 57).
You do not need to set the default data locations in Options Manager before creating a P&ID
in SmartPlant Drawing Manager. These locations are set at the time of plant structure
creation. The drawing template path should be set to the correct node name and share
name so that the software can locate the templates for P&ID creation. For the correct share
name, see Install SmartPlant P&ID Reference Data (on page 33).
For a configuration in an integrated environment, be sure the SmartPlant Resource Path
setting in Options Manager points to the SmartPlant Resources folder installed with the
SmartPlant P&ID reference data.
8. Click Install.
9. On completion of the installation, if you want to open the Readme file, select View Readme.
10. Click Finish to close the installation wizard.
11. After installation, do the following:
a. Share the folder that contains the reference data. All SmartPlant users must be granted
read permission to this share. Write permission to the share is required to make
changes to the symbols, rules, templates, and other reference data.
b. Ensure that the SmartPlant Resource Path setting in Options Manager points to this
folder.
We recommend that you make a copy of the reference data and store it with your
plant files. This common practice will help you with future service pack installations, data
recovery, and so forth.
When you access the SmartPlant P&ID 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: upgrading the database to a new version or importing a large
number of drawings.
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.
In a Citrix environment, links within a .chm file to open a web browser will not work. To
view the linked web page, copy and paste the web address into the web browser on your local
machine.
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.
d. Click Check Names to verify the entered names.
h. Click Next.
10. On the Shortcut presentation page, do the following:
a. Click Change Icon to change the application icon if necessary.
b. Select options for application shortcut placement as desired.
c. Click Next.
11. On the Publish immediately page, click Finish.
In the main window, click the Delivery Groups tab, select the groups, and in the
Actions pane at the right, click Create Application.
In the main window, click the Applications tab and in the Actions pane at the right,
click Add Applications.
4. On the Applications page, select the check boxes beside the applications you want to add
and click Next.
If you want to add an application from a location other than the local machine, click
Add applications manually and in the dialog box that opens, enter the required
information.
Upgrade Prerequisites
1. Identify Oracle database constraint violations using the Database Constraint Report.exe
delivered with the current version of SmartPlant P&ID. If you are working on a SQL Server
platform, you can skip this step.
2. If your site database is out of date, upgrade it using SmartPlant Engineering Manager, and
then if the application database is out of date, upgrade it using the SmartPlant Engineering
Manager Upgrade Utility. If you are using Workshare and have a satellite plant, upgrade that
plant too.
3. Open and then close SmartPlant P&ID Options Manager without running any commands.
This action updates the RAD version for the ProjectStyles.spp file and as a result, changes
the status of the Symbology for the drawings to 'Out-of-Date'.
4. Update drawings as needed using SmartPlant P&ID Drawing Manager.
4. Resolve constraint violations. For more information, see Using Constraint Utilities (on page
53).
5. Generate a database constraint exceptions report again.
6. Run the appropriate constraint utilities again if any exceptions still exist.
7. Continue running the database constraint report and the constraint utilities until no
exceptions are reported.
8. Make a complete backup of the now compliant data.
For additional information on resolving discrepancies listed in the database constraint
report, contact your Customer Service representative.
If you use SmartPlant P&ID to connect to the plant, be sure to close all drawings before
proceeding.
Microsoft Excel must be installed on any workstation from which you run the Database
Constraint Exception Report utility.
1. In the ..\SmartPlant\P&ID Workstation\bin folder, double-click the Database Constraint
Report.exe file.
2. On the Database Constraint Exception Report Utility dialog box, click Connect to Active
Plant.
The utility runs the report on the active plant that you are connected to at the
time. To run a report on another plant, connect to that plant using SmartPlant P&ID or one of
its manager applications.
3. After connecting to the database, click the Create Database Constraint Report button.
This process may take several minutes, depending on the amount of data you have in your
plant.
4. When complete, the utility automatically saves a copy of the report in the temp directory
under your user profile and displays the file name (plant name -
ConstraintExceptions.xls) in the list box on the right side of the Database Constraint
Exception Report Utility dialog box.
5. Exit the Database Constraint Exception Report utility.
6. Open the report using Microsoft Excel and save a copy of the report to another location
other than the Temp folder.
7. Review the completed report for discrepancies that must be resolved before you can
upgrade to the new version of SmartPlant P&ID. We recommend running this utility again
until no discrepancies are reported.
Constraint Utilities
Delivered with SmartPlant P&ID, the following constraint utilities help you correct any database
constraint exceptions reported in the database constraint exception report.
In general, each utility attempts to repair the constrain violation. However, in some cases the
violation cannot be cleaned up by the utility and the item is band-aided in the drawing. This
situation is noted and logged in each utility's corresponding log file. For more information, see
Constraint Utilities Log Files (on page 55).
You must manually fix any band-aided item in a drawing by deleting the item and
replacing it. If you have difficulty finding the band-aided items, click Tools > Options in
SmartPlant P&ID, then select the Display as Printed option on the Options > General tab.
cmdnotconnectedcomps.dll — Repairs items that have a relationship to a PipeRun or
SignalRun (sp_piperunid or sp_signalrunid are not null), but are not referenced by a
corresponding connector. If the relationship cannot be repaired, you must delete it and replace
it.
cmdLPCheck.dll — Checks for LabelPersist records pointing to a representation that does not
exist. If the graphical label is watching a graphic, the database is updated to match, thus
repairing the LabelPersist. If the label cannot be repaired, the utility band aids it. You should
delete and replace these band-aided items.
cmdRepOIDCheck.dll — Checks for symbol records with a null graphic OID. If the graphical
symbol exists, the utility repairs the item by updating the database with its graphic OID value. If
the graphical symbol does not exist, the utility sets the InStockpile flag = True to repair the item.
ConnectorItem12.dll — Checks for connector records pointing to a symbol that does not
exist. If the graphical connector is connected to a symbol, the utility repairs the connector by
updating the database to match. If the connector cannot be repaired, the utility band aids
it. You should delete and replace these band-aided items.
OPCFK.dll — Checks for OPC records with a partner that does not exist. If the graphical OPC
exists, fix it. You should delete these items.
PointIndexCheck.dll — Checks for PipingPoint records and SignalPoint records with non-
unique indices or point numbers, then repairs the item by deleting from the database whichever
one of the duplicate points is not loaded into the cache.
RelationshipOIDMacro.dll — Checks for relationship records with a null graphic OID. If the
graphical relationship indicator exists, the utility repairs the item by updating the database with
its graphic OID value. If the graphical relationship indicator does not exist, the utility deletes the
relationship from the database.
RepairBadConnector.dll — Checks for connectors with the same start and end objects and
connectors with the wrong number of vertices. The utility band aids the graphical connector,
which you should delete.
RepairNullFileNameCmd.dll — Checks for LabelPersist records with a null file name value.
If the number of LabelPersist records equals the number of SmartLabel objects locked to the
watched symbol, the utility repairs the LabelPersist record by updating the filename value for
the LabelPersist.
If the number of LabelPersist records does not equal the number of SmartLabel objects
locked to the watched symbol, then the utility band aids the watched symbol. You should
delete band-aided items.
For the remaining LabelPersist records with a null filename, if the graphic exists, the utility
band aids it. You should delete band-aided items. If the graphic does not exist, the utility
deletes the representation from the database.
RepairOrphanedNozzleCmd.dll — Checks for the following situations.
Nozzle records without a Parent — If the Nozzle graphic is not in the drawing, the utility
repairs the nozzle by setting the Instockpile flag = True. If the Nozzle graphic is in the
drawing, the utility tries to set either the SP_EquipmentID or SP_PartOfID based on the
graphic relationship. The graphic parent must be an equipment or equipment component
for the relationship to be re-established. If the relationship cannot be re-established, the
utility band aids it. You should delete band-aided items.
Nozzles associated via SP_EquipmentID to a Parent in the stockpile — If the Nozzle
graphic is not in the drawing, the utility repairs the Nozzle by setting the Instockpile flag =
True. If the Nozzle graphic is in the drawing, the utility band aids it. You should delete
band-aided items.
Nozzles associated via SP_PartOfID to a Parent in the stockpile — If the Nozzle graphic
is not in the drawing, the utility repairs the Nozzle by setting Instockpile flag = True. If the
Nozzle graphic is in the drawing, the utility band aids it. You should delete band-aided
items.
Nozzles that are a Part of a Run — The utility clears the SP_PartOfID attribute. If the
Nozzle graphic is not in the drawing, the utility repairs the Nozzle by setting the Instockpile
flag = True. If the Nozzle graphic is in the drawing, the utility band aids it. You should
delete band-aided items.
cmdnotconnectedcomps.dll RepairNotConnectedComps.log
cmdLPCheck.dll RepairBadEmbLabelCmd.log
cmdRepOIDCheck.dll RepresentationOIDChecks.log
ConnectorItem12.dll ConnectorItem12_Check.log
OPCFK.dll OPC_OPC_FK.log
PointIndexCheck.dll PointIndexConstraint_check.log
RelationshipOIDMacro.dll RelationshipOID_Checks.log
RepairBadConnector.dll RepairBadConnector.log
RepairOrphanedNozzleCmd.dll RepairOrphanedNozzles_.pid.log
RepairNullFileNameCmd.dll RepairNullFileNameCmd.log
Post-Upgrade Tasks
After you complete all of the upgrade tasks for a plant, make a full backup of the upgraded
databases. You should also use the Oracle analyzer scripts to optimize your databases.
Some or all of the following post-upgrade tasks may also be required:
Backup Each Upgraded Plant (on page 56)
Use Oracle Analyzer Scripts (on page 56)
Preserve Software Customizations (on page 56)
Update Symbology Definitions (on page 57)
Make Additional Changes for SmartPlant P&ID (on page 57)
3. In the Engineering Data Editor, click the View menu and select Edit View.
4. On the Table Properties dialog box, click Advanced.
User Access
Before you can upgrade the reference data and drawings for an upgraded plant, you must
define user access for the plant in SmartPlant Engineering Manager. For more information
about defining user access, see the SmartPlant Engineering Manager User's Guide.
After you upgrade reference data, you cannot view it in earlier versions of the software.
For information about changes made during the reference data upgrade, see the
V4RefDataUpgrade.log file. This log file is saved in the folder where the symbols are
stored. For more information about upgrading reference data, see the SmartPlant P&ID
Options Manager User's Guide.
4. Click OK.
After you upgrade reference data, you should not view it in earlier versions of the software.
For information about changes made during the reference data upgrade, see the
V4RefDataUpgrade.log file. This log file is saved in the folder where the symbols are
stored.
For more information about upgrading reference data, see SmartPlant P&ID Options
Manager Help.
Updating Drawings
Changes are often made to the SmartPlant P&ID reference data while work is being managed
on the P&IDs. When these changes are made, they apply to all drawings items after the time of
change, but do not apply to existing drawing items. The Update Drawings functionality (provided
by the set of Out-of-Date Drawings commands in Drawing Manager) allows you to manage
which drawings are updated with the latest reference data changes by defining values that
define out-of-date drawings criteria and by resolving any symbols that have been deleted,
moved, or renamed.
You can also schedule these update operations and create reports. For more information about
this functionality, see the Drawing Manager User's Guide.
Using the Update Drawings functionality is not required as part of the upgrade process, but it
is strongly recommended.
After upgrading to the latest version of SmartPlant P&ID, opening Options Manager for the
first time updates the RAD version for the ProjectStyles.spp file and as a result, changes the
status of the Symbology for the drawings to 'Out-of-Date'. For this reason, after upgrading
SmartPlant P&ID, you should open and close Options Manager once before updating your
drawings using SmartPlant P&ID Drawing Manager.
After upgrading SmartPlant P&ID from a version earlier than 2014, you should open and
close Rule Manager once before updating your drawings using SmartPlant P&ID Drawing
Manager. This ensures that the Rules.rul file is updated with the new rules. The following
rules were added in SmartPlant P&ID 2014:
Connect To Process To Duct Run
Duct Run
Duct Run Label
Duct Run OPC To Duct Run
Duct Run To Duct Run
Duct Run To Nozzle
Ducting Components
Ducting Component Label
Ducting Comp To Duct Run
Ducting Comp To Ducting Comp
Ducting Comp To Instrument Inline
Ducting Comp To Nozzle
Ducting Comp To Signal Pipe Run
Instrument Inline To Duct Run
Internal Nozzle To Room
Nozzle To Room
Process Pipe Run to Ducting Comp
Room
Room Component
Room Component Label
Room Comp to Room
Room Comp to Room Comp
Room Label
If an existing rule has the same name as one of the new rules, a numeric suffix is added to
the name of the new rule, for example: 'Duct Run_1'
When you submit a selection of P&IDs to the Out-of-Date Drawings > Update command,
Drawing Manager analyzes the drawing for changes to the following:
Data Dictionary (select lists)
Formats
Symbols (moved and missing symbols, and changes to the .sym file)
Rules Manager
Options Manager (heat tracing, gapping, and symbology)
Model Items (via Llama)
OPCs (moved)
Drawings in a Re-create state
Drawing Properties
After this analysis process, a summary displays, listing the number of drawings selected, the
number of out-of-date drawings, and the number of drawings with missing symbols. You must
manually resolve the missing symbols using the Resolve Missing Symbols dialog box, which
lists the symbols in question and allows you to define the new location of each symbol.
In addition to the interactive approach of updating drawings, you can schedule the entire update
process, except for the resolution of missing symbols, which is a manual process as described
above.
Reporting capability provides a summary of the selected drawings and the out-of-date criteria
detected during the analyze step. This report format is non-configurable.
Update Command
Displays the Update Drawings dialog box. When you select this command, the selected
drawings are analyzed based on the out-of-date criteria and the results display on the Update
Drawings dialog box.
Update does not update any symbol whose definition has been changed into a break
component. This situation occurs when you have a catalog item that has been placed in a
drawing and then you change its definition to be a break component. The SmartPlant P&ID
Replace command does not allow a non-breaking component to be replaced with a break
component. The Update command relies on the SmartPlant P&ID Replace command to
replace symbols that are out-of-date.
If an item type property has Write P&ID or Write Both permissions in Data Dictionary
Manager and a symbol belonging to the item type is changed in Catalog Manager, running
the Update command on a drawing in Drawing Manager will NOT overwrite values assigned
to this property with any defaults that may have been pre-defined in Catalog Manager. If the
property permissions are Write Catalog in Data Dictionary Manager, Update will restore any
default property values defined in Catalog Manager.
Intergraph recommends that you backup your work or create a version of your work
prior to using this command.
In order to resolve any missing symbols, you must have an existing symbol in the catalog to
define as the replacement for the missing symbol.
You cannot resolve missing symbols for offline instruments of a different class using this
command.
See Also
Update Command (on page 60)
Symbology Changes — Symbology GUID on the drawing item is not equivalent to the
Symbology GUID in Option Manager Setting.
Out-of-Date Model Items — SP_ModelItemTimeStamp for at least one representation in the
drawing is not equivalent to the TimeStamp on the History Item of its Model Item. This criteria
covers model items updated via Llama (Outside the drawing).
Moved OPCs — MatingOPCPath (will have Drawing ID of its mate) on the OPC is not
equivalent to the SP_DrawingId of its mate OPC. The OPC label is in a to-be-updated state as
its mate has been moved.
Recreate State — The drawing is in a re-create state.
Drawing Property Changes — Property Changes GUID on the drawing item is not equivalent
to Drawing Property Changes GUID on the drawing item. Drawing Property Changes GUID is
set when drawing properties are modified from Drawing Manager.
User Access
User access identifies the users allowed to work at specified access levels within the site and
related plant structures. With user access, administrators can control access to data and
thereby ensure the security of their project data.
To see the roles currently defined for a plant, click the Roles node under the plant node in
the Tree view.
To view the rights settings for a particular role, right-click the role in the List view and click
Properties.
Mutually-Exclusive Rights
User rights can vary from one plant to another in the same site. These rights are defined by
categories. Categories with radio button options indicate that the rights contained within are
mutually exclusive, meaning you can choose only one right in that category to apply to the role.
In other categories, you can choose multiple rights, as denoted by check boxes.
None — The user is not allowed to execute the application or utility for this plant structure.
Read-Only — The user can execute the application or utility for this plant structure to view
the data held within it.
Modify Settings — The user can execute the application or utility for this plant structure to
view the data held within it and to modify any custom settings.
Full Control — The user can execute the application or utility for this plant structure and
perform all commands and modifications. This right is not available to a satellite site when
operating in the Workshare mode because the reference data must be controlled by the host
site.
Plant Filters None None prevents users from accessing Filter Manager.
Full Control Full Control allows users to create new filters and
edit existing filters. Full Control is disabled for
Workshare satellites and projects.
Display Sets None Controls the ability to view, edit, and define display
sets. Full Control is disabled for Workshare
Read-Only
satellites.
Full Control
Default Views None Controls the ability to specify default filters and
layouts for item types. Also controls setting the
Read-Only
Brief/Bulk Lists associated with item types.
Full Control Full Control is disabled for Workshare satellites and
projects.
Plant Reports None None prevents users from accessing the plant
reports.
Full Control Full Control allows users to create new rules and
edit existing rule definitions. Full Control is
disabled for Workshare satellites and projects.
Data Dictionary None None prevents users from accessing Data Dictionary
Manager. Modify Select Entry and Full Control
are disabled for Workshare satellites and for
projects.
Modify Select Modify Select Entry allows users to edit select lists.
Entry
Full Control Full Control allows users to add items and edit
existing items in the data dictionary. Modify Select
Entry and Full Control are disabled for Workshare
satellites and for projects.
Full Control Full Control allows users to add options and edit
existing options. Full Control is disabled for
Workshare satellites and for projects, but users must
have at least Modify Settings level privileges to use
Workshare.
Drawing Management Create P&ID Create P&ID allows users to execute the New
Drawing command in Drawing Manager.
Edit Import Map Edit Import Map allows users to execute the Edit
Import Map command in Drawing Manager.
P&ID Objects None None prevents users from accessing objects in the
SmartPlant P&ID Modeler environment.
Get Latest Get Latest Version allows users to obtain the latest
Version published drawing from the host or satellite site.
Projects Check Out Check Out allows users to execute the Check Out
and Undo Check Out commands in Drawing
Manager.
Plant Administrators
This user group has full control over all aspects of the plant structure for drawings,
administrative tasks, and reference data. The users should have the capability to create plant
groups, add applications and roles, create projects, enable Workshare, and create satellites, but
should not see the hierarchy templates or plant group types.
Plant Users
This group has full control on all drawings, can set personal filters, set up personal display sets,
set up My Reports, create drawings, and archive drawings (needed for personal use in case
there are big changes to the drawing design).
Engineers
This group has access to drawings to view and modify data reports but not graphics. They can
set up personal filters, set up personal display sets, and create My Reports. They should not be
able to modify any project reference data or perform any administrative tasks with respect to
drawing management, projects, or Workshare activities.
Managers
This group needs only view data access. They can set up personal filters, set up personal
display sets, and create My Reports. They should not be able to modify any project reference
data or perform any administrative tasks with respect to drawing management or Workshare
activities.
Display Sets Full Control Full Control Full Control Full Control
Drawing Management Create P&ID, Create P&ID Undefined (do Undefined (do
Delete P&ID not choose not choose
anything) anything)
Metric Templates
Template File Border File Page Size
English Templates
Template File Border File Page Size
8. Click Open.
9. Click OK on the Insert Object dialog box.
10. Position the border file in the template.
11. Click File > Exit.
SmartPlant P&ID interacts with SmartPlant Foundation by correlating items between the plant
database and the SmartPlant Foundation database, retrieving documents from SmartPlant
Foundation. Also, SmartPlant P&ID creates a set of tasks in the To Do List that you can run to
update the plant database. In SmartPlant P&ID, you can also use the commands on the
SmartPlant menu to publish documents and retrieve data, access the SmartPlant Foundation
Web Portal in order to browse in SmartPlant Foundation, and subscribe to change notifications
and compare documents.
You can only use the SmartPlant menu commands after your plant is registered. For
more information, see SmartPlant Engineering Manager Online Help.
Registering Tools
Before you can publish and retrieve documents from any of the other authoring tools, such as
SmartPlant Electrical or SmartPlant Instrumentation, you must register each plant in SmartPlant
P&ID with a SmartPlant Foundation database. The connection allows SmartPlant P&ID to use
the commands on the SmartPlant menu. A SmartPlant Engineering Manager administrator
typically registers a plant.
The software maps a plant and all its projects to a single SmartPlant Foundation URL, which
points to one, and only one, SmartPlant Foundation plant database and its projects. When you
use the Register command in any of the authoring tools, you are registering an authoring tool
plant with a SmartPlant Foundation URL and plant that you specify.
The system administrator must register each plant in the authoring tool once; this action takes
place in SmartPlant Engineering Manager. After the plant is registered, you can publish and
retrieve documents.
The path specified in Options Manager must contain the tool schema (for
example, SPIDDataMap.xml) for publish and retrieve operations between the tool and
SmartPlant to work properly. For more information, see the SmartPlant P&ID User's Guide.
5. Register your SmartPlant plant with SmartPlant Foundation, as described in the SmartPlant
Engineering Manager Help.
When you register your plant, you must specify the location of the SmartPlant
Engineering Manager schema map file (SPEMDataMap.xml). For more information,
see the Specify Map File Dialog Box topic in SmartPlant Engineering Manager Help.
If only one application is associated with the plant at the time it is registered, only that
application is registered. If another application is later associated with the plant, the
Register command is enabled so that you can register the new application with the
plant.
Instrument Expansion
A SmartPlant P&ID instrument or loop tag does not always have a 1:1 relationship with
instruments in SmartPlant Instrumentation. In some cases, a single item tag in a P&ID
corresponding to an instrument or loop needs to be expanded to create several instruments
when publishing the data for SmartPlant Instrumentation. For this purpose, the Expansion
Type property in SmartPlant P&ID specifies the expansion behavior when publishing an
instrument or loop. Each value of the property corresponds to a SmartPlant Instrumentation
rule that determines which instrument types and numbers are to be created in SmartPlant
Instrumentation when the SmartPlant P&ID tag is expanded and retrieved.
When retrieving data back to SmartPlant P&ID, the behavior of a particular
instrument created by expansion is determined by SmartPlant Instrumentation parameters.
For an expanded instrument, the state of the IRetrievableExpansion interface determines
whether that instrument will be retrieved by SmartPlant P&ID: if the IRetrievableExpansion
interface is realized, the instrument is retrieved, whereas if the IRetrievableExpansion
interface is not realized, the instrument is not retrieved. The 'parent' item tag is always
retrieved, regardless of the realization state of the IRetrievableExpansion interface.
Ports
SmartPlant Instrumentation uses physical ports, while SmartPlant P&ID uses logical ports.
SmartPlant Instrumentation publishes the physical ports with the Dimensional Data Sheets
and not the Instrument Index. SmartPlant P&ID retrieves the Instrument Index and does
not retrieve the Dimensional Data Sheets.
When the workflow goes from SmartPlant P&ID to SmartPlant Instrumentation, followed by
SmartPlant Instrumentation publishing the Dimensional Datasheet, a Same As relationship
is created between the ports in the SmartPlant Foundation database. That Same As
relationship is required by Smart 3D to correctly match the design basis ports to the 3D
representation of the ports.
When the workflow goes from SmartPlant Instrumentation to SmartPlant P&ID, however, a
Same As relationship is not created in the SmartPlant Foundation database. Without the
Same As relationship created in the SmartPlant Foundation database, the result may be
additional ports in Smart 3D. To obtain the Same As relationship on the ports requires that
SmartPlant P&ID publish the P&ID with the instrument, this P&ID be retrieved by SmartPlant
Instrumentation and then having SmartPlant Instrumentation publish the Dimensional Data
Sheet.
Drawing Items
For Smart 3D to properly determine flow direction in a process run, that process run must be
connected to at least 2 items.
Some items that can be represented as single objects in SmartPlant P&ID, such as Vent
Detail, are modeled in Smart 3D as a set of separate objects. For full correlation to be
established between the two tools, ensure that these objects are modeled in SmartPlant
P&ID with the same configuration used to represent them in Smart 3D.
Properties
Smart 3D handles temperature and pressure properties in pairs and does not support having
a temperature (for example, Normal Operating Temperature) without defining the matching
pressure (in this case, Normal Operating Pressure). While this is a valid condition for
SmartPlant P&ID, it should be a consideration when publishing for retrieval into Smart 3D.
Without the Pressure / Temperature pair of values defined, the Smart 3D user will be
required to enter a value that was not defined in SmartPlant P&ID.
found, the software uses the CatalogItemName from the first one. If no match is found, the
software performs the search based on Class.
Search Based on Class Value — Searches the catalog index for all rows with matching
ItemTypeName and Class values and IsDefaultForClass = True. If one or more rows are found,
the software uses the CatalogItemName from the first one. If no match is found, the software
returns an empty string.
If you add an enumerated list attribute to the plant data dictionary, see the Hierarchical
Enumerated Lists topic in the SmartPlant P&ID User's Guide for information about mapping
these complex data types.
The default SPEMdatamap.xml file contains the EF_SPAPlant attributes (CompanyName,
SiteName, SiteLocation, DivisionName, and DivisionLocation). This file is delivered to the
..\Engineering Manager\SmartPlant Resources folder.
After registering, SmartPlant Engineering Manager cannot retrieve the PBS document if the
plant and SmartPlant hierarchies are not compatible. To be compatible with the SmartPlant
hierarchy, your plant hierarchy can contain less than or equal, but not more than the number
of levels in the SmartPlant hierarchy.
SmartPlant Engineering Manager retrieves from the SmartPlant hierarchy only the hierarchy
levels it needs. For example, if your plant hierarchy contains 4 levels and the SmartPlant
hierarchy contains 8 levels, only the top 4 levels of the SmartPlant hierarchy are retrieved.
All SmartPlant Engineering Manager hierarchy item names (plant group names) below the
plant (top level) must match the names in the SmartPlant Foundation plant hierarchy that are
at the same level. The names are case-sensitive and therefore the cases must also
match. The plant names do not have to match.
In addition to requiring a minimum of three-levels in hierarchies, SmartPlant integration also
requires that the names of hierarchy items cannot be changed after they are created and
that the hierarchy structure cannot be modified after you create the project. For more
information, see the SmartPlant Enterprise Installation and Setup Guide.
You must install the Schema Component and the SmartPlant Client, delivered with
SmartPlant Foundation, on your SmartPlant Engineering Manager workstation before you
can register your plant.
If only one application is associated with the plant at the time it is registered, only that
application is registered. If another application is later associated with the plant, you must
also register the new application with the plant.
After the plant is registered, the SmartPlant tab is added to the Plant Structure Properties
dialog box. The SmartPlant tab displays the SmartPlant Foundation URL, the SmartPlant
Foundation plant database, and the unique application identifiers returned by the registration
process.
G P
Generate a Database Constraint Post-Upgrade Tasks • 56
Exceptions Report • 52 Preparing the Integrated Environment • 80
Grant Permissions to Write to a Registry Prerequisites • 20
Key • 24 Preserve Software Customizations • 56
Publish SmartPlant Applications Using
H XenApp 6.5 • 36
Hardware and Software Recommendations Publish SmartPlant Applications Using
• 13 XenDesktop 7.0 RDS • 46
I R
Install Intergraph Smart 3D SP3DPIDClient Register Command (SmartPlant Menu) • 86
• 23 Resolve Command (File > Out-of-Date
Install Oracle Client • 20 Drawings > Update Drawings Menu) • 61
S
Silent Mode Installation Example Scripts •
31
SmartPlant P&ID Database Server • 13
SmartPlant P&ID Delivered Templates • 75
SmartPlant P&ID Program Group • 8
SmartPlant P&ID User Rights • 65
SmartPlant P&ID User Rights Examples •
70
SmartPlant P&ID Workstation • 14
T
Tool Requirements for Integrating
SmartPlant P&ID • 81
Tuning the Software for Use in Thin Client
Mode • 36
U
Uninstall a Previous Version of SmartPlant
P&ID • 24
Update Command • 60
Update Symbology Definitions • 57
Updating Drawings • 58
Upgrade Reference Data • 58
Upgrading Reference Data • 57
Upgrading SmartPlant P&ID • 51
Use Oracle Analyzer Scripts • 56
User Access • 65
Using Constraint Utilities • 53
Using Custom Hierarchies in an Integrated
Environment • 85
Using Environment Variables for Tracking
Licensing • 17
W
Welcome to SmartPlant • 7
Working in Thin Client Mode • 35
Working with Filters • 73
Working with Formats • 74
Working with SmartPlant Integration • 79
Working with Symbols and Labels • 74