SmartPlant 3D Setup and Administration V2009.1

(1)

SmartPlant 3D Setup and Administration

Intergraph PPM Training

(2)

Prerequisites for this class:



Experience with Microsoft Windows Operating

System architecture



Experience with Microsoft SQL or Oracle database

server administration

(3)

Agenda

Day 1



Introduction to SmartPlant 3D (concepts, terminology)



System Setup



Project Hardware Sizing



Project Setup (Database Creation, permissions)

Day 2



Backup and Restore



Project Management (delete plants, delete catalogs, hierarchy icons,

create catalog)

(4)

Agenda (Cont’d)

Day 3



SP3D Common Applications



Model Data Reuse



Synchronization



Database Maintenance



Database Integrity



PDS Reference



Point Cloud Reference

Day 4



Error Logs



Interference Checking (IFC)

(5)

Agenda (Cont’d)

Day5



Reference 3D (R3D) Part II



Global Workshare Overview



Plant Version Upgrade



Smart Plant License Manager (SPLM)

(6)

(7)

SP3D Intro:

SmartPlant 3D synchronizes key elements of integration and

relationships.



Integration - SmartPlant 3D allows multiple engineering

disciplines to work concurrently and in real-time against

relational databases.



Relationships - SmartPlant 3D's relationship manager

controls design changes across disciplines, which in turn

establishes and maintains appropriate behaviors among

structures, equipment, and systems.

(8)

SP3D Intro: Server-Client

architecture

- Database Server

- Name Generator

- Symbols

- Interference

Checking Server

- SmartPlant 3D

Client

- SmartPlant 3D

Client

Ancillary servers

- Drawings

Batch Server

(9)

Site Database:

Contains all permission groups and related

facts to serve as the primary or main

database; it is also the container of the other

databases.

Catalog Database:

Contains the reference data that is used by all

disciplines.

Model Database: Contains and organizes all

of the three-dimensional objects in the plant.

Reports Database : Interacts with the other

five databases to generate tabular reports

from SmartPlant 3D data

Model Database

Site Database set

Catalog Database set

Reports Database set

(10)

Site 1

Model 1

Model 2

Model 3

Catalog 1

Catalog 2

Report 3

Report 2

Report 1

Multiple Plants can rely

upon the same Catalog.

(11)

Site 1

Model 1

Model 2

Model 3

Catalog 1

Catalog 2

Report 3

Report 2

Report 1

Multiple Plants can rely

upon the same Catalog.

(12)



Filter on database



Returns only the data you want to see

and builds a logical “Working Set”

• System

• Assembly

• Spatial (Volume or Planes)

• Logical Permission Groups

• Object Types/Properties

Site Database set

Catalog Database set

Reports Database set

Model Database

SP3D Intro: Define Workspace

(13)

CAD

SP3D Intro:

Single Database

SYSTEM

ASSEMBLY

SPACE

SYSTEM

SPACE

_ASSEMBLY

File boundaries inhibit

simultaneous

access to data

Databases provide easy

access to arbitrary subsets of data

Logical set of

databases

CAD CAD CAD CAD CAD CAD CAD CAD CAD CAD CAD CAD CAD CAD

Model

database

(14)

SP3D Intro: Rules Services

–

Design Rules

• Naming Rules

• Surface Style Rules

–

Clash Rules

• Server based

• Local based

Update

results

Update

design

changes

Periodic

display

refresh

Local application

SP3D

Periodic

query

changes

Server based

rules analysis

Local based

rules analysis

Database

(15)

• SmartPlant “Task” oriented interface

• Common windows interface

• Ribbon bars

• Graphic views

SP3D Intro: Common Windows Based

User Interface

Main

Task

Toolbar

Active

View

Status

Bar

Common

Toolbar

Workspace

Explorer

Active

command

Ribbon bar

Access

Control

(16)

SP3D Intro: Design Re-use

Copy to catalog or

instance in another

location

Internal relationships maintained.

External relationships exposed

(17)

Database Wizard – Project Management:

Allows quick restoration of the Catalog Database template that

contains all Intergraph delivered sample data.

Bulkload Utility:

Creates a new Catalog Database(s), and is used to maintain

existing Catalog Database(s).

SP3D Intro: Creating the Catalog

Database

.DAT

_{Catalog database set}

(18)

• Same task specific ribbon bars for placement and object-action

SP3D Intro: SmartStep Commands

Active properties

(19)

SP3D Intro: Administrative Guides



Project Management User's Guide



SmartPlant 3D Database Integrity Guide



SmartPlant 3D Global Workshare Guide



SmartPlant 3D Installation Guide



SmartPlant 3D Installation Checklist



SmartPlant 3D Interference Checking Guide



SmartPlant 3D Release Bulletin



SmartPlant 3D Troubleshooting Guide

(20)

(21)

(22)

System Setup: Server - Workstation



Hardware Recommendations



Software Prerequisites



Installation

(23)

System Setup: SP3D server

introduction



Purpose

One or multiple server machines can be used to

provide the following required services:

–

Database Server

–

Symbols Share

(24)

System Setup: SP3D ancillary

server



Ancillary servers are computers dedicated to

perform a specific task with the purpose to offload

processing from the main database server.



- Interference checking (IFC)



- Drawings batch update

(25)

System Setup: Hardware

Recommendations: Server

–

3 GHz Pentium 4 or multi-core processor (64-bit for medium and large

projects)

–

4 GB to 32 GB RAM depending on project size

–

Digital tape or DVD backup system for server

–

Access to DVD drive, either locally or through a network connection

–

100 BaseT or higher network interface

At least 3 physical drives recommended for a small size project with SQL

server 2005

• Operating System and Software

• SQL Data Files

(26)

System Setup: Software

prerequisites: Server



Supported Operating Systems

-

Microsoft Windows Standard/Enterprise Server 2003 Service Pack 2 (32-bit)

-

Microsoft Windows Standard/Enterprise Server 2003 R2 SP2 (32-bit and

64-bit)



Supported Database Servers

-

Microsoft SQL Server 2005 Service Pack 2 or higher [32 or 64 bits]*

-

Oracle Database 10g Release 2 (10.2.0.4) [32 or 64 bits]*

* Standard edition for stand-alone environments; Enterprise edition for Global

Workshare environments



Software Prerequisites

- Microsoft .NET Framework 2.0 and 3.5 SP1

- Adobe Reader

(27)

System Setup: Software Install

SP3D Server



Launch setup and pick “SmartPlant 3D Reference Data Installation” for

the SP3D reference data server software load

(28)

System Setup: Software Install

SP3D Server



Installation Tips

–

Account used to run SP3DNameGenerator as a

component service, must have a non-blank password.

–

If backups need to be stored over the network, the

account under which MSSQLSERVER service runs

should be a domain account (not Local System)

(29)

System Setup: SP3D Workstation

Machine Introduction



Purpose

–

Administrative client

–

Modeling client

–

Interactive (or batch) drawings creation

–

Isometric generation

–

(Optional) Interference detection server

–

(Optional) Drawings batch server

(30)

System Setup: Hardware

Recommendations: Workstation



3 GHz Pentium 4 processor or Core 2 Duo



4 GB RAM



Access to a DVD drive, either locally or through a network connection



100BaseT network interface



Graphics card designed for 3D intensive applications that meet the following requirements:

• Color depth of 65,536 colors or higher

• 32-bit main RGBA pixel buffer

• Hardware OpenGL 1.1 support

• Hardware Z buffer: 32 bit

• 128 MB RAM for single screens, 256 MB RAM for dual screens

• 4-bit minimum overlay buffer support

• 8-bit stencil buffer

• Hardware Anti-aliasing support recommended

• Hardware Alpha blending support recommended to improve speed of translucent object display

• Graphics acceleration set to full

(31)

System Setup: Software Prerequisite

Workstation



Supported Operating Systems and Required

Components

-

Microsoft Windows Vista Business Client 1.0 with Service Pack 1 (32-bit

or 64 bit)

-

Microsoft Windows XP Professional Service Pack 3 (32 or 64 bits)



Supported database clients and required

versions

-

Microsoft SQL Server 2005 Standard Service Pack 2 or higher (optional)

(32)



Software Prerequisites

–

Microsoft Internet Explorer 7.0 (required for viewing the online

documentation delivered with the software)

–

Adobe Reader 7.0 or higher

–

Microsoft XML Core Services (MSXML) 6.0

–

Microsoft .NET Framework 2.0 and 3.5 SP1

–

Microsoft Data Access Components (MDAC) 2.8.1 (MDAC 2.8.1 is

delivered as part of Microsoft XP Service Pack 2.)

–

Database system client software (SQL or Oracle)

• Oracle Client 10g rel2 (10.2.0.4) (Oracle “Light Client” will not work)

• SQL Server 2005 Client SP2

–

Microsoft Office 2003 or Microsoft Office 2007

–

SmartPlant License Manager 11.0

System Setup: Software Prerequisite

Workstation

(33)

System Setup: Software Install

SP3D Workstation



From Installation CD pick “SmartPlant 3D Installation” for the Workstation

Install

(34)

System Setup: Software Install

SP3D Workstation



Installation Tips

–

Make sure Distributed Transaction Coordinator Windows

service is started and its startup type is set to Automatic

–

When installing an administrator’s machine, choose all

optional components such as 3D Server Connectivity and

Project Management for a complete installation package

–

If installing both Server and Workstation builds on the

same machine for the purpose of training, make sure

installation path is unique for both. For example, install

Server to C:\Program Files\SmartPlant\3D\Server and

Workstation to C:\Program

(35)

System Setup: Optional Software

Workstation

Solid Edge v20

–

May be used for creating equipment symbology

Visual Basic 6 with SP6

–

Required for creating graphic visual basic symbols, macros, custom

rules, etc.

PDS Data Access components

–

Allows referencing or export of PDS Projects

Point Cloud vendor software

–

Allows referencing Point Cloud projects in SP3D

Intergraph Batch Services

(36)

The major bottleneck for performance in a database

server for SP3D is disk I/O.

System Setup: File and Database

Server Considerations

*.mdf

(37)

(38)



Three different ways to setup SP3D.

Server

Name Generator

Database Templates…

Workstation

Project Management

Bulkload

IFC…

SP3D Setup

Standalone

(39)

SP3D Setup



When setting up SP3D as a Standalone

configuration, change the default installation

folder for Server (Reference Data) and

(40)

SP3D Setup

Software versioning is based on the different

releases.



RTM - Release To Manufacturing (CD/DVD)



Service Packs



HotFixes

(41)

Silent Install



SP3D Can be installed through command line



Ideal to reduce deployment and maintenance

impact

(42)

Silent Install



Msiexec.exe /I

"\\path\to\SP3D\software\SP3DInstallation.msi

" SERIALNUMBER=XXXXXXXXXXXXXX SLAACCEPT=Yes

ADDLOCAL=All REMOVE=PIDService /qn /l*

%temp%\SP3DSetup.log

(43)

SP3D Setup

Before Installing…



Use an account with administrative privileges.



Verify that all prerequisite software have been

installed.



Don't skip any restart recommended by the

software.



Restart after installing RTM, even if not prompted to

do so.

(44)

SP3D Setup

(45)

SP3D Setup

(46)

SP3D Setup

Server - RTM

(47)

SP3D Setup

Server - RTM

(48)

SP3D Setup

Server - RTM

(49)

SP3D Setup

Server - RTM

(50)

SP3D Setup

Server - RTM

(51)

SP3D Setup

Server - RTM

(52)

SP3D Setup

Server - RTM

(53)

SP3D Setup

Server - RTM

(54)

SP3D Setup

Server - RTM

(55)

SP3D Setup

Server - RTM

(56)

SP3D Setup

Server - RTM

(57)

SP3D Setup

(58)

SP3D Setup

(59)

SP3D Setup

(60)

SP3D Setup

(61)

SP3D Setup

(62)

SP3D Setup

(63)

SP3D Setup

(64)

SP3D Setup

(65)

SP3D Setup

(66)

SP3D Setup

(67)

SP3D Setup

(68)

(69)

SP3D Setup

HotFix installation

-

Installed through a GUI with similar options to

RTM installation.

-

Can be installed silently with a script

-

HotFixes are listed as updates to SmartPlant

(70)

SP3D Setup

(71)

SP3D Setup

Final Configurations for a Workstation

-

Enable and check security settings for MSDTC

-

Verify firewall is turned off or set proper exceptions.

-

Set the Distributed Transactions Coordinator

Windows Service to automatic startup.

-

Register SQL Server or configure the Oracle Net

(72)

SP3D Setup

Final Configurations for a Server

-

Adjust proper permissions on the Symbols and

Database Templates shared folders.

-

Check access permissions on Name Generator

(73)

(74)

Project Setup: Hardware sizing

recommendations



Hardware sizing, especially for servers, depends on many

factors such as:

- The number of concurrent users per site

- The number of sites (Global workshare)

- The size of the project (which translates into the size of the

databases)

(75)

Project Setup: Hardware sizing

recommendations



The number of users for each project size (small, medium, and large) is

the effective number connected to a single server. The effective number

of users should be calculated by taking into consideration:



Drawing Batch server - add 3 users



Remote IFC - add 1 user



Global Workshare Setup - For each server add 25% of the total

concurrent users of all the other sites.

Effective concurrent users for one site = Cu + (0.25 * (Ct))

Where:

Cu = concurrent users for this site

(76)

Project Setup: Hardware sizing

recommendations

Example:



In a configuration with 6 sites, 40 users at 5 sites, 5 users at 1 site:

• When the three sites with 40 users are working concurrently, the

equivalent number of users at each site is:

40 + (0.25 * (2*40)) = 60 concurrent users

• When all 6 sites are working concurrently, the equivalent number of users

at each site is:

a. The equivalent number of users at each of the 40-user sites is: 40 + (0.25 * (165))

= 81 users

(77)

Project Setup: Hardware sizing

recommendations

Project Size

Effective users

on one server

Model

database size

IFC Server

Batch Server

Small project

1 to 15

Up to 8 GB

Separate

server or

workstation

Separate server

or workstation

Medium project

16 to 50

8 – 15 GB

Separate

server or

workstation

One or more

separate server

or workstation

Large project

51 to 100

15 GB or more

Separate

server or

workstation

Multiple separate

server or

(78)

Project Setup: Hardware sizing

recommendations

Project Size

Small

Medium

Large

Number of 3.0 GHZ Pentium 4 or Xeon

Processors (one core Duo counts as

two)

2 2 – 4

4 – 8 or more

Memory for SQL Server 2005 and

Oracle 10g

4 – 8GB

8 – 16GB

32+GB

Bus Size, OS, and Database

32 bit or 64

bit

(79)

Project Setup: Familiarize with the

software

(80)

Project Setup: Database creation



Site and Catalog Creation

–

Database Wizard



Plant Creation

(81)

Project Setup: SP3D Permissions

Hierarchy



Plant/Catalog

–

Top level item in the hierarchy



Permission Group Folder

–

A set used to organize permission groups



Permission Group

–

Portion of plant/catalog over which various

people have various levels of access and

responsibility

(82)

Project Setup: SP3D Permissions

Hierarchy



This hierarchy is seen only in Project Management



Can have unlimited number of levels of folders



Cannot have permission groups and

permission group folders at the same level



Permission Group is the last leaf in a branch



Copy/Paste permission groups available

(83)

Project Setup: SP3D Permissions

Sample Hierarchy

(84)

Project Setup: SP3D Permissions

Modify Hierarchy

Rename command

Folders cannot be deleted if there are permission groups

under them

Permission groups containing objects cannot be deleted

Copy/paste copies the names and permissions from

(85)

Project Setup: SP3D Permissions

Plant root vs permission group level



Permissions can be granted to Windows users and/or groups

at the plant/catalog root and permission group level



Permissions granted at plant/catalog root level allow access

to modify permissions hierarchy within the plant and perform

various administrative tasks.



Permissions granted at

permission group level affect access

to objects within that permission

group. These are used for general

modeling purposes.

(86)

Project Setup: SP3D Permissions

Association concept



When objects are placed, they will be automatically assigned

to a permission group.



Objects can be associated to systems assigned to

permission group where user has write or full control access



Objects can only be modified or deleted if user has write or

full control access to permission group assigned to the

object.



You can associate objects to those Work Breakdown System

(WBS) items to which you have write or full control access

based on the permission group they belong to.

(87)

Project Setup: SP3D Permissions

Access levels



Read – Can view objects



Write – Can create/modify/delete objects

(88)

Project Setup: SP3D Permissions

Approval Status



Working – This is the state an object is in when a designer is working on it



In Review – This is the state to which a designer can send objects for

revision



Rejected – If an object is found to be incorrect, reviewer can send object

to this status



Approved – If an object is found to be correct, reviewer can send object to

this status

(89)

Project Setup: SP3D Permissions

Status Change



Read – can’t change status



Write

–

can change from Working to InReview

–

can change from InReview to Working

–

can change from Rejected to Working

(90)

Project Setup: SP3D Permissions

Logical Model

View

Create/Modify/

Delete

Sent to

review/

bring back

Approve/

reject

Read



Write



Full Control



(91)

Project Setup: SP3D Permissions

Add Users

(92)

Project Setup: SP3D Permissions

Remove users



Select the users to be removed



Pick the places they need to be

removed from

(93)

Setup and Administration Lab

(94)

(95)

Backup and Restore: Overview

Backup



Project Management Backup



Manual backup of the Symbols folder

Restore options



Restore one or more plant databases from

backup



Restore plant for selective recovery of

model objects

(96)

Backup and Restore: Project

Management Backup



Backs up the Model Catalog and Site databases.

A backup configuration file (bcf) containing information about

the backup set is created in the location specified



Backup files will be saved to database server by default



Backups may be saved to a network location where MS SQL

Server service account has write access (Oracle backups have

to be made to a UNC path)

(97)

Backup and Restore: Project

Management Backup



Reports databases are not backed up



There are no individual files to be backed up – only databases



To complete the backup set, user needs to manually backup

the symbols share for the plant

Users (as well as accounts used as logon for Oracle services)

need to have write permissions on the folder under which

(98)

Backup and Restore: Project

Management Backup

(99)

Backup and Restore: Restore

options

(100)

Backup and Restore: Restore one or

more plant databases from backup

Restores previously backed up plants overwriting the existing

one.

You can only restore a complete plant

Option to leave Catalog in place and link it with plant being

restored



Items manually backed up (symbols folder) need to be

manually restored as well

(101)

Backup and Restore: Restore plant for

selective recovery of model objects



Restores a plant from backup, without overwriting the existing

plant.



Allows for selective recovery of work from previous versions

of the same Model.



Functionality to restore objects from a previous backup into

the existing plant without losing object identities and

relationships.



The restored project would exist in the Site database in

parallel to the current project and would share the same

catalog.

(102)

Backup and Restore: Restore plant as a

copy



Allows the import of projects from a different site database.



Allows a backup to be used to create a 2

nd

_{project within an}

existing Site and Site Schema .



Ability to change the name of the Plant and the restored

Model and Catalog databases.



When the selected plant to restore is registered with

SmartPlant Foundation, the registration is removed from the

copy during the restore.

(103)

Backup and Restore: Off-site

Restore

May be used to restore entire project on a new location, it can

be a server change, or to restore a backup received from a third

party company.

-

Using database wizard, restore site from backup set

-

Using project management, restore plant from backup (this

brings in catalog associated with the plant)

-

Regenerate report database

-

Manually copy all the symbols and outputs to the remote site

-

Custom symbol dlls need to be registered on each client

workstation at the remote site if required.

(104)

Project Management: Delete a Plant



Full Control permission at the root level.



Drop or leave the physical database files in place.



For plants in Oracle, the software does not delete all of the

associated schemas. To delete schema information after

deleting an Oracle plant, you must use the Oracle Database

Tools Wizard for SmartPlant 3D located at [Product

Directory]\ProjectMgmt\Tools\Bin\SP3DOracleDBToolsWizar

(105)



Catalogs can only be deleted if they are not associated with

any plant.



On Oracle servers, Catalog must also be deleted using the

Oracle Database Tools Wizard for SmartPlant 3D

Project Management: Delete a

Catalog

(106)

Project Management: Hierarchy

Icons

- Top level of the hierarchy

- Reference data

- Catalog associated with a plant

- Catalog associated with a plant. Missing database

- Catalog associated with a plant. Needs to be upgraded

- Catalog not associated with a plant

- Catalog not associated with a plant. Missing database

- Catalog not associated with a plant. Needs to be upgraded

- Plant model

- Plant model. Missing database

- Plant model. Needs to be upgraded

- Permission group folder

(107)

Project Management: New Catalog

Command



Create a new empty catalog or create a catalog from a

template.



Default permission groups and access rules are created.



You cannot create or modify data in the new catalog through

the Catalog task until after the catalog is associated with a

plant.



In a Global Workshare configuration, the Database > New >

Catalog command is available at the Host location, but not at

(108)

Project Management: New Catalog

Command



An empty catalog is a catalog database that contains all of

the tables, procedures, views, and so on, but does not

contain any data, such as part data or specifications.



Use Apprepos.dat or Apprepos.dmp to create an Empty

(109)

Project Management: New Catalog

Command

(110)

Custom Properties: Define Property

Schema



Can define additional properties for plants, permission

group folders and permission groups



Properties can be viewed in project management task

but are also reportable



Property schema for plants is stored in the site to which

they belong



Property schema for folders and permission groups is

stored in the plant to which they belong

(111)

Custom Properties: Define plant

property

(112)

Setup and Administration Lab

(113)

(114)

Plant Organization: Contents



System Hierarchy



Create and Modify Systems Hierarchy

(115)

Plant Organization: System

Hierarchy



A system is a way to group objects logically



Systems have other systems as children creating a hierarchy

with unlimited levels



Each system can contain several child subsystems



Subsystems can belong to a different permission group from

their parent



Many different types of systems are supplied



Every object must belong to a system



Different types of objects can be associated with different

system types

(116)

Plant Organization: System Types



Generic system



HVAC system



Equipment system



Pipeline system



Unit system



Conduit system



Electrical system



Piping system



Structural system



Area system

(117)

Systems and Specifications:

Creating Systems



Create New System Command



Importing from Excel

(118)

Systems and Specifications: Create

New System Command



Creates a system as a child of

the currently selected system



Currently active name rule for the

system type being created is

used to generate the name



If currently active name rule is

‘User-defined’, you can enter the

name during creation

(119)

Systems and Specifications: Create

New System Command



Systems can be created from

workspace explorer hierarchy.

(120)

Systems and Specifications: Create

New System Command



Systems can be created from

workspace explorer hierarchy.

(121)

Systems and Specifications: Copy

and paste systems



Select a system then copy



To select the entire hierarchy under a system, right-click the

system then select nested



Paste the hierarchy where desired



You can copy and paste system hierarchies between two

plants in same site

(122)

Systems and Specifications: Import

Systems from external Excel Workbook



You can create an entire systems

hierarchy or add pipelines to an

existing hierarchy



Allowed specifications for

pipelines can also be set in the

workbook.



If specifications are allowed by

import, child systems will not

inherit specifications allowed at

parent levels, including the root

level. Specifications will have to

be allowed system by system

(123)

Systems and Specifications: Editing

Systems



Deleting Systems



Renaming Systems

–

User defined

–

Default naming rule



Moving Systems

–

Move using parent property

(124)

Systems and Specifications: Allow

specifications



Specifications limit part selection and placement based on

rules.



Are defined in the Catalog and must first be added to the Plant



All systems inherit the specifications allowed in at Plant root



Each system must be allowed at least one specification



Specifications allowed for a system are automatically inherited

by its children, unless they were allowed using import command

with Excel workbook.

(125)

Systems and Specifications: Define

allowed specifications

(126)

• Whole categories can be selected with a single click

Systems and Specifications: Define

allowed specifications

(127)

• Multi-select of specifications and/or categories

Systems and Specifications: Define

allowed specifications (Cont’d)

(128)

• Multi-select of specifications of different categories

Systems and Specifications: Define

allowed specifications

(129)

• Easier method to remove allowable specifications from a system

(Multi- select allowable specifications and press delete key)

Systems and Specifications: Define

allowed specifications

(130)

Setup and Administration Lab

(131)

Common Applications

(132)

(133)

Model Data Reuse: Introduction



Model Data Reuse (MDR) is a way to copy

large amounts of 3D model data in a robust,

scalable and intelligent way



MDR supplements the current copy/paste

process – the existing process remains in

place for smaller sets of data

(134)

(135)

Model Data Reuse: Advantages



Process works in Project Management task as a

wizard – interaction is not required



Does not require objects to be loaded into memory –

process is scalable and can copy much larger sets

of data



Software breaks down copy set into multiple

transactions –process is robust and can tolerate a

failure and continue with the rest of the objects

(136)

Model Data Reuse: Advantages



Software determines the sequence in which to copy

objects – incorporates best practices into the

process



Permission group mapping to existing or default

permission group



Transformation can be chosen using coordinate

systems



Very good logging of process (including failures)

(137)

Model Data Reuse



MDR command exists only in Project

(138)

Model Data Reuse: Workflow

Begin Model Data

Reuse

Select source objects

based on systems

Select disciplines

to be copied

Select a

transformation to

position copied

objects

Confirm copy

and review

results

Select source objects

based on filters

Select

destination plant

and system

(139)

Model Data Reuse



The Model Data Reuse command invokes a

wizard with which you set up the data reuse

operation.

(140)

Setup and Administration Lab

(141)

(142)



Used to propagate changes from the catalog to the model

(including property, specification, and symbol changes)

(143)

Synchronize Model with Catalog

The model is refreshed to include the following:



Modifications to properties that have been bulkloaded into the

catalog.



Modifications to name rules.



parts that have been deleted from the Catalog are added to

the To Do List.



Parts created with the Copy to Catalog command may be

converted from non-cached to cached format to improve

performance.

(144)

Synchronize Model with Catalog



Synchronization can take more time if changes are

updated by a user with write or higher level of

access to all permission groups – use a login who

has no permissions on model objects to perform the

synchronization command instead, this will create

ToDo records of objects that need to be updated.

(145)

(146)

(147)

Database Maintenance Command



Provides a tool to purge temporary data that may cause

performance issues.

(148)

Database Maintenance Command



Delete temporary symbol variations (flavors) in database

-Specifies that you want to delete any orphan flavors in the

database. These are temporary symbol variations that the

software used during creation or placement of certain

symbols.



Delete records of objects that users have deleted from model



Rebuild selected indexes

(149)

(150)

DB Integrity: Overview



Database integrity problems are data problems that

can prevent modeling and can impact the accuracy

of deliverables such as drawings or reports. These

problems can be grouped into the following types:

–

Runtime objects and relations that are not in a workable state or are

incorrect

–

Persisted objects and relations that are not in a workable state or are

incorrect



A typical example of a database integrity issue is an

object that exists without a mandatory relation to

(151)

DB Integrity: Overview

Important



These errors are not expected. However, in the event that

they occur, you can correct them by taking the actions

described on the reports or by executing a clean action.



We strongly recommend that you check the databases from

time to time and promptly report any unknown problems to

Intergraph. Please provide details about how to reproduce

the problem.



If you receive a database integrity error that is not listed in

documentation, contact Intergraph Process, Power & Marine

Support. Be prepared to provide a backup of the databases if

requested.

(152)

DB Integrity: Workflow



The workflow to address database integrity issues

have three overall steps:

1. Check database integrity.

2. Run reports to review errors.

(153)



Checking Database Integrity

Check Database Integrity runs directly on a database (Site, Catalog,

or Model), and creates records for the objects that need to be cleaned.

Once the database has been scanned for errors, you can generate a

report to review the errors that the Check Database Integrity

command generated.

You can run this command for several different reasons:

–

To check the database for objects with integrity problems

–

To confirm that objects have been deleted or cleaned

–

To check for new problems

(154)

DB Integrity: Run Reports



Running Database Integrity Reports

The software includes various report templates intended for diagnosing

database integrity issues. You can run these report templates by opening

a session in the software and clicking Run Report command from the

Tools menu. Report templates are located in the Catalog Reports tab

then under Report > Types of Reports > Diagnostics node. Select any

of the four following reports:

Diagnostic clean database issues

Diagnostic clean database issues grouped by problem description

Diagnostic clean database issues grouped by status

(155)

DB Integrity: Run Reports (cont’d)

–

DataStore - Displays whether the problem exists in the model or

–

Catalog database.

–

Problem Description – Use to reference problem in DBIntegrity.pdf

–

Status Check Database Integrity

-–

Severity - Fatal, Crucial, High, or Normal

–

Action to Take - Describes what to do to fix the problem. Possible

values include No Action, To Be Removed or To Be Repaired. If the

action is To Be Repaired, you should run Clean Database custom

command.