Smart 3D Setup and Administration Practice Labs 2016 PDF

Intergraph Smart 3D™
Setup and Administration Practice Labs
Version 2016
Wednesday, January 18, 2017

TSP3D-TP-10011A
Copyright
Copyright © 2009-2012 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.
Portions of this software are owned by Spatial Corp. © 1986-2015. All Rights Reserved.
Portions of the user interface are copyright © 2012-2015 Telerik AD.
U.S. Government Restricted Rights Legend

Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was
developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with
subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal
Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the
United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished - rights reserved under the copyright laws of the United States.
Intergraph Corporation
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.
Intergraph Smart 3D™ Setup and Administration Practice Labs 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, PDS, SmartPlant, FrameWorks, I-Sketch, SmartMarine, IntelliShip, ISOGEN, SmartSketch,
SPOOLGEN, SupportManager, SupportModeler, Sapphire, and Intergraph Smart are trademarks or registered trademarks of
Intergraph Corporation or its subsidiaries in the United States and other countries. Hexagon and the Hexagon logo are registered
trademarks of Hexagon AB or its subsidiaries. Microsoft and Windows are registered trademarks of Microsoft Corporation. ACIS is a
registered trademark of SPATIAL TECHNOLOGY, INC. Infragistics, Presentation Layer Framework, ActiveTreeView Ctrl,
ProtoViewCtl, ActiveThreed Ctrl, ActiveListBar Ctrl, ActiveSplitter, ActiveToolbars Ctrl, ActiveToolbars Plus Ctrl, and ProtoView are
trademarks of Infragistics, Inc. Incorporates portions of 2D DCM, 3D DCM, and HLM by Siemens Product Lifecycle Management
Software III (GB) Ltd. All rights reserved. Gigasoft is a registered trademark, and ProEssentials a trademark of Gigasoft, Inc.
VideoSoft and VXFlexGrid are either registered trademarks or trademarks of ComponentOne LLC 1991-2013, All rights reserved.
Oracle, JD Edwards, PeopleSoft, and Retek are registered trademarks of Oracle Corporation and/or its affiliates. Tribon is a
trademark of AVEVA Group plc. Alma and act/cut are trademarks of the Alma company. Other brands and product names are
trademarks of their respective owners.

Contents
LAB 1: Domain, Server, and Client Setup ................................................................................................. 6
LAB 2: Create new site, catalog, and model ........................................................................................... 11
LAB 3: Create permission groups and assign permissions ................................................................. 22
LAB 4: Simple Backup .............................................................................................................................. 33
LAB 5: Restoring a Model Database (Option 1)...................................................................................... 37
LAB 8: Deleting a Model ........................................................................................................................... 52
LAB 9: Deleting a Catalog......................................................................................................................... 54
LAB 10: New Catalog Command .............................................................................................................. 57
LAB 11: Manual Creation of System Hierarchy ...................................................................................... 61
LAB 12: Import Creation of System Hierarchy ....................................................................................... 66
LAB 13: Assign Specifications to Systems ............................................................................................ 68
LAB 14: Restore as copy Training Model ............................................................................................... 73
LAB 15: Workspace Simplification by Role ............................................................................................ 75
LAB 16: Set Default Color Configuration for Fluid Code ...................................................................... 80
LAB 17: Prepare the session for Model Data Reuse command............................................................ 93
LAB 18: Model Data Reuse – Copy in Existing Model ......................................................................... 100
LAB 19: Model Data Reuse -Troubleshooting ...................................................................................... 112
LAB 20: Model Data Reuse – Copy to New Model ............................................................................... 123
LAB 21: Model Data Transform .............................................................................................................. 160
LAB 22: Synchronize Model with Catalog and View Generation ........................................................ 173
LAB 23: Database Maintenance ............................................................................................................. 178

Contents
LAB 24: Database Integrity ..................................................................................................................... 182
LAB 25: Error log files............................................................................................................................. 191
LAB 26: Interference Checking .............................................................................................................. 194
LAB 27: Export ZVF and XML files to be used in R3D referencing .................................................... 215
LAB 28: Attach external 3D data as a reference (R3D) ........................................................................ 219
LAB 29: Perform transformation (rotation, scaling, and translation) to R3D models. ..................... 224
LAB 30: Update attached R3D models .................................................................................................. 228
LAB 31: Export VUE and MDB2 files to be used for R3D Referencing .............................................. 235
LAB 32: Convert DGN to ZVF and Create Folder Hierarchy for R3D Models
(Optional) .................................................................................................................................................. 241
LAB 33: Use R3D referenced models for Parallel Design (Optional) ................................................. 245
LAB 34: Install Intergraph Batch Services ............................................................................................ 253
LAB 35: Configure Intergraph Batch Services ..................................................................................... 257
LAB 36: Submitting a job to a batch server .......................................................................................... 266
LAB 37: Adding User Defined Attribute to Smart 3D Database .......................................................... 270
LAB 38: Adding Approval Status in Smart 3D ...................................................................................... 275

LAB 1: Domain, Server, and Client Setup
Objectives
After completing this lab, you will be able to:
 Create Smart 3D users and groups in Windows
Before Starting
The practices performed in this guide will make changes to the training model that will leave it in
a state not suitable for the continuation of other lab practices. It is strongly encouraged to
discard databases used during this class and restore fresh copies for future practices.
Create Users and Groups in Windows

In class you will do this locally on the training workstation. At the office, users and groups are
created at the Domain level.
1. Open Control Panel > Administrative Tools > Computer Management> Local Users and
Groups.
2. Create the following users, set password to be same as username: pipe1, pipe2,
struct1, struct2, elect1, hvac1, equip1 (uncheck option- "User must change password at
next logon").
Note: If an error message regarding policy requirements for the password appears on
screen, then use a password that matches settings of the local or domain policy.
3. Create new groups named Pipe, Structure, S3Dusers, S3Dadmins, ProjectA.
4. Assign users to groups as follows:
Group Users
Pipe pipe1, pipe2
Structure struct1, struct2
S3Dusers pipe1, pipe2, struct1, struct2, equip1, hvac1, elect1
S3Dadmins pipe1, struct1, administrator
ProjectA pipe1, struct1
Verify MSDTC Settings for the Workstation

In class, a functioning database system may already be provided. Proceed to install and
configure required pre-requisite software, following the installation guide provided with
the Smart 3D CD (this step may have been completed with the assistance of the

instructor). The training workstation will be acting as a database server, reference data server,
name generator, and administrator workstation.
At the office, MSDTC must be configured on the Name Generator as follows:
Go to: Control Panel > Administrative Tools > Component Services > Computers > My
Computer > Distributed Transaction Coordinator > Local DTC > right click and select Properties
> Security tab.
On an entirely stand-alone machine this may not be required for Smart 3D to function.
If the Windows Firewall is enabled, you must set proper exceptions as outlined in
InstallationGuide.pdf document delivered with the software.
Close the component services window and any other windows.
Assign permissions in the file system

5. Using Windows Explorer, navigate to the directory where the SharedContent folder is
located.

Example: C:\Program Files (86)\Smart3D\3DRefData\SharedContent
6. From the Tools menu in the Explorer window, select Folder Options.
Note: Press the ALT key to make the menu bar appear.

7. On the View tab, ensure Use Sharing Wizard option is unchecked.
8. Click OK.
9. Right mouse click on the SharedContent folder, then select Properties.
10. Select the Sharing tab, then click on Advanced Sharing. Click Share this folder option;
then click Permissions.
11. Add permissions such that SP3DUsers group (created on Lab1) have Full Control access.
12. Click OK until returned to the SharedContent folder Properties page.

13. Go to the Security tab and modify security permissions to add SP3DUsers group with Full
Control.
14. Click OK then Close.

LAB 2: Create new site, catalog, and
model
Objectives
 Create a new site for a Smart 3D project
 Create a new Catalog inside the site created above using the delivered database template
 Create a new Model in the site created above from Project Management
Create New Site and Catalog Databases

1. Select Start > All Programs > Intergraph Smart 3D > Database Tools > Database
Wizard.

LAB 2: Create new site, catalog, and model
2. Select Create a new site. Click Next.
3. Select Database type as appropriate for your classroom setup (MSSQL/Oracle).
4. From the Site database server drop down list, select your server name (which will be
your machine name when working in a stand-alone) for the site database server.
5. Enter Admin_SDB as the Site database name.
6. Enter HSV (or any other alphanumeric string) as the Site database workshare
location.
7. Enter 1 as Name rule ID.
8. Type in a Name generator server for site. This identifies the machine where the
Name Generator Service (NGS) COM+ application has been installed. In a stand-
alone setup this will be the machine name of the computer you are working on.
9. Click "…" in the option Template file to be used to create site schema. Select
[Reference Data Install Directory]\Database Templates\MaterialHandling\AppRepos.dat.

i.e.: C:\Program
Files(86)\Smart3D\3DRefData\DatabaseTemplates\MaterialHandling\Apprepos.dat
(AppRepos.DMP if Oracle)
10. Click Next.

Screenshot above is assuming an MSSQL configuration. The principal
difference with an Oracle configuration is the "Template file to be used to create site
schema" path. For an MSSQL project, the path for the Apprepos.dat template is as it
would be when read from the Server machine (direct path, not UNC). For Oracle, UNC
path must be used.

11. Select Restore catalog from backup.
12. Select server name for Catalog database server.

13. Enter Admin_CDB for Catalog database name.
14. Provide the UNC path for the SharedContent folder.
Type in \\servername\SharedContent (see file:///\\\\servername\\sharedcontent -
file:///\\\\servername\\sharedcontent). \\servername is the name of the computer where the
Smart 3D Reference Data software was installed. In a standalone configuration you may
use the local path [Reference Data Install Directory] \SharedContent
15. Click "…" in the option Template file to be used to create catalog database and
schema, select [Reference Data Install
Directory]\DatabaseTemplates\MaterialHandling\MHE_CatalogDB.dat
i.e.: C:\Program Files (86x)\Smart
3D\3DRefData\DatabaseTemplates\MaterialHandling\MHE_CatalogDB.dat

(MHE_CatalogDB.DMP if Oracle)
Screenshot above is assuming an MSSQL configuration, principal difference with an

Oracle configuration is the "Template file to be used to create catalog database and
schema" path. For an MSSQL project, the path for the CatalogDB.dat template is as it
would be when read from the Server machine (direct path, not UNC). For Oracle, UNC
path must be used.

16. Click Next.
17. Click Next.
18. After process is complete, click Finish.

19. Review log file DbwRestoredXXXXX.log in your temp folder. You may type %temp% in
the address bar of Windows Explorer for quick access.
20. Note: The last 5 characters of the restore log file name will change depending upon
different databases being restored.
Shown log file will be different for Oracle database configurations.
Verify New Site Creation

21. Select Start >All Programs > Intergraph Smart 3D > Database Tools > Modify Database
and Schema Location.
22. The form will display the location of the Site and Site_Schema databases.
This connection information can be manually edited on Smart 3D workstations to

allow for connection to this Site database and the Models that it will contain.
23. Click OK.

Create New Model

24. Select Start > All Programs > Intergraph Smart 3D > Project Management.
25. From the Database menu, select New > Model…

26. Fill in the General tab of the New Model dialog. Choose Material Handling from Model
Type drop down.
27. Complete the Databases tab as follows. Complete each row to provide information for
Catalog, Model, and Reports databases. Remember to identify the Name Generator machine
as it was previously done for the Site Database on the Database Wizard form.

28. Click OK to create the model and then review the results when completed.
29. Review the Project Management hierarchy and observe the change for the Catalog icon.
This is the result of the Catalog being associated to at least one model. Before, it was
unassigned.


LAB 3: Create permission groups and
assign permissions
Objectives
 Create permission groups and assign permissions to Smart 3D Catalog and Model in
Project Management
 Assign permissions to the Symbols folder for various SP3D users
Create Permission Groups

1. If required, select Start > All Programs > Intergraph Smart 3D > Project
Management.

LAB 3: Create permission groups and assign permissions
2. Right-click on Admin_Model and select New Permission Group Folder…
You may also access this functionality by clicking on the "New permission group
folder" icon, located on the ribbon bar.
3. Name the folder Design. Select OK.
4. Expand the Model hierarchy by clicking on the + box to the left of Admin_Model.

5. Select the folder Design.
6. Right-click on Design and select New Permission Group...

You may also access this functionality by clicking on the "New permission group"
icon, located on the ribbon bar.
7. Name the group Piping.
8. Click OK.

9. Create another permission group and name it Structure.
10. Similarly, create the following hierarchy of permission group folder WBS and permission
groups As-Built and ProjectA.
Assign Permission in Project Management

11. Select permission group Piping.

12. Right-click and select Permissions.
13. Click Add… button.

This form can be operated in two modes determined by the checkbox "Only allow
names from trusted domains". If you want the form to verify the existence of the user or
group on Active Directory, leave the check box selected. If you want to add the user or
group without domain verification, leave the box unchecked. Make this decision before
keying in user names in the User block. An example of when to uncheck this box while
working in a non Global Workshare Configuration would be to pre-assign permissions to
users of a contractor company to which the project will be given and where there is no
communication or trust with the contractor’s company Active Directory.
14. Click Add… button.
15. Use the standard user/group form for Windows to identify by domain\name the user or
group you wish to add. In our case we will be selecting the group Pipe from the local computer.
16. Click OK.

17. Expand Type of access drop down list to change permission as Write access.
18. Click OK and review the Access Permissions form.
19. Click Add… button to return to the Add Users and Groups form. This time a user will be
added without verifying its existence on the domain or Active Directory.

20. Uncheck the box Only allow names from trusted domains.
21. In the User field, type in the Structure Windows local group in the form of Domain\User.
For this example, that would be sp3dsuptng\Structure, adjust accordingly for your case.
22. Set Type of Access to Read.
23. Click OK.

24. Review Access Permissions form.
25. Click OK.

26. Select the Permission Group Structure.
27. Right click and select Permissions.

28. Select Add and choose the option you prefer (domain verification on/off).
29. Select Add to add Windows groups Pipe and Structure.

30. Assign Write permissions to ‘Structure’ and Read permissions to ‘Pipe’ Windows groups.
31. Click OK.
32. Click OK.

33. Select permission group ProjectA and assign Write permissions to the windows user
group ProjectA.
34. Click OK.

LAB 4: Simple Backup
Objectives
 Create a backup of the Site, Catalog and Model from Project Management
1. Start Project Management if not already open.
2. From the Tools menu, select Backup.
3. In the Backup form, use Calculate Size button to determine the size of the backup.

For Oracle based projects, this calculation can take several minutes.
4. Click button ‘…’ on Select folder and name for backup configuration file field. Create a
folder on a drive that has sufficient space to hold the backup. Name the folder S3DBackups.

5. Click Save.
6. Return to the Backup form and use the browse button on Select server and folder for the
site, catalog and model... option to determine a location to store database file backups. If
possible, try to place the .bcf and the database files together during the backup procedure.
For Oracle based projects you must specify a folder that is shared (UNC path).
7. Click OK and allow the backup to complete.

8. Review Backup log report (errors will appear in the backup log file if there is insufficient
disk space).
9. Close log file.

10. Click X button on the top right or the Cancel button on the Backup form to return to Project
Management.
For Oracle based projects, the Backup log file will look different than the screenshot
above.

LAB 5: Restoring a Model Database
(Option 1)
Objectives
 Restore a model from backup using "Restore one or more model databases from backup"
option from Project Management
Option 1 is "Restore one or more model databases from backup". The intent of
this is to restore a Model that already exists (or has pointers) in the current Site Database.
This would generally happen when the production model has a need to be rolled back to a
previous date or immediately after restoring a backup of the Site Database onto a new
server. In the latter case, only the pointer in the Site would be present and we would want
to follow that action by restoring the Model and Catalog onto that server as well.
1. Start Project Management, if not already open.
2. From the Tools menu, select Restore…
3. Choose the option Restore one or more model databases from backup. This will restore
OVER THE EXISTING model database and it will only work if the model already exists in the

LAB 5: Restoring a Model Database (Option 1)
Site and Site_Schema databases (model must be listed under the Models node in Project
Management hierarchy).
4. Click Next.
5. Complete the form as depicted below by identifying the backup configuration file (*.bcf),
Backup file path, Catalog and Model names/locations, and Symbols share path:

For Oracle based projects, ‘Database Backup Files Path’ must be a shared location.
6. Click Finish.
7. Because the Catalog database already exists on the server, you have two options in this
restore mode. You can either leave the existing Catalog in place (linking it) or overwrite it from
the backup. Because there have not been any changes to the Catalog, the logical choice would
be to select yes and leave the existing Catalog intact.
8. Click Yes.

9. An additional warning message will be displayed.
10. Click the Close button (we will not be required to run Synchronization at this time because
the Catalog has not changed).
11. An Additional confirmation form will be displayed because you are overwriting the Model
Database.
12. Click Yes.

13. When the restore is complete, click OK and review the log file. Because we only restored
the model, the log file will only contain information regarding the model restoration and not the
catalog. Click Close on the Restore form to return to Project Management.
14. Repeat the process described in steps 1-13 but this time, choose to restore over the
Catalog Database.

(Option 2)
Objectives
 Restore a model from backup using Restore model for selective recovery of model
objects option from Project Management
Restore Option 2 is Restore model for selective recovery of model objects. The
intent with this option is to restore a Model database into a Site database where a current
version of the model already exists. The restored Model (which would represent old data)
would exist in the Site database in parallel to the current Model and would share the same
Catalog. Users could then open two sessions, one pointed to the restored Model and one
pointed to the current Model, and select items from the restored model to Copy and then
"Paste/Restore" into the current model. Doing this type of workflow allows for selective
recovery of work from previous versions of the same model.
2. From the Tools menu select Restore…

3. Select the second option Restore model for selective recovery of model objects.
4. Click Next.

5. Complete the form as depicted below by identifying the backup configuration file (*.bcf),
Backup Files Path, and Catalog and Model names/location.
Note: The New model name contains the current date. Provide a description that is
meaningful to you.
6. Click Finish.
7. Indicate that you would like to link to the existing Catalog by selecting Yes.

8. Click OK. Once again, you may want to review the restore log file:
For Oracle based projects, the restore log file will look different than the screenshot
above.
9. Close Restore Wizard form.

10. Review Project Management Tree and observe that there now exists two models that
share the same Catalog.
11. Right mouse click on the newly restored model and select Regenerate Report database.

12. Click OK and allow reports databases to be re-created.
13. Click OK to dismiss dialog box.

14. Typically, you would follow this type of operation by restricting access to permission groups
in the restored Model. As an exercise, use the skills you have learned to set user access to
read for all groups and users except yourself on the Restored Model.
15. The database can now be used for recovery of objects operations, had this been a live
project.
The workflow to recover objects from a previous backup of the model may involve
one of two methods; first there is "Copy/Paste Restore" procedure between two sessions, or
the use of Model Data Reuse command found in Project Management.

(Option 3)
Objectives
 Restore a model from backup using "Restore model as a copy" option from Project
Management
Option 3 is represented by the restore option Restore model as a copy. This
option is generally used to restore a model that does not exist in the current Site database
set or to duplicate a Model (by use of a backup) in the same Site database set. Unlike
restore option 1, Option 3 does not require an instance of the same Model to exist in the Site
database.
2. From the Tools menu, select Restore.

3. Select the option to Restore model as a copy.
4. Click Next.
Your instructor will provide the location of the training model that includes the *.bcf
file and backup files before you continue on to step 5.
5. The selections in this form are similar to restore options 1 and 2. Complete the form as
shown below by keying in a New Model name, locating the .bcf and backup files, choosing
the Catalog name, and the Model name.

6. Click Finish.
You will not be prompted to link to the existing catalog database (as this is a
separate unique catalog) and you will not be prompted to restore over an existing model (as
one does not yet exist on the server).
7. When databases have been restored, click OK.
8. Review the log file to verify the restore operation’s integrity.
9. Close the restore form when completed.

10. Note there are two catalogs and three models. The question mark next to S3DTrain
model is an indication that the Reports databases have not been regenerated.
11. Right mouse click on the SP3DTrain model and select Regenerate Reports Databases.
12. Click OK.

13. Click OK.

LAB 8: Deleting a Model
Objectives
 Delete an existing model from Project Management
1. Start Project Management if not already open.
2. Right mouse click on the SP3DTrain model and select Delete.
3. Deleting the model will effectively remove its pointer from the Site database. Click Yes.

LAB 8: Deleting a Model
4. Select Yes on next form to delete physical database files. This allows release of hard
drive space on the database server.
5. Note the Model has been removed from the hierarchy but the Catalog still remains.
6. Delete the model that was restored using option Restore model for selective recovery of
model objects.
S3DTrain_CDB database still remains. Possible actions for it include deletion as it

is no longer associated to any model, or it can be reused with a new model by running
Database > New > Model... command.

LAB 9: Deleting a Catalog
Objectives
 Delete an existing catalog from Project Management
1. Catalog databases can only be deleted if there are no models associated with them.
Catalogs ready for deletion can be recognized by a yellow mini book icon in the Project
Management hierarchy.
2. Right click on SP3DTrain_CDB Catalog and select Delete.
3. As with deleting models, the software will prompt for confirmation. Select Yes.

4. Select Yes.
5. Try to delete the Catalog database named Admin_CDB and note the results.
For Oracle based projects:
When you delete an Oracle model in Project Management task, the software may not
delete all of the associated database objects (user, tablespace and schema). To delete
schema information after deleting an Oracle model, you must use the Oracle Database
Tools Wizard for Smart 3D.
The Oracle Database Tools Wizard for Smart 3D is delivered to [Product
Directory]\ProjectMgmt\Tools\Bin\SP3DOracleDBToolsWizard.exe.
 Open the Oracle Database Tools Wizard for Smart 3D.

 On the Introduction page, select Delete Schema and its associated tablespaces, and
then click Next.
 Select the schemas to delete and click Finish.

This process may take some time to complete (approximately from 5 to 10 minutes
per database), depending on the quantity of databases to process and performance/load
factors of the server. The Wizard window may at times look like it is hung, but do not kill it.
Wait for it to complete. It will return to normal with a message announcing completion.

LAB 10: New Catalog Command
Objectives
 Create a new Catalog from within Project Management
 The new catalog command allows you to create a new empty catalog without
performing a restore command. You will then be able to bulkload to this database at
will, but you cannot use the catalog task to change anything in it unless you also make a
Model based off of the newly created catalog.
 In a Global Workshare configuration, this command is only available for use at the Host
location.
1. Open Project Management. Select Database > New > Catalog command.

2. The new catalog form will appear. Select the server where the catalog will be restored on.
Note that some information may be filled in for you, if possible. If Apprepos.dat template is
not at the suggested location, or you wish to use another custom starting template, you can
specify it in the template options section.
3. From Catalog database server list, select or make sure the proper database server is
selected.
4. From Catalog database name drop-down list, select <new database>, and then type over
as new name New_Catalog_CDB. You can also just place the cursor in the field and start
typing the new name.

5. Select option Create a new catalog from a template and locate MHE_CatalogDB.dat
(CatalogDB.dmp if Oracle) template, also type in the symbols folder path.
6. When the form has been completed, click OK.

Apprepos.dat is the template you would use to create an empty Catalog. An empty
Catalog is defined as a catalog database that contains all of the necessary tables, stored
procedures, views, objects and so on, but does not contain any modeling data, such as part
data or specifications. Only use this template with the first option.

7. Project Management hierarchy should resemble the following:

LAB 11: Manual Creation of System
Hierarchy
Objectives
 Create a systems hierarchy in a new model from the Systems and Specifications task
1. Go to Start > All Programs > Intergraph Smart 3D > Database Tools >Modify
Database And Schema Location to set the Site database to Admin_SDB.
2. Open Smart 3D. When prompted, select Plant tab and select either English or Metric
Units template.
3. Go to File > Define Workspace.
4. From the model drop down list, select Admin_Model and on the filter drop down list
click More… to create a filter.

LAB 11: Manual Creation of System Hierarchy
5. Highlight Plant Filters node and click New Filter button at the top of the form.
6. In the form that opens up, type All as filter name.

7. In System tab, highlight Admin_Model, and click OK to the form.

8. Select the newly created filter All and click OK.
9. Click OK on Define Workspace form.

10. Go to menu Tasks > Systems and Specifications.
11. Change the Active Permission Group to Permission Group1.
12. Right click on Admin_Model root level and select New System >New Area System.

13. Name the new area A1. Click OK.

14. Right click Admin_Model root level and select New System > New Area System.
15. Name the new area A2. Click OK on the form.
16. Right click on area A2 and select New System > New Unit System to create unit U01.
Click OK on the form.
17. Right click on unit U01 and select New System >New Electrical System. Use
properties page dialog to name the new system to Electrical. Click OK on the form.
18. Likewise create the following systems in U01:
For “Piping”, create a new Piping System.

19. Right click on Structural system and select Properties.
20. On the Configuration tab, set Permission Group = Structure, click OK.
21. Assign Piping system to its own permission group.
22. Right click on unit U01 and select Select Nested.
23. From the main menu select Edit > Copy (not from right click).
24. Right click on A2 and select Paste. Ensure Paste dialog shows A2 under Selection.
25. Select option Keep original permission groups and click OK.
26. Rename the new unit from U01(2) to U02 by going to the Properties.

27. Repeat the unit Paste and rename procedure to create units U03-U05.

LAB 12: Import Creation of System
Hierarchy
Objectives
 Create a systems hierarchy in a new model using an Excel spreadsheet
1. Copy the sample system import workbook "ImportData_Sample.xls" from the delivery
location to a different folder.
The software delivers two sample Excel files, ImportData_Sample.xls and
Pipelines_Sample.xls to [Product Directory]\SystemsAndSpecs\Import as part of default
client setup.
2. Open workbook ImportData_Sample.xls then go to worksheet SYSTEM_HIERARCHY.

3. Edit system names in this workbook to values that might better meet needs at your
company. At a minimum, delete systems that may not apply to your industry.
4. In Air System worksheet note the pipeline systems already defined (AS001, AS002…).
5. Save the workbook and close Excel.
This is not a Bulkload workbook, so there’s no need for A/M/D modifier on column
A.
6. Open Smart 3D if not already open.
7. Define a workspace and select the All filter created in a previous lab practice.
8. Go to the Systems and Specifications task and select Tools > Import Systems
Hierarchy from Excel…
9. Click Add and locate the folder where ImportData_Sample.xls workbook was saved.
10. Accept default option Create a system hierarchy option and proceed to click Import.

LAB 12: Import Creation of System Hierarchy
11. Click Finish to close the Import dialog box when the command has finished (see status bar
of the form).
12. Review the system hierarchy. The new systems should appear in their assigned position.
The piping system named Air System should be populated with 4 pipelines ready to use.
13. Use system properties dialog to review system ownership (permission group) and correct
as needed. This ownership was defined by the active permission group in use during the import
command execution (drop down in the top left corner).
The example hierarchy included in ImportData_Sample.xls workbook was created for
a Marine type of project. Hull and Outfitting are marine terms, but this should not affect
applicability with Smart 3D in Materials Handling mode.

LAB 13: Assign Specifications to
Systems
Objectives
 Designate allowed specifications for multiple disciplines in the model
2. Define a workspace and select the All filter created in a previous lab practice.
3. Go to Systems and Specifications task.
4. Click on the root level of the model, e.g. Admin_Model.
5. Select Define Allowed Specifications button to the left of the Help button (question
mark).
6. Select Add All to allow all specifications/All disciplines at the root level and click OK.

LAB 13: Assign Specifications to Systems
7. Expand A2 > U02 > and select the Piping system, use Define Allowed Specifications
command to restrict (<<Remove) the use of piping specifications to only show N0,
1C0031 and 2C0032 for this piping system folder. Click OK.
8. Go to unit U01 > Piping and use the same command to restrict (<<Remove) the use of
piping specs to only show 1C0101, 1S3984 and 4C0033 for this piping system.
9. Perform this procedure on the Electrical system on U03 and leave only CB-S1-L6-12B
and Cws-0 Cableway specs.
10. Go to one of the Pipeline systems created by import from Excel (AS001, AS002, AS003,
etc) and attempt to restrict the usage to piping specs 1C0031 and 2C0032, note what
happens.
11. Switch to Piping task and set the locate filter to ALL. Create a new pipeline system
from the workspace explorer under Piping system of unit U02 as shown in the figure
below.

12. Select Tasks > Piping. Select the Route Pipe command.
13. Click on any point in the screen. The New Pipe Run form will display.
14. Click in the Pipeline field. It will turn into a drop down list. Select More.
15. In the Select System dialog that opens, expand the hierarchy to select the recently created
Pipeline. It should be located under Admin_Model > A2 > U02 > Piping.
16. Click OK.

17. Back in the New Pipe Run form, notice that you should only have available for use the
three specifications previously allowed in the Systems and Specifications task.
18. To route the pipe, select specification 1C0031, 6 in Nominal Diameter, switch to the
Temperature and Pressure option in the Category drop down list and type value 1 for Design
Maximum Temperature and 1 for Design Maximum Pressure. Click OK in the form.

19. Wait for the preview of the pipe to display, then click a second time after it has been
stretched over the screen when ready to place it.
20. Right click terminates the command.

LAB 14: Restore as copy Training Model
Objectives
 Restore a copy of the training model that will be used for Model Data Reuse practice
1. Start Project Management.
2. Use Restore model as a copy command (restore option 3) that was covered earlier.
Locate the training model backup and fill the form to complete the restore process.
When the restore finishes, regenerate reports databases.

LAB 14: Restore as copy Training Model
3. When done, Project Management should resemble the following:
You may delete catalog database named New_Catalog_CDB if desired as it will not
be needed anymore.

LAB 15: Workspace Simplification by
Role
Objective
By the end of this session, you will be able to:
 Exclude certain object types based on a user's role
Overview
Define Workspace supports the use of user-defined roles to further refine the filtering of objects
displayed in the workspace. In the model, this will help to simplify the workspace by excluding
objects that are not related to your role.
With the option of user-defined roles, you will see a new field labeled Role. This new option
allows users to exclude objects that are not important to their task. For example, if I am a
piping designer and I select the Piping Designer (Aboveground) role, it will exclude structural
objects other than parts. If I’m a structural designer, selecting the Structural Designer role
will exclude piping objects other than parts. By excluding these objects from the workspace, a
user will see a noticeable reduction in the number of objects brought into the session and the
time it takes to complete workspace definition.
Steps
1. Open a Smart 3D session.
2. Click the File menu and select the Define Workspace... command. In the Model field,
select SP3DTrain.
3. In the Filter, select the More... option.

LAB 15: Workspace Simplification by Role
4. From the Training Filters, select U02 and click OK on both dialog boxes to start the
workspace definition.

5. This filter will add about 1100 objects to the workspace.
6.
7. From a Windows Explorer window, go to [\\server\SharedContent]\Xml directory.

8. Locate the file name OptimizationForRole.xml.
9. By default, the sample file for model has been used. If you want to use the Marine
sample, just rename it as OptimizationForRole.xml.
10. Within Smart 3D, go back to File > Define Workspace...
In the Role field, select Piping Designer (Aboveground) and click OK.
11. Set the locate Filter to All.

12. Hover your mouse over a piping object and wait for the quick pick to appear. Notice
that different piping objects, such as parts, features, runs, etc are available for selection.
13. Go back to File > Define Workspace... Change role to Structural Designer to load the
objects into the workspace. There are about 703 objects that are loaded.
14. Hover the mouse over a structural beam and notice the Quick Pick list for that
structural object is available.

15. Select a piping feature and notice that the only object available is a piping part.
16. Exit Smart 3D.

LAB 16: Set Default Color Configuration
for Fluid Code
Objective:
By the end of the session you will be able to:
 Import Default Color configuration
 Set Default Color Configuration for Piping Objects based on Fluid Code
 Export Default Color Configuration
1. Open a new Smart 3D session and define your workspace with objects from Plant
Filters > Training Filters > U02 & U03.
2. Check the color of Piping objects.
3. Open Project Management.

LAB 16: Set Default Color Configuration for Fluid Code
4. Select the root of SP3DTrain from Models hierarchy.
5. Go to Tools > Project Settings > Configure Default Colors.
6. In Default Color Configuration window click on the first row and press Ctrl+A to select
all rows.
7. Click on Delete command to delete all the colors used on SP3DTrain model.
8. Click on the Save command to save the changes done on the model and close the
window.

9. Open a new Smart 3D session and define your workspace with objects from Plant
Filters > Training Filters > U02 & U03.
10. Check the color represented by all objects.
11. Open Project Management if not already opened.

12. Select SP3DTrain model and go to Tools > Project Settings > Import...
13. Select DefaultSymbologyRules.xml file from \\ServerName\SharedContent\Xml using

Browse on Import Project Settings dialog and click OK.
Note: The command is expecting the text and XML file to be present at the same path.
Review imported rules under the Configure Default Colors section. Default Colors XML

and TXT files are delivered in the SharedContent folder.

(\\ServerName\SharedContent\Xml\DefaultSymbologyRules.XML)
14. Select SP3DTrain model root and go to Tools > Project Settings > Apply Default
Colors.

15. Project Management shows confirmation at the bottom as show below:
16. Open a new Smart 3D session and define your workspace with objects from Plant Filters
> Training Filters > U02 & U03. Check the color changes on objects after Import.

Set Default Color for Fluid Code:

1. In the Default Color Configuration window, click on the Insert Row command to add a
new rule.
2. Click the Object Type field to obtain access to the object type hierarchy.
3. Select Piping > Piping Parts > Pipes as object type.
4. Select Green color using Drop down list under Style (Color).

5. Click on the Criteria field. Criteria allows the user to define a filter to select certain objects.
In this case we will use the 'Fluid Code' as the criteria. In the next few steps you will create a
filter based on the Fluid Code.
6. Use the following criteria as guidance to define the property filter:

a. Object Type used as the basis for property identification = Piping > Piping Parts >
Pipes
b. Relationship = Pipeline to Piping parts
c. Related object type = Systems > Pipelines
d. Display properties in this category = Standard
e. Fluid Type

7. Click OK, select the = operator and P, Process as the value, click OK.
8. Save the changes in the Default Color Configuration window.
9. To see the new rule added in the proper section re-open Default Color Configuration
window selecting Tools > Project Settings > Configure Default Colors on the root level of the
SP3DTrain model.
10. Expand the Piping section and observe that there are two rules for Pipes.
11. Highlight the new rule created for FluidCode=P.

12. Click on the Move up command until the new rule moves one row above the Default Pipes
rule and click on the Save command to save changes.
13. Select SP3DTrain model root and go to Tools > Project Settings > Apply Default
Colors.
14. Project Management shows confirmation at the bottom as shown below:

15. Open a new Smart 3D session and define your workspace with objects from Plant Filters
> Training Filters > U02 & U03. Check the color they are represented with.
Set Default Color based on specific Role:

1. Open Project Management, if not already open.
2. Go to Tools > Project Settings > Configure Default Colors.
3. Expand the Piping discipline and expand the Pipes rule created in earlier section.
4. Select the option Click here to add new item.

5. From the dropdown list, choose Piping and color Yellow.
6. Click on the next field or hit the Enter key to finish creating the role assignment.
7. Click on Save command to save the changes.

8. Open a new session, use the filter from Plant Filters > Training Filters > U02 & U03 and
role as Piping Designer (Aboveground).
9. Check the color of Piping parts with Process.

10. Open a new session, use the filter from Training Filters > U02 & U03 and role as None.
Export Default Color Settings:

2. Select SP3DTrain model.
3. Go to Tools > Project Settings > Export.
4. Provide a path and name for the output of the files, then click OK.

5. The generated files are comprised of a text and an XML file. Both files are required during
the import operation.
Note: The software expects the files to be in the same folder during the Import Project
Settings operation.

LAB 17: Prepare the session for Model
Data Reuse command
Objectives
 Create session files and prepare the environment with system nodes that will be used with
Model Data Reuse command
Set Default Colors for the Admin_Model

1. Select Admin_model and go to Tools > Project Settings > Import...
2. Select DefaultSymbologyRules.xml file from \\ServerName\SharedContent\Xml using

Browse on Import Project Settings dialog and click OK.
3. Select Admin_Model root and go to Tools > Project Settings > Apply Default Colors.
4. Close Project Management.
Create Session Files for Admin_Model and SP3DTrain

2. Select English or Metric units template in the “Plant” tab.

LAB 17: Prepare the session for Model Data Reuse command
3. Define a Workspace on model SP3DTrain. Under Plant Filters node, expand the
folder “Training Filters” and use U04 filter.
4. Click OK to define workspace.
5. Use the Fit command to bring all objects into the view. This will be the data copied with
MDR.
6. Select the Common Views command from the ribbon bar (top right) to see the unit
in Isometric view.

7. Select Isometric view (select dot w/mouse) and re-fit the view.
8. Graphically or from the Workspace Explorer, select Equipment 40V-101.
9. Open its Properties Page .

10. Change the category from “Standard” to “Position and Orientation”. Note the original
values as reference for the copy.
11. Click Cancel.

12. Go to Tools > Run Report and select the “Catalog Reports” tab.
13. Run the following reports from the Structure and Piping folders in Reports >Types of
Reports:
Structure Linear Member Itemized Material Take-off
i. In the Filter Properties for Asking Filter select unit A2 >U04 and click
OK.

ii. Click Finish

Piping Material Take-Off
iii. Select the same unit, U04

iv. Do not specify a Baseline Report. Click Next.
v. Leave the Default Report Parameters. Click Finish

14. Review the reports.

15. On the Desktop, create folder MDR and save the reports as “Structure_PreMDR” and
“Piping_PreMDR”. Close the reports.
16. With the Locate Filter set to “All”, select the unit system U04 from the Workspace
Explorer.
17. Right click on this system and select “Select Nested”. Note the object count of the
highlighted objects.
18. Right click to deselect the unit.

19. In the Workspace Explorer, select and right-click on the model node SP3DTrain.
20. Select New System > New Area System.

21. Name the new system MDR_Dest.
22. Click OK.

23. Select File > Save to save the Smart 3D session as MDR_Copy in the Desktop > MDR
folder.
24. Go to File > New. Select No if asked to save the previous session file.
25. Select the English Units template in the “Plant” tab.
26. Select File > Define Workspace…
27. Set the model selection to Admin_Model.
28. In the Filter dropdown, select More…
29. Under Plant Filters folder, select All filter.
30. Click OK. Click OK.
31. In the Workspace Explorer, right-click on the model node “Admin_Model”.
32. Select New System > New Generic System.

33. Enter the name “MDR_Dest”. Click OK.
34. Save the session as MDR_Admin in the Desktop > MDR folder.
35. Close Smart 3D.

LAB 18: Model Data Reuse – Copy in
Existing Model
Objective
 Use Model Data Reuse command from Project Management to copy objects by using the
predefined filter within the model.
 Map permissions between the original and copied objects in the model.
1. Open Project Management if not already open.
There are two models in the Site. SP3DTrain contains the model objects that will be
used for this practice. Admin_Model is an empty model that will be used to copy objects
across models.
2. Start Model Data Reuse command from menu Tools > Model Data Reuse…
3. Select Begin New Operation and click Next.

LAB 18: Model Data Reuse – Copy in Existing Model
4. Name the operation MDR_Copy and click Next.
5. In the Source Model window, click Select Model, and choose SP3DTrain. This will be
the source, or ‘from’ model. Set the “Source object selection method” to Source
objects by filter. Click Next.
6. In the Source Objects by Filter page, expand the drop down list, and select More.

7. Select U04 filter from Training Filters node.
8. Click OK, then Next.

9. On the Disciplines page, you may select either all disciplines or select disciplines for
object data to be copied as required. Toggle the radio button from All disciplines to
Select disciplines, reselect All disciplines radio button. Click Next.
10. Next page displays the destination or ‘to’ model and system(s) where the objects will be
copied under. If chosen filter in previous step contains a common grandparent system,
then mapping has to be done for one or few systems only in contrast to the mapping
that has to be done for several objects that do not belong to a common parent system.
Sub-nodes of source system(s) will be automatically created under new mapped
system. Make sure destination model is set as SP3DTrain then click Next.

11. Click the browse button in Destination System Parent field from source system CS to
assign a new destination system. On Select Destination System form, select
MDR_Dest system and click OK.
12. Repeat procedure to map MDR_Dest to source system A2.

13. Back on the Destination systems page, expand Default Permission Group drop down
list. The system performs a check and only allows the user to assign copied items to
an existing Permission Group where privileges are sufficient. Maintain Admin group
selection.
14. Select Map button. This form allows the user to map same or new permissions to
copied objects based on availability of permission groups in destination model. By

default all objects will be assigned to default permission group which was ‘Admin’ per
previous window selection.
Since the copy operation is being performed within the model, selecting Keep Originals
option will let the software try automatic mapping of permission groups.
15. Click OK to dismiss Permissions Group Map form.

16. Select Next on the Destination page.
17. Select Move by relative distance radio button (if not selected by default). Expand
Units drop down list and select ft as default unit. Type in 100ft for East distance, 150ft
for North distance and 5ft for Up distance (equivalent to 100ft X, 150ft Y, 5ft Z).
18. Click Next.

19. Click Copy on the confirmation screen.

20. The system processes the command.
21. Notice now there is a stop radio button on the Model data reuse processing form. This
allows the user to stop the operation if needed. Stop the operation. It does not matter
when the operation is stopped just stop it before it completes.
22. Once the operation is stopped the Operation Properties dialog box appears. Review
the information then Click OK.

23. Start Model Data Reuse command again from Tools > Model Data Reuse.
24. Select Restart Existing Operation and click Next.
Notice the operation MDR_Move status is stopped because the user clicked stop on
the progress button. There are four possible statuses: Stopped which indicates the process
was terminated in an orderly way, Incomplete which indicates the process was
terminated abnormally, In Progress which indicates the operation is in progress, and
Completed which indicates the operation was completed successfully.
25. Select MDR_Move and click Next.
26. Click Copy on the confirmation page.

27. The operation should continue from where it left. Upon completion, the operation
properties dialog box displays again with the results of the copy. Notice the status
changes to Completed.
28. Review and click OK.

30. Open a Windows Explorer window.
31. Enter %temp% in the address field.
32. Locate the recently created “MDR#” text file.
33. Open this file and inspect the entries at the bottom. The “Results by Class” should
match the summary reported in the Project Management results GUI.
34. Copy and paste this log file in the Desktop > MDR folder. Close the log file.
35. Open the saved Smart 3D session MDR_Copy.
37. Make sure the model selection is SP3DTrain. In the Filter dropdown, select “Create
New Filter…” Enter the following:

Name: MDR_Copy
System: A2 > U04, CS > U04 CS and MDR_Dest
38. Click OK and Define Workspace with this new filter.
39. Fit the new workspace in the graphic view to visually verify the copy.

40. Expand the “MDR_Dest” folder in the Workspace Explorer.

41. Compare this with the original hierarchy.
42. Right click on the U04 Unit system underneath the “MDR_Dest” folder. Choose “Select
Nested” and verify that the object count is equal from step from Lab 17.
43. Select Tools > Run Report… and select the Catalog Reports tab.
44. Run the following reports from the Structure and Piping folders once again.
Structure Linear Member Itemized Material Take-off.
In the Filter Properties for Asking Filter select “U04” under the
“MDR_Dest” folder. Click OK.
Leave the default report parameters and click Finish. If asked to
overwrite a previous report, select Yes.

Piping Material Takeoff

a. Make the same filter selection as in the previous report.
b. Do not select a Baseline report, click Next.
c. Leave the default report parameters and click Finish. If asked to overwrite a
previous report, select Yes.
45. Briefly verify that the values reported from the copies are equal to the reports generated
from the original objects.
46. Close the reports.

LAB 19: Model Data Reuse -
Troubleshooting
Objectives
 Review results of the Model Data Reuse command for additional troubleshooting if certain
objects failed to be copied
Review MDR Results Utility

1. Select Tools > Utilities > Review MDR Results.
2. In the Review MDR Results dialog, expand the ellipses and browse for the “MDR###”
txt file copied to the Desktop > MDR folder.

LAB 19: Model Data Reuse -Troubleshooting
3. Open this file into the application. The “Design objects” list will be populated.
4. Select Report command at the bottom of the window.

5. Review and save the generated document in the Desktop > MDR folder.
6. Select the Filter command in the window.

7. Uncheck Design objects successfully copied and Design objects not attempted to
be copied. Click OK.

In this exercise, the failed object list will be empty, but this will be a powerful tool for
pin pointing failed objects in complex copy operations.
8. Select the Filter command in the window once again. Filter to display only the
following:
 Results: Design objects successfully copied
 Classes: Equipment system, Pipe run, Slab
9. Click OK. Run a report for this selection.
10. Close the reports.

11. Back in the Review MDR Results dialog, click on one of the entries in the Original
Name column and then click on the Select command.
12. Click on its respective Copy Name and click the Select command
13. Verify that:
 The entries are highlighted in the Review MDR Results window.
 The objects are highlighted in the Workspace Explorer.
 The objects can be brought into view with the Fit command.

14. Click on the Unselect command for each of these Names and close the Review MDR
Results window.
MDR Validation Custom Command

15. Go to Tools > Custom Commands…
16. Click on the Add command, and enter the following:
 Command Progid: MDRValidation.CValidateGeometry
 Command name: MDR Geometry Validation
17. Click OK.

18. Select Run.

19. Select the Model Data Reuse Log File method and browse for the MDR log file saved
in the Desktop > MDR folder.

20. Press the Generate Data for Validation button. Leave the Differences Only checkbox
selected.
21. When the notification Generated Data for Source and Destination Objects appears in
the main window’s message bar, press the Process Generated Data button.

22. When the notification Completed Processing the Generated Data appears in the main
window’s message bar, select the Review Results button.

23. Expand the Summary of Anomalies by selecting the Show Details button.

24. Select Setup Views button. The following views will be created.
25. Navigate between the found differences.

The differences reported through this custom command cover minute
inconsistencies several levels down in the primary object. It is up to the user to

evaluate the impact of the shown differences in accordance to the project’s

tolerance.
26. Select Next>> in the dialog box.
27. Select Create Text Report.
28. Open Windows Explorer and navigate to the path shown in the message bar.

29. Open in Notepad the .RPT file created with the same name as the MDR log file. This
report can serve as a reference in future modelling integrity investigations.
30. Close the report and Windows Explorer.

31. Once objects that failed to copy have been identified, the user can evaluate their
condition and integrity (Verify they are not in the ToDo list or reported by Database
Integrity). It can also be determined if it would be faster to use traditional method to
copy/paste between sessions or remodeling of the destination model.
In cases where issues are identified with the data in the select set before or after the
copy operation, the following Smart 3D tools/commands may help identify and address
these issues:
 Database Integrity command
 Database Clean command
 To Do List
 Synchronize Model with Catalog
 Catalog Comparison in MDR Wizard
32. Close Smart 3D and save your changes to the session.

LAB 20: Model Data Reuse – Copy to
New Model
Objectives
 Use Model Data Reuse command from Project management to copy objects between
models in the same site
 Use one of the copy options in the Model Data Reuse command to copy volumes in range
 Use Model Data Reuse command to copy models with different catalogs
1. Launch Smart 3D.


4. Select model SP3DTrain.

LAB 20: Model Data Reuse – Copy to New Model
5. From the Filter dropdown, select More…

6. Underneath the Plant Filters folder, select the filter All. Click OK.
7. Define the Workspace with these selections.
8. Once the workspace is loaded, open the Common Views window. Select the frontal
Isometric view.
9. In the Workspace Explorer, expand node A2 and right-click on system “U02”.

10. Click on “Select Nested”.
11. Fit the selection into the graphic area.
12. Right click anywhere to unselect.

13. Go to View > Named Views…

14. Enter the following:

Name: Unit U02
Description: Isometric
15. Click OK.

16. Follow steps 9-15 for the following units:
A3 > U13
A3 > U14
17. In the Named Views window, you should have the following three views:
18. Close the Named Views window.
19. In the ribbon toolbar, expand the dropdown from the Named Views command.
20. Verify that each of the named views displays one of the three different units. These units
contain the data to be copied by the MDR operation.

21. Save the Smart 3D session as “MDR_SRC” in the Desktop > MDR.
22. Close Smart 3D.
24. Open the Model Data Reuse wizard. Begin a new operation, provide as name “MDR
from SP3DTrain to Admin Model/Catalog”. Click Next.
25. This time the source objects will be selected via Source Systems. Select SP3DTrain
as source model. Click Next.
26. In the Source Systems window, select the following parent systems:
 A2 > U02
 A3 > U13
 A3 > U14

27. Click Next.

28. Select All disciplines. Under Copy options, select Copy volumes in range.
29. Click Next.

30. On Destination System page, select Admin_Model. The software warns about the
possibility of Schemas not having the same information. Click OK.
31. Click Next.

32. Click the browse button to select “MDR_Dest” as the Destination System Parent for both
Source System Parents.
33. Set default permission group to Permission Group 1.
The values in the "Default permission group:" drop down list has changed. The
groups are defined per Model.

34. Go to the “Space” tab, and in the Destination Space Parent column, expand the
ellipses to select the Admin Model node.
35. Click OK.

36. Click Next.

37. Select None if not already selected.
38. Click Next.

39. The Compare Catalogs page appears. This will only be present when user is
performing a copy across models that have different catalogs. It will compare the
catalog schemas and the pipe specs in the select set chosen. Verify the source and
destination catalog information.
40. Click the Compare button. A progress window will appear.

41. Once the comparison has been completed, the View & Map window will be displayed
with the results.

42. Select Report.

43. Open the generated Excel spreadsheet, and review the contents of each sheet.
44. Save this report as “MDR_NoMapping” in the Desktop > MDR folder. Close the report.
In cases with substantial catalog differences, it is recommended that this initial report
is used by the catalog administrators to evaluate and address reference data
differences prior to continuing with the MDR operation.
45. Click on the empty “Destination Pipe Spec” cell to map Source pipe spec 1C0031-PB.
46. Expand the dropdown and select pipe spec “1C0031”.

47. The status in this row should change.

48. Expand the ellipses in the Status cell of Source Pipe Spec 2C0032.

49. Review the report and Close it.

50. Back in the View & Map window, check the box Only show items used by current
operation.
51. Go to the Short Codes tab and maximize the View & Map window.
52. Expand the Inline Fittings folder.
53. Select the Valves folder.
54. Verify that the Butterfly Valve missing for spec 2C0032 in the Target catalog is not
employed in the select data set.

55. Open the Other Inline Fittings folder.
56. Expand the dropdown in the Destination Short Codes field for the Coupling row.
57. Scroll down and select All Short Codes…
58. Re- expand the dropdown list and select the short code Endolet.
59. Go to the Option Codes tab.

Only Option Codes created in addition to the delivered catalog content are
displayed and made available for mapping.
60. Run a new report. Check that the previous mapping is reflected.
 Pipe Spec 1C0031-PB to 1C0031
 Short Code “Coupling” to “Endolet
61. Save this Report as MDR_WithMapping.
Iterations of the mapping process across catalogs are useful references in
cases where multiple MDR operations are expected to be performed across the
same two models, since the mapping between two catalogs will be saved by
Project Management.
62. Click OK on the View & Map window.
63. From the Compare Catalogs window, select the Pipe spec and short code mapping
will be used box.

64. Select Next.

65. Review the Confirmation window. Select Copy.

66. Once the copy operation is complete, inspect the tabs in the Operation Properties
dialog.
67. Click OK.

69. Open the saved session MDR_Admin.
70. Run the Refresh Workspace command.

71. In the Workspace Explorer, right-click on the MDR_Dest folder and select Select
Nested.
72. Fit the graphic view to these objects.

73. Open the Common Views window and select the Isometric View.
74. Right-click anywhere to de-select.

76. Click on Properties.

77. Edit the filter by selecting the root node for the model in the Named Space tab.
78. Click OK.

79. Define the Workspace with this selection to verify the execution of the “Copy volumes in
range” setting.

80. From the Workspace Explorer, select the Space tab at the bottom. Locate and select
Copy of Volume U02 under Admin_Model > Name Space.
81. Open its Properties Page and modify the copied volume:
 Name: VolumeU02_Target
 Type: Areas\Support Areas\ Product Processing
82. Click OK.

83. Select volumes “Copy of Volume U03” and “Copy of Volume U01”.

84. Delete them.

85. Press CTRL+W to open Define Workspace.
86. Click on Properties.
87. Go to the Named Spaces tab and de-select the root node for the model with
CTRL+CLICK.
88. Click OK.

89. Define the Workspace with this selection.

90. Without closing the current session, open the saved session “MDR_SRC” to view the
source model SP3DTrain.
91. Go through each of the Named Views in the source model session while bringing
the respective unit into view in the destination model session.
(Optional) Manipulate the Common Views to inspect the objects in each copied unit.
92. Go to Tasks > Piping.
93. Set the Locate Filter to “Pipe runs”
94. Enter “U02-12-P-0001-1C0031-PB” in the “Systems” tab of the Workspace Explorer

95. Hit Enter
96. Fit the graphic view to this selection

97. Open its Properties Page to check the original Specification in this pipe run
98. Press Cancel.

99. Open session file MDR_Admin, go to Tasks > Piping.
100. Set the Locate Filter to Piping runs.

101. In the “Systems” tab of the Workspace Explorer, navigate to

MDR_Dest>U02>Process>2005-P
102. Select the Pipe run under this Pipeline System
103. Fit the graphic view to this selection
104. Open its Properties Page to see the mapping effect on the Specification

105. Press Cancel.

106. Go back to the Source model session MDR_SRC.
107. With the Locate filter still set to Piping Runs, enter U13-1-P-0101-1C0031 into the
Systems tab of the Workspace Explorer.
108. Select and fit this pipe run into the graphic view.

109. Open its Properties Page.

110. Go to the Relationships tab.
111. Click on the Coupling entry and select Go To.
112. In the Pipe Component Properties window, go to the Definition tab and note the Part
Number, Display Prog ID, and Commodity Type.
113. Press Cancel.

114. Go to the Target model session.
115. Change the Locate Filter to All.
116. Identify pipeline P-10145 using the Workspace Explorer. Fit this pipeline into view.

117. Select the branching piping run (equivalent to U13-1-P-0101-1C0031) and open its
Properties Page.
118. Go to the Relationships tab.
119. Select the Endolet entry (the substitution of the Coupling in the source) and select Go
To.
120. In the Pipe Component Properties window, go to the Definition tab and note the
mapping effect on the Part Number, Display Prog ID, and Commodity Type.
121. Press Cancel.
Symbol Replacement
122. In the Source model session, locate pipeline P-10148.
123. Fit this pipeline into view with the shown Isometric Common View.

124. In the Target model session, locate the same pipeline P-10148 and fit it into view with
the same Isometric Common View
125. Change the Locate Filter to Pipe Parts in both model sessions

126. Select a Gate Valve in the source model session and open its Properties Page.
127. Go the Definition tab. Note its Display Prog ID among other properties, such as part
number, valve trim, Primary Size, and Commodity Sub Class
128. Identify the equivalent part in the target model session and open its Properties Page.
129. Go the Definition tab. Note the Display Prog ID has changed, while all other properties,
such as part number, valve trim, Primary Size, and Commodity Sub Class have
remained the same.

130. Press Cancel on each Pipe Component Properties pages.

131. Perform a similar comparison between globe valve VL2-0201 in the source model
session…
132. …and its equivalent in the target model session

133. Close all Properties pages.
Replacing Piping Generic Components

134. Go to the target model session
135. Navigate to Tools > Select by Filter…
136. Click on the New Filter command.

137. Enter the name Piping Generic Components.

138. Go to the Object Type tab.
139. Under the S3D folder, expand Piping > Piping Parts > Piping Generic.

140. Click OK.

141. Back in the Select Filter window, choose the newly created filter and click OK
142. Fit the Workspace to the selected items.

143. Resize the Workspace Explorer and navigate it to locate Generic components created
during the MDR operation, shown as “Replace Me” children in the hierarchy.
144. Right-click in the graphic space to deselect all the generic components.
145. Change the Locate Filter to “All” if not set to this
146. Expand the following in the Systems hierarchy: MDR_Dest > U14 > Piping > P-10116.
147. Select the generic component.

148. Fit the workspace to this selection.

149. Open its Properties Page, locate the value for Pipe Specialty’s Tag

150. Close the Properties Page and right-click anywhere to de-select

151. Tag STR-002-6 corresponds to the Pipe Specialty Item “Jamison Model FQ Single
Basket Strainer Model FB/FQ-600”. Verify this by going to the source model session
and examining U14 > Piping > P-10116 > U14-6-P-0003-1C0031 > STR-002-6.

152. Return to the target model session and change the Locate Filter to “Piping Features”
153. Select the generic component graphically from the Active View.
154. In the ribbon bar, expand the “Type” dropdown list
155. Select “Browse piping custom specialties…”

156. In the “Browse piping custom specialties” dialog box, select “More …” from the
Specialties dropdown
157. Navigate to Custom Specialties > Basket Strainer > CSBasketStrainer4.

158. Select this Part Number and click OK.

159. Once the part is computed, right-click anywhere to exit selection.
160. Go to Tools > Select By Filter…
161. Select the Piping Generic Components filter.
162. Click OK.

163. Without exiting the selection, locate the replaced piping specialty to verify it’s no longer
identified and highlighted as a Piping Generic Component.

164. Save changes and close both Smart 3D sessions.

LAB 21: Model Data Transform
Objectives
After completing this lab you will be able to:
 Complete a transform operation of an entire unit that must be repositioned according to a
newly defined coordinate system.
1. Launch Smart 3D.




6. Underneath the Plant Filters folder, select the filter All. Click OK.
8. Once the workspace is loaded, open the Common Views window. Select the frontal
Isometric view.
9. Expand folder A2 and right-click on U05. Select Select Nested.
10. Fit the selection into View. This will be the select set for the Transformation
operation.

11. Right click anywhere to de-select.

12. With the Locate Filter set to “All”, select the Structural System “Solids” in the A2 > U05
> Structural folder.
13. Right-click and Select Nested.
14. Open the Properties Page and go to its Configuration tab.
15. Change the status from “Working” to “Approved”.

16. Click Apply and close the Properties Page.
18. In the Workspace Explorer, expand the “Equipment” folder under U05. Select equipment
E-PP-A2.
19. Open its Properties Page and go to the “Occurrence” tab.
20. Change the Category from “Standard” to “Position and Orientation”. This will be a
marker for the transformation operation.
21. Go to the Configuration tab and change the status from “Working” to “Approved”.
22. Click Apply and close the Properties Page.


24. In the Workspace Explorer, expand the “CS” folder. Select “U05 CS” and open its
Properties Page. Note the global coordinates from the General tab and close.
25. Select File > Save to save the session as “MDR_Transform” in the Desktop > MDR
and close it.
27. Go to Tools > Model Data Transform…
28. Select Begin New Operation and click Next.

29. Name the operation MDR_Coordinate System Change and click Next.
30. In the Model window.
Press “Select Model” and choose SP3DTrain.
Object selection method: Systems
Options: Uncheck “Ignore approval status during transform”. Accept the following
warning:
Operation permission group: Admin.
31. Select Next.

32. In the Systems window, expand the A2 folder to select U05.

33. Select Next.

34. In the Transformations window, select the Move and rotate mode.
35. Expand the ellipses in the From coordinate system: field. Expand the CS folder to
select U05 CS.

36. Click OK.

37. Expand the ellipses in the To coordinate system field. Expand the CS folder to select
CS_MDT.
38. Check the coordinate system inputs.
39. Click Next.

40. In the Confirmation window, press Check Write Access.

41. Once the status window disappears, press the Copy to Clipboard button in the Check
Write Access-Results window.
42. Open a new Excel spreadsheet.

43. Paste the contents of the clipboard.
44. Review that the objects set to an Approved status are mentioned in the messages.
45. Save this workbook as MDR_CheckWriteAccess in the Desktop > MDR folder.
46. Close the workbook.
47. Back in the Check Write Access- Results window, click OK.
48. Back in the Confirmation window, press Transform.

49. A progress bar will appear, wait until both the disconnection and transformation phases
are complete.
50. The following dialog will appear. Click OK.
51. An Operation Properties window will appear with a results summary.

52. Explore its contents and close the window to exit the Model Data Transform wizard.
53. Go to Tools > Model Data Transform
54. In the Welcome page, select Restart Existing Operation.
55. Locate operation MDR_Coordinate System Change and review its status.

56. Click Cancel.

57. Exit Project Management.
Evaluating MDT Results

58. Open the saved session file MDR_Transform.ses in Smart 3D.
59. Run the Refresh Workspace command.
60. Verify the new alignment of the non-Read Only objects.

61. Change to an isometric view in the Common Views window.

62. Open the Properties Page for Equipment E-PP-A1 in A2 > U05>Equipment to check
that all relationships were preserved.
63. Click Cancel.

Close Smart 3D

LAB 22: Synchronize Model with Catalog
and View Generation
Objectives
 Actively choose whether to synchronize the model with catalog or run the view generator on
the model command, or both from within Project Management
 Let us play out the scenario that there are two models (model A and model B) sharing
the same catalog. This catalog has changed significantly since the last backup was
taken for model B. In this scenario we would perhaps run the synchronize model with
catalog command on model B in the event it gets restored with the old backup.
Synchronization will try to push down changes on the catalog and bring part definitions
in line with the live/current database.
 Likely, after the restore of this outdated model, you would then regenerate reports
databases and would be presented with a message saying that some views failed to
generate, this is one indication of where you would use the view generator feature in
this command.
1. Start Project Management.
2. Select the model in the tree that you wish to Synchronize (SP3DTrain). Then, from the
Tools menu select Synchronize Model with Catalog.

LAB 22: Synchronize Model with Catalog and View Generation
3. Note the existence of two check boxes:
Not all Catalog changes require a true Synchronization of the data but the following
instances are an example of when to run it: perhaps an entirely new part class has been
added to the Catalog that did not previously exist, or even a new Interface that was not
there. The views associated with this data would probably be absent from this restored
model, or perhaps columns on prior views would be different.
4. Leave all checkboxes checked on the Synchronize Model with Catalog form and allow
the command to run to completion by clicking OK.
5. Click OK.
6. Click OK, then OK to dismiss the second dialog box.

7. Open and review generated log file.
8. Go to the end of the file for a summary of the errors reported.
Note: In a production or test environment you would then follow this action by regenerating
reports databases.
If the user did not have permissions to update objects or only chose the option Mark out-of-
date occurences, objects can be flagged for interactive updates in the model workspace by
running the report Diagnostic Synch Workspace Report.
9. Launch Smart 3D.



13. Underneath the Plant Filters > Training Filters folder, select the filter U04. Click OK.
15. Click OK on Define Workspace form and allow Refresh to complete.

16. From the Tools menu select Run Report.

17. From the Catalog Reports tab, select Diagnostic under Types of Reports and Diagnostic
Synch Workspace Report.
18. Select Run.
19. From the Select Filter window, select Plant Filters > All.
20. Review results.

LAB 23: Database Maintenance
Objectives
 Access Maintenance form to perform optimization tasks in the database
This is an enhancement to the delivered software that allows users to purge
temporary data and perform tasks such as optimizing indexes.
1. Start Project Management. Select the model or catalog you want to perform
maintenance for, then select Database > Maintenance.

2. Place checkboxes in the first two options and then click the Analyze button to understand
the current need for the maintenance.
3. To perform these actions, close the Analyze form and then click OK on the database
maintenance form.
4. Click Yes, acknowledging that the process may take some time.


5. After this process has finished, go back to the Database Maintenance form and select the
Rebuild selected indexes option from the Index optimization section. It may take a few
seconds to populate the list.
6. Select any four tables. Click OK.

7. Note the warning message and then review the server to ensure that all users followed
directions and disconnected.
8. Click Yes to let the command work.
9. Once the command has completed, you can close the form by using X or Cancel button.

LAB 24: Database Integrity
Objectives
 Run Database Integrity command to verify consistency of model objects and perform the
clean action
 Run a report to find objects with Integrity issues
 Clean inconsistent objects detected by DBI by using a custom command delivered out of the
box


2. Select Database > Integrity…
3. Select the database you wish to check (check all three databases for this lab). Choose
Basic check and then click Run.
4. Exit the form when finished.

5. Open the temp folder by typing in the address bar of windows explorer %temp% and
review the three error logs created for database integrity check. Make sure there were
no catastrophic failures by looking for the word error or making sure the command
completed successfully on each database.

6. A file called DbIntegrityCommandLine-PlantName.txt will be created on this same

directory. It will contain the command line you would need to use if you wish to run
Database Integrity on a batch script.
7. We will now run a report for Database Integrity entries. This report could be executed
both before and after the Clean Custom Command is executed.
8. Start a new Smart 3D session.
9. Click OK.
10. Use File > Define Workspace to select SP3DTrain model:
11. From the Filter drop down select More and then select ALL filter.
12. Click OK.

13. Click OK on Define Workspace form and allow Refresh to complete.

14. From the Tools menu select Run Report.
15. From the Catalog Reports tab, select Diagnostic under Types of Reports and Diagnostic
Clean Database Issues report as depicted below and execute it. If there had been any
problems found or fixed by the Integrity script then this report would reflect it.
16. Click the Run button and an Excel workbook will appear containing results of the report.

Note: You may see the following dialog box if the security settings for Visual Basic
projects have not been set in Excel (they are not by default).
Note: Follow these instructions to set Excel security settings for Office 2010.
- Open Excel
- Click the Office button at the top left margin of the window.
- Select Excel Options from the bottom.
- Choose TrustCenter from the left menu, then TrustCenter Settings...
- Go to Macro Settings on the left, then check radio button Enable all macros...
- Check Trust access to the VBA project object model checkbox.
- Click OK on the two forms to dismiss and close Excel.
17. Close Excel after revision of reported objects.

Note: Once Database Integrity has finished, next action is to clean the database for
issues that were found. The Clean Database command is not yet integrated in the GUI
environment, you will need to use a special custom command with ProgID
SP3DCleanDatabaseCmd.CCheckObj to perform the clean procedure. This command
needs to be executed from a Smart 3D session as there may be objects that need to be
modified in the graphical environment. An example of how to access this from a Smart 3D
session in the event that there were items to be cleaned is as follows.

18. From the Tools menu select Custom Command.
19. Click the Add button on the following form.
20. Click OK after completing the form as shown below.

21. Click the Run command.
22. In general, you will use this form to select any items appearing on the list and then perform
a Clean Now operation. Refer to the DBIntegrity.pdf help file (located in C:\Program
Files(x86)\Common Files\Intergraph\Smart3D\Help) for more detailed information on
specific issues.
23. Close the command and custom commands window.

24. Close the Smart 3D session.

LAB 25: Error log files
Objectives
 Configure and save options for Smart 3D error log reporting
1. During execution of the software, several log files are created that will help to perform
troubleshooting procedures if needed. The majority of these log files are written to the
temp folder of the current user profile. This location can be quickly accessed by using
the windows environment variable %temp% on the address bar of Windows Explorer.
By default, Smart 3D error logs are created when a session is opened, but the log file will be
deleted if it has not been set to be permanent.
2. Navigate to [Smart 3D install folder]\Core\Tools\Administrator\Bin\ and execute
program ErrorLogEnable.exe.
3. Set options according to the following values.
Ensure the path that is provided on the form is writable by all local users (if it is not,
then it will not be written for other users that log in because it will not be able to write to
specified location).
In General, severity level "1-Normal" will usually be sufficient, but there may be times when
a support analyst working a problem you have reported, will have you adjust this value.
You will need to close Smart 3D and start it again (potentially from an already saved session
file) before these settings take effect.
4. Click OK.
5. From now on, an error log file will remain in the temp directory every time a session is
opened and closed. A different error log is going to be created for each instance of
Smart 3D opened.
6. Open Smart 3D to generate a new log file.

7. Navigate to the temp folder (you can type in the address bar of a Windows Explorer
window %temp% then enter).
8. Open the most recent Smart 3D log file (sort by date modified column for quick
revision), it will have a name that is compounded of the words
SP3DErrors_TIMESTAMP where TIMESTAMP is the date and time when the log file
was created.
9. The information reported initially will help to identify the kind of operating system, total
addressable memory and product version (very helpful when troubleshooting setup
issues).

10. Further down, information about process ID and path to executable file that generated
the log file can be seen, continued by display rendering settings.
11. Knowledge of the location and information on the error log files is important when
performing troubleshooting procedures. An Intergraph support analyst may also
require you to generate and send this error log file as a regular methodology to track
down and find additional data when performing troubleshooting.
12. Close the log file and Smart 3D session.

LAB 26: Interference Checking
Objectives
 Configure an Interference Checking Server for a particular project
 Enable and use Local interference checking
 Review interference objects using the List view
 Modify and configure Interference clearance rules
Database Detection
Upon software installation, the option "Database Interference Detection Service" can be
selected from the list of available features. This is what enables the workstation to become a
potential IFC Server.
During this lab practice, the word IFC will be used to refer to Interference Checking.
1. Click on Configure Interference Checking Service utility found in Start > All
Programs > Intergraph Smart 3D > Database Tools > Configure Interference
Checking Service.

2. Complete the form as shown below identifying Admin_SDB and

Admin_SDB_SCHEMA. By completing this form in this manner you are indicating that
this IFC Server can process any Model that belongs to Admin_SDB site database.
3. Click OK to close the Configure Interference Service form.

4. Open a windows Services console by going to Start > Run. Then, type command
services.msc. Locate the service named Smart 3D Interference Detection Service.
Right click on it and select Properties.
5. Switch to the Log On tab and select This account option. Specify a login account that
meets permission requirements to act as the identity for the Interference Checking

service. For the purpose of this lab practice, type in the local administrator account
credentials, then click OK.
In a production project, this identity is a domain account that meets the following
permission requirements.
 Account is included in local administrators group
 Has database access and permissions as a regular user to SQL or Oracle database
 Has write or higher level of access to at least one permission group
6. Start windows service Smart 3D Interference Detection Service.

7. Open Project Management and expand SP3DTrain model. Right mouse click on the
Interference Server icon and select Properties.
8. Complete the form as shown below taking care to identify the machine name where the
practice is being performed as domain\computer. This field identifies the computer
where the IFC service has been started. In a production environment, this form could

be completed from any computer with Project Management loaded and does not need
to be completed from the IFC machine.
9. Click the Start Button.

If the Service was not started in the previous steps, you may be presented with the
following message:

10. It may take up to 4 minutes for the processing to start and when it does, you can review
progress on the status tab.
11. Start a Smart 3D session. Define a workspace on model SP3DTrain with the All filter.

12. From the Tools menu select Check Interference.
13. A new toolbar will be displayed. Click on the yellow icon to open the Interference List.

14. Hold the Ctrl key and select any row header from this list. The IFC object and its
corresponding clashing objects will be highlighted.
15. Click on Fit Interferences button located on the Interference checking toolbar.
16. The graphic window will zoom you to that interference and the objects involved.
Change to an isometric view for better viewing.

17. Any user can turn on/off the IFC markers that are displayed graphically on a session by
using the Settings button to access following form.
18. De-selecting the checkboxes from Type or Required Action sections will hide IFC
markers from the current view (though they will still exist in the database).

19. The status tab shows progress of database interference detection in workstations where
Project Management is not installed.
20. On the Local Detect tab you will find options to set and start local interference
checking. Note the options that can be set are basically the same as settings for

database detection. However, the user is free to modify them according to his/her
needs. Local IFC will not interfere with Database IFC results.
21. Close the interference checking settings form.

22. Enable Interference list from the toolbar or bring it to focus. Expand it to see the
Notes column.
23. Click the Notes field of any IFC entry and start typing. Hit enter to accept the input.
Try to find this interference in the Model and review its properties. The note should be
there as well.
24. Right click any Interference under the Name column. The properties page for that
interference will appear.
25. Close the list and review overall IFC markers. Examine one that may catch your
attention and determine if it is of the correct type (hard, soft, or clearance) according to
the options set in Project Management on the IFC form.
Local Detection
27. Start Smart 3D (Start > All Programs > Intergraph Smart 3D > Smart 3D), if not already
open.

28. Define a workspace using the All filter or refresh the session.
29. If the IFC toolbar is not already enabled, from the Tools menu, select Check Interference.
30. Click the left most button for IFC Settings , the following form will be displayed.

31. On Local Detect tab, complete the form as follows:
32. Click OK.

33. Note that IFC word appears at the bottom left of the Smart 3D window as acknowledgment
of local IFC execution for the session:
34. Save session file as "IFC LocalDetect Example.ses".

35. Because this class is presumed to be taken before the Equipment or Piping classes, the
instructor may guide you through some ad hoc simple examples to show that the Local Detect is
now working. You may also try to generate some clashes by doing base move of objects so as
to make them collide to move objects, use the commands from the main toolbar).

36. Bring up the IFC List. Note that Local Detect Entries do not have a name and there is no
additional information different than the two colliding parts.
37. Do a Refresh to the workspace and note that local detect markers disappear, while
database detect IFC markers (if any) remain.
38. Try to create one of each clash type (hard, soft and clearance) depending on the rules
previously set when enabling local detect.
39. To finish the practice at this point, stop Database Interference Checking from Project
Management, then stop the windows service Smart 3D Interference Detection Service.
40. Close any open Smart 3D Sessions.
Configuring IFC Clearance Rules (Optional)

Clearance rules are used to mark two objects that are closer than a specified distance.
Interferences created as clearances can be identified by the color green. This lab practice will

help you review existing clearance rules and create a new one based from existing Plant125
rule.
41. Open Excel workbook IFCRule.xls delivered to [Smart 3D install
folder]\CatalogData\BulkLoad\Datafiles\.
42. In IFCClearanceRule worksheet, highlight all rows pertaining to "Equipment with other
objects types" section from Plant125 rule. This is approximately row 7 thru 116.
43. Copy selected rows.
44. Select row header where Plant125 name is located.
45. Right click the row header and select Insert copied cells.
46. Insert one additional blank row at that same location so that you can create a name for the
new Clearance Rule. In the case of the screen shot below, that cell is B4. Provide the name
EquipOnlyClearance for the new Clearance rule.
47. Scroll to column G, which is labeled Clearance.

48. Replace all values with "152" (~6 in) for all EquipOnlyClearance Rule entries that have just
been copied. This will now create a clearance rule of 152mm between equipment against all
other S3D object types (except R3D objects).
49. Save the Excel Workbook as IFCRule_Admin.xls.

50. Start the Bulkload Utility by going to Start > All Programs > Intergraph Smart 3D >
Database Tools > Bulkload Reference Data.

51. Complete the bulkload form providing the path to the Excel file "IFCRule_Admin.xls" and
options as shown below:
Make sure the Catalog and Catalog schema databases are properly selected.
52. Click Load.

53. Review bulkload log file for any errors. Correct and retry the bulkload as necessary. There
will be a large number of warnings due to records already existing in the database, this is ok, but
errors have to be reviewed.
54. Start a new Project Management session.

55. Open Interference checking properties form by going to SP3DTrain > Interference Server.
56. Stop Interference checking if it is running.

57. Observe existence of recently bulkloaded rule EquipOnlyClearance.

58. Complete the form similar to what was done in previous practice for local detection, except
this time select the newly created EquipOnlyClearance rule.
59. Start the Smart 3D Interference Detection windows service, then click Start.
60. The following message will be displayed advising that the model will be rechecked due to
changes in the IFC settings. Click OK.
61. You may now go into a modeling session and test the newly added rule.

If this is the last Interference Checking practice performed, stop the Windows
Service Smart 3D Interference Detection Service.

LAB 27: Export ZVF and XML files to be
used in R3D referencing
Objectives
 Export zvf and xml files from a Smart 3D project that can be used for attachment as R3D
references
 If the project is currently registered with SmartPlant Foundation, the user generating these
files must be able to make a successful connection onto SPF server.
 SmartPlant Schema Component is a prerequisite software that cannot be omitted. Make
sure it is loaded on the system before proceeding.
1. On any graphical task, go to Tools > Drawing Console.

LAB 27: Export ZVF and XML files to be used in R3D referencing
2. Right click on Drawings or any other folder in drawings hierarchy, select New > 3D
Model Data.
The 3D Model Data object can be located on any folder in the drawings hierarchy,
but not under the root.
3. Right click recently created 3D Model Data object and select Setup…
4. In the setup form, select the filter containing objects to be exported. Choose filter U01
& U02 from Plant filters >Training filters node.
5. Select the option Generate SmartPlant Review output (.vue file), check Generate
streaming vue ouput (.zvf file) checkbox if not selected.

6. Check Disk only (do not save to database) checkbox if not selected.
7. Define a path that can be accessed later and give as name for graphics file
U01_U02.vue. The path for data file should be automatically populated with same
location.
8. Click OK.
9. Back on the Drawings Console, right click recently modified 3D Model Data object and
select Create Drawing.

10. When a drawing object has been created, right click on it and select Update Now.
The drawing object must update successfully.
11. Once the drawing has been properly updated as shown by the green check mark, go to
the specified location and retrieve*.zvf and *.xml files to be used in R3D referencing.
Following errors may appear in the drawing log file if SmartPlant Schema component
is not loaded in the system:
Error Number: 1
Process Virtual Memory: 183 MB
Description: Schema Component installation not found.
Source: CThreeDViewGenerator::Run
Method: CThreeDViewGenerator::Run
Source File: ThreeDViewGenerator.cpp
Source Line: 644
13. Close the Smart 3D session.

LAB 28: Attach external 3D data as a
reference (R3D)
Objectives
 Attach external 3D data (R3D reference)
This practice will demonstrate the steps to attach external 3D data into the model with the option
to perform basic transformations (rotation, scaling and translation).
1. Locate files needed for R3D reference, these are the zvf and xml files previously
exported from Smart 3D. Place them into a directory where they must remain and be
accessible at all times. The symbols folder is the preferred location.
Example..\SharedContent\Reference3D\.

3. Expand SP3DTrain model hierarchy. Note the existence of a Reference 3D Models
node. This node will only exist on models that already have a R3D referenced object.

LAB 28: Attach external 3D data as a reference (R3D)
4. Right click the Reference 3D Models node and select New Reference 3D Model…

5. Set the values on the form as shown below. Use a name that is related to the files to
be referenced. Make sure to use a UNC path when browsing for the files.
6. Click OK.
7. The referencing process will start and a new dialog will be shown indicating the actions
that are currently being performed.

8. When the process finishes, the referenced project will appear as a new item under the
Reference 3D Models node.
9. Review the import log file created for the referencing. It can be located in the
%temp% folder.
10. Open a session file or create a new one and define a workspace to bring the inserted
Reference 3D objects.
Referenced objects have their own classification in the objects hierarchy. You may
use predefined filters found in the Catalog filters node > Default Filters > Reference 3D

Object Filters > Object Types or you can create a filter based on Object types. A new tab
for Reference3D objects is available as well.

LAB 29: Perform transformation
(rotation, scaling, and translation) to
R3D models.
Objectives
 Perform different transformations to currently attached R3D projects
1. Open a session file or define one and bring the referenced model that will be
transformed into the workspace.
3. Open the properties dialog for U01_U02 referenced model.
4. Set values as follow:
 Target Point - Northing: -50 m
 Rotation – Up angle: 30 deg
5. Click Apply.
6. Return to Smart 3D session and do a refresh.

LAB 29: Perform transformation (rotation, scaling, and translation) to R3D models.
You might need to fit the view in order to locate the objects.
7. Return to Project Management and try other transformation values. Compare results
by going back to the session file keeping in mind to do a refresh every time there is a
change.
8. Define a workspace that will return objects from U02 and U01 units as well as the
attached reference 3D model U01_U02. You may create a filter with following criteria for
this purpose:

 System tab:
 Reference3D tab:

9. Compare results. Try other transformation values now that there is a visual reference of
the original position.

LAB 30: Update attached R3D models
Objectives
 Perform updates to attached R3D models. Such updates can be modifications performed to
modeled objects such as new designs, change in styles (color of the objects) or removal of
content due to revisions.
To simulate an update performed to initially published objects, it would be necessary
to perform a change that will allow visible comparison of the results. The next series of steps
will guide you through the process of deletion for some objects in unit U02 of the training
model.
Prepare Objects to be Republished

1. Open a session file or define a new workspace with the filter U01 & U02 located under
Plant filters > Training filters.
2. From the workspace explorer, right click the Structural system under U02 and choose
Select Nested.

3. You may be able to see all structural objects under the Structural system being
highlighted in the active view.

4. With the objects selected, select the delete key, or go to Edit > Delete… don't worry,
you can recover using MDR or SP3D Backups.
5. Open the Drawings Console from Tools > Drawing console and update the 3D
Model data object created in the previous lab.

6. Locate exported zvf and xml files. Recall their location by opening the setup properties
of the 3D Model Data object.
Update Reference 3D Models

7. Replace existing zvf and xml files of exported objects from U01 & U02 filter into their
referenced location from Project Management. This place could be the symbols folder.
8. Open Project Management. If there is a session already open, do a refresh by hitting the
F5 key or go to View > Refresh.

9. The referenced 3D model should now look out of date as an indication that the files have
been added, removed, or modified.
10. Right-click on Reference 3D Models root node and select Update Reference 3D
Model(s)…
Select U01_U02 and select Update.

You can also open the properties dialog for U01_U02 referenced model and check the box
at the bottom Reference 3D Model data has been updated … Click OK.
12. Status dialog will appear:
13. Once the update has finished, open an existing session or create a new one to
evaluate the results.

14. Refresh the workspace if needed for the changes to be reflected.

LAB 31: Export VUE and MDB2 files to
be used for R3D Referencing
Objectives
 Create VUE and MDB2 files using SPRDirect in a SP3D project
 Convert VUE to to ZVF using the ConvertToZVF utility
 Attach new R3D model using the ZVF and MDB2 files in SP3D
1. Open a Smart 3D session or create a new session.

2. Define your workspace to view Unit U02 from SP3DTrain model using the filter named
U02 located under Plant Filters > Training Filters > U02.
3. Switch your graphic view to Isometric and do a Fit. Your workspace should resemble
the view shown below.
4. Switch to the Drawings and Reports task by selecting Tasks > Drawings and Reports...
5. Expand the Reports folder in the Management Console.
6. Select the Spreadsheet Reports in the Management Console and right click and select
Create Report...

LAB 31: Export VUE and MDB2 files to be used for R3D Referencing
7. On the Select Report Template dialog select the S3DToSPRDirect report from Types of
Reports > SmartPlant Review > S3DToSPRDirect and click OK.
8. On the Select filter dialog select the filter named U02 located under Plant Filters >
Training Filters > U02 and click OK.
9. On the Report Parameters dialog specify the output location for the files as c:\SPROutput\
and click Finish. Do not provide the optional coordinate system information.
10. A new SPRDirect report will be created. Select the report, right click, and choose Update
Now.

11. After the update is complete, a green check will be placed on the report.
12. Open Windows Explorer and navigate to the output folder location specified on the Report
Parameters dialog in step 9.
13. Create a new folder in the SPROutput folder, name it SPR_R3D_Files and copy the
U02.mdb2 file from SPROutput folder to SPR_R3D_Files folder.

Convert to ZVF
14. Open Windows Explorer and navigate to the following location to get to the
ConvertToZVF.exe utility.
[Smart 3D install folder]\Core\Tools\Administrator\Bin\
15. Start the utility by double clicking on the ConvertToZVF.exe.
16. Specify the Input and Output folder path on the ConvertToZVF window and click Convert.
Input Folder: C:\SPROutput
Output Folder: C:\SPROutput\SPR_R3D_Files
17. After the conversion is complete, open the SPR_R3D_Files folder and you should see the
converted ZVF file.
18. Copy the SPR_R3D_Files folder to your SharedContent folder.
Attach a new R3D Model

20. Expand SP3DTrain model hierarchy.
21. Right click Reference 3D Models node and select New Reference 3D Model...
22. Set the values on the form as shown below. Use a name that is related to the files to be
referenced. Make sure to use a UNC path when browsing for the files.

23. Click OK.

24. The referencing process will start and a new dialog will be shown indicating the actions that
are currently being performed. When the process finishes, the reference project will appear as
a new item under the Reference 3D Models node.
25. Review the log file created for the referencing. It can be located in the %temp% folder.
27. Open a new Smart 3D session and define your workspace to view the Reference 3D
model attached and U02 side by side.


LAB 32: Convert DGN to ZVF and Create
Folder Hierarchy for R3D Models
(Optional)
Objectives
 Convert DGN file to ZVF using the ConvertToZVF utility
 Create folder hierarchy for R3D models which will be reflected in the workspace explorer
(WSE)
 Attach multiple R3D models in Smart 3D under a single parent folder
During this session we will go over the workflow to convert DGN files to ZVF using the
ConvertToZVF utility delivered with the software. The ZVF files will be used to attach new R3D
models in Smart 3D. The DGN files used in this lab practice have different object types defined
on different levels.
When the user creates a folder hierarchy on disk below the root folder of the R3D attachment,
the folder hierarchy is automatically reflected in the WSE without having to do anything extra in
Smart 3D.
Instructor will provide the location of the DGN files.
Convert to ZVF
1. Open Windows Explorer and navigate to the following location to get to the
ConvertToZVF.exe utility; [Smart 3D install folder]\Core\Tools\Administrator\Bin\
2. Start the utility by double clicking on the ConvertToZVF.exe.

LAB 32: Convert DGN to ZVF and Create Folder Hierarchy for R3D Models (Optional)
3. Specify the Input and Output folder path on the ConvertToZVF window. Instructor will
provide the location for two DGN files (Piping_Equipment.dgn and
Structure_HVAC.dgn) that will be converted to ZVF.
It is recommended that the Input and the Output folder should not be the same.
4. Click on the Convert button after specifying the correct paths for the input and outputs
folders.
5. Close the ConvertToZVF window after the DGN files are converted. At this point you
will have two ZVF’s converted from DGN files.
Create Folder Hierarchy

6. Open windows explorer and navigate to the Shared Content folder;
\\ComputerName\SharedContent\.
7. Create a new folder under the SharedContent folder and name it DGN_Reference3D.
8. Create two new folders under the DGN_Reference3D folder and name them
Piping_Equipment and Structure_HVAC.
9. Copy the Piping_Equipment.zvf and Structure_HVAC.zvf to the Piping_Equipment and

Structure_HVAC folders, which were created in step 8.
Attach Reference 3D Model

11. Expand the SP3DTrain model hierarchy.

12. Right click Reference 3D Models node and select New Reference 3D Model…
13. Set the values on the form as shown below. Use a name that is related to the files to be
referenced. Make sure to use a UNC path when browsing for the files.
14. Click OK.

15. The referencing process will start and a new dialog will be shown indicating the actions that
are currently being performed.

16. When the process finishes, the referenced project will appear as a new item under
Reference 3D Models node.
17. Review the log file created for the referencing. It can be located in the %temp% folder.

LAB 33: Use R3D referenced models for
Parallel Design (Optional)
Objectives
 Reference multiple times the same model to achieve initial phase of parallel design workflow
It is sometimes a requirement to work in parallel on areas that will need to be replicated later in
the project. In the meantime, work may need to be performed around the areas where the
objects will be finally positioned. To achieve parallel design of a unit that will be replicated, the
base unit will first be exported as a zvf and xml files, and then referenced as an R3D model as
many times as needed.
After work on the initial unit is completed, the referenced models will be deleted and MDR will be
used to replicate the actual objects.
1. Export zvf and xml files of unit U04 from SP3DTrain model. Use previous labs as
guidance on how to achieve this. U04 objects can be found on the filters hierarchy
under Plant Filters > Training Filters > U04.

LAB 33: Use R3D referenced models for Parallel Design (Optional)
2. Attach as R3D reference U04 objects on SP3DTrain model; name it U04_1, set as
target point -30 m E, 0 m N and 0 m EL.
It is recommended to create a hierarchy of folders to avoid double referencing of files

in the model. Project Management will attach and assign all zvf and xml files existing in
provided file path to same R3D model.

3. Open a new session and define a workspace to bring objects from U04 unit alongside
recently attached R3D model U04_1.
4. Attach same zvf and xml files of U04 objects to the model SP3DTrain, name it as
U04_2 and set as target point -60 m E, 0 m N, 0 m EL.
5. Open a session and review new R3D objects.
If you are working on a previous session file which was open at the moment the
attachment was made in Project Management, you are required to re-open the session in
order to get the new connection objects to see the recently attached R3D model. Until that
is done, refresh will not return any additional referenced objects. To re-open the session,
you can either close it, save changes if preferred, then open it from its saved location, or you
can leave the session file up, then go to File > Close then File > Open, or select it from the
list of recent files.

You may also need to modify the filter definition in order to include recently attached R3D
model.
6. Repeat the attachment procedure of U04 model one more time, name it as U04_3 and
set as target point -90 m, 0 m N, 0 m EL.

7. The list of referenced models in Project Management hierarchy may resemble

something like this:
8. Open a session to review changes and the new R3D objects.

The session file needs to be re-opened if it was active when doing the reference.
Filter may also need to be modified for the attached objects to be returned.
Work can now be performed against or around the referenced models. If IFC is configured
appropriately, interferences with R3D modeled objects will be detected and properly
reported.
To simulate parallel design, changes need to be performed in the original unit. These
changes will then need to be reflected in referenced models.
9. Perform a change in the design to objects in unit U04 of SP3DTrain model. It could be
adding or removing content. If necessary, refer to previous lab practices for assistance
on how to remove objects.

10. Once the modifications have been performed, republish xml and zvf files of unit U04,
then replace existing files in referenced location file path for all three R3D models. This
would make the referenced objects to be out of date as reflected in the Project
Management hierarchy.
You may need to refresh Project Management session for the icons to change.
11. Update each one of the referenced models. Remember that referenced models are
updated by using the check box provided in properties form. Alternately, they can be updated

simultaneously by using option Update Reference 3D Model(s) found under the right click
menu of the Reference 3D Models node.
12. Refresh the Smart 3D session and review changes.

This time closing and opening the session is not necessary as there are no new
connections to the database. R3D models were not referenced in previous step, they were
only updated.

LAB 34: Install Intergraph Batch
Services
Objectives
 Install Intergraph Batch Services and configure it with the purpose to act as a Batch server
for Smart 3D related tasks
1. Locate and execute Intergraph Batch Services installer file (setup.exe) .

Intergraph Batch Services software can be downloaded from the Smart Support
website (https://smartsupport.intergraph.com/) located under View Downloads > BATCH
SERVICES > Service Packs and Fixes > Current Version Updates or it may be provided by
the instructor.
2. Select Batch Services Installation.
3. Provide registration information.

LAB 34: Install Intergraph Batch Services
4. Acknowledge license agreement by clicking Display, then Yes.

5. Confirm the path where to install Intergraph Batch Services. This path can be anywhere in
the system, however, if this installation of batch services is to be used with the PDS software,
then it must be a path containing no spaces.
6. Select Yes to run all jobs as the same user account. This account must be a domain
account that meets the same permission requirements as any other Smart 3D user in order to
be able to access the model and perform the required batch actions. For this practice you will
use the local administrator account to run all the jobs.
7. Finish the product installation.


LAB 35: Configure Intergraph Batch
Services
Objectives
 Configure an Intergraph Batch Services server to be used with Smart 3D scheduled jobs
After Intergraph Batch Services software is installed on the system, there are additional
configurations that must be done in order to create the queues and to configure the machine to
act as a Batch server for a Smart 3D project.
Verify Intergraph Batch Services Status

1. When you install Intergraph Batch Services software, the batch server service is
configured to start automatically each time you restart your computer. No further
configuration is required. The windows service for the Batch server can be found in the
list of Windows Services with name Intergraph Batch Server.
2. Open the properties page of the Intergraph Batch Server service and verify that the
startup type is set to Automatic.
Grant Access Privileges and Enable Error Logging to Batch server

3. Before you begin using Intergraph Batch Services, you should use Intergraph Batch
Manager to ensure that users on your system (and users on other systems if appropriate) are
granted the proper privileges for access to Batch Services.
4. Open the Batch manager by going to Start > All Programs > Intergraph Batch Services >
Intergraph Batch Manager.
5. You may get prompted to create a queue, select No.

LAB 35: Configure Intergraph Batch Services
6. Select the current batch server from the tree on the left, right click, and then choose
Properties.
7. Logging information for the operations carried out by Batch server will be located in the
Application Event Viewer. Under the General tab, enable the following auditing options:
Server logging, Queue logging, Job logging, Job error logging.
8. Switch to the Security tab and add users that will act as managers or operators of the batch
server. Users with manager privileges can use all the commands that affect batch server
configuration and operation. A user with operator privileges can manage jobs, including those
belonging to other users, and can start/stop batch server queues. For this exercise, add the

S3DAdmins local group as a manager to this server. S3DAdmins local user group was
created in lab practice number one.
Users or groups without privileges can only submit requests to queues to which they
have been granted access. Most users or user groups are non-privileged users.
9. Click OK
Configure Account Mappings

10. After manager and operator users have been defined, it is recommended to verify that
account mapping has been properly set for Smart 3D users. The mapped account must meet
the permission requirements as a Smart 3D user to perform the tasks of each one of the
scheduled jobs (i.e. enough privileges to perform backups, run database integrity, update
drawings, etc).
11. In the Intergraph Batch Services window, go to Server > Account Mapping.

12. Type * in the domain/host and user field as shown below to indicate that all users
connecting to the server will be mapped to the same account. For the purposes of this practice,
map the local administrator account to all accounts connecting to the Batch server.
Account mapping configuration depends on the security needs and configuration of

your models. For more information on configuring account mapping, see the Intergraph
Batch Services help. Other mapping options are possible. For instance, jobs submitted by
some users can be mapped to one account while jobs from other users can be mapped to a
second account. It is not a requirement for the mapped account to be a local administrator.
13. When finished, click Close.
Create Smart 3D Related Queues

The queues to be used with Smart 3D must be created before submitting jobs. To create the
queues you can use the ConfigureSP3DBatchQueue.exe utility provided by the software. This
utility will also create an additional environment variable needed for proper functioning of the
batch server.
14. Open Windows Explorer on the computer in which Intergraph Batch Services is installed.
15. Locate and execute the utility ConfigureSP3DBatchQueue.exe found in the following path
of the Smart 3D installation folder:
..\ProjectMgmt\Tools\bin\ConfigureSP3DBatchQueue.exe

16. Select the system defined queues SP3DProjectManagement, SP3DApplication, and

SP3DPrinting. The name of an SMTP server can be provided for emails to be sent to
submitters after jobs are processed (including error logs of the operation).
17. After queues are created successfully, the following message will appear.
18. Click OK. The queues will not be reflected in the Batch server interface until the services
are restarted. To do this, open the Windows services console and restart the service
Intergraph Batch Server.
19. Open the Batch manager to verify the queues were created.
Configuring the Batch Services Server for Drawings Tasks

20. In the folder [Smart 3D Installation folder]\Core\Container\Bin\Assemblies\Release, run
ConfigureDrawingsBatch.exe.
21. Click Yes and then click OK.

22. Append the following entries to the system PATH environment variable for 3D model data
documents to update:
- [Smart 3D Installation folder]\Core\Runtime
- [Smart 3D Installation folder]\Common2D\Rad2d\Bin
- [Smart 3D Installation folder]\GeometryTopology\Runtime
Excel Configurations
These configurations are required for the successful update of reports in Excel format.
23. Microsoft Excel must have the same security settings that are necessary for interactive
updates. Excel must be configured correctly for every mapped account on the batch server, so
that it can be accessed by the batch processes (Excel security settings to allow access to VB
Projects).
24. Microsoft Excel must be opened on the batch server machine at least once by each
mapped user.
Configure Queues for Jobs

You must have Smart 3D project administrator privileges to access this tool. When you are
logged in as an administrator, this tool is available under the Tools menu from Project
Management.
For sites, you must have the following privileges:
 In Oracle, you must have the SP3DProjectAdministrator role.
 In SQL, you must be a sysadmin on the server.
For models, you must have full access or write permissions on the selected model database.

26. Right click the Smart 3D node in the hierarchy root, then select the option Configure
Queues for Jobs.

27. Click OK.

28. Right click the model to be configured, then select option Configure Queues for Jobs.

29. Review the different job types and map them to queues as appropriate, then click OK.

Additional considerations
 Log files produced during a batch process are saved in a folder called
"SP3DBatchSvcTemp". The folder is created under the location defined by the system
variable %SYSTEMDRIVE%. Example "C:\SP3DBatchSvcTemp".
 Print jobs require printer access on both the client where the job is created and on the
server where the job will be performed. The server and the client machines must have
exactly the same printer setup, and every individual printer should have exactly the same
name on both the client and server machines. This issue is shared with the previous batch
implementation.
 The ConfigureDrawingsBatch utility must be run each time mapped account settings are
changed.
 If you are running 64-bit drawings batch services and Oracle, you must install the 64-bit
Oracle client on the computer running the batch services.

LAB 36: Submitting a job to a batch
server
Objectives
 Submit a job or schedule a task to an Intergraph batch server that is already configured for
use with Smart 3D.
2. Go to Tools > Backup option.
3. Note the submit job button appears as enabled. This button is only enabled when
Intergraph Batch services software is installed in the workstation where the job is being
submitted.

LAB 36: Submitting a job to a batch server
4. Fill the backup form as you normally would. The folders defined for output will be the
actual folders were the resulting files of the backup job will be placed.
5. Click Submit Job.

6. Select the batch server where the job will be processed from the drop down list and set
scheduling options for the backup job to be submitted. For this practice, you will set the
backup job to run once and five minutes from now.
7. Click OK, the following message will appear as a confirmation of the action.
8. Click OK to dismiss the dialog box, and then click Cancel in the backup form.
9. Open Batch manager if not already open and then verify that the job appears under the
SP3DProjectManagement queue.
10. Wait for the backup job to complete, the entry under the SP3DProjectManagement
queue will be automatically cleared if it is not a recurrent event.

11. Open the output folder where the backup files were set to be saved, verify the backup
files were created.
12. Open the SP3DBatchSvcTemp folder on the batch server and review the log files
created for the backup job. You may open the log files folder by typing
%SYSTEMDRIVE%\SP3DBatchSvcTemp in the address bar of any windows explorer
window.
13. When properly configured, the batch server can send emails notifying of job completion
or failure; these output files can be sent as attachments.
14. As an additional practice, use guidelines already provided and schedule a weekly job to
perform a Database Integrity check on the Site, Catalog, Model and Reports databases
of the training model. Verify results using the Batch manager to confirm the job is in the
queue and has been successfully executed.
15. Close Project Management and Batch Manager if they are open.

LAB 37: Adding User Defined Attribute
to Smart 3D Database
Objectives
 Add user defined attributes to objects in Smart 3D database.
1. In this lab practice we will add the Room Number attribute on Smart 3D object classes
using the workbook RoomNumber.xls delivered under [Smart 3D install
folder]\CatalogData\BulkLoad\ SampleDataFiles\
2. Start the Bulkload utility by going to Start > All Programs > Intergraph Smart 3D >
Database Tools > Bulkload Reference Data.

LAB 37: Adding User Defined Attribute to Smart 3D Database
3. Complete bulkload form providing the path to the Excel file "RoomNumber.xls" and
options as shown below:
Make sure the Catalog and Catalog schema databases for the Admin model are
selected correctly.
4. Click Load.

5. Once the bulkload is complete, review bulkload log file for any errors.
6. Start a new Smart 3D session and define your workspace in Admin_Model.

7. Switch to the Equipment and furnishing task.
8. Start the Place Equipment command on the vertical toolbar.

9. On the Select Equipment window, navigate to Equipment > Mechanical > Pumps >
Pump and select PUMP 001A-E and click OK.

10. The equipment properties dialog will be displayed. Note the Room Number attribute on
the Occurrence tab of the equipment properties under the Standard category.
11. Click OK on the equipment properties dialog and click in the graphic view to place the
equipment.
12. The Room Number attribute will be displayed on all the S3D object classes that we saw
in the RoomNumber.xls workbook. If time permits, try placing a few objects and check
for the Room Number attribute on their properties dialog.
13. Exit Smart 3D.

LAB 38: Adding Approval Status in
Smart 3D
Objectives
 Add approval reasons for objects modeled in Smart 3D. These approval reasons will be
shown on the properties page of modeled object on the configuration tab.
1. In this lab practice, we will add approval reasons on Smart 3D objects using the
workbook ApprovalReasons.xls delivered under [Smart 3D Install
folder]\CatalogData\BulkLoad\ SampleDataFiles\.
2. Start the Bulkload by going to Start > All Programs > Intergraph Smart 3D >
Database Tools >Bulkload Reference Data.

LAB 38: Adding Approval Status in Smart 3D
3. Complete the bulkload form providing the path to the Excel file "ApprovalReasons.xls"
and options as shown below:
Make sure the Catalog and Catalog schema databases are properly selected. The
ApprovalReasons.xls is a codelist file and has to be bulkloaded as such.
4. Click Load.

5. Once the bulkload is complete, review the bulkload log file for any errors.
6. Start a new Smart 3D session and define your workspace in SP3DTrain model using
filter U01 located under Plant Filters > Training Filters > U01.

7. Select the equipment E-102 in the workspace and go to its properties.

8. Switch to the Configuration tab on the Equipment properties dialog and note the new
Approval statuses that were bulkloaded in the catalog.
9. Close the Equipment properties dialog and exit Smart 3D.


Smart 3D Setup and Administration Practice Labs 2016 PDF

Uploaded by

Copyright:

Available Formats

Smart 3D Setup and Administration Practice Labs 2016 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Smart 3D Setup and Administration Practice Labs 2016 PDF

Uploaded by

Copyright:

Available Formats

Intergraph Smart 3D™

Setup and Administration Practice Labs

Wednesday, January 18, 2017

U.S. Government Restricted Rights Legend

Intergraph Smart 3D™ Setup and Administration Practice Labs 2

Intergraph Smart 3D™ Setup and Administration Practice Labs 3

LAB 2: Create new site, catalog, and model ........................................................................................... 11

LAB 3: Create permission groups and assign permissions ................................................................. 22

LAB 4: Simple Backup .............................................................................................................................. 33

LAB 5: Restoring a Model Database (Option 1)...................................................................................... 37

LAB 6: Restoring a Model Database (Option 2)...................................................................................... 41

LAB 7: Restoring a Model Database (Option 3)...................................................................................... 47

LAB 8: Deleting a Model ........................................................................................................................... 52

LAB 9: Deleting a Catalog......................................................................................................................... 54

LAB 10: New Catalog Command .............................................................................................................. 57

LAB 11: Manual Creation of System Hierarchy ...................................................................................... 61

LAB 12: Import Creation of System Hierarchy ....................................................................................... 66

LAB 13: Assign Specifications to Systems ............................................................................................ 68

LAB 14: Restore as copy Training Model ............................................................................................... 73

LAB 15: Workspace Simplification by Role ............................................................................................ 75

LAB 19: Model Data Reuse -Troubleshooting ...................................................................................... 112

LAB 21: Model Data Transform .............................................................................................................. 160

LAB 23: Database Maintenance ............................................................................................................. 178

Intergraph Smart 3D™ Setup and Administration Practice Labs 4

LAB 24: Database Integrity ..................................................................................................................... 182

LAB 25: Error log files............................................................................................................................. 191

LAB 26: Interference Checking .............................................................................................................. 194

LAB 28: Attach external 3D data as a reference (R3D) ........................................................................ 219

LAB 30: Update attached R3D models .................................................................................................. 228

LAB 34: Install Intergraph Batch Services ............................................................................................ 253

LAB 35: Configure Intergraph Batch Services ..................................................................................... 257

LAB 36: Submitting a job to a batch server .......................................................................................... 266

LAB 38: Adding Approval Status in Smart 3D ...................................................................................... 275

Intergraph Smart 3D™ Setup and Administration Practice Labs 5

Create Users and Groups in Windows

Pipe pipe1, pipe2

Structure struct1, struct2

S3Dusers pipe1, pipe2, struct1, struct2, equip1, hvac1, elect1

S3Dadmins pipe1, struct1, administrator

ProjectA pipe1, struct1

Verify MSDTC Settings for the Workstation

Intergraph Smart 3D™ Setup and Administration Practice Labs 6

Assign permissions in the file system

Intergraph Smart 3D™ Setup and Administration Practice Labs 7

Example: C:\Program Files (86)\Smart3D\3DRefData\SharedContent

Intergraph Smart 3D™ Setup and Administration Practice Labs 8

7. On the View tab, ensure Use Sharing Wizard option is unchecked.

12. Click OK until returned to the SharedContent folder Properties page.

Intergraph Smart 3D™ Setup and Administration Practice Labs 9

14. Click OK then Close.

Intergraph Smart 3D™ Setup and Administration Practice Labs 10

Create New Site and Catalog Databases

Intergraph Smart 3D™ Setup and Administration Practice Labs 11

2. Select Create a new site. Click Next.

3. Select Database type as appropriate for your classroom setup (MSSQL/Oracle).

Intergraph Smart 3D™ Setup and Administration Practice Labs 12

10. Click Next.

Intergraph Smart 3D™ Setup and Administration Practice Labs 13

11. Select Restore catalog from backup.