Smart3D Content

Read me First -- Smart 3D .Net Plant symbols

August 2019
Copyright
Copyright © 2005-2019 Hexagon AB and/or its subsidiaries and affiliates. All Rights Reserved.
This computer program, including software, icons, graphic symbols, documentation, file formats, and audio-visual displays; may be used only as
pursuant to applicable software license agreement; contains confidential and proprietary information of Hexagon AB and/or third parties which is
protected by patent, trademark, copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available
without proper authorization from Hexagon AB and/or its subsidiaries and affiliates.
Portions of the user interface are copyright © 2012-2019 Telerik AD.
Portions of this software are owned by GemBox Software. Copyright (©) GemBox Software. All Rights Reserved.

U.S. Government Restricted Rights Legend

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

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

Read me First -- Smart 3D .Net Plant symbols 2

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.

Limitation of Damages
IN NO EVENT WILL INTERGRAPH CORPORATION BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL INCIDENTAL, SPECIAL,
OR PUNITIVE DAMAGES, INCLUDING BUT NOT LIMITED TO, LOSS OF USE OR PRODUCTION, LOSS OF REVENUE OR PROFIT, LOSS
OF DATA, OR CLAIMS OF THIRD PARTIES, EVEN IF INTERGRAPH CORPORATION HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
UNDER NO CIRCUMSTANCES SHALL INTERGRAPH CORPORATION’S LIABILITY EXCEED THE AMOUNT THAT INTERGRAPH
CORPORATION HAS BEEN PAID BY LICENSEE UNDER THIS AGREEMENT AT THE TIME THE CLAIM IS MADE. EXCEPT WHERE
PROHIBITED BY APPLICABLE LAW, NO CLAIM, REGARDLESS OF FORM, ARISING OUT OF OR IN CONNECTION WITH THE SUBJECT
MATTER OF THIS DOCUMENT MAY BE BROUGHT BY LICENSEE MORE THAN TWO (2) YEARS AFTER THE EVENT GIVING RISE TO
THE CAUSE OF ACTION HAS OCCURRED.
IF UNDER THE LAW RULED APPLICABLE ANY PART OF THIS SECTION IS INVALID, THEN INTERGRAPH LIMITS ITS LIABILITY TO THE
MAXIMUM EXTENT ALLOWED BY SAID LAW.

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®, SmartPlant®, SmartMarine, SmartSketch®, SmartPlant Cloud®, PDS®, FrameWorks®,
I-Route, I-Export, ISOGEN®, SPOOLGEN, SupportManager®, SupportModeler®, SAPPHIRE®, TANK, PV Elite®, CADWorx®, CADWorx
DraftPro®, GTSTRUDL®, and CAESAR II® are trademarks or registered trademarks of Intergraph Corporation or its affiliates, parents,
subsidiaries. Hexagon and the Hexagon logo are registered trademarks of Hexagon AB or its subsidiaries. Other brands and product names are
trademarks of their respective owners.

Read me First -- Smart 3D .Net Plant symbols 3

Contents
Introduction ................................................................................................................................................. 5

.NET Symbols available .............................................................................................................................. 5

.NET Symbols on an existing Project ....................................................................................................... 5

Plan to replace existing COM Symbols/Occurrences............................................................................. 7
Example of changing a part to use the compatible .NET symbol ........................................................... 8
For Equipment parts .................................................................................................................................. 8
For Piping and Instrumentation parts ........................................................................................................... 9
For HVAC parts ...................................................................................................................................... 10
For Cabletray parts .................................................................................................................................. 12
For Conduit parts .................................................................................................................................... 13

.NET Symbols on a new Project .............................................................................................................. 14

Read me First -- Smart 3D .Net Plant symbols 4

Introduction
The objective of this document is to Read it First before usage of the Smart 3D - .Net Plant
symbols

You must read this document before you start using the Smart 3D .NET Plant symbols.

.NET Symbols available

The .NET Symbols are created for the following disciplines:

• Civil
• Conduit
• Equipment
• HVAC
• Layout
• Materials Handling
• Penetration
• Piping
• Architecture
• Cable Tray

.NET Symbols on an existing Project

A symbol, which constitutes the graphics, is referred by a part in the Catalog database. The
SymbolDefinition property on the part defines the symbol that needs to be used for that part. A
symbol is identified uniquely by a ProgID, which is a string. The ProgID of the symbol is
specified on that SymbolDefinition property of the part.

Before Smart 3D v2014, all the symbols were developed using VB6 language and are called
COM symbols. The below graphic shows the ProgId: ‘SP3DGateValve.CGateValve’ of a Gate
valve part specified for the SymbolDefinition property in the data workbook.

Read me First -- Smart 3D .Net Plant symbols 5

An Occurrence is an instance of a part placed in the model. The occurrence placed in the model
refers to the part that exists in the Catalog.

After Smart 3D v2014, new .NET symbols have been developed in C# language and used the
APIs provided by the new 3D API framework. The .NET symbols are available in a separate .dll
file and have a different ProgID from that of COM symbols. As the 3D API framework is
available from Smart 3D v2014 or later, these .NET symbols can be used from Smart 3D v2014
or later.

Retired COM symbols

An exact matching .NET symbol has been created for every COM symbol that is developed as
per the best practices of symbol creation. However, there are few COM symbols, which are not
created as per the symbol creation standard and are set to be retired eventually.

So, an exact matching .NET symbol has not been created, however an equivalent best practice
.NET symbol to be used in lieu of it is identified.

All the ‘Eventually to be retired’ COM symbols that have an equivalent .NET symbol are
uniquely identified. The list of ‘Eventually to be retired’ COM symbols and their
equivalent.NET symbols are available on the Smart Support website under the Content download
page (Download the “SmartPlant Eventually to be Retired Symbols 2014.zip” zip file from the
folder “SmartPlant Eventually to be Retired Symbols - 2014 and 2014R1”).

The below graphic shows a snippet of the documentation that is available on the Smart Support
website, which lists the ‘Eventually to be retired’ COM symbols and its corresponding
replacement symbol information.

Read me First -- Smart 3D .Net Plant symbols 6

 A new part can refer to.NET symbol and occurrences can be placed in the model without
impacting any existing occurrences in the model. In other words, occurrences of COM symbol
parts and new .NET symbol parts can co-exist in the model without any issues.

If you are still not sure, open an SR.

Plan to replace existing COM Symbols/Occurrences

You can continue to use the COM-based symbol occurrences in the project if they are already
placed in the model.

If you are planning to update the COM symbol-based occurrences to refer to .NET based
symbol, then the Catalog data must be updated to refer to .NET symbol as described in the
examples below. You must run the ‘Synchronize Model with Catalog’ from Project Management
to update the placed occurrences.

Note: If the COM and .NET Symbol input attributes/parameters do not match, then the Symbol
input attributes defined on a partclass must be properly mapped with .NET Symbol input
attributes. Also ensure that Partdatabasis attribute is updated accordingly, if applicable for that
symbol.
For mapping the input parameters between two symbols, their corresponding SymbolIcon must
be referred. The input attributes/parameters of the replacement symbol must be defined in the
partclass. These attributes can be correlated with existing attributes by referring their respective
symbol icons.
For more information, contact Technical Support.

Read me First -- Smart 3D .Net Plant symbols 7

Example of changing a part to use the compatible .NET
symbol
The following steps must be followed for a user to change an existing part that refers to a Best
Practice COM symbol to a .NET symbol.

Refer to the “COM-3DAPI Symbol ProgID Map.pdf” on Smart Support for the mapping of the
ProgIDs between the COM and 3DAPI Symbols.

For Equipment parts

1. The Symbol Definition provided in the highlighted box below must be replaced.
Below is an existing part that refers to a Best Practice COM symbol.

2. The part should be updated with the corresponding .NET symbol.

Below is the updated part that refers to a .NET symbol.

Read me First -- Smart 3D .Net Plant symbols 8

 3. Specify the bulkload modifier ‘M’ at the partclass level and part level.
4. Bulk load the partclass in Add/Modify/Delete mode by specifying them in the Excel
files category of the bulkload tool.

For Piping and Instrumentation parts

1. The Symbol Definition provided in the highlighted box below must be replaced.
Below is an existing part that refers to a Best Practice COM symbol.

2. The part should be updated with the corresponding .NET symbol.

Below is the updated part that refers to a .NET symbol.

Read me First -- Smart 3D .Net Plant symbols 9

 3. Specify the bulkload modifier ‘M’ at the partclass level and part level.
4. Bulk load the partclass in Add/Modify/Delete mode by specifying them in the Excel
files category of the bulkload tool.

For HVAC parts

1. The Symbol Definition provided in the highlighted box below must be replaced.
Below is an existing part that refers to a Best Practice COM symbol.

2. The part should be updated with the corresponding .NET symbol.

Below is the updated part that refers to a .NET symbol.

Read me First -- Smart 3D .Net Plant symbols 10

 3. Specify the bulkload modifier ‘M’ at the partclass level and part level.
4. Bulk load the partclass in Add/Modify/Delete mode by specifying them in the Excel
files category of the bulkload tool.

Read me First -- Smart 3D .Net Plant symbols 11

For Cabletray parts

1. The Symbol Definition provided in the highlighted box below must be replaced.
Below is an existing part that refers to a Best Practice COM symbol.

2. The part should be updated with the corresponding .NET symbol.

Below is the updated part that refers to a .NET symbol.

3. Specify the bulkload modifier ‘M’ at the partclass level and part level.
4. Bulk load the partclass in Add/Modify/Delete mode by specifying them in the Excel
files category of the bulkload tool.

Read me First -- Smart 3D .Net Plant symbols 12

For Conduit parts

1. The Symbol Definition provided in the highlighted box below must be replaced.
Below is an existing part that refers to a Best Practice COM symbol.

2. The part should be updated with the corresponding .NET symbol.

Below is the updated part that refers to a .NET symbol.

3. Specify the bulkload modifier ‘M’ at the partclass level and part level.
4. Bulk load the partclass in Add/Modify/Delete mode by specifying them in the Excel
files category of the bulkload tool.

Read me First -- Smart 3D .Net Plant symbols 13

.NET Symbols on a new Project
The .NET Symbols and data in the zip files can be used for new catalogs and their corresponding
models without any issues.
If you are still not sure, open an SR.

Read me First -- Smart 3D .Net Plant symbols 14