Sppidtopds
Sppidtopds
March 2015
DPID2-PE-200019I
Copyright
Copyright © 2003-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.
Index ........................................................................................................................................................... 27
Installation
You can set up SmartPlant P&ID using a full installation. Full installation works with the full
SmartPlant P&ID Installation on the local computer.
For details of supported SmartPlant P&ID software versions, see the SmartPlant P&ID
Installation and Upgrade Guide > Hardware and Software Recommendations.
Install Oracle
1. Start Oracle Database Configuration Assistant, select the Local Net Service Name
configuration option from the list, and click Next.
2. Click Add, and then click Next.
3. In the Service Name box, type the oracle SID name of the SmartPlant database. Click
Next.
4. In the protocol form, accept the default TCP option. Click Next.
5. In the Host Name box, type the P&ID site server name. Accept the default port number
1521. Click Next.
6. Click Yes to perform the test, and then click Next.
7. To test the service, click Change Login and specify a valid username/password
combination of the SmartPlant database, and then click OK. You should see the
Connecting...Test successful message. Click Next.
8. In the Net Service Name box, type the name of the database alias to use for the data
transfer. The Net Service Name must be exactly the same as it was defined in the
SmartPlant database server. Click Next three times, and then click Finish.
You may enter any values that you want for the user name and company name;
however, you may not leave these fields blank.
8. Under Select Features to Install, select any additional features that you want to install.
If you want to upgrade your SmartPlant Engineering Manager data, be sure that you
select Upgrade Utility to install the SmartPlant Engineering Manager Upgrade Utility.
For more information, see the SmartPlant Engineering Manager Upgrade Utility User's
Guide.
SmartPlant Engineering Manager is always installed, regardless of any other features
you select.
9. In the Install Path field, accept the default installation path or if desired, specify a different
path, and then click Install.
10. On completion of the installation, if you want to open the Readme file, select View Readme.
11. Click Finish to close the installation wizard.
SmartPlant License Manager software is required for concurrent licensing for both the core
SmartPlant P&ID to PDS Piping Data Transfer product and for each feature, therefore you
must install and configure SmartPlant License Manager on your workstation before installing
SmartPlant P&ID to PDS Piping Data Transfer. 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 to PDS Piping Data Transfer 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 Start Setup.
3. On the Details and Features page, enter your product serial number.
A green check mark beside the serial number indicates that it is valid.
4. If desired, 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.
5. Under Select Installation Mode, choose whether to install SmartPlant P&ID or SmartPlant
P&ID Engineering.
6. 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.
7. In the Install Path field, accept the default installation path or if desired, specify a different
path, and then click Next.
8. 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.
9. Click Install.
10. On completion of the installation, if you want to open the Readme file, select View Readme.
11. Click Finish to close the installation wizard.
If you try to install SmartPlant P&ID to PDS Piping Data Transfer 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 SmartPlant P&ID
Installation and Upgrade Guide > Grant Permissions to Write to a Registry Key.
The driver used for printing the PDF files, SmartPlant PDF Converter (Amyuni 4.5), is
included in the SmartPlant P&ID to PDS Piping Data Transfer 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.
numbers for a PDS piping segment must match with a P&ID segment. If the SmartPlant P&ID to
PDS Piping Data Transfer has not been done for a piping segment, then no node number is
defined for that segment. This situation generates a Node Numbers Undefined only
discrepancy. If the majority of the piping falls under this category, then the number of
discrepancies can be very high. To reduce this number, change the matching criteria to
something other than node numbers. Typically, any of the individual properties of a line
number label such as NPD, line sequence number, insulation purpose, and so forth, can be
used. It is better to use as many properties as possible so that they form a unique combination.
All properties specified as matching criteria should have some value assigned to them on both
sides.
Another alternative to running the comparison report is to specify segment search criteria. This
method can be used if all instrument connections on equipment or drain lines not shown on the
P&ID contain common attributes such as different fluid codes or prefixes to line sequence
numbers, and so forth.
Another possibility is to use a range of diameters so that small diameter segments can be
eliminated.
When setting up data transfer for multiple plants, if the PDS 3D and SmartPlant P&ID
plants have the same set of properties and the same intended mapping, then you can
copy the SPMap.mdb file from one plant to another. The Attribute Mapper always
verifies that the SmartPlant site in the .mdb file is the same as the map for the selected
PDS project. However, if you are not sure if the plants have the same set of properties,
we recommend that you copy the delivered SPMap.mdb file from the PDSHELL\pid\
folder.
For a project where data transfer was set up to work with an earlier version of
SmartPlant P&ID, some attribute mappings have changed. You can use either the new
SPMap.mdb file delivered in the PDSHELL\pid\ folder or follow the procedure mentioned
for CR32693 in the PDS README file.
Even if you are going to work with the default attribute mapping, you must start
SmartPlant Attribute Mapper at least once. If necessary, you can back up the updated
SPMap.mdb file, delete the changes, and copy a fresh SPMap.mdb to go through the
mapping process again.
1. Copy \WIN32APP\INGR\PDSHELL\pid\SPMap.mdb and SPTransferOpt to the PDS project
directory. For projects created with version 6.4.1 or later, these files are copied automatically
from the PDSHELL\pid folder at the time of project creation.
2. Click Start > Programs > PD_Shell > SP PID to PDS 3D to display a list of available PDS
projects.
The software reads the list of PDS projects from the PDS proj_file.
The Attribute Mapper does not honor any other variables defined in the pds.cmd file,
such as RIS parameter file locations, and so forth.
3. Double-click the PDS project to use with SmartPlant P&ID and locate the SmartPlant
initialization (.ini) file.
The SmartPlant Migrator for P&ID utility opens and shows the PDS attributes for the
selected project.
The location of the SmartPlant initialization (.ini) file must be specified using a
complete UNC path. If path to this .ini file is mapped on a network drive and the mapped
network drive path is used to locate it, this results in errors.
Mapping Attributes
SmartPlant P&ID to Piping Data Transfer relies on an attribute map stored in a Microsoft Access
database located in the PDS project folder. This map database file is named SPMap.mdb, and
contains information about the Smart Plant P&ID site server and plant. The Attribute Mapper
utility is used to manipulate this map database. The Attribute Mapper is started from a shortcut
provided in the PD_Shell program group named SP PID to PDS 3D.
The Attribute Mapper utility maps, un-maps, or ignores attributes between PDS 3D and
SmartPlant P&ID. The Attribute Mapper interface is similar to Windows Explorer in that it
displays a tree view on the left side and list view on the right side. Attributes for piping segment,
piping component, and instrument tables from the PDS 3D design database are available to
map with corresponding SmartPlant P&ID tables, specifically the PipeRun, PipingComp and
Instrument tables.
The tree view divides attributes into four categories based on map status: Mapped, Unmapped,
Ignored, and All. For SmartPlant P&ID to PDS 3D data transfer, the Ignored map status is the
same as the Unmapped status.
Select Lists
Select-listed SmartPlant P&ID properties are transferred based on their text value instead of
number. The Attribute Mapper creates a map of PDS codelist entries for every SmartPlant select
list used in the mapped properties.
For example, fluid code "P" is represented by the PDS 3D codelist entry 25 and by entry 35 in
the SmartPlant P&ID select list. When the fluid code property is transferred, the property value
changes from 35 in the SmartPlant database to attribute value 25 in the PDS Database. This
functionality has removed the requirement of maintaining the same select list and codelist
values in SmartPlant P&ID and PDS 3D.
Properties mapped with the Transfer Mode option set to Partial are transferred when you
use the Partial Data Transfer toggle within PDS.
Properties mapped with the Transfer Mode option set to Default receive the default value,
which you enter in the Default box, during partial data transfer.
Properties mapped with the Transfer Mode option set to No Default do not get a default
value and do not get transferred during partial data transfer.
Properties mapped with the Transfer Mode option set to Partial are transferred when you
use the Partial Data Transfer toggle within PDS.
Properties mapped with the Transfer Mode option set to Default receive the default value,
which you enter in the Default box, during partial data transfer.
Properties mapped with the Transfer Mode option set to No Default do not get a default
value and do not get transferred during partial data transfer.
All Mapped properties are transferred during complete data transfer.
The Segment Data Comparison Report also includes line sequence numbers.
Because the data comparisons are performed on the basis of the PDS piping segments, not
all segments in the SmartPlant database are checked for matches.
The software creates the following files in the same directory location as the processed model
file:
A report file named model_number.pc (model_number is the number of the model that is
extracted from the PDS Project Database).
A non-printable, sorted file named model_number.pci (this file is used by the Review P&ID
Comparison Report command).
A non-printable, sorted file named model_number.pca (this file is used by the P&ID Data
Comparison, Update Model, Segment Data Comparison Report, and Review P&ID
Comparison Report commands for the approval of data discrepancies. The .pca file is
initially created when you approve a discrepancy, and the file is appended to with each
additional approval).
You can format the title page and the heading for each page of the Segment Data Comparison
Report using the \win32app\ingr\pddesign\sample\pid_cmprpt.fmt format file. The remainder of
the report is in the following format:
<line number> <P&ID Node Numbers> <P&ID Drawing Number>
insulation_purpose N P
Data in the Segment Data Comparison Report is sorted first by line number label and then by
the SmartPlant P&ID node numbers, if applicable.
SmartPlant P&ID
Consider the following points when planning for data transfer from a SmartPlant P&ID plant to a
PDS 3D project.
Symbol Properties — By default, PDS searches the piping specification based on
predefined aabbcc codes. SmartPlant P&ID symbols must have a property mapped to the
aabbcc_code attribute in the PDS database. The delivered SmartPlant P&ID piping
component symbols have a property called aabbcc_code, which can be viewed and edited
in Catalog Manager. Any new symbols must have this value defined, either at symbol
creation or later.
Naming Conventions — PDS 3D is not capable of handling spaces in the path names to
any files. Therefore, this PDS restriction also applies to P&IDs. While creating units and
drawings in the SmartPlant P&ID site, take care to avoid creating paths with spaces.
Symbology — SmartPlant P&ID stores drawings in a format other than IGDS
(MicroStation). These drawings are converted to IGDS format to display in PDS. By default,
PDS and MicroStation use a black background, while SmartPlant P&ID uses a white
background. When converted to IGDS format, this difference can make some SmartPlant
P&ID graphics barely visible on the black background. Consideration should be given to this
fact while defining symbology within SmartPlant P&ID plants. SmartPlant P&ID symbology is
defined in Options Manager.
Two methods exist to manipulate the display so that all of the graphics are clearly visible in
their new format:
Method 1: Turn off the Reference File > Use Color Table setting under User > User
Preferences > Reference File in PDS. This action displays the drawing using the active
color scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID.
Method 2: Change the Background color of the piping model to a light color by using
Settings > Colors.
Additional Attributes — If properties added to the SmartPlant database need to be
transferred to PDS, be careful to match attribute type and length on either side. The
maximum string length supported by RIS / PDS 3D is 240 characters. If a property has an
associated select list in SmartPlant P&ID, then it should have a corresponding codelist in
3D. You must run the Attribute Mapper to map new properties if you want the data to
transfer.
Codelists and Select Lists — Even though having the same number and sequence for
entries within a codelist or select list is not required, for any mapped attributes, the PDS 3D
codelist should have all entries from the SmartPlant P&ID select list. If a new text entry is
added to a SmartPlant P&ID select list, the same text entry should be created in the
corresponding PDS 3D codelist. The Attribute Mapper must be run after any such change.
Layers and Drawing Filters — PDS uses the concept of layers in a piping design to display
selected elements of a drawing; whereas, SmartPlant P&ID uses drawing filters. The
ExportLayer.xlsx file defines how the layers in PDS are related to the different drawing
objects. The location of this Excel file is defined in Options Manager.
You can assign layer alphanumeric names to item types in order to assure that graphics
appear in the designated layers in PDS. Items are named according to filters, which are
defined in Filter Manager. For more information, see the topics dealing with layers in the
SmartPlant P&ID Online Help.
PDS 3D
Codelists — A PDS 3D codelist can be a super set of a SmartPlant P&ID select list. This
means that a PDS code list can have extra entries not contained in the SmartPlant select list
because the data transfer works one way; that is, from SmartPlant P&ID to PDS 3D.
User Attributes — Attributes can be created in PDS 3D independent of the SmartPlant
P&ID plant if data transfer is not required. If transfer is required, care should be taken when
adding attributes. A SmartPlant database does not distinguish between short and long
integers. Any new integer property that is added to such a database must be created as a
long integer in the PDS database.
Units of Measure Option — Converts SI units in SmartPlant P&ID using unit-related codelists
from the Standard Note library in PDS. SmartPlant P&ID stores all properties with a unit of
measure in SI units. For example, length is stored in meters regardless of your plant settings.
The software then checks another property that determines how you want length values to
appear. When a property represents a quantity based on units (for example, pressure,
temperature, and so forth) data transfer looks at the active segment data, or type 63 settings, to
determine the unit of measure to use. The SI value stored in the database is then converted
using unit- related code lists from the Standard Note library.
Code-listed Attributes Option — Uses a codelist map to translate the codelisted attributes.
The Attribute Mapper stores mapping of codelist numbers such that their text values match.
Data transfer uses this codelist map to translate the codelisted attributes from the database to
the PDS database.
If the SmartPlant database participates in Workshare environment, then the P&ID list is a
combination of the P&IDs owned and subscribed to (that is, published by remote location) by
the site.
Use the LocalModelItemLookupTable.sql utility if your connected Workshare satellite
experiences performance problems when transferring piping data from SmartPlant P&ID to
PDS. This script converts a satellite database view (namely, the T_ModelItemLookup) that
references a host table into a local table, allowing the data transfer to proceed without using
a DBLink. SmartPlant P&ID uses the DBLink to fetch unique Long IDs from the Host when
running from a connected Workshare satellite. If the performance of opening the PID file in
PDS is an issue or if maintaining the correlation between SmartPlant P&ID and PDS after
the merge is not an issue, then you can run this script to change the lookup for the Long ID
from a view to the host to a local query. This utility is delivered as an SQL script to the
..\SmartPlant\P&ID Workstation\bin folder and can be executed using any Oracle user
interface, such as SQLPlus. Do not use this script if the transferred PDS data will be
merged back into a host PDS database because the Long IDs will not be unique at the host.
Because SmartPlant databases are unit-dependent and PDS databases are design
area-dependent, one PDS piping design area can include data from different SmartPlant
units. Consequently, you must specify the correct unit number in the active segment data
prior to requesting a list of P&IDs from a SmartPlant database.
Inline instruments are compared on the basis of their instrument component number
Tagged piping commodities in the SmartPlant database that have the following data are
included:
The Commodity Code flag is set to by system or by user and the commodity code is
defined
The Piping Component Number is defined
Piping specialties in the SmartPlant database are determined by those piping components
that have the following data:
The Commodity Code flag is set by the user or is blank
The Piping Component Number is defined
Instruments in the SmartPlant database are determined by the following criterion:
Only those instruments that are applicable to the PDS 3D model, such as those
requiring dimension definition in the RDB, as determined by an Instrument Correlation
List
The Instrument Correlation List, which is necessary to define the applicable instruments for
transfer, is a user-defined ASCII file in the project folder and is named pid_instrument. With this
list you can specify the inclusion or exclusion of SmartPlant P&ID instruments on the basis of
their aabb or aabbcc codes. You can include or exclude groups of instruments on the basis of
the aabb code for that instrument by using the appropriate keyword, either Include or Exclude,
followed by the aabb code. You can specify exceptions to the aabb codes on the basis of
specific aabbcc codes so that you can exclude from an Include group, or you can add those
entries to an Exclude group by adding the exceptions under the line containing the Include or
Exclude statement.
The ! character signifies a comment line in this ASCII file.
The following text represents the default Instrument Correlation List that defines the SmartPlant
P&ID instruments that are applicable to the PDS 3D model. In this example, the aabb code
represents a substring search of the aabbcc code.
!Include all control valves
Include 7P1E
!Include all relief devices
Include 7P2C
!Include all other in-line instruments
Include 7P3C
!except for the following
7P3C44
7P3C46
!Exclude all off-line instruments
Exclude 7Q4D
!except for the following
7Q4D21
7Q4D24
7Q4D27
7Q4D28
7Q4D29
7Q4D30
7Q4D31
7Q4D32
7Q4D33
! Exclude all system functions
Exclude 7Q5A
You can format the title page and the heading for each page of the Named Component
Existence report using the win32app\ingr\pddesign\sample\pid_cmprpt.fmt file. The remainder of
the report contains the following sections:
The list of line IDs that determine the basis for the report
Named components in the SmartPlant database, that are not in the PDS 3D model, are
reported with the component number and the drawing number
Named components in the PDS 3D model that are not in the SmartPlant database are
reported with the component number, the design area number, and the model number
Troubleshooting
Some common difficulties that you may encounter are listed here, along with possible solutions.
Display
Start PD_Shell, and go to piping. Inside the PDS piping model but before using the Graphical
P&ID Setup command, select one of the two methods below so that all of the P&ID items are
clearly visible in order to display properly the converted P&ID within PDS:
Method 1: Turn off the Reference File > Use Color Table setting under User > User
Preferences > Reference File. This action displays the drawing using the active color
scheme for the PDS model, rather than honoring the colors from SmartPlant P&ID.
Method 2: Change the Background color of the piping model to a lighter color by using
Settings > Colors.
Temperature/Pressure Units
Select lines for pipe run and component data for the Name from P&ID option. For Pipeline data,
four sets of temperature/pressure values with units must be set in the SmartPlant P&ID or you
will receive an error about temperature/pressure limits. You can choose the No Minimum T-P
Data for Service Limits Verification option in the PDS project data manager to prevent that
error. When using this option, the lower range of the temperature/pressure values is not
checked, thus allowing undefined values in PDS: -9999.
You must dismiss the Graphics Setup menu after selecting the P&ID that you want to
display. Sometimes this form may be hidden, and you must dismiss it before you can
transfer data from a pipeline.
Levels settings (that is, displays of drawing filters) are not saved for a SmartPlant P&ID
drawing. You must select the correct levels each time that you enter the drawing.
If you want to see the P&ID labels and line types correctly, you must map your P&ID fonts to
proper MicroStation fonts in one of the .ini files. ISO Plus RDB fonts and borders.txt contain
this information. Also, the standard RDB Arial Narrow is mapped to a not-always-present
MicroStation font and causes unreadable labels on the screen.
C R
Choosing Data Transfer Options • 18 Restore View of Piping Model Command •
Creating and Maintaining Links • 11 22
Review P&ID Drawing Details Command •
D 22
Revising Linked Models • 15
Disable Display of P&ID Drawing Command
• 22
S
E Segment Data Comparison Report • 17
Select P&ID by Line ID Command • 21
Establish a SmartPlant/PDS Link • 13 Select P&ID Drawing by Nozzle Command •
21
G
Graphical P&ID Setup Command • 20 T
Test the SmartPlant Connection • 10
I Transferring Piping Data • 7
Install Oracle • 8 Troubleshooting • 24
Install SmartPlant Engineering Manager • 8
Install SmartPlant P&ID • 9
Installation • 8
L
Load from P&ID Options • 20
M
Map an Ignored Attribute • 16
Map an Unmapped Attribute • 17
Mapping Attributes • 15
N
Name from P&ID Option • 20
Named Component Existence Report
Command • 22
O
Options and Commands • 18
P
P&ID Drawing Display Categories
Command • 22